date:20181022

Your first issue appears to be a duplicate of bug 1650259:

  "1 no audio on audio jack"

Please remove mention of that here, and anything else that is a separate
bug so all that's left is a different bug to 1650259, and is a single
issue. Each issue should go in a separate bug.

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

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

Title:
  wrong behaviour of interface - audio specific

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  report
  1 no audio on audio jack
  2 in trying to fix after testing sound with the audio test Right and Left i 
changed the stereo to 5-1 surround option available in the test windows
  3 this caused to remove from the audio setting windows all output devices ( 
now is empty) 
  Audio stopped working completely and the volume in the top bar had the x and 
I cannot activate.
  is gray

  4 I just update the system with regular updates and the sound now work
  on the browser but the volume still have an x and is greyed but the
  Audio is  active!! I can hear sound on video on  youtube and and play
  music but I cannot adjust volume.

  5 try to activate pavucontrol but get message " establishing
  connection with pulseaudio please wait " but no responce

  system information:
  Linux jaki-XPS-13-9350 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
   suppose to be one of the certified laptop

  Regarding the jack still do not work and when inserted the jack the
  audio from internal speaker stop but there is no output. Dell changed
  the motherboard but the problem persisted, tried windows 10 on a live
  usb memory and sound worked out of the jack.

  willing to let someone to log on the system and check remotely

  jaki@jaki-XPS-13-9350:~$ xprop WM_CLASS
  WM_CLASS(STRING) = "unity-control-center", "Unity-control-center"

  unity-control-center:
Installato: 15.04.0+16.04.20160705-0ubuntu1
Candidato:  15.04.0+16.04.20160705-0ubuntu1
Tabella versione:
   *** 15.04.0+16.04.20160705-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   15.04.0+16.04.20160413-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  jaki@jaki-XPS-13-9350:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/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 Dec 16 13:29:44 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-06-25 (174 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  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: Upgraded to xenial on 2016-09-07 (99 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 0H67KH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1650536/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]

** Summary changed:

- No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell 
XPS 13 9360/9370]
+ No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell 
XPS 13 9360]

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card

2018-10-22 Thread Walter Garcia-Fontes

** This bug is no longer a duplicate of bug 1781294
   No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell 
XPS 13 9360/9370]

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

Title:
  [XPS 13 9370,  Intel Corporation Sunrise Point-LP HD Audio (rev 21),
  Speaker, Internal] Pulseaudio fails to detect card

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the 18.10 development version from 18.04 only
  "Dummy sound" is shown. The speakers are not recognized, but plugging
  headphones works. The system was working well in 18.04.

  With:

  sudo alsa force-reload

  the speakers start to be shown in the sound system parameters and
  sound is reproduced through the speakers normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/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:Unity7:ubuntu
  Date: Fri Sep 21 07:18:03 2018
  InstallationDate: Installed on 2018-04-09 (164 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+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 1798712] Re: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

Please also try uninstalling Sophos Anti-Virus. That's one thing that
might be causing some kind of resource exhaustion, which could be the
root cause here.

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

Title:
  [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Incomplete
Status in rtkit package in Ubuntu:
  Incomplete

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

That was for people like Justin whose pulseaudio process is missing, not
running.

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

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

Which doesn't seem to include you (bug 1793640). Maybe we need to unmark
that as a duplicate...?

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

2018-10-22 Thread Walter Garcia-Fontes

Daniel, I did what you suggest in #10 and no change.

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

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)

Ah okay well then it's a mystery, kernel could see it as hwinfo sound 
showed, pulse audio could not even after purging reinstalling it and alsa.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 23 Oct 2018, Daniel van Vugt wrote:

> Date: Tue, 23 Oct 2018 03:51:58 -
> From: Daniel van Vugt 
> Reply-To: Bug 1799203 <1799...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1799203] Re: [Mac-Pro 1,
> 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to
> Ubuntu 18.10)
> 
> It appears "AudioIPC Server" is actually Firefox. It shows up as such
> in:
>
>  Settings > Sound > Applications
>
> when Firefox is playing audio.
>
> So I don't think that's related to this bug at all.
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799203
>
> Title:
>  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
>  upgrading to Ubuntu 18.10)
>
> Status in pulseaudio package in Ubuntu:
>  Incomplete
>
> Bug description:
>  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
>  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
>  at all.  The kernel seems to detect the hadware okay:
>
>  hwinfo --sound
>  22: PCI 1b.0: 0403 Audio device
>[Created at pci.378]
>Unique ID: u1Nb.8PjrOxLnqG6
>SysFS ID: /devices/pci:00/:00:1b.0
>SysFS BusID: :00:1b.0
>Hardware Class: sound
>Model: "Intel 631xESB/632xESB High Definition Audio Controller"
>Vendor: pci 0x8086 "Intel Corporation"
>Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
>Revision: 0x09
>Driver: "snd_hda_intel"
>Driver Modules: "snd_hda_intel"
>Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
>IRQ: 36 (119384 events)
>Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
>Driver Info #0:
>  Driver Status: snd_hda_intel is active
>  Driver Activation Cmd: "modprobe snd_hda_intel"
>Config Status: cfg=new, avail=yes, need=no, active=unknown
>
>   But there is no sound output, pavucontrol does not show ANY hardware to 
> configure.  I have
>  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
> reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
> in pavucontrol and there is no audio output.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.10
>  Package: pulseaudio 1:12.2-0ubuntu4
>  Uname: Linux 4.18.0-10-lowlatency x86_64
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
> '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
> '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
> 1:
>  CurrentDesktop: MATE
>  Date: Mon Oct 22 04:11:54 2018
>  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  SourcePackage: pulseaudio
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions
>

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model:

[Touch-packages] [Bug 1580216] Re: Color manager breaks Zebra ZPL

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Color manager breaks Zebra ZPL

Status in cups package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04.3 LTS
  CUPS 1.7.2-0ubuntu1.7
  On new install, I setup a Zebra printer (USB). I guess I'm used to the old 
CUPS web UI because I didn't even notice the Color Manager option. So I didn't 
uncheck it. If you leave Color Manager enabled it will cause some print jobs to 
not print but show the job completed normally.

  #EDIT: Issue remains with color manager disabled

  D [10/May/2016:09:26:18 -0500] [Job 56] Failed to send: 
org.freedesktop.ColorManager.Device.NothingMatched:nothing matched expression 
'Gray.Thermal.203dpi,Gray.Thermal.*,Gray.*.203dpi,Gray.*.*,*'
  D [10/May/2016:09:26:18 -0500] [Job 56] Failed to get profile filename for 
cups-TestTouch
  D [10/May/2016:09:26:18 -0500] cupsd is not idle any more, canceling shutdown.
  I [10/May/2016:09:26:18 -0500] [Job 56] no profiles specified in PPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1580216/+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 1574862] Re: CUPS attached printer always paused

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  CUPS attached printer always paused

Status in cups package in Ubuntu:
  Expired

Bug description:
  CUPS network printing has not worked for several weeks now.  I can
  print to the printer from the system it is physically attached to by
  USB; the printer shows as Idle-ready to print.  But from another
  computer on the same LAN the printer shows as paused and all of the
  print jobs as held.

  jcobban@jcobban-laptop:~$ /usr/lib/cups/backend/snmp
  jcobban@jcobban-laptop:~$ lpinfo -v
  network https
  network ipp
  network ipps
  network http
  network ipp14
  network beh
  network socket
  network lpd
  network smb
  direct hp
  direct hpfax
  network 
dnssd://HP%20Deskjet%20F4500%20series%20%40%20jcobban-server._ipp._tcp.local/cups?uuid=d67423d3-4c38-341a-5cef-03a958e31b7e
  jcobban@jcobban-laptop:~$ sudo 'usr/lib/cups/backend/dnssd
  > '
  [sudo] password for jcobban: 
  sudo: usr/lib/cups/backend/dnssd
  : command not found
  jcobban@jcobban-laptop:~$ sudo /usr/lib/cups/backend/dnssd
  DEBUG: Querying 
"HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local"...
  DEBUG: Querying 
"HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipps._tcp.local"...
  DEBUG: Querying 
"HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._printer._tcp.local"...
  DEBUG: sent=0, count=3
  DEBUG2: query_callback(browser=0x558f5b5aadf0, interfaceIndex=2, protocol=1, 
event=0, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local",
 rrclass=1, rrtype=16, rdata=0x558f5b5ac6f0, rdlen=474, flags=5, 
context=0x558f5b5a8bd0)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "rp=printers/HP-Deskjet-F4500-series".
  DEBUG2: query_callback: "ty=HP Deskjet f4500 Series, hpcups 3.15.7".
  DEBUG2: query_callback: 
"adminurl=https://jcobban-server.local:631/printers/HP-Deskjet-F4500-series;.
  DEBUG2: query_callback: "note=jcobban-server".
  DEBUG2: query_callback: "priority=0".
  DEBUG2: query_callback: "product=(HP Deskjet f4500 All-in-one Printer 
Series)".
  DEBUG2: query_callback: 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf".
  DEBUG2: query_callback: "URF=DM3".
  DEBUG2: query_callback: "UUID=d67423d3-4c38-341a-5cef-03a958e31b7e".
  DEBUG2: query_callback: "TLS=1.2".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "printer-state=3".
  DEBUG2: query_callback: "printer-type=0x900E".
  DEBUG2: query_callback(browser=0x558f5b5aadf0, interfaceIndex=2, protocol=0, 
event=0, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local",
 rrclass=1, rrtype=16, rdata=0x558f5b5ac940, rdlen=474, flags=5, 
context=0x558f5b5a8bd0)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "rp=printers/HP-Deskjet-F4500-series".
  DEBUG2: query_callback: "ty=HP Deskjet f4500 Series, hpcups 3.15.7".
  DEBUG2: query_callback: 
"adminurl=https://jcobban-server.local:631/printers/HP-Deskjet-F4500-series;.
  DEBUG2: query_callback: "note=jcobban-server".
  DEBUG2: query_callback: "priority=0".
  DEBUG2: query_callback: "product=(HP Deskjet f4500 All-in-one Printer 
Series)".
  DEBUG2: query_callback: 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf".
  DEBUG2: query_callback: "URF=DM3".
  DEBUG2: query_callback: "UUID=d67423d3-4c38-341a-5cef-03a958e31b7e".
  DEBUG2: query_callback: "TLS=1.2".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "printer-state=3".
  DEBUG2: query_callback: "printer-type=0x900E".
  DEBUG2: query_callback(browser=0x558f5b5aadf0, interfaceIndex=-1, 
protocol=-1, event=2, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipp._tcp.local",
 rrclass=1, rrtype=16, rdata=(nil), rdlen=0, flags=0, context=0x558f5b5a8bd0)
  DEBUG2: query_callback(browser=0x558f5b5aae90, interfaceIndex=2, protocol=1, 
event=0, 
fullName="HP\032Deskjet\032F4500\032series\032\064\032jcobban-server._ipps._tcp.local",
 rrclass=1, rrtype=16, rdata=0x558f5b5acb90, rdlen=474, flags=5, 
context=0x558f5b5aaa00)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "rp=printers/HP-Deskjet-F4500-series".
  DEBUG2: query_callback: "ty=HP Deskjet f4500 Series, hpcups 3.15.7".
  DEBUG2: query_callback: 
"adminurl=https://jcobban-server.local:631/printers/HP-Deskjet-F4500-series;.
  DEBUG2: query_callback: "note=jcobban-server".
  DEBUG2: query_callback: "priority=0".
  DEBUG2: query_callback: "product=(HP

[Touch-packages] [Bug 1572489] Re: Canon MF4330d needs usb-no-reattach-default=true

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Canon MF4330d needs usb-no-reattach-default=true

Status in cups package in Ubuntu:
  Expired

Bug description:
  Following the instructions on
  , I'd like to
  report that my Canon MF4330d (USB) needs usb-no-reattach-default=true
  to print the 2nd job; otherwise it only prints the first one after
  each power cycle.

  $ lsusb
  Bus 003 Device 007: ID 04a9:26ee Canon, Inc.

  $ lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  $ apt-cache policy cups
  cups:
