[Touch-packages] [Bug 1755447] Re: issue 32185: SSLContext.wrap_socket sends SNI Extension when server_hostname is IP

2018-10-21 Thread Steve Langasek
** Changed in: python2.7 (Ubuntu Artful)
   Status: New => Won't Fix

** Changed in: python3.6 (Ubuntu Artful)
   Status: New => Won't Fix

** Changed in: python3.7 (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  issue 32185: SSLContext.wrap_socket sends SNI Extension when
  server_hostname is IP

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  New
Status in python3.6 package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Trusty:
  New
Status in python3.4 source package in Trusty:
  New
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  New
Status in python2.7 source package in Artful:
  Won't Fix
Status in python3.6 source package in Artful:
  Won't Fix
Status in python3.7 source package in Artful:
  Won't Fix
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  Fix Released
Status in python3.7 source package in Bionic:
  Fix Released
Status in python2.7 package in Debian:
  New
Status in python3.4 package in Debian:
  New
Status in python3.5 package in Debian:
  New

Bug description:
  the fix for https://bugs.python.org/issue32185 needs backports for the
  stable releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1755447/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] Re: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

2018-10-21 Thread zhangboyang...@gmail.com
This is the upstream issue:

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

I reported this bug about 1 year ago. The bug is introduced in

[base] Don't zero out allocated memory twice (#51816).
https://savannah.nongnu.org/bugs/?51816
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=bd28952e23bcd268a623ea5202e1cde4a92defe4

And fixed in:

Fix access to uninitalized memory (#52613).
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=e1090c608b72dcfc1899c33974acd056e120aa53

[base] Fix bitmap emboldening.
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=3b88576ba0807f5203310c22d5dbfff803c4abd9


To fix this problem, there are two ways:
(1) revert changes bd28952e
(2) merge e1090c60 and 3b88576b to current code base

I suggest (1) because it's simpler.

** Bug watch added: Non-GNU Savannah Bug Tracker #52613
   http://savannah.nongnu.org/bugs/?52613

** Bug watch added: Non-GNU Savannah Bug Tracker #51816
   http://savannah.nongnu.org/bugs/?51816

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

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&t=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 1767228] Re: Plasma Could Not Correctly Use OpenGL 2 after upgrading to 18.04

2018-10-21 Thread Daniel van Vugt
It looks like your kernel command line might be to blame:

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
root=UUID=8258f7ec-7593-4407-95b1-cf77cc95da6c ro nogpumanager quiet
splash nouveau.runpm=0 vt.handoff=1


Please:
  1. Remove "nogpumanager" and "nouveau.runpm=0" from /etc/default/grub
  2. Run: sudo update-grub
  3. Reboot
  4. Tell us if the problem persists.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Plasma Could Not Correctly Use OpenGL 2 after upgrading to 18.04

Status in Ubuntu:
  Incomplete

Bug description:
  After I upgrade Kubuntu from 17.10 to 18.04, and restarted it, all I'm
  seeing is my mouse cursor, which responds to my movements, and that's
  pretty much it. I tried to see if I can start up sddm, but that
  failed.

  I got to login by installing slick-greeter and use that instead.

  After logging in, the message says:

  
  Plasma is unable to start as it could not correctly use OpenGL 2. Please 
check that your graphics drivers are set up correctly. 
  

  I checked the environment variable `$DISPLAY`, but it seems to be
  unset.

  I tried reinstalling `plasma-desktop`, `sddm`, `mesa` drivers, `xorg`,
  `xserver-xorg*intel`, `kde*`, `kwin`, and `nvidia-340` drivers.

  My laptop is a Lenovo Z40 with NVIDIA GT810m (currently disabled and
  using Intel HD Graphics).

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Apr 26 20:51:46 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   nvidia-340, 340.106, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
 Subsystem: Lenovo GeForce 820M [17aa:380d]
  InstallationDate: Installed on 2017-04-11 (380 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170411)
  MachineType: LENOVO 20366
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8258f7ec-7593-4407-95b1-cf77cc95da6c ro nogpumanager quiet splash 
nouveau.runpm=0 vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN91WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 4A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20366:pvrLenovoZ40-70:rvnLENOVO:rnLancer4A5:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoZ40-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20366
  dmi.product.version: Lenovo Z40-70
  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

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

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


[Touch-packages] [Bug 1766883] Re: pb à l'ouverture de la session

2018-10-21 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  pb à l'ouverture de la session

Status in Ubuntu:
  Incomplete

Bug description:
  pas de pb signalé ni remarqué à l'ouverture des applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr 25 15:52:15 2018
  DistUpgraded: 2016-08-10 19:54:46,940 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2014-03-20 (1496 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Compaq 6000 Pro SFF PC
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=70546220-22de-4bbe-bdf0-8d91d160f8b7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (622 days ago)
  dmi.bios.date: 08/25/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v01.09
  dmi.board.asset.tag: CZC0510XBX
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC0510XBX
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:svnHewlett-Packard:pnHPCompaq6000ProSFFPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq 6000 Pro SFF PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 25 15:08:13 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1767098] Re: Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

