[Touch-packages] [Bug 1767578] [NEW] libcurl is missing brotli support

[cc]

Public bug reported:

Now that the bionic release of curl has added HTTP/2 support, please
consider adding support for brotli too.

This can be compiled in with the --with-brotli flag that is already
available and adding the libbrotli-dev package as a dependency.

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


** Tags: brotli curl

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

Title:
  libcurl is missing brotli support

Status in curl package in Ubuntu:
  New

Bug description:
  Now that the bionic release of curl has added HTTP/2 support, please
  consider adding support for brotli too.

  This can be compiled in with the --with-brotli flag that is already
  available and adding the libbrotli-dev package as a dependency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1767578/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Corey Seliger]

This also creates a conflict with r-core-base. I can have curl installed
or R installed, but not both at the same time. Ubuntu 18.04.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1705297] Re: login after booting hangs

[Launchpad Bug Tracker]

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

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

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Adria]

@28 Good thinking on the MATE solution. This package is called "mate-
mouse-properties"

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1767556] [NEW] Screen goes blank after booting

[Manoz]

Public bug reported:

I can only use the recovery mode and not the normal mode on ubuntu. This
is happening after i upgraded to Ubuntu 18.04. I have an Asus R554L
model laptop and no special hardware at this time.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
Date: Fri Apr 27 22:59:45 2018
DistUpgraded: 2018-04-27 22:06:39,664 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK COMPUTER INC. TP550LAB
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c1a388d3-c492-42e1-a077-44d34cf97386 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-28 (0 days ago)
dmi.bios.date: 12/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TP550LAB.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TP550LAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP550LAB.202:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TP
dmi.product.name: TP550LAB
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.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
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: Fri Apr 27 22:43:41 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
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/1767556

Title:
  Screen goes blank after booting

Status in xorg package in Ubuntu:
  New

Bug description:
  I can only use the recovery mode and not the normal mode on ubuntu.
  This is happening after i upgraded to Ubuntu 18.04. I have an Asus
  R554L model laptop and no special hardware at this time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr 27 22:59:45 2018
  DistUpgraded: 2018-04-27 22:06:39,664 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. TP550LAB
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c1a388d3-c492-42e1-a077-44d34cf97386 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (0 days ago)
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP550LAB.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP550LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.

[Touch-packages] [Bug 1767552] [NEW] screen rotates if laptop tilts

[keith moore]

Public bug reported:

I have ran windows 7, 10, ubuntu 16.04, linux mint and maybe others and
i can't recall it doing this before. it is hp 450 g2 laptop. it is not a
2in1 tablet/laptop. i looked for info in forums but had no luck. i also
checked in settings because i thought it may have had a tablet setting i
could turn off.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 21:58:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:2248]
   Subsystem: Hewlett-Packard Company Topaz PRO [Radeon R5 M255] [103c:224a]
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP ProBook 450 G2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d0b638ce-09f3-4d54-a78f-b7aeebaef22f ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M73 Ver. 01.09
dmi.board.name: 2248
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 59.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.09:bd01/21/2015:svnHewlett-Packard:pnHPProBook450G2:pvrA3009DD10303:rvnHewlett-Packard:rn2248:rvrKBCVersion59.21:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 450 G2
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
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 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

** 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/1767552

Title:
  screen rotates if laptop tilts

Status in xorg package in Ubuntu:
  New

Bug description:
  I have ran windows 7, 10, ubuntu 16.04, linux mint and maybe others
  and i can't recall it doing this before. it is hp 450 g2 laptop. it is
  not a 2in1 tablet/laptop. i looked for info in forums but had no luck.
  i also checked in settings because i thought it may have had a tablet
  setting i could turn off.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 21:58:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:2248]
 Subsystem: Hewlett-Packard Company Topaz PRO [Radeon R5 M255] [103c:224a]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProBook 450 G2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d0b638ce-09f3-4d54-a78f-b7aeebaef22f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.09
  dmi.board.name: 2248
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias:

[Touch-packages] [Bug 1767535] [NEW] package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

[Abdul Khan]

Public bug reported:

I tried updating ubuntu and then i got this error.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-crypto 2.6.1-4build1
ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
Uname: Linux 3.19.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Fri Apr 27 18:49:42 2018
DuplicateSignature: package:python-crypto:2.6.1-4build1:subprocess new 
pre-removal script returned error exit status 126
ErrorMessage: subprocess new pre-removal script returned error exit status 126
InstallationDate: Installed on 2016-05-15 (712 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.14
SourcePackage: python-crypto
Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 126
UpgradeStatus: Upgraded to trusty on 2018-04-27 (0 days ago)

** Affects: python-crypto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 126

Status in python-crypto package in Ubuntu:
  New

Bug description:
  I tried updating ubuntu and then i got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Apr 27 18:49:42 2018
  DuplicateSignature: package:python-crypto:2.6.1-4build1:subprocess new 
pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (712 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 126
  UpgradeStatus: Upgraded to trusty on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1767535/+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 1767535] Re: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

[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 python-crypto in Ubuntu.
https://bugs.launchpad.net/bugs/1767535

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 126

Status in python-crypto package in Ubuntu:
  New

Bug description:
  I tried updating ubuntu and then i got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Apr 27 18:49:42 2018
  DuplicateSignature: package:python-crypto:2.6.1-4build1:subprocess new 
pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (712 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 126
  UpgradeStatus: Upgraded to trusty on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1767535/+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 1767535] Re: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126

[Abdul Khan]

I seek your assistance in resolving this issue

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

Title:
  package python-crypto 2.6.1-4build1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 126

Status in python-crypto package in Ubuntu:
  New

Bug description:
  I tried updating ubuntu and then i got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4build1
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-61-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Apr 27 18:49:42 2018
  DuplicateSignature: package:python-crypto:2.6.1-4build1:subprocess new 
pre-removal script returned error exit status 126
  ErrorMessage: subprocess new pre-removal script returned error exit status 126
  InstallationDate: Installed on 2016-05-15 (712 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 126
  UpgradeStatus: Upgraded to trusty on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1767535/+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 1767529] [NEW] [broadwell-rt286 - broadwell-rt286, playback] No sound at all but sound controls available

[Igor]

Public bug reported:

hi, this is fresh install of Ubuntu 18.04. I have sound controls but
neither speakers nor headphones generate any sound. Computer is HP
Spectre x360 from 2015

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   igor   1455 F...m pulseaudio
 /dev/snd/controlC1:  igor   1455 F pulseaudio
 /dev/snd/controlC0:  igor   1455 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 28 01:45:51 2018
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:broadwellrt286 
failed
Symptom_Card: Built-in Audio - broadwell-rt286
Symptom_Type: No sound at all
Title: [broadwell-rt286 - broadwell-rt286, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.47
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 802D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 58.63
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.47:bd11/22/2017:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.63:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre x360 Convertible 13
dmi.sys.vendor: Hewlett-Packard

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1767529

Title:
  [broadwell-rt286 - broadwell-rt286, playback] No sound at all but
  sound controls available

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  hi, this is fresh install of Ubuntu 18.04. I have sound controls but
  neither speakers nor headphones generate any sound. Computer is HP
  Spectre x360 from 2015

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   igor   1455 F...m pulseaudio
   /dev/snd/controlC1:  igor   1455 F pulseaudio
   /dev/snd/controlC0:  igor   1455 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 01:45:51 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:broadwellrt286 
failed
  Symptom_Card: Built-in Audio - broadwell-rt286
  Symptom_Type: No sound at all
  Title: [broadwell-rt286 - broadwell-rt286, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 802D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.63
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.47:bd11/22/2017:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.63:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1767529/+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 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'

[Seth Arnold]

Paula, no need to do anything if you only see this during an upgrade.

Thanks

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

Title:
  GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib
  /gdk-pixbuf-2.0/2.10.0/loaders.cache'

Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Debian:
  Invalid

Bug description:
  During installation of updated version of libgdk-pixbuf2.0-0 on August
  10th 2010, the apt term.log contained multiple (>300) copies of the
  following warning:

  (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf
  loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No
  such file or directory

  Nevertheless, the file complained about exists, and is readable in
  gedit.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
  Uname: Linux 2.6.35-15-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Mon Aug 16 18:13:29 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdk-pixbuf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+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 1764858] Re: Can't update / install / delete packages due to missing libzstd.so.1

[Ubfan]

My situation breaking the install was a legacy install, to a disk
partition with another Ubuntu installation (16.04) maintaining the
bootloader files.  The install was done without a bootloader (select an
empty USB, and the error dialog allows you to procede without a
bootloader).  The update (after a month of successful updates) with a
kernel update 4.0.15-15), apparently got really messed up by this
situation.  There was no /var/log/installer directory, nor the
libzstd.so.1... library.  With the release, I'll just reinstall, let the
18.04 take over the bootloader,  and jump through the hoops to reinstall
grub from the  16.04 installation.  So, not every installation needs to
add a bootloader, but it's too bad it's not as simple as adding a "none"
to the choice of bootloader locations.

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

Title:
  Can't update / install / delete packages due to missing libzstd.so.1

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1764858/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

[Roman Shchekin]

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

This is very old and annoying bug. Can someone fix it, please???

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767453/+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 1754270] Re: systemd-user PAM configuration should initialize the keyring with pam_keyinit

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-user PAM configuration should initialize the keyring with
  pam_keyinit

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  /etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's
  possible this should instead be added to common-session-noninteractive
  but I am not entirely sure about that - someone with more
  understanding of the PAM modules would probably need to weigh in on
  that.  In any case systemd-user itself should at least have it - as it
  has it's own special PAMname for processes it launches.

  This means that the keyring does not link to the user keyring as it
  should, and will cause issues with programs needing a key from the
  keyring.  In particular the use case that breaks for me is using
  'fscrypt' and 'libpam-fscrypt' however anything making use of kernel
  keyrings would be affected.

  Something non-obvious about this, is that many desktop session
  processes are started under 'systemd-user' instead of the 'session' -
  this includes gnome-terminal-server which means any gnome-terminal
  shell runs under this context.  If you start xterm instead of gnome-
  terminal, you get a different keyring and this can cause confusion
  when debugging the issue as some processes are in one state and the
  others are in another including your primary debug tool gnome-
  terminal.  You can verify this by running 'systemctl status $(pidof
  gnome-terminal)' and 'systemctl status $(pidof xterm)' and note the
  different hierachy.

  The change to add pam_keyinit.so was made upstream in December 2016:
  
https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f

  Ubuntu should make the same change so that services needing a keyring
  will work correctly in the desktop session, and the same keyring is
  used for processes launched under both methods.  In my test I add the
  usual pam_keyinit.so line after "pam_limits.so" and before "common-
  session-noninteractive".  I am not sure if this is the most ideal
  location (but it appears to work).

  
  You can test the behavior by running "keyctl show @s" in both contexts

  Working contexts:
  - xterm
  - SSH login

  Broken contexts:
  - gnome-terminal
  - systemd-run --user keyctl show @s (then check output with journalctl --user 
--follow)

  
  When the configuration is broken you will see this output:
  lathiat@ubuntu:~/src/systemd$ keyctl show @s
  Keyring
59654779 --alswrv   1000  1000  keyring: _ses
 6806191 s-rv  0 0   \_ user: invocation_id

  When the configuration is working, you will see a link to the user session 
instead:
  lathiat@ubuntu:~/src/systemd$ keyctl show @s
  Keyring
59654779 --alswrv   1000  1000  keyring: _ses
 6806191 s-rv  0 0   \_ keyring: _uid.1000

  
  As background, what is broken on my test setup with libpam-fscrypt?
  gnome-terminal for example is unable to write any file in my encrypted /home 
which means that it cannot save preferences, so if you go into preferences and 
try to tick a checkbox it will immediately revert and an error is logged to the 
journal.  You can use the guide at https://github.com/google/fscrypt to setup 
such a system if you wish to fully test my case.  But you can simply verify the 
behavior as above.

  Verified on bionic (its the only version with fscrypt) however this
  issue extends back to at least xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754270/+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 1754686] Re: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

[Nowell Morris]

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

https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294 post #25
worked for me to install slack-3.1

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686/+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 1767484] [NEW] package libxcb1:i386 1.13-1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[anibal]

Public bug reported:

no puedo instalar ningun programa de la tienda como lo puedo arreglar

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libxcb1:i386 1.13-1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
Date: Fri Apr 27 16:13:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ErrorMessage: problemas de dependencias - se deja sin configurar
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=30afcc43-18e7-41ab-b173-88e63a9e3ce7 ro quiet splash
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: libxcb
Title: package libxcb1:i386 1.13-1 failed to install/upgrade: problemas de 
dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
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 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

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


** Tags: apport-package bionic i386 ubuntu

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

Title:
  package libxcb1:i386 1.13-1 failed to install/upgrade: problemas de
  dependencias - se deja sin configurar

Status in libxcb package in Ubuntu:
  New

Bug description:
  no puedo instalar ningun programa de la tienda como lo puedo arreglar

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libxcb1:i386 1.13-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Apr 27 16:13:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ErrorMessage: problemas de dependencias - se deja sin configurar
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=30afcc43-18e7-41ab-b173-88e63a9e3ce7 ro quiet splash
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: libxcb
  Title: package libxcb1:i386 1.13-1 failed to install/upgrade: problemas de 
dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

I updated the ifupdown pkg builds in my test ppa using the upstream
(debian) patch, which is a variation of my previous patch.  Anyone
affected by this regression please test with the latest ifupdown and
vlan pkgs from my ppa.

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  In Progress
Status in ifupdown source package in Trusty:
  In Progress
Status in vlan source package in Trusty:
  In Progress
Status in ifupdown source package in Xenial:
  In Progress
Status in vlan source package in Xenial:
  In Progress
Status in ifupdown source package in Artful:
  In Progress
Status in vlan source package in Artful:
  In Progress
Status in ifupdown source package in Bionic:
  In Progress
Status in vlan source package in Bionic:
  In Progress
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
└─run-parts,1501 /etc/network/if-pre-up.d
└─bridge,1502 /etc/network/if-pre-up.d/bridge
└─bridge,1508 /etc/network/if-pre-up.d/bridge
└─vlan,1511 /etc/network/if-pre-up.d/vlan
└─ifup,1532 eth0

  
  
  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet static
address 192.168.10.65
netmask 255.255.255.192
gateway 192.168.10.66

  auto eth0.11
address 192.168.11.1
netmask 255.255.255.0

  auto br1134
  iface br1134 inet manual
bridge_ports eth0.1134
bridge_stp off
bridge_fd 0
  

  The underlying interface eth0.1134 is not explicitly defined, but was
  previously auto-created during "ifup -a" execution. This apparently
  fails now.

  Reverting back to the 10.1 version re-establishes old behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1726930

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Incomplete
Status in laptop-mode-tools source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed
Status in laptop-mode-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Trans

[Touch-packages] [Bug 1767407] Re: package software-properties-common 0.96.24.32.1 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit s

[Brian Murray]

This error is strange:

/var/lib/dpkg/info/python3-apt.prerm: /usr/bin/py3clean:
/usr/bin/python3: bad interpreter: No such file or directory

Especially since the Python3Details shows /usr/bin/python3 linking to
/usr/bin/python3.6. Just to be sure that is the output of 'which
python3'?

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package software-properties-common 0.96.24.32.1 failed to
  install/upgrade: new software-properties-common package pre-removal
  script subprocess returned error exit status 126

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I don't know how it happened

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 14:03:01 2018
  ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.32.1 failed to 
install/upgrade: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1767407/+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 1767444] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Michel Weimerskirch]

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

I had the same issue. Thanks for the hint with libssl1.1 being the
cause. I disabled all PPAs and then reinstalled libssl1.1 as well as
openssl manually by reinstalling the versions provided with Ubuntu
Bionic. After that, apt-get was able to finish configuring all packages.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Setting up ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1
  dpkg: dependency problems prevent configuration of 