Installed: 2.1.0-4ubuntu3
Candidate: 2.1.0-4ubuntu3
Version table:
   *** 2.1.0-4ubuntu3 0
  500 http://nl.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CupsErrorLog:
   W [20/Apr/2016:11:48:49 +0200] Notifier for subscription 62 (dbus://) went 
away, retrying!
   W [20/Apr/2016:11:48:49 +0200] Notifier for subscription 65 (dbus://) went 
away, retrying!
   W [20/Apr/2016:11:48:49 +0200] Notifier for subscription 68 (dbus://) went 
away, retrying!
  Date: Wed Apr 20 11:58:45 2016
  Lpstat: device for Canon: 
usb://Canon/MF4320-4350%20(UFRII%20LT)?serial=SJ3008471311L=1
  MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=d901b113-8377-400e-9d0b-8a3bb6e3caac ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: cups
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: Z68AP-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68AP-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1572489/+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 1582251] Re: CUPS does not find network Samsung SCX-4729FD printer

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  CUPS does not find network Samsung SCX-4729FD printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  CUPS does not find network Samsung SCX-4729FD printer i.e. one
  connected to router's ethernet socket. This error is intermittent. It
  occurs because I have to keep deleting and adding networked Samsung
  SCX-4729FD printer, due to desktop being informed that printer is not
  connected when attempting to print.

  printer-driver-splix (version 2.0.0+svn315-2fakesync1) package is
  installed.

  Add button (in Printers dialog) does not find (using Find Network
  hotspot) Samsung SCX-4729FD printer printer: it used to do so.

  Similarly, localhost:631/printers (in Firefox) does not find Samsung
  SCX-4729FD printer.

  Printer has static ip address (on my network) of 192.168.1.20

  Ping of printer shows connection is OK:
  john@Desktop:~$ ping 192.168.1.20
  PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
  64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=0.516 ms


  Firewall has port 631 open.

  Using Ubuntu 64 bit desktop fully up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon May 16 14:53:17 2016
  InstallationDate: Installed on 2014-04-25 (752 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Deskjet-2540-series: 
usb://HP/Deskjet%202540%20series?serial=CN51A5721J0604=1
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  PpdFiles: Deskjet-2540-series: HP Deskjet 2540 Series, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic 
root=UUID=0d248ee7-6e51-4cfd-aa7e-f1963792d493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2PV
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFH:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PV:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1582251/+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 1583997] Re: cannot print correctly on HP Deskjet 840C

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  cannot print correctly on HP Deskjet 840C

Status in cups package in Ubuntu:
  Expired

Bug description:
  I have some problems printing with HP Deskjet 840C. At times I can
  print correctly while at times I have problems mainly with pdf files.
  Sometimes they will not be printed at all (the status says "waiting"
  or "cancelled"). Sometimes some pages get printed and the others fail.

  I recently installed HP Tools and while initially I could print fine,
  now it doesn't print at all or it prints ALL pages while I choose a
  range of pages. I installed and reinstalled the printer and the HP
  Tools to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-87.132-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri May 20 12:45:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-02 (868 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  Lpstat: device for HP_DeskJet_840C: hp:/usb/DeskJet_840C?serial=HU0292N111LW
  MachineType: TOSHIBA Satellite A300
  Papersize: a4
  PpdFiles: HP_DeskJet_840C: HP DeskJet 840C - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=0554b137-c865-40cf-a427-1501c7ec954f ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to trusty on 2014-06-24 (695 days ago)
  dmi.bios.date: 04/14/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.70
  dmi.board.name: Satellite A300
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.70:bd04/14/2008:svnTOSHIBA:pnSatelliteA300:pvrPSAJ4E-01U00NGE:rvnTOSHIBA:rnSatelliteA300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:
  dmi.product.name: Satellite A300
  dmi.product.version: PSAJ4E-01U00NGE
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1583997/+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 1799265] Re: avahi-daemon high cpu, unusable networking

2018-10-22 Thread Trent Lloyd

Hi Matt,

Thanks for the report. I'd like to profile avahi using perf to get
information on what functions are being executed. Could you run the
following commands to generate such data?

If you are unsure about any of this feel free to ask.


echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list
sudo apt update
sudo apt install linux-tools-generic ubuntu-dbgsym-keyring 
linux-cloud-tools-generic
sudo apt update
sudo apt install avahi-daemon-dbgsym libavahi-common3-dbgsym 
libavahi-core7-dbgsym libavahi-glib1-dbgsym libc6-dbgsym libcap2-dbgsym 
libdaemon0-dbgsym libdbus-1-3-dbgsym libecore-avahi1-dbgsym libexpat1-dbgsym 
libgcrypt20-dbgsym libgpg-error0-dbgsym liblz4-1-dbgsym liblzma5-dbgsym 
libnss-systemd-dbgsym libsystemd0-dbgsym 

then to record a profile:

sudo perf record -p $(cat /run/avahi-daemon/pid) -g -- sleep 60

This will exit after 60 seconds, then generate perf script output:

sudo perf script > avahi-perf.script.txt
sudo perf report -n --stdio > avahi-perf.report.txt

And then upload the resulting avahi-perf.script.txt and avahi-
perf.report.txt for analysis.


You'll want to make sure avahi is using 100%+ CPU at the time you do this.

Lastly from the same bootup, can you please collect the log info from 
journalctl:
journalctl -u avahi-daemon --no-pager --no-tail > avahi-journal.txt


Thanks for reporting the bug! Hopefully we can figure it out.

In the mean time if you want to disable avahi you can try this:
sudo systemctl disable avahi-daemon.socket avahi-daemon
sudo systemctl stop avahi-daemon.socket avahi-daemon

(to re-enable change to start and enable)

Regards,
Trent

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

Title:
  avahi-daemon high cpu, unusable networking

Status in avahi package in Ubuntu:
  New

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+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 1799265] Re: avahi-daemon high cpu, unusable networking

2018-10-22 Thread Trent Lloyd

Instructions fixed to work with the 80 column limit of comments:

echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse" | \
 sudo tee -a /etc/apt/sources.list.d/ddebs.list
sudo apt update
sudo apt install linux-tools-generic ubuntu-dbgsym-keyring \
 linux-cloud-tools-generic
sudo apt update
sudo apt install avahi-daemon-dbgsym libavahi-common3-dbgsym \
libavahi-core7-dbgsym libavahi-glib1-dbgsym libc6-dbgsym libcap2-dbgsym \
libdaemon0-dbgsym libdbus-1-3-dbgsym libecore-avahi1-dbgsym libexpat1-dbgsym \
libgcrypt20-dbgsym libgpg-error0-dbgsym liblz4-1-dbgsym liblzma5-dbgsym \
libnss-systemd-dbgsym libsystemd0-dbgsym

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

Title:
  avahi-daemon high cpu, unusable networking

Status in avahi package in Ubuntu:
  New

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)

It appears "AudioIPC Server" is actually Firefox. It shows up as such
in:

  Settings > Sound > Applications

when Firefox is playing audio.

So I don't think that's related to this bug at all.

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
Revision: 0x09
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
IRQ: 36 (119384 events)
Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

   But there is no sound output, pavucontrol does not show ANY hardware to 
configure.  I have
  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
in pavucontrol and there is no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.18.0-10-lowlatency x86_64
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Oct 22 04:11:54 2018
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)

If you have the indicator Applet installed there are not one but three 
speaker symbols each doing different things, it shows up under the middle
drop-down menu under Playback Streams.  I'll be honest, I am not familiar with
the internals of Ubuntu's audio system.  Back in the old days when you had
/dev/audio and you wrote to it, or used ioctl calls to change the bit rate or
width, I could grock it, now it's too much of a hack for me to keep track of.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 23 Oct 2018, Daniel van Vugt wrote:

> Date: Tue, 23 Oct 2018 03:30:19 -
> From: Daniel van Vugt 
> Reply-To: Bug 1799203 <1799...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1799203] Re: [Mac-Pro 1,
> 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to
> Ubuntu 18.10)
> 
> I mean; what is "audioIPCServer"? Where are you seeing that?
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799203
>
> Title:
>  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
>  upgrading to Ubuntu 18.10)
>
> Status in pulseaudio package in Ubuntu:
>  Incomplete
>
> Bug description:
>  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
>  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
>  at all.  The kernel seems to detect the hadware okay:
>
>  hwinfo --sound
>  22: PCI 1b.0: 0403 Audio device
>[Created at pci.378]
>Unique ID: u1Nb.8PjrOxLnqG6
>SysFS ID: /devices/pci:00/:00:1b.0
>SysFS BusID: :00:1b.0
>Hardware Class: sound
>Model: "Intel 631xESB/632xESB High Definition Audio Controller"
>Vendor: pci 0x8086 "Intel Corporation"
>Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
>Revision: 0x09
>Driver: "snd_hda_intel"
>Driver Modules: "snd_hda_intel"
>Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
>IRQ: 36 (119384 events)
>Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
>Driver Info #0:
>  Driver Status: snd_hda_intel is active
>  Driver Activation Cmd: "modprobe snd_hda_intel"
>Config Status: cfg=new, avail=yes, need=no, active=unknown
>
>   But there is no sound output, pavucontrol does not show ANY hardware to 
> configure.  I have
>  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
> reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
> in pavucontrol and there is no audio output.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.10
>  Package: pulseaudio 1:12.2-0ubuntu4
>  Uname: Linux 4.18.0-10-lowlatency x86_64
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
> '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
> '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
> 1:
>  CurrentDesktop: MATE
>  Date: Mon Oct 22 04:11:54 2018
>  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  SourcePackage: pulseaudio
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions
>

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device

[Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)

I mean; what is "audioIPCServer"? Where are you seeing that?

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
Revision: 0x09
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
IRQ: 36 (119384 events)
Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

   But there is no sound output, pavucontrol does not show ANY hardware to 
configure.  I have
  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
in pavucontrol and there is no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.18.0-10-lowlatency x86_64
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Oct 22 04:11:54 2018
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

I notice the bug description mentions:

  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1:
No PulseAudio daemon running, or not running as session daemon.

Justin (and anyone else who finds that the 'pulseaudio' process is
missing), please try adding:

  realtime-scheduling = no

to /etc/pulse/daemon.conf and reboot.

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

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)

The in place upgrade did not install audioIPCServer but a fresh install
did.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 23 Oct 2018, Daniel van Vugt wrote:

> Date: Tue, 23 Oct 2018 02:50:28 -
> From: Daniel van Vugt 
> Reply-To: Bug 1799203 <1799...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1799203] Re: [Mac-Pro 1,
> 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to
> Ubuntu 18.10)
> 
> Can you please elaborate on where/how you see audio components missing
> in the upgrade?
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799203
>
> Title:
>  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
>  upgrading to Ubuntu 18.10)
>
> Status in pulseaudio package in Ubuntu:
>  Incomplete
>
> Bug description:
>  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
>  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
>  at all.  The kernel seems to detect the hadware okay:
>
>  hwinfo --sound
>  22: PCI 1b.0: 0403 Audio device
>[Created at pci.378]
>Unique ID: u1Nb.8PjrOxLnqG6
>SysFS ID: /devices/pci:00/:00:1b.0
>SysFS BusID: :00:1b.0
>Hardware Class: sound
>Model: "Intel 631xESB/632xESB High Definition Audio Controller"
>Vendor: pci 0x8086 "Intel Corporation"
>Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
>Revision: 0x09
>Driver: "snd_hda_intel"
>Driver Modules: "snd_hda_intel"
>Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
>IRQ: 36 (119384 events)
>Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
>Driver Info #0:
>  Driver Status: snd_hda_intel is active
>  Driver Activation Cmd: "modprobe snd_hda_intel"
>Config Status: cfg=new, avail=yes, need=no, active=unknown
>
>   But there is no sound output, pavucontrol does not show ANY hardware to 
> configure.  I have
>  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
> reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
> in pavucontrol and there is no audio output.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.10
>  Package: pulseaudio 1:12.2-0ubuntu4
>  Uname: Linux 4.18.0-10-lowlatency x86_64
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
> '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
> '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
> 1:
>  CurrentDesktop: MATE
>  Date: Mon Oct 22 04:11:54 2018
>  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  SourcePackage: pulseaudio
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions
>

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"

