date:20180504

How to check you have this issue:

1) get provided resume script, replace 
/usr/share/initramfs-tools/scripts/local-premount/resume with it
2) sudo update-initramfs -k $(uname -r) -u
3) sudo systemctl hibernate
4) edit grub menu entry, add 'debug' parameter to kernel command line, boot
5) look into /run/initramfs/initramfs.debug, if you see following lines, you 
have this issue:
+ /scripts/local-premount/resume
Success: Resume device: 'UUID=106238b0-707d-4422-866d-a7534da50702' ()
Failure: Failed to get /sys/class/block//dev major/minor


** Attachment added: "resume script with extra debug messages"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+attachment/5134182/+files/resume

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 1769297] Re: resume from hibernation broken when resume image is autodetected

This bug is actually a regression. I remember hibernation was functional
around a year ago in ubuntu 17.04 with any kernel, but at some point it
became broken. Probably in 17.10.

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 1769297] Re: resume from hibernation broken when resume image is autodetected

Here is a fix for this bug. This makes hibernation functional for me.

** Patch added: "init.patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+attachment/5134187/+files/init.patch

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 1769297] [NEW] resume from hibernation broken when resume image is autodetected

Public bug reported:

I found a reason of non-functioning resume from hibernation when resume
partition/file is autodetected by intiramfs hook /usr/share/initramfs-
tools/hooks/resume.

Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

2) during boot init script sets 'resume' variable to 'RESUME' value from
conf/conf.d/zz-resume-auto, then it executes local-premount scripts
including local-premount/resume

3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
DEV=$(readlink ${resume})
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read MAJMIN < "$DEV"
fi

4) next check fails and resume process silently aborts:
if [ -z "$MAJMIN" ]; then
exit 1
fi

Resuming script fails to get device major-minor because
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
into device path in init script.

Commonly mentioned workaround is to explicitly specify kernel parameter
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in this case
init script resolves it to device path.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
Uname: Linux 4.16.6-041606-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 11:32:31 2018
InstallationDate: Installed on 2018-03-27 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Description changed:

  I found a reason of non-functioning resume from hibernation when resume
  partition/file is autodetected by intiramfs hook /usr/share/initramfs-
  tools/hooks/resume.
  
  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
  
- 2) when resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
+ 2) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
- read MAJMIN < "$DEV"
+ read MAJMIN < "$DEV"
  fi
  
- 3) then next check fails and resume process silently aborts:
+ 3) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
- exit 1
+ exit 1
  fi
  
- 
- Resuming script fails to get device major-minor because 
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved into 
device path in init script.
+ Resuming script fails to get device major-minor because
+ resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
+ into device path in init script.
  
  Commonly mentioned workaround is to explicitly specify kernel parameter
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in this case
  init script resolves it to device path.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  I found a reason of non-functioning resume from hibernation when resume
  partition/file is autodetected by intiramfs hook /usr/share/initramfs-
  tools/hooks/resume.
  
  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
  
- 2) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
+ 2) during boot init script sets 'resume' variable to 'RESUME' value from
+ conf/conf.d/zz-resume-auto, then it executes local-premount scripts
+ including local-premount/resume
+ 
+ 3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor

[Touch-packages] [Bug 1702495] Re: touchpad too sensitive

[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/1702495

Title:
  touchpad too sensitive

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The mouse cursor moves even when i move my fingers over the touchpad
  in the air(without touching it) but doesnt move at all when i use the
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  5 20:00:11 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  InstallationDate: Installed on 2017-06-27 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Hewlett-Packard HP 450 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=159622e6-6a00-43f4-baad-7b2d60cb8bd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3C
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG347B4F2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3C:bd10/11/2013:svnHewlett-Packard:pnHP450NotebookPC:pvr088612005B1600010:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 450 Notebook PC
  dmi.product.version: 088612005B1600010
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jul  5 19:48:09 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702495/+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 1753298] Re: audio not working, apollo lake 4.16 kernel

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

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 1753298] Re: audio not working, apollo lake 4.16 kernel

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

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753298/+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 183447] Re: rhythmbox should understand .wpl playlists (SMIL format)

2018-05-04 Thread Bug Watch Updater

** Changed in: gstreamer
   Status: Confirmed => Invalid

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

Title:
  rhythmbox should understand .wpl playlists (SMIL format)

Status in GStreamer:
  Invalid
Status in gstreamer0.10 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  Currently, rhythmbox fails to import Windows Media Player .wpl
  playlist files.  It reports the error "The GStreamer plugins to decode
  "SMIL document" files cannot be found.

  Rhythmbox should support this format.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/183447/+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 1769284] Re: ssh client: blowfish-cbc required - missing in bionic

2018-05-04 Thread Jens Elkner

No, this is not an option. Also note, that this breaks a lot of
workflows without reason, because  Ubuntu ssh client simply stops
working with a message like "~/.ssh/config line 3: Bad SSH2 cipher spec
'...'": it simply does not know such ciphers (does not ignore them). So
especially in environments with shared homes bionic (the usual case in
enterprises?) cannot be deployed (and telling people, that they need to
use different options when the are on bionic, is simply is useless pain
for the users as well as company hotlines).

Ubuntu should do, what all major enterprise ready distributions/unices
do, i.e. bundle support for those ciphers for backward compatibility,
but disable them per default).

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

Title:
  ssh client: blowfish-cbc required - missing in bionic

Status in openssh package in Ubuntu:
  Won't Fix
Status in openssh-ssh1 package in Ubuntu:
  Fix Released

Bug description:
  In bionic openssh client/server ships without blowfish-cbc, arcfour,
  arcfour128, arcfour256 and cast128-cbc. Unfortunately they are
  required for backward compatibility, especially for embedded devices,
  which do not support other ciphers (e.g. Rittal Liquid Cooling Package
  for racks).

  So disable them per default is ok, but one should still be able to use
  them on demand for older, non-upgradable HW/SW envs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1769284/+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 1769288] [NEW] indicator-datetime displays the date unnaturally in Japanese

2018-05-04 Thread Joe Carey

Public bug reported:

The date should be (and has been in previous Ubuntu versions) displayed
as follows (for YMD):

2018年5月4日 (the symbols clearly mean year, month, day).

Instead, they're displayed weirdly as "5月 4 2018" This is not the way a
date would ever be written in Japanese. In gnome this happens on the
lock screen as well.

If you were writing a date without the year it would be:

5月4日

it doesn't make sense to leave off the 日.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  indicator-datetime displays the date unnaturally in Japanese

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The date should be (and has been in previous Ubuntu versions)
  displayed as follows (for YMD):

  2018年5月4日 (the symbols clearly mean year, month, day).

  Instead, they're displayed weirdly as "5月 4 2018" This is not the way
  a date would ever be written in Japanese. In gnome this happens on the
  lock screen as well.

  If you were writing a date without the year it would be:

  5月4日

  it doesn't make sense to leave off the 日.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1769288/+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 1769284] Re: ssh client: blowfish-cbc required - missing in bionic

2018-05-04 Thread Seth Arnold

Hello Jens, I believe the openssh-client-ssh1 package provides a client
that can be used to communicate with legacy hardware.

Thanks

** Also affects: openssh-ssh1 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: openssh-ssh1 (Ubuntu)
   Status: New => Fix Released

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

Title:
  ssh client: blowfish-cbc required - missing in bionic

Status in openssh package in Ubuntu:
  Won't Fix
Status in openssh-ssh1 package in Ubuntu:
  Fix Released

Bug description:
  In bionic openssh client/server ships without blowfish-cbc, arcfour,
  arcfour128, arcfour256 and cast128-cbc. Unfortunately they are
  required for backward compatibility, especially for embedded devices,
  which do not support other ciphers (e.g. Rittal Liquid Cooling Package
  for racks).

  So disable them per default is ok, but one should still be able to use
  them on demand for older, non-upgradable HW/SW envs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1769284/+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 1769284] [NEW] ssh client: blowfish-cbc required - missing in bionic

2018-05-04 Thread Jens Elkner

Public bug reported:

