[Touch-packages] [Bug 1756755] Re: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-08-19 Thread GMPH
** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => GMPH (gmphtravel)

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

Title:
  package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from xenial to bionic failed the removal of systemd-shim.
  I think the messages were the same as the following, that I can reproduce by 
running "apt upgrade" from the upgraded system:

  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 18 22:52:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-11 (1892 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-03-18 (0 days ago)

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

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


[Touch-packages] [Bug 1777942] Re: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-insta

2018-08-19 Thread Launchpad Bug Tracker
[Expired for pam (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade:
  package libpam-runtime is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in pam package in Ubuntu:
  Expired

Bug description:
  I was trying to install gparted when this happed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-runtime 1.1.8-3.2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
  Uname: Linux 4.4.0-31-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  Date: Wed Jun 20 23:06:02 2018
  DuplicateSignature:
   package:libpam-runtime:1.1.8-3.2ubuntu2
   Processing triggers for libc-bin (2.23-0ubuntu10) ...
   dpkg: error processing package libpam-runtime (--configure):
package libpam-runtime is not ready for configuration
  ErrorMessage: package libpam-runtime is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-06-18 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: pam
  Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: 
package libpam-runtime is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1787756] Re: system booting locked at login

2018-08-19 Thread Daniel van Vugt
I can't tell what the problem is.


What do you see? What is going wrong?

** Summary changed:

- 18.04 lts
+ system booting locked at login

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

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

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

Title:
  system booting locked at login

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  system booting locked at login

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  BootLog:
   [* ] (1 of 11) A start job is running for 
dev-disk-by\x2dpath-pci\x2d:00:1d.0\x2dusb\x2d0:1.3:1.0\x2dscsi\x2d0:0:0:0.device
 (29s / 1min 30s)
[  OK  ] Started Modem Manager.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Aug 19 00:27:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 2nd Generation Core Processor 
Family Integrated Graphics Controller [1179:fb20]
  InstallationDate: Installed on 2016-07-07 (771 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite C850
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=0b46d6d7-62a9-4dc4-b79e-d3885d2434df ro plymouth:debug drm.debug=0xe
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd09/21/2012:svnTOSHIBA:pnSatelliteC850:pvrPSC74G-01S001:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C850
  dmi.product.version: PSC74G-01S001
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Aug 19 00:10:29 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputTOSHIBA Web Camera: TOSHIBA Web KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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


[Touch-packages] [Bug 1787651] Re: Mouse stops clicking using Jabra Evolve 65 via bluetooth

2018-08-19 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (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/1787651

Title:
  Mouse stops clicking using Jabra Evolve 65 via bluetooth

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I'm experiencing a problem using a Jabra Evolve 65. When using the usb
  bluetooth dongle every time a sound is reproduced the mouse stops
  clicking.

  When i'm using the Jabra USB cable instead, it works correclty

  Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-lowlatency 4.10.3
  Uname: Linux 4.10.0-14-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Aug 17 17:32:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2245]
  InstallationDate: Installed on 2016-04-24 (845 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20HES4KF02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-lowlatency 
root=/dev/mapper/vg_ldt-lv_root ro resume=/dev/mapper/vg_ldt-lv_swap
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HES4KF02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET68W(1.43):bd11/10/2017:svnLENOVO:pn20HES4KF02:pvrThinkPadT470:rvnLENOVO:rn20HES4KF02:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HES4KF02
  dmi.product.version: ThinkPad T470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Aug 17 15:57:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4157 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1787613] Re: after fresh install again broken dependencies

2018-08-19 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (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/1787613

Title:
  after fresh install again broken dependencies

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  the built-in screen does not work properly (since 8 months, after an
  update of 16.04LTS). The interesting message is:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-20
  Depends: xserver-xorg-core (>= 2:1.17.99.902)
  E: Unable to correct problems, you have held broken packages.

  
  LAPTOP IDEAPAD 15IBD

  external monitor works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug 17 17:41:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:382a]
  InstallationDate: Installed on 2018-08-15 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO INVALID
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=4b7dd599-0b13-489a-9717-7b9cf1555ea0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN11WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN11WW:bd06/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNODPK:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.family: IDEAPAD
  dmi.product.name: INVALID
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Aug 17 16:08:28 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1787613/+subscriptions

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


[Touch-packages] [Bug 1787645] Re: Most, but not all, boots from cold, I get a Low Graphics Mode error

2018-08-19 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (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/1787645

Title:
  Most, but not all, boots from cold, I get a Low Graphics Mode error

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  After an update (kernel?), I have begun to receive the message
  "Running in Low Graphics Mode" at boot. I can tell it to use Default
  setting from the options it offers, and get by it, after which things
  look and work normally until a reboot, which may or may not occur
  correctly.

  If I select extra graphics debug messages and display boot messages in
  Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
  problem begins again.

  I don't know which update caused it, but it was somewhere around mid
  or early May.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 17 12:02:03 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-32-generic, x86_64: installed
   virtualbox, 5.1.38, 4.4.0-133-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1502 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro quiet plymouth:debug=1 
plymouth:debug=1=1=1=1=1 splash plymouth:debug=1=1=1=1=1=1=1=1=1 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (607 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Aug 17 12:00:19 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1787645/+subscriptions

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


[Touch-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost

2018-08-19 Thread Daniel van Vugt
This is surprising. It sounds like reconnecting is disabled by default
unless you specify exactly which devices to reconnect in
/etc/bluetooth/main.conf:

# The ReconnectUUIDs defines the set of remote services that should try
# to be reconnected to in case of a link loss (link supervision
# timeout). The policy plugin should contain a sane set of values by
# default, but this list can be overridden here. By setting the list to
# empty the reconnection feature gets disabled.
#ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 
111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb

So maybe try editing /etc/bluetooth/main.conf and change:

  #ReconnectUUIDs=1112--1000-8000-00805f9b34fb,
111f--1000-8000-00805f9b34fb,
110a--1000-8000-00805f9b34fb

to:

  ReconnectUUIDs=1124--1000-8000-00805f9b34fb,
1812--1000-8000-00805f9b34fb

in an attempt to auto-reconnect your Human Interface Devices.

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

Title:
  Bluetooth keyboard won't connect again after connection was lost

Status in bluez package in Ubuntu:
  New

Bug description:
  After my Bluetooth keyboard from Logitech (K380) looses its
  connection, either after a Ubuntu restart or by manually turning the
  keyboard off an on, it won't connect any more. Additionally, while the
  keyboard tries to reestablish the connection, my Logitech Bluetooth
  mouse (M590) looses its connection too! After that I can't establish
  any Bluetooth connection at all. Only a "sudo service bluetooth
  restart" helps.

  Then my mouse reconnects easily, if it's not disrupted by my keyboard.
  So I'm only possible to use my mouse and not the keyboard, because
  while it tries to reconnect, it kills the connection of my mouse and
  everything starts over again.

  I've also tried to reconnect the keyboard through "bluetoothctl", but
  without success:

  $ bluetoothctl paired-devices
  Device 34:88:5D:42:7E:03 Keyboard K380
  Device FA:6A:9E:DA:2B:30 M585/M590

  $ bluetoothctl connect 34:88:5D:42:7E:03
  Attempting to connect to 34:88:5D:42:7E:03
  Failed to connect: org.bluez.Error.Failed

  
  Both devices are "trusted":

  $ bluetoothctl info 34:88:5D:42:7E:03
  Device 34:88:5D:42:7E:03 (public)
Name: Keyboard K380
Alias: Keyboard K380
Class: 0x2540
Icon: input-keyboard
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v046DpB342d4200

  $ bluetoothctl info FA:6A:9E:DA:2B:30
  Device FA:6A:9E:DA:2B:30 (random)
Name: M585/M590
Alias: M585/M590
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
Modalias: usb:v046DpB01Bd0007

  $ bluetoothctl show
  Controller 2C:6F:C9:44:57:E0 (public)
Name: mir
Alias: mir
Class: 0x000c010c
Powered: yes
Discoverable: yes
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no

  
  The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing:

  bluetoothctl
  remove XX:XX:XX:XX:XX:XX
  exit
  sudo service bluetooth restart
  bluetoothctl
  scan on
  trust XX:XX:XX:XX:XX:XX
  pair XX:XX:XX:XX:XX:XX
  connect XX:XX:XX:XX:XX:XX 
  exit

  
  This keyboard works flawlessly with my Android 

[Touch-packages] [Bug 1787581] Re: sudo apt-get install xserver-xorg-video-intel

2018-08-19 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (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/1787581

Title:
  sudo apt-get install xserver-xorg-video-intel

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  While attempting to install display drivers.

  My laptop's battery gets drained too early because of power setting &
  don't have hibernate option.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug 17 16:33:57 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2212]
 Subsystem: Hewlett-Packard Company GF117M [GeForce 610M/710M/810M/820M / 
GT 620M/625M/630M/720M] [103c:2212]
  InstallationDate: Installed on 2018-07-23 (24 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Hewlett-Packard 15-r014tx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=1ce01056-3b54-40dc-8a89-fa42de6dc8ab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pn15-r014tx:pvr098511450E1000100:rvnHewlett-Packard:rn2212:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: 15-r014tx
  dmi.product.version: 098511450E1000100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Aug 17 10:07:22 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1787873] [NEW] package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

2018-08-19 Thread Stephen Bardowell
Public bug reported:

Ubuntu 16.04 -> 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: hicolor-icon-theme 0.17-2
Uname: Linux 4.15.16-041516-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Fri Aug 17 09:17:18 2018
Dependencies:
 
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-10-07 (681 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 -> 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  Uname: Linux 4.15.16-041516-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 17 09:17:18 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-10-07 (681 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1787873/+subscriptions

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


[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-08-19 Thread August Pamplona
But the directions mentioned elsewhere from https://dev.solus-
project.com/T5224 do work even thought they appear to break Bluetooth
(even with the updated instructions workaround mentioned in that
thread).

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1770166] Re: The brightness of the notebook

2018-08-19 Thread Daniel van Vugt
Brightness and other custom keybindings are the responsibility of the
kernel. Although in some cases a BIOS update helps too.

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

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

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

Title:
  The brightness of the notebook

Status in linux package in Ubuntu:
  New

Bug description:
  The brightness of the notebook does not lower or rise with the FN key. Acer 
Aspire 5742 i3-380m 6gb ram ssd kingston 120gb.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0487]
  InstallationDate: Installed on 2018-06-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Aspire 5742
  Package: xorg 1:7.7+19ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742
  dmi.board.vendor: Acer
  dmi.board.version: V1.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.18
  dmi.modalias: 
dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5742
  dmi.product.version: V1.18
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1083310] Re: cups returns malformed UTF-8

2018-08-19 Thread gf
Thanks for the update, Роман. I will close the report now.
Have a great day!
:)
G

Closed per reporter’s feedback.

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

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

Title:
  cups returns malformed UTF-8

Status in cups package in Ubuntu:
  Invalid

Bug description:
  This is Ubuntu 12.04, libcups2 1.5.3-0ubuntu4.

  I noticed gedit and evince were crashing whenever I opened the print
  dialog. I'm attaching an example stack trace from gedit.

  Eventually I traced the bug to CUPS. gedit crashes in GTK+ code when
  trying to process an invalid UTF-8 string starting with "Параметры,
  разрешенн". That string comes from my PPD file (will attach), and its
  byte length coincides with the size of ppd_group_t::text in CUPS,
  which means that it's being improperly truncated within CUPS.

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

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


[Touch-packages] [Bug 1787871] [NEW] update-ca-certificates does not update browsers

2018-08-19 Thread modolo
Public bug reported:

Until Ubuntu 16.04 to add a certificate authority (CA) I would put the
files in '/usr/local/share/ca-certificates' and then run the 'sudo
update-ca-certificates'

After that, Chrome and Firefox browsers started to identify sites signed
with the new CA added as secure.

With Ubuntu 18.04 this behavior has changed. After adding the new
certificate authority (CA) to '/usr/local/share/ca-certificates' and
running the sudo command sudo update-ca-certificates the Firefox and
Chrome browsers continue to indicate that the sites are not secure.

I am required to manually import the CAs into each of the browsers.

Is there any new command that has the same behavior as Ubuntu 16.04 in
adding new CAs?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_24_26_generic_42
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 21:48:32 2018
InstallationDate: Installed on 2018-03-30 (142 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  update-ca-certificates does not update browsers

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Until Ubuntu 16.04 to add a certificate authority (CA) I would put the
  files in '/usr/local/share/ca-certificates' and then run the 'sudo
  update-ca-certificates'

  After that, Chrome and Firefox browsers started to identify sites
  signed with the new CA added as secure.

  With Ubuntu 18.04 this behavior has changed. After adding the new
  certificate authority (CA) to '/usr/local/share/ca-certificates' and
  running the sudo command sudo update-ca-certificates the Firefox and
  Chrome browsers continue to indicate that the sites are not secure.

  I am required to manually import the CAs into each of the browsers.

  Is there any new command that has the same behavior as Ubuntu 16.04 in
  adding new CAs?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_24_26_generic_42
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 21:48:32 2018
  InstallationDate: Installed on 2018-03-30 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1787871/+subscriptions

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


[Touch-packages] [Bug 1783626] Re: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed

2018-08-19 Thread Dimitri John Ledkov
fixed in cosmic release. unblocking.

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

** Tags removed: block-proposed

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

Title:
  systemd in cosmic should not migrate until apparmor abstract socket
  locks mediation is fixed

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd in cosmic should not migrate until apparmor abstract socket
  locks mediation is fixed

  See https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227

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

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


[Touch-packages] [Bug 1083310] Re: cups returns malformed UTF-8

2018-08-19 Thread Роман Донченко
Sorry, but I no longer have that printer, or that machine. So I cannot
help you any further.

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

Title:
  cups returns malformed UTF-8

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is Ubuntu 12.04, libcups2 1.5.3-0ubuntu4.

  I noticed gedit and evince were crashing whenever I opened the print
  dialog. I'm attaching an example stack trace from gedit.

  Eventually I traced the bug to CUPS. gedit crashes in GTK+ code when
  trying to process an invalid UTF-8 string starting with "Параметры,
  разрешенн". That string comes from my PPD file (will attach), and its
  byte length coincides with the size of ppd_group_t::text in CUPS,
  which means that it's being improperly truncated within CUPS.

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

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


[Touch-packages] [Bug 1787867] [NEW] Ubuntu 18.04 LTS bluetooth left discoverable

2018-08-19 Thread jowfdoijdfdwfwdf
Public bug reported:

Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable
which opens up unnecessary vulnerability surface. There should be a
separate UI switch for discoverability with auto timeout. Leaving
bluetooth on (using a Bluetooth mouse) should not leave the computer
always discoverable.

Current behavior does not match documentation
https://help.ubuntu.com/stable/ubuntu-help/bluetooth-visibility.html.en,
even without Bluetooth panel open, the computer is still discoverable.

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

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

Title:
  Ubuntu 18.04 LTS bluetooth left discoverable

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays
  discoverable which opens up unnecessary vulnerability surface. There
  should be a separate UI switch for discoverability with auto timeout.
  Leaving bluetooth on (using a Bluetooth mouse) should not leave the
  computer always discoverable.

  Current behavior does not match documentation
  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-
  visibility.html.en, even without Bluetooth panel open, the computer is
  still discoverable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions

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


[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-08-19 Thread August Pamplona
Nope, getting rid of '/lib/udev/rules.d/71-nvidia.rules' does nothing.

It's a Mint 19 (Tara) with Cinnamon installation that I sometimes use on
a Dell E6400 which used to work well with it before with earlier
kernels.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1526010] Re: Duplex not working

2018-08-19 Thread gf
Thanks for the update, Francois. I will close the report now.
Have a great day!
:)
G

Closed per reporter’s feedback.

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

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

Title:
  Duplex not working

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I just upgraded to cups:amd64 1.7.2-0ubuntu1.6 1.7.2-0ubuntu1.6

  Since then, duplex stopped working. It use to work flawlessly.

  My setup:
  - Brother HL-3170CDW
  - local network.
  - ipp protocol

  What I tried:
  - Factory reset on the printer
  - JetDirect, IPP, LDP, etc...
  - Default option on duplex
  - Changing options on duples.

  Nothing worked. Also note: on each of these setups, duplex was working
  find from a Windows VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 14 13:05:28 2015
  InstallationDate: Installed on 2014-04-18 (604 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for FTPrint-04_Laser: 
dnssd://Brother%20HL-3170CDW%20series%20%5B30055c4e13e1%5D%20(2)._ipp._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: FTPrint-04_Laser: Brother HL-3170CDW series CUPS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-39-generic 
root=UUID=d423eb51-548f-4e17-b402-46a6ecc057f5 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/ubuntu/+source/cups/+bug/1526010/+subscriptions

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


[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

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

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

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

Title:
  AppArmor treats regular NFS file access as network op

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 
audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 
audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2788 comm="man" 

[Touch-packages] [Bug 1787853] [NEW] SystemD's default TimeoutStart and TimeoutStop are too long for Desktop

2018-08-19 Thread Damiön la Bagh
Public bug reported:


On Ubuntu 18.04LTS starting and stopping the computer is extremely slow.

SystemD defaults to a start time timeout of 90seconds and a stop time timeout 
of 90seconds
in the file

/etc/systemd/system.conf

This is great for huge databased raid systems in some cloud datacenter
but is very inappropriate for desktop computing where there is a human
waiting for the process.

Ubuntu Desktops need to have the 
/etc/systemd/system.conf

Set to timeout in less than <10 seconds (the magic computer irritation
moment for humans) out of the box, default

for example:
DefaultTimeoutStartSec=9s
DefaultTimeoutStopSec=9s

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 23:12:49 2018
InstallationDate: Installed on 2015-11-15 (1008 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago)
dmi.bios.date: 08/15/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: X99 Extreme11
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.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11: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.
mtime.conffile..etc.systemd.system.conf: 2018-08-19T23:11:55.785333

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


** Tags: amd64 apport-bug bionic

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

Title:
  SystemD's default TimeoutStart and TimeoutStop are too long for
  Desktop

Status in systemd package in Ubuntu:
  New

Bug description:
  
  On Ubuntu 18.04LTS starting and stopping the computer is extremely slow.

  SystemD defaults to a start time timeout of 90seconds and a stop time timeout 
of 90seconds
  in the file

  /etc/systemd/system.conf

  This is great for huge databased raid systems in some cloud datacenter
  but is very inappropriate for desktop computing where there is a human
  waiting for the process.

  Ubuntu Desktops need to have the 
  /etc/systemd/system.conf

  Set to timeout in less than <10 seconds (the magic computer irritation
  moment for humans) out of the box, default

  for example:
  DefaultTimeoutStartSec=9s
  DefaultTimeoutStopSec=9s

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 23:12:49 2018
  InstallationDate: Installed on 2015-11-15 (1008 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago)
  dmi.bios.date: 08/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X99 Extreme11
  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.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11: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.
  mtime.conffile..etc.systemd.system.conf: 2018-08-19T23:11:55.785333

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

-- 
Mailing list: 

[Touch-packages] [Bug 1787843] [NEW] tengo un problema de arranque de equipo, despues de instalar la ultima version de ubuntu

2018-08-19 Thread juan angel Mora
Public bug reported:

Instale la nueva version de Ubuntu, pero al reiniciarse se me quedaba 
ploqueado, lo intente a traves del BIOS pidiendole que me reparase lo que podia 
haber mal y en apariencias fue bien (eso fue ayer), hoy lo vuelvo a encender y 
me vuelve a pasar lo mismo le pido que me identifique el problema y me dice que 
es un problema al instalar el software y que esta en el paquete : systemd-shim 
9-1bzr4ubuntu1 y hasta ahi se, me podrian ayudar?
Agracias

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Fri Aug 17 02:50:45 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2015-09-11 (1073 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  tengo un problema de arranque de equipo, despues de instalar la ultima
  version de ubuntu

Status in systemd package in Ubuntu:
  New

Bug description:
  Instale la nueva version de Ubuntu, pero al reiniciarse se me quedaba 
ploqueado, lo intente a traves del BIOS pidiendole que me reparase lo que podia 
haber mal y en apariencias fue bien (eso fue ayer), hoy lo vuelvo a encender y 
me vuelve a pasar lo mismo le pido que me identifique el problema y me dice que 
es un problema al instalar el software y que esta en el paquete : systemd-shim 
9-1bzr4ubuntu1 y hasta ahi se, me podrian ayudar?
  Agracias

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Fri Aug 17 02:50:45 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2015-09-11 (1073 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1787837] [NEW] No sound in Ubuntu 16.04

2018-08-19 Thread Arjun Gupta
Public bug reported:

The sound settings keep showing Dummy output as a device for a sound
output. After restarting the laptop all the output devices are shown but
even then there is no sound.

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

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

Title:
  No sound in Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound settings keep showing Dummy output as a device for a sound
  output. After restarting the laptop all the output devices are shown
  but even then there is no sound.

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

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


[Touch-packages] [Bug 1787835] Re: package linux-image-extra-4.4.0-133-generic 4.4.0-133.159 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-08-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-133-generic 4.4.0-133.159 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:
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  Just logged in and got one of those "System Error Report" popups. I
  ran auto-remove after I got this error message because I got another
  warning that /boot was running out of space.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-133-generic 4.4.0-133.159
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rad2274 F pulseaudio
   /dev/snd/controlC0:  rad2274 F pulseaudio
  Date: Sat Aug 18 16:27:13 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (777 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 005: ID 03eb:8a1d Atmel Corp.
   Bus 001 Device 003: ID 5986:055e Acer, Inc
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80K9
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-133-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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 2.02~beta2-36ubuntu3.18
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-133-generic 4.4.0-133.159 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: A9CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.name: 80K9
  dmi.product.version: Lenovo Edge 15
  dmi.sys.vendor: LENOVO

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

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


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

2018-08-19 Thread rDumas
Public bug reported:

Description:Ubuntu 16.04.5 LTS
Release:16.04

Just logged in and got one of those "System Error Report" popups. I ran
auto-remove after I got this error message because I got another warning
that /boot was running out of space.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-133-generic 4.4.0-133.159
ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
Uname: Linux 4.4.0-133-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rad2274 F pulseaudio
 /dev/snd/controlC0:  rad2274 F pulseaudio
Date: Sat Aug 18 16:27:13 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
InstallationDate: Installed on 2016-07-02 (777 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 005: ID 03eb:8a1d Atmel Corp.
 Bus 001 Device 003: ID 5986:055e Acer, Inc
 Bus 001 Device 002: ID 8087:8001 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80K9
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-133-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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 2.02~beta2-36ubuntu3.18
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-133-generic 4.4.0-133.159 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: Lenovo
dmi.bios.version: A9CN61WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Edge 15
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Edge 15
dmi.modalias: 
dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
dmi.product.name: 80K9
dmi.product.version: Lenovo Edge 15
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package xenial

** Description changed:

  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  
  Just logged in and got one of those "System Error Report" popups. I ran
- auto-remove yesterday because I got another warning that /boot was
- running out of space.
+ auto-remove after I got this error message because I got another warning
+ that /boot was running out of space.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-133-generic 4.4.0-133.159
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  rad2274 F pulseaudio
-  /dev/snd/controlC0:  rad2274 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  rad2274 F pulseaudio
+  /dev/snd/controlC0:  rad2274 F pulseaudio
  Date: Sat Aug 18 16:27:13 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c
  InstallationDate: Installed on 2016-07-02 (777 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
-  Bus 001 Device 005: ID 03eb:8a1d Atmel Corp. 
-  Bus 001 Device 003: ID 5986:055e Acer, Inc 
-  Bus 001 Device 002: ID 8087:8001 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 005: ID 03eb:8a1d Atmel Corp.
+  Bus 001 Device 003: ID 5986:055e Acer, Inc
+  Bus 001 Device 002: ID 8087:8001 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80K9
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-133-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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 2.02~beta2-36ubuntu3.18
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-133-generic 4.4.0-133.159 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  

[Touch-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set

2018-08-19 Thread linex83
Following-up on my previous comment, the problem did come back, even
though it was gone at first after I switched to ibus and then back to
xim. Now I switched to ibus and restarted, the problem is gone. So I'm
not switching back to xim, as I suspect the problem would reappear again
then.

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue when
  GTK_IM_MODULE=xim is set

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

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

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


[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

2018-08-19 Thread Bug Watch Updater
** Changed in: appstream (Debian)
   Status: Unknown => Fix Released

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  New
Status in appstream package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Fix Released

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.

2018-08-19 Thread Erkan ÜNLÜTÜRK
** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1787824/+attachment/5177558/+files/asad

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

Title:
  "rfkill: input handler disabled" boot time 11 seconds.

Status in util-linux package in Ubuntu:
  New

Bug description:
  My computer is slowly opening, I looked at the output of dmesg and at 11th I 
get this post.
  What i need to do? thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rfkill 2.31.1-0.4ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 19:44:21 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libsmartcols1 2.31.1-0.4ubuntu3.1
  InstallationDate: Installed on 2018-08-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1787824] [NEW] "rfkill: input handler disabled" boot time 11 seconds.

2018-08-19 Thread Erkan ÜNLÜTÜRK
Public bug reported:

My computer is slowly opening, I looked at the output of dmesg and at 11th I 
get this post.
What i need to do? thanks.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rfkill 2.31.1-0.4ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 19:44:21 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
 libsmartcols1 2.31.1-0.4ubuntu3.1
InstallationDate: Installed on 2018-08-18 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  "rfkill: input handler disabled" boot time 11 seconds.

Status in util-linux package in Ubuntu:
  New

Bug description:
  My computer is slowly opening, I looked at the output of dmesg and at 11th I 
get this post.
  What i need to do? thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rfkill 2.31.1-0.4ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 19:44:21 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libsmartcols1 2.31.1-0.4ubuntu3.1
  InstallationDate: Installed on 2018-08-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

2018-08-19 Thread Matthias Klumpp
** Changed in: appstream (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: appstream (Ubuntu)
 Assignee: (unassigned) => Matthias Klumpp (ximion)

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  New
Status in appstream package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Unknown

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

2018-08-19 Thread Matthias Klumpp
This is fixed in Debian now, in package appstream/0.12.2-2.


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

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

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  New
Status in appstream package in Ubuntu:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Unknown

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

2018-08-19 Thread Hans Joachim Desserud
** Tags added: bionic

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions

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


[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

2018-08-19 Thread Bug Watch Updater
** Changed in: appstream
   Status: Unknown => New

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  New
Status in appstream package in Ubuntu:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

2018-08-19 Thread Darafei Praliaskouski
The same thing reproduces on new install of Kubuntu Bionic. Install
locale is be_BY.UTF-8, in case it matters.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions

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


[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

2018-08-19 Thread Matthias Klumpp
See the linked upstream issue for details - this will be fixed soon.

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

** Bug watch added: github.com/ximion/appstream/issues #198
   https://github.com/ximion/appstream/issues/198

** Also affects: appstream via
   https://github.com/ximion/appstream/issues/198
   Importance: Unknown
   Status: Unknown

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  Unknown
Status in appstream package in Ubuntu:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1512012] Re: Kyocera Mita FS-1900 prints garbage

2018-08-19 Thread gf
Sorry Joachim. I only have the two options to close the ticket: fix released or 
invalid.
No offense meant.
Take care
:)
G

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

Title:
  Kyocera Mita FS-1900 prints garbage

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Using the PPD from
  http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8
  .-downloadcenteritem-Single-
  
License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter
  (the German one, not sure if that could make a difference).

  Followed the instructions on
  https://wiki.ubuntu.com/DebuggingPrintingProblems.

  Steps in "USB Printer" gave the following results:

  2. lsmod | grep usb would give several modules (is usblp the right one? the 
page doesn't tell)
  3. tailing the syslog would show me USB activity during plug and unplug.
  6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp.
  8. Device id seems legit, usb_printerid /dev/usb/lp0 says 
ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript 
Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP 
Laserjet 4050 Series;
  10. lpinfo -v has this to say about the printer: direct 
usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers 
listed are "direct hp" and "direct hpfax", could be a modem jack I never cared 
about, could be something emulated, no idea)

  Printing the test page gives me two sheets of paper, the first mostly
  empty except for three lines each starting(?) with a single full stop
  character, and a second with these lines (note the initial blank on
  most line starts, could actually be multiple blanks):

   ERROR
   rangecheck
   OFFENDING COMMAND:
   filter
   STACK:
  .
   563135
   --nostringval--
   --nostringval--
   5

  The printer seems to be emitting a line with a full stop every 20
  lines or so, the full stop in the message above is somehow connected
  to that.

  
  From the DebuggingPrintingProblems page, I tried both usb-unidir-default and 
usb-no-reattach-default, with no discernible difference.

  
  (Things were slightly complicated by the docking station being entirely 
unresponsibe on three of six USB ports. I don't know whether the ports of the 
drivers are at fault here, but I guess that's unrelated to CUPS.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CupsErrorLog:
   E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden.
   E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden.
  CurrentDesktop: XFCE
  Date: Sat Oct 31 21:45:05 2015
  InstallationDate: Installed on 2015-08-24 (68 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Lpstat:
   device for Farblaser: 
dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/
   device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070
  MachineType: Dell Inc. Precision M4600
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', 
'/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Farblaser.ppd: Permission denied
   grep: /etc/cups/ppd/FS-1900.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  SourcePackage: cups
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 08V9YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1787803] [NEW] [G752VY, Realtek ALC668, Black Line Out, Right] Background whir or pipes

2018-08-19 Thread Wenzel
Public bug reported:

Problem: There is humming and high-frequency whistling over the entire
volume of the line-out headphones and speakers. This problem does not
exist under the WIN10 only under Ubuntu 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  frank  1851 F pulseaudio
 /dev/snd/controlC0:  frank  1851 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 11:58:46 2018
InstallationDate: Installed on 2018-05-13 (98 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Eingebautes Tongerät - HDA Intel PCH
Symptom_Jack: Black Line Out, Right
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: High background noise, or volume is too low
Title: [G752VY, Realtek ALC668, Black Line Out, Right] Background noise or low 
volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VY.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [G752VY, Realtek ALC668, Black Line Out, Right] Background whir or
  pipes

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Problem: There is humming and high-frequency whistling over the entire
  volume of the line-out headphones and speakers. This problem does not
  exist under the WIN10 only under Ubuntu 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  frank  1851 F pulseaudio
   /dev/snd/controlC0:  frank  1851 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 11:58:46 2018
  InstallationDate: Installed on 2018-05-13 (98 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Eingebautes Tongerät - HDA Intel PCH
  Symptom_Jack: Black Line Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [G752VY, Realtek ALC668, Black Line Out, Right] Background noise or 
low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VY.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VY
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1787799] [NEW] package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

2018-08-19 Thread Hrushikesh Edara
Public bug reported:

Attempted to install idle3 when this error occured

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bsdutils 1:2.31.1-0.4ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat Aug 18 20:45:10 2018
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package bsdutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package bsdutils is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2018-07-21 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: util-linux
Title: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade:
  package bsdutils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  Attempted to install idle3 when this error occured

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bsdutils 1:2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 18 20:45:10 2018
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-07-21 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: 
package bsdutils is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1787795] [NEW] PCI/internal sound card not detected

2018-08-19 Thread DEEPAK MAURYA
Public bug reported:

no sound coming either in speaker nor in headphones

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 18:30:01 2018
InstallationDate: Installed on 2018-08-04 (15 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
dmi.bios.date: 09/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X542UQR.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X542UQR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQR.300:bd09/19/2017:svnASUSTeKCOMPUTERINC.:pnX542UQR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X542UQR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-19T18:10:14.264377

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


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

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  no sound coming either in speaker nor in headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 18:30:01 2018
  InstallationDate: Installed on 2018-08-04 (15 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQR.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQR.300:bd09/19/2017:svnASUSTeKCOMPUTERINC.:pnX542UQR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X542UQR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-19T18:10:14.264377

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

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


[Touch-packages] [Bug 1512012] Re: Kyocera Mita FS-1900 prints garbage

2018-08-19 Thread Joachim Durchholz
Hmf. "Invalid" adds insult to injury.

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

Title:
  Kyocera Mita FS-1900 prints garbage

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Using the PPD from
  http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8
  .-downloadcenteritem-Single-
  
License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter
  (the German one, not sure if that could make a difference).

  Followed the instructions on
  https://wiki.ubuntu.com/DebuggingPrintingProblems.

  Steps in "USB Printer" gave the following results:

  2. lsmod | grep usb would give several modules (is usblp the right one? the 
page doesn't tell)
  3. tailing the syslog would show me USB activity during plug and unplug.
  6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp.
  8. Device id seems legit, usb_printerid /dev/usb/lp0 says 
ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript 
Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP 
Laserjet 4050 Series;
  10. lpinfo -v has this to say about the printer: direct 
usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers 
listed are "direct hp" and "direct hpfax", could be a modem jack I never cared 
about, could be something emulated, no idea)

  Printing the test page gives me two sheets of paper, the first mostly
  empty except for three lines each starting(?) with a single full stop
  character, and a second with these lines (note the initial blank on
  most line starts, could actually be multiple blanks):

   ERROR
   rangecheck
   OFFENDING COMMAND:
   filter
   STACK:
  .
   563135
   --nostringval--
   --nostringval--
   5

  The printer seems to be emitting a line with a full stop every 20
  lines or so, the full stop in the message above is somehow connected
  to that.

  
  From the DebuggingPrintingProblems page, I tried both usb-unidir-default and 
usb-no-reattach-default, with no discernible difference.

  
  (Things were slightly complicated by the docking station being entirely 
unresponsibe on three of six USB ports. I don't know whether the ports of the 
drivers are at fault here, but I guess that's unrelated to CUPS.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CupsErrorLog:
   E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden.
   E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden.
  CurrentDesktop: XFCE
  Date: Sat Oct 31 21:45:05 2015
  InstallationDate: Installed on 2015-08-24 (68 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Lpstat:
   device for Farblaser: 
dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/
   device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070
  MachineType: Dell Inc. Precision M4600
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', 
'/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Farblaser.ppd: Permission denied
   grep: /etc/cups/ppd/FS-1900.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  SourcePackage: cups
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 08V9YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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