[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

2018-10-22 Thread Eric Buist

I ended up running sudo apt purge pulseaudio, which completely removed 
PulseAudio and some configuration files. Then I rebooted and surprise, sound 
was back. However, it wasn't working for Firefox/YouTube, and Spotify. I then 
tried to reinstall PulseAudio, which didn't do anything. But systemctl --user 
start pulseaudio restarted the daemon, and then I have sound. I tried to reboot 
and still have sound.
Not sure if that will remain stable, will have to monitor this.

There are at least two issues: I got removed from the "audio" group
which prevented me from using ALSA devices, then PulseAudio
configuration got screwed up preventing PulseAudio from accessing ALSA
devices.

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)

Can you please elaborate on where/how you see audio components missing
in the upgrade?

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
Revision: 0x09
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
IRQ: 36 (119384 events)
Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

   But there is no sound output, pavucontrol does not show ANY hardware to 
configure.  I have
  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
in pavucontrol and there is no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.18.0-10-lowlatency x86_64
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Oct 22 04:11:54 2018
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not

It obviously would be good to have in place upgrades work properly.
I can see after the re-install there are new components to the audio system
that did not get installed by the upgrade, AudioIPCServer among others. 
However not a huge show stopper since work station is temporarily expendable 
and I do not have sound on servers.  Also, sound via x2go works on servers even 
after in place upgrade.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 23 Oct 2018, Daniel van Vugt wrote:

> Date: Tue, 23 Oct 2018 02:24:16 -
> From: Daniel van Vugt 
> Reply-To: Bug 1799203 <1799...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1799203] Re: [Mac-Pro 1,
> 1] Kernel Detects Sound Chip but PulseAudio does not
> 
> Thanks for figuring that out. It sounds like the problem is now fixed
> for you.
>
> I will now set the bug to Incomplete so it will stay open for 60 days
> but close automatically thereafter if nobody else comments about the
> issue.
>
>
> ** Changed in: pulseaudio (Ubuntu)
>   Status: New => Incomplete
>
> ** Summary changed:
>
> - [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not
> + [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after 
> upgrading to Ubuntu 18.10)
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799203
>
> Title:
>  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
>  upgrading to Ubuntu 18.10)
>
> Status in pulseaudio package in Ubuntu:
>  Incomplete
>
> Bug description:
>  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
>  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
>  at all.  The kernel seems to detect the hadware okay:
>
>  hwinfo --sound
>  22: PCI 1b.0: 0403 Audio device
>[Created at pci.378]
>Unique ID: u1Nb.8PjrOxLnqG6
>SysFS ID: /devices/pci:00/:00:1b.0
>SysFS BusID: :00:1b.0
>Hardware Class: sound
>Model: "Intel 631xESB/632xESB High Definition Audio Controller"
>Vendor: pci 0x8086 "Intel Corporation"
>Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
>Revision: 0x09
>Driver: "snd_hda_intel"
>Driver Modules: "snd_hda_intel"
>Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
>IRQ: 36 (119384 events)
>Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
>Driver Info #0:
>  Driver Status: snd_hda_intel is active
>  Driver Activation Cmd: "modprobe snd_hda_intel"
>Config Status: cfg=new, avail=yes, need=no, active=unknown
>
>   But there is no sound output, pavucontrol does not show ANY hardware to 
> configure.  I have
>  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
> reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
> in pavucontrol and there is no audio output.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.10
>  Package: pulseaudio 1:12.2-0ubuntu4
>  Uname: Linux 4.18.0-10-lowlatency x86_64
>  Architecture: amd64
>  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
> '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
> '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
> 1:
>  CurrentDesktop: MATE
>  Date: Mon Oct 22 04:11:54 2018
>  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  SourcePackage: pulseaudio
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions
>

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status

[Touch-packages] [Bug 1799218] Re: brightness controller missing after installing nvidia-390

It looks like your kernel command line has a custom backlight change,
which is unusual:

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash
acpi_backlight=vendor vt.handoff=1

Maybe try:
  1. Removing the "acpi_backlight=vendor" from /etc/default/grub
  2. sudo update-grub
  3. Reboot


** Summary changed:

- brightness controller missing
+ brightness controller missing after installing nvidia-390

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

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

Title:
  brightness controller missing after installing nvidia-390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  brightness controller gone after installing nvidia drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 18:26:31 2018
  DistUpgraded: 2018-09-13 00:30:24,004 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2018-08-16 (66 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH3AEN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (39 days ago)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH3AEN:pvrC1074QWS:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEH3AEN
  dmi.product.version: C1074QWS
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 17:22:30 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799218/+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 1799228] Re: USB-ports do not work

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  USB-ports do not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Two out of 3 USB-ports are not regognized anymore (i.e. when I insert
  a USB-stick, it will not be shown in Nautilus). I tried various
  workarounds from ubuntuusers, but they were not successful. Among them
  to use "dpkg-reconfigure x-server". X-org now reported an error,
  docuimented in the attachment.

  Earlier I wanted to create an image with Clonezilla and selected a
  USB-stick at port #2 as target, however, the target was not detected
  successfully and the backup-procedure stopped. I suspect that the
  issues may be relatd.

  Kind regards,
  Stefan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 22 15:57:33 2018
  DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() (E:Nicht 
gesperrt)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.4.0-137-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1ccd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a]
  InstallationDate: Installed on 2016-07-21 (823 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash pci=noaer 
acpi_osi= acpi_backlight=native vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  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.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 15:43:15 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799228/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not

Thanks for figuring that out. It sounds like the problem is now fixed
for you.

I will now set the bug to Incomplete so it will stay open for 60 days
but close automatically thereafter if nobody else comments about the
issue.


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

** Summary changed:

- [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not
+ [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after 
upgrading to Ubuntu 18.10)

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after
  upgrading to Ubuntu 18.10)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
Revision: 0x09
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
IRQ: 36 (119384 events)
Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

   But there is no sound output, pavucontrol does not show ANY hardware to 
configure.  I have
  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
in pavucontrol and there is no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.18.0-10-lowlatency x86_64
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Oct 22 04:11:54 2018
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+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 1799232] Re: Thunderbolt displays jump to the right occasionally

Does the problem occur if you log into an "Ubuntu on Wayland" session? I
am wondering if it is specific to Xorg sessions.

** Summary changed:

- my displays jump to the right occasionally
+ Thunderbolt displays jump to the right occasionally

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Thunderbolt displays jump to the right occasionally

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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: Tue Oct 31 11:01:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1799232/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not

On Mon, October 22, 2018 6:51 pm, Daniel van Vugt wrote:
> ** Summary changed:
>
>
> - Kernel Detects Sound Chip but PulseAudio does not
> + [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not
>
>
> ** Tags added: cosmic
>
>
> --
> You received this bug notification because you are subscribed to the bug
> report. https://bugs.launchpad.net/bugs/1799203
>
>
> Title:
> [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not
>
>
> Status in pulseaudio package in Ubuntu:
> New
>
>
> Bug description:
> I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
> 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
> at all.  The kernel seems to detect the hadware okay:
>
> hwinfo --sound 22: PCI 1b.0: 0403 Audio device
> [Created at pci.378]
> Unique ID: u1Nb.8PjrOxLnqG6
> SysFS ID: /devices/pci:00/:00:1b.0
> SysFS BusID: :00:1b.0
> Hardware Class: sound
> Model: "Intel 631xESB/632xESB High Definition Audio Controller"
> Vendor: pci 0x8086 "Intel Corporation"
> Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
> Revision: 0x09
> Driver: "snd_hda_intel"
> Driver Modules: "snd_hda_intel"
> Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
> IRQ: 36 (119384 events)
> Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
> Driver Info #0:
> Driver Status: snd_hda_intel is active
> Driver Activation Cmd: "modprobe snd_hda_intel"
> Config Status: cfg=new, avail=yes, need=no, active=unknown
>
>
> But there is no sound output, pavucontrol does not show ANY hardware to
> configure.  I have purged and reinstalled both pulseaudio and alsa to
> noavail, I"ve force reloaded alsa, I've restarted pulseaudio.  Nothing
> makes the hardware show up in pavucontrol and there is no audio output.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.10
> Package: pulseaudio 1:12.2-0ubuntu4
> Uname: Linux 4.18.0-10-lowlatency x86_64
> Architecture: amd64
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
> '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
> '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit
> code 1: CurrentDesktop: MATE
> Date: Mon Oct 22 04:11:54 2018
> LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
>  SourcePackage: pulseaudio
> dmi.bios.date: 07/02/07
> dmi.bios.vendor: Apple Computer, Inc.
> dmi.bios.version: MP21.88Z.007F.B06.0707021348
> dmi.board.asset.tag: Base Board Asset Tag#
> dmi.board.name: Mac-F4208DC8
> dmi.board.vendor: Apple Inc.
> dmi.board.version: PVT
> dmi.chassis.asset.tag: Asset Tag#
> dmi.chassis.type: 2
> dmi.chassis.vendor: Apple Computer, Inc.
> dmi.chassis.version: Mac-F4208DC8
> dmi.modalias:
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnA
> ppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:c
> vnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
> dmi.product.family: MacPro
> dmi.product.name: MacPro2,1
> dmi.product.sku: System SKU#
> dmi.product.version: 1.0
> dmi.sys.vendor: Apple Computer, Inc.
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscri
> ptions
>

 This problem only occurs with an in-place upgrade.  I did a fresh
install and audio is working again.

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
Revision: 0x09
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
IRQ: 36 (119384 events)
Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

   But there is no sound output, pavucontrol does not show ANY hardware to 
configure.  I have
  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
reloaded alsa, I've restarted pulseaudio.  Nothing makes

[Touch-packages] [Bug 1799280] Re: Low graphics mode with ubuntu 18.04

Your low graphics mode is because the system is stuck in recovery mode
with the 'nomodeset' kernel option:

[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset

To fix this, please reboot and tap Escape immediately as soon as you see
the first purple screen. Now navigate the menus and find the default
kernel option that is not recovery mode.

When done, please confirm the correct change has been made by running:

  cat /proc/cmdline

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Low graphics mode with ubuntu 18.04

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have problem login since update to 18.04 last week.
  I tried to boot to recovery mode but got a message with low graphics mode.
  I tried to install intel driver again but I have the latest version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 20:19:27 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
 Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
  InstallationDate: Installed on 2017-04-23 (547 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. OptiPlex GX620
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0F8098
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/20/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 19:20:47 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL DELL USB Keyboard KEYBOARD, id 8
   inputMicrosoft Express Mouse MOUSE, id 9
   inputMicrosoft Express Mouse KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1799280/+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 1799283] Re: Macbook Air keyboard backlighting does not work on Ubuntu 18.10

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

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


** Package changed: xorg (Ubuntu) => upower (Ubuntu)

** This bug has been marked a duplicate of bug 1796550
   [regression] Keyboard brightness control keys (down/up) don't work in cosmic 
(upower 0.99.8)

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

Title:
  Macbook Air keyboard backlighting does not work on Ubuntu 18.10

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Tested on a fresh installation of Ubuntu 18.10 and also on Ubuntu
  18.10 Live.

  The keyboard backlighting works fine on Ubuntu 18.04 and MacOS . Also
  tested `xset led 1` for 1 to 32 command and it does not work as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 22:41:33 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011b]
  InstallationDate: Installed on 2018-10-20 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Apple Inc. MacBookAir6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=89e36b21-5540-440c-a145-16be978fa6ba ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0103.B00.1708080653
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0103.B00.1708080653:bd08/08/2017:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1799283/+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 1799327] Re: screen display

The radeon graphics driver is unable to work properly, probably because
you are stuck in recovery mode where kernel mode setting has been
disabled:

  [68.968] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=010804b7-21f1-4e4e-a968-18ae8286fbf2 ro recovery nomodeset

To fix this, please reboot and tap Escape immediately as soon as you see
the first purple screen. Now navigate the menus and find the default
kernel option that is not recovery mode.

When done, please confirm the correct change has been made by running:

  cat /proc/cmdline

** Tags added: radeon

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  screen display

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  my home and login screen looks like i had taken LSD vivid distorted
  colours. and just solid color on normal start-up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 22 18:54:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  InstallationDate: Installed on 2016-02-13 (982 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: LENOVO 200763U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=010804b7-21f1-4e4e-a968-18ae8286fbf2 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE6WW (2.26 )
  dmi.board.name: 200763U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn200763U:pvrThinkPadT60:rvnLENOVO:rn200763U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 200763U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 17:23:51 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1799327/+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 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not

** Summary changed:

- Kernel Detects Sound Chip but PulseAudio does not
+ [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not

** Tags added: cosmic

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

Title:
  [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a 2006 vintage Mac-Pro 1,1.  The audio has worked fine from
  12.04 through 18.04, but upon upgrade to 18.10 it no longer functions
  at all.  The kernel seems to detect the hadware okay:

  hwinfo --sound
  22: PCI 1b.0: 0403 Audio device 
[Created at pci.378]
Unique ID: u1Nb.8PjrOxLnqG6
SysFS ID: /devices/pci:00/:00:1b.0
SysFS BusID: :00:1b.0
Hardware Class: sound
Model: "Intel 631xESB/632xESB High Definition Audio Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller"
Revision: 0x09
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable)
IRQ: 36 (119384 events)
Module Alias: "pci:v8086d269Asvsdbc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown

   But there is no sound output, pavucontrol does not show ANY hardware to 
configure.  I have
  purged and reinstalled both pulseaudio and alsa to noavail, I"ve force 
reloaded alsa, I've restarted pulseaudio.  Nothing makes the hardware show up 
in pavucontrol and there is no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.18.0-10-lowlatency x86_64
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Oct 22 04:11:54 2018
  LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+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 1798712] Re: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

** Tags added: system76

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

Title:
  [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Incomplete
Status in rtkit package in Ubuntu:
  Incomplete

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

Tessa,

Thanks. Can you please also attach a full system log from the machine by
running this?

  journalctl -b > journal.txt

and attach it here.

Everyone else, please log your own new bug by running:

  ubuntu-bug pulseaudio


** Summary changed:

- no sound after 18.10 upgrade
+ [System76 Oryx Pro] no sound after 18.10 upgrade

** Tags added: system76

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

2018-10-22 Thread Eric Buist

If that can be of any help, here is my ALSA information. http://www
.alsa-project.org/db/?f=d957084a5503ca9a9c61d3b695f84ea6595f4a3d

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]

2018-10-22 Thread Eric Buist

I'm on this for more than two hours. Everything I try just fails, and
every search I attempt results into outdated or non-working tips. I was
able to get sound by adding myself to the audio group; now speaker-test
-D sysdefault:CARD=PCH works, but PulseAudio stubbornly does not detect
my device. Tried to delete ~/.config/pulse, tried to restart PulseAudio,
attempted to get verbose logging, no useful information. pactl list and
pavucontrol only show a NVIDIA HDMI audio, and a USB webcam, no onboard
HDA Intel. Do I really need to get an external USB sound card for Ubuntu
18.10? This is a real deal breaker. We need a downgrade path if upgrade
fails the system that hard, but there is no such thing, besides
formatting and loosing all my settings.

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360/9370]

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1798712] Re: [System76 Oryx Pro] No sound (18.10 Cosmic)