In bionic openssh client/server ships without blowfish-cbc, arcfour,
arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required
for backward compatibility, especially for embedded devices, which do
not support other ciphers (e.g. Rittal Liquid Cooling Package for
racks).

So disable them per default is ok, but one should still be able to use
them on demand for older, non-upgradable HW/SW envs.

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

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

Title:
  ssh client: blowfish-cbc required - missing in bionic

Status in openssh package in Ubuntu:
  New

Bug description:
  In bionic openssh client/server ships without blowfish-cbc, arcfour,
  arcfour128, arcfour256 and cast128-cbc. Unfortunately they are
  required for backward compatibility, especially for embedded devices,
  which do not support other ciphers (e.g. Rittal Liquid Cooling Package
  for racks).

  So disable them per default is ok, but one should still be able to use
  them on demand for older, non-upgradable HW/SW envs.

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

2018-05-04 Thread Aaron Reason

Public bug reported:

I have a Lenovo T430.
When I reboot the screen will freeze (requires reboot) before the login prompt 
if I have both my digital display port and vga plugged in while my laptop is 
open. If I unplug the external monitors it boots fine. If I boot then quickly 
close the laptop screen it boots fine.

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 May  4 14:14:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
InstallationDate: Installed on 2018-05-04 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 23472P2
ProcEnviron:
 PATH=(custom, no User Name)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ET93WW (2.53 )
dmi.board.asset.tag: Not Available
dmi.board.name: 23472P2
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23472P2:pvrThinkPadT430:rvnLENOVO:rn23472P2:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 23472P2
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO
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 freeze 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/1769270

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Lenovo T430.
  When I reboot the screen will freeze (requires reboot) before the login 
prompt if I have both my digital display port and vga plugged in while my 
laptop is open. If I unplug the external monitors it boots fine. If I boot then 
quickly close the laptop screen it boots fine.

  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 May  4 14:14:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 23472P2
  ProcEnviron:
   PATH=(custom, no User Name)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not

[Touch-packages] [Bug 1769262] Re: PythonDetails contains an error message if python not installed

** Description changed:

- I an Ubuntu 18.04 apport-package report, bug 1768866, we can see the
- following which looks super messy:
+ [Test Case]
+ 0) ensure python is not installed on the system
+ 1) launchpad update-manager
+ 2) kill update-manager
+ 3) view the crash report
+ 
+ With the version of apport in the archive you will see messy
+ PythonDetails like below. With the version of apport from -proposed you
+ will instead see:
+ 
+ PythonDetails: N/A
+ 
+ 
+ Original Description
+ 
+ In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:
  
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit
  code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  New

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launchpad update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  
  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1769262/+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 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2018-05-04 Thread azanaz

Here is my lspci output, please tell me what else I can attach.

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5134048/+files/lspci

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu
  /graphics-drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

2018-05-04 Thread Tom

@Bernadette:  If I would have same situation again, I think I would:

1 - Ctrl-Alt-F3/2 at login prompt
2 - sudo apt purge nvidia*
3 - sudo apt install nvidia-390
4 - sudo prime-select intel
5 - sudo nvidia-xconfig
6 - sudo nano /etc/X11/xorg.conf
7 - .. and replace with contents of #117
8 - sudo nano /etc/default/grub
9 - .. GRUB_CMDLINE_LINUX_DEFAULT="'quiet splash acpi_osi=Linux acpi_osi=! 
acpi_osi=Windows 2009' nouveau.runpm=0"
10- sudo update-grub
11 - sudo reboot 
12 - login... 
13 - and start praying...

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-05-04 Thread Sergey Ponomarev

Ok, so I restored my system and I got back to my Mate and all my settings are 
kept.
I did a lot of things, even removed ecryptfs while extracted all my home 
directory from it.
I removed NVidia drivers but I don't think that they caused the problem.
But only reinstalling of XServer finally resolved the problem. I did something 
like described here:
https://www.computersnyou.com/4945/re-install-xorg-xserver-completely-ubuntu/

Hint: if you get "Ubuntu Black Screen" then on GRUB item press "e" to
edit menu item then replace "no splash" or "splash quit" with nomodeset
and press F10.

Thus I think the problem was caused by some tricky X11 configs upgrade.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1769262] Re: PythonDetails contains an error message if python not installed

This'll make it look nicer.


@@ -519,6 +519,9 @@
 def add_python_details(key, python, report):
 '''Add comma separated details about which python is being used'''
 python_path = apport.hookutils.command_output(['which', python])
+if python_path.startswith('Error: '):
+report[key] = 'N/A'
+return
 python_link = apport.hookutils.command_output(['readlink', '-f',
   python_path])
 python_pkg = apport.fileutils.find_file_package(python_path)

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  New

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launchpad update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  
  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1769262/+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 1769262] [NEW] PythonDetails contains an error message if python not installed

Public bug reported:

[Test Case]
0) ensure python is not installed on the system
1) launchpad update-manager
2) kill update-manager
3) view the crash report

With the version of apport in the archive you will see messy
PythonDetails like below. With the version of apport from -proposed you
will instead see:

PythonDetails: N/A


Original Description

In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the following 
which looks super messy:

PythonDetails: /root/Error: command ['which', 'python'] failed with exit
code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
"/root/Error: command ['which', 'python'] failed with exit code 1:":
"/root/Error: command ['which', 'python'] failed with exit code 1:",
unpackaged

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

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  New

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launchpad update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  
  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1769262/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2018-05-04 Thread Till Kamppeter

Please also attach your file /etc/cups/cupsd.conf.

Please attach files one by one, do not package them together and do not
compress them.

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1763520/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2018-05-04 Thread Till Kamppeter

Please run the command

ps auxwww | grep cups

and post the output here.

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1763520/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2018-05-04 Thread Till Kamppeter

Have you checked

https://wiki.ubuntu.com/DebuggingPrintingProblems

Especially follow the instructions of the section "CUPS error_log".

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

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1763520/+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 1769206] Re: In admin panel "Sharing - Screen Sharing". Dialog box, (bottom "Network" part of it) says there is "No networks selected for sharing". (Nothing to select) Server don

2018-05-04 Thread PG

Problem solved

Cleaned /etc/netplan and replaced the content with this:
https://paste.ubuntu.com/p/PSWHYgdQrZ/

Rebooted, and all working

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

Title:
  In admin panel "Sharing - Screen Sharing". Dialog box, (bottom
  "Network" part of it) says there is "No networks selected for
  sharing".  (Nothing to select) Server don't detect actual working
  wired connections.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able
  to activate Screen Sharing.

  The Screen Sharing dialog box, (bottom "Network" part of it) says
  there is "No networks selected for sharing".  It should at least show
  "Wired Connection 1", as in fact the wired connection is working
  perfectly (the box has internet connection in and out, and I am able
  to connect to it using ssh).

  As the sharing dialog does not show any available networks to pick
  from, it is not possible to activate the sharing.

  Another problem indicator is that the desktop systray network icon
  does not show up, even if the box is connected to fully working wired
  ethernet connection, and internet is working in and out of the
  machine.

  Also, in admin panel "Network" configuration dialog, there is no
  visible config area for "Wired Connections".  It appear as the
  computer has no network cards at all, only the VPN and Proxy settings
  are visible.

  *

  Possible related problem with drivers: I tried 'ubuntu-drivers devices' in 
order to find correct drivers for my graphic card.  The output from the command 
was simply nothing at all, it just reverted to the empty clean command prompt.
  root@mybox:~# ubuntu-drivers devices
  root@mybox:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  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 May  4 18:18:02 2018
  IfupdownConfig:
   # ifupdown has been replaced by netplan(5) on this system.  See
   # /etc/netplan for current configuration.
   # To re-enable ifupdown on this system, you can run:
   #sudo apt install ifupdown
  InstallationDate: Installed on 2018-04-29 (4 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.199 metric 100 
   192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.199 
   192.168.0.1 dev enp4s0 proto dhcp scope link src 192.168.0.199 metric 100
  IwConfig:
   enp5s0no wireless extensions.
   
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   enp4s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --   
   ----   
   enp5s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
   ----   
   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   disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769206/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

2018-05-04 Thread Steve Beattie

Thanks, Brian, reviewing now.

** Changed in: apport (Ubuntu Trusty)
 Assignee: Brian Murray (brian-murray) => Steve Beattie (sbeattie)

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  In Progress
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Zesty:
  Fix Released
Status in apport source package in Artful:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

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

  ---

  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:

  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1733366/+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 1769245] [NEW] My graphics driver gives error when i run matlab

