date:20171030

Feedback

Since i was not able to get a login prompt, i've booted with an Artful
install, which also use the same /home partition. Then i have tryied to
boot again with Bionic, and that time all is fine, except that only
error:

 systemd-udevd.service: Job systemd-hwdb-update.service/start deleted to
break ordering cycle starting with systemd-udevd.service/start

so the reported problem seems a transitional conflict with the shared
configs.

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 599439] Re: evince crashed with SIGSEGV in JPXStream::readTilePartData()

On Ubuntu 17.04 "Zesty Zapus", the attached file doesn't crash evince,
but most of the page is not displayed.  Firefox 56.0 doesn't display any
of it. Possibly a broken document?

evince 3.24.0-0ubuntu1.1
poppler 0.48.0-2ubuntu2.4

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

Title:
  evince crashed with SIGSEGV in JPXStream::readTilePartData()

Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  
  evince crashes with the following valgrind output when opening the attached 
file.

  $ valgrind evince sample.pdf
  ==12903== Memcheck, a memory error detector.
  ==12903== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
  ==12903== Using LibVEX rev 1884, a library for dynamic binary translation.
  ==12903== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP.
  ==12903== Using valgrind-3.4.1-Debian, a dynamic binary instrumentation 
framework.
  ==12903== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al.
  ==12903== For more details, rerun with: -v
  ==12903== 
  Error: PDF file is damaged - attempting to reconstruct xref table...
  ==12903== Thread 2:
  ==12903== Use of uninitialised value of size 4
  ==12903==at 0x4E1E47F: JPXStream::readTilePartData(unsigned int, unsigned 
int, int) (JPXStream.cc:1951)
  ==12903==by 0x4E1F5CD: JPXStream::readTilePart() (JPXStream.cc:1924)
  ==12903==by 0x4E20766: JPXStream::readCodestream(unsigned int) 
(JPXStream.cc:1366)
  ==12903==by 0x4E225C9: JPXStream::readBoxes() (JPXStream.cc:735)
  ==12903==by 0x4E227EC: JPXStream::reset() (JPXStream.cc:272)
  ==12903==by 0x4EA33E2: ImageStream::reset() (Stream.cc:419)
  ==12903==by 0x4739923: CairoOutputDev::drawSoftMaskedImage(GfxState*, 
Object*, Stream*, int, int, GfxImageColorMap*, Stream*, int, int, 
GfxImageColorMap*) (CairoOutputDev.cc:1485)
  ==12903==by 0x4E5C9B5: Gfx::doImage(Object*, Stream*, int) (Gfx.cc:3857)
  ==12903==by 0x4E60894: Gfx::opXObject(Object*, int) (Gfx.cc:3526)
  ==12903==by 0x4E52AB9: Gfx::execOp(Object*, Object*, int) (Gfx.cc:771)
  ==12903==by 0x4E5307E: Gfx::go(int) (Gfx.cc:642)
  ==12903==by 0x4E55AEE: Gfx::display(Object*, int) (Gfx.cc:611)
  ==12903== 
  ==12903== Use of uninitialised value of size 4
  ==12903==at 0x4E1E48A: JPXStream::readTilePartData(unsigned int, unsigned 
int, int) (JPXStream.cc:1952)
  ==12903==by 0x4E1F5CD: JPXStream::readTilePart() (JPXStream.cc:1924)
  ==12903==by 0x4E20766: JPXStream::readCodestream(unsigned int) 
(JPXStream.cc:1366)
  ==12903==by 0x4E225C9: JPXStream::readBoxes() (JPXStream.cc:735)
  ==12903==by 0x4E227EC: JPXStream::reset() (JPXStream.cc:272)
  ==12903==by 0x4EA33E2: ImageStream::reset() (Stream.cc:419)
  ==12903==by 0x4739923: CairoOutputDev::drawSoftMaskedImage(GfxState*, 
Object*, Stream*, int, int, GfxImageColorMap*, Stream*, int, int, 
GfxImageColorMap*) (CairoOutputDev.cc:1485)
  ==12903==by 0x4E5C9B5: Gfx::doImage(Object*, Stream*, int) (Gfx.cc:3857)
  ==12903==by 0x4E60894: Gfx::opXObject(Object*, int) (Gfx.cc:3526)
  ==12903==by 0x4E52AB9: Gfx::execOp(Object*, Object*, int) (Gfx.cc:771)
  ==12903==by 0x4E5307E: Gfx::go(int) (Gfx.cc:642)
  ==12903==by 0x4E55AEE: Gfx::display(Object*, int) (Gfx.cc:611)
  ==12903== 
  ==12903== Conditional jump or move depends on uninitialised value(s)
  ==12903==at 0x4E1E509: JPXStream::readTilePartData(unsigned int, unsigned 
int, int) (JPXStream.cc:1977)
  ==12903==by 0x4E1F5CD: JPXStream::readTilePart() (JPXStream.cc:1924)
  ==12903==by 0x4E20766: JPXStream::readCodestream(unsigned int) 
(JPXStream.cc:1366)
  ==12903==by 0x4E225C9: JPXStream::readBoxes() (JPXStream.cc:735)
  ==12903==by 0x4E227EC: JPXStream::reset() (JPXStream.cc:272)
  ==12903==by 0x4EA33E2: ImageStream::reset() (Stream.cc:419)
  ==12903==by 0x4739923: CairoOutputDev::drawSoftMaskedImage(GfxState*, 
Object*, Stream*, int, int, GfxImageColorMap*, Stream*, int, int, 
GfxImageColorMap*) (CairoOutputDev.cc:1485)
  ==12903==by 0x4E5C9B5: Gfx::doImage(Object*, Stream*, int) (Gfx.cc:3857)
  ==12903==by 0x4E60894: Gfx::opXObject(Object*, int) (Gfx.cc:3526)
  ==12903==by 0x4E52AB9: Gfx::execOp(Object*, Object*, int) (Gfx.cc:771)
  ==12903==by 0x4E5307E: Gfx::go(int) (Gfx.cc:642)
  ==12903==by 0x4E55AEE: Gfx::display(Object*, int) (Gfx.cc:611)
  ==12903== 
  ==12903== Use of uninitialised value of size 4
  ==12903==at 0x4E1E515: JPXStream::readTilePartData(unsigned int, unsigned 
int, int) (JPXStream.cc:1978)
  ==12903==by 0x4E1F5CD: JPXStream::readTilePart() (JPXStream.cc:1924)
  ==12903==by 0x4E20766: JPXStream::readCodestream(unsigned int) 
(JPXStream.cc:1366)
  ==12903==by 0x4E225C9: JPXStream::readBoxes() (JPXStream.cc:735)
  ==12903==by 0x4E227EC: JPXStream::reset()

[Touch-packages] [Bug 406826] Re: evince-thumbnailer crashed with SIGSEGV in DCTStream::reset()