Thanks!

It appears PulseAudio is repeatedly failing to start and timing out
because rtkit-daemon.service is failing to start. And rtkit-
daemon.service is failing to start for some reason related to "Bad
address" errors occurring on lots of mount operations.

As a workaround, you can tell pulseaudio to avoid using realtime
scheduling by adding:

  realtime-scheduling = no

to /etc/pulse/daemon.conf. Hopefully that will fix pulseaudio but it
won't address the root cause. I think your root cause might be related
to an impending disk hardware failure, or filesystem corruption.

To check for disk hardware failure run app "Disks" and click ≡ then
"SMART Data & Self Tests...".

Also, please try live booting Ubuntu from USB and see if that avoids the
bug.

** Also affects: rtkit (Ubuntu)
   Importance: Undecided
   Status: New

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

** Summary changed:

- [System76 Oryx Pro] No sound (18.10 Cosmic)
+ [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

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

Title:
  [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Incomplete
Status in rtkit package in Ubuntu:
  Incomplete

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1799327] [NEW] screen display

2018-10-22 Thread Sam Salado

Public bug reported:

my home and login screen looks like i had taken LSD vivid distorted
colours. and just solid color on normal start-up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct 22 18:54:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
InstallationDate: Installed on 2016-02-13 (982 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: LENOVO 200763U
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=010804b7-21f1-4e4e-a968-18ae8286fbf2 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE6WW (2.26 )
dmi.board.name: 200763U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn200763U:pvrThinkPadT60:rvnLENOVO:rn200763U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 200763U
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 17:23:51 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  screen display

Status in xorg package in Ubuntu:
  New

Bug description:
  my home and login screen looks like i had taken LSD vivid distorted
  colours. and just solid color on normal start-up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 22 18:54:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  InstallationDate: Installed on 2016-02-13 (982 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: LENOVO 200763U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=010804b7-21f1-4e4e-a968-18ae8286fbf2 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE6WW (2.26 )
  dmi.board.name: 200763U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn200763U:pvrThinkPadT60:rvnLENOVO:rn200763U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 200763U

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

2018-10-22 Thread Bryan Quigley

Can this bug make the complete failure of DNS (like
https://github.com/systemd/systemd/issues/6490) more likely?

If SERVFAIL is for the DNS server, that sounds like this would cause
more failures of DNS per the other issue.

** Tags added: sts

** Bug watch added: github.com/systemd/systemd/issues #6490
   https://github.com/systemd/systemd/issues/6490

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  New

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+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 1798884] Re: Upgrade or install fails 1:7.2p2-4ubuntu2.5

2018-10-22 Thread Andreas Hasenack

Thanks for filing this bug in Ubuntu.

The 1:7.2p2-4ubuntu2.5 openssh update introduced a check in the systemd
service file to prevent the daemon from stopping if there is a
configuration syntax error (bug #1771340). This is done by calling
"/usr/sbin/sshd -t".

It looks like this call worked, from the information you provided:

  Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited,
status=0/SUCCESS)

The real failure must have come after.

Could you please attach more logs? You can inspect /var/log/syslog for
sshd messages, same for /var/log/auth, or just run:

sudo apport-collect -p openssh 1798884

to attach a default set of logs to this bug.


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

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

Title:
  Upgrade or install fails 1:7.2p2-4ubuntu2.5

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Today I've got an update to openssh-server version 1:7.2p2-4ubuntu2.5
  but installation fails. Also when I purge the package and install it
  again, I get the same error message:

  openssh-server (1:7.2p2-4ubuntu2.5) wird eingerichtet ...
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  Job for ssh.service failed because the control process exited with error 
code. See "systemctl status ssh.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Fr 2018-10-19 20:53:49 CEST; 12ms 
ago
Process: 29682 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
   Main PID: 29682 (code=exited, status=255)

  Okt 19 20:53:48 zulu1451.server4you.de systemd[1]: Starting OpenBSD Secure 
Shell server...
  Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Main process 
exited, code=code=exited, status=255/n/a
  Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: Failed to start OpenBSD 
Secure Shell server.
  Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Unit entered 
failed state.
  Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Failed with 
result 'exit-code'.
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück
  dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ssh:
   ssh hängt ab von openssh-server (>= 1:7.2p2-4ubuntu2.5); aber:
Paket openssh-server ist noch nicht konfiguriert.

  dpkg: Fehler beim Bearbeiten des Paketes ssh (--configure):
   Abhängigkeitsprobleme - verbleibt unkonfiguriert
  Fehler traten auf beim Bearbeiten von:
   openssh-server
   ssh

  
  The system is:
  Description:Ubuntu 16.04.5 LTS
  Release:16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1798884/+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 1670959] Re: systemd-resolved using 100% CPU

2018-10-22 Thread Andreas Hasenack

There is some configuration that leads to a loop between these two
resolvers, and that is what causes the cpu usage. If we could get a step
by step way to reproduce it, it could probably be addressed.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-10-22 Thread Melvin1981

Texted to NVidia support about the issue. Got reply

Your case is being escalated to our Level 2 Tech Support group. The
Level 2 agents will review the case notes and may attempt to recreate
your issue or find a workaround solution if possible. As this process
may take some time we ask that you be patient and a Level 2 tech will
contact you as soon they can to help resolve your issue.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1798839] Re: Canonical Livepatch doesn't appear in "Updates" tab.

2018-10-22 Thread Matthew Paul Thomas

I’ve reported bug 1799310 about warning you when an upgrade will result
in Livepatch no longer being available.

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

Title:
  Canonical Livepatch doesn't appear in "Updates" tab.

Status in software-properties package in Ubuntu:
  New

Bug description:
  Livepatch was working and appearing fine in 'Software & Updates' until
  after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch
  does not appear as an option anymore after upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-gtk 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:04:03 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1798839/+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 1798712] Re: [System76 Oryx Pro] No sound (18.10 Cosmic)

2018-10-22 Thread Dylan M Corrales

Sorry, wrong pastebin link.
Here's the correct one: https://pastebin.com/NL6UCN49

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

Title:
  [System76 Oryx Pro] No sound (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1798712] Re: [System76 Oryx Pro] No sound (18.10 Cosmic)

2018-10-22 Thread Dylan M Corrales

Running pulseaudio with `-` outputs this:
https://pastebin.com/2fbrzwzb

Here's a small explanation of pauses:

[line 1] pulseaudio -
[some output]
[line 5] Failed to acquire high-priority scheduling: Input/output errorI: 
[pulseaudio] core-util.c: Failed to acquire high-priority scheduling: 
Input/output error

[long pause]

[line 6] I: [pulseaudio] main.c: This is PulseAudio 12.2
[some output]
[line 2003] D: [pulseaudio] alsa-sink.c: Calculated software volume: 
front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB 
(accurate-enough=yes)

[long pause]

[line 2004] I: [alsa-sink-ALC892 Analog] core-util.c: Failed to acquire
real-time scheduling: Input/output error


So looking at the output, both 5 minutes pauses are followed by "Failed to 
acquire real-time scheduling: Input/output error"

Hope this helps a bit!

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

Title:
  [System76 Oryx Pro] No sound (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

  I tried killing the currently running pulseaudio daemon, then starting it 
with `-`, here's what happens:
  `~$ pulseaudio -
  I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation 
not permitted
  I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation 
not permitted
  D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.`
  Although this appears in the terminal, there's still no sound in the settings 
menu, or in pavucontrol.

  alsamixer runs just fine, showing that alsa is working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1799038] Re: Ubuntu 18.10 does not suspend on lid close

2018-10-22 Thread MZ

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

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

Title:
  Ubuntu 18.10 does not suspend on lid close

Status in systemd package in Ubuntu:
  New

Bug description:
  After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid
  on notebooks does not work any more.

  The machine goes to suspend mode but wakes up immediately due to some
  events (can be network, or others).

  In 18.04 this issue was fixed (we had the same situation with any
  version since 14.04).

  Seems a regression.

  Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. 
The changes do NOTHING.
  One might spare the time to experiment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 11:55:48 2018
  InstallationDate: Installed on 2018-04-30 (174 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 1799038] Re: Ubuntu 18.10 does not suspend on lid close

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

Title:
  Ubuntu 18.10 does not suspend on lid close

Status in systemd package in Ubuntu:
  New

Bug description:
  After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid
  on notebooks does not work any more.

  The machine goes to suspend mode but wakes up immediately due to some
  events (can be network, or others).

  In 18.04 this issue was fixed (we had the same situation with any
  version since 14.04).

  Seems a regression.

  Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. 
The changes do NOTHING.
  One might spare the time to experiment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 11:55:48 2018
  InstallationDate: Installed on 2018-04-30 (174 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 1799283] [NEW] Macbook Air keyboard backlighting does not work on Ubuntu 18.10

2018-10-22 Thread Mos

Public bug reported:

Tested on a fresh installation of Ubuntu 18.10 and also on Ubuntu 18.10
Live.