2018-05-04 Thread Oladapo Ogunbodede

Public bug reported:

My graphics driver gives error when i run matlab

libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Segmentation fault (core dumped)

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.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May  4 14:33:05 2018
DistUpgraded: 2018-04-27 13:28:46,673 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:1693]
InstallationDate: Installed on 2017-09-24 (221 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
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=7cfc9cb1-6009-4b08-9058-4bd98169f5a0 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-27 (7 days ago)
dmi.bios.date: 01/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.37
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1693
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 14.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06911220461620100:rvnHewlett-Packard:rn1693:rvrKBCVersion14.16:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 06911220461620100
dmi.sys.vendor: Hewlett-Packard
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: Thu Apr 26 21:49:50 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 754 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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

Title:
  My graphics driver gives error when i run matlab

Status in xorg package in Ubuntu:
  New

Bug description:
  My graphics driver gives error when i run matlab

  libGL error: unable to load driver: i965_dri.so
  libGL error: driver pointer missing
  libGL error: failed to load driver: i965
  libGL error: unable to load driver: i965_dri.so
  libGL error: driver pointer missing
  libGL error: failed to load driver: i965
  libGL error: unable to load driver: swrast_dri.so
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)

  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.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:33:05 2018
  DistUpgraded: 2018-04-27 13:28:46,673 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:1693]
  InstallationDate: Installed on 2017-09-24 (221 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily

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

2018-05-04 Thread Bernadette Addison

tried #116 and also #108.  Now all I get is a boot loop at the lighdm
login screen.  Put in password and it brings me back to login screen.
This is so frustratingsmh

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1761063] Re: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

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

** This bug has been marked a duplicate of bug 1705345
   Installing packages hangs on plymouth --ping

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

Title:
  package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  run on dell 2 in 1 tablet pc. off of usbstick

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr  4 01:38:08 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1761063/+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 1769231] [NEW] wpa_cli -i flag and p2p_disabled=1 config broken

2018-05-04 Thread Raymond E Ferguson

Public bug reported:

When connecting to wpa_supplicant with wpa_cli -i interface command, the
connection hangs and never completes.  This breaks various ifupdown
integrations.

Also, when p2p_disable=1 is set in wpa_supplicant.conf, the directive is
not honored.

I pulled the latest upstream hostap 2.6 source from git and built it
using the same config file pulled from the deb source and tested to
verify.  Oddly the bug is actually in the wpa_supplicant binary as
starting 2.6 with the right flags allows both the 2.4 and the 2.6 client
to work correctly.  However, starting the 2.4 daemon provided by artful
causes both wpa_cli -i connection flags to fail.

Starting the packaged wpa_supplicant throws an odd warning as well, not
the double prefix on the p2p-dev.

/sbin/wpa_supplicant -B -P /run/wpa_supplicant.wlp4s0.pid -i wlp4s0 -W -D 
nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not read interface p2p-dev-wlp4s0 flags: No such device
Failed to create interface p2p-dev-p2p-dev-wlp4s0: -22 (Invalid argument)
nl80211: Failed to create a P2P Device interface p2p-dev-p2p-dev-wlp4s0
P2P: Failed to enable P2P Device interface

Also, in the presence of the p2p_disabled=1 flag, the 2.6 daemon
provides the expected behavior of simply not creating the addition
/run/wpa_supplicant/p2p-dev-wlp4s0 socket and unnamed device as seen by
iw dev.  However, the packaged version still creates both, apparently
leaving p2p enabled.

root@mendota:~/code/hostap/wpa_supplicant# iw dev
phy#0
Unnamed/non-netdev interface
wdev 0x5e
addr e0:9d:31:d6:45:f3
type P2P-device
txpower 0.00 dBm
Interface wlp4s0
ifindex 3
wdev 0x1
addr e0:9d:31:d6:45:f2
type managed
txpower 22.00 dBm
root@mendota:~/code/hostap/wpa_supplicant# ls -l /run/wpa_supplicant
total 0
srwxrwx--- 1 root dialout 0 May  4 12:49 p2p-dev-wlp4s0
srwxrwx--- 1 root dialout 0 May  4 12:49 wlp4s0

root@mendota:~/code/hostap/wpa_supplicant# wpa_cli -p /run/wpa_supplicant -i 
wlp4s0
wpa_cli v2.4
Copyright (c) 2004-2015, Jouni Malinen  and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Interactive mode

Warning: Failed to attach to wpa_supplicant.
Could not connect to wpa_supplicant: wlp4s0 - re-trying ...

Note that 2.6 still allows a connection even when p2p_disabled is not
set and the unnammed p2p dev and socket is created.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: wpasupplicant 2.4-0ubuntu10
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Fri May  4 12:49:50 2018
ProcEnviron:
 LANGUAGE=en_US
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  wpa_cli -i flag and p2p_disabled=1 config broken

Status in wpa package in Ubuntu:
  New

Bug description:
  When connecting to wpa_supplicant with wpa_cli -i interface command,
  the connection hangs and never completes.  This breaks various
  ifupdown integrations.

  Also, when p2p_disable=1 is set in wpa_supplicant.conf, the directive
  is not honored.

  I pulled the latest upstream hostap 2.6 source from git and built it
  using the same config file pulled from the deb source and tested to
  verify.  Oddly the bug is actually in the wpa_supplicant binary as
  starting 2.6 with the right flags allows both the 2.4 and the 2.6
  client to work correctly.  However, starting the 2.4 daemon provided
  by artful causes both wpa_cli -i connection flags to fail.

  Starting the packaged wpa_supplicant throws an odd warning as well,
  not the double prefix on the p2p-dev.

  /sbin/wpa_supplicant -B -P /run/wpa_supplicant.wlp4s0.pid -i wlp4s0 -W -D 
nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf
  Successfully initialized wpa_supplicant
  Could not read interface p2p-dev-wlp4s0 flags: No such device
  Failed to create interface p2p-dev-p2p-dev-wlp4s0: -22 (Invalid argument)
  nl80211: Failed to create a P2P Device interface p2p-dev-p2p-dev-wlp4s0
  P2P: Failed to enable P2P Device interface

  Also, in the presence of the p2p_disabled=1 flag, the 2.6 daemon
  provides the expected behavior of simply not creating the addition
  /run/wpa_supplicant/p2p-dev-wlp4s0 socket and unnamed device as seen
  by iw dev.  However, the packaged version still creates both,
  apparently leaving p2p enabled.

[Touch-packages] [Bug 1767653] Re: gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-4.4.0-122-generic with 1. dpkg: Fehler bei

You've run out of room on your /boot partition. Please remove some old
kernels and try the package operation again.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  gzip: stdout: No space left on device E: mkinitramfs failure cpio 141
  gzip 1 update-initramfs: failed for /boot/initrd.img-4.4.0-122-generic
  with 1. dpkg: Fehler beim Bearbeiten des Paketes initramfs-tools
  (--configure):  Unterprozess installiertes post-installation-Skript
  gab den Fehlerwert 1 zurück Trigger für resolvconf (1.78ubuntu6)
  werden verarbeitet ... Es wurde kein Apport-Bericht verfasst, da das
  Limit MaxReports bereits erreicht ist. Trigger für dbus
  (1.10.6-1ubuntu3.3) werden verarbeitet ... Fehler traten auf beim
  Bearbeiten von:  linux-image-extra-4.4.0-122-generic  linux-image-
  generic  linux-generic  linux-generic-lts-utopic  initramfs-tools E:
  Sub-process /usr/bin/dpkg returned an error code (1)

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-122-generic with 1.
  dpkg: Fehler beim Bearbeiten des Paketes initramfs-tools (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück
  Trigger für resolvconf (1.78ubuntu6) werden verarbeitet ...
  Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits 
erreicht ist.
  Trigger für dbus (1.10.6-1ubuntu3.3) werden verarbeitet ...
  Fehler traten auf beim Bearbeiten von:
   linux-image-extra-4.4.0-122-generic
   linux-image-generic
   linux-generic
   linux-generic-lts-utopic
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1767653/+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 1767875] Re: /usr/bin/update-manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