** Changed in: poppler (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  evince-thumbnailer crashed with SIGSEGV in DCTStream::reset()

Status in Poppler:
  Invalid
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  After i created a new pdf file, i had this crash and no preview

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/evince-thumbnailer
  Package: evince 2.26.1-0ubuntu1
  ProcCmdline: evince-thumbnailer -s 128 
file:///home/username/MyDownloads/Farmaceutica2-2x2.pdf 
/tmp/.gnome_desktop_thumbnail.K83UXU
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? () from /usr/lib/libjpeg.so.62
   DCTStream::reset () from /usr/lib/libpoppler.so.4
   ImageStream::reset () from /usr/lib/libpoppler.so.4
   CairoOutputDev::drawImage ()
   Gfx::doImage () from /usr/lib/libpoppler.so.4
  Title: evince-thumbnailer crashed with SIGSEGV in DCTStream::reset()
  Uname: Linux 2.6.28-13-generic i686
  UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev 
sambashare scanner tape video

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

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

[Touch-packages] [Bug 1726647] Re: crash reports still sent to LP on artful

This bug was fixed in the package apport - 2.20.7-0ubuntu3.1

---
apport (2.20.7-0ubuntu3.1) artful; urgency=medium

  * etc/apport/crashdb.conf: Disable Launchpad crash reports for 17.10
release. (LP: #1726647)

 -- Brian Murray   Tue, 24 Oct 2017 08:22:21 -0700

** Changed in: apport (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  crash reports still sent to LP on artful

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  /etc/apport/crashdb.conf was not modified to stop sending crash
  reports to Launchpad for Ubuntu 17.10, since it was released they
  should only be going to errors.ubuntu.com.

  The problem_types field needs to change to ['Bug', 'Package'].

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 17:43:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  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/1726647/+subscriptions

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

[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.

2017-10-30 Thread Ferdaus

I have something to report almost everyday via the system since eI'd
upgraded to 17.10, but I am not very much sure what they are. I submit
these problem/bug report in the hope that it will help the system/ OS
Engineers/ Programmers to rectify these bugs

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

Title:
  cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368:
  __spawnix: Assertion `ec >= 0' failed.

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Confirmed

Bug description:
  1. Error: Package/cups-daemon2.2.4-7 (mutilated)
  2. compiz-core/tmp/apport_core_q_vnqis (corrupted)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Fri Sep 22 22:16:18 2017
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2017-05-27 (118 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-K D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1728773] Re: [235.2ubuntu1] systemd upgrade set a read only filesystem

2017-10-30 Thread Steve Langasek

** Tags removed: regression-update

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1713808] Re: please switch the default bug category to something else than "Display"

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

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

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

Title:
  please switch the default bug category to something else than
  "Display"

Status in apport package in Ubuntu:
  Expired

Bug description:
  People use ubuntu-bug to file bugs, and they get a dialog which has
  the default bug category selected as "Display (X.org)". Looks like
  many don't bother to change that, so please switch the default to
  "Other problem" so that 'xorg' doesn't get to be the default target
  for poor quality bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
  CurrentDesktop: Unity
  Date: Tue Aug 29 22:55:21 2017
  InstallationDate: Installed on 2016-01-12 (595 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  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/1713808/+subscriptions

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

[Touch-packages] [Bug 286175] Re: evince crashed with SIGSEGV in FcConfigSubstituteWithPat()

Official support for Ubuntu 11.04 "Natty Narwhal" and earlier releases
has ended.  Is this still occurring on Ubuntu 17.10 "Artful Aardvark"?

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

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

Title:
  evince crashed with SIGSEGV in FcConfigSubstituteWithPat()

Status in cairo package in Ubuntu:
  Invalid
Status in fontconfig package in Ubuntu:
  Incomplete
Status in cairo source package in Intrepid:
  Won't Fix
Status in fontconfig source package in Intrepid:
  Won't Fix

Bug description:
  Binary package hint: evince

  Opening a pdf document from the web.

  Crashed before it was able to render anything.

  Link: http://www.copyright.gov/history/1790act.pdf

  STEPS TO REPRODUCE:
  1. Make sure GNOME is running, evince gets fontconfig info from another 
library (it doesn't access FC directly)
  2. Open evince on any file, then close it.
  3. Install or remove a font (try mstcorefonts)
  4. Open evince with a document (i.e., try the link provided above). It SHOULD 
crash.

  ProblemType: Crash
  Architecture: amd64
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/evince
  NonfreeKernelModules: nvidia
  Package: evince 2.24.0-0ubuntu2
  ProcAttrCurrent: unconfined
  ProcCmdline: evince 
file:///home/username/Documents/Grad_School/SI-519/SI519%20-%20SyllabusF2008.%20Aug.%2026.pdf
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   FcConfigSubstituteWithPat ()
   GlobalParams::getDisplayFont (this=0x2989190, 
   CairoFont::create (gfxFont=0x7fc1eeb14f70, 
   CairoFontEngine::getFont (this=0x7fc1eea017e0, 
   CairoOutputDev::updateFont (this=0x7fc1eea020a0,
  Title: evince crashed with SIGSEGV in FcConfigSubstituteWithPat()
  Uname: Linux 2.6.27-7-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
sambashare video

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

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

[Touch-packages] [Bug 1527942] Re: pdfimprt crash libreoffice 5.0.3 when import a pdf in libreoffice

Is this still happening on Ubuntu 17.10 "Artful Aardvark"? If so, please
attach a sample PDF file to this bug report.

** Tags added: trusty

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

** Package changed: rsyslog (Ubuntu) => libreoffice (Ubuntu)

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

Title:
  pdfimprt crash libreoffice 5.0.3 when import a pdf in libreoffice

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have installed libreoffice 5.0.3 on  ubuntu 14.04 LTS 64 bit throw the
  libreoffice official ppa.

  It seems that libreoffice crach when I try to use pdfimport like this

  Open libreoffice 5.03
  chose file open
  chose a pdf on my disk and try to open a file
  Actual result

  Libreoffice crach, show an error message and reovery documents

  Could you help me please ?

  Best regards

  mparchet

  
  My configuration

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  libreoffice-pdfimport
  libreoffice:
Installed: 1:5.0.3~rc2-0ubuntu1~trusty2
Candidate: 1:5.0.3~rc2-0ubuntu1~trusty2
Version table:
   *** 1:5.0.3~rc2-0ubuntu1~trusty2 0
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-0/ubuntu/ 
trusty/main amd64 Packages
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:4.2.8-0ubuntu3 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
   1:4.2.3~rc3-0ubuntu2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  apt-cache policy libreoffice-pdfimport
  libreoffice-pdfimport:
Installed: 1:5.0.3~rc2-0ubuntu1~trusty2
Candidate: 1:5.0.3~rc2-0ubuntu1~trusty2
Version table:
   *** 1:5.0.3~rc2-0ubuntu1~trusty2 0
  500 http://ppa.launchpad.net/libreoffice/libreoffice-5-0/ubuntu/ 
trusty/main amd64 Packages
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:4.2.8-0ubuntu3 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1:4.2.3~rc3-0ubuntu2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1728773] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1728773/+attachment/5000647/+files/ProcModules.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] SystemdFailedUnits.txt

apport information

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/bugs/1728773/+attachment/5000649/+files/SystemdFailedUnits.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1728773/+attachment/5000641/+files/JournalErrors.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1728773/+attachment/5000643/+files/ProcCpuinfo.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] ProcEnviron.txt

apport information

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

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

apport information

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1728773/+attachment/5000650/+files/UdevDb.txt

** Tags removed: artful

** Description changed:

-  systemd updates on Bionic  ends with a read only filesystem, and startx
+ systemd updates on Bionic  ends with a read only filesystem, and startx
  also fails.
  
  Looks like it is related to the tmpfiles right change in systemd:
  
  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
- --- 
+ ---
+ 
+ note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
+ 
+ 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

** Description changed:

- systemd updates on Bionic  ends with a read only filesystem, and startx
+ systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.
  
  Looks like it is related to the tmpfiles right change in systemd:
  
  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  
  
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1728773/+attachment/5000642/+files/Lspci.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

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

apport information

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1728773/+attachment/5000646/+files/ProcInterrupts.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] SystemdDelta.txt

apport information

** Attachment added: "SystemdDelta.txt"
   
https://bugs.launchpad.net/bugs/1728773/+attachment/5000648/+files/SystemdDelta.txt

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] Re: [235.2ubuntu1] systemd upgrade set a read only filesystem

apport information

** Tags added: apport-collected artful

** Description changed:

   systemd updates on Bionic  ends with a read only filesystem, and startx
  also fails.
  
  Looks like it is related to the tmpfiles right change in systemd:
  
  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ EcryptfsInUse: Yes
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: systemd 234-2ubuntu12.1
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
+ ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
+ Tags:  artful
+ Uname: Linux 4.13.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/07/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P7.00
+ dmi.board.name: B150M-HDV
+ dmi.board.vendor: ASRock
+ 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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1728773] [NEW] [235.2ubuntu1] systemd upgrade set a read only filesystem

Public bug reported:

systemd update on Bionic  ends with a read only filesystem, and startx
also fails.

Looks like it is related to the tmpfiles right change in systemd:

[ Michael Biebl ]
* New upstream version 235
- cryptsetup-generator: use remote-cryptsetup.target when _netdev is
present (Closes: #852534)
- tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
---

note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.


ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: systemd 234-2ubuntu12.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Tags:  artful
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.00
dmi.board.name: B150M-HDV
dmi.board.vendor: ASRock
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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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


** Tags: apport-collected bionic regression-update

** Summary changed:

- [235.2ubuntu1] systemd upgrades set a read only filesystem
+ [235.2ubuntu1] systemd upgrade set a read only filesystem

** Tags added: bionic regression-update

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1727515] Re: Pulse audio doesn't store configuration any longer

** Tags added: xenial

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

Title:
  Pulse audio doesn't store configuration any longer

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since my upgraded from Kubuntu 14.04 to 16.04, my audio settings are not 
stored properly any longer. 
  When I reboot, the audio comes through the built-in audio speakers of my 
Thinkpad. However; I have a screen attached to HDMI (dock) with a better audio 
device. 

  With Pulse Audio Volume Control under Configuration, I see that the setting 
is Analog Surround 4.0. 
  Then I change to Digital Stereo (HDMI) Output, and the sound comes from my 
HDMI device.

  After each and every reboot, it starts with the Analog Surround Sound 4.0 and 
from my laptop.
  Once I have switched back to HDMI, the tab 'Output Devices' then shows as 
only available Device HDMI/Display Port (unplugged). It is *not* unplugged, 
otherwise I couldn't get my sound from my HDMI device, could I?
  Reboot and repeat. 

  This never happened under 14.04.

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

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

[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

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

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/7151
   Importance: Unknown
   Status: Unknown

** Changed in: iio-sensor-proxy (Ubuntu)
   Status: In Progress => Invalid

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

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

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  Unknown
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/iio-sensor-proxy/+bug/1726160/+subscriptions

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

[Touch-packages] [Bug 1727043] Re: random screen rotation of laptop disply when using additional screen.

Is it an HP laptop? If so then this is a duplicate of bug 1726160

** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  random screen rotation of laptop disply when using additional screen.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm on 17.10.  One screen - the laptop screen - rotates at random,
  typically when a video is playing, but not, I think always.  It
  rotates 180 degrees and stays upside down.  Mouse movememnts are
  reversed (ie correct for  the orientation of the screen).

  I tried

  gsettings set org.gnome.settings-daemon.plugins.orientation active
  false

  following a thread here https://askubuntu.com/questions/968169/screen-
  randomly-rotates-on-ubuntu-17-10/968284

  but it doesn't stop the behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727043/+subscriptions

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

[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-30 Thread Bug Watch Updater

** Changed in: iio-sensor-proxy
   Status: Unknown => Fix Released

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  Unknown
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/iio-sensor-proxy/+bug/1726160/+subscriptions

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

[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

Rejected upstream: https://github.com/hadess/iio-sensor-proxy/issues/198

Now assigned to systemd?...

** Bug watch added: github.com/hadess/iio-sensor-proxy/issues #198
   https://github.com/hadess/iio-sensor-proxy/issues/198

** Also affects: iio-sensor-proxy via
   https://github.com/hadess/iio-sensor-proxy/issues/198
   Importance: Unknown
   Status: Unknown

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

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  Unknown
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/iio-sensor-proxy/+bug/1726160/+subscriptions

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

Re: [Touch-packages] [Bug 1728596] Re: APT killed the OS load

2017-10-30 Thread Александр

there is a clear link with: BCM43228 and bcmwl

2017-10-30 21:33 GMT+05:00 Julian Andres Klode
<1728...@bugs.launchpad.net>:

> How did you try to update your system? It sounds like you used one of
> the reboot to upgrade packagekit front-ends, not apt.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728596
>
> Title:
>   APT killed the OS load
>
> Status in apt package in Ubuntu:
>   New
>
> Bug description:
>   after trying to update the system, the computer crashed, after which
>   it refused to boot. The download was made with the previous version of
>   the kernel - 4.10.0-28-generic (x86_64).
>
>   at startup, the computer began to ask for a password to replace the
> second disk, after entering the user's password for the current OS, the
> download continues. For this drive in another installation of this OS, I
> entered a different password. Enter the password does not match the
> password of the current user (root) did not try.
>   When you reboot, the password request for the disk is missing. However,
> in working with this version of the OS, this is periodically observed for
> my computer.
>
>   The system is freshly installed. It already had one unresolved problem.
>   https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1728550
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: apt 1.2.25
>   ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
>   Uname: Linux 4.10.0-28-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Mon Oct 30 18:16:55 2017
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2017-10-30 (0 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   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/1728596/+subscriptions
>

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

Title:
  APT killed the OS load

Status in apt package in Ubuntu:
  New

Bug description:
  after trying to update the system, the computer crashed, after which
  it refused to boot. The download was made with the previous version of
  the kernel - 4.10.0-28-generic (x86_64).

  at startup, the computer began to ask for a password to replace the second 
disk, after entering the user's password for the current OS, the download 
continues. For this drive in another installation of this OS, I entered a 
different password. Enter the password does not match the password of the 
current user (root) did not try.
  When you reboot, the password request for the disk is missing. However, in 
working with this version of the OS, this is periodically observed for my 
computer.

  The system is freshly installed. It already had one unresolved problem.
  https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1728550

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 30 18:16:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1728596/+subscriptions

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

[Touch-packages] [Bug 1017243] Re: Program received signal SIGBUS, Bus error.

2017-10-30 Thread Bug Watch Updater

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

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

Title:
  Program received signal SIGBUS, Bus error.

Status in Mesa:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  i'm using ubuntu 12.10 (i386) with latest updates installed (see end
  of dscription).

  
  i'm trying to use clutter and textures and get a "Bus Error". The attached 
python program can reproduce the error. Here is a backtrace (produced with 
another C program):

  Program received signal SIGBUS, Bus error.
  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  1417  main/texstore.c: No such file or directory.
  (gdb) bt
  #0  0xb6d292a5 in _mesa_texstore_argb (ctx=0x807a218, dims=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768, 
dstSlices=0xbfffea98,
  srcWidth=3648, srcHeight=2736, srcDepth=1, srcFormat=6407, srcType=5121, 
srcAddr=0xa4fde008, srcPacking=0x8088cac) at main/texstore.c:1417
  #1  0xb6d29f01 in _mesa_texstore (ctx=ctx@entry=0x807a218, dims=dims@entry=2, 
baseInternalFormat=6408, dstFormat=MESA_FORMAT_ARGB, dstRowStride=32768,
  dstSlices=dstSlices@entry=0xbfffea98, srcWidth=srcWidth@entry=3648, 
srcHeight=srcHeight@entry=2736, srcDepth=srcDepth@entry=1, 
srcFormat=srcFormat@entry=6407,
  srcType=srcType@entry=5121, srcAddr=srcAddr@entry=0xa4fde008, 
srcPacking=srcPacking@entry=0x8088cac) at main/texstore.c:4386
  #2  0xb6d2a173 in store_texsubimage (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008, packing=packing@entry=0x8088cac, 
caller=caller@entry=0xb6e4efe5 "glTexSubImage2D") at main/texstore.c:4517
  #3  0xb6d2a795 in _mesa_store_texsubimage2d (ctx=ctx@entry=0x807a218, 
texImage=texImage@entry=0x82a4e40, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  width=width@entry=3648, height=height@entry=2736, 
format=format@entry=6407, type=type@entry=5121, pixels=pixels@entry=0xa4fde008, 
packing=packing@entry=0x8088cac)
  at main/texstore.c:4653
  #4  0xb6eeaf9a in intelTexSubImage2D (ctx=0x807a218, texImage=0x82a4e40, 
xoffset=1, yoffset=2739, width=3648, height=2736, format=6407, type=5121, 
pixels=0xa4fde008,
  packing=0x8088cac) at intel_tex_subimage.c:164
  #5  0xb6d1535c in texsubimage (ctx=0x807a218, dims=dims@entry=2, 
target=target@entry=3553, level=level@entry=0, xoffset=xoffset@entry=1, 
yoffset=yoffset@entry=2739,
  zoffset=zoffset@entry=0, width=width@entry=3648, 
height=height@entry=2736, depth=depth@entry=1, format=format@entry=6407, 
type=type@entry=5121,
  pixels=pixels@entry=0xa4fde008) at main/teximage.c:2808
  #6  0xb6d18712 in texsubimage (pixels=0xa4fde008, type=5121, format=6407, 
depth=1, height=2736, width=3648, zoffset=0, yoffset=2739, xoffset=1, level=0, 
target=3553,
  dims=2, ctx=) at main/teximage.c:2751
  #7  _mesa_TexSubImage2D (target=3553, level=0, xoffset=1, yoffset=2739, 
width=3648, height=2736, format=6407, type=5121, pixels=0xa4fde008) at 
main/teximage.c:2853
  #8  0xb7a854c6 in _cogl_texture_driver_upload_subregion_to_gl 
(gl_target=3553, gl_handle=6, is_foreign=0, src_x=0, src_y=0, dst_x=1, 
dst_y=2739, width=3648,
  height=2736, source_bmp=0x8071af0, source_gl_format=6407, 
source_gl_type=5121) at ./driver/gl/cogl-texture-driver-gl.c:176
  #9  0xb7ac014a in _cogl_texture_2d_set_region (tex=0x82a7ad0, src_x=0, 
src_y=0, dst_x=1, dst_y=2739, dst_width=3648, dst_height=2736, bmp=0x8071af0)
  at ./cogl-texture-2d.c:783
  #10 0xb7abf004 in cogl_texture_set_region_from_bitmap_EXP (texture=0x82a7ad0, 
src_x=src_x@entry=0, src_y=src_y@entry=0, dst_x=1, dst_y=2739,
  dst_width=dst_width@entry=3648, dst_height=dst_height@entry=2736, 
bmp=bmp@entry=0x8071af0) at ./cogl-texture.c:641
  #11 0xb7ac60d2 in _cogl_atlas_texture_set_region_with_border 
(atlas_tex=atlas_tex@entry=0x82a6770, src_x=src_x@entry=0, src_y=src_y@entry=0, 
dst_x=dst_x@entry=0,
  dst_y=dst_y@entry=0, dst_width=dst_width@entry=3648, 
dst_height=dst_height@entry=2736, bmp=bmp@entry=0x8071af0) at 
./cogl-atlas-texture.c:445
  #12 0xb7ac6f9f in _cogl_atlas_texture_new_from_bitmap 
(bmp=bmp@entry=0x8071aa0, flags=flags@entry=COGL_TEXTURE_NONE, 
internal_format=,
  internal_format@entry=COGL_PIXEL_FORMAT_RGB_888) at 
./cogl-atlas-texture.c:768
  #13 0xb7abe1fa in cogl_texture_new_from_bitmap (bitmap=0x8071aa0,

Re: [Touch-packages] [Bug 1728596] Re: APT killed the OS load

2017-10-30 Thread Александр

sudo apt update
sudo apt upgrade

In previous installations I tried through the software center Ubuntu, same
result. I suspect that the problem is in incorrect installation of the
previous package, but without it I won't have Internet.

2017-10-30 21:33 GMT+05:00 Julian Andres Klode
<1728...@bugs.launchpad.net>:

> How did you try to update your system? It sounds like you used one of
> the reboot to upgrade packagekit front-ends, not apt.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728596
>
> Title:
>   APT killed the OS load
>
> Status in apt package in Ubuntu:
>   New
>
> Bug description:
>   after trying to update the system, the computer crashed, after which
>   it refused to boot. The download was made with the previous version of
>   the kernel - 4.10.0-28-generic (x86_64).
>
>   at startup, the computer began to ask for a password to replace the
> second disk, after entering the user's password for the current OS, the
> download continues. For this drive in another installation of this OS, I
> entered a different password. Enter the password does not match the
> password of the current user (root) did not try.
>   When you reboot, the password request for the disk is missing. However,
> in working with this version of the OS, this is periodically observed for
> my computer.
>
>   The system is freshly installed. It already had one unresolved problem.
>   https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1728550
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: apt 1.2.25
>   ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
>   Uname: Linux 4.10.0-28-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Mon Oct 30 18:16:55 2017
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2017-10-30 (0 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   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/1728596/+subscriptions
>

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

Title:
  APT killed the OS load

Status in apt package in Ubuntu:
  New

Bug description:
  after trying to update the system, the computer crashed, after which
  it refused to boot. The download was made with the previous version of
  the kernel - 4.10.0-28-generic (x86_64).

  at startup, the computer began to ask for a password to replace the second 
disk, after entering the user's password for the current OS, the download 
continues. For this drive in another installation of this OS, I entered a 
different password. Enter the password does not match the password of the 
current user (root) did not try.
  When you reboot, the password request for the disk is missing. However, in 
working with this version of the OS, this is periodically observed for my 
computer.

  The system is freshly installed. It already had one unresolved problem.
  https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1728550

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 30 18:16:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1728596/+subscriptions

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

[Touch-packages] [Bug 1640180] Re: gnome-todo doesn't load CalDav task list from EDS

François or anyone, are you still able to reproduce this bug with Ubuntu
17.10?

** Also affects: evolution-data-server (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  gnome-todo doesn't load CalDav task list from EDS

Status in GNOME To Do:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in evolution-data-server package in Ubuntu:
  Incomplete
Status in gnome-todo package in Ubuntu:
  Triaged

Bug description:
  Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav
  task list that were set through evolution. The list are still
  available in working in Evolution.

  I tried to set them up again but they didn't appear. 
  I tried upgrading to version available in various gnome3-ppa (still 3.20.* 
though) and it didn't help.

  The bug seems to have been handled in Fedora :
  https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1363848
  and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I
  found those while searching the web for a solution).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-todo/+bug/1640180/+subscriptions

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

[Touch-packages] [Bug 1728587] Re: No audio device after upgrade to Kubuntu 17.10

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

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 1720519, 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.


** This bug has been marked a duplicate of bug 1720519
   KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at 
most. Refusing to load.

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

Title:
  No audio device after upgrade to Kubuntu 17.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading Kubuntu 17.04 to 17.10, KDE lost the audio device
  (Realtek sound card on a Lenovo Thinkpad T470s). Volume icon is on
  mute, with info-popup given: "No output or input devices found". Audio
  backend is Phonon GStreamer. Re-installing pulseaudio didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Mon Oct 30 13:58:15 2017
  InstallationDate: Installed on 2017-08-25 (66 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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 artful on 2017-10-30 (0 days ago)
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-10-30 Thread Yuan-Chen Cheng

@Lukasz, per https://help.ubuntu.com/community/UbuntuBackports, the
Ubuntu Security Team does not update packages in Backports. I hope we
use something with Security update.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  In Progress

Bug description:
  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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

[Touch-packages] [Bug 1717474] Re: Multi monitor config issues

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

Thanks for the bug report. Please try to keep each bug about one issue
only...

Your first issue is being discussed in bug 1726538 also. So let's make
this a duplicate of that.

The second issue is probably bug 1723025 (?). Please comment in that
one.

** This bug has been marked a duplicate of bug 1726538
Dual monitor configuration not saved across logout / login

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

Title:
Multi monitor config issues

Status in gdm3 package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Status in xorg package in Ubuntu:
New

Bug description:
Since wayland will be the default with 17.10 it might be important to
have it ready for multiple monitor support. I have the latest updates
installed and I am on the artful channel.

SETUP:
HiDPI internal screen running at 2160x1440 (Surface Pro 3)
External FullHD HDMI monitor running at 1920x1080
Since the upgrade to the latest GNOME 3.26, wayland got activated again. I
was running X before.
Usually, I set my internal screen off and only work with the external monitor
if plugged in.

ISSUE:
With wayland active for both GDM and GNOME there is actually two issues:

1. I am able to configure my desired settings in the display settings
as usual (=turn off internal screen and use only external monitor).
But since the latest update this setting is not remembered after a new
login. It can only remember the "mirror" or "join displays" options
but not the "single display" option. Very annoying to reconfigure this
after every login.

Before the update to the new GNOME settings look I was at least able
to have this setting remembered (even with wayland). However, even
back then it was not perfect since the internal screen was not
completely turned off (black but with light on). After manually
setting the displays again the screen was turned off but not after a
login. This is a wayland related issue since it is not reproducable
with X.

2. GDM is always on the internal screen and simply does not match and
respect your GNOME config. I tried several ways to configure this:

sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config - does not work
since wayland ignores this config file.

I tried to using shell scripts executed at startup with xrandr. But
xrandr does not work with wayland, too. So this is also not a
solution.

FIX:
I don't know how to configure GDM with wayland. I am willing to test things
out but have no further ideas and am relatively new to Linux/Ubuntu. Thanks for
any help.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 10:57:43 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 0b) (prog-if 00 [VGA controller])
Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics
Controller [1414:0005]
InstallationDate: Installed on 2017-08-24 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170823)
MachineType: Microsoft Corporation Surface Pro 3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed
root=UUID=f348de47-cb83-4d73-8de3-bdd738092165 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.11.2150
dmi.board.asset.tag: 0
dmi.board.name: Surface Pro 3
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: 0
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 1
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2150:bd04/26/2017:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
dmi.product.family: Surface
dmi.product.name: Surface Pro 3
dmi.product.version: 1
dmi.sys.vendor: Microsoft Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6

[Touch-packages] [Bug 1727043] Re: random screen rotation of laptop disply when using additional screen.

2017-10-30 Thread Springnuts

Seems to be OK using Xorg.

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

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

Title:
  random screen rotation of laptop disply when using additional screen.

Status in wayland package in Ubuntu:
  New

Bug description:
  I'm on 17.10.  One screen - the laptop screen - rotates at random,
  typically when a video is playing, but not, I think always.  It
  rotates 180 degrees and stays upside down.  Mouse movememnts are
  reversed (ie correct for  the orientation of the screen).

  I tried

  gsettings set org.gnome.settings-daemon.plugins.orientation active
  false

  following a thread here https://askubuntu.com/questions/968169/screen-
  randomly-rotates-on-ubuntu-17-10/968284

  but it doesn't stop the behaviour.

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

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

[Touch-packages] [Bug 1690861] Re: typo of descripiton in README

2017-10-30 Thread Simon Vall

** Changed in: patch (Ubuntu)
 Assignee: (unassigned) => Simon Vall (svsimonvall)

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

Title:
  typo of descripiton in README

Status in Patch:
  Unknown
Status in patch package in Ubuntu:
  Confirmed

Bug description:
  Line 19 of /usr/share/doc/patch/README contains "descripiton".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: patch 2.7.1-4ubuntu2.3
  Uname: Linux 3.4.0+ x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon May 15 18:40:47 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.11
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.11
  ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/62/environ'
  SourcePackage: patch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1728747] [NEW] package linux-image-4.4.0-97-generic 4.4.0-97.120 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-10-30 Thread opensource

Public bug reported:

Ubuntu will not update to the latest version.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-97-generic 4.4.0-97.120
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   opensource   1782 F...m pulseaudio
 /dev/snd/controlC0:  opensource   1782 F pulseaudio
Date: Mon Oct 30 16:46:16 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=c85243f7-537c-47e7-814f-41e504c022ec
InstallationDate: Installed on 2015-11-29 (701 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Apple Inc. iMac10,1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic.efi.signed 
root=UUID=ae74090e-1fb0-422f-8a2e-11ddccc49a5f ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-97-generic 4.4.0-97.120 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2016-06-25 (492 days ago)
dmi.bios.date: 09/03/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM101.88Z.00CC.B00.0909031926
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F2268CC8
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F2268CC8
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM101.88Z.00CC.B00.0909031926:bd09/03/09:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:
dmi.product.name: iMac10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-package need-duplicate-check xenial

** Description changed:

  Ubuntu will not update to the latest version.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-97-generic 4.4.0-97.120
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0p:   opensource   1782 F...m pulseaudio
-  /dev/snd/controlC0:  opensource   1782 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   opensource   1782 F...m pulseaudio
+  /dev/snd/controlC0:  opensource   1782 F pulseaudio
  Date: Mon Oct 30 16:46:16 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=c85243f7-537c-47e7-814f-41e504c022ec
  InstallationDate: Installed on 2015-11-29 (701 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. iMac10,1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic.efi.signed 
root=UUID=ae74090e-1fb0-422f-8a2e-11ddccc49a5f ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-97-generic 4.4.0-97.120 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-06-25 (492 days ago)
  dmi.bios.date: 09/03/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM101.88Z.00CC.B00.0909031926
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2268CC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268CC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM101.88Z.00CC.B00.0909031926:bd09/03/09:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:
  dmi.product.name: iMac10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

Title:
  package linux-image-4.4.0-97-generic 4.4.0-97.120 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Ubuntu will not update to the latest version.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-97-generic 4.4.0-97.120
  ProcVersionSignature:

[Touch-packages] [Bug 1728444] Re: Random graphical freezes Ubuntu 17.10

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

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

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

Title:
  Random graphical freezes Ubuntu 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello everyone!

  I'm not sure if this is the right package to report this graphics
  related bug. As this affects Wayland and Xorg sessions on my machine.

  I've noticed that mouse becomes very choppy for some time period at
  random, not sure why. Also it seems if there's high disk load (I/O
  indicator is on all the time) all graphics can freeze for very long
  time ( 30m-1h or more).

  Happy to provide extra info as needed. 
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 19:57:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7560D] [1002:9904]
  InstallationDate: Installed on 2017-09-30 (29 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=9e917423-5dbc-446b-bed6-506a46eb2382 ro quiet splash radeon.dpm=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  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:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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 N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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+git20170309-0ubuntu1
  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/1728444/+subscriptions

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

[Touch-packages] [Bug 1728741] [NEW] Xorg freeze

2017-10-30 Thread Jack J. Woehr

Public bug reported:

Will not come back after screen lock.
The main VAIO laptop lid monitor does not come back, stays dark, no backlight.
I have a second HDMI monitor.
The HDMI monitor will come back from screen lock, but scrambled.
Mouse does not appear.
I have also tried suckless.org slock with same result.
Closing and opening the lid does not help.
I also hear the laptop fan come on when trying to restore which indicates CPU 
is probably running away.
No keyboard sequence seems to work, though I have not tested this exhaustively.
All that works is a 5-second powerdown button press with restart.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 30 16:17:32 2017
DistUpgraded: 2017-10-30 08:29:59,969 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Sony Corporation GF108M [GeForce GT 540M] [104d:9086]
InstallationDate: Installed on 2016-10-29 (366 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
MachineType: Sony Corporation VPCF215FX
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to artful on 2017-10-30 (0 days ago)
dmi.bios.date: 02/10/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0200V3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0200V3:bd02/10/2011:svnSonyCorporation:pnVPCF215FX:pvrC608AVBH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCF215FX
dmi.product.version: C608AVBH
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
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 artful freeze ubuntu wayland-session

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Will not come back after screen lock.
  The main VAIO laptop lid monitor does not come back, stays dark, no backlight.
  I have a second HDMI monitor.
  The HDMI monitor will come back from screen lock, but scrambled.
  Mouse does not appear.
  I have also tried suckless.org slock with same result.
  Closing and opening the lid does not help.
  I also hear the laptop fan come on when trying to restore which indicates CPU 
is probably running away.
  No keyboard sequence seems to work, though I have not tested this 
exhaustively.
  All that works is a 5-second powerdown button press with restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 16:17:32 2017
  DistUpgraded: 2017-10-30 08:29:59,969 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously

[Touch-packages] [Bug 1724711] Re: rsyslog fails to start (Lubuntu 17.10)

2017-10-30 Thread Dima

I think it can't start because /var/run/rsyslogd.pid does not removed on
shutdown.

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

Title:
  rsyslog fails to start (Lubuntu 17.10)

Status in rsyslog package in Ubuntu:
  New

Bug description:
  1) 
  Description:  Ubuntu 17.10
  Release:  17.10

  2) 8.16.0-1ubuntu9

  3) I'd like to see what happened in the system

  4) syslog is empty, messages is obsolete, lastlog shows only pure
  console logins (it maybe unrelated)

  root@user:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2017-10-19 02:24:34 MSK; 1h 
15min ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 1858 ExecStart=/usr/sbin/rsyslogd -n (code=exited, 
status=1/FAILURE)
   Main PID: 1858 (code=exited, status=1/FAILURE)

  окт 19 02:24:33 user systemd[1]: rsyslog.service: Main process exited, 
code=exited, stat
  окт 19 02:24:33 user systemd[1]: Failed to start System Logging Service.
  окт 19 02:24:33 user systemd[1]: rsyslog.service: Unit entered failed state.
  окт 19 02:24:33 user systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Service hold-off time over, 
scheduling
  окт 19 02:24:34 user systemd[1]: Stopped System Logging Service.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Start request repeated too 
quickly.
  окт 19 02:24:34 user systemd[1]: Failed to start System Logging Service.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Unit entered failed state.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Failed with result 
'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Oct 19 03:59:04 2017
  InstallationDate: Installed on 2017-10-06 (12 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1728461] Re: Python GC destroys PyGObject with external references

2017-10-30 Thread Bug Watch Updater

** Changed in: pygobject
   Status: Unknown => Fix Released

** Changed in: pygobject
   Importance: Unknown => Medium

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

Title:
  Python GC destroys PyGObject with external references

Status in pygobject:
  Fix Released
Status in pygobject package in Ubuntu:
  New

Bug description:
  PyGObject traverses its closures in tp_traverse, but the lifetime of the 
closures
  is tied to the lifetime of the GObject and not the wrapper. This confuses
  the Python GC when it sees a ref cycle and tries to break it up with tp_clear.
  Since tp_clear will not invalidate the closure and only invalidate the Python
  wrapper the closure callback gets called with the now cleared/invalid object.

  This bug make python gtk programs to segfault randomly.

  Patch available here:
  https://bugzilla.gnome.org/show_bug.cgi?id=731501

  Should apply to 3.24 or be easily backported: one line patch adding a
  if statement.

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

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

[Touch-packages] [Bug 304345] Re: File chooser dialog doesn't provide network access

2017-10-30 Thread Norbert

** Tags added: bionic xenial

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

Title:
  File chooser dialog doesn't provide network access

Status in GTK+:
  Fix Released
Status in One Hundred Papercuts:
  Fix Released
Status in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Baltix:
  Fix Released

Bug description:
  Binary package hint: audacious

  Audacious cannot open files samba shares. Just like Gringotts and
  Firefox it cannot open (save) to network share.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=8.10
  DISTRIB_CODENAME=intrepid
  DISTRIB_DESCRIPTION="Ubuntu 8.10"

  ii  audacious  1.5.1-3ubuntu1.1
  small and fast audio player which supports

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

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

[Touch-packages] [Bug 1727825] Re: networkd DHCP immediately drops lease ( on igbx cards )

2017-10-30 Thread Jon Proulx

if I configure a static v4 address in netplan then dhcpv6 works

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

Title:
  networkd DHCP immediately drops lease ( on igbx cards )

Status in systemd package in Ubuntu:
  New

Bug description:
  On new install of 17.10 systemd-networkd loops with:

  Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
  Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
  Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost

  that is the correct interface and address.

  If I manually run 'dhclient nep129s0f0' the lease sticks and
  'journalctl -fu systemd-networkd' shows:

  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured

  I have verified this is reproducible on other systems with ixgbe based
  add in cards.

  igb (1G) cards seem to behave properly as do a random assortment of
  onboard devices and virtio devices inside VMs.

  Based on a pseudo random selection of my available gear it does seem
  hardware specific but this is our only flavor of 10G nic (and we have
  kindof a lot of them). Since isc-dhcp-client can bring up the
  interface on the commandline I don't *think* it's a driver issue.

  root@host:~# lsb_release -rd;uname -r ; dpkg -l nplan systemd
  Description: Ubuntu 17.10
  Release: 17.10
  4.13.0-16-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version Architecture Description
  
+++-==-==-==-=
  ii nplan 0.30 amd64 YAML network configuration abstraction fo
  ii systemd 234-2ubuntu12 amd64 system and service manager

  my current workaround:

  root@host:~# cat /etc/rc.local
  #!/bin/sh
  dhclient enp129s0f0

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

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

[Touch-packages] [Bug 1728709] Re: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc

2017-10-30 Thread Hans Joachim Desserud

** Tags added: manpage

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

Title:
  bash man page has a typo, repeating .bashrc when one should be
  /etc/bash.bashrc

Status in bash package in Ubuntu:
  New

Bug description:
  The INVOCATION section of the man page has the text

  "reads and executes commands from ~/.bashrc and ~/.bashrc, if these
  files exist and are readable"

  which repeats "~/.bashrc".  By experiment, I find it probable that the
  first of these .bashrc references should read "/etc/bash.bashrc".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 30 13:28:43 2017
  InstallationDate: Installed on 2016-08-08 (447 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1727515] Re: Pulse audio doesn't store configuration any longer

2017-10-30 Thread Joseph Salisbury

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

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => 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/1727515

Title:
  Pulse audio doesn't store configuration any longer

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since my upgraded from Kubuntu 14.04 to 16.04, my audio settings are not 
stored properly any longer. 
  When I reboot, the audio comes through the built-in audio speakers of my 
Thinkpad. However; I have a screen attached to HDMI (dock) with a better audio 
device. 

  With Pulse Audio Volume Control under Configuration, I see that the setting 
is Analog Surround 4.0. 
  Then I change to Digital Stereo (HDMI) Output, and the sound comes from my 
HDMI device.

  After each and every reboot, it starts with the Analog Surround Sound 4.0 and 
from my laptop.
  Once I have switched back to HDMI, the tab 'Output Devices' then shows as 
only available Device HDMI/Display Port (unplugged). It is *not* unplugged, 
otherwise I couldn't get my sound from my HDMI device, could I?
  Reboot and repeat. 

  This never happened under 14.04.

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

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

[Touch-packages] [Bug 1728709] [NEW] bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc

2017-10-30 Thread Kevin O'Gorman

Public bug reported:

The INVOCATION section of the man page has the text

"reads and executes commands from ~/.bashrc and ~/.bashrc, if these
files exist and are readable"

which repeats "~/.bashrc".  By experiment, I find it probable that the
first of these .bashrc references should read "/etc/bash.bashrc".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Oct 30 13:28:43 2017
InstallationDate: Installed on 2016-08-08 (447 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  bash man page has a typo, repeating .bashrc when one should be
  /etc/bash.bashrc

Status in bash package in Ubuntu:
  New

Bug description:
  The INVOCATION section of the man page has the text

  "reads and executes commands from ~/.bashrc and ~/.bashrc, if these
  files exist and are readable"

  which repeats "~/.bashrc".  By experiment, I find it probable that the
  first of these .bashrc references should read "/etc/bash.bashrc".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 30 13:28:43 2017
  InstallationDate: Installed on 2016-08-08 (447 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

** Also affects: gnome-control-center (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** No longer affects: gnome-control-center (Ubuntu Artful)

** Changed in: gtk+3.0 (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: New => In Progress

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+subscriptions

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

[Touch-packages] [Bug 1681910] Re: gnome-terminal constantly logs "Unable to load blank_cursor from the cursor theme" under gnome/wayland

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  The systemd journal gets full of useless messages about "Unable to load 
blank_cursor from the cursor theme" when using GNOME Terminal in Wayland on 
Ubuntu 17.10. Ubuntu 17.10 uses Wayland by default when the hardware supports 
it.

  Test Case
  =
  1.Install the gtk3 updates to Ubuntu 17.10.
  2. Log out then log into "Ubuntu" or "GNOME" on a computer that supports 
Wayland.
  3. Open the default terminal app.
  4. Verify that you are running Wayland by running this command. If there is 
output, you are running Wayland.

   env | grep -i wayland

  5. Run this command to check for the useless messages from gnome-
  terminal:

  journalctl -f

  Regression Potential
  ===
  This fix is part of the gtk3 3.22.25 update (LP: #1728421) and seems unlikely 
to cause problems.

  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=fc741adbb

  Original Bug Report
  ===
  Under GNOME/Wayland, regardless of cursor theme (I'm using 'DMZ-White', but 
confirmed with 'Adwaita'), whenever the terminal obtains focus and the user 
starts entering input, gnome-terminal will generate two log entries:

  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme
  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme

  This seems to be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417490

  and related to:
  https://bugzilla.gnome.org/show_bug.cgi?id=775217

  (though in Ubuntu 17.04 the log doesn't contain 'gdkcursor-
  wayland.c:170' like in the gnome bug.

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

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

[Touch-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  GTK3 menus don't work over SSH forwarding

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  In Progress

Bug description:
  * Impact
  
  GTK interfaces used over SSH might miss their menus

  * Test case
  ---
  - connect via ssh -X to a cygwin server
  - start an application that is using menus (e.g virt-manager)
  -> the menus should work

  * Regression potential
  --
  check that gtk softwares have working menus and look the same

  Original Bug Report
  ---

  When connecting remotely (either SSH X11 forwarding or direct to X11
  server), drop down menus do not display properly.

  Bug upstream in gtk3:
  https://bugzilla.gnome.org/show_bug.cgi?id=780101

  Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3
  Server: Windows 10 Cygwin/X 1.19.2-1

  Programs exhibiting this problem:
  evince 3.24.0 (and any other gtk3 apps with menus along the top).

  Patch applied to gtk3 in cygwin to fix this problem and attached to this post:
  https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch

  Console errors:

  (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
  assertion 'G_IS_DBUS_PROXY (proxy)' failed

  (evince:7390): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: The name org.freedesktop.portal.Desktop is 
not owned

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: 
assertion 'width >= 0' failed
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation
  1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu)

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

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

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

[Touch-packages] [Bug 1728573] Re: request to pull in an upstream bug fix for systemd

2017-10-30 Thread Joseph Salisbury

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

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

Title:
  request to pull in an upstream bug fix for systemd

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  There's a bug in systemd's virtualization detection algorithm that
  prevents the XenServer Tools from working: systemd-virt-detect reports
  "vm-other" instead of Xen on AMD hosts, and if it doesn't report
  "xen", then xe-daemon will refuse to start. Thus, installing Ubuntu as
  a guest on XenServer on an AMD host will be less than ideal.

  This has been patched upstream:
  
https://github.com/systemd/systemd/commit/530c1c3028c484c503725bbac769b9051af83da7

  If this fix could be pulled into Xenial / Ubuntu 16.04 LTS, it would
  be greatly appreciated. Thanks!

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

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

[Touch-packages] [Bug 1728421] Re: Update gtk+3.0 to 3.22.25

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  Update gtk+3.0 to 3.22.25

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  There is a new gtk3 release, 3.22.25.

  Highlights
  --
  * Allows dropping these cherry-picked patches:
    - 0001-Adwaita-Fix-typo-.backgrounf-.background.patch
    - 0002-theme-Fix-Adwaita-headerbars.patch
   - 0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch
  * Fixes crash with GNOME Online Accounts (LP: #1720400)
  * Fixes menu forwarding over SSH (LP: #1700319)
  * Fixes log spam about cursor when running gnome-terminal on Wayland (LP: 
#1681910)
  * Support KDE SSD (server-side decorations) handling on Wayland
  * Restores middle-click to do the opposite of primary (usually left-) click 
in scrollbars, GTKRange
  * Some theme fixes for the gtk3 High Contrast theme
  * Allow more key buttons in the GNOME Settings > Keyboard panel to be 
translatable
  * A fix to not show duplicate printers in some cases
  * Improves the GNOME 3.26 tiling feature for GNOME Terminal

  For more changes since 3.22.24, see
  https://git.gnome.org/browse/gtk+/log?h=gtk-3-22
  https://git.gnome.org/browse/gtk+/tree/NEWS?h=gtk-3-22

  Test Case
  =
  Install the update. Run a variety of apps in the default Ubuntu install with 
the Ambiance theme.

  Also check that the Adwaita and High Contrast themes still look ok. You can 
change the theme with the GNOME Tweaks app (gnome-tweak-tool). For the window 
buttons to look as designed, you should change the icon theme to Adwaita when 
you set the theme to Adwaita or High Contrast. Afterwards, you can reset your 
theme back to the defaults with
  gsettings reset org.gnome.desktop.interface gtk-theme
  gsettings reset org.gnome.desktop.interface icon-theme

  Regression Potential
  
  Quite a few changes, but mostly it's bug fixes.

  Earlier gtk3 releases had some regressions (that's why we had those
  cherry-picked patches), but that was mostly related to the late GNOME
  3.26 tiling feature that was rushed in. This release does not have any
  major new features like that.

  Unfortunately, very few people run gtk3 from git master so regressions
  often aren't seen until distros start shipping the gtk3 update.

  The GNOME stack has an SRU Micro-release exception
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  We haven't done micro-release SRUs for gtk3.22 yet. This might be a
  good trial run to see how well it works before 18.04 LTS. Fedora does
  keep their gtk3 up to date throughout the life of their releases.

  Other Info
  ==
  This update also drops a few old patches that weren't listed in 
debian/patches/series. Sorry about the noise but this makes it a bit cleaner in 
the future.

  0001-Update-the-GDK-Mir-backend-to-fix-a-few-problems.patch
  0001-Improve-external-drives-detection.patch
  0002-fix-other-locations-with-glib-249.patch
  0003-use-null-for-generic-marshallers.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728421/+subscriptions

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

[Touch-packages] [Bug 1727515] [NEW] Pulse audio doesn't store configuration any longer

You have been subscribed to a public bug:

Since my upgraded from Kubuntu 14.04 to 16.04, my audio settings are not stored 
properly any longer. 
When I reboot, the audio comes through the built-in audio speakers of my 
Thinkpad. However; I have a screen attached to HDMI (dock) with a better audio 
device. 

With Pulse Audio Volume Control under Configuration, I see that the setting is 
Analog Surround 4.0. 
Then I change to Digital Stereo (HDMI) Output, and the sound comes from my HDMI 
device.

After each and every reboot, it starts with the Analog Surround Sound 4.0 and 
from my laptop.
Once I have switched back to HDMI, the tab 'Output Devices' then shows as only 
available Device HDMI/Display Port (unplugged). It is *not* unplugged, 
otherwise I couldn't get my sound from my HDMI device, could I?
Reboot and repeat. 

This never happened under 14.04.

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

-- 
Pulse audio doesn't store configuration any longer
https://bugs.launchpad.net/bugs/1727515
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1238408] Re: apport-collect is not functional until manual installation of python-apport

2017-10-30 Thread Norbert

** Tags added: beaver

** Tags removed: beaver
** Tags added: bionic

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

Title:
  apport-collect is not functional until manual installation of python-
  apport

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to launch `apport-collect 1712200`

  Expected results:
  apport-collect works out-the-box and collected corresponding info

  Actual results:
  apport-collect does not work and shows message:

  "You need to run 'sudo apt-get install python-apport' for apport-
  collect to work."

  Note: manual installation of python-apport adds 15 MB of new packages,
  after that apport-collect works as expected.

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

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

[Touch-packages] [Bug 1681910] Re: gnome-terminal constantly logs "Unable to load blank_cursor from the cursor theme" under gnome/wayland

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3artful

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

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  The systemd journal gets full of useless messages about "Unable to load 
blank_cursor from the cursor theme" when using GNOME Terminal in Wayland on 
Ubuntu 17.10. Ubuntu 17.10 uses Wayland by default when the hardware supports 
it.

  Test Case
  =
  1.Install the gtk3 updates to Ubuntu 17.10.
  2. Log out then log into "Ubuntu" or "GNOME" on a computer that supports 
Wayland.
  3. Open the default terminal app.
  4. Verify that you are running Wayland by running this command. If there is 
output, you are running Wayland.

   env | grep -i wayland

  5. Run this command to check for the useless messages from gnome-
  terminal:

  journalctl -f

  Regression Potential
  ===
  This fix is part of the gtk3 3.22.25 update (LP: #1728421) and seems unlikely 
to cause problems.

  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=fc741adbb

  Original Bug Report
  ===
  Under GNOME/Wayland, regardless of cursor theme (I'm using 'DMZ-White', but 
confirmed with 'Adwaita'), whenever the terminal obtains focus and the user 
starts entering input, gnome-terminal will generate two log entries:

  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme
  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme

  This seems to be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417490

  and related to:
  https://bugzilla.gnome.org/show_bug.cgi?id=775217

  (though in Ubuntu 17.04 the log doesn't contain 'gdkcursor-
  wayland.c:170' like in the gnome bug.

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

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3artful

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+subscriptions

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

[Touch-packages] [Bug 1728421] Re: Update gtk+3.0 to 3.22.25

** Branch linked: lp:~ubuntu-desktop/gtk/ubuntugtk3artful

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

Title:
  Update gtk+3.0 to 3.22.25

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  There is a new gtk3 release, 3.22.25.

  Highlights
  --
  * Allows dropping these cherry-picked patches:
    - 0001-Adwaita-Fix-typo-.backgrounf-.background.patch
    - 0002-theme-Fix-Adwaita-headerbars.patch
   - 0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch
  * Fixes crash with GNOME Online Accounts (LP: #1720400)
  * Fixes menu forwarding over SSH (LP: #1700319)
  * Fixes log spam about cursor when running gnome-terminal on Wayland (LP: 
#1681910)
  * Support KDE SSD (server-side decorations) handling on Wayland
  * Restores middle-click to do the opposite of primary (usually left-) click 
in scrollbars, GTKRange
  * Some theme fixes for the gtk3 High Contrast theme
  * Allow more key buttons in the GNOME Settings > Keyboard panel to be 
translatable
  * A fix to not show duplicate printers in some cases
  * Improves the GNOME 3.26 tiling feature for GNOME Terminal

  For more changes since 3.22.24, see
  https://git.gnome.org/browse/gtk+/log?h=gtk-3-22
  https://git.gnome.org/browse/gtk+/tree/NEWS?h=gtk-3-22

  Test Case
  =
  Install the update. Run a variety of apps in the default Ubuntu install with 
the Ambiance theme.

  Also check that the Adwaita and High Contrast themes still look ok. You can 
change the theme with the GNOME Tweaks app (gnome-tweak-tool). For the window 
buttons to look as designed, you should change the icon theme to Adwaita when 
you set the theme to Adwaita or High Contrast. Afterwards, you can reset your 
theme back to the defaults with
  gsettings reset org.gnome.desktop.interface gtk-theme
  gsettings reset org.gnome.desktop.interface icon-theme

  Regression Potential
  
  Quite a few changes, but mostly it's bug fixes.

  Earlier gtk3 releases had some regressions (that's why we had those
  cherry-picked patches), but that was mostly related to the late GNOME
  3.26 tiling feature that was rushed in. This release does not have any
  major new features like that.

  Unfortunately, very few people run gtk3 from git master so regressions
  often aren't seen until distros start shipping the gtk3 update.

  The GNOME stack has an SRU Micro-release exception
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  We haven't done micro-release SRUs for gtk3.22 yet. This might be a
  good trial run to see how well it works before 18.04 LTS. Fedora does
  keep their gtk3 up to date throughout the life of their releases.

  Other Info
  ==
  This update also drops a few old patches that weren't listed in 
debian/patches/series. Sorry about the noise but this makes it a bit cleaner in 
the future.

  0001-Update-the-GDK-Mir-backend-to-fix-a-few-problems.patch
  0001-Improve-external-drives-detection.patch
  0002-fix-other-locations-with-glib-249.patch
  0003-use-null-for-generic-marshallers.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728421/+subscriptions

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

[Touch-packages] [Bug 1728701] [NEW] package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-10-30 Thread KOB

Public bug reported:

Using ubuntu 17.10 live from pendrive with 4GB persistency created by
Yumi.

First start. First thing to do is open Software Updater and run it. its
starts but it fails saying "Package operation failed".

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: initramfs-tools 0.125ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Mon Oct 30 20:04:15 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful need-duplicate-check

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

Title:
  package initramfs-tools 0.125ubuntu12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Using ubuntu 17.10 live from pendrive with 4GB persistency created by
  Yumi.

  First start. First thing to do is open Software Updater and run it.
  its starts but it fails saying "Package operation failed".

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Mon Oct 30 20:04:15 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1613184] Re: method mirror broken at 1.3

2017-10-30 Thread Julian Andres Klode

** Tags removed: verification-failed

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

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

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

[Touch-packages] [Bug 1728596] Re: APT killed the OS load

2017-10-30 Thread Julian Andres Klode

** Tags added: bot-stop-nagging

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

Title:
  APT killed the OS load

Status in apt package in Ubuntu:
  New

Bug description:
  after trying to update the system, the computer crashed, after which
  it refused to boot. The download was made with the previous version of
  the kernel - 4.10.0-28-generic (x86_64).

  at startup, the computer began to ask for a password to replace the second 
disk, after entering the user's password for the current OS, the download 
continues. For this drive in another installation of this OS, I entered a 
different password. Enter the password does not match the password of the 
current user (root) did not try.
  When you reboot, the password request for the disk is missing. However, in 
working with this version of the OS, this is periodically observed for my 
computer.

  The system is freshly installed. It already had one unresolved problem.
  https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1728550

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 30 18:16:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1728596/+subscriptions

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

[Touch-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

** Description changed:

  * Impact
- GTK interfaces used over GTK might miss their menus
+ 
+ GTK interfaces used over SSH might miss their menus
  
  * Test case
+ ---
  - connect via ssh -X to a cygwin server
  - start an application that is using menus (e.g virt-manager)
  -> the menus should work
  
  * Regression potential
+ --
  check that gtk softwares have working menus and look the same
  
+ Original Bug Report
  ---
  
- 
- When connecting remotely (either SSH X11 forwarding or direct to X11 server), 
drop down menus do not display properly.
+ When connecting remotely (either SSH X11 forwarding or direct to X11
+ server), drop down menus do not display properly.
  
  Bug upstream in gtk3:
  https://bugzilla.gnome.org/show_bug.cgi?id=780101
  
  Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3
  Server: Windows 10 Cygwin/X 1.19.2-1
  
  Programs exhibiting this problem:
  evince 3.24.0 (and any other gtk3 apps with menus along the top).
  
  Patch applied to gtk3 in cygwin to fix this problem and attached to this post:
  https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch
  
  Console errors:
  
  (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
  assertion 'G_IS_DBUS_PROXY (proxy)' failed
  
  (evince:7390): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: The name org.freedesktop.portal.Desktop is 
not owned
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
  
  (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: 
assertion 'width >= 0' failed
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug
  
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug
  
  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1,
  extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  
  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug
  
  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1,
  extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)
  
  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1,
  extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)
  
  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1,
  extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

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

Title:
  GTK3 menus don't work over SSH forwarding

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  * Impact
  
  GTK interfaces used over SSH might miss their menus

  * Test case
  ---
  - connect via ssh -X to a cygwin server
  - start an application that is using menus

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

This bug was fixed in the package linux - 4.4.0-98.121

---
linux (4.4.0-98.121) xenial; urgency=low

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)

  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB

  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.

  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
- snapcraft.yaml: add dpkg-dev to the build deps

  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
- i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT

  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi_transport_sas: add function to get SAS endpoint address
- ses: fix discovery of SATA devices in SAS enclosures
- scsi: sas: provide stub implementation for scsi_is_sas_rphy
- scsi: ses: Fix SAS device detection in enclosure

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
- SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819

  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring

  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing

  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW

  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
- SAUCE: update OpenNSL kernel modules to 6.5.10

  * Xenial update to 4.4.90 stable release (LP: #1721550)
- cifs: release auth_key.response for reconnect.
- mac80211: flush hw_roc_start work before cancelling the ROC
- KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
- tracing: Fix trace_pipe behavior for instance traces
- tracing: Erase irqsoff trace with empty write
- md/raid5: fix a race condition in stripe batch
- md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
- scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
  nlmsg properly
- crypto: talitos - Don't provide setkey for non hmac hashing algs.
- crypto: talitos - fix sha224
- KEYS: fix writing past end of user-supplied buffer in keyring_read()
- KEYS: prevent creating a different user's keyrings
- KEYS: prevent KEYCTL_READ on negative key
- powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
- Fix SMB3.1.1 guest authentication to Samba
- SMB: Validate negotiate (to protect against downgrade) even if signing off
- SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
- vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
- nl80211: check for the required netlink attributes presence
- bsg-lib: don't free job in bsg_prepare_job
- seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
- arm64: Make sure SPsel is always set
- arm64: fault: Route pte translation faults via do_translation_fault
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
- kvm: nVMX: Don't allow L2 to access the hardware CR8
- PCI: Fix race condition with driver_override
- btrfs: fix NULL pointer dereference from free_reloc_roots()
- btrfs: propagate error to btrfs_cmp_data_prepare caller
- btrfs: prevent to set invalid default subvolid
- x86/fpu: Don't let userspace set bogus xcomp_bv
- gfs2: Fix debugfs glocks dump
- timer/sysclt: Restrict timer migration sysctl values to 0 and 1
- KVM: VMX: do not change SN bit in vmx_update_pi_irte()
- KVM: VMX: remove WARN_ON_ONCE in kvm_vcpu_trigger_posted_interrupt
- cxl: Fix driver use count
- dmaengine: mmp-pdma: add number of requestors
- ARM: pxa: add the number of DMA requestor lines
- ARM: pxa: fix the number of DMA requestor lines
- KVM: VMX: use

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

This bug was fixed in the package linux - 4.4.0-98.121

---
linux (4.4.0-98.121) xenial; urgency=low

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)

  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB

  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.

  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
- snapcraft.yaml: add dpkg-dev to the build deps

  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
- i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT

  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi_transport_sas: add function to get SAS endpoint address
- ses: fix discovery of SATA devices in SAS enclosures
- scsi: sas: provide stub implementation for scsi_is_sas_rphy
- scsi: ses: Fix SAS device detection in enclosure

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
- SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819

  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring

  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing

  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW

  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
- SAUCE: update OpenNSL kernel modules to 6.5.10

  * Xenial update to 4.4.90 stable release (LP: #1721550)
- cifs: release auth_key.response for reconnect.
- mac80211: flush hw_roc_start work before cancelling the ROC
- KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
- tracing: Fix trace_pipe behavior for instance traces
- tracing: Erase irqsoff trace with empty write
- md/raid5: fix a race condition in stripe batch
- md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
- scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
  nlmsg properly
- crypto: talitos - Don't provide setkey for non hmac hashing algs.
- crypto: talitos - fix sha224
- KEYS: fix writing past end of user-supplied buffer in keyring_read()
- KEYS: prevent creating a different user's keyrings
- KEYS: prevent KEYCTL_READ on negative key
- powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
- Fix SMB3.1.1 guest authentication to Samba
- SMB: Validate negotiate (to protect against downgrade) even if signing off
- SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
- vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
- nl80211: check for the required netlink attributes presence
- bsg-lib: don't free job in bsg_prepare_job
- seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
- arm64: Make sure SPsel is always set
- arm64: fault: Route pte translation faults via do_translation_fault
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
- kvm: nVMX: Don't allow L2 to access the hardware CR8
- PCI: Fix race condition with driver_override
- btrfs: fix NULL pointer dereference from free_reloc_roots()
- btrfs: propagate error to btrfs_cmp_data_prepare caller
- btrfs: prevent to set invalid default subvolid
- x86/fpu: Don't let userspace set bogus xcomp_bv
- gfs2: Fix debugfs glocks dump
- timer/sysclt: Restrict timer migration sysctl values to 0 and 1
- KVM: VMX: do not change SN bit in vmx_update_pi_irte()
- KVM: VMX: remove WARN_ON_ONCE in kvm_vcpu_trigger_posted_interrupt
- cxl: Fix driver use count
- dmaengine: mmp-pdma: add number of requestors
- ARM: pxa: add the number of DMA requestor lines
- ARM: pxa: fix the number of DMA requestor lines
- KVM: VMX: use

[Touch-packages] [Bug 1613184] [apt/xenial] possible regression found

2017-10-30 Thread Ubuntu Foundations Team Bug Bot

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of apt from xenial-proposed was
performed and bug 1728596 was found.  Please investigate this bug report
to ensure that a regression will not be created by this SRU. In the
event that this is not a regression remove the "verification-failed" tag
from this bug report and add the tag "bot-stop-nagging" to bug 1728596
(not this bug). Thanks!

** Tags added: verification-failed

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

This bug was fixed in the package linux - 4.10.0-38.42

---
linux (4.10.0-38.42) zesty; urgency=low

  * linux: 4.10.0-38.42 -proposed tracker (LP: #1722330)

  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB

  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization

  * Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB (LP: #1700657)
- mfd: intel-lpss: Add missing PCI ID for Intel Sunrise Point LPSS devices

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.

  * CVE-2017-1000252
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ

  * CVE-2017-10663
- f2fs: sanity check checkpoint segno and blkoff

  * xfstest sanity checks on seek operations fails (LP: #1696049)
- xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff()

  * [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results
in call traces and system goes for reboot. (LP: #1706033)
- powerpc/64s: Handle data breakpoints in Radix mode

  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi: ses: do not add a device to an enclosure if enclosure_add_links()
  fails.

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * More migrations with constant load (LP: #1713576)
- sched/fair: Prefer sibiling only if local group is under-utilized

  * New PMU fixes for marked events. (LP: #1716491)
- powerpc/perf: POWER9 PMU stops after idle workaround

  * CVE-2017-14340
- xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present

  * [Zesty][Yakkety] rtl8192e bug fixes (LP: #1698470)
- staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.
- staging: rtl8192e: fix 2 byte alignment of register BSSIDR.
- staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.
- staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  * Stranded with ENODEV after mdadm --readonly (LP: #1706243)
- md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring

  * CVE-2017-11176
- mqueue: fix a use-after-free in sys_mq_notify()

  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- Revert "UBUNTU: SAUCE: seccomp: log actions even when audit is disabled"
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing

  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- Revert "UBUNTU: SAUCE: seccomp: log actions even when audit is disabled"
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW

  * Backport recent bbr bugfixes to 4.10 kernel (LP: #1708604)
- tcp_bbr: cut pacing rate only if filled pipe
- tcp_bbr: introduce bbr_bw_to_pacing_rate() helper
- tcp_bbr: introduce bbr_init_pacing_rate_from_rtt() helper
- tcp_bbr: remove sk_pacing_rate=0 transient during init
- tcp_bbr: init pacing rate on first RTT sample

  * [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0 (LP: #1716483)
- arm64: kernel: restrict /dev/mem read() calls to linear region

 -- Kleber Sacilotto de Souza   Tue, 10 Oct
2017 13:49:34 +0200

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

This bug was fixed in the package linux - 4.10.0-38.42

---
linux (4.10.0-38.42) zesty; urgency=low

  * linux: 4.10.0-38.42 -proposed tracker (LP: #1722330)

  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB

  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization

  * Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB (LP: #1700657)
- mfd: intel-lpss: Add missing PCI ID for Intel Sunrise Point LPSS devices

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.

  * CVE-2017-1000252
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ

  * CVE-2017-10663
- f2fs: sanity check checkpoint segno and blkoff

  * xfstest sanity checks on seek operations fails (LP: #1696049)
- xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff()

  * [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results
in call traces and system goes for reboot. (LP: #1706033)
- powerpc/64s: Handle data breakpoints in Radix mode

  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi: ses: do not add a device to an enclosure if enclosure_add_links()
  fails.

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * More migrations with constant load (LP: #1713576)
- sched/fair: Prefer sibiling only if local group is under-utilized

  * New PMU fixes for marked events. (LP: #1716491)
- powerpc/perf: POWER9 PMU stops after idle workaround

  * CVE-2017-14340
- xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present

  * [Zesty][Yakkety] rtl8192e bug fixes (LP: #1698470)
- staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.
- staging: rtl8192e: fix 2 byte alignment of register BSSIDR.
- staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.
- staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  * Stranded with ENODEV after mdadm --readonly (LP: #1706243)
- md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring

  * CVE-2017-11176
- mqueue: fix a use-after-free in sys_mq_notify()

  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- Revert "UBUNTU: SAUCE: seccomp: log actions even when audit is disabled"
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing

  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- Revert "UBUNTU: SAUCE: seccomp: log actions even when audit is disabled"
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW

  * Backport recent bbr bugfixes to 4.10 kernel (LP: #1708604)
- tcp_bbr: cut pacing rate only if filled pipe
- tcp_bbr: introduce bbr_bw_to_pacing_rate() helper
- tcp_bbr: introduce bbr_init_pacing_rate_from_rtt() helper
- tcp_bbr: remove sk_pacing_rate=0 transient during init
- tcp_bbr: init pacing rate on first RTT sample

  * [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0 (LP: #1716483)
- arm64: kernel: restrict /dev/mem read() calls to linear region

 -- Kleber Sacilotto de Souza   Tue, 10 Oct
2017 13:49:34 +0200

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000252

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10663

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10911

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-11176

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-14340

** Changed

[Touch-packages] [Bug 1728385] syslog.txt

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1728385/+attachment/5000314/+files/syslog.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1728385/+attachment/5000303/+files/JournalErrors.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] getfacl.txt

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1728385/+attachment/5000312/+files/getfacl.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] rfkill.txt

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1728385/+attachment/5000313/+files/rfkill.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1728385/+attachment/5000310/+files/ProcModules.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1728385/+attachment/5000311/+files/UdevDb.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1728385/+attachment/5000309/+files/ProcInterrupts.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1728385/+attachment/5000305/+files/Lsusb.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

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

apport information

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

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1728385/+attachment/5000303/+files/JournalErrors.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1728385/+attachment/5000304/+files/Lspci.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1728385/+attachment/5000306/+files/ProcCpuinfo.txt

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] ProcEnviron.txt

apport information

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

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

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

apport information

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

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

apport information

** Tags added: apport-collected artful wayland-session

** Description changed:

  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2017-10-24 (6 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: LENOVO 20GJ001HMH
+ Package: bluez 5.46-0ubuntu3
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
+ Tags:  artful wayland-session
+ Uname: Linux 4.13.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/13/2016
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: R0CET26W (1.14 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20GJ001HMH
+ dmi.board.vendor: LENOVO
+ dmi.board.version: S
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad S2
+ dmi.product.name: 20GJ001HMH
+ dmi.product.version: ThinkPad S2
+ dmi.sys.vendor: LENOVO
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
+   DOWN 
+   RX bytes:14933 acl:0 sco:0 events:2414 errors:0
+   TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

Title:
  Failed to set mode: Blocked through rfkill (0x12)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

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

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

[Touch-packages] [Bug 1728587] Re: No audio device after upgrade to Kubuntu 17.10

2017-10-30 Thread alphablue52

I just found a fix here:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519

You have to remove and reinstall alsa-base and pulseaudio.

I figured it out when I tried to start pulseaudio directly, and got this
error message:

W: [pulseaudio] module.c: module-combine is deprecated: Please use 
module-combine-sink instead of module-combine!
W: [pulseaudio] module-combine.c: We will now load module-combine-sink. Please 
make sure to remove module-combine from your configuration.
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Hintergrunddienst konnte nicht initialisiert werden.


After 
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio
sudo alsa force-reload

It works again.

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

Title:
  No audio device after upgrade to Kubuntu 17.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading Kubuntu 17.04 to 17.10, KDE lost the audio device
  (Realtek sound card on a Lenovo Thinkpad T470s). Volume icon is on
  mute, with info-popup given: "No output or input devices found". Audio
  backend is Phonon GStreamer. Re-installing pulseaudio didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Mon Oct 30 13:58:15 2017
  InstallationDate: Installed on 2017-08-25 (66 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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 artful on 2017-10-30 (0 days ago)
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1728587] Re: No audio device after upgrade to Kubuntu 17.10

2017-10-30 Thread alphablue52

Same problem for me:
after upgrading to 17.10, no more sound devices shown by pulse.
Lenovo Ideapad Z510 with Intel hda soundchip.
Alsainfo attached.

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728587/+attachment/5000294/+files/alsa-info.txt

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

Title:
  No audio device after upgrade to Kubuntu 17.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading Kubuntu 17.04 to 17.10, KDE lost the audio device
  (Realtek sound card on a Lenovo Thinkpad T470s). Volume icon is on
  mute, with info-popup given: "No output or input devices found". Audio
  backend is Phonon GStreamer. Re-installing pulseaudio didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Mon Oct 30 13:58:15 2017
  InstallationDate: Installed on 2017-08-25 (66 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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 artful on 2017-10-30 (0 days ago)
  dmi.bios.date: 04/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET31W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET31W(1.10):bd04/17/2017:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices

2017-10-30 Thread MaskedDriver

** Description changed:

  I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289
  Ultrabook that has a single 3.5mm jack for both input and output. This
  installation is in a dual-boot situation with Windows 10. This device
  has UEFI secure boot enabled.
  
  The combo jack works perfectly in Windows 10, however, when I plug in a
  headset or headphone of any kind, it does not register that anything has
  been plugged in. The laptop is connected to a Dell dock via USB-C, so
  there is also USB Audio (Output only) available on the dock, but that
  also does not work. It worked for one session yesterday on my dock at
  work, however it does not work at my dock that I have at home. The
  internal speakers and the microphone built into the lid work fine. The
  Combo jack also does not work disconnected from the dock.
  
  I have installed gnome and gnome-shell, but it does not work in either
  gnome or unity (I continue to use lightdm so that I can switch back and
  forth).
  
  Neither Unity nor Gnome bring up any kind of "What Did You Plug In"
  dialog.
  
  alsamixer does not have a headphone option as expected
  
  pavucontrol does not allow me to select "Headphones" under the Built-in
  Audio Analog Stereo Port
  
  I have attempted to tweak settings in hdajackretask to no success
  
  I have attempted to add:
  
  options snd_hda_intel model=dell-headset-multi(dell-headset-dock,
  generic, auto, headset-mic, etc) to no success
  
+ I have also tried updating my kernel to 4.13.10, to no success.
+ 
  Outputs:
  --
  uname -sr
  Linux 4.10.0-37-generic
  --
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  
  cat /proc/asound/car*/co* | grep Codec
  Codec: Realtek ALC3253
  Codec: Intel Kabylake HDMI

** Description changed:

  I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289
  Ultrabook that has a single 3.5mm jack for both input and output. This
  installation is in a dual-boot situation with Windows 10. This device
  has UEFI secure boot enabled.
  
  The combo jack works perfectly in Windows 10, however, when I plug in a
  headset or headphone of any kind, it does not register that anything has
  been plugged in. The laptop is connected to a Dell dock via USB-C, so
  there is also USB Audio (Output only) available on the dock, but that
  also does not work. It worked for one session yesterday on my dock at
  work, however it does not work at my dock that I have at home. The
  internal speakers and the microphone built into the lid work fine. The
  Combo jack also does not work disconnected from the dock.
  
  I have installed gnome and gnome-shell, but it does not work in either
  gnome or unity (I continue to use lightdm so that I can switch back and
  forth).
  
  Neither Unity nor Gnome bring up any kind of "What Did You Plug In"
  dialog.
  
  alsamixer does not have a headphone option as expected
  
  pavucontrol does not allow me to select "Headphones" under the Built-in
  Audio Analog Stereo Port
  
  I have attempted to tweak settings in hdajackretask to no success
  
  I have attempted to add:
  
  options snd_hda_intel model=dell-headset-multi(dell-headset-dock,
  generic, auto, headset-mic, etc) to no success
  
  I have also tried updating my kernel to 4.13.10, to no success.
  
+ I also tried 17.10 to no success.
+ 
  Outputs:
  --
  uname -sr
  Linux 4.10.0-37-generic
  --
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1]
    Subdevices: 1/1
    Subdevice #0:

[Touch-packages] [Bug 1727566] Re: extra left-behind domains break domain name rsolution

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

Title:
  extra left-behind domains break domain name rsolution

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This seems related to LP: #1717995 but that is marked fixed.

  I used my laptop at work, where I have a docking station with USB
  ethernet included (interface enx0050b6cf4d4a).  The dhcp on the wired
  ethernet includes my work domain, purestorage.com.  I undocked,
  suspended, and came home, where I have no USB ethernet (just wifi
  wlp4s0), and dhcp on wifi doesn't mention purestorage.com.  However, I
  still have leftover state that stops purestorage.com names from
  resolving:

  $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search lan purestorage.com dev.purestorage.com

  $ systemd-resolve --status
  Global
DNS Domain: lan
purestorage.com
dev.purestorage.com
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 3 (wlp4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 10.1.0.1
fda0:5173:b519::1
DNS Domain: lan

  Link 2 (enp0s31f6)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  It seems there are still issues around network interfaces being
  removed but leaving behind their DNS config.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 17:48:47 2017
  InstallationDate: Installed on 2016-09-01 (419 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 13d3:5248 IMC Networks 
   Bus 001 Device 005: ID 056a:5087 Wacom Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-26 (91 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st

[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2017-10-30 Thread Christian Kujau

Launchpad really needs something similar to RESOLVED/DUPLICATE, as I had
to crawl through the whole report to find out that this is considered a
duplicate of 578431.

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

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

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

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-10-30 Thread Imre Széll

After upgrading from 17.04 I had this issue. Neither could I connect to
an external audio device via Bluetooth.

I started pulseaudio in verbose mode (-vvv) and found that the module
"module-switch-on-connect" is already loaded when it is tried to load
again. I commented out the following lines in /etc/pulse/default.pa:

.ifexists module-switch-on-connect.so
load-module module-switch-on-connect
.endif

This workaround solves the problem permanently. I was able to use my USB
Bluetooth adapter to connect external playback device.

The module "module-switch-on-connect" could be loaded by default or some
dependency...

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  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.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr: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: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1666676] Re: Install tracker by default

** Description changed:

  Benefits
  
  
  1. It speeds up searching for files in the Files app.
  
  2. It enables full-text search in the Files app. In other words, you can
  look for files that contain specific words, instead of searching just by
  filename.
  
  3. It allows the Batch Rename feature in the Files app able to rename
  based on file metadata. For instance, you can use the Artist name for
  properly tagged music files as part of the new file name.
  
  4. It enables file and folder search in the Activities Overview on
  GNOME. Without tracker, this is a functional regression from Unity and
  is noticed by a lot of people.
  
  Other Info
  --
- You can customize the folders it indexes from Settings > Search > gear button.
+ You can customize the folders it indexes from Settings > Search > gear 
button. (LP: #1702878)
+ 
+ How to Install
+ ==
+ Until this is installed by default, you can install it yourself. Run this 
command in a terminal then log out and log back in (LP: #1697769):
+ 
+ sudo apt install tracker
  
  Original Bug Report
  ===
  For Nautilus' built-in search to not be very slow, Nautilus needs to use 
tracker for search.
  
  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)
  
  To not cripple Ubuntu GNOME, it was previously decided to let Nautilus
  build against tracker but not use that functionality on Unity. See this
  patch:
  
  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch
  
  This bug is requesting that patch be dropped and the extra tracker
  components be allowed into main and installed by default in Unity.

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

Title:
  Install tracker by default

Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Benefits
  

  1. It speeds up searching for files in the Files app.

  2. It enables full-text search in the Files app. In other words, you
  can look for files that contain specific words, instead of searching
  just by filename.

  3. It allows the Batch Rename feature in the Files app able to rename
  based on file metadata. For instance, you can use the Artist name for
  properly tagged music files as part of the new file name.

  4. It enables file and folder search in the Activities Overview on
  GNOME. Without tracker, this is a functional regression from Unity and
  is noticed by a lot of people.

  Other Info
  --
  You can customize the folders it indexes from Settings > Search > gear 
button. (LP: #1702878)

  How to Install
  ==
  Until this is installed by default, you can install it yourself. Run this 
command in a terminal then log out and log back in (LP: #1697769):

  sudo apt install tracker

  Original Bug Report
  ===
  For Nautilus' built-in search to not be very slow, Nautilus needs to use 
tracker for search.

  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)

  To not cripple Ubuntu GNOME, it was previously decided to let Nautilus
  build against tracker but not use that functionality on Unity. See
  this patch:

  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

  This bug is requesting that patch be dropped and the extra tracker
  components be allowed into main and installed by default in Unity.

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

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

[Touch-packages] [Bug 1728653] Re: Update evolution-data-server to 3.26.2

** Description changed:

  Impact
  ==
- evolution-data-server has released a new stable bugfix release. Updating 
e-d-s is required to update evolution to 3.26.2 (LP: #)
+ evolution-data-server (e-d-s) has released a new stable bugfix release.
+ (These will happen about once every month or two until 3.28 is released.)
+ 
+ Updating e-d-s is required to update evolution to 3.26.2 (LP: #1728655)
  
  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26
  
  Test Case
  =
  After installing the update, restart your computer.
  
  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.
  
  Regression Potential
  
  GNOME 3.26 distros will be shipping this update.
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

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

Title:
  Update evolution-data-server to 3.26.2

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  evolution-data-server (e-d-s) has released a new stable bugfix release.
  (These will happen about once every month or two until 3.28 is released.)

  Updating e-d-s is required to update evolution to 3.26.2 (LP:
  #1728655)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

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

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

[Touch-packages] [Bug 1728658] [NEW] Blank screens when connecting OneLink dock with a display connected

2017-10-30 Thread Sergey Menshikov

Public bug reported:

Lenovo X1 Carbon 4th gen
OneLink dock
2 x 2K dell displays

Connecting the dock without displays works fine
Connecting the dock with even one display connected results in blank screens on 
all displays

The combination worked fine on 17.04

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Oct 30 09:49:58 2017
DistUpgraded: 2017-10-28 15:48:46,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 4.10.0-37-generic, x86_64: installedError! Could not locate 
dkms.conf file.
 File:  does not exist.
 
 acpi-call, 1.1.0, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 520 [17aa:2238]
InstallationDate: Installed on 2017-04-14 (199 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: LENOVO 20FB002LUS
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bc08c404-a63f-4e47-b021-49cc7c200f5f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-28 (1 days ago)
dmi.bios.date: 07/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET53W (1.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FB002LUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FB002LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB002LUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 4th
dmi.product.name: 20FB002LUS
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
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+git20170309-0ubuntu1
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 artful ubuntu wayland-session

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

Title:
  Blank screens when connecting OneLink dock with a display connected

Status in xorg package in Ubuntu:
  New

Bug description:
  Lenovo X1 Carbon 4th gen
  OneLink dock
  2 x 2K dell displays

  Connecting the dock without displays works fine
  Connecting the dock with even one display connected results in blank screens 
on all displays

  The combination worked fine on 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 30 09:49:58 2017
  DistUpgraded: 2017-10-28 15:48:46,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.10.0-37-generic, x86_64: installedError! Could not 
locate dkms.conf file.
   File:  does not exist.
   
   acpi-call, 1.1.0, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 520 [17aa:2238]
  InstallationDate: Installed on 2017-04-14 (199 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: LENOVO 20FB002LUS
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash

[Touch-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2017-10-30 Thread Bruce Duncan

** Package changed: xorg (Ubuntu) => linux-firmware (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/1728651

Title:
  System hangs after iwlwifi firmware crash

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
  InstallationDate: Installed on 2016-09-09 (416 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG6354JW5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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-firmware/+bug/1728651/+subscriptions

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

[Touch-packages] [Bug 1728653] [NEW] Update evolution-data-server to 3.26.2

Public bug reported:

Impact
==
evolution-data-server has released a new stable bugfix release. Updating e-d-s 
is required to update evolution to 3.26.2 (LP: #)

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26

Test Case
=
After installing the update, restart your computer.

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

GNOME 3.26 distros will be shipping this update.

There is a micro-release exception for GNOME:
https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

3.22.6 introduced a regression in pop3 support that was fixed within a
week by 3.22.7.

** Affects: evolution-data-server (Ubuntu)
 Importance: Medium
 Status: Fix Committed

** Affects: evolution-data-server (Ubuntu Artful)
 Importance: Medium
 Status: Triaged


** Tags: artful upgrade-software-version

** Also affects: evolution-data-server (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: evolution-data-server (Ubuntu Artful)
   Status: New => Triaged

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

Title:
  Update evolution-data-server to 3.26.2

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  evolution-data-server has released a new stable bugfix release. Updating 
e-d-s is required to update evolution to 3.26.2 (LP: #)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

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

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

[Touch-packages] [Bug 1728596] Re: APT killed the OS load

2017-10-30 Thread Julian Andres Klode

How did you try to update your system? It sounds like you used one of
the reboot to upgrade packagekit front-ends, not apt.

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

Title:
  APT killed the OS load

Status in apt package in Ubuntu:
  New

Bug description:
  after trying to update the system, the computer crashed, after which
  it refused to boot. The download was made with the previous version of
  the kernel - 4.10.0-28-generic (x86_64).

  at startup, the computer began to ask for a password to replace the second 
disk, after entering the user's password for the current OS, the download 
continues. For this drive in another installation of this OS, I entered a 
different password. Enter the password does not match the password of the 
current user (root) did not try.
  When you reboot, the password request for the disk is missing. However, in 
working with this version of the OS, this is periodically observed for my 
computer.

  The system is freshly installed. It already had one unresolved problem.
  https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1728550

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 30 18:16:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1728596/+subscriptions

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

[Touch-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2017-10-30 Thread Bruce Duncan

I don't easily see the firmware hang message in the attached files, so
I'm pasting it here:

Microcode SW error detected.  Restarting 0x8200.
Start IWL Error Log Dump:
Status: 0x0200, count: 6
0x0038 | BAD_COMMAND 
0x0220 | trm_hw_status0
0x | trm_hw_status1
0x00010040 | branchlink2
0x00028DA6 | interruptlink1
0x | interruptlink2
0x009A001C | data1
0x029B | data2
0x009B | data3
0x31818996 | beacon time
0xDA54AE68 | tsf low
0x0927 | tsf hi
0x | time gp1
0x34A281CF | time gp2
0x0001 | uCode revision type
0x001F | uCode version major
0x00082201 | uCode version minor
0x0201 | hw version
0x00489008 | board version
0x009A001C | hcmd
0x24022080 | isr0
0x0100 | isr1
0x2820180A | isr2
0x00417CC0 | isr3
0x | isr4
0x0099014E | last cmd Id
0x | wait_event
0x4288 | l2p_control
0x00018030 | l2p_duration
0x03BF | l2p_mhvalid
0x00E7 | l2p_addr_match
0x000D | lmpm_pmg_sel
0x15062149 | timestamp
0xE0F0 | flow_handler
Start IWL Error Log Dump:
Status: 0x0200, count: 7
0x0070 | ADVANCED_SYSASSERT
0x | umac branchlink1
0xC0086B70 | umac branchlink2
0xC00844E0 | umac interruptlink1
0xC00844E0 | umac interruptlink2
0x0800 | umac data1
0xC00844E0 | umac data2
0xDEADBEEF | umac data3
0x001F | umac major
0x00082201 | umac minor
0xC088627C | frame pointer
0xC088627C | stack pointer
0x009A001C | last host cmd
0x | isr status reg
FW Error notification: type 0x cmd_id 0x1C
FW Error notification: seq 0x009A service 0x001C
FW Error notification: timestamp 0x34A1CCC1

(I trimmed words from the start of each line like: "Oct 23 16:31:59 fry
kernel: [29533.463611] iwlwifi :02:00.0:")

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

Title:
  System hangs after iwlwifi firmware crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]

[Touch-packages] [Bug 1728651] [NEW] System hangs after iwlwifi firmware crash

2017-10-30 Thread Bruce Duncan

Public bug reported:

Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
unpredictable times. I have experienced probably 20 hangs. Once the
system is hung no mouse movement, NumLock toggle, VT switch,
Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
audio playing is stuck looping in the hardware buffer. The system is
really stuck. Only the keyboard backlight is still responsive.

The only correlation I have noticed is that the system only hangs if
WiFi is enabled. This morning I experienced two hangs in ten minutes
necessitating reboots. Having disabled WiFi the system has been stable
since ~1100 (~5 hours).

Often, I see a iwlwifi hardware reset in the logs before the system
dies:

/var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
:02:00.0: Microcode SW error detected.  Restarting 0x8200.

(apport has hopefully uploaded the full log, please lmk if not).
Sometimes the message doesn't make it into the logs, and ext4 truncates
the file at the next mount.

There seems to be no correlation with any messages immediately before
the wifi chip dies. It doesn't seem to matter whether I'm at home or at
work. I have wired ethernet at work simultaneously with wifi, but the
wifi provides IPv6 so I would imagine most traffic uses wifi, so it's
hard to say whether there's any effect of the traffic load on the
probability of failure.

Here is a sample of the firmware load:

/var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
/var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
/var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
/var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
/var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

Any help appreciated.

Thanks,
Bruce

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Oct 30 16:15:43 2017
DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: kubuntu
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
InstallationDate: Installed on 2016-09-09 (416 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP EliteBook 820 G3
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
dmi.bios.date: 11/01/2016
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.13
dmi.board.name: 807C
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.74
dmi.chassis.asset.tag: 5CG6354JW5
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 820 G3
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
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 artful fonts kubuntu

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

Title:
  System hangs after iwlwifi firmware crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping

[Touch-packages] [Bug 1722843] Re: Updates Block

2017-10-30 Thread Leonidas S. Barbosa

** Information type changed from Private Security to Public

** Tags added: trusty

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

Title:
  Updates  Block

Status in xorg package in Ubuntu:
  New

Bug description:
  ERRO LINUX MINT – DIFICULDADE DE ATUALIZAÇÃO

  
  W: Falhou ao buscar http://packages.domain.com/dists/trusty/InRelease  

  W: Falhou ao buscar cdrom://Linux Mint 17.1 _Rebecca_ - Release i386
  20141126/dists/trusty/contrib/binary-i386/Packages  Por favor, use o
  apt-cdrom para fazer com que este CD-ROM seja reconhecido pelo APT. O
  apt-get update não pode ser usado para adicionar novos CD-ROMs

  W: Falhou ao buscar cdrom://Linux Mint 17.1 _Rebecca_ - Release i386
  20141126/dists/trusty/main/binary-i386/Packages  Por favor, use o apt-
  cdrom para fazer com que este CD-ROM seja reconhecido pelo APT. O apt-
  get update não pode ser usado para adicionar novos CD-ROMs

  W: Falhou ao buscar cdrom://Linux Mint 17.1 _Rebecca_ - Release i386
  20141126/dists/trusty/non-free/binary-i386/Packages  Por favor, use o
  apt-cdrom para fazer com que este CD-ROM seja reconhecido pelo APT. O
  apt-get update não pode ser usado para adicionar novos CD-ROMs

  W: Falhou ao buscar
  http://packages.domain.com/dists/trusty/Release.gpg  Não foi possível
  ligar a packages.domain.com:http:

  W: Falhou o download de alguns ficheiros de índice. Foram ignorados ou
  os antigos foram usados em seu lugar.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CurrentDesktop: X-Cinnamon
  Date: Wed Oct 11 12:20:42 2017
  InstallationDate: Installed on 2017-09-09 (31 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1666676] Re: Install tracker by default