2018-10-21 Thread Daniel van Vugt
Please run this command so that we can see if the kernel is reporting
the HDMI as connected:

  grep . /sys/class/drm/*/status

and send us the output.

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

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

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

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

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

Title:
  Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On a fresh installation of Ubuntu 18.04, both DVI outputs on the back
  of the card function as expected but it is not possible to enable the
  HDMI output.

  I can reliably reproduce the issue under both X and Wayland.

  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: Thu Apr 26 11:22:57 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.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
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.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.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/linux/+bug/1767098/+subscriptions

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


[Touch-packages] [Bug 1766968] Re: loss of launcher and desktop graphic

2018-10-21 Thread Daniel van Vugt
Can you please explain in more detail what went wrong? What do you mean
by "lost services and all ability to change Desktop to include
Graphic,", and does it still happen?

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

** Changed in: ubuntu
   Status: Confirmed => Incomplete

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

Title:
  loss of launcher and desktop graphic

Status in Ubuntu:
  Incomplete

Bug description:
  Logged out to change from gnome to unity and lost services and all
  ability to change Desktop to include Graphic,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr 25 15:03:56 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d0]
   NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0]
  InstallationDate: Installed on 2017-01-21 (459 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 4180W4B
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=debe0dd6-6497-46f9-afe1-933bd5f7cbaf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET67WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W4B
  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:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4180W4B:pvrThinkPadT420:rvnLENOVO:rn4180W4B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W4B
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 25 14:45:00 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 738 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1766974] Re: /dev/dri/card0

2018-10-21 Thread Daniel van Vugt
Dave,

Please run this command to send us more information about the machine:

  apport-collect 1766974

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

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

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

Title:
  /dev/dri/card0

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  There are very many bugs reported recently against xorg with a commmon
  theme

  the following are just 2 examples from the various xorg logs

  (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission 
denied
  (EE) intel(0): [drm] failed to set drm interface version: Permission denied 
[13].

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

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


[Touch-packages] [Bug 1791397] Re: Bug

2018-10-21 Thread Daniel van Vugt
Please report one bug per issue. Let's make this bug about just "Video
is running slow".

Can you please explain in more detail what the problem is? What exactly
is slow? Is it fast for the first few hours?

Also, if you can, please try Ubuntu version 18.10
(https://www.ubuntu.com/download/desktop).


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

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Bug
+ Video is running slow.

** Tags added: performance

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

Title:
  Video is running slow.

Status in Ubuntu:
  Incomplete

Bug description:
  Video is running slow.
  Bluetooth adapter is not working.
  After several hours system running slow.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  8 09:19:54 2018
  DistUpgraded: 2018-09-08 08:32:59,711 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1224): WARNING **: Failed to load user image: Failed 
to open file '/home/deepak/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  Lsusb:
   Bus 002 Device 003: ID 05c8:0348 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 250 G1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=321496ab-6cbc-4803-affa-13e40e9abdb2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (0 days ago)
  dmi.bios.date: 12/19/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.45
  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: 5CG33772D7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.45:bd12/19/2013:svnHewlett-Packard:pnHP250G1NotebookPC:pvr088E1300591600010:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP 250 G1 Notebook PC
  dmi.product.version: 088E1300591600010
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Sep  8 04:45:00 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 917 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Touch-packages] [Bug 1790257] Re: sudo update issue

2018-10-21 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  sudo update issue

Status in Ubuntu:
  Incomplete

Bug description:
  sudo update issue

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep  1 08:12:45 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:078c]
  InstallationDate: Installed on 2018-08-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15-3567
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=801910ef-d61d-4b8d-8464-876a6ba4b079 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-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

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

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


[Touch-packages] [Bug 1798487] Re: ubuntu

2018-10-21 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  ubuntu

Status in Ubuntu:
  Incomplete

Bug description:
  $ ubuntu-bug xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Oct 18 00:43:26 2018
  DistUpgraded: 2018-10-14 08:37:38,803 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:832a]
  InstallationDate: Installed on 2018-10-14 (3 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:58ed Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c087 Logitech, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs1xx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=41511a8e-8ac5-477b-86b9-0ac1708a0280 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-14 (3 days ago)
  dmi.bios.date: 08/06/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832A
  dmi.board.vendor: HP
  dmi.board.version: 23.61
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd08/06/2018:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.61:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1
  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: Sun Oct 14 08:02:35 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1799129] [NEW] [X555LAB, Intel Haswell HDMI, Digital Out, HDMI] No sound at all

2018-10-21 Thread gopendra
Public bug reported:

Please check and let me know the solution

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gopendra   6008 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 11:32:46 2018
InstallationDate: Installed on 2018-10-10 (11 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Built-in Audio - HDA Intel HDMI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1143 F pulseaudio
  gopendra   6008 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [X555LAB, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LAB.503
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555LAB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-10-22T11:27:17.870832

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


** Tags: amd64 apport-bug bionic

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

Title:
  [X555LAB, Intel Haswell HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Please check and let me know the solution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopendra   6008 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 11:32:46 2018
  InstallationDate: Installed on 2018-10-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1143 F pulseaudio
gopendra   6008 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [X555LAB, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-10-22T11:27:17.870832

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1799129/+subscriptions

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


[Touch-packages] [Bug 1555566] Re: Après une mise à jour, très souvent mon imprimante ne fonctionne plus.

2018-10-21 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Après une mise à jour, très souvent mon imprimante ne fonctionne plus.

Status in cups package in Ubuntu:
  Expired

Bug description:
  Et l'icône HPLIP, qui permettait de résoudre des problèmes, n'apparait
  plus dans la barre des menus

  Merci

  Maigret Yvan

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

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


[Touch-packages] [Bug 1528292] Re: /usr/bin/apt-get:11:pkgCache::VerIterator::VerStr:pkgCache::DepIterator::IsSatisfied:pkgDepCache::CheckDep:pkgDepCache::CheckDep:pkgDepCache::DependencyState

2018-10-21 Thread Launchpad Bug Tracker
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/bin/apt-
  
get:11:pkgCache::VerIterator::VerStr:pkgCache::DepIterator::IsSatisfied:pkgDepCache::CheckDep:pkgDepCache::CheckDep:pkgDepCache::DependencyState

Status in apt package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apt.  This problem was most recently seen with version
  1.0.10.2ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8df1e2814e20a598621de381e2d0d11a222659fe
  contains more details.

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

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


[Touch-packages] [Bug 1530984] Re: /usr/bin/apt-get:11:pkgDepCache::StateCache::StripEpoch:pkgDepCache::StateCache::Update:pkgDepCache::Init:pkgCacheFile::BuildDepCache:pkgCacheFile::Open

2018-10-21 Thread Launchpad Bug Tracker
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/bin/apt-
  
get:11:pkgDepCache::StateCache::StripEpoch:pkgDepCache::StateCache::Update:pkgDepCache::Init:pkgCacheFile::BuildDepCache:pkgCacheFile::Open

Status in apt package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apt.  This problem was most recently seen with version
  1.0.10.2ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7f57d44cb828fdc21df48c4b255075936cf2e392
  contains more details.

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

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


[Touch-packages] [Bug 1530945] Re: /usr/bin/apt-get:11:pkgPolicy::GetCandidateVer:pkgDepCache::GetCandidateVer:pkgDepCache::Init:pkgCacheFile::BuildDepCache:pkgCacheFile::Open

2018-10-21 Thread Launchpad Bug Tracker
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/bin/apt-
  
get:11:pkgPolicy::GetCandidateVer:pkgDepCache::GetCandidateVer:pkgDepCache::Init:pkgCacheFile::BuildDepCache:pkgCacheFile::Open

Status in apt package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apt.  This problem was most recently seen with version
  1.0.10.2ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/d25b0230983b94d741845108c30aaf16201e938f
  contains more details.

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

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


[Touch-packages] [Bug 1747619] Re: package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

2018-10-21 Thread Launchpad Bug Tracker
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 10

Status in apt package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Expired

Bug description:
  installation of a new package impossible

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb  6 10:22:06 2018
  DuplicateSignature:
   package:samba-common:2:4.3.11+dfsg-0ubuntu0.16.04.12
   Setting up grub-pc (2.02~beta2-36ubuntu3.16) ...
   dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2014-04-24 (1383 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   nautilus 1:3.18.4.is.3.14.3-0ubuntu6
   gvfs 1.28.2-1ubuntu1~16.04.2
  SambaClientRegression: No
  SourcePackage: samba
  Title: package samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1752583] Re: apt-get autoremove error

2018-10-21 Thread Launchpad Bug Tracker
[Expired for apt (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  apt-get autoremove error

Status in apt package in Ubuntu:
  Expired

Bug description:
  To free up space in /boot, I ran "apt-get autoremove.

  Before running the command, I had 4 kernel packages installed:

  linux-image-extra-4.4.0-109-generic
  linux-image-extra-4.4.0-112-generic
  linux-image-extra-4.4.0-116-generic
  linux-image-extra-4.4.0-92-generic

  Afterwards, the 3 kernel packages remaining were:

  linux-image-extra-4.4.0-112-generic
  linux-image-extra-4.4.0-116-generic
  linux-image-extra-4.4.0-92-generic

  It would appear that the packages to be removed are selected based on
  a numeric sort, and linux-image-extra-4.4.0-92-generic has the highest
  version number.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar  1 14:16:39 2018
  InstallationDate: Installed on 2016-09-29 (517 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1788192] Re: package base-files 10.1ubuntu2.2 failed to install/upgrade: end of file on stdin at conffile prompt

2018-10-21 Thread Launchpad Bug Tracker
[Expired for base-files (Ubuntu) because there has been no activity for
60 days.]

** Changed in: base-files (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package base-files 10.1ubuntu2.2 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in base-files package in Ubuntu:
  Expired

Bug description:
  I have been facing update problems every month.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: base-files 10.1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   base-files:amd64: Install
   base-files:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Aug 21 10:15:39 2018
  Dependencies:
   
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-03-14 (159 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: base-files
  Title: package base-files 10.1ubuntu2.2 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.issue:
   Ubuntu 18.04 LTS \n \l
  modified.conffile..etc.issue.net: Ubuntu 18.04 LTS
  modified.conffile..etc.lsb-release:
   DISTRIB_ID=Ubuntu
   DISTRIB_RELEASE=18.04
   DISTRIB_CODENAME=bionic
   DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"
  mtime.conffile..etc.issue: 2018-04-24T05:34:22
  mtime.conffile..etc.issue.net: 2018-04-24T05:34:22
  mtime.conffile..etc.legal: 2015-10-22T15:15:21
  mtime.conffile..etc.lsb-release: 2018-04-24T05:33:11
  mtime.conffile..etc.update-motd.d.00-header: 2015-10-22T15:15:21
  mtime.conffile..etc.update-motd.d.10-help-text: 2016-06-14T09:23:23
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-06-29T12:35:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1788192/+subscriptions

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


[Touch-packages] [Bug 1799064] Re: Bluetooth refuses to power on after cosmic upgrade

2018-10-21 Thread Daniel van Vugt
Please try installing an older kernel like that which was in Ubuntu
18.04:

  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/

Reboot, and as soon as you see the purple screen hit Esc. Then select
the older kernel you have installed.

If that fixes the problem then please repeat and try to find the kernel
version where it stopped working:

  http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=A

If that didn't work then please repeat with an even older kernel than
4.15.

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

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

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

Title:
  Bluetooth refuses to power on after cosmic upgrade

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  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.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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


[Touch-packages] [Bug 1799064] Status changed to Confirmed

2018-10-21 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Bluetooth refuses to power on after cosmic upgrade

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  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.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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


[Touch-packages] [Bug 1799064] Re: Bluetooth refuses to power on after cosmic upgrade

2018-10-21 Thread Daniel van Vugt
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Bluetooth refuses to power on after cosmic upgrade

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  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.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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


[Touch-packages] [Bug 1799069] Re: 18.10 regression: guake resets font choice after every login

2018-10-21 Thread Daniel van Vugt
Please run this command to send us more information about the machine:

  apport-collect 1799069

** Tags added: cosmicv

** Tags removed: cosmicv
** Tags added: cosmic

** Package changed: pulseaudio (Ubuntu) => guake (Ubuntu)

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

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

Title:
  18.10 regression: guake resets font choice after every login

Status in guake package in Ubuntu:
  Incomplete

Bug description:
  I've got guake set to use my system monospaced font (which is Ubuntu
  Mono). however, on every fresh login, it resets to some other font
  until I go into the guake prefs and unckeck then recheck the "Use the
  system fixed width font" box. It seems to remember it's checked, but
  it just doesn't correctly use it on startup.

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

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


[Touch-packages] [Bug 1799103] Re: [radeon] Screen corrupted (skewed stride) after boot

2018-10-21 Thread Daniel van Vugt
** Summary changed:

- Screen corrupted after boot
+ [radeon] Screen corrupted (skewed stride) after boot

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

** Tags added: radeon

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

Title:
  [radeon] Screen corrupted (skewed stride) after boot

Status in mutter package in Ubuntu:
  New

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see 
pic.
  However, if I mouseover the line, colors/lines change, and if I click middle 
of screen I see the cursor changing from 'arrow' to 'vertical line where you 
can type'. I then type the login password and voilà! I get the cosmic 
cuttlefish desktop and everything works fine :-D

  I have 2 more pics for the blind/hidden login sequence

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 01:57:20 2018
  DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
  InstallationDate: Installed on 2018-10-05 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 06/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 20 22:32:39 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2

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

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


[Touch-packages] [Bug 1799035] Re: my ubuntu doesnt show resolution above 1024X800

2018-10-21 Thread Daniel van Vugt
It appears that Xorg can't get any resolution information from your
monitor, which is why it is using the default resolution of 1024x768.

Please run this command on the machine and send us the output:

  cat /sys/class/drm/*/edid