** Tags added: rls-bb-incoming

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

Title:
  /usr/bin/update-
  
manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate

Status in apt package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1767875/+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 1769206] Re: In admin panel "Sharing - Screen Sharing" dialog, not able to activate Screen Sharing. The Screen Sharing dialog box, (bottom "Network" part of it) says there is "

2018-05-04 Thread PG

** Summary changed:

- Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able to 
activate Screen Sharing.   The Screen Sharing dialog box, (bottom "Network" 
part of it) says there is "No networks selected for sharing".  It should at 
least show "Wired Connection 1", as in fact the wired connection is working 
perfectly (the box has internet connection in and out, and I am able to connect 
to it using ssh).  As the sharing dialog does not show any available networks 
to pick from, it is not possible to activate the sharing.  Another problem 
indicator is that the desktop systray network icon does not show up, even if 
the box is connected to fully working wired ethernet connection, and internet 
is working in and out of the machine.  Also, in admin panel "Network" 
configuration dialog, there is no visible config area for "Wired Connections".  
It appear as the computer has no network cards at all, only the VPN and Proxy 
settings are visible.  *  Possible related problem with drivers: I tried 
'ubuntu-drivers devices' in order to find correct drivers for my graphic card.  
The output from the command was simply nothing at all, it just reverted to the 
empty clean command prompt. root@mybox:~# ubuntu-drivers devices root@mybox:~#
+ In admin panel "Sharing - Screen Sharing" dialog, not able to activate Screen 
Sharing.   The Screen Sharing dialog box, (bottom "Network" part of it) says 
there is "No networks selected for sharing".

** Summary changed:

- In admin panel "Sharing - Screen Sharing" dialog, not able to activate Screen 
Sharing.   The Screen Sharing dialog box, (bottom "Network" part of it) says 
there is "No networks selected for sharing".
+ In admin panel "Sharing - Screen Sharing". Dialog box, (bottom "Network" part 
of it) says there is "No networks selected for sharing".  (Nothing to select) 
Server don't detect actual working wired connections.

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

Title:
  In admin panel "Sharing - Screen Sharing". Dialog box, (bottom
  "Network" part of it) says there is "No networks selected for
  sharing".  (Nothing to select) Server don't detect actual working
  wired connections.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able
  to activate Screen Sharing.

  The Screen Sharing dialog box, (bottom "Network" part of it) says
  there is "No networks selected for sharing".  It should at least show
  "Wired Connection 1", as in fact the wired connection is working
  perfectly (the box has internet connection in and out, and I am able
  to connect to it using ssh).

  As the sharing dialog does not show any available networks to pick
  from, it is not possible to activate the sharing.

  Another problem indicator is that the desktop systray network icon
  does not show up, even if the box is connected to fully working wired
  ethernet connection, and internet is working in and out of the
  machine.

  Also, in admin panel "Network" configuration dialog, there is no
  visible config area for "Wired Connections".  It appear as the
  computer has no network cards at all, only the VPN and Proxy settings
  are visible.

  *

  Possible related problem with drivers: I tried 'ubuntu-drivers devices' in 
order to find correct drivers for my graphic card.  The output from the command 
was simply nothing at all, it just reverted to the empty clean command prompt.
  root@mybox:~# ubuntu-drivers devices
  root@mybox:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  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 May  4 18:18:02 2018
  IfupdownConfig:
   # ifupdown has been replaced by netplan(5) on this system.  See
   # /etc/netplan for current configuration.
   # To re-enable ifupdown on this system, you can run:
   #sudo apt install ifupdown
  InstallationDate: Installed on 2018-04-29 (4 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.199 metric 100 
   192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.199 
   192.168.0.1 dev enp4s0 proto dhcp scope link src 192.168.0.199 metric 100
  IwConfig:
   enp5s0no wireless extensions.
   
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY

[Touch-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-04 Thread Andrea Azzarone

This is what I get when the account is expired. The check-button is not
sensible but is ticked. Are you getting something different?

It would also be nice to understand why the accounts tend to expire but
it's a different bug that need to be discussed somewhere elese.

** Attachment added: "account-expired.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1768797/+attachment/5133887/+files/account-expired.png

** Changed in: gnome-online-accounts (Ubuntu)
Status: New => Incomplete

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

Title:
LivePatch in Software & Updates shows that LP is not enabled when the
U1 account has expired in g-o-a

Status in gnome-online-accounts package in Ubuntu:
Incomplete

Bug description:
I enabled LivePatch via gnome-initial-setup and added my U1 account to
g-o-a.

My U1 account gets marked as expired quite often. When it's expired
the LP entry in Software & Updates is not ticked to show that LP is
running. When my u1 account is re-authenticated then everything shows
correctly.

This could make it seem that LivePatch does not run if your account
expires, which is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1768797/+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 1769141] Re: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to '/usr/lib/i386-linux-gnu/

2018-05-04 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

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

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

Title:
  package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to
  '/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of
  file or stream

Status in curl package in Ubuntu:
  Invalid

Bug description:
  errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcurl3 7.35.0-1ubuntu2.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:26 2018
  DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: curl
  Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1769141/+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 1769140] Re: package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgstiso

2018-05-04 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Status: New => Invalid

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

Title:
  package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-
  gnu/gstreamer-0.10/libgstisomp4.so' to '/usr/lib/i386-linux-
  gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected end of file
  or stream

Status in gst-plugins-good0.10 package in Ubuntu:
  Invalid

Bug description:
  system errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:01 2018
  DuplicateSignature: 
package:gstreamer0.10-plugins-good:0.10.31-3+nmu1ubuntu5:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: gst-plugins-good0.10
  Title: package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1769140/+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 1769206] [NEW] Problem: In admin panel "Sharing - Screen Sharing" dialog, not able to activate Screen Sharing. The Screen Sharing dialog box, (bottom "Network" part of it) says

2018-05-04 Thread PG

Public bug reported:

Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able to
activate Screen Sharing.

The Screen Sharing dialog box, (bottom "Network" part of it) says there
is "No networks selected for sharing".  It should at least show "Wired
Connection 1", as in fact the wired connection is working perfectly (the
box has internet connection in and out, and I am able to connect to it
using ssh).

As the sharing dialog does not show any available networks to pick from,
it is not possible to activate the sharing.

Another problem indicator is that the desktop systray network icon does
not show up, even if the box is connected to fully working wired
ethernet connection, and internet is working in and out of the machine.

Also, in admin panel "Network" configuration dialog, there is no visible
config area for "Wired Connections".  It appear as the computer has no
network cards at all, only the VPN and Proxy settings are visible.

*

Possible related problem with drivers: I tried 'ubuntu-drivers devices' in 
order to find correct drivers for my graphic card.  The output from the command 
was simply nothing at all, it just reverted to the empty clean command prompt.
root@mybox:~# ubuntu-drivers devices
root@mybox:~#

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
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 May  4 18:18:02 2018
IfupdownConfig:
 # ifupdown has been replaced by netplan(5) on this system.  See
 # /etc/netplan for current configuration.
 # To re-enable ifupdown on this system, you can run:
 #sudo apt install ifupdown