software-properties-common:
   software-properties-common depends on ca-certificates; however:
Package ca-certificates is not configured yet.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 23:23:20 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-10 (381 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767444/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

[Brian Murray]

** Description changed:

  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.
  
+ [Regression Potential]
+ The test being modified is designed to not report crashes that happen during 
logout. It's possible that some reports don't have a Date in them but in that 
case we couldn't compare the logind_session information to the Date anyway so 
those crashes would have been reported anyway. Regardless, the potential is 
that we'll have some more crashes reported about things crashing on logout 
which is better than the hundreds of crashes we get like this one.
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress

Bug description:
  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.

  [Regression Potential]
  The test being modified is designed to not report crashes that happen during 
logout. It's possible that some reports don't have a Date in them but in that 
case we couldn't compare the logind_session information to the Date anyway so 
those crashes would have been reported anyway. Regardless, the potential is 
that we'll have some more crashes reported about things crashing on logout 
which is better than the hundreds of crashes we get like this one.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1767407] Re: package software-properties-common 0.96.24.32.1 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit s

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  package software-properties-common 0.96.24.32.1 failed to
  install/upgrade: new software-properties-common package pre-removal
  script subprocess returned error exit status 126

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I don't know how it happened

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 14:03:01 2018
  ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.32.1 failed to 
install/upgrade: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1767407/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

[Brian Murray]

The point of comparing the logind_session time is to the Date is try and
determine if the crash happened during logout and not report the crash.
Without a Date in the report this comparison can not be done and
get_timestamp only returns None or a timestamp in seconds since epoch if
Date exists in the report so requiring Date in the report is fine.

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress

Bug description:
  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1731610] Re: add --save option to apport-collect

[Brian Murray]

apport-collect is used to gather additional information about a bug
reported in Launchpad so requires an internet connection to work.
Additionally, if you do have an internet connection you can choose to
keep the report for filing later. So I this is bug isn't really valid.

 $ apport-collect 1760220
   
*** Collecting problem information
   
The collected information can be sent to the developers to improve the
application. This might take a few minutes.


*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (5.7 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): k
Problem report file: /tmp/apport.apport.dea1bbst.apport


** Changed in: apport (Ubuntu)
   Status: New => Invalid

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

Title:
  add --save option to apport-collect

Status in apport package in Ubuntu:
  Invalid

Bug description:
  The `--save` option of `apport-bug` allows collected and generated
  data to be save in a file and to use the data for a report later. It'd
  be nice if `apport-collect` would have this function since collecting
  the data for an update and having an internet connection might not be
  possible at all times.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Nov 11 09:17:10 2017
  InstallationDate: Installed on 2015-12-12 (699 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-19 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1731610/+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 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Brian Murray]

The fixed version of libssl is installed, and the error message is not
about a duplicate certificate so this is not a duplicate of bug 1764848.

Updating certificates in /etc/ssl/certs...
rehash: skipping cacert.cer,it does not contain exactly one certificate or CRL
rehash: skipping req.pem,it does not contain exactly one certificate or CRL

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767453/+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 1767444] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Brian Murray]

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

You have libssl1.1 from a PPA and it does not include an important bug
fix which does exist in the package from the official Ubuntu archive.
This causes the ca-certificates package installation to fail.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Setting up ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1
  dpkg: dependency problems prevent configuration of 
software-properties-common:
   software-properties-common depends on ca-certificates; however:
Package ca-certificates is not configured yet.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 23:23:20 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-10 (381 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767444/+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 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[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 ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1767453

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767453/+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 1738204] Re: error updating apport with apt

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1745406
   plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

Title:
  error updating apport with apt

Status in apport package in Ubuntu:
  New

Bug description:
  apt log session:

  ...
  Configuring python3-apport (2.20.8-0ubuntu4) ...
  Configuring apport (2.20.8-0ubuntu4) ...
  Job for apport.service failed because timeout was exceeded.
  See "systemctl status apport.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript apport, action "start" failed.
  ● apport.service - LSB: automatic crash report generation
      Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
      Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 7ms 
ago
    Docs: man: systemd-sysv-generator (8)
     Process: 9187 ExecStart = / etc / init.d / apport start (code = killed, 
signal = TERM)
   Tasks: 2 (limit: 4915)
      CGroup: /system.slice/apport.service
      └─9190 plymouth --ping

  ...

  $ systemctl status apport.service

  ● apport.service - LSB: automatic crash report generation
 Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
 Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 2h 
35min ago
   Docs: man:systemd-sysv-generator(8)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/apport.service
 └─9190 plymouth --ping

  dez 14 08:38:36 etm systemd[1]: Starting LSB: automatic crash report 
generation...
  dez 14 08:43:36 etm systemd[1]: apport.service: Start operation timed out. 
Terminating.
  dez 14 08:43:36 etm systemd[1]: apport.service: Failed with result 'timeout'.
  dez 14 08:43:36 etm systemd[1]: Failed to start LSB: automatic crash report 
generation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu4
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 11:02:39 2017
  InstallationDate: Installed on 2017-09-29 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738204/+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 1767455] [NEW] package libperl5.26 5.26.0-8ubuntu1.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent

[Kacouchia Marie-Aude]

Public bug reported:

I can't upgrade Ubuntu because of this package.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.26 5.26.0-8ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Apr 27 19:39:55 2018
ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres 
instances du paquet libperl5.26:i386
InstallationDate: Installed on 2017-10-13 (196 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: perl
Title: package libperl5.26 5.26.0-8ubuntu1.1 failed to install/upgrade: 
tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz 
», qui est différent d'autres instances du paquet libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package libperl5.26 5.26.0-8ubuntu1.1 failed to install/upgrade:
  tentative de remplacement de «
  /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent
  d'autres instances du paquet libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  I can't upgrade Ubuntu because of this package.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr 27 19:39:55 2018
  ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres 
instances du paquet libperl5.26:i386
  InstallationDate: Installed on 2017-10-13 (196 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1.1 failed to install/upgrade: 
tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz 
», qui est différent d'autres instances du paquet libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1767455/+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 1767453] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[kevinred]

Public bug reported:

Happened during upgrade to ubunut 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 17:51:26 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767453/+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 1729218] Re: package rsyslog-pgsql 8.16.0-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Brian Murray]

It looks like a database is missing.