If things are working then you will see junk on the screen :)


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

** Summary changed:

- my ubuntu doesnt show resolution above 1024X800
+ my ubuntu doesnt show resolution above 1024x768

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

** Summary changed:

- my ubuntu doesnt show resolution above 1024x768
+ [SKL] My ubuntu doesn't show resolution above 1024x768

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

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

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

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

Title:
  [SKL] My ubuntu doesn't show resolution above 1024x768

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  my ubuntu doesn't show resolution above 1024X800

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 14:35:55 2018
  DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
  InstallationDate: Installed on 2017-05-01 (537 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd03/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 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/linux/+bug/1799035/+subscriptions

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


[Touch-packages] [Bug 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

** Summary changed:

- Corruption at GDM screen
+ Purple corruption on the purple login screen

** Tags added: amgdpu radeon

** Summary changed:

- Purple corruption on the purple login screen
+ [amdgpu] Purple corruption on the purple login screen

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

Title:
  [amdgpu] Purple corruption on the purple login screen

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1798797] Re: Drucker

2018-10-21 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1798533 ***
https://bugs.launchpad.net/bugs/1798533

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


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

** This bug has been marked a duplicate of bug 1798533
   Drucker

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

Title:
  Drucker

Status in Ubuntu:
  New

Bug description:
  Kompliziert ... Ich möchte nur den Drucker zum laufen bringen. Zeigt
  an, Drucker druckt nicht. Bei Ubuntu 16.4 ist alles einwandfrei
  gelaufen...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct 19 12:21:45 2018
  DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d]
  InstallationDate: Installed on 2018-03-08 (224 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 6596
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-17 (1 days ago)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EKKT25BUS
  dmi.board.name: Remore CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD MM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  dmi.product.name: 6596
  dmi.product.version: Lenovo C445
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1
  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: Wed Oct 17 11:04:23 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade

2018-10-21 Thread Daniel van Vugt
Please run this command to send us more information about the system:

  apport-collect 1799007

** Tags added: cosmic

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

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

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

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

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

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


[Touch-packages] [Bug 1798712] Re: No sound (18.10 Cosmic)

2018-10-21 Thread Daniel van Vugt
Please run this command to send us more information about the system:

  apport-collect 1798712


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

** Tags added: cosmic

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

Title:
  No sound (18.10 Cosmic)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Installed: 1:12.2-0ubuntu4

  I'm getting no sound on boot after upgrade.

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

  alsamixer runs just fine, showing that alsa is working.

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

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


[Touch-packages] [Bug 1798739] Re: All video games freeze 5-10mins into play

2018-10-21 Thread Daniel van Vugt
Next time the problem happens and you have to reboot, please use this
command to collect the logs and send us the resulting file:

  journalctl -b-1 > previous_boot.txt


** Tags added: amdgpu radeon

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  All video games freeze 5-10mins into play

Status in Ubuntu:
  Incomplete

Bug description:
  I recently installed steam on my system (Ubuntu 18.04), installed a
  couple of games and attemped to play them. About a couple of minutes
  in to playing cities: skylines, kerbal space program and mount and
  blade: warband, the screen goes blank and the computer freezes. A hard
  reboot is the only way to proceed. I have reinstalled drivers several
  times, with no change in this situation. I know it's not a specs
  problem because I ran these games on the exact same machine a couple
  of weeks ago when I had Windows 10 installed (which I have since
  removed). I think this is an xorg problem but I am not sure.

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 14:02:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 18.30-641594, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 
OEM] [1002:6611] (prog-if 00 [VGA controller])
 Subsystem: Pegatron Oland [Radeon HD 8570 / R7 240/340 OEM] [1b0a:90c4]
  InstallationDate: Installed on 2018-09-11 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard 500-002a
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=49e15d88-cf4f-45cf-abc1-8e165cbdb4e4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.15
  dmi.board.name: 2ADA
  dmi.board.vendor: Foxconn
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE3190T0P
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.15:bd02/05/2013:svnHewlett-Packard:pn500-002a:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 500-002a
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.96+git1810161830.5a3bdc~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1810170730.58a51d~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1810170730.58a51d~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.1.0+git1809261933.80514b~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1809061934.25c9a2~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1807201019.ac8f7b~oibaf~b

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

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