The keyboard backlighting works fine on Ubuntu 18.04 and MacOS . Also
tested `xset led 1` for 1 to 32 command and it does not work as well.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 22:41:33 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b]
InstallationDate: Installed on 2018-10-20 (2 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Apple Inc. MacBookAir6,2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=89e36b21-5540-440c-a145-16be978fa6ba ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0103.B00.1708080653
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0103.B00.1708080653:bd08/08/2017:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir6,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

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

Title:
  Macbook Air keyboard backlighting does not work on Ubuntu 18.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Tested on a fresh installation of Ubuntu 18.10 and also on Ubuntu
  18.10 Live.

  The keyboard backlighting works fine on Ubuntu 18.04 and MacOS . Also
  tested `xset led 1` for 1 to 32 command and it does not work as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 22:41:33 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011b]
  InstallationDate: Installed on 2018-10-20 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Apple Inc. MacBookAir6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=89e36b21-5540-440c-a145-16be978fa6ba ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0103.B00.1708080653
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias:

[Touch-packages] [Bug 1799287] [NEW] usbmud service will not load on boot

2018-10-22 Thread Herminio

Public bug reported:

I use usbmux for my iphone so I can access my photos via shotwell and
move files around. I have to start the service manually via systemd.
When I try to enable I get the following.

hhernandez@hhernandez-Precision-M4800:~$ sudo systemctl enable usbmuxd
[sudo] password for hhernandez: 
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: usbmuxd 1.1.0-2build1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Oct 22 13:04:24 2018
SourcePackage: usbmuxd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  usbmud service will not load on boot

Status in usbmuxd package in Ubuntu:
  New

Bug description:
  I use usbmux for my iphone so I can access my photos via shotwell and
  move files around. I have to start the service manually via systemd.
  When I try to enable I get the following.

  hhernandez@hhernandez-Precision-M4800:~$ sudo systemctl enable usbmuxd
  [sudo] password for hhernandez: 
  The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
  settings in the [Install] section, and DefaultInstance for template units).
  This means they are not meant to be enabled using systemctl.
  Possible reasons for having this kind of units are:
  1) A unit may be statically enabled by being symlinked from another unit's
 .wants/ or .requires/ directory.
  2) A unit's purpose may be to act as a helper for some other unit which has
 a requirement dependency on it.
  3) A unit may be started when needed via activation (socket, path, timer,
 D-Bus, udev, scripted systemctl call, ...).
  4) In case of template units, the unit is meant to be enabled with some
 instance name specified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: usbmuxd 1.1.0-2build1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Oct 22 13:04:24 2018
  SourcePackage: usbmuxd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1799287/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.

2018-10-22 Thread David Coronel

I tested friendly-recovery 0.2.31ubuntu2 in Xenial/16.04.3 LTS.

Selecting network Enable networking" from the Recovery Menu now enables
the network and DNS successfully. I can "cat /etc/resolv.conf" vs before
I couldn't. I don't see any issues with dependencies or asking for tty-
ask-password or anything that was reported previously.

Selecting "resume Resume normal boot" works good as well to return to
the normal OS.


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Invalid
Status in systemd source package in DD-Series:
  Won't Fix

Bug description:
  [Impact]

   * network menu in recovery mode doesn't work correctly, blocking at
  starting systemd services depends to enable networking.

  [Test Case]

   * Boot w/ Xenial or Bionic in recovery mode via grub
   * Choose "network" in friendly-recovery menu

   The network won't be activated and it'll be stuck at systemd-tty-ask-
  password :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask

  [Regression Potential]

  * Low.
  * All options works fine.
  * Cosmic has the same changes already in place.

  * According to xnox, resume option fails to boot now.
  After verification the 'resume' has the same effect before/after that change, 
it boots up but still seems to stick in 'recovery' option according to 
/proc/cmdline so I don't see any obvious behaviour change before and after.

  [Other Info]

   * Upstream :
  
https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161
  Revision  154 to 161

  [Original Description]

  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1799283] Re: Macbook Air keyboard backlighting does not work on Ubuntu 18.10

2018-10-22 Thread Cristian Aravena Romero

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

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

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

Title:
  Macbook Air keyboard backlighting does not work on Ubuntu 18.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Tested on a fresh installation of Ubuntu 18.10 and also on Ubuntu
  18.10 Live.

  The keyboard backlighting works fine on Ubuntu 18.04 and MacOS . Also
  tested `xset led 1` for 1 to 32 command and it does not work as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 22:41:33 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011b]
  InstallationDate: Installed on 2018-10-20 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Apple Inc. MacBookAir6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=89e36b21-5540-440c-a145-16be978fa6ba ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0103.B00.1708080653
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0103.B00.1708080653:bd08/08/2017:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799283/+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 1325614] Re: Cannot unlock screen in KDE

2018-10-22 Thread Henry Waldschmidt

I am running Kubuntu 18.04 on a Dell Precision 5810 with a NVIDIA Quadro
K4200 graphics card.  The driver is NVIDIA 390.77.  I have two Dell 27"
U2713 monitors with display port cables.

If the screen is locked for a long time, i.e. when I leave work for the
day, but not during lunch, the keyboard no longer responds.  The mouse
cursor is still moving but does not seem to interact with the screen.
If I use ssh to kill the session with loginctl, everything starts
working again.

I will try unplugging the second monitor tonight to see if that makes a
difference with the issue.

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

Title:
  Cannot unlock screen in KDE

Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  System Info:
  Description:Ubuntu 14.04 LTS
  Release:14.04

  Hardware: Lenovo THingpand T430 connected to an external Dell montior;
  using onboard Intel 4000 HD

  Configuration: widget-enabled screen locker, desktop effects (OpenGL
  3.1).

  Expected:
  When screen locks (either through time-out or user request), clicking on the 
cashew in the top right should permit unlock.

  What happens:
  Nothing - it is not possible to unlock the screen.

  Viable workaround:
  None. It might be that using "xrandr" for effects doesn't cause the issue, 
but I haven't had time to fully test.
  The only option is to force a shutdown and then start, losing all data in 
open applications.
  Reboot does not seem to work correctly when the screen can't be unlocked, 
hangs with black screen when it should show log-in screen.

  I am more than happy to run any required tests or pull required logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1325614/+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 1325614] Re: Cannot unlock screen in KDE

2018-10-22 Thread Henry Waldschmidt

** Also affects: sddm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Cannot unlock screen in KDE

Status in lightdm package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  System Info:
  Description:Ubuntu 14.04 LTS
  Release:14.04

  Hardware: Lenovo THingpand T430 connected to an external Dell montior;
  using onboard Intel 4000 HD

  Configuration: widget-enabled screen locker, desktop effects (OpenGL
  3.1).

  Expected:
  When screen locks (either through time-out or user request), clicking on the 
cashew in the top right should permit unlock.

  What happens:
  Nothing - it is not possible to unlock the screen.

  Viable workaround:
  None. It might be that using "xrandr" for effects doesn't cause the issue, 
but I haven't had time to fully test.
  The only option is to force a shutdown and then start, losing all data in 
open applications.
  Reboot does not seem to work correctly when the screen can't be unlocked, 
hangs with black screen when it should show log-in screen.

  I am more than happy to run any required tests or pull required logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1325614/+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 1799279] Re: kernel update hangs inside update-secureboot-policy

2018-10-22 Thread Jonathan Kamens

Sorry, I misspoke above. I'm on 18.04, not 18.10. I've updated the
comment above to indicate this.

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

Title:
  kernel update hangs inside update-secureboot-policy

Status in apt package in Ubuntu:
  New

Bug description:
  I just ran `apt-get --auto-remove dist-upgrade` on 18.04.

  It is hung on update-secureboot-policy waiting for confirmation from
  whiptail.

  apt-get --auto-remove dist-upgrade
  |
  -/usr/bin/dpkg --status-fd 80 --configure --pending
   |
   -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst 
configure
    |
    -run-parts --report --exit-on-error --arg=4.15.0-38-generic 
/etc/kernel/header_postinst.d
     |
     -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic
  |
  -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
   |
   -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
    |
    -/usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
     |
     -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key
     -whiptail --backtitle Package configuration --title Configuring Secure 
Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot 
enabled.  UEFI Secure Boot requires additional configuration to work with  
third-party drivers.  The system will assist you in configuring UEFI Secure 
Boot. To permit  the use of third-party drivers, a new Machine-Owner Key (MOK) 
has been  generated. This key now needs to be enrolled in your system's 
firmware.  To ensure that this change is being made by you as an authorized 
user,  and not by an attacker, you must choose a password now and then confirm  
the change after reboot using the same password, in both the "Enroll  MOK" and 
"Change Secure Boot state" menus that will be presented to you  when this 
system reboots.  If you proceed but do not confirm the password upon reboot, 
Ubuntu will  still be able to boot on your system but any hardware that 
requires  third-party drivers to work correctly may not be usable. --scrolltext 
20 77

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:15:56 2018
  InstallationDate: Installed on 2018-09-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+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 1799280] [NEW] Low graphics mode with ubuntu 18.04

2018-10-22 Thread Sherif Saleh

Public bug reported:

I have problem login since update to 18.04 last week.
I tried to boot to recovery mode but got a message with low graphics mode.
I tried to install intel driver again but I have the latest version.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 20:19:27 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
   Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