^[[K^[[1;1H^[[37mPackage 
configuration^[[20;2H^[[30m^[[47mâ<94><8c>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94>¤
 ^[[31mConfiguring rsyslog-pgsql^[[30m 
â<94><9c>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><90>^[[21;2Hâ<94><82>

â<94><82>^[[97m^[[40m ^[[22;2H^[[30m^[[47mâ<94><82> The 
rsyslog-pgsql package must have a database installed and configured before it 
can be   â<94><82>^[[97m^[[40m ^[[23;2H^[[30m^[[47mâ<94><82> used. This can 
be optionally handled with dbconfig-common. 
â<94><82>^[[97m^[[40m ^[[24;2H^[[30m^[[47mâ<94><82> 
   
â<94><82>^[[97m^[[40m ^[[25;2H^[[30m^[[47mâ<94><82> If you are an advanced 
database administrator and know that you want to perform this   
â<94><82>^[[97m^[[40m ^[[26;2H^[[30m^[[47mâ<94><82> configuration manually, or 
if your database has already been  installed and configured, you 
â<94><82>^[[97m^[[40m ^[[27;2H^[[30m^[[47mâ<94><82> should refuse this option. 
Details on what needs to be done should most likely be provided in  
â<94><82>^[[97m^[[40m ^[[28;2H^[[30m^[[47mâ<94><82> 
/usr/share/doc/rsyslog-pgsql.   
   â<94><82>^[[97m^[[40m ^[[29;2H^[[30m^[[47mâ<94><82>  

  â<94><82>^[[97m^[[40m ^[[30;2H^[[30m^[[47mâ<94><82> Otherwise, you should 
probably choose this option. 
â<94><82>^[[97m^[[40m ^[[31;2H^[[30m^[[47mâ<94><82> 
   
â<94><82>^[[97m^[[40m ^[[32;2H^[[30m^[[47mâ<94><82> Configure database for 
rsyslog-pgsql with dbconfig-common? 
â<94><82>^[[97m^[[40m ^[[33;2H^[[30m^[[47mâ<94><82> 
   
â<94><82>^[[97m^[[40m ^[[34;2H^[[30m^[[47mâ<94><82>   
^[[37m^[[41m^[[ 30m^[[47m  
  â<94><82>^[[97m^[[40m ^[[35;2H^[[30m^[[47mâ<94><82>   

 â<94><82>^[[97m^[[40m 
^[[36;2H^[[30m^[[47mâ<94><94>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><80>â<94><98>^[[97m^[[40m
 ^[[37;3H   
   
^[[34;31H^[[?12l^[[?25h^[[55;1H^[[37m^[(B^[[m^[[39;49m^M^[[K^M^[[?1049l^[[?1049h^[[1;55r^[[4l^[[?25l^[(B^[[m^[[37m^[[40m^[[1;55r^[[H^[[2J^[[1;1H^[[97m^[[45m^[[K
^[[K

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

Title:
  package rsyslog-pgsql 8.16.0-1ubuntu9 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  think it has something to do dkms

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: rsyslog-pgsql 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Tue Oct 31 23:36:12 2017
  ErrorMes

[Touch-packages] [Bug 1745505] Re: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Brian Murray]

[3698105.633667] frontend[30228]: segfault at 0 ip 564fab9c2fa4 sp
7ffe77529ed0 error 6 in perl[564fab93e000+1f7000]

It looks like there was a crash in perl.

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

Title:
  package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Using do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 26 12:28:07 2018
  DuplicateSignature:
   package:rsyslog:8.16.0-1ubuntu9
   Installing new version of config file /etc/init.d/rsyslog ...
   Segmentation fault
   dpkg: error processing package rsyslog (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-12-01 (55 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu9 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to artful on 2018-01-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1745505/+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 1767444] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Setting up ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1
  dpkg: dependency problems prevent configuration of 
software-properties-common:
   software-properties-common depends on ca-certificates; however:
Package ca-certificates is not configured yet.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 23:23:20 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-10 (381 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767444/+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 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Julian Andres Klode]

py3clean is only executed if which tells us it exists:

if which py3clean >/dev/null 2>&1; then
py3clean -p python3-apt 
else


hence it's quite strange.

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

Title:
  package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  Problem occurred setting the displays arrangement

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.0~rc2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1763844/+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 1767444] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Pham Quoc Hung]

Public bug reported:

Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of 
software-properties-common:
 software-properties-common depends on ca-certificates; however:
  Package ca-certificates is not configured yet.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 23:23:20 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-04-10 (381 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Setting up ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1
  dpkg: dependency problems prevent configuration of 
software-properties-common:
   software-properties-common depends on ca-certificates; however:
Package ca-certificates is not configured yet.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 23:23:20 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-04-10 (381 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767444/+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 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Chris Coleman]

It does in my system:
chris@ubuntu-quadcore:~$ ls -l /usr/bin/py3clean
-rwxr-xr-x 1 root root 7806 Apr 10 10:48 /usr/bin/py3clean

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

Title:
  package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  Problem occurred setting the displays arrangement

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-apt 1.6.0~rc2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: python-apt
  Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1763844/+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 1603183] Re: Bottom right area of touchpad no longer treated as right click

[Patrick Kilgore]

@vanvugt I think this is still a big problem lots of 16.04 -> 18.04
upgraders will run into.

This one blew my mind after installing 18.04 today.  If this is going to
be the new default, we need to warn users, because those of us not using
Apple/ChromeOS hardware *expect* clickpads to work like they have for a
decade now so it feels like an Ubuntu regression / issue.

The easier solution may be to do a little bit of hardware detection
before Ubuntu configures this one for the users, and set the relevant
hardware accordingly (Apple/ChromeOs->"fingers";
Dell/Lenovo/Etc->"areas").

Currently (18.04), the easy fix for this is to set:

$ gsettings set org.gnome.desktop.peripherals.touchpad click-method
areas

My bug 1767383 is almost certainly a dupe of this one (sorry, I was
originally searching for it against the old driver), but I'll let
someone else decide that.

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

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+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 1766794] Re: apport-collect doesn't create a ProblemType in the report

[Brian Murray]

For some reason the ProblemType is being removed from the report,
causing package hooks or the ubuntu general hook which expect it to
fail.  This'll fix the bug.

 $ bzr diff apport/ui.py
=== modified file 'apport/ui.py'
--- apport/ui.py2018-02-14 18:10:19 +
+++ apport/ui.py2018-04-27 15:55:37 +
@@ -559,7 +559,6 @@
 self.add_extra_tags()
 
 # delete the uninteresting keys
-del self.report['ProblemType']
 del self.report['Date']
 try:
 del self.report['SourcePackage']

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

Title:
  apport-collect doesn't create a ProblemType in the report

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1766794/+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 1767407] [NEW] package software-properties-common 0.96.24.32.1 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit

[Mirwais Shah Arya]

Public bug reported:

I don't know how it happened

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: software-properties-common 0.96.24.32.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 14:03:01 2018
ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: software-properties
Title: package software-properties-common 0.96.24.32.1 failed to 
install/upgrade: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

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


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

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

Title:
  package software-properties-common 0.96.24.32.1 failed to
  install/upgrade: new software-properties-common package pre-removal
  script subprocess returned error exit status 126

Status in software-properties package in Ubuntu:
  New

Bug description:
  I don't know how it happened

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 14:03:01 2018
  ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.32.1 failed to 
install/upgrade: new software-properties-common package pre-removal script 
subprocess returned error exit status 126
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1767407/+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 1766794] Re: apport-collect doesn't create a ProblemType in the report

[Brian Murray]

** Also affects: apport (Ubuntu Bionic)
   Importance: High
   Status: Triaged

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

Title:
  apport-collect doesn't create a ProblemType in the report

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

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

[Eric Desrochers]

or possibly add After=network.target or something around those line.

-- 
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 in Bionic

Status in friendly-recovery package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug 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 1184387] Re: while playing video computer becomes unresponsive

[Launchpad Bug Tracker]

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

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

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

Title:
  while playing video computer becomes unresponsive

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When I was playing a flash video the screen froze and the audio continued a 
bit and then stopped for a minute or so and then started for a few seconds 
again. I was able to ssh into my laptop and save the logs. Syslog said:
  pulseaudio[2242]: [alsa-sink] alsa-util.c: snd_pcm_avail() returned a value 
that is exceptionally large: 591416 bytes (3352 ms).
  pulseaudio[2242]: [alsa-sink] alsa-util.c: Most likely this is a bug in the 
ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
  so I did. The full logs are attached. This bug happens often but I can't 
reliably reproduce it and it seems very random.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1184387/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Jean-Philippe Vignolo]

Having more or less the same bug as anybody here, but with final Bionic
18.04.

I tried what proposed on #29 and #47 => installing from ppa :
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa without
success (either 390 or 396 version of drivers) without success

Tried also installing lightdm instead of gdm3 which just get me a dark
screen.

Reverted back to Nouveau drivers doing what Ivan did in #78, I managed
to do a startx and get into gnome desktop. Then I rebooted, and gdm3 was
just fine and managed to login.

But after another reboot I could just access to gdm3 but system seemed
hangs after login (fixed cursor in middle of a dark screen). If I play
with alt+ctrl+f1 , f2 It turns back to gdm3 login screen. alt+ctrl+f3
gets me to a standard text login.

I managed to properly boot again after doing a sudo dpkg-reconfigure
gdm3 but it worked only once.

Finally, out of desperation, I did another sudo apt-get install nvidia-
driver-396 and now everything is working :) Go figure...

My guess is that removing the old xorg.conf file did the trick for me

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

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 1766794] Re: apport-collect with debian-installer doesn't create a ProblemType in the report

[Brian Murray]

I was able to recreate this by running apport-collect on bug 1766787 and
it crashed whether I choose to view the report or keep it. The same
thing happens with a ubiquity bug report too.  However, when running
apport-collect on an apport bug report a report is created without a
ProblemType it just is not checked for anything so the process doesn't
crash.

Anyway, this pretty seriously impacts the usability of apport-collect.


** Summary changed:

- apport-collect with debian-installer doesn't create a ProblemType in the 
report
+ apport-collect doesn't create a ProblemType in the report

** Changed in: apport
   Status: New => Triaged

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

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

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

Title:
  apport-collect doesn't create a ProblemType in the report

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1766794/+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 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

[Thomas Friedrichsmeier]

Same symptoms(*) here after a fresh upgrade to 18.04.

Tried installing gdm, as suggested above, and also adding "xrandr" as
suggested, here: https://forums.fedoraforum.org/showthread.php?316354
-SDDM-shows-black-screen-with-Nvidia . Neither made a difference for me.

However, the problem finally went away after switching to the nouveau
driver. (And I have no recollection of ever asking for the proprietary
nvidia driver, specifically, but I may be wrong about that.)

(*) Symptoms: sddm, but also lightdm and gdm3 showing only black. startx
brings up an xfce session without problems.

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+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 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

[Launchpad Bug Tracker]

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

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

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+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 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

[Launchpad Bug Tracker]

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

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

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+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 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

[Launchpad Bug Tracker]

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

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

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

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

[Eric Desrochers]

So all the remaining jobs are basically waiting for friendly-recovery to
exit to start due to the "oneshot" instruction, which make xnox patch
(revno 152) not working.

Some waiting jobs are units in which the desired network services in revno 152 
depends on.
I totally understand why "oneshot" is set, but in this case it is the blocker.

If we remove "oneshot" then everything will start and make the recovery mode 
useless. 
So I think "oneshot" need to stay there.

The only thing then I can think of atm is to add --job-mode=ignore-
dependencies --no-ask-password and possibly extra stuff in frienly-
recovery.service to make the necessary network services to start in
recovery mode when requesting 'Enable Network'.

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

-- 
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 in Bionic

Status in friendly-recovery package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug 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 1767375] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1767375

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  This happened while doing software upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Apr 27 10:34:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1767375/+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 1767375] [NEW] package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[lukaka]

Public bug reported:

This happened while doing software upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Fri Apr 27 10:34:42 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-04-26 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  This happened while doing software upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Apr 27 10:34:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Eric Desrochers]

By reading more about systemd, I start to think the blocker here to
start the desired services is "Type=oneshot" instruction in friendly-
recovery.service.

"
Behavior of oneshot is similar to simple; however, it is expected that the 
process has to exit before systemd starts follow-up units.
"

Need to explore more that route.

-- 
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 in Bionic

Status in friendly-recovery package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug 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 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()

[Bearsh]

here we go...

** Attachment added: "output of dpkg -l"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+attachment/5128438/+files/dpkg-l.txt

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+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 1742156] Re: network-manager wired DHCP mode doesn't work on Ubuntu 18.04

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  network-manager wired DHCP mode doesn't work on Ubuntu 18.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  In virtualbox with NAT configured (10.0.2.2 as defaul DHCP IP),
  network-manager on ubuntu 18.04 cannot find any wired interface and
  also cannot connect to network via DHCP.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager (not installed)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jan  9 21:44:54 2018
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1742156/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Simone Scisciani]

** Changed in: casper (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1767342] [NEW] Dosplay scale factor reset after changing screen size or reboot

[Viacheslav Kaloshin]

Public bug reported:

Steps to reproduce

1. Take computer with HiDPI monitor
2. Install bionic in VM, install open-vm-tools && open-vm-tools-desktop and 
enable hi-dpi
3. Settings-Devices-Display-Scale to 200% and press apply
4. Drag VM window corner for changing VM screen size or simple reboot VM.

Scale resets to 100%

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Unity
Date: Fri Apr 27 14:20:34 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=203b7377-6f0c-4d39-a33f-db18baece74c ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
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 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

** 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/1767342

Title:
  Dosplay scale factor reset after changing screen size or reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. Take computer with HiDPI monitor
  2. Install bionic in VM, install open-vm-tools && open-vm-tools-desktop and 
enable hi-dpi
  3. Settings-Devices-Display-Scale to 200% and press apply
  4. Drag VM window corner for changing VM screen size or simple reboot VM.

  Scale resets to 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Fri Apr 27 14:20:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=203b7377-6f0c-4d39-a33f-db18baece74c ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product

[Touch-packages] [Bug 1767336] [NEW] package ca-certificates 20180409 failed to install/upgrade: gatilhos em "loop", abandonado

[Carlos Alberto Neri]

Public bug reported:

i dont know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 08:02:11 2018
ErrorMessage: gatilhos em "loop", abandonado
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: gatilhos em 
"loop", abandonado
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: gatilhos
  em "loop", abandonado

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 08:02:11 2018
  ErrorMessage: gatilhos em "loop", abandonado
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: gatilhos 
em "loop", abandonado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767336/+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 1767331] [NEW] package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Carlos Alberto Neri]

Public bug reported:

i dont know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: uuid-runtime 2.31.1-0.4ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
Date: Fri Apr 27 07:46:33 2018
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: util-linux
Title: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in util-linux package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: uuid-runtime 2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 27 07:46:33 2018
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1767331/+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 1762984] Re: DNS resolving not working due to wrong entry in resolv.conf

[thet]

Nope. Still an issue.

** Changed in: network-manager (Ubuntu)
   Status: Invalid => New

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

Title:
  DNS resolving not working due to wrong entry in resolv.conf

Status in network-manager package in Ubuntu:
  New

Bug description:
  In my ``/etc/resolv.conf`` I have the entry:

  ```
  nameserver 127.0.0.53
  ```

  I'm connected to the network via WIFI.
  My IP is ``192.168.0.31``

  The network-manager applet shows me automatic DNS configuration and a DNS 
server of 192.0.0.1, which is correct.
  Changing DNS configuration in the network-manager applet to manual and 
editing it there doesn't work either.

  I have to edit the resolv.conf file in order to get DNS resolving
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 11:51:58 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  wifi  1523440039  Mi 11 
Apr 2018 11:47:19 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp1s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   welanseppaf2f9fd1-2a81-4e2c-95e5-3f4e9a9997b9  wifi  1523402504  Mi 11 
Apr 2018 01:21:44 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1762984/+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 1767322] [NEW] "Activation of network connection failed" popup shows incessantly

[Jacob Zimmermann]

Public bug reported:

All network connections work normally, however the popup "Activation of
network connection failed" keeps showing.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 20:04:56 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-04-03 (24 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 
 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug bionic third-party-packages wayland-session

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1767322/+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 1767321] [NEW] Xorg freeze

[Jacob Zimmermann]

Public bug reported:

In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random
intervals. When it resumes, gnome shell's dock flickers as if the
problem was caused by it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 20:02:51 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079]
 Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
InstallationDate: Installed on 2018-04-03 (24 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
MachineType: HP HP EliteBook 850 G3
ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 
radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2016
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.10
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.6F
dmi.chassis.asset.tag: 5CG6351LQL
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 850 G3
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
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 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

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze third-party-packages 
ubuntu wayland-session

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random
  intervals. When it resumes, gnome shell's dock flickers as if the
  problem was caused by it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:02:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 
radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Vöggur Guðmundsson]

Now that 18.04 out now, can we have new build of the packet?

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1762984] Re: DNS resolving not working due to wrong entry in resolv.conf

[thet]

Works now.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  DNS resolving not working due to wrong entry in resolv.conf

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  In my ``/etc/resolv.conf`` I have the entry:

  ```
  nameserver 127.0.0.53
  ```

  I'm connected to the network via WIFI.
  My IP is ``192.168.0.31``

  The network-manager applet shows me automatic DNS configuration and a DNS 
server of 192.0.0.1, which is correct.
  Changing DNS configuration in the network-manager applet to manual and 
editing it there doesn't work either.

  I have to edit the resolv.conf file in order to get DNS resolving
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 11:51:58 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  wifi  1523440039  Mi 11 
Apr 2018 11:47:19 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp1s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   welanseppaf2f9fd1-2a81-4e2c-95e5-3f4e9a9997b9  wifi  1523402504  Mi 11 
Apr 2018 01:21:44 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
NSACIAGCHQ5  f8431fbb-6f3c-4848-bcc4-4449012df3f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1762984/+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 459730] Re: rsyslog doesn't create /dev/xconsole

[Andrey--k]

k--andrey@kandrey:/tmp$ cat /etc/issue
Ubuntu 16.04.4 LTS \n \l

k--andrey@kandrey:/tmp$ uname -a
Linux kandrey.kitsoft.kiev.ua 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 
14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Apr 27 12:12:41 kandrey rsyslogd-2039: Could not open output pipe
'/dev/xconsole':: No such file or directory [v8.16.0 try
http://www.rsyslog.com/e/2039 ]

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

Title:
  rsyslog doesn't create /dev/xconsole

Status in One Hundred Papercuts:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  Looks like this was missed in the move to upstart.

  This function was called in init.d/rsyslog start:

  create_xconsole() {
  if [ ! -e /dev/xconsole ]
  then
  mknod -m 640 /dev/xconsole p
  chown root:adm /dev/xconsole
  [ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
  fi
  }

  I can't find any reference to it now. If this is old school then it should be 
re
  moved from the config.

  rsyslog:
Installed: 4.2.0-2ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+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 1767314] [NEW] Ubuntu Bionic vi/vim not working correctly

[Roel Van de Paar]

Public bug reported:

The vim default configuration in Bionic does not match Ubuntu 17.10 nor
Centos 7 and is hard to use. It auto-inserts tabs or spaces, and the '/'
search mode command works differently (pressing enter is required before
you can use cursors left/right).

For some discussion, please see https://askubuntu.com/questions/1026820
/vi-vim-usage-in-ubuntu-bionic-not-normal/1028684#1028684

Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
required.

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


** Tags: bionic vi vim

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  New

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+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 1767283] Re: nc doesn't support "-s IP" option

[Bug Watch Updater]

** Changed in: netcat-openbsd (Debian)
   Status: Unknown => New

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed
Status in netcat-openbsd package in Debian:
  New

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1763111] Re: autokey starting maximized (not in system tray)

[Duns]

Seems that the problem is "autokey-gtk -c" command: instead works
correctly "autokey" command.

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

Title:
  autokey starting maximized (not in system tray)

Status in xorg package in Ubuntu:
  New

Bug description:
  It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window,
  not, as expected (and as in Kubuntu 17.10) as system tray icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763111/+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 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()

[Daniel van Vugt]

In that case please also send us your package listing (dpkg -l).

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

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+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 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

[Daniel van Vugt]

If the problem is caused by pulseaudio 1:8.0-0ubuntu3.9 then please try
installing packages from the previous version:

https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.8/+build/14353783

And tell us if that resolves the issue.

** Summary changed:

- pulseaudio+bluetooth crash causing user to be logged out
+ pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 
1:8.0-0ubuntu3.9)

** Tags added: regression-update

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

Title:
  pulseaudio+bluetooth crash causing user to be logged out (since
  pulseaudio 1:8.0-0ubuntu3.9)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ChristianEhrhardt]

Debian bug at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020

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

** Also affects: netcat-openbsd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020
   Importance: Unknown
   Status: Unknown

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed
Status in netcat-openbsd package in Debian:
  Unknown

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1767299] [NEW] Ubuntu 18.04 Installer creates swap partition too small

[Johon Doee]

Public bug reported:

Installed Ubuntu 18.04 final release.

The disk is 512 Gigabyte, the RAM is 8 Gigabyte. The installer just gave
me 979 Megabyte of space. I chose LVM to have an encrypted drive.

Here are some details:

free -h
  totalusedfree  shared  buff/cache   available
Mem:   7,7G4,0G152M399M3,6G3,0G
Swap:  979M  0B979M


swapon --show
NAME  TYPE  SIZE USED PRIO
/dev/dm-2 partition 980M   0B   -2


cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
/dev/mapper/ubuntu--vg-root /   ext4errors=remount-ro 0   1
# /boot was on /dev/sda2 during installation
UUID=removed-id /boot   ext4defaults0   2
# /boot/efi was on /dev/sda1 during installation
UUID=removed-id  /boot/efi   vfatumask=0077  0   1
/dev/mapper/ubuntu--vg-swap_1 noneswapsw  0   0

** Affects: partman-auto (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: sudo (Ubuntu) => partman (Ubuntu)

** Package changed: partman (Ubuntu) => partman-auto (Ubuntu)

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

Title:
  Ubuntu 18.04 Installer creates swap partition too small

Status in partman-auto package in Ubuntu:
  New

Bug description:
  Installed Ubuntu 18.04 final release.

  The disk is 512 Gigabyte, the RAM is 8 Gigabyte. The installer just
  gave me 979 Megabyte of space. I chose LVM to have an encrypted drive.

  Here are some details:

  free -h
totalusedfree  shared  buff/cache   
available
  Mem:   7,7G4,0G152M399M3,6G
3,0G
  Swap:  979M  0B979M


  swapon --show
  NAME  TYPE  SIZE USED PRIO
  /dev/dm-2 partition 980M   0B   -2

  
  cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  #
  /dev/mapper/ubuntu--vg-root /   ext4errors=remount-ro 0   
1
  # /boot was on /dev/sda2 during installation
  UUID=removed-id /boot   ext4defaults0   2
  # /boot/efi was on /dev/sda1 during installation
  UUID=removed-id  /boot/efi   vfatumask=0077  0   1
  /dev/mapper/ubuntu--vg-swap_1 noneswapsw  0   0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+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 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()

[Bearsh]

and with the workaround from bug 994921, it refuses to report the bug
because it's not an official kde package (well for sure it is not...)
and I have to remove some third party packages...

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+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 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed

[Johon Doee]

This happens with the final release 18.04 as well.

Is there a temporary solution or some progress in fixing that
regression?

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  I experience a bug after upgrading from Ubuntu 17.10 to 18.04.

  The bug seems to be a regression because what I am trying to do was
  working with Ubuntu 17.10 and stopped working after the upgrade.

  Here is the problem:

  I have 2 users on my system. One is the user that is created during
  installation, named zzz. The other user I added later, named abc. Both
  users have passwords set. According to passwd the password for user
  abc is a locked password (L) (whatever that means).

  Now I am logged into user zzz and want to execute a program as user
  abc without entering the password of user abc.

  Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java 
-version".
  To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: 
/usr/bin/java"

  Now this seems to be ignored. Instead the terminal is asking for the
  password of user abc. I see this in /var/log/auth.log: "sudo:
  pam_unix(sudo:auth): conversation failed".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1766325/+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 1767283] Re: nc doesn't support "-s IP" option

[ChristianEhrhardt]

I'm not an expert on netcat but I hope this initial triage helps the
next that will look at it.

I reported to Debian as well as they are also affected.
Especially since the change came from Guilhem - it might be best to think about 
a solution together.

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed
Status in netcat-openbsd package in Debian:
  Unknown

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1766325] Re: sudo: pam_unix(sudo:auth): conversation failed

[Launchpad Bug Tracker]

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

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

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

Title:
  sudo: pam_unix(sudo:auth): conversation failed

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  I experience a bug after upgrading from Ubuntu 17.10 to 18.04.

  The bug seems to be a regression because what I am trying to do was
  working with Ubuntu 17.10 and stopped working after the upgrade.

  Here is the problem:

  I have 2 users on my system. One is the user that is created during
  installation, named zzz. The other user I added later, named abc. Both
  users have passwords set. According to passwd the password for user
  abc is a locked password (L) (whatever that means).

  Now I am logged into user zzz and want to execute a program as user
  abc without entering the password of user abc.

  Until Ubuntu 17.10 this was done like this: "sudo -i -u abc /usr/bin/java 
-version".
  To get that working I had to add this via visudo: "zzz ALL=(abc) NOPASSWD: 
/usr/bin/java"

  Now this seems to be ignored. Instead the terminal is asking for the
  password of user abc. I see this in /var/log/auth.log: "sudo:
  pam_unix(sudo:auth): conversation failed".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1766325/+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 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()

[Daniel van Vugt]

That would be because you failed to apply a workaround for bug 994921.
It might require some tweaking :/

But lucky for you we did get enough info from the crash file:

Stacktrace:
 #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
 agent = 
 #1  0x55922049561b in adapter_register (adapter=0x559220a77c20) at 
src/adapter.c:7434
 agent = 
 db = 
 #2  read_info_complete (status=, length=, 
param=, user_data=0x559220a77c20) at src/adapter.c:7897
 adapter = 0x559220a77c20
 rp = 
 missing_settings = 
 __func__ = "read_info_complete"
 #3  0x5592204bf656 in request_complete (mgmt=mgmt@entry=0x559220a71d90, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x559220a72d29) at src/shared/mgmt.c:261
 match = {opcode = 4, index = 0}
 request = 0x559220a72fb0
 #4  0x5592204c011c in can_read_data (io=, 
user_data=0x559220a71d90) at src/shared/mgmt.c:353
 hdr = 
 cc = 0x559220a72d26
 cs = 
 opcode = 4
 event = 
 index = 
 length = 283
 #5  0x5592204cbe25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
 watch = 
 result = 
 destroy = 
 #6  0x7f310746b04a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #7  0x7f310746b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #8  0x7f310746b712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #9  0x55922042d09d in main (argc=1, argv=0x7ffe83a0edb8) at src/main.c:687
 context = 
 err = 0x0
 sdp_flags = 
 gdbus_flags = 
 watchdog = 0
 watchdog_usec = 
 __func__ = "main"
StacktraceAddressSignature: 
/usr/lib/bluetooth/bluetoothd:4:/usr/lib/bluetooth/bluetoothd+8461b:/usr/lib/bluetooth/bluetoothd+ae656:/usr/lib/bluetooth/bluetoothd+af11c:/usr/lib/bluetooth/bluetoothd+bae25:/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2+4a04a:/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2+4a3f0:/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2+4a712:/usr/lib/bluetooth/bluetoothd+1c09d
StacktraceTop:
 agent_get (owner=owner@entry=0x0) at src/agent.c:267
 adapter_register (adapter=0x559220a77c20) at src/adapter.c:7434
 read_info_complete (status=, length=, 
param=, user_data=0x559220a77c20) at src/adapter.c:7897
 request_complete (mgmt=mgmt@entry=0x559220a71d90, status=, 
opcode=opcode@entry=4, index=index@entry=0, length=length@entry=280, 
param=0x559220a72d29) at src/shared/mgmt.c:261
 can_read_data (io=, user_data=0x559220a71d90) at 
src/shared/mgmt.c:353
Tags: xenial third-party-packages
ThreadStacktrace:
 .
 Thread 1 (Thread 0x7f3107894880 (LWP 23334)):
 #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
 agent = 
 #1  0x55922049561b in adapter_register (adapter=0x559220a77c20) at 
src/adapter.c:7434
 agent = 
 db = 
 #2  read_info_complete (status=, length=, 
param=, user_data=0x559220a77c20) at src/adapter.c:7897
 adapter = 0x559220a77c20
 rp = 
 missing_settings = 
 __func__ = "read_info_complete"
 #3  0x5592204bf656 in request_complete (mgmt=mgmt@entry=0x559220a71d90, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x559220a72d29) at src/shared/mgmt.c:261
 match = {opcode = 4, index = 0}
 request = 0x559220a72fb0
 #4  0x5592204c011c in can_read_data (io=, 
user_data=0x559220a71d90) at src/shared/mgmt.c:353
 hdr = 
 cc = 0x559220a72d26
 cs = 
 opcode = 4
 event = 
 index = 
 length = 283
 #5  0x5592204cbe25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
 watch = 
 result = 
 destroy = 
 #6  0x7f310746b04a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #7  0x7f310746b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #8  0x7f310746b712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #9  0x55922042d09d in main (argc=1, argv=0x7ffe83a0edb8) at src/main.c:687
 context = 
 err = 0x0
 sdp_flags = 
 gdbus_flags = 
 watchdog = 0
 watchdog_usec = 
 __func__ = "main"

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

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  New

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.serv

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ChristianEhrhardt]

In gdb I see it gets to read -s

case 's':
sflag = optarg;
break;

It realizes no more options are there and then ends at
} else if (argv[0] && argv[1]) {
host = argv[0];
uport = &argv[1];
if (pflag || sflag)
usage(1);

And sflag is set, so it reports usage and exits.
The particular check in this path of pflag/sflag didn't exist back then.

I found this comes in via a patch
  debian/patches/misc-failures-and-features.patch
That was in Debian and Ubuntu since late 2016

This patch was modified by:
commit 2ebffb014c830e49f6fad600c59cc1b82fe356a4
Author: Guilhem Moulin 
Date:   Sun Dec 3 22:58:11 2017 +0100

Allow usage of -s with -l for consistency with netcat-traditional.

Since then this is also in Debian.

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1767292] [NEW] The bluetooth mouse cannot connect after sleep mode.

[Giacomo Trimarchi]

Public bug reported:

The bluetooth mouse cannot connect after sleep mode.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  giacomo1998 F pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Fri Apr 27 09:49:41 2018
InstallationDate: Installed on 2017-04-13 (378 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago)
dmi.bios.date: 07/27/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R08ET43W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FU001PMC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L460
dmi.product.name: 20FU001PMC
dmi.product.version: ThinkPad L460
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  The bluetooth mouse cannot connect after sleep mode.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The bluetooth mouse cannot connect after sleep mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giacomo1998 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Apr 27 09:49:41 2018
  InstallationDate: Installed on 2017-04-13 (378 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago)
  dmi.bios.date: 07/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU001PMC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L460
  dmi.product.name: 20FU001PMC
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1767292/+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 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()

[Bearsh]

for whatever reason 'ubuntu-bug /var/crash/YOURFILE.crash' doesn't provide an 
URL or open a browser window :(
I'll attache the .cash file here

** Attachment added: "_usr_lib_bluetooth_bluetoothd.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+attachment/5128211/+files/_usr_lib_bluetooth_bluetoothd.0.crash

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

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

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

[Andrei Hornoiu]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128204/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon runn

[Touch-packages] [Bug 1767065] Dependencies.txt

[Andrei Hornoiu]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128202/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon ru

[Touch-packages] [Bug 1767065] AlsaInfo.txt

[Andrei Hornoiu]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128200/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, o

[Touch-packages] [Bug 1767065] Dependencies.txt

[Andrei Hornoiu]

apport information

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

** Description changed:

  Hello,
  
  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can tell
  from the journalctl printout this appears immediately after either
  bluetoothd or pulsaudio crashes.
  
  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent by
  the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.
  
  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  
  We are running Ubuntu 16.04 LTS with the latest updated.
  
  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.16
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: pulseaudio 1:8.0-0ubuntu3.9
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ Tags:  xenial
+ Uname: Linux 4.13.0-39-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/07/2018
+ dmi.bios.ve

[Touch-packages] [Bug 1767065] CurrentDmesg.txt

[Andrei Hornoiu]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128201/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon ru

[Touch-packages] [Bug 1767065] CurrentDmesg.txt

[Andrei Hornoiu]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128198/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon ru

[Touch-packages] [Bug 1767065] ProcCpuinfoMinimal.txt

[Andrei Hornoiu]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128203/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAud

[Touch-packages] [Bug 1767065] AlsaInfo.txt

[Andrei Hornoiu]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1767065/+attachment/5128197/+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/1767065

Title:
  pulseaudio+bluetooth crash causing user to be logged out

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, o

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ChristianEhrhardt]

Even the example from the manpage fails:
$ nc -s 10.1.2.3 host.example.com 42

** Changed in: netcat-openbsd (Ubuntu)
   Status: New => Confirmed

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out

[Andrei Hornoiu]

Another update. After truning off pulseaudio yesterday, the system
didn't crash as fast as before, but it did eventually lock up a couple
of times. The logs seems similar even without pulse, still beginning
with the bluetooth service.

After this I completely turned off bluetooth from the BIOS of the
machine. This seemed to have solved the issue until a few moments ago
when the bluetoothservice tried to start something again. I have now
disabled the bluetooth service. I hope it doesn't do anything more.

Here's how the system locks-up now:

Apr 27 09:37:26 ESS-PC26 dbus[1187]: [system] Failed to activate service 
'org.bluez': timed out
Apr 27 09:37:26 ESS-PC26 pulseaudio[2214]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out
Apr 27 09:37:26 ESS-PC26 pulseaudio[1521]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out

The system freezes for multiple seconds then recovers.

I've now run apport-collect and authorized it for one week. Hope this
helps.

** Tags added: apport-collected

** Description changed:

  Hello,
  
  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can tell
  from the journalctl printout this appears immediately after either
  bluetoothd or pulsaudio crashes.
  
  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent by
  the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.
  
  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  
  We are running Ubuntu 16.04 LTS with the latest updated.
  
- EDIT: Worth mentioning, this error happens with both Unity and Gnome as
- desktop environments.
+ EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.16
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: pulseaudio 1:8.0-0ubuntu3.9
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ Tags:  xenial
+ Uname: Linux 4.13.0-39-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/07/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1301
+ dmi.board.asset.tag: Default string
+ dmi.board.name: PRIME X299-DELUXE
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

-- 
You received this bug notification because you are 

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

[ChristianEhrhardt]

-t in description (typo) mislead me - fixed the description

** Description changed:

  Hey,
  
- netcat shows a usage error if i try to use the "-t" option:
+ netcat shows a usage error if i try to use the "-s" option:
  
  Example in Bionic:
  
- $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null 
+ $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
- [-m minttl] [-O length] [-P proxy_username] [-p source_port]
- [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
- [-X proxy_protocol] [-x proxy_address[:port]]   [destination] 
[port]
- 
+    [-m minttl] [-O length] [-P proxy_username] [-p source_port]
+    [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
+    [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]
  
  Example in Xenial:
  
- netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null 
+ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4
  
- 
- Manpage shows that the option is still availible and should work. Both 
systems use openbsd netcat.
+ Manpage shows that the option is still availible and should work. Both
+ systems use openbsd netcat.
  
  $ type netcat
  netcat is hashed (/bin/netcat)
- $ ls -lah /bin/netcat 
+ $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
-  gcc-8-base 8-20180414-1ubuntu2
-  libbsd0 0.8.7-1
-  libc6 2.27-3ubuntu1
-  libgcc1 1:8-20180414-1ubuntu2
+  gcc-8-base 8-20180414-1ubuntu2
+  libbsd0 0.8.7-1
+  libc6 2.27-3ubuntu1
+  libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+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 1763111] Re: autokey starting maximized (not in system tray)

[Duns]

And this is the warning message in terminal:

duns@sar-intel1:~$ autokey-gtk -c
/usr/lib/python2.7/dist-packages/autokey/gtkapp.py:24: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib
/usr/lib/python2.7/dist-packages/autokey/gtkui/notifier.py:19: PyGIWarning: 
Notify was imported without specifying a version first. Use 
gi.require_version('Notify', '0.7') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gtk, Gdk, Notify
/usr/lib/python2.7/dist-packages/autokey/gtkui/configwindow.py:20: PyGIWarning: 
GtkSource was imported without specifying a version first. Use 
gi.require_version('GtkSource', '3.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gtk, Pango, GtkSource, Gdk, Gio

duns@sar-intel1:~$ autokey
/usr/lib/python2.7/dist-packages/autokey/gtkapp.py:24: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib
/usr/lib/python2.7/dist-packages/autokey/gtkui/notifier.py:19: PyGIWarning: 
Notify was imported without specifying a version first. Use 
gi.require_version('Notify', '0.7') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gtk, Gdk, Notify
/usr/lib/python2.7/dist-packages/autokey/gtkui/configwindow.py:20: PyGIWarning: 
GtkSource was imported without specifying a version first. Use 
gi.require_version('GtkSource', '3.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gtk, Pango, GtkSource, Gdk, Gio

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

Title:
  autokey starting maximized (not in system tray)

Status in xorg package in Ubuntu:
  New

Bug description:
  It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window,
  not, as expected (and as in Kubuntu 17.10) as system tray icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763111/+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 1763111] Re: autokey starting maximized (not in system tray)

[Duns]

No! Solved once yes and once not. This is the .desktop:

[Desktop Entry]
Categories=GNOME;GTK;Utility;
Comment[en_US]=Program keyboard shortcuts
Comment=Program keyboard shortcuts
Exec=autokey-gtk -c
GenericName[en_US]=Keyboard Automation
GenericName=Keyboard Automation
Icon=autokey
MimeType=
Name[en_US]=AutoKey
Name=AutoKey
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=

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

Title:
  autokey starting maximized (not in system tray)

Status in xorg package in Ubuntu:
  New

Bug description:
  It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window,
  not, as expected (and as in Kubuntu 17.10) as system tray icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763111/+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 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'

[Paula Thomas]

I got this error in upgrading to xubuntu 18.04! Do I need to do anything
about it?

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

Title:
  GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib
  /gdk-pixbuf-2.0/2.10.0/loaders.cache'

Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Debian:
  Invalid

Bug description:
  During installation of updated version of libgdk-pixbuf2.0-0 on August
  10th 2010, the apt term.log contained multiple (>300) copies of the
  following warning:

  (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf
  loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No
  such file or directory

  Nevertheless, the file complained about exists, and is readable in
  gedit.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
  Uname: Linux 2.6.35-15-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Mon Aug 16 18:13:29 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdk-pixbuf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+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 1749728] Re: GDebi doesn't handle Firefox "open with"

[Jani Uusitalo]

** Description changed:

-  GDebi doesn't handle Firefox "open with" option instead of "save file".
- It will open GDebi but when presing to install the pachage it will close.
+ When launched from Firefox with the "open with" function, GDebi is
+ unable to complete installing the package. The GDebi window does open,
+ but after selecting to "install" the package the window closes and the
+ package is left uninstalled.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 15 17:08:31 2018
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180215)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- GDebi doesn't handle Firefox "open with"
+ Installing packages fails when launched via Firefox ("open with")

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

Title:
  Installing packages fails when launched via Firefox ("open with")

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When launched from Firefox with the "open with" function, GDebi is
  unable to complete installing the package. The GDebi window does open,
  but after selecting to "install" the package the window closes and the
  package is left uninstalled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 15 17:08:31 2018
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180215)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1749728/+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 1767283] [NEW] nc doesn't support "-s IP" option

[Stefan Schwarz]

Public bug reported:

Hey,

netcat shows a usage error if i try to use the "-t" option:

Example in Bionic:

$ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null 
usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
  [-m minttl] [-O length] [-P proxy_username] [-p source_port]
  [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
  [-X proxy_protocol] [-x proxy_address[:port]]   [destination] 
[port]


Example in Xenial:

netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null 
SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4


Manpage shows that the option is still availible and should work. Both systems 
use openbsd netcat.

$ type netcat
netcat is hashed (/bin/netcat)
$ ls -lah /bin/netcat 
lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
$ ls -lah /etc/alternatives/netcat
lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netcat-openbsd 1.187-1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 13:41:20 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libbsd0 0.8.7-1
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: netcat-openbsd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: netcat-openbsd (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 netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1767283

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-t" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null 
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
  [-m minttl] [-O length] [-P proxy_username] [-p source_port]
  [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
  [-X proxy_protocol] [-x proxy_address[:port]]   [destination] 
[port]

  
  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null 
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  
  Manpage shows that the option is still availible and should work. Both 
systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat 
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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