InstallationDate: Installed on 2018-04-29 (4 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
IpRoute:
 default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.199 metric 100 
 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.199 
 192.168.0.1 dev enp4s0 proto dhcp scope link src 192.168.0.199 metric 100
IwConfig:
 enp5s0no wireless extensions.
 
 lono wireless extensions.
 
 enp4s0no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 enp4s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
 enp5s0  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
 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   disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1769206

Title:
  Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able
  to activate Screen Sharing.   The Screen Sharing dialog box, (bottom
  "Network" part of it) says there is "No networks selected for
  sharing".  It should at least show "Wired Connection 1", as in fact
  the wired connection is working perfectly (the box has internet
  connection in and out, and I am able to connect to it using ssh).  As
  the sharing dialog does not show any available networks to pick from,
  it is not possible to activate the sharing.  Another problem indicator
  is that the desktop systray network icon does not show up, even if the
  box is connected to fully working wired ethernet connection, and
  internet is working in and out of the machine.  Also, in admin panel
  "Network" configuration dialog, there is no visible config area for
  "Wired Connections".  It appear as the computer has no network cards
  at all, only the VPN and Proxy settings are visible.  *  Possible
  related problem with drivers: I tried 'ubuntu-drivers devices' in
  order to find correct drivers for my graphic card.  The output from
  the command was simply nothing at all, it just reverted to the empty
  clean command prompt. root@mybox:~# ubuntu-drivers devices
  root@mybox:~#

Status in network-manager package in Ubuntu:
  New

Bug description:
  Problem:  In admin panel "Sharing - Screen Sharing" dialog, not able
  to activate Screen Sharing.

  The Screen

[Touch-packages] [Bug 1769194] Re: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed resolvconf package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package resolvconf 1.79ubuntu10 failed to install/upgrade: installed
  resolvconf package post-installation script subprocess returned error
  exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  During a "do-release-upgrade -d" from 16.04 to 18.04, an unrelated
  error occurred.  DNS didn't work at that time, so I removed
  resolvconf.  I manually updated my sources.list and did a successful
  dist-upgrade.  Then I tried to reinstall resolvconf, and got the error
  below.

  Installing new version of config file /etc/resolvconf/resolv.conf.d/head ...
  Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  Removing obsolete conffile /etc/init/resolvconf.conf ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu10
  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
  AptOrdering:
   resolvconf:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri May  4 11:46:44 2018
  DuplicateSignature:
   package:resolvconf:1.79ubuntu10
   Removing obsolete conffile /etc/init/resolvconf.conf ...
   cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
   dpkg: error processing package resolvconf (--configure):
installed resolvconf package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed resolvconf package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-05-26 (343 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: resolvconf
  Title: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed 
resolvconf package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1769194/+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 1768539] Re: Conflicts between / and /usr

This bug was fixed in the package neutron-vpnaas - 2:12.0.0-0ubuntu2

---
neutron-vpnaas (2:12.0.0-0ubuntu2) cosmic; urgency=medium

  * d/rules: Ensure neutron config files are not installed to
/usr/etc (LP: #1768539).

 -- Corey Bryant   Wed, 02 May 2018 10:46:55
-0400

** Changed in: neutron-vpnaas (Ubuntu)
   Status: New => Fix Released

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

Title:
  Conflicts between / and /usr

Status in molly-guard package in Ubuntu:
  New
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  New
Status in safe-rm package in Ubuntu:
  New
Status in pm-utils package in Debian:
  New
Status in safe-rm package in Debian:
  New

Bug description:
  bin/rm and usr/bin/rm conflict between coreutils and safe-rm

  ---
  Not a conflict, but these just look weird:
  neutron-vpnaas ships these in python-neutron-vpnaas
  etc/neutron/rootwrap.d/vpnaas.filters
  usr/etc/neutron/rootwrap.d/vpnaas.filters

  ---
  pm-utils and molly-guard conflict on:

  sbin/pm-hibernate
  usr/sbin/pm-hibernate
  sbin/pm-suspend
  usr/sbin/pm-suspend
  sbin/pm-suspend-hybrid
  usr/sbin/pm-suspend-hybrid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+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 1769140] Re: package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgstiso

** Tags removed: need-duplicate-check

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

Title:
  package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-
  gnu/gstreamer-0.10/libgstisomp4.so' to '/usr/lib/i386-linux-
  gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected end of file
  or stream

Status in gst-plugins-good0.10 package in Ubuntu:
  New

Bug description:
  system errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:01 2018
  DuplicateSignature: 
package:gstreamer0.10-plugins-good:0.10.31-3+nmu1ubuntu5:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: gst-plugins-good0.10
  Title: package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1769140/+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 1769142] Re: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to '/usr/lib/i386-linux-gnu/

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1769141
   package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot copy 
extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream

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

Title:
  package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to
  '/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of
  file or stream

Status in curl package in Ubuntu:
  New

Bug description:
  errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcurl3 7.35.0-1ubuntu2.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:26 2018
  DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: curl
  Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1769142/+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 1769141] Re: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to '/usr/lib/i386-linux-gnu/

** Tags removed: need-duplicate-check

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

Title:
  package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to
  '/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of
  file or stream

Status in curl package in Ubuntu:
  New

Bug description:
  errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcurl3 7.35.0-1ubuntu2.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:26 2018
  DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: curl
  Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1769141/+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 1769194] [NEW] package resolvconf 1.79ubuntu10 failed to install/upgrade: installed resolvconf package post-installation script subprocess returned error exit status 1

2018-05-04 Thread Dan Christensen

Public bug reported:

During a "do-release-upgrade -d" from 16.04 to 18.04, an unrelated error
occurred.  DNS didn't work at that time, so I removed resolvconf.  I
manually updated my sources.list and did a successful dist-upgrade.
Then I tried to reinstall resolvconf, and got the error below.

Installing new version of config file /etc/resolvconf/resolv.conf.d/head ...
Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
Removing obsolete conffile /etc/init/resolvconf.conf ...
cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
dpkg: error processing package resolvconf (--configure):
 installed resolvconf package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 resolvconf
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: resolvconf 1.79ubuntu10
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
AptOrdering:
 resolvconf:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri May  4 11:46:44 2018
DuplicateSignature:
 package:resolvconf:1.79ubuntu10
 Removing obsolete conffile /etc/init/resolvconf.conf ...
 cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
 dpkg: error processing package resolvconf (--configure):
  installed resolvconf package post-installation script subprocess returned 
error exit status 1
ErrorMessage: installed resolvconf package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2017-05-26 (343 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: resolvconf
Title: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed 
resolvconf package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago)

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

Title:
  package resolvconf 1.79ubuntu10 failed to install/upgrade: installed
  resolvconf package post-installation script subprocess returned error
  exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  During a "do-release-upgrade -d" from 16.04 to 18.04, an unrelated
  error occurred.  DNS didn't work at that time, so I removed
  resolvconf.  I manually updated my sources.list and did a successful
  dist-upgrade.  Then I tried to reinstall resolvconf, and got the error
  below.

  Installing new version of config file /etc/resolvconf/resolv.conf.d/head ...
  Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  Removing obsolete conffile /etc/init/resolvconf.conf ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu10
  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
  AptOrdering:
   resolvconf:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri May  4 11:46:44 2018
  DuplicateSignature:
   package:resolvconf:1.79ubuntu10
   Removing obsolete conffile /etc/init/resolvconf.conf ...
   cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
   dpkg: error processing package resolvconf (--configure):
installed resolvconf package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed resolvconf package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed

[Touch-packages] [Bug 1769194] Re: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed resolvconf package post-installation script subprocess returned error exit status 1

2018-05-04 Thread Dan Christensen

I removed the dangling "original" symlink, and then "apt-get -f install"
completed successfully.

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

Title:
  package resolvconf 1.79ubuntu10 failed to install/upgrade: installed
  resolvconf package post-installation script subprocess returned error
  exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  During a "do-release-upgrade -d" from 16.04 to 18.04, an unrelated
  error occurred.  DNS didn't work at that time, so I removed
  resolvconf.  I manually updated my sources.list and did a successful
  dist-upgrade.  Then I tried to reinstall resolvconf, and got the error
  below.

  Installing new version of config file /etc/resolvconf/resolv.conf.d/head ...
  Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
  Removing obsolete conffile /etc/init/resolvconf.conf ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu10
  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
  AptOrdering:
   resolvconf:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri May  4 11:46:44 2018
  DuplicateSignature:
   package:resolvconf:1.79ubuntu10
   Removing obsolete conffile /etc/init/resolvconf.conf ...
   cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
   dpkg: error processing package resolvconf (--configure):