[Touch-packages] [Bug 1798579] Re: GUI Graphics are not working and touchpad is also not working

2018-10-21 Thread Daniel van Vugt
Also, next time please report separate bugs for each separate issue.

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

Title:
  GUI Graphics are not working and touchpad is also not working

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  It has Intel Graphics Driver but still display is not fine. 
  Touchpad drivers are also available but it is also not working. Although 
external mouse is working fine.

  Version- Ubuntu 18.04.1 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 16:46:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3964]
 Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] 
[17aa:3964]
  InstallationDate: Installed on 2018-10-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:58ea Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 062a:413e Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81DE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=773e1eb0-580f-49a5-ab82-20f86c99e160 ro i8042.reset quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.version: Lenovo ideapad 330-15IKB
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 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/1798579/+subscriptions

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


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

2018-10-21 Thread Daniel van Vugt
** Summary changed:

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

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

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

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

  and have included some output of those diagnostic steps below:

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

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

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

  Sound settings still only list dummy output.

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

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

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


[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

2018-10-21 Thread Daniel van Vugt
** Tags added: resume suspend-resume

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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


[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2018-10-21 Thread Daniel van Vugt
Confirmed, gnome-control-center is where such a setting would live. So I
am reopening that task at least to avoid people logging duplicate bugs.

However, keep in mind that mouse wheel ticks are emitted as button click
events which have no "size" that can be controlled from a central
location. This means each toolkit needs to implement the setting
separately. If it was implemented for GTK-3 then that's no guarantee
that the setting would be honoured in Chrome or Firefox because they
have their own separate toolkits.

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: gnome-control-center (Ubuntu)
 Assignee: Markus Kühne (m-kuehne) => (unassigned)

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions

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


[Touch-packages] [Bug 1410012] Re: Does not detect hotplugged storage device

2018-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Does not detect hotplugged storage device

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I plug it in, it doesn't automatically mount, is not visible in
  nautilus.  Mounts fine on system start up.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 218-3ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan 12 22:07:54 2015
  EcryptfsInUse: Yes
  HotplugNewDevices: /dev/sda /dev/sda1
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-07-09 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  MachineType: Acer TravelMate P273-MG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-8-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash vt.handoff=7
  SourcePackage: systemd
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P273-MG
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 419664] New Business Address : from the 24th October

2018-10-21 Thread Peter W Bowey
*** This bug is a duplicate of bug 418509 ***
https://bugs.launchpad.net/bugs/418509

Good Morning,

>From the *24th October 2018*, my NEW physical address is:
*4A March Avenue,*
*Hayborough,*
*Victor Harbor, SA 5211*

Please note that all email and phone numbers remain the same.

A *map* for your convenience is below:
[image: image.png]

It is business as usual,along with a better premise and workshop area.

Note that I am right behind the *new ALDI store*.
[image: image.png]

Kind Regards,
Peter
-- 
*Peter Bowey*
Web Developer, Programmer & IT Engineering

Peter Bowey Computer Solutions

4A March Avenue,
Hayborough, South Australia, Australia
Tel.: 08 8552 8630
Email: supp...@pbcomp.com.au 
Web: http://www.pbcomp.com.au/ 


Making Windows, Macintosh & Linux work for you! 

This email and any attachment is intended only for the exclusive and
confidential use of the addressee(s).

If you are not the intended recipient, any use, interference with,
disclosure or copying of this material is unauthorised and prohibited.
Notify us by a return email
 and then delete this message without copying or
publishing any privileged information contained therein.

Consider the environment before printing this e-mail.


** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/419664/+attachment/5203805/+files/image.png

** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/419664/+attachment/5203806/+files/image.png

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

Title:
  karmic is not shutting down

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Binary package hint: unattended-upgrades

  while shutting down the karmic (development branch), the system is halting 
with a blank screen and a blinking "_"
  when I pressed ctrl+alt+delete, it showed the following message

  'checking for running unattended-upgrades ... '

  it is in the same state for more than 5 min.

  Each and every time I have to do hard reset to shutdown the system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/419664/+subscriptions

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


[Touch-packages] [Bug 1799103] Re: Screen corrupted after boot

2018-10-21 Thread fiamma
** Attachment added: "clicked and cursor changes to 'type-vertical line'"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799103/+attachment/5203802/+files/2018-10-22%20Photo0037.jpg

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

Title:
  Screen corrupted after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see 
pic.
  However, if I mouseover the line, colors/lines change, and if I click middle 
of screen I see the cursor changing from 'arrow' to 'vertical line where you 
can type'. I then type the login password and voilà! I get the cosmic 
cuttlefish desktop and everything works fine :-D

  I have 2 more pics for the blind/hidden login sequence

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 01:57:20 2018
  DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
  InstallationDate: Installed on 2018-10-05 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 06/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 20 22:32:39 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2

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

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


[Touch-packages] [Bug 1799103] Re: Screen corrupted after boot

2018-10-21 Thread fiamma
** Attachment added: "mouseover changes lines/colors, cursor still arrow"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799103/+attachment/5203801/+files/2018-10-22%20Photo0036.jpg

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

Title:
  Screen corrupted after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see 
pic.
  However, if I mouseover the line, colors/lines change, and if I click middle 
of screen I see the cursor changing from 'arrow' to 'vertical line where you 
can type'. I then type the login password and voilà! I get the cosmic 
cuttlefish desktop and everything works fine :-D

  I have 2 more pics for the blind/hidden login sequence

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 01:57:20 2018
  DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
  InstallationDate: Installed on 2018-10-05 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 06/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 20 22:32:39 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2

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

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


[Touch-packages] [Bug 1799103] [NEW] Screen corrupted after boot

2018-10-21 Thread fiamma
Public bug reported:

after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see pic.
However, if I mouseover the line, colors/lines change, and if I click middle of 
screen I see the cursor changing from 'arrow' to 'vertical line where you can 
type'. I then type the login password and voilà! I get the cosmic cuttlefish 
desktop and everything works fine :-D

I have 2 more pics for the blind/hidden login sequence

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 01:57:20 2018
DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
DistroCodename: cosmic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
InstallationDate: Installed on 2018-10-05 (16 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
dmi.bios.date: 06/26/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Sat Oct 20 22:32:39 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.1-3ubuntu2

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


** Tags: amd64 apport-bug corruption cosmic third-party-packages ubuntu

** Attachment added: "screen after reboot, no login visible"
   
https://bugs.launchpad.net/bugs/1799103/+attachment/5203781/+files/2018-10-22%20Photo0035.jpg

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

Title:
  Screen corrupted after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see 
pic.
  However, if I mouseover the line, colors/lines change, and if I click middle 
of screen I see the cursor changing from 'arrow' to 'vertical line where you 
can type'. I then type the login password and voilà! I get the cosmic 
cuttlefish desktop and everything works fine :-D

  I have 2 more pics for the blind/hidden login sequence

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 01:57:20 2018
  DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
  InstallationDate: Installed on 2018-10-05 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3

[Touch-packages] [Bug 1785093] Re: RecursionError error in call_adjusted()

2018-10-21 Thread Balint Reczey
Marking as verification done based on the crash not appearing with the
fixed release.

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

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

Title:
  RecursionError error in call_adjusted()

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades may crash and stop installing security updates on 
users' system due to entering infinite loop.
   * The fix ensures terminating the recursive calls.

  [Test Case]

   * TODO / observe the crash not being reported for fixed releases on
  errors.ubuntu.com.

  [Regression Potential]

   * Unattended-upgrades now adjusts package candidates only to lower versions 
than the one originally offered by apt's resolver. This is a change in behavior 
which aligns well with the default configuration, i.e. installing packages from 
-security but not from -updates, since -updates almost always have higher 
version numbers. This change may cause using different upgrade paths when PPAs 
are involved and all packages can't be upgraded to the highest versions found 
in allowed origins, because of Conflicts: for example.
   * Unexpected regressions can cause candidate adjustments not taking place, 
but please note that autopkgtest now includes applying all outstanding security 
updates for the release thus the new code is covered, too.

  [Original Bug report]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/fa706afe2f0e04b661fe54da0a59b9fc3da50734 
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/.

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1991, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1647, in main
  cache, options, allowed_origins, blacklisted_pkgs, whitelisted_pkgs)
    File "/usr/bin/unattended-upgrade", line 1349, in calculate_upgradable_pkgs
  whitelisted_pkgs)
    File "/usr/bin/unattended-upgrade", line 1288, in try_to_upgrade
  cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed)
    File "/usr/bin/unattended-upgrade", line 212, in mark_upgrade_adjusted
  self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs)
    File "/usr/bin/unattended-upgrade", line 206, in call_adjusted
  self.call_adjusted(function, pkg, **kwargs)
    File "/usr/bin/unattended-upgrade", line 206, in call_adjusted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1785093/+subscriptions

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