InstallationDate: Installed on 2017-04-23 (547 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. OptiPlex GX620
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0F8098
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/20/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex GX620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 19:20:47 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDELL DELL USB Keyboard KEYBOARD, id 8
 inputMicrosoft Express Mouse MOUSE, id 9
 inputMicrosoft Express Mouse KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Low graphics mode with ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I have problem login since update to 18.04 last week.
  I tried to boot to recovery mode but got a message with low graphics mode.
  I tried to install intel driver again but I have the latest version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 20:19:27 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
 Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
  InstallationDate: Installed on 2017-04-23 (547 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. OptiPlex GX620
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0F8098
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/20/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri:

[Touch-packages] [Bug 1799279] Re: kernel update hangs inside update-secureboot-policy

2018-10-22 Thread Jonathan Kamens

Note that I got out of this by killing the update-secureboot-policy and
whiptail processes, and I did not get an error message from dpkg or dkms
after doing that, so the fact that the update-secureboot-policy and
whiptail commands exited with non-zero statuses was not detected.

Note also that I ran the update over an SSH session. When I ran `sudo
/usr/sbin/update-secureboot-policy --enroll-key` manually in a gnome-
terminal window directly on the host, it succeeded.

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

Title:
  kernel update hangs inside update-secureboot-policy

Status in apt package in Ubuntu:
  New

Bug description:
  I just ran `apt-get --auto-remove dist-upgrade` on 18.04.

  It is hung on update-secureboot-policy waiting for confirmation from
  whiptail.

  apt-get --auto-remove dist-upgrade
  |
  -/usr/bin/dpkg --status-fd 80 --configure --pending
   |
   -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst 
configure
    |
    -run-parts --report --exit-on-error --arg=4.15.0-38-generic 
/etc/kernel/header_postinst.d
     |
     -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic
  |
  -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
   |
   -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
    |
    -/usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
     |
     -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key
     -whiptail --backtitle Package configuration --title Configuring Secure 
Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot 
enabled.  UEFI Secure Boot requires additional configuration to work with  
third-party drivers.  The system will assist you in configuring UEFI Secure 
Boot. To permit  the use of third-party drivers, a new Machine-Owner Key (MOK) 
has been  generated. This key now needs to be enrolled in your system's 
firmware.  To ensure that this change is being made by you as an authorized 
user,  and not by an attacker, you must choose a password now and then confirm  
the change after reboot using the same password, in both the "Enroll  MOK" and 
"Change Secure Boot state" menus that will be presented to you  when this 
system reboots.  If you proceed but do not confirm the password upon reboot, 
Ubuntu will  still be able to boot on your system but any hardware that 
requires  third-party drivers to work correctly may not be usable. --scrolltext 
20 77

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:15:56 2018
  InstallationDate: Installed on 2018-09-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+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 1799279] [NEW] kernel update hangs inside update-secureboot-policy

2018-10-22 Thread Jonathan Kamens

Public bug reported:

I just ran `apt-get --auto-remove dist-upgrade` on 18.04.

It is hung on update-secureboot-policy waiting for confirmation from
whiptail.

apt-get --auto-remove dist-upgrade
|
-/usr/bin/dpkg --status-fd 80 --configure --pending
 |
 -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst configure
  |
  -run-parts --report --exit-on-error --arg=4.15.0-38-generic 
/etc/kernel/header_postinst.d
   |
   -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic
|
-/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
 |
 -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
  |
  -/usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
   |
   -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key
   -whiptail --backtitle Package configuration --title Configuring Secure 
Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot 
enabled.  UEFI Secure Boot requires additional configuration to work with  
third-party drivers.  The system will assist you in configuring UEFI Secure 
Boot. To permit  the use of third-party drivers, a new Machine-Owner Key (MOK) 
has been  generated. This key now needs to be enrolled in your system's 
firmware.  To ensure that this change is being made by you as an authorized 
user,  and not by an attacker, you must choose a password now and then confirm  
the change after reboot using the same password, in both the "Enroll  MOK" and 
"Change Secure Boot state" menus that will be presented to you  when this 
system reboots.  If you proceed but do not confirm the password upon reboot, 
Ubuntu will  still be able to boot on your system but any hardware that 
requires  third-party drivers to work correctly may not be usable. --scrolltext 
20 77

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.3ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 15:15:56 2018
InstallationDate: Installed on 2018-09-27 (25 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

- I just ran `apt-get --auto-remove dist-upgrade` on 18.10.
+ I just ran `apt-get --auto-remove dist-upgrade` on 18.04.
  
  It is hung on update-secureboot-policy waiting for confirmation from
  whiptail.
  
  apt-get --auto-remove dist-upgrade
  |
  -/usr/bin/dpkg --status-fd 80 --configure --pending
-  |
-  -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst 
configure
-   |
-   -run-parts --report --exit-on-error --arg=4.15.0-38-generic 
/etc/kernel/header_postinst.d
-|
--/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic
- |
- -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
-  |
-  -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
-   |
-   -/usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
-|
--/bin/sh /usr/sbin/update-secureboot-policy --enroll-key
--whiptail --backtitle Package configuration --title Configuring Secure 
Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot 
enabled.  UEFI Secure Boot requires additional configuration to work with  
third-party drivers.  The system will assist you in configuring UEFI Secure 
Boot. To permit  the use of third-party drivers, a new Machine-Owner Key (MOK) 
has been  generated. This key now needs to be enrolled in your system's 
firmware.  To ensure that this change is being made by you as an authorized 
user,  and not by an attacker, you must choose a password now and then confirm  
the change after reboot using the same password, in both the "Enroll  MOK" and 
"Change Secure Boot state" menus that will be presented to you  when this 
system reboots.  If you proceed but do not confirm the password upon reboot, 
Ubuntu will  still be able to boot on your system but any hardware that 
requires  third-party drivers to work correctly may not be usable. --scrolltext 
20 77
+  |
+  -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst 
configure
+   |
+   -run-parts --report --exit-on-error --arg=4.15.0-38-generic 
/etc/kernel/header_postinst.d
+    |
+    -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic
+ |
+ -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
+  |
+  -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
+   |
+   -/usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
+    |
+

[Touch-packages] [Bug 1715319] Re: [IPV6] DHCP client gets 128 subnet mask instead of any other that defined

2018-10-22 Thread Zeta

** Changed in: isc-dhcp (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [IPV6] DHCP client gets 128 subnet mask instead of any other that
  defined

Status in isc-dhcp package in Ubuntu:
  Invalid

Bug description:
  After configuring DHCP server (with and without RADVD), the client
  gets ipv6 address in range that was defined, or preserved. But the
  subnetmask of the address is 128 no matter what was the definition.

  Steps to reproduce

  1.Install packages:
  #apt-get install -y *dhcp*
  #apt-get install radvd

  2.Define DHCP and RADVD files:

  #vim /etc/dhcp/dhcpd6.conf
  authoritative;
  default-lease-time 600;
  max-lease-time 7200;
  log-facility local7;
  subnet6 ::/64 {
  option dhcp6.name-servers ::;
  range6 ::1 ::100;
  }

  #vim /etc/radvd.conf
  interface enp5s0f0
  {
  AdvSendAdvert on;
  MinRtrAdvInterval 3;
  MaxRtrAdvInterval 10;
  prefix ::/64 {
  AdvOnLink on;
  AdvAutonomous on;
  AdvRouterAddr on;
  };
  };

  
  3.
  # sysctl net.ipv6.conf.ens3.forwarding
  net.ipv6.conf.ens3.forwarding = 1

  4.Create empty server data base file and bring up DHCP server:
  #echo "" >  /tmp/dhcp6.lease
  # dhcpd -6 -cf /etc/dhcp/dhcpd6.conf -lf /tmp/dhcpd6.leases enp5s0f0

  5.Define client interface in /etc/network/interfaces file:
  #vim  /etc/network/interfaces
  auto enp6s0f0
  iface enp6s0f0 inet6 dhcp

  6.Start client and check the ip:
  #ifdown 
  #ifup
  #ifconfig enp6s0f0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1715319/+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 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails

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

Title:
  fstrim -av tries to trim read only mounted ntfs-3g and fails

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  If I run sudo fstrim -av I see:
  /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed
  fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor
  /: 26.9 GiB (28823887872 bytes) trimmed

  /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is 
read-only mounted NTFS, also via ntfs-3g. Lines from fstab:
  UUID=censored /media/SSD_Data ntfs-3g 
rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec
 0 0
  UUID=censored /media/Win7 ntfs-3g 
ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files
 0 0

  If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7
  then sudo fstrim -av takes longer and succeeds for all filesystems.
  So, it seems the read only is the problem.

  This seems cosmetic, but it causes periodic runs of fstrim via systemd
  to report failures.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: util-linux 2.32-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 13 15:25:41 2018
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+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 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails

2018-10-22 Thread Ivan Larionov

I see the same warnings in systemd log.

systemd[1]: fstrim.service: Main process exited, code=exited, status=64/USAGE
systemd[1]: fstrim.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Discard unused blocks.

If I run it manually:

$ sudo fstrim -av
/home: 9.7 GiB (10445021184 bytes) trimmed
fstrim: /mnt/win_c: FITRIM ioctl failed: Bad file descriptor
fstrim: /mnt/win_d: FITRIM ioctl failed: Bad file descriptor
fstrim: /mnt/win_g: FITRIM ioctl failed: Bad file descriptor
fstrim: /mnt/win_e: FITRIM ioctl failed: Bad file descriptor
fstrim: /mnt/win_f: FITRIM ioctl failed: Bad file descriptor
fstrim: /mnt/win_re: FITRIM ioctl failed: Bad file descriptor
/: 2.4 GiB (2608013312 bytes) trimmed

with exit status 64.

Related mount points:

$ mount | grep win
/dev/sda4 on /mnt/win_re type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdc1 on /mnt/win_f type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdb1 on /mnt/win_e type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdd1 on /mnt/win_g type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sda5 on /mnt/win_d type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sda3 on /mnt/win_c type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sde1 on /mnt/win_h type fuseblk 
(ro,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)

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

Title:
  fstrim -av tries to trim read only mounted ntfs-3g and fails

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  If I run sudo fstrim -av I see:
  /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed
  fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor
  /: 26.9 GiB (28823887872 bytes) trimmed

  /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is 
read-only mounted NTFS, also via ntfs-3g. Lines from fstab:
  UUID=censored /media/SSD_Data ntfs-3g 
rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec
 0 0
  UUID=censored /media/Win7 ntfs-3g 
ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files
 0 0

  If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7
  then sudo fstrim -av takes longer and succeeds for all filesystems.
  So, it seems the read only is the problem.

  This seems cosmetic, but it causes periodic runs of fstrim via systemd
  to report failures.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: util-linux 2.32-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 13 15:25:41 2018
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago)

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

apport information

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

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

apport information

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

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799007] Re: no sound after 18.10 upgrade

```
tessa@viper:~$ fuser -v /dev/snd/pcmC*
 USERPID ACCESS COMMAND
/dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
/dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
tessa@viper:~$ pacmd list
Daemon not responding.
```

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

apport information

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

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

apport information

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

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

apport information

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

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799007] Re: no sound after 18.10 upgrade

@lissyx: so you're probably just experiencing #1797714. can you give the
exact fuser command you ran and the output you saw though, so others can
repeat that test on this bug?

** Tags added: apport-collected third-party-packages

** Description changed:

  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even the
  builtin HDMI which usually always shows.
  
- Not sure what happened, but this is a major regression and needs to be
- fixed. Note that this isn't the same as the bug with Timidity taking
- exclusive soundcard access
- (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I
- don't have any timidity packages installed.
+ Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  tessa 11703 F pulseaudio
+  /dev/snd/controlC0:  tessa 11703 F pulseaudio
+  /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
+ CurrentDesktop: pop:GNOME
+ DistroRelease: Pop!_OS 18.10
+ InstallationDate: Installed on 2018-03-05 (230 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
+ Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
+ Tags: third-party-packages cosmic
+ Uname: Linux 4.18.0-10-generic x86_64
+ UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
+ UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
+ UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/20/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.05.02dRSA2
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: Oryx Pro
+ dmi.board.vendor: System76
+ dmi.board.version: oryp3-ess
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: System76
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
+ dmi.product.family: Not Applicable
+ dmi.product.name: Oryx Pro
+ dmi.product.sku: Not Applicable
+ dmi.product.version: oryp3-ess
+ dmi.sys.vendor: System76

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare

[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-10-22 Thread augusto_hp

> I'm affected by this bug. It breaks password changes in Nextcloud and other 
> websites.
> Is there any resolution to this bug?

There is a fixed version of 'ibus-gtk3' packaged as a '.deb' (you can
install) available on Firefox's bug page:
https://bugzilla.mozilla.org/show_bug.cgi?id=1405634

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+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 1799265] [NEW] avahi-daemon high cpu, unusable networking

2018-10-22 Thread Matt

Public bug reported:

Currently running Kubuntu 18.10, Dell XPS 13 9350

Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
consistently hampering network performance and using CPU for long
periods of time.

When booting machine from off state, avahi-daemon uses an entire CPU at
max load for approx 10 minutes. During this time, internet connectivity
via wifi is essentially unusable. The wifi connection is good, but it
seems that http transactions are cutoff mid-way so no webpage is able to
load.

When waking from sleep, the avahi-daemon causes similar symptoms, but
with less than 1 full cpu usage, and with somewhat less degraded network
performance, but still quite unusable.

I have never had issues with avahi prior to the 18.10 upgrade, so I am
fairly confident the issue is rooted in that change.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: avahi-daemon 0.7-4ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Oct 22 10:00:34 2018
InstallationDate: Installed on 2017-07-24 (455 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LD_PRELOAD=
 SHELL=/bin/bash
SourcePackage: avahi
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  avahi-daemon high cpu, unusable networking

Status in avahi package in Ubuntu:
  New

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1799265/+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 1799251] [NEW] mount options for /run should be the same as initramfs tools

Public bug reported:

mount options for /run should be the same as initramfs tools

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

** Affects: systemd (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  mount options for /run should be the same as initramfs tools

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  mount options for /run should be the same as initramfs tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799251/+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 1799251] Re: mount options for /run should be the same as initramfs tools

H... not sure if /run should be limited to 10%, or if runtime
journald should be limited to 1%.

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

Title:
  mount options for /run should be the same as initramfs tools

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  mount options for /run should be the same as initramfs tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799251/+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 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

2018-10-22 Thread Dmitry Shachnev

This is a bug in qdoc generator (built from qttools-opensource-src) and
in qtbase5-doc-html binary package. Re-assigning accordingly.

** Bug watch added: Debian Bug tracker #908328
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908328

** Also affects: qtdoc-opensource-src (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908328
   Importance: Unknown
   Status: Unknown

** Package changed: qtdoc-opensource-src (Debian) => qtbase-opensource-
src (Debian)

** Package changed: qtdoc-opensource-src (Ubuntu) => qtbase-opensource-
src (Ubuntu)

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Debian:
  Unknown

Bug description:
  The Qt offline documentation for cosmic is incomplete. In fact there's
  virtually no content what so ever. It would be easier I think to list
  what actually got picked up that what was missed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799111/+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 1799111] [NEW] lots of Classes missing from docs (e.g. QFileInfo)

You have been subscribed to a public bug:

The Qt offline documentation for cosmic is incomplete. In fact there's
virtually no content what so ever. It would be easier I think to list
what actually got picked up that what was missed.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtbase-opensource-src (Debian)
 Importance: Unknown
 Status: Unknown

-- 
lots of Classes missing from docs (e.g. QFileInfo)
https://bugs.launchpad.net/bugs/1799111
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src 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

Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2018-10-22 Thread Alejandro

Histill having the same problem  with the "systemd-shim"I don't know how
to fix it May be I will format everything and reinstall Ubuntu 18
againgreetings

  From: José Enrique <1773...@bugs.launchpad.net>
 To: avertaness...@yahoo.com 
 Sent: Thursday, October 18, 2018 3:10 AM
 Subject: Re: [Bug 1773859] Re: upgrades to 18.04 fail
   
Hy, in this moment I can't update my laptop or install any package or
program
Greetings

El mié., 17 oct. 2018 23:11, Brian Murray  escribió:

> ** Tags added: bugpattern-written
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  In Progress
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial.
>
>  [Regression Potential]
>
>    * systemd-shim/upstart are both removed and not supported in bionic,
>  thus forcing their removal via conflicts should bring the system into
>  an expected state.
>
>  [Other Info]
>
>    * original bug report
>
>
>  $ sudo apt upgrade
>  Reading package lists... Done
>  Building dependency tree
>  Reading state information... Done
>  Calculating upgrade... Done
>  The following packages will be REMOVED:
>    systemd-shim
>  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>  1 not fully installed or removed.
>  After this operation, 71.7 kB disk space will be freed.
>  Do you want to continue? [Y/n] y
>  (Reading database ... 63 files and directories currently installed.)
>  Removing systemd-shim (9-1bzr4ubuntu1) ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
>    different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>  dpkg: error processing package systemd-shim (--remove):
>    subprocess installed post-removal script returned error exit status 2
>  Errors were encountered while processing:
>    systemd-shim
>  E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>  Commenting out the dpkg-divert in systemd-shim's postrm solved this
>  for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1796221).
https://bugs.launchpad.net/bugs/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

  * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

  * monitor drop-off of upgrades with below reported problem

  * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial.

  [Regression Potential]

  * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]
  
  * original bug report

  
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following