installed resolvconf package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed resolvconf package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-05-26 (343 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: resolvconf
  Title: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed 
resolvconf package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1769194/+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 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-05-04 Thread Phillip Lord

My problem was solved by the fix suggested in this bug:

https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468

I don't know if mine is the same problem as reported here, but worth a
try.

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+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 1767359] Re: netplan does not work on nfsroot

2018-05-04 Thread Mathieu Trudel-Lapierre

There's more code needed to allow this to work properly.

For one, we need to have netplan write "CriticalConnection=true" in
systemd-networkd config for the remote root cases, so that networkd
doesn't release the IP when it restarts...

This is definitely an issue that requires changes in netplan.io and
initramfs; so I'm updating the targets here on the bug to reflect that.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan
   Status: Incomplete => In Progress

** Changed in: netplan
   Importance: Undecided => High

** Changed in: initramfs-tools (Ubuntu)
   Status: New => In Progress

** Changed in: netplan.io (Ubuntu)
   Status: New => In Progress

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

** Changed in: netplan
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  netplan does not work on nfsroot

Status in netplan:
  In Progress
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in netplan.io package in Ubuntu:
  In Progress

Bug description:
  It seems like netplan is not working on nfsroot systems.

  Whenever a valid config.yaml is located in /etc/netplan/ the boot
  procedure gets stuck.

  However, with an empty /etc/netplan directory, the nfsroot system
  boots (fetching IP DHCP config by kernel). Then, when I store a config
  in /etc/netplan and run "netplan apply", it stucks again.

  I guess, netplan is (temporarily) taking down active interfaces when
  applying a configuration. This must never happen on nfsroot
  systems(!). I this assumption is true, this is probably a general
  mistake, in my opinion.

  Regards,
   -frank

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1767359/+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 1768906] Re: Xorg crash

2018-05-04 Thread Cyrus Harmon

This happens with all combination of (bionic-ish) kernels and drivers
I've tried so far, including:

Drivers: NVIDIA proprietary installer 396.24, nvidia-driver-396
(396.24-0ubuntu0~gpu18.04.1), nvidia-390 (390.48-0ubuntu3+gpu18.04.2)

kernels: 4.15.0-20-lowlatency, a locally built 4.16.3

cards: GTX 770 and GTX 1070ti

I've tried erasing /etc/X11/xorg.conf, running things with and without
nomodeset, etc... all to no avail. Any suggestions for tracking this
down further? thanks!

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  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-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1

[Touch-packages] [Bug 1769183] [NEW] ubuntu-bug ignores default browser setting

2018-05-04 Thread Hynek Vychodil

Public bug reported:

When running ubuntu-bug and sending the bug report, the default web
browser setting is ignored. It just launches Firefox, even I have set
google-chrome as mine default browser.

$ sudo update-alternatives --config x-www-browser
[sudo] password for hynek: 
There are 2 choices for the alternative x-www-browser (providing 
/usr/bin/x-www-browser).

  SelectionPath Priority   Status

* 0/usr/bin/google-chrome-beta   150   auto mode
  1/usr/bin/firefox  40manual mode
  2/usr/bin/google-chrome-beta   150   manual mode

Press  to keep the current choice[*], or type selection number:

Description:Ubuntu 17.10
Release:17.10
apport:
  Installed: 2.20.7-0ubuntu3.8
  Candidate: 2.20.7-0ubuntu3.8
  Version table:
 *** 2.20.7-0ubuntu3.8 500
500 http://sk.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
500 http://sk.archive.ubuntu.com/ubuntu artful-updates/main i386 
Packages
100 /var/lib/dpkg/status
 2.20.7-0ubuntu3.7 500
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu artful-security/main i386 Packages
 2.20.7-0ubuntu3 500
500 http://sk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://sk.archive.ubuntu.com/ubuntu artful/main i386 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.8
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportLog:
 
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CrashReports: 640:1000:119:1580218:2018-04-30 08:27:05.361482009 
+0200:2018-04-30 08:27:03.801016602 
+0200:/var/crash/_usr_bin_kactivitymanagerd.1000.crash
Date: Fri May  4 17:10:25 2018
InstallationDate: Installed on 2017-11-09 (176 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2018-05-04T17:01:59.655303

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


** Tags: amd64 apport-bug artful

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

Title:
  ubuntu-bug ignores default browser setting

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug and sending the bug report, the default web
  browser setting is ignored. It just launches Firefox, even I have set
  google-chrome as mine default browser.

  $ sudo update-alternatives --config x-www-browser
  [sudo] password for hynek: 
  There are 2 choices for the alternative x-www-browser (providing 
/usr/bin/x-www-browser).

SelectionPath Priority   Status
  
  * 0/usr/bin/google-chrome-beta   150   auto mode
1/usr/bin/firefox  40manual mode
2/usr/bin/google-chrome-beta   150   manual mode

  Press  to keep the current choice[*], or type selection number:

  Description:Ubuntu 17.10
  Release:17.10
  apport:
Installed: 2.20.7-0ubuntu3.8
Candidate: 2.20.7-0ubuntu3.8
Version table:
   *** 2.20.7-0ubuntu3.8 500
  500 http://sk.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://sk.archive.ubuntu.com/ubuntu artful-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.7-0ubuntu3.7 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main i386 
Packages
   2.20.7-0ubuntu3 500
  500 http://sk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://sk.archive.ubuntu.com/ubuntu artful/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CrashReports: 640:1000:119:1580218:2018-04-30 08:27:05.361482009 
+0200:2018-04-30 08:27:03.801016602 
+0200:/var/crash/_usr_bin_kactivitymanagerd.1000.crash
  Date: Fri May  4 17:10:25 2018
  InstallationDate: Installed on 2017-11-09 (176 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2018-05-04T17:01:59.655303

To manage notifications about this bug go to:

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

2018-05-04 Thread Tom

#117 worked for me, although "suspend" is still shaky; 50% of time I
need to force power off.

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-04 Thread Sebastien Bacher

** Description changed:

- The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
- it was working some weeks/months ago, so this is a recent regression.
+ * Impact
+ The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)). 
+ 
+ * Test case
+ try installing Ubuntu on an hidpi machine, it shouldn't hit an XError
+ 
+ * Regression potential
+ the fix is ubiquity touches the code handle uid drop/privilege, that can hide 
unexpected side effect so we need proper/complete testing of the installer
+ 
+ --
  
  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the most
  common place it is experienced.
  
  ---
  
  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
  
  ---
  
  WORKAROUND:
  
  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
  
  ---
  
  Crashed in a VM in the middle of installation. The host is Bionic up to
  date.
  
  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  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
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

** Description changed:

  * Impact
- The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)). 
+ The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).
  
  * Test case
  try installing Ubuntu on an hidpi machine, it shouldn't hit an XError
  
  * Regression potential
- the fix is ubiquity touches the code handle uid drop/privilege, that can hide 
unexpected side effect so we need proper/complete testing of the installer
+ the fix is ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effect so we need proper/complete testing of the installer
  
  --
  
  Update: Actually the crash occurs on slow-ish systems due to a race

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

2018-05-04 Thread Jean-Sébastien Herbaux

#116 worked for me, thanks

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer details to help improving Ubuntu

2018-05-04 Thread Didier Roche

** Branch linked: lp:~didrocks/ubuntu-release-upgrader/add_telemetry

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

Title:
  [ffe] Optional recording/sending of installer details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review those informations
  - the desktop settings should have a control to change the option later on

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1755456/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

2018-05-04 Thread Kev Bowring

@albertomilone - could we have a fix for bug 1761593 ? I did try on the
off-chance using the updated software-properties from proposed - but I
was left having to rm /etc/modprobe.d/nvidia-340.conf

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+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 1769140] [NEW] package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgsti

2018-05-04 Thread Hadaka

Public bug reported:

system errors

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Date: Fri May  4 09:11:01 2018
DuplicateSignature: 
package:gstreamer0.10-plugins-good:0.10.31-3+nmu1ubuntu5:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
InstallationDate: Installed on 2018-05-04 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
SourcePackage: gst-plugins-good0.10
Title: package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-good0.10 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check trusty

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