[Touch-packages] [Bug 1799098] Re: Discrepancy between configuration and systemd unit

2018-10-21 Thread Arunas
/etc/init.d/isc-dhcp-server has a comment
if test -n "$INTERFACES" -a -z "$INTERFACESv4"; then
echo "DHCPv4 interfaces are no longer set by the 
INTERFACES variable in" >&2
echo "/etc/default/isc-dhcp-server.  Please use 
INTERFACESv4 instead." >&2
echo "Migrating automatically for now, but this will go 
away in the future." >&2

so I guess separate configurations for v4 and v6 is the new way. In that
case systemd service unit files have to catch up.

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

Title:
  Discrepancy between configuration and systemd unit

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  /etc/default/isc-dhcp-server file is generated with variables, 'INTERFACESv4' 
and 'INTERFACESv6', however, both /lib/system/system/isc-dhcp-server.service 
and isc-dhcp-server6.service use same INTERFACES variable on the command line.
  Not sure which is more up to date, but they obviously need to be consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1799098/+subscriptions

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


[Touch-packages] [Bug 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

2018-10-21 Thread Balint Reczey
** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/unattended-upgrades/+bug/1795696/+subscriptions

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


[Touch-packages] [Bug 1798951] Re: Unattended Upgrades failing with variable reference error

2018-10-21 Thread Balint Reczey
*** This bug is a duplicate of bug 1795696 ***
https://bugs.launchpad.net/bugs/1795696

** This bug has been marked a duplicate of bug 1795696
   
/usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

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

Title:
  Unattended Upgrades failing with variable reference error

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When running unattended-upgrades with auto-remove enabled the script
  complains about a variable being referenced before assignment:

  ```
  # unattended-upgrade -d
  [...]
  Removing unused kernel packages: linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic
  Keeping 2 auto-removable package(s) because it would also remove the 
following packages which should be kept in this step: [...]
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1991, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1791, in main
  options.verbose or options.debug, options.dry_run)
File "/usr/bin/unattended-upgrade", line 1480, in do_auto_remove
  if res:
  UnboundLocalError: local variable 'res' referenced before assignment
  ```

  This causes the apt-daily-upgrade.service to "fail" which then again
  causes no updates to be installed, which means the package does not
  fulfil its purpose:

  ```
  # systemctl status apt-daily-upgrade.service
  ● apt-daily-upgrade.service - Daily apt upgrade and clean activities
 Loaded: loaded (/lib/systemd/system/apt-daily-upgrade.service; static; 
vendor preset: enabled)
 Active: inactive (dead) since Sat 2018-10-20 06:17:09 CEST; 6h ago
   Docs: man:apt(8)
   Main PID: 32708 (code=exited, status=0/SUCCESS)

  Oct 20 06:16:00 myhost systemd[1]: Starting Daily apt upgrade and clean 
activities...
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]: Traceback (most recent call 
last):
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]:   File 
"/usr/bin/unattended-upgrade", line 1991, in 
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]: sys.exit(main(options))
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]:   File 
"/usr/bin/unattended-upgrade", line 1791, in main
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]: options.verbose or 
options.debug, options.dry_run)
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]:   File 
"/usr/bin/unattended-upgrade", line 1480, in do_auto_remove
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]: if res:
  Oct 20 06:17:09 myhost apt.systemd.daily[32708]: UnboundLocalError: local 
variable 'res' referenced before assignment
  Oct 20 06:17:09 myhost systemd[1]: Started Daily apt upgrade and clean 
activities.

  # apt-get --just-print upgrade | grep ^Inst | wc -l
  99
  ```

  Mapped to the current source code of the script within the bionic
  branch the error occurs in this line:

  https://git.launchpad.net/ubuntu/+source/unattended-upgrades/tree
  /unattended-
  upgrade?h=ubuntu/bionic&id=165a91cd44a77a03a83c64cd3812831ba26e3a80#n1418

  Used version of the package:

  ```
  # apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 1.1ubuntu1.18.04.5
Candidate: 1.1ubuntu1.18.04.5
Version table:
   *** 1.1ubuntu1.18.04.5 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
  500 http://mirror.hetzner.de/ubuntu/packages bionic-updates/main 
amd64 Packages
  500 http://mirror.hetzner.de/ubuntu/packages bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  500 http://mirror.hetzner.de/ubuntu/packages bionic/main amd64 
Packages
  500 http://mirror.hetzner.de/ubuntu/packages bionic/main i386 Packages
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1798951/+subscriptions

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


[Touch-packages] [Bug 1799098] [NEW] Discrepancy between configuration and systemd unit

2018-10-21 Thread Arunas
Public bug reported:

/etc/default/isc-dhcp-server file is generated with variables, 'INTERFACESv4' 
and 'INTERFACESv6', however, both /lib/system/system/isc-dhcp-server.service 
and isc-dhcp-server6.service use same INTERFACES variable on the command line.
Not sure which is more up to date, but they obviously need to be consistent.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Discrepancy between configuration and systemd unit

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  /etc/default/isc-dhcp-server file is generated with variables, 'INTERFACESv4' 
and 'INTERFACESv6', however, both /lib/system/system/isc-dhcp-server.service 
and isc-dhcp-server6.service use same INTERFACES variable on the command line.
  Not sure which is more up to date, but they obviously need to be consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1799098/+subscriptions

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


[Touch-packages] [Bug 1771962] Re: hanging at boot for about 30 seconds since upgrade to bionic

2018-10-21 Thread DiagonalArg
I also applies when you have a swap partition and root is luks.

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

Title:
  hanging at boot for about 30 seconds since upgrade to bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, even if the swap 
device is ephemeral (i.e. swap encrypted with a random key).  This adds an 
inappropriate 30-second boot delay to any system with randomly-crypted swap, 
which includes any system that was installed with encrypted home directories in 
earlier releases.

  [Test case]
  1. Install the ecryptfs-utils package.
  2. Enable encrypted swap by running 'sudo ecryptfs-setup-swap'.
  3. Run 'update-initramfs -u' to regenerate the initramfs.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language.  An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users.  A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A `dmesg` 
shows

  ```
  [3.407230] clocksource: Switched to clocksource tsc
  [   34.632583] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  ```

  This is 100% reproducable and is always 30s minimum. I do not know in
  which package to report this properly – please excuse me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: i3
  Date: Fri May 18 09:40:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-03 (1444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized

   This incident has been reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771962/+subscriptions

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


[Touch-packages] [Bug 1799079] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 - "Possible missi

2018-10-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1 - "Possible missing firmware ... for module amdgpu"

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Trying to clean up after a 16.04 -> 18.04 upgrade, I removed lvm2,
  which I'm honestly still not sure is necessary for LVM support, but
  resulted in many lines of the form during "processing of initramfs-
  tools":

  W: Possible missing firmware /lib/firmware/amdgpu/vegam_smc.bin for
  module amdgpu

  Not sure even if that's the main issue, but nothing else looks out of
  place. Here's a more complete transcript:

  Setting up lvm2 (2.02.176-4.1ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
  invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
  ● lvm2-lvmetad.service - LVM2 metadata daemon
 Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
 Active: inactive (dead) since Sun 2018-10-21 14:50:29 EDT; 3min 29s ago
   Docs: man:lvmetad(8)
   Main PID: 512 (code=exited, status=0/SUCCESS)

  Oct 21 14:50:29 monolith systemd[1]: Stopping LVM2 metadata daemon...
  Oct 21 14:50:29 monolith systemd[1]: Stopped LVM2 metadata daemon.
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for initramfs-tools (0.130ubuntu3.5) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-36-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec2.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_me.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_pfp.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_ce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma1.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_uvd.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_vce.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vegam_smc.bin for module 
amdgpu
  Errors were encountered while processing:
   lvm2
  Press Return to continue, 'q' followed by Return to quit.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   libreadline5:amd64: Install
   lvm2:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Oct 21 14:53:42 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-12 (313 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  So

[Touch-packages] [Bug 1799079] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 - "Possible mis

2018-10-21 Thread Dav Clark
Public bug reported:

Trying to clean up after a 16.04 -> 18.04 upgrade, I removed lvm2, which
I'm honestly still not sure is necessary for LVM support, but resulted
in many lines of the form during "processing of initramfs-tools":

W: Possible missing firmware /lib/firmware/amdgpu/vegam_smc.bin for
module amdgpu

Not sure even if that's the main issue, but nothing else looks out of
place. Here's a more complete transcript:

Setting up lvm2 (2.02.176-4.1ubuntu3) ...
update-initramfs: deferring update (trigger activated)
Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
● lvm2-lvmetad.service - LVM2 metadata daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
   Active: inactive (dead) since Sun 2018-10-21 14:50:29 EDT; 3min 29s ago
 Docs: man:lvmetad(8)
 Main PID: 512 (code=exited, status=0/SUCCESS)

Oct 21 14:50:29 monolith systemd[1]: Stopping LVM2 metadata daemon...
Oct 21 14:50:29 monolith systemd[1]: Stopped LVM2 metadata daemon.
dpkg: error processing package lvm2 (--configure):
 installed lvm2 package post-installation script subprocess returned error exit 
status 1
Processing triggers for initramfs-tools (0.130ubuntu3.5) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-36-generic
W: Possible missing firmware /lib/firmware/amdgpu/vega12_gpu_info.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_asd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sos.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_ce.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_sdma.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_uvd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_uvd.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_vce.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_vce.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega12_smc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vegam_smc.bin for module 
amdgpu
Errors were encountered while processing:
 lvm2
Press Return to continue, 'q' followed by Return to quit.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: lvm2 2.02.176-4.1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 libreadline5:amd64: Install
 lvm2:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Oct 21 14:53:42 2018
ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2017-12-12 (313 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
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.3ubuntu0.1
SourcePackage: lvm2
Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-10-09 (12 days ago)

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed
  lvm2 

[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

2018-10-21 Thread Jondice
*** This bug is a duplicate of bug 1768610 ***
https://bugs.launchpad.net/bugs/1768610

Can confirm that the fix from xjbhenry worked for me as well (previously
the system was 16.04, then 17.?? and then upgraded to 18.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/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 1799077] [NEW] package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2018-10-21 Thread Jari Kero
Public bug reported:

I upgraded to 18.04.1 LTS and after booting the system having this
error.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.5
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sun Oct 21 17:13:17 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-05-05 (534 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
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.3ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-10-21 (0 days ago)

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

Title:
  package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I upgraded to 18.04.1 LTS and after booting the system having this
  error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Oct 21 17:13:17 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-05-05 (534 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1799077/+subscriptions

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


[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

2018-10-21 Thread Joao Meira
** Also affects: apport
   Importance: Undecided
   Status: New

** No longer affects: apport

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade

2018-10-21 Thread Tessa
Digging into the pulse config on 18.10, it looks like instead of using
the daemon mode it's trying to setup up some sort of IPC socket, but
this isn't getting run correctly:

tessa@viper:~$ systemctl start pulseaudio.socket
tessa@viper:~$ systemctl status pulseaudio.socket
● pulseaudio.socket - Sound System
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.socket; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Sun 2018-10-21 10:37:45 PDT; 4s ago
   └─ ConditionUser=!root was not met
   Listen: /run/pulse/native (Stream)

note that it requires a non-root user, but running as more normal user
for some reason evaluates to root and fails.

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  New

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

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

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

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


[Touch-packages] [Bug 1799069] [NEW] 18.10 regression: guake resets font choice after every login

2018-10-21 Thread Tessa
Public bug reported:

I've got guake set to use my system monospaced font (which is Ubuntu
Mono). however, on every fresh login, it resets to some other font until
I go into the guake prefs and unckeck then recheck the "Use the system
fixed width font" box. It seems to remember it's checked, but it just
doesn't correctly use it on startup.

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

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

Title:
  18.10 regression: guake resets font choice after every login

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I've got guake set to use my system monospaced font (which is Ubuntu
  Mono). however, on every fresh login, it resets to some other font
  until I go into the guake prefs and unckeck then recheck the "Use the
  system fixed width font" box. It seems to remember it's checked, but
  it just doesn't correctly use it on startup.

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

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


[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade

2018-10-21 Thread Tessa
hmmm. I tried that, but no dice for me. pulse starts in a terminal, but
nothing in my session sees a sound device still. for the one started in
a terminal, it doesn't respond to kill signals, and needs to be kill
-9d.

I suspect the "/usr/bin/pulseaudio --daemonize=no" process is just
grabbing the soundcard and so running the second one does nothing
useful. running the X11 wrapper script errors out:

$ start-pulseaudio-x11
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

Given that pacmd explicitly complains about there being no daemon
running, the fact that systemd is running pulseaudio with --daemonize=no
is probably a bad thing.

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  New

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

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

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

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


[Touch-packages] [Bug 1799064] [NEW] Bluetooth refuses to power on after cosmic upgrade

2018-10-21 Thread yitzhaq
Public bug reported:

After upgrading from bionic to cosmic, Bluetooth has stopped working. It
has worked fine for several versions before.

Error message from syslog is:

Failed to set mode: Failed (0x03)

Which according to various random forum posts seems to suggest the
device is not powering on.

Powering on manually also does not work:

% bluetoothctl
Agent registered
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Failed

And results in the same set mode failure getting logged again in syslog.
hciconfig reports the device as down:

% sudo hciconfig
hci0:   Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

And, again, it refuses to power on:

% sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

rfkill does not appear to be blocking it:

% rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

And systemd-rfkill.service is masked:

~ % sudo systemctl status systemd-rfkill.service
● systemd-rfkill.service
   Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
[..]

The system does not have tlp installed.

I have tried numerous reboots, power offs, and moving the USB Bluetooth
adapter to different ports, with no change in result. I have also tried
unloading and loading btusb.

The adapter is a cheap noname thing off of eBay, I trust the system
report will provide every possibly interesting detail about it.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Sun Oct 21 17:22:28 2018
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK Computer INC. EB1501P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0501
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: EB1501P
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.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Eee Family
dmi.product.name: EB1501P
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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


** Tags: amd64 bluetooth cosmic

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

Title:
  Bluetooth refuses to power on after cosmic upgrade

Status in bluez package in Ubuntu:
  New

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Uni

[Touch-packages] [Bug 1799062] [NEW] Tried to install driver, but both printer and scanner don't work. Exact model: CANON i-sensys MF8230Cn

2018-10-21 Thread lauris
Public bug reported:

"lsmod | grep usb" gives:
usblp  20480  0
usbhid 49152  0
hid   118784  2 hid_generic,usbhid

"tail -f /var/log/syslog" gives:
Oct 21 17:44:59 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [29061.138363] 
audit: type=1400 audit(1540133099.706:36): apparmor="ALLOWED" 
operation="file_perm" profile="libreoffice-oopslash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_4a5ac26629998095145aabf6e58c38e6" 
pid=4848 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
Oct 21 17:44:59 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [29061.138366] 
audit: type=1400 audit(1540133099.706:37): apparmor="ALLOWED" 
operation="file_perm" profile="libreoffice-oopslash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_4a5ac26629998095145aabf6e58c38e6" 
pid=4848 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
Oct 21 18:01:14 vasaramaja-HP-Compaq-6200-Pro-SFF-PC systemd[1]: Started Run 
anacron jobs.
Oct 21 18:01:14 vasaramaja-HP-Compaq-6200-Pro-SFF-PC anacron[5675]: Anacron 2.3 
started on 2018-10-21
Oct 21 18:01:14 vasaramaja-HP-Compaq-6200-Pro-SFF-PC anacron[5675]: Normal exit 
(0 jobs run)
Oct 21 18:02:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30124.951667] usb 
1-1.5: USB disconnect, device number 5
Oct 21 18:02:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30124.954199] 
usblp0: removed
Oct 21 18:02:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.1
Oct 21 18:02:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5
Oct 21 18:02:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC colord-sane[5682]: failed 
to receive list of devices: Failed to connect to missing device 
/org/freedesktop/ColorManager/devices/sysfs_Canon_Inc__MF8200C_Series
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.701662] usb 
1-1.6: new high-speed USB device number 6 using ehci-pci
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.822317] usb 
1-1.6: New USB device found, idVendor=04a9, idProduct=2779
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.822321] usb 
1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.822323] usb 
1-1.6: Product: MF8200C Series
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.822325] usb 
1-1.6: Manufacturer: Canon,Inc.
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.822328] usb 
1-1.6: SerialNumber: 2c9efc50cf55
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30179.827137] 
usblp 1-1.6:1.1: usblp0: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 
0x04A9 pid 0x2779
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC systemd[1]: Starting 
Configure Plugged-In Printer...
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC 
udev-configure-printer[5699]: add usb-001-006
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'bind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'bind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC 
udev-configure-printer[5699]: device devpath is 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6
Oct 21 18:03:38 vasaramaja-HP-Compaq-6200-Pro-SFF-PC 
udev-configure-printer[5699]: MFG:Canon MDL:MF8200C Series SERN:- 
serial:2c9efc50cf55
Oct 21 18:03:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30184.969000] 
usblp0: removed
Oct 21 18:03:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1
Oct 21 18:03:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'bind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1
Oct 21 18:03:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1
Oct 21 18:03:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC kernel: [30184.982603] 
usblp 1-1.6:1.1: usblp0: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 
0x04A9 pid 0x2779
Oct 21 18:03:43 vasaramaja-HP-Compaq-6200-Pro-SFF-PC upowerd[1574]: unhandled 
action 'bind' on /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.1
Oct 21 18:03:45 vasaramaja-HP-Compaq-6200-Pro-SFF-PC 
udev-configure-printer[5699]: URI contains USB serial number
Oct 21 18:03:45 vasaramaja-HP-Compaq-6200-Pro-SFF-PC 
udev-configure-printer[5699]: URI match: 
usb://Canon/MF8200C%20Series?serial=2c9efc50cf55&interface=1
Oct 21 18:03:45 vasaramaja-HP-Compaq-6200-Pro-SFF-PC 
udev-configure-printer[5699]: URI of detected printer: 
usb://Canon/MF8200C%20Series?serial=2c9efc

[Touch-packages] [Bug 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer
Also note that the screen jitters at the GDM login screen.

My video card does not exhibit have any of these issues when I boot into
Windows 10.

Sometimes logging in doesn't fix the jittering so I reboot into Windows
10.

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer
** Attachment added: "the bright box"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203630/+files/20181020_172739.jpg

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1799061] Re: Corruption at GDM screen

2018-10-21 Thread Scott Palmer
** Attachment added: "the horizontal band"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203629/+files/20181020_172736.jpg

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Touch-packages] [Bug 1799061] [NEW] Corruption at GDM screen

2018-10-21 Thread Scott Palmer
Public bug reported:

Video does not appear to be getting set correctly for GDM but seems
"corrected" after I login.

I have attached some screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 21 08:01:42 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
InstallationDate: Installed on 2018-10-20 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug corruption cosmic ubuntu wayland-session

** Attachment added: "20181020_172728.jpg"
   
https://bugs.launchpad.net/bugs/1799061/+attachment/5203613/+files/20181020_172728.jpg

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

Title:
  Corruption at GDM screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Video does not appear to be getting set correctly for GDM but seems
  "corrected" after I login.

  I have attached some screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 08:01:42 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 550 
640SP / RX 560/560X] [1462:8a91]
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=31f5be02-c37e-43e6-96f2-8c912726514e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  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.:bvr2104:bd08

[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade

2018-10-21 Thread Victor Perin
I've manage to get sound working again running:

```
$ sudo apt install --reinstall pulseaudio
$ pulseaudio
```

And at every boot I need to open a terminal for pulseaudio. (It still
doesn't start with the system).

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  New

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

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

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

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


[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade

2018-10-21 Thread Victor Perin
Same problem here.
Upgraded ubuntu from 18.04.

$ pacmd list-cards
No PulseAudio daemon running, or not running as session daemon.

Does anyone know a way to fix it?

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

Title:
  no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  New

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

  Not sure what happened, but this is a major regression and needs to be
  fixed. Note that this isn't the same as the bug with Timidity taking
  exclusive soundcard access
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
  I don't have any timidity packages installed.

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

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


[Touch-packages] [Bug 1797941] Re: package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  package installation failed, inconsistent content

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tzdata 2018e-0ubuntu0.18.04
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Mon Oct 15 20:16:55 2018
  DuplicateSignature:
   package:tzdata:2018e-0ubuntu0.18.04
   Setting up libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.3) ...
   dpkg: error processing package tzdata (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: tzdata
  Title: package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1799048] Re: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-10-21 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libffi package in Ubuntu:
  New

Bug description:
  1 st time system get restart

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libffi6:i386 3.2.1-8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Oct 20 23:57:30 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  DuplicateSignature:
   package:libffi6:i386:3.2.1-8
   Setting up vlc-plugin-visualization:amd64 (3.0.3-1-1ubuntu1) ...
   dpkg: error processing package libffi6:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: libffi
  Title: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1799048] [NEW] package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-10-21 Thread Satya Narayan Sahu
Public bug reported:

1 st time system get restart

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libffi6:i386 3.2.1-8
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Oct 20 23:57:30 2018
Dependencies:
 gcc-8-base 8.2.0-1ubuntu2~18.04
 libc6 2.27-3ubuntu1
 libgcc1 1:8.2.0-1ubuntu2~18.04
DuplicateSignature:
 package:libffi6:i386:3.2.1-8
 Setting up vlc-plugin-visualization:amd64 (3.0.3-1-1ubuntu1) ...
 dpkg: error processing package libffi6:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-10-20 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: libffi
Title: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package bionic i386

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

Title:
  package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libffi package in Ubuntu:
  New

Bug description:
  1 st time system get restart

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libffi6:i386 3.2.1-8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Oct 20 23:57:30 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  DuplicateSignature:
   package:libffi6:i386:3.2.1-8
   Setting up vlc-plugin-visualization:amd64 (3.0.3-1-1ubuntu1) ...
   dpkg: error processing package libffi6:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: libffi
  Title: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1799032] Re: Update to libcap 2.26

2018-10-21 Thread Hans Joachim Desserud
** Bug watch added: Debian Bug tracker #911509
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911509

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

** Tags added: upgrade-software-version

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

Title:
  Update to libcap 2.26

Status in libcap2 package in Ubuntu:
  New
Status in libcap2 package in Debian:
  Unknown

Bug description:
  Hey everyone,

  We recently pushed support for ambient capabilities and namespaces filesystem 
capabilities
  to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have released 
a version 2.26
  of libcap2. Note that libcap2 has moved to a new location [2]

  The 2.26 release can be downloaded from [3].

  Please update to the new version!

  [1]: 
https://sites.google.com/site/fullycapable/release-notes-for-libcap/pre-releasenotesfor226
  [2]: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/
  [3]: 
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/snapshot/libcap-2.26.tar.gz

  Thanks!
  Christian

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

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


[Touch-packages] [Bug 1799038] [NEW] Ubuntu 18.10 does not suspend on lid close

2018-10-21 Thread Wolf Rogner
Public bug reported:

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

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

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

Seems a regression.

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

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

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Ubuntu 18.10 does not suspend on lid close

Status in systemd package in Ubuntu:
  New

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

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

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

  Seems a regression.

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

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

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

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


[Touch-packages] [Bug 1799035] [NEW] my ubuntu doesnt show resolution above 1024X800

2018-10-21 Thread Bhushan
Public bug reported:

my ubuntu doesn't show resolution above 1024X800

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 21 14:35:55 2018
DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
InstallationDate: Installed on 2017-05-01 (537 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
 Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
dmi.bios.date: 03/15/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H110M-S2-CF
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: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd03/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  my ubuntu doesnt show resolution above 1024X800

Status in xorg package in Ubuntu:
  New

Bug description:
  my ubuntu doesn't show resolution above 1024X800

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 14:35:55 2018
  DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
  InstallationDate: Installed on 2017-05-01 (537 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2-CF
  dmi.board.

[Touch-packages] [Bug 1799032] [NEW] Update to libcap 2.26

2018-10-21 Thread Christian Brauner
Public bug reported:

Hey everyone,

We recently pushed support for ambient capabilities and namespaces filesystem 
capabilities
to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have released a 
version 2.26
of libcap2. Note that libcap2 has moved to a new location [2]

The 2.26 release can be downloaded from [3].

Please update to the new version!

[1]: 
https://sites.google.com/site/fullycapable/release-notes-for-libcap/pre-releasenotesfor226
[2]: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/
[3]: 
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/snapshot/libcap-2.26.tar.gz

Thanks!
Christian

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

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

Title:
  Update to libcap 2.26

Status in libcap2 package in Ubuntu:
  New

Bug description:
  Hey everyone,

  We recently pushed support for ambient capabilities and namespaces filesystem 
capabilities
  to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have released 
a version 2.26
  of libcap2. Note that libcap2 has moved to a new location [2]

  The 2.26 release can be downloaded from [3].

  Please update to the new version!

  [1]: 
https://sites.google.com/site/fullycapable/release-notes-for-libcap/pre-releasenotesfor226
  [2]: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/
  [3]: 
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/snapshot/libcap-2.26.tar.gz

  Thanks!
  Christian

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

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


[Touch-packages] [Bug 1786625] Re: "find" command throws nonsense error message

2018-10-21 Thread Andreas Metzler
Hello,

If you run "find . -name *.txt" in a directory containing foo.txt and
bar.txt then the shell expands *.txt before executing find, i.e. you
would be running "find . -name foo.txt bar.txt" which produces a syntax
error. Either quote ('*.txt') or escape (\*.txt) the argument.

Closing.

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

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

Title:
  "find" command throws nonsense error message

Status in findutils package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Run this command from a terminal:
  $ find . -name *.txt

  Expected result:
  It should list all the files found in the current directory or any descendant 
directory whose name ends in ".txt". It may or may not find matching files, 
depending on whether there are or there aren't.
  If there's something wrong in my command, then it should ALWAYS consistently 
issue a sensible error message explaining what's wrong with my command, and 
that should happen regardless of the contents of the current directory.

  Observed results:
  If there are no .txt files to be found, it behaves as expected (i.e., no 
results, no error message).
  If there are files ending in .txt, sometimes it behaves as expected, showing 
the results.

  If, however, there are files ending in ".txt" with dashes ("-") or spaces (" 
") in the filename, AND there is more than one file that matches the criteria, 
then it displays this completely nonsensical error message:
  
  find: paths must precede expression: .txt
  Usage: find [-H] [-L] [-P] [-Olevel] [-D 
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
  
  where "X.txt" is  an actual filename of a matching file.

  For example, this will reproduce the issue:
  
  $ echo "lalala" > aaa.txt
  $ echo "lololo" > foo-bar.txt
  $ find . -name *.txt
  find: paths must precede expression: foo-bar.txt
  Usage: find [-H] [-L] [-P] [-Olevel] [-D 
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-131-generic 4.4.0-131.157
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2898 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Aug 11 17:30:54 2018
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (1764 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-131-generic N/A
   linux-backports-modules-4.4.0-131-generic  N/A
   linux-firmware 1.157.20
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1793668] Re: xargs gives "[: err: unexpected operator" on Ubuntu but not Centos

2018-10-21 Thread Andreas Metzler
Hello,

tst is a shell script that does specify which interpreter should be used
and therefore the system falls back to try /bin/sh.

However the script is using bash extensions ([ "$1" == "" ]) which won't
work with *any* sh-type shell. Debian is using dash as /bin/sh and there
an error is thrown, Centos is probably using bash.

So this is not a bug but a user error. If you want to use bash-extension
you'll need to take care that the script runs under bash by using a
correct #!-line.

Closing.

** Changed in: findutils (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  xargs gives "[: err: unexpected operator" on Ubuntu but not Centos

Status in findutils package in Ubuntu:
  Invalid

Bug description:
  cd /tmp
  rm -Rf tst err
  echo 'if [ "$1" == "" ]; then echo "empty"; else cat $1; fi' > tst
  chmod +x tst
  echo "a" > err
  ls err | xargs ./tst # ./tst: 1: [: err: unexpected operator
  ./tst err # works fine, outputs 'a'

  On Ubuntu the error will be shown, on Centos it won't. The error looks
  to be incorrect.

  $ lsb_release -rd
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  $ xargs --version
  xargs (GNU findutils) 4.7.0-git
  Copyright (C) 2017 Free Software Foundation, Inc.

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

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