[Touch-packages] [Bug 1799228] [NEW] USB-ports do not work

2018-10-22 Thread Stefanhdb

Public bug reported:

Two out of 3 USB-ports are not regognized anymore (i.e. when I insert a
USB-stick, it will not be shown in Nautilus). I tried various
workarounds from ubuntuusers, but they were not successful. Among them
to use "dpkg-reconfigure x-server". X-org now reported an error,
docuimented in the attachment.

Earlier I wanted to create an image with Clonezilla and selected a USB-
stick at port #2 as target, however, the target was not detected
successfully and the backup-procedure stopped. I suspect that the issues
may be relatd.

Kind regards,
Stefan

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Mon Oct 22 15:57:33 2018
DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() (E:Nicht 
gesperrt)
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.48, 4.4.0-137-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1ccd]
   Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a]
InstallationDate: Installed on 2016-07-21 (823 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. X555UB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash pci=noaer 
acpi_osi= acpi_backlight=native vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago)
dmi.bios.date: 01/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555UB.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555UB
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.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555UB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 15:43:15 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  USB-ports do not work

Status in xorg package in Ubuntu:
  New

Bug description:
  Two out of 3 USB-ports are not regognized anymore (i.e. when I insert
  a USB-stick, it will not be shown in Nautilus). I tried various
  workarounds from ubuntuusers, but they were not successful. Among them
  to use "dpkg-reconfigure x-server". X-org now reported an error,
  docuimented in the attachment.

  Earlier I wanted to create an image with Clonezilla and selected a
  USB-stick at port #2 as target, however, the target was not detected
  successfully and the backup-procedure stopped. I suspect that the
  issues may be relatd.

  Kind regards,
  Stefan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis:

[Touch-packages] [Bug 1799232] Re: my displays jump to the right occasionally

2018-10-22 Thread Max Waterman

IINM, this is the thunderbolt-3 display adaptor I am using:

https://www.startech.com/uk/AV/thunderbolt-3-video-
adapters/thunderbolt-3-to-dual-hdmi~TB32HD24K60

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

Title:
  my displays jump to the right occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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: Tue Oct 31 11:01:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799232/+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 1799240] [NEW] When I attempt to update "Software & Updates" I get "Failed to download repository information" window.

2018-10-22 Thread Robert Pearson

Public bug reported:

The error window details are:

E:The repository 'http://ppa.launchpad.net/webupd8team/indicator-
kdeconnect/ubuntu cosmic Release' does not have a Release file.

This is probably why the KDE app in the Software Boutique failed to
install. The repository is not yet ready for release.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: software-properties-gtk 0.96.27
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Oct 22 10:52:16 2018
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2018-10-22 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

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

Title:
  When I attempt to update "Software & Updates" I get "Failed to
  download repository information" window.

Status in software-properties package in Ubuntu:
  New

Bug description:
  The error window details are:

  E:The repository 'http://ppa.launchpad.net/webupd8team/indicator-
  kdeconnect/ubuntu cosmic Release' does not have a Release file.

  This is probably why the KDE app in the Software Boutique failed to
  install. The repository is not yet ready for release.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-gtk 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Oct 22 10:52:16 2018
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2018-10-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1799240/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

root@subtle-cobra:~# dpkg-query -W systemd
systemd 229-4ubuntu21.4
root@subtle-cobra:~# systemctl mask systemd-logind
Created symlink from /etc/systemd/system/systemd-logind.service to /dev/null.
root@subtle-cobra:~# systemctl stop systemd-logind
root@subtle-cobra:~# shutdown +1
Failed to set wall message, ignoring: Unit systemd-logind.service is masked.
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: 
Unit systemd-logind.service is masked.
root@subtle-cobra:~# echo $?
1
root@subtle-cobra:~# sleep 60

root@subtle-cobra:~# nano /etc/apt/sources.list
root@subtle-cobra:~# apt update
root@subtle-cobra:~# apt full-upgrade

root@subtle-cobra:~# dpkg-query -W systemd
systemd 229-4ubuntu21.5
root@subtle-cobra:~# shutdown +1
Failed to set wall message, ignoring: Unit systemd-logind.service is masked.
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: 
Unit systemd-logind.service is masked.
root@subtle-cobra:~# xnox@sochi:~$
(container shutdown correctly)


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in landscape-client source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

No journald watchdog kills yet for the xenial SRU.

https://errors.ubuntu.com/?release=Ubuntu%2016.04=systemd=month=229-4ubuntu21.5

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * systemd aborts journald, upon watchdog expiry and generates lots of crash 
reports
   * it appears that journald is simply stuck in fsync
   * it has been agreed to disable watchdog timer on journald

  [Test Case]

   * watch drop-off of errors w.r.t. watchdog timer

  [Regression Potential]

   * Potentially journald does get stuck, and thus is no longer
  automatically restarted with a sigabrt crash. However, so far, it is
  not known to do that.

  
  [Other Info]
   
   * Original bug report

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1773148/+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 1799232] Re: my displays jump to the right occasionally

2018-10-22 Thread Max Waterman

It just occurred again. dmesg output hasn't changed from what is in
CurrentDmesg.txt. Attempting to find details, I found:

$ boltctl list
 ● StarTech.com TB32HD24K60
   ├─ type:  peripheral
   ├─ name:  TB32HD24K60
   ├─ vendor:StarTech.com
   ├─ uuid:  cf03-0080-7718-2378-36488f03111d
   ├─ status:authorized
   │  ├─ authflags:  boot
   │  ├─ authorized: Mon 22 Oct 2018 14:13:05 UTC
   │  └─ connected:  Mon 22 Oct 2018 14:13:05 UTC
   └─ stored:yes
  ├─ when:   Wed 23 May 2018 08:12:24 UTC
  ├─ policy: auto
  └─ key:no

$ boltctl info cf03-0080-7718-2378-36488f03111d
 ● StarTech.com TB32HD24K60
   ├─ type:  peripheral
   ├─ name:  TB32HD24K60
   ├─ vendor:StarTech.com
   ├─ uuid:  cf03-0080-7718-2378-36488f03111d
   ├─ dbus path: 
/org/freedesktop/bolt/devices/cf03_0080_7718_2378_36488f03111d
   ├─ status:authorized
   │  ├─ authflags:  boot
   │  ├─ parent: c503-00b2-9d18-222d-f4d412c1b818
   │  ├─ syspath:
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0/0-1
   │  ├─ authorized: Mon 22 Oct 2018 14:13:05 UTC
   │  └─ connected:  Mon 22 Oct 2018 14:13:05 UTC
   └─ stored:yes
  ├─ when:   Wed 23 May 2018 08:12:24 UTC
  ├─ policy: auto
  └─ key:no

I don't see much else of interest. Let me know what else is needed.

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

Title:
  my displays jump to the right occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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: Tue Oct 31 11:01:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1.3

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

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

[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

2018-10-22 Thread Jacob D'Onofrio

I'm on cosmic, upgraded from bionic, and I have the same issue. I had to
revert to an X11 session in order to launch slack.

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu1.2

To manage

[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

2018-10-22 Thread Jacob D'Onofrio

Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] 
Activating service name='org.gnome.GConf' requested by ':1.84' (uid=1000 
pid=5586 comm="/snap/slack/9/usr/lib/slack/slack --executed-from
=" label="snap.slack.slack (complain)")
Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] 
Successfully activated service 'org.gnome.GConf'
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE)
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Backtrace:
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 0: 
/usr/bin/Xwayland (OsLookupColor+0x139) [0x55bab3776c39]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f18b4fcae1f]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 2: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f18b1449760]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f18b130e4b1]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f18b122b52a]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f18b122b5ee]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f18b122b6c9]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f18b10f7432]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f18b146335d]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f18b1827e89]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so 
(__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f18b1825c93]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 11: 
/usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55bab36a3c69]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 12: 
/usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55bab36a168b]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 13: 
/usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55bab376561d]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 14: 
/usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55bab36abbd9]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 15: 
/usr/bin/Xwayland (glvndGetExports+0xde5) [0x55bab3785f35]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 16: 
/usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55bab3740bae]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 17: 
/usr/bin/Xwayland (InitFonts+0x3b6) [0x55bab3744b36]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f18b4df209b]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 19: 
/usr/bin/Xwayland (_start+0x2a) [0x55bab36161ea]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE)
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Segmentation 
fault at address 0x68
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE)
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: Fatal server error:
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Caught signal 11 
(Segmentation fault). Server aborting
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE)

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins:

[Touch-packages] [Bug 1799232] [NEW] my displays jump to the right occasionally

2018-10-22 Thread Max Waterman

Public bug reported:

I have two monitors connected to my Dell XPS 13 via the USB-C output.

For the majority of the time, it works fine. Occasionally, one or both
of the images on the displays jump to the right, so that the right few
inches appear on the left.

To rectify the problem, I run the 'displays' app, move one of the
displays a little, click 'apply', and then, instead of 'keep settings',
I 'revert' them to their original, and then everything is fine for a
while.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 15:17:27 2018
DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:075b]
InstallationDate: Installed on 2017-10-11 (376 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. XPS 13 9360
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
dmi.bios.date: 05/21/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.7.1
dmi.board.name: 05JK94
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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: Tue Oct 31 11:01:05 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5193 
 vendor SHP
xserver.version: 2:1.19.3-1ubuntu1.3

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  my displays jump to the right occasionally

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two monitors connected to my Dell XPS 13 via the USB-C output.

  For the majority of the time, it works fine. Occasionally, one or both
  of the images on the displays jump to the right, so that the right few
  inches appear on the left.

  To rectify the problem, I run the 'displays' app, move one of the
  displays a little, click 'apply', and then, instead of 'keep
  settings', I 'revert' them to their original, and then everything is
  fine for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:17:27 2018
  DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:075b]
  InstallationDate: Installed on 2017-10-11 (376 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago)
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.7.1
  dmi.board.name: 05JK94
  dmi.board.vendor:

[Touch-packages] [Bug 805423] Re: pam_motd needs a module option to disable in-line dynamic updates

2018-10-22 Thread GGrandes

I have same problem in Ubuntu 18.04, +2 seconds in sshd logins.

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

Title:
  pam_motd needs a module option to disable in-line dynamic updates

Status in Landscape Client:
  Invalid
Status in pam package in Ubuntu:
  Fix Released

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 10.04.2 LTS
  Release:  10.04

  2)  Installiert: 1.1.1-2ubuntu5.3
Kandidat: 1.1.1-2ubuntu5.3
Versions-Tabelle:
   *** 1.1.1-2ubuntu5.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
  100 /var/lib/dpkg/status
   1.1.1-2ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages

  3) Login on systems with high load/a lot of io wait via ssh should
  still be possible.

  4) On servers with high load or a lot of io wait login times out,
  because pam_motd does io intensive calculations. This hurts even more
  when using nagios check_by_ssh. There should be a way to use a cron
  job again (like update-motd did). Logging into a system is more
  important than motd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/805423/+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 997217] Re: salsauthd maxes cpu

2018-10-22 Thread Roberto Suarez

I reply to myself: while the version in Xenial is *still* affected with
this bug, any of the later versions is fixed. The version
2.1.26.dfsg1-14 is bugged, but the next one, 2.1.26.dfsg1-15 is not. I
backported the one in Bionic easily and it's working now without
problems.

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

Title:
  salsauthd maxes cpu

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Precise:
  Triaged

Bug description:
  sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a
  bug that causes heavy cpu utilization, impacting normal operation of
  one of our mail servers following an upgrade to Ubuntu 12.04.

  We are running the daemon with the following options:

  /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m
  /var/spool/postfix/var/run/saslauthd -n 5

  
  We noticed that users were unable to send mail and that the saslauthd 
processes were using approximately 100% of each cpu core. An strace of one of 
the runaway process showed that it was stuck in the following behaviour:

  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  .

  
  with further inspection showing that the file descriptor in question was a 
socket connected to our imap server in CLOSE_WAIT.

  Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin,
  we came across the following code, repeated in two locations:

  while( select (fds, , NULL, NULL,  ) >0 ) {
 if ( FD_ISSET(s, ) ) {
ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
if ( ret<0 ) {
   rc = ret;
   break;
} else {
   rc += ret;
}
 }
  }

  
  It looks like this loop is expected to run until a read error is encountered 
or the timeout of 1 second is reached. There is no test to check that 0 bytes 
were read, indicating that the connection was closed by the remote peer. Since 
select() will immediately return the size of the set of the partially closed 
descriptor (1, which is >0), and calls to read() will always yield 0 bytes, 
there's the potential for execution to get stuck in this non blocking loop and 
I'm presuming that that's what's happening here.

  We've not performed any further analysis to prove that this is really
  what's happening but if my intuition is correct then our IMAP server
  (an nginx imap proxy) most liklely closes the connection at an
  unexpected time under as yet undetermined conditions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 1799218] [NEW] brightness controller missing

2018-10-22 Thread vamsi krishna

Public bug reported:

brightness controller gone after installing nvidia drivers

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 18:26:31 2018
DistUpgraded: 2018-09-13 00:30:24,004 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
InstallationDate: Installed on 2018-08-16 (66 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Sony Corporation VPCEH3AEN
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-12 (39 days ago)
dmi.bios.date: 11/17/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R0190Z9
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH3AEN:pvrC1074QWS:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEH3AEN
dmi.product.version: C1074QWS
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 17:22:30 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  brightness controller missing

Status in xorg package in Ubuntu:
  New

Bug description:
  brightness controller gone after installing nvidia drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 18:26:31 2018
  DistUpgraded: 2018-09-13 00:30:24,004 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2018-08-16 (66 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH3AEN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  SourcePackage: xorg

[Touch-packages] [Bug 1799215] Re: package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from oth

2018-10-22 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 libpng in Ubuntu.
https://bugs.launchpad.net/bugs/1799215

Title:
  package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz',
  which is different from other instances of package libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  I have an error on my installation package. I can not force install. It 
"seems" that my "installed packages have unmet dependencies".
  This is the output of the terminal :

  
  sudo apt-get install -f
  [sudo] password for ***: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
libllvm5.0 linux-headers-4.13.0-45 linux-headers-4.13.0-45-generic
linux-headers-4.4.0-131 linux-headers-4.4.0-131-generic
linux-image-4.13.0-43-generic linux-image-4.13.0-45-generic
linux-image-4.4.0-131-generic linux-image-extra-4.13.0-43-generic
linux-image-extra-4.13.0-45-generic linux-image-extra-4.4.0-131-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libpng12-0
  The following packages will be upgraded:
libpng12-0
  1 to upgrade, 0 to newly install, 0 to remove and 89 not to upgrade.
  2 not fully installed or removed.
  Need to get 0 B/116 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 326539 files and directories currently installed.)
  Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
  Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
   trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', 
which is different from other instances of package libpng12-0:amd64
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Thanks for your help !

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.54-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   libpng12-0: Install
   libpng12-0: Configure
   libpng12-0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct 22 13:24:25 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DpkgHistoryLog:
   Start-Date: 2018-10-22  13:24:22
   Commandline: apt-get install -f
   Requested-By: eternalfalcon (1000)
   Upgrade: libpng12-0:amd64 (1.2.54-1ubuntu1, 1.2.54-1ubuntu1.1)
  DpkgTerminalLog:
   Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', 
which is different from other instances of package libpng12-0:amd64
  DuplicateSignature:
   package:libpng12-0:1.2.54-1ubuntu1
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', 
which is different from other instances of package libpng12-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other 
instances of package libpng12-0:amd64
  InstallationDate: Installed on 2018-05-24 (150 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: libpng
  Title: package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is 
different from other instances of package libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1799215] [NEW] package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from o

2018-10-22 Thread eternal falcon

Public bug reported:

I have an error on my installation package. I can not force install. It "seems" 
that my "installed packages have unmet dependencies".
This is the output of the terminal :


sudo apt-get install -f
[sudo] password for ***: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libllvm5.0 linux-headers-4.13.0-45 linux-headers-4.13.0-45-generic
  linux-headers-4.4.0-131 linux-headers-4.4.0-131-generic
  linux-image-4.13.0-43-generic linux-image-4.13.0-45-generic
  linux-image-4.4.0-131-generic linux-image-extra-4.13.0-43-generic
  linux-image-extra-4.13.0-45-generic linux-image-extra-4.4.0-131-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libpng12-0
The following packages will be upgraded:
  libpng12-0
1 to upgrade, 0 to newly install, 0 to remove and 89 not to upgrade.
2 not fully installed or removed.
Need to get 0 B/116 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 326539 files and directories currently installed.)
Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', 
which is different from other instances of package libpng12-0:amd64
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks for your help !

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpng12-0 1.2.54-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 libpng12-0: Install
 libpng12-0: Configure
 libpng12-0: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 22 13:24:25 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 zlib1g 1:1.2.8.dfsg-2ubuntu4.1
DpkgHistoryLog:
 Start-Date: 2018-10-22  13:24:22
 Commandline: apt-get install -f
 Requested-By: eternalfalcon (1000)
 Upgrade: libpng12-0:amd64 (1.2.54-1ubuntu1, 1.2.54-1ubuntu1.1)
DpkgTerminalLog:
 Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', 
which is different from other instances of package libpng12-0:amd64
DuplicateSignature:
 package:libpng12-0:1.2.54-1ubuntu1
 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', 
which is different from other instances of package libpng12-0:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other 
instances of package libpng12-0:amd64
InstallationDate: Installed on 2018-05-24 (150 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: libpng
Title: package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is 
different from other instances of package libpng12-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz',
  which is different from other instances of package libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  I have an error on my installation package. I can not force install. It 
"seems" that my "installed packages have unmet dependencies".
  This is the output of the terminal :

  
  sudo apt-get install -f
  [sudo] password for ***: 
  Reading package lists... Done
  Building dependency tree

[Touch-packages] [Bug 1796911] Re: libnss-systemd was denied talking to pid1

2018-10-22 Thread David Myers

I see very similar errors with strongSwan when the daemon charon is run
as non-root:

[119648.278942] audit: type=1107 audit(1540071113.311:674): pid=806
uid=105 auid=4294967295 ses=4294967295 subj==unconfined
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system"
path="/org/freedesktop/systemd1"
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers"
mask="send" name="org.freedesktop.systemd1" pid=26066
label="/usr/lib/ipsec/charon" peer_pid=1 peer_label="unconfined"

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

Title:
  libnss-systemd was denied talking to pid1

Status in apparmor package in Ubuntu:
  New

Bug description:
  cosmic
  apparmor 2.12-4ubuntu8
  kernel 4.18.0-8-generic #9-Ubuntu 

  I'm getting these audit messages in dmesg showing apparmor denied errors:
  [   68.649187] audit: type=1107 audit(1539094926.655:32): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1091 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  161.059989] audit: type=1107 audit(1539095018.957:33): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1191 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  437.582034] audit: type=1107 audit(1539095295.553:34): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1534 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  468.184231] audit: type=1107 audit(1539095326.159:35): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1577 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'

  I pinged #ubuntu-hardened, and xnox had these comments:
   ha
   ahasenack, libnss-systemd was denied talking to pid1
   to query dynamicusers i think
   so i think something somehwere need adjustemnt to allow libnss-systemd 
to talk to pid1 and call GetDynamicUsers
   LookupDynamicUserByName LookupDynamicUserByUID GetDynamicUsers
   as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1796911/+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 997217] Re: salsauthd maxes cpu

2018-10-22 Thread Roberto Suarez

I'm seeing this exact same problem with saslauthd in sasl2-bin
2.1.26.dfsg1-14, using Ubuntu 16.04.4. Is there any other possible
cause?

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

Title:
  salsauthd maxes cpu

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Precise:
  Triaged

Bug description:
  sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a
  bug that causes heavy cpu utilization, impacting normal operation of
  one of our mail servers following an upgrade to Ubuntu 12.04.

  We are running the daemon with the following options:

  /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m
  /var/spool/postfix/var/run/saslauthd -n 5

  
  We noticed that users were unable to send mail and that the saslauthd 
processes were using approximately 100% of each cpu core. An strace of one of 
the runaway process showed that it was stuck in the following behaviour:

  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  select(9, [8], NULL, NULL, {0, 0})  = 1 (in [8], left {0, 0})
  read(8, "", 940)= 0
  .

  
  with further inspection showing that the file descriptor in question was a 
socket connected to our imap server in CLOSE_WAIT.

  Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin,
  we came across the following code, repeated in two locations:

  while( select (fds, , NULL, NULL,  ) >0 ) {
 if ( FD_ISSET(s, ) ) {
ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
if ( ret<0 ) {
   rc = ret;
   break;
} else {
   rc += ret;
}
 }
  }

  
  It looks like this loop is expected to run until a read error is encountered 
or the timeout of 1 second is reached. There is no test to check that 0 bytes 
were read, indicating that the connection was closed by the remote peer. Since 
select() will immediately return the size of the set of the partially closed 
descriptor (1, which is >0), and calls to read() will always yield 0 bytes, 
there's the potential for execution to get stuck in this non blocking loop and 
I'm presuming that that's what's happening here.

  We've not performed any further analysis to prove that this is really
  what's happening but if my intuition is correct then our IMAP server
  (an nginx imap proxy) most liklely closes the connection at an
  unexpected time under as yet undetermined conditions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2018-10-22 Thread D . Schäfer

Dell XPS 13 9630

Had the same problem as multiple times described above what helped in my
case

$ alsactl restore

weird but it helped

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

Also reading above comments, did we verify that Bionic is correctly
synchronized, and needs no workaround? It would be nice to reliably
confirm that these things operate race-free in bionic and up, and then
mark this bug to affect only xenial and below.

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

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

2018-10-22 Thread Pirouette Cacahuète

Same on upgrade from Ubuntu 18.04 to 18.10, fuser -v confirms exclusive
access taken by timidity on the sound device, removing timidity* fixes.

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1799203] [NEW] Kernel Detects Sound Chip but PulseAudio does not