Title:
  package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-
  gnu/gstreamer-0.10/libgstisomp4.so' to '/usr/lib/i386-linux-
  gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected end of file
  or stream

Status in gst-plugins-good0.10 package in Ubuntu:
  New

Bug description:
  system errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:01 2018
  DuplicateSignature: 
package:gstreamer0.10-plugins-good:0.10.31-3+nmu1ubuntu5:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: gst-plugins-good0.10
  Title: package gstreamer0.10-plugins-good 0.10.31-3+nmu1ubuntu5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so' to 
'/usr/lib/i386-linux-gnu/gstreamer-0.10/libgstisomp4.so.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1769140/+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 1769141] [NEW] package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to '/usr/lib/i386-linux-gn

2018-05-04 Thread Hadaka

Public bug reported:

errors

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libcurl3 7.35.0-1ubuntu2.3
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Date: Fri May  4 09:11:26 2018
DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2018-05-04 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
SourcePackage: curl
Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check trusty

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

Title:
  package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to
  '/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of
  file or stream

Status in curl package in Ubuntu:
  New

Bug description:
  errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcurl3 7.35.0-1ubuntu2.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:26 2018
  DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: curl
  Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1769141/+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 1769142] [NEW] package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to '/usr/lib/i386-linux-gn

2018-05-04 Thread Hadaka

Public bug reported:

errors

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libcurl3 7.35.0-1ubuntu2.3
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Date: Fri May  4 09:11:26 2018
DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2018-05-04 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
SourcePackage: curl
Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check trusty

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

Title:
  package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to
  '/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of
  file or stream

Status in curl package in Ubuntu:
  New

Bug description:
  errors

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcurl3 7.35.0-1ubuntu2.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Fri May  4 09:11:26 2018
  DuplicateSignature: package:libcurl3:7.35.0-1ubuntu2.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  SourcePackage: curl
  Title: package libcurl3 7.35.0-1ubuntu2.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libcurl.so.4.3.0' to 
'/usr/lib/i386-linux-gnu/libcurl.so.4.3.0.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1769142/+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 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

2018-05-04 Thread Andrea Azzarone

Gtk upstream is not going to work on this until we find a way to
reproduce the crash.

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

** Merge proposal linked:
   https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  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
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 1769132] [NEW] ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

2018-05-04 Thread widon1104

Public bug reported:

ubuntu18.04's libfreetype6 version 2.8.1 has a bug of rendering bitmap font 
like ZFull gb, should be upgrade to version 2.9.
I checked libfreetype 2.9 fix this bug. I post this bug in:

https://savannah.nongnu.org/bugs/?53798

there are some picture I grab for this bug:

http://forum.ubuntu.org.cn/viewtopic.php?f=186=487304

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

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

Title:
  ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

Status in freetype package in Ubuntu:
  New

Bug description:
  ubuntu18.04's libfreetype6 version 2.8.1 has a bug of rendering bitmap font 
like ZFull gb, should be upgrade to version 2.9.
  I checked libfreetype 2.9 fix this bug. I post this bug in:

  https://savannah.nongnu.org/bugs/?53798

  there are some picture I grab for this bug:

  http://forum.ubuntu.org.cn/viewtopic.php?f=186=487304

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1769132/+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 1769075] Re: Upgrade to 18.04 broke the battery reporting of bluetooth keyboard

2018-05-04 Thread Vasilis Vlachoudis

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Upgrade to 18.04 broke the battery reporting of bluetooth keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] [NEW] Upgrade to 18.04 broke the battery reporting of bluetooth keyboard

You have been subscribed to a public bug:

I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard.
Which is a bit annoying since I get a KDE warning on the battery.

Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
  native-path:  hid-34:88:5d:5e:0c:2f-battery
  model:Logitech K810
  power supply: no
  updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
  has history:  yes
  has statistics:   yes
  keyboard
present: yes
rechargeable:yes
state:   unknown
warning-level:   none
percentage:  0%
icon-name:  'battery-missing-symbolic'

My guess is that the issue is in the bluetooth rather in the upowerd
since the reporting in the /sys/devices shows battery level of 0

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


** Tags: bot-comment
-- 
Upgrade to 18.04 broke the battery reporting of bluetooth keyboard
https://bugs.launchpad.net/bugs/1769075
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

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

[Touch-packages] [Bug 1768232] Re: i915 driver issue in Ubuntu 18.04

2018-05-04 Thread Ubuntulearner

@Tarik GRABA  My system stuck at ubuntu logo while booting. To resolve it, I've 
set nomodeset.
But now it occurs a resolution issue to 1024x768. In 'Try Ubuntu' it worked 
well. No such issue. I tried installing 4.16 kernel but not resolved.

I've two HDD in system. In one Ubuntu 16.04.04 installed and other
18.04. No issue with 16.04.04.

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

Title:
  i915 driver issue in Ubuntu 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My system stuck at ubuntu logo while booting. To resolve it, I've set
  nomodeset.

  But now it occurs a resolution issue to 1024x768. Here are the
  necessary information:

  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  and

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
    • checking for i915 module in /sys/module
    • i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
    • fetching https://download.01.org/gfx/ilg-config.cfg
    • saving to /home/test/.ilg-config
    • fetched 1626 bytes
    • fetched 9818 bytes
    • fetched 12301 bytes
    • looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  
  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: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  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

[Touch-packages] [Bug 1768755] Re: Missing links to libGL.so and libglapi.so

2018-05-04 Thread Timo Aaltonen

correct, but libglvnd-dev (which libgl1-mesa-dev depends on) does
provide libGL.so

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

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

Title:
  Missing links to libGL.so and libglapi.so

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain
  the symbolic links libGL.so and libglapi.so.

  Thus, it is not possible to use the -lGL option to compile a
  program...

  System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
  Package: libgl1-mesa-dev:amd64 18.0.0~rc5-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768755/+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 1768232] Re: i915 driver issue in Ubuntu 18.04

2018-05-04 Thread Ubuntulearner

** Description changed:

+ My system stuck at ubuntu logo while booting. To resolve it, I've set
+ nomodeset.
+ 
+ But now it occurs a resolution issue to 1024x768. Here are the necessary
+ information:
+ 
  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
- Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
- Kernel modules: i915, intelfb
- 
+ Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
+ Kernel modules: i915, intelfb
  
  and
  
- xrandr 
+ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
-1024x768  76.00*
+    1024x768  76.00*
  
  Output of sudo lshw -c display
  
- *-display UNCLAIMED   
-description: VGA compatible controller
-product: 82945G/GZ Integrated Graphics Controller
-vendor: Intel Corporation
-physical id: 2
-bus info: pci@:00:02.0
-version: 02
-width: 32 bits
-clock: 33MHz
-capabilities: msi pm vga_controller bus_master cap_list
-configuration: latency=0
-resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d
+ *-display UNCLAIMED
+    description: VGA compatible controller
+    product: 82945G/GZ Integrated Graphics Controller
+    vendor: Intel Corporation
+    physical id: 2
+    bus info: pci@:00:02.0
+    version: 02
+    width: 32 bits
+    clock: 33MHz
+    capabilities: msi pm vga_controller bus_master cap_list
+    configuration: latency=0
+    resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d
  
- I've tried solution 1 and solution 2 but no success.
  
  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.
  
  Intel Graphics Update Tool shows:
  
  Checking if Intel graphics card available...
-   • checking for i915 module in /sys/module
-   • i915 module found
+   • checking for i915 module in /sys/module
+   • i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
-   • fetching https://download.01.org/gfx/ilg-config.cfg
-   • saving to /home/garden/.ilg-config
-   • fetched 1626 bytes
-   • fetched 9818 bytes
-   • fetched 12301 bytes
-   • looking up [Ubuntu bionic] configuration
+   • fetching https://download.01.org/gfx/ilg-config.cfg
+   • saving to /home/test/.ilg-config
+   • fetched 1626 bytes
+   • fetched 9818 bytes
+   • fetched 12301 bytes
+   • looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed
+ 
https://askubuntu.com/questions/1030483/resolution-issue-driver-i915-with-nomodeset
+ 
https://chat.stackexchange.com/rooms/76832/discussion-between-sudodus-and-d-a-i-s-y
+ 
  
  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: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
-  Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
+  Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
-  Section "Device"
-   Identifier "Intel Graphics"
-   Driver "intel"
-   Option "AccelMethod" "uxa"
-  EndSection
+  Section "Device"
+

[Touch-packages] [Bug 1769091] [NEW] Xorg freeze on login

2018-05-04 Thread Berenyi Lajos

Public bug reported:

Ubuntu 18.04.
If I give a wrong password during the login, it of course fails, and write an 
error message.
But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
This behavior occurs either on my real laptop either on vitualbox gest.

Other problem:
On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

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 May  4 10:05:01 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GpuHangFrequency: I don't know
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2018-04-27 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic freeze 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/1769091

Title:
  Xorg freeze on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  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 May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet

[Touch-packages] [Bug 1769091] Re: Xorg freeze on login

2018-05-04 Thread Berenyi Lajos

Ubuntu 18.04.
If I give a wrong password during the login, it of course fails, and write an 
error message.
But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
This behavior occurs either on my real laptop either on vitualbox gest.

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

Title:
  Xorg freeze on login

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  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 May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769091/+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 1164016] Re: restore type-ahead find

2018-05-04 Thread Lubomir Brindza

Try this: https://launchpad.net/~lubomir-brindza/+archive/ubuntu
/nautilus-typeahead

The changes are based on the patch from Arch community
(https://aur.archlinux.org/packages/nautilus-typeahead/), with slight
modifications to work on 3.26.3 release.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1558511] Re: systemd-journald crashed with SIGABRT

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

Title:
  systemd-journald crashed with SIGABRT

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Crashed shortly after logging in to my laptop.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Thu Mar 10 21:12:39 2016
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-02-13 (398 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 1420
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=71fcab68-425b-4dae-a9ec-13245f989fe1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0DT492
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0DT492:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1558511/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-04 Thread Andrey Arapov

The patch
https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056
did work for me on my mid-2017 MacBookPro (HW, not VM).

Thank you, Andrea!

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  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
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 1769056] Re: driverless printing generates wrong language/encoding PPD

** Attachment added: "driverlesstest-en.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+attachment/5133471/+files/driverlesstest-en.ppd

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  New

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+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 1769056] Re: driverless printing generates wrong language/encoding PPD

** Attachment added: "ipptool.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+attachment/5133472/+files/ipptool.txt

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  New

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

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

2018-05-04 Thread UmaShankar

Public bug reported:

I have upgraded ubuntu form 17.10 to 18.04, but after login in Gnome or Ubuntu 
desktop environment, UI is not responding. No mouse no keyboard, every thing is 
frozen, even i can't logout from screen. i have to manually turnoff the laptop.
Currently i am using deepin desktop environment.
Please do the needful.

Thanks

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
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Deepin
Date: Fri May  4 12:02:20 2018
DistUpgraded: 2018-04-28 03:31:09,905 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5002]
InstallationDate: Installed on 2017-03-30 (399 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 20140
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=871acc38-6b5a-4871-8105-c9af13662669 ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2018-04-27 (6 days ago)
dmi.bios.date: 04/10/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: H1ET73WW(1.16)
dmi.board.asset.tag: Not Available
dmi.board.name: 20140
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrH1ET73WW(1.16):bd04/10/2013:svnLENOVO:pn20140:pvrLenovoB480:rvnLENOVO:rn20140:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: Lenovo B480
dmi.product.name: 20140
dmi.product.version: Lenovo B480
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.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

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze 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/1769058

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have upgraded ubuntu form 17.10 to 18.04, but after login in Gnome or 
Ubuntu desktop environment, UI is not responding. No mouse no keyboard, every 
thing is frozen, even i can't logout from screen. i have to manually turnoff 
the laptop.
  Currently i am using deepin desktop environment.
  Please do the needful.

  Thanks

  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
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Deepin
  Date: Fri May  4 12:02:20 2018
  DistUpgraded: 2018-04-28 03:31:09,905 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5002]
  InstallationDate: Installed on 2017-03-30 (399 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20140
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=871acc38-6b5a-4871-8105-c9af13662669 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (6 days ago)
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1ET73WW(1.16)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20140
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor:

[Touch-packages] [Bug 1769056] Re: driverless printing generates wrong language/encoding PPD

** Attachment added: "driverlesstest-ja.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+attachment/5133470/+files/driverlesstest-ja.ppd

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  New

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+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 1769056] [NEW] driverless printing generates wrong language/encoding PPD

Public bug reported:

The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

I tried with Epson EP-879AW.

Steps to reproduce:

1) generate a print queue by driverless feature with ja-JP locale:

$ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
everywhere

2) check the generated PPD (attached driverlesstest-ja.ppd)

$ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

Expected: PPD have same language/encoding with content (if the content
have Japanese, language/encoding should be Japanese/UTF-8)

Actual: PPD has Japanese strings, but language/encoding is
English/ISOLatin1



Attached files:
 
EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of EP-879AW 
driverless print queue
driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
driverless-en.ppd: PPD generated with C locale
ipptool.txt: output of ipptool, by following command:

$ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

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

** Attachment added: "screenshot of printing option dialog of EP-879AW 
driverless print queue"
   
https://bugs.launchpad.net/bugs/1769056/+attachment/5133468/+files/EPSON_EP_879A_Series_007.png

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  New

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+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 1659676] Re: backport timesyncd patch for updating the RTC

2018-05-04 Thread Cam Cope

Whoops, just checked the latest xenial systemd source package and
mistakenly thought I saw the patch had already been pulled. Please pull
this.

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

** Description changed:

- Please backport this patch to 16.04, which should improve reliability of
- timesyncd updates to the RTC:
+ Please backport this patch to 16.04. Sometimes hosts can boot up with
+ system clocks that are off by more than the NTP_MAX_ADJUST. This patch
+ improves reliability of timesyncd updates to the RTC:
  
  
https://github.com/systemd/systemd/commit/5f36e3d30375cf04292bbc1bf3f4d7512cf80139

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

Title:
  backport timesyncd patch for updating the RTC

Status in systemd package in Ubuntu:
  New

Bug description:
  Please backport this patch to 16.04. Sometimes hosts can boot up with
  system clocks that are off by more than the NTP_MAX_ADJUST. This patch
  improves reliability of timesyncd updates to the RTC:

  
https://github.com/systemd/systemd/commit/5f36e3d30375cf04292bbc1bf3f4d7512cf80139

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1768991/+attachment/5133448/+files/ProcModules.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1768991] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1768991/+attachment/5133449/+files/UdevDb.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1659676] Re: backport timesyncd patch for updating the RTC

2018-05-04 Thread Cam Cope

** Tags added: patch patch-accepted-upstream

** Changed in: systemd (Ubuntu)
   Status: New => 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/1659676

Title:
  backport timesyncd patch for updating the RTC

Status in systemd package in Ubuntu:
  New

Bug description:
  Please backport this patch to 16.04. Sometimes hosts can boot up with
  system clocks that are off by more than the NTP_MAX_ADJUST. This patch
  improves reliability of timesyncd updates to the RTC:

  
https://github.com/systemd/systemd/commit/5f36e3d30375cf04292bbc1bf3f4d7512cf80139

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1768991/+attachment/5133443/+files/IwConfig.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1768991] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1768991/+attachment/5133444/+files/Lspci.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1768991] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1768991/+attachment/5133450/+files/WifiSyslog.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1768991] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1768991/+attachment/5133447/+files/ProcInterrupts.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

-- 
Mailing list:

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

apport information

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

-- 
Mailing list:

[Touch-packages] [Bug 1768991] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1768991/+attachment/5133445/+files/Lsusb.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

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

apport information

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

-- 
Mailing list:

[Touch-packages] [Bug 1768991] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1768991/+attachment/5133440/+files/CRDA.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/1768991

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

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

apport information

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

-- 
Mailing list:

[Touch-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work