[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

2018-08-27 Thread Matthias Klose
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Fix Committed

Bug description:
  SRU for bionic:

  Acceptance criteria: An encrypted partition can be decrypted using
  cryptroot-unlock.

  Regression potential: It's not the default method, so unused by the
  majority of people. Besides that the patched script runs fine in
  cosmic.

  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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


[Touch-packages] [Bug 987212] Re: Wireless printer "Processing - Unable to locate printer."

2018-08-27 Thread emni petro
I have an HP printer laserjet pro M1136. It's a multifunctional printer its 
printer quality is too good.
but when I trying to print through a printer its hang the printer and unable to 
print the page. so I contact hp support team and they resolve my issue 
immediately. I just share my experience with it...
so if you also face an issue with this type you can also connect them.
so visit that site 
https://www.hptechnicalsupportphonenumbersusa.com/hp-customer-support/   
if any issue face..they provide the best service to their customer.

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

Title:
  Wireless printer "Processing - Unable to locate printer."

Status in avahi package in Ubuntu:
  Confirmed
Status in avahi source package in Precise:
  Confirmed
Status in avahi source package in Quantal:
  Won't Fix
Status in avahi source package in Raring:
  Won't Fix

Bug description:
  Description: Ubuntu 12.04 LTS (Precise Pangolin) Beta 2
  Release: 12.04 Beta 2

  The printer is a Lexmark X734de  printer connected over a wireless
  network that can be found, but will not print. The print job stays in
  the queue forever. Wireless Printer "Processing - Unable to locate
  printer."

  Network/Local Printers found but cannot print - Unable to get printer
  status and says it's "Processing".

  I'm shure we want avoid this for the Ubuntu 12.04 LTS (Precise
  Pangolin) release, when the final has been released. I'm using Ubuntu
  12.04 LTS (Precise Pangolin) Beta 2 with latest update as of today.

  CUPS log: /var/log/cups/error_log

  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' 
already exists
  W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: 
org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' 
already exists
  E [23/Apr/2012:11:50:58 +0200] [Job 2] Unable to find printer.
  E [23/Apr/2012:11:51:13 +0200] [Job 2] Unable to find printer.
  E [23/Apr/2012:11:51:28 +0200] [Job 2] Unable to find printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: system-config-printer-gnome 1.3.8+20120201-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  CheckboxSubmission: e28f23d40ba6960d2759044b1acbd380
  CheckboxSystem: c69722ecac764861be52925fa50b4dcc
  Date: Mon Apr 23 11:58:03 2012
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  InterpreterPath: /usr/bin/python2.7
  Lpstat:
   device for Canon-MP190-series: 
usb://Canon/MP190%20series?serial=E14D77&interface=1
   device for Lexmark-X734de: 
dnssd://Lexmark%20X734de._pdl-datastream._tcp.local/
  MachineType: Acer AOA150
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   Lexmark-X734de: Lexmark X734de
   Canon-MP190-series: Canon PIXMA MP190 - CUPS+Gutenprint v5.2.8-pre1
  ProcEnviron:
   LANGUAGE=se_NO:nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en
   LANG=se_NO
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae 
root=UUID=6448F9C148F991D2 loop=/hostname/disks/root.disk ro quiet splash 
vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3305
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3305:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:c

[Touch-packages] [Bug 1641779] Re: printer cropping the top off on prints

2018-08-27 Thread BronsonMathews
I dont think I can close this. Please close this for me :)
Thanks!

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

Title:
  printer cropping the top off on prints

Status in cups package in Ubuntu:
  Invalid

Bug description:
  using a hp photosmart 5520 over the wireless. Im fairly positive this worked 
fine on 15.10.
  But on 16.04 when printing the top of the page is always cropped off.

  Ive tried all the things on the following page:
  
http://askubuntu.com/questions/112684/why-does-ubuntu-add-a-5-margin-to-the-top-when-printing-to-my-hp-psc-750

  however no luck at all with any of these.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
   W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
   W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
   W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
  CurrentDesktop: Unity
  Date: Tue Nov 15 11:33:32 2016
  InstallationDate: Installed on 2016-08-15 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for HP-Photosmart-5520-series: 
dnssd://Photosmart%205520%20series%20%5BDF47AD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-fc15b4df47ad
  MachineType: TOSHIBA Satellite L850
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Photosmart-5520-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-Photosmart-5520-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=4657cafb-40f4-447f-b155-5e2db880d622 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  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.:bvr1.40:bd04/24/2012:svnTOSHIBA:pnSatelliteL850:pvrPSKDLA-0CC00R:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L850
  dmi.product.version: PSKDLA-0CC00R
  dmi.sys.vendor: TOSHIBA

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

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


[Touch-packages] [Bug 1641779] Re: printer cropping the top off on prints

2018-08-27 Thread BronsonMathews
I havent used ubuntu for a while now. So I cannot test this. So ill
close the issue as I cannot test it.

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

Title:
  printer cropping the top off on prints

Status in cups package in Ubuntu:
  Invalid

Bug description:
  using a hp photosmart 5520 over the wireless. Im fairly positive this worked 
fine on 15.10.
  But on 16.04 when printing the top of the page is always cropped off.

  Ive tried all the things on the following page:
  
http://askubuntu.com/questions/112684/why-does-ubuntu-add-a-5-margin-to-the-top-when-printing-to-my-hp-psc-750

  however no luck at all with any of these.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
   W [15/Nov/2016:11:28:01 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
   W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-Gray..\' already exists
   W [15/Nov/2016:11:30:34 +1030] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'HP-Photosmart-5520-series-RGB..\' already exists
  CurrentDesktop: Unity
  Date: Tue Nov 15 11:33:32 2016
  InstallationDate: Installed on 2016-08-15 (92 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for HP-Photosmart-5520-series: 
dnssd://Photosmart%205520%20series%20%5BDF47AD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-fc15b4df47ad
  MachineType: TOSHIBA Satellite L850
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Photosmart-5520-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-Photosmart-5520-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=4657cafb-40f4-447f-b155-5e2db880d622 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  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.:bvr1.40:bd04/24/2012:svnTOSHIBA:pnSatelliteL850:pvrPSKDLA-0CC00R:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L850
  dmi.product.version: PSKDLA-0CC00R
  dmi.sys.vendor: TOSHIBA

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

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


[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-08-27 Thread lepidas blades rompolos
This bug is still affecting me, downloaded yesterday iso images from
ubuntu,kubuntu,xubuntu and can't boot from pxe server saying that iam in
emergency mode.

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

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

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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


[Touch-packages] [Bug 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS

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

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

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

Title:
  LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and
  STARTTLS

Status in openldap package in Ubuntu:
  Expired

Bug description:
  Tested with vivid and wily...
  also logged with openldap as 
http://www.openldap.org/its/index.cgi/Incoming?id=8374

  
  The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different
  between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs.

  When accessing server with a self-signed certificate, the results are:

  
  ldaps://

  neverOK
  hard Error: can't contact LDAP server
  demand   Error: can't contact LDAP server
  allowOK
  try  Error: can't contact LDAP server

  
  ldap:// plus explicit ldap_start_tls_s()

  neverOK
  hard OK
  demand   OK
  allowOK
  try  OK

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

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


[Touch-packages] [Bug 592550] Re: setxkbmap fills in /var/lib/xkb

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: x11-xkb-utils (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  setxkbmap fills in /var/lib/xkb

Status in x11-xkb-utils package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: x11-xkb-utils

  using setxkbmap with different mappings silently fills in /var/lib/xkb
  with xkm files

  when are these files purged !! ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/592550/+subscriptions

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


[Touch-packages] [Bug 710144] Re: Xsession: unable to launch "" X session --- "" not found; falling back to default session.

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Xsession: unable to launch "" X session --- "" not found; falling back
  to default session.

Status in xorg package in Ubuntu:
  Won't Fix
Status in xorg package in Debian:
  New

Bug description:
  Binary package hint: xorg

  I recently both got an upgrade for Xorg and went to KDE 4.6 (via the
  PPA), so I don't know who caused this message to appear. But now
  everytime I logon I get an xmessage telling me "Xsession: unable to
  launch "" X session --- "" not found; falling back to default
  session."

  This is from /etc/X11/Xsession.d/20x11-common_process-args but I don't
  know where the session name comes from. Anyway, I think an empty
  session name should be special cased with something like the following
  (untested) patch:

  --- 20x11-common_process-args.orig  2010-03-02 17:33:01.0 +0100
  +++ 20x11-common_process-args   2011-01-30 13:57:18.073443001 +0100
  @@ -40,7 +40,7 @@
 fi
   fi
   ;;
  -  default)
  +  default|"")
   # Default behavior was requested.
   ;;
 *)

  Apart from that it would be nice if that message gave me a hint on how
  to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: x11-common 1:7.5+6ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic x86_64
  Architecture: amd64
  DRM.card0.HDMI_Type_A.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 
1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 
800x600 720x576 720x480 640x480 640x480 640x480 640x480 720x400
   edid-base64: 
AP///wAmzQxWuAkAACYUAQOANB14KmBBplZKnCUSUFS/7wBxT4FAgYCVAJUPswABAQEBAjqAGHE4LUBYLEUACSUhAAAe/QA4TB5TEQAKICAgICAg/ABQTDI0MDlIRAogICAg/wAxMTAwNU0wOTAyNDg4AaQCAx/xTAECAwQFEBESExQeHyMJBwGDAQAAZQMMABAAjArQiiDgLRAQPpYACSUhAAAYAR0AclHQHiBuKFUACSUhAAAejArQkCBAMSAMQFUACSUhAAAYTw==
  Date: Sun Jan 30 13:50:23 2011
  DkmsStatus:
   
  MachineType: Acer AL 5100 / VL410
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-25-generic root=/dev/mapper/lvm-sys 
ro rootfstype=ext4 iommu=noaperture quiet splash
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 04/14/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R02-A1
  dmi.board.name: FRS690L
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR02-A1:bd04/14/2008:svnAcer:pnAL5100/VL410:pvrR02-A1:rvnAcer:rnFRS690L:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: AL 5100 / VL410
  dmi.product.version: R02-A1
  dmi.sys.vendor: Acer
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-25-generic

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

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


[Touch-packages] [Bug 1227612] Re: Scren freezes with amd 13.9 driver

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Scren freezes with amd 13.9 driver

Status in fglrx:
  New
Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Screen freezed, xorg process zombied

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Sep 19 21:17:41 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz 
Edition] [1002:6818] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e217]
  InstallationDate: Installed on 2013-05-14 (128 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  JockeyStatus:
   kmod:fglrx - ATI Fire GL (Проприетарные, Активирован, Используется)
   kmod:fglrx_updates - Video driver for the AMD graphics accelerators 
(Проприетарные, Выключен, Не используется)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=7c70a218-5c1f-4cd0-96db-dd25b7da7106 ro rootfstype=ext4 drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5304
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55-M LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5304:bd11/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep 19 21:05:30 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   OutputCRT1DFP1   
DFP10DFP2DFP3DFP4DFP5   
 DFP6DFP7DFP8DFP9 
   product id   
26442 
   vendor 
NEC
  xserver.version: 2:1.13.3-0ubuntu6.1
  xserver.video_driver: fglrx

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

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


[Touch-packages] [Bug 1250635] Re: system crashes on launching Mathematica 9.0.1, return to login window

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  system crashes on launching Mathematica 9.0.1, return to login window

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  After I updated my system (13.10) this morning, I cannot launch
  Mathematica. Everytime I try to launch it, the screen becomes black
  then go back to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: compiz-core 1:0.9.10+13.10.20131011-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.88  Wed Mar 27 14:26:46 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.1
  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
  CurrentDmesg:
   
  Date: Tue Nov 12 14:23:24 2013
  DistUpgraded: 2013-10-18 11:49:20,327 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.88, 3.11.0-12-generic, x86_64: installed
   nvidia-304, 304.88, 3.11.0-13-generic, x86_64: installed
   nvidia-304, 304.88, 3.8.0-31-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:3518]
  InstallationDate: Installed on 2012-10-28 (379 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Gigabyte Technology Co., Ltd. Z68A-D3H-B3
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=c9a4d91b-71b2-4040-9ac5-e455a0d33e0f ro recovery nomodeset
  SourcePackage: compiz
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (25 days ago)
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: Z68A-D3H-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68A-D3H-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68A-D3H-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68A-D3H-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Tue Nov 12 14:11:42 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.3-3ubuntu2

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

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


[Touch-packages] [Bug 1374618] Re: [present + prime] HDMI output (nouveau) broken

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [present + prime] HDMI output (nouveau) broken

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  I recently upgraded my system to Ubuntu 14.10.
  Now when testing HDMI, I hit some bug.

  My system is an optimus laptop.
  The HDMI is connected to a nvidia card.

  Now the HDMI has signal, and while logging in (so when Xorg is
  starting) I can shortly move my cursor over the external display. But
  when login is complete, the external display is 1 artifact, and
  doesn't show any updates anymore.

  So I started bisecting the version from 14.10 to 14.04 (where it was
  working).

  And I found out the following commit caused the issue:
  commit 975b9798be77b30cbed485583d0ccb48318708f7
  Author: Chris Wilson 
  Date:   Wed May 21 08:58:24 2014 +0100

  sna: Add support for Present
  
  Signed-off-by: Chris Wilson 

  
  Now I recompiled the intel driver without the commit, and that fixes the 
issue.
  Another option is to use --disabled-dri3.

  My hardware
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 
540M] (rev a1)

  The driver I use for the nvidia card is nouveau.

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

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


[Touch-packages] [Bug 1385810] Re: Chromium causes drm/i915 stuck on render ring

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Chromium causes drm/i915 stuck on render ring

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Reproducible example: visit http://ello.co/jondcook in Chromium and
  the GPU will crash

  Linux 4720z 3.13.0-38-generic #65~precise1-Ubuntu SMP Thu Oct 9 19:24:05 UTC 
2014 i686 i686 i386 GNU/Linux
  NAME="Ubuntu"
  VERSION="12.04.5 LTS, Precise Pangolin"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu precise (12.04.5 LTS)"
  VERSION_ID="12.04"
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS"

  Chromium Version 37.0.2062.120 Ubuntu 12.04 (281580)

  Oct 26 00:43:08 4720z kernel: [242523.988084] [drm] stuck on render ring
  Oct 26 00:43:08 4720z kernel: [242523.988096] [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Oct 26 00:43:08 4720z kernel: [242523.988101] [drm] GPU hangs can indicate a 
bug anywhere in the entire gfx stack, including userspace.
  Oct 26 00:43:08 4720z kernel: [242523.988106] [drm] Please file a _new_ bug 
report on bugs.freedesktop.org against DRI -> DRM/Intel
  Oct 26 00:43:08 4720z kernel: [242523.988110] [drm] drm/i915 developers can 
then reassign to the right component if it's not a kernel issue.
  Oct 26 00:43:08 4720z kernel: [242523.988115] [drm] The gpu crash dump is 
required to analyze gpu hangs, so please always attach it.
  Oct 26 00:43:08 4720z kernel: [242523.989889] [drm:i915_set_reset_status] 
*ERROR* render ring hung inside bo (0xd32a000 ctx 0) at 0xd32aadc
  Oct 26 00:43:08 4720z kernel: [242524.496024] [drm:i915_reset] *ERROR* Failed 
to reset chip.
  Oct 26 00:43:18 4720z kernel: [242533.988090] [drm:i915_gem_wait_for_error] 
*ERROR* Timed out waiting for the gpu reset to complete
  Oct 26 00:43:18 4720z kernel: [242533.988107] [drm:i915_gem_wait_for_error] 
*ERROR* Timed out waiting for the gpu reset to complete
  Oct 26 00:43:18 4720z kernel: [242534.148091] [drm:i915_gem_wait_for_error] 
*ERROR* Timed out waiting for the gpu reset to complete
  Oct 26 00:43:18 4720z kernel: [242534.204095] [drm] GMBUS [i915 gmbus vga] 
timed out, falling back to bit banging on pin 2

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

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


[Touch-packages] [Bug 1286313] Re: Garbled Text

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Garbled Text

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Please see the attached screenshot. There is a glitch in the small
  window. Happens everywhere - Firfox etc. It is indeed very hard to
  read sometimes with this issue. It goes away however with selection
  using mouse or clickng on it.

  WORKAROUND: Install fglrx.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2.2
  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 Feb 28 14:09:21 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz 
Edition] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:2304]
  InstallationDate: Installed on 2014-01-08 (50 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS 8500
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=00190dd5-dc02-4fe9-92ff-0581caddd1fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0YJPT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd09/05/2012:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Fri Feb 28 12:55:54 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL DELL USB Laser Mouse MOUSE, id 8
   inputDELL Dell USB Wired Multimedia Keyboard KEYBOARD, id 9
   inputDELL Dell USB Wired Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2~saucy1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1447919] Re: Intel DRM GPU hang in Kubuntu 15.04

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Intel DRM GPU hang in Kubuntu 15.04

Status in xf86-video-intel:
  Invalid
Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Intel driver hangs every time KDE uses one of the special system
  effects. I can reliably reproduce it by pressing "Alt-Tab", for
  example. The only fix is to reboot the computer.

  Kernel version:
  $ uname -a
  Linux darkstar 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  
  -- Logcat output --

  [   47.675521] [drm] stuck on render ring
  [   47.676178] [drm] GPU HANG: ecode 7:0:0x, in kwin_x11 [1519], 
reason: Ring hung, action: reset
  [   47.676180] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [   47.676180] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [   47.676181] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [   47.676182] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [   47.676183] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [   47.683468] drm/i915: Resetting chip after gpu hang

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 23 23:40:38 2015
  InstallationDate: Installed on 2013-10-13 (557 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago)

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

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


[Touch-packages] [Bug 1511473] Re: nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x002140 [ !ENGINE ]

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at
  0x002140 [ !ENGINE ]

Status in Nouveau Xorg driver:
  Confirmed
Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  dmesg:
  [  163.227218] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Oct 29 02:22:19 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c650]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c650]
  LiveMediaBuild: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Q470C/500P4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P02RAB
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP500P4C-S02CL
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP02RAB:bd08/29/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnQ470C/500P4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP500P4C-S02CL:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: Q470C/500P4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Oct 29 02:14:13 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13897 
   vendor SEC
  xserver.version: 2:1.17.1-0ubuntu3

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

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


[Touch-packages] [Bug 1517952] Re: Ubuntu 15.10 Hangs totally once a day

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Ubuntu 15.10 Hangs totally once a day

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  I'm using a Cincoze -dc1100
  http://www.cincoze.com/products_detail.php?bgid=27&sgid=28&gid=107
  Atom- e3845 based

  To control a 4 axis robot with a qt5 (GL based) gui.

  Sometimes (say once a day) it hangs completely without any interesting
  trace in syslog or xorglog.

  The same things happened in 14.04 using SNA or UXA acceleration for
  the intel GPU.

  IT resembles to me https://bugs.freedesktop.org/show_bug.cgi?id=88012.

  peppedx

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

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


[Touch-packages] [Bug 1537308] Re: [HP Pavilion Notebook - 15-ab153nr (ENERGY STAR)] System sends Control, Alt and Shift events without input.

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [HP Pavilion Notebook - 15-ab153nr (ENERGY STAR)] System sends
  Control, Alt and Shift events without input.

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  I noticed strange behavior from my Ubuntu system.  While left idle,
  the screensaver would shut off with no interaction with the machine.
  While using the machine, webpages would zoom in or out when trying to
  scroll, and command windows would open while typing.

  Using xev, I found that these events corresponded with ALt_L,
  Control_L and Shift_R events, even though those buttons were not being
  pressed.  I'm attaching a xev log, searching for _L will show the
  events.  ((Shift_R events are, for some reason, much rarer and do not
  occur in the particular log I'm adding.)  In many (but not all)
  incidents, the KeyRelease event occurs without a preceding KeyPress
  event.  This problem starts a variable period of time after booting
  the machine; generally within 4 hours.  Once it starts, it persists
  until a reboot.

  Disabling the trackpad with xinput will stop the problem for several
  hours, but eventually something re-enables the trackpad and the
  problem reappears.

  WORKAROUND: Use kernel parameter:
  i8042.dumbkbd

  Running memtest on the box generates an error when one specific core
  runs one specific test, but I cannot rule out that being related to
  memtest's problems with UEFI systems.  (See
  passmark.com/forum/showthread.php?5638 for info on my memtest results
  and the UEFI issues.) I returned the machine to HP for service.  They
  replaced the keyboard, trackpad and memory.  This did not resolve the
  problem.

  I've recreated the problem in UbuntuMate, Ubuntu, and Debian, on both
  3.x and 4.x kernels.  I cannot reliably reproduce the issue on the
  Windows partition on the same box; I think I might have seen it once
  or twice while working on the machine, but can't rule out accidental
  keypresses by me at those times.  Leaving a keylogger running for over
  24 hours on the Windows partition did not show any unexpected keyboard
  events.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 22 21:36:14 2016
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-32-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-33-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-42-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:80af]
  InstallationDate: Installed on 2015-10-30 (84 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:938): WARNING **: [PIDs] Failed to execute command: 
upstart

   ** (lightdm-gtk-greeter:938): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1191): WARNING **: [PIDs] Failed to execute command: 
upstart

   ** (lightdm-gtk-greeter:1191): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic.efi.signed 
root=UUID=613f6223-b665-4289-9dfa-7b003124dfdf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80AF
  dmi.board.vendor: HP
  dmi.board.version: 81.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd08/06/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80AF:rvr81.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm

[Touch-packages] [Bug 1682133] Re: Dual screen is broken

2018-08-27 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
 Assignee: Nicolas (nicolastracktik) => (unassigned)

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

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

Title:
  Dual screen is broken

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi,

  After an update of Ubuntu 14.04 and a reboot, my second screen was not 
recognized by the laptop.
  This is the second time I get this. Last time I had to re-install all my 
stuffs...

  Laptop: Samsung NP900X3G
  System: Ubuntu 14.04.5 LTS
  Graphic card: Intel (00:02.0 VGA compatible controller: Intel Corporation 
Haswell-ULT Integrated Graphics Controller (rev 09))

  Need more informations, tell me thx.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 12 09:24:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c109]
  InstallationDate: Installed on 2016-04-18 (358 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5e26e584-5e80-41c8-9b69-9a0e61826dff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADU.025.140523.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADU.025.140523.PS:bd05/23/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP05ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 900X3G
  dmi.product.version: P05ADU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Apr 12 09:23:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

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

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


[Touch-packages] [Bug 1789249] Re: flickering issue on the startup

2018-08-27 Thread Daniel van Vugt
Can you please provide a video (or just a photo) of the problem?

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

Title:
  flickering issue on the startup

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  midhun@midhun-das:~$ ispci -v

  Command 'ispci' not found, did you mean:

command 'lspci' from deb pciutils

  Try: sudo apt install 
  

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 22:38:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-33-generic, x86_64: installed
   oem-touchpad-alps-synaptics, 0.1: added
   openrazer-driver, 2.3.1, 4.15.0-33-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2018-08-21 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 3542
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=8812aa11-5b02-4d29-abbf-d1c2fc0a81c8 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C3NP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

2018-08-27 Thread Daniel van Vugt
** Tags added: realtime

** Bug watch removed: freedesktop.org Bugzilla #100488
   https://bugs.freedesktop.org/show_bug.cgi?id=100488

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

Title:
  [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I believe this is a pulseaudio regression, as the output of alsa-info
  (http://www.alsa-
  project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine
  as far as I can see.

  I'm currently running Ubuntu 18.04, and I believe this is a regression
  as audio used to work under 17.10. Since upgrading (which fixed a good
  number of other incompatibilities with the machine), I've had no luck
  getting audio to work at all.

  I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and
  'pulseaudio -vv'.

  If I can provide any other information, or if there's anything you'd
  like me to try, I'd be happy to help in any way possible.

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

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


[Touch-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so

2018-08-27 Thread Daniel van Vugt
** Tags added: realtime

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

Title:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 22 22:04:28 2018
  InstallationDate: Installed on 2018-08-13 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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

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


[Touch-packages] [Bug 1789244] Re: Sound driver does not appear to show

2018-08-27 Thread Daniel van Vugt
With Ubuntu and Linux you don't usually need to install any drivers. It
does however look like pulseaudio is failing on the machine, which will
cause loss of sound:

!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - No

To try and fix this, please run:

sudo sh -c "echo 'realtime-scheduling = no' >> /etc/pulse/daemon.conf"

and then reboot.

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

** Tags added: realtime

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

Title:
  Sound driver does not appear to show

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Using my Thomson Neo 10, which is a French made notebook with a UK
  qwerty keyboard, however it appears all support for this notebook is
  that all support is in other languages including french and it is not
  clear what the actual drivers are in order to attempt to find a way of
  installing it myself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  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.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 17:24:50 2018
  InstallationDate: Installed on 2018-08-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: E.C116CM.Thomson.A01
  dmi.bios.version: 5.11
  dmi.board.asset.tag: WS_reserve
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: WS_reserve
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnE.C116CM.Thomson.A01:bvr5.11:bd05/18/2018:svnThomson:pnUK-NEO10A-2WH32:pvrWS_reserve:rvnDefaultstring:rnDefaultstring:rvrWS_reserve:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: UK-NEO10A-2WH32
  dmi.product.version: WS_reserve
  dmi.sys.vendor: Thomson

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

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


[Touch-packages] [Bug 1789204] Re: Problems with GeForce GT 710

2018-08-27 Thread Daniel van Vugt
I can see that you have installed an 'NVIDIA Corporation GK208 [GeForce
GT 710B]' and it is using the default driver called 'nouveau'.

If the NVIDIA card is not yet working properly for you then please try:

  sudo apt install nvidia-driver-390

and reboot.

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

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

** Summary changed:

- Problems with GeForce GT 710
+ [nouveau] Problems with GeForce GT 710

** Tags added: nouveau

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

Title:
  [nouveau] Problems with GeForce GT 710

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The adapter ZOTAC GeForce GT710 was inserted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  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: Mon Aug 27 14:21:44 2018
  DistUpgraded: 2018-08-15 10:35:36,467 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200EV [102b:0530] (prog-if 00 [VGA 
controller])
 Subsystem: IBM MGA G200EV [1014:0369]
   NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710] 
[19da:5360]
  InstallationDate: Installed on 2011-01-28 (2767 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  Lsusb:
   Bus 001 Device 004: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: IBM System x3200 M3 -[7328EAG]-
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=f1c34310-6932-4182-8543-5ef4ab214681 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (12 days ago)
  dmi.bios.date: 06/21/2010
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[GYE136AUS-1.07]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 69Y1171
  dmi.board.vendor: IBM
  dmi.board.version: SIT
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 7
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[GYE136AUS-1.07]-:bd06/21/2010:svnIBM:pnSystemx3200M3-[7328EAG]-:pvr05:rvnIBM:rn69Y1171:rvrSIT:cvnIBM:ct7:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3200 M3 -[7328EAG]-
  dmi.product.version: 05
  dmi.sys.vendor: IBM
  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: Mon Aug 27 11:37:49 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft  Microsoft Basic Optical Mouse v2.0  MOUSE, id 8
   inputLITE-ON Technology USB NetVista Full Width Keyboard. KEYBOARD, 
id 9
  xserver.errors:
   Failed to load module "mga" (module does not exist, 0)
   Failed to load module "mga" (module does not exist, 0)
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

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

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


[Touch-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so

2018-08-27 Thread Daniel van Vugt
To report the bluetooth problem please create a new bug by running this
command:

  ubuntu-bug bluez

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

Title:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 22 22:04:28 2018
  InstallationDate: Installed on 2018-08-13 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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

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


[Touch-packages] [Bug 1132033] Re: Gnome-Shell activities shows black background

2018-08-27 Thread Daniel van Vugt
** Changed in: cairo (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: fglrx-installer (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Gnome-Shell activities shows black background

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Won't Fix
Status in fglrx-installer package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  The Gnome-Shell activities view shows a solid black background while
  using fglrx in raring. I have found that this solid black background
  is only when you have "file manager handle the desktop" enabled. If
  you turn off the file manager handling the desktop, you can then see
  the background image in the activities view.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 22 23:04:29 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'font-name' b"'Ubuntu 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2012-11-24 (91 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release 
amd64(20121023)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to raring on 2013-02-21 (1 days ago)

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

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


[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Triaged
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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


[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

Status in debhelper:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in debhelper source package in Xenial:
  Won't Fix
Status in rsyslog source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Confirmed
Status in debhelper source package in Artful:
  Won't Fix
Status in rsyslog source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Confirmed
Status in debhelper source package in Bionic:
  Won't Fix
Status in rsyslog source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  /var/log's Permission is going back to 755
  after upgrading systemd
  if there are rsyslog's configuration on /var/lib/tmpfiles.d/

  Affected X, A, B, C

  This is because rsyslog's pkg has 00rsyslog.conf and copied it on 
/var/lib/tmpfiles.d/ when it is installing.
  after upgrading systemd, systemd only refresh it's own tmpfiles so disappear 
conf for 00rsyslog.conf ( it doesn't remove file itself )
  so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back 
permission to 775

  [Test Case]

  1. deploy 16.04 vm
  2. check ll /var (775)
  3. apt install --reinstall systemd
  4. check ll /var (755)

  [Regression Potential]
  This fix changes debhelper's override process by using absolute path to 
filename. so if the other pkgs using debhelper e.g systemd are there, It should 
be re-build with new debhelper after patching in theory, now only systemd is 
affected. but building is not affected. also, pkg like rsyslog which is using 
systemd's tmpfile system need to be changed to use 
/etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 
00rsyslog.conf.

  [Others]

  For this issue, need to fix below pkgs

  debhelper
  systemd ( rebuilding with new debhelper is needed )
  rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, 
to support override supported by debhelper )

  [Original description]

  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
    Installed: 229-4ubuntu21.1
    Candidate: 229-4ubuntu21.1
    Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  nick @ log2.be1.ams1:~ $ apt policy rsyslog
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf
  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf
  # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by
  # the syslog group, so that rsyslog can run as user.
  # See tmpfiles.d(5) for details.

  # Type PathMode UID  GID  Age Argument
  d /var/log 0775 root syslog -

  nick @ log2.be1.ams1:

[Touch-packages] [Bug 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  systemd sometimes misdetects Xen VMs (fixed up-stream)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * XEN virtualization missidentified as hyperv
   * This may cause units limited to a virtualisation not to be started; or 
redundant units for the other type of virtualisation to be started instead.
   * Previously xen & hyper-v were detected correctly separately, even when xen 
emulates/suggests that it is hyper-v.

  [Test Case]

   * Execute systemd-detect-virt and check that it detects Xen & Hyperv

  [Regression Potential]

   * Things that "fake" xen might not work as the detection code
  branches are changed, but it would affect previous releases and future
  releases of systemd-detect-virt. So far such things are not known to
  exist, and if such things appear in the future support for them would
  need to land upstream first.

  [Other Info]
   
   * Original bug report

  Cherrypick
  
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a

  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this
  CPUID information when detecting Xen, and thus it erroneously assumes
  that the guest is running under Hyper-V. This causes Xen-related
  services (and anything else that relies on systemd's VM-detection
  functionality) to fail.

  I *believe* this is a regression from systemd 229 as used in Xenial —
  we have at least a few Xen-based VMs that report as Hyper-V via CPUID
  and don't have this issue on that version — but i haven't confirmed
  that for certain.

  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:

  https://github.com/systemd/systemd/issues/8844

  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.

  Thanks!

  See also:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573

  ---

  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  % apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10
    Candidate: 237-3ubuntu10
    Version table:
   *** 237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

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


[Touch-packages] [Bug 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

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

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


[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

2018-08-27 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu4

---
systemd (239-7ubuntu4) cosmic; urgency=medium

  * Workaround broken meson copying symlinked data files, as dangling
symlinks.

 -- Dimitri John Ledkov   Wed, 22 Aug 2018 14:11:35
+0100

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

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-

[Touch-packages] [Bug 1775877] Re: Totem not playing videos after upgrade to 18.04

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Totem not playing videos after upgrade to 18.04

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  After the update, totem does not play any video.
  the only error is about some gtk widget.
  Gstreamer works, since
  gst-launch-1.0 playbin uri=file:///file.mp4
  correctly plays the video.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jun  8 17:30:28 2018
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1775877/+subscriptions

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


[Touch-packages] [Bug 1641949] Re: Paper jam when the printer is shared in xenial

2018-08-27 Thread smurf
Please close this ticket because I do not longer own that printer.
Thank you.

Luca.

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

Title:
  Paper jam when the printer is shared in xenial

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I made a fresh install from scratch of Xenial Xerus 16.04 Mate, my printer is 
a Brother HL-2140.
  The printer was working well until I decided to share it, because I have 
other two pcs that use the printer.
  So I opened the printer manager from the menu, I checked the "Share" box in 
the printer window, then I opened the "Server Configuration" and I checked the 
"Publish shared printers" box and the "Allow printing from Internet" box.
  Starting from that moment my printer is no more able to print because each 
time that prints one sheet automatically collect a second sheet (as if it was 
the same sheet, probably an error in paper size) and obviously an error occurs 
and everything get blocked.
  Unfortunately even if I unpublished and unshared the printer, the error 
persist so now I can't print, I suspect that the Server is the guilty and I 
wish to try to "Desconnect" the server to prove it, but I don't know how to do 
it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Nov 15 08:25:23 2016
  InstallationDate: Installed on 2016-11-04 (10 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat:
   device for Deskjet_3520: hp:/net/Deskjet_3520_series?ip=10.21.39.105
   device for HL-2140-series: usb://Brother/HL-2140%20series?serial=G8J723823
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_3520.ppd', '/etc/cups/ppd/HL-2140-series.ppd'] failed 
with exit code 2: grep: /etc/cups/ppd/Deskjet_3520.ppd: Permission denied
   grep: /etc/cups/ppd/HL-2140-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=d99fe658-6f6c-472d-a1d0-05507c89d3c5 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A55M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd03/29/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA55M-E:rvrRevX.0x: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/1641949/+subscriptions

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


[Touch-packages] [Bug 1789266] Re: ypackage python2.7 2.7.15~rc1-1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 139

2018-08-27 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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1789266

Title:
  ypackage python2.7 2.7.15~rc1-1 failed to install/upgrade: installed
  python2.7 package post-installation script subprocess returned error
  exit status 139

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The only thing I did before this happened was shrinking my boot drive
  volume

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python2.7 2.7.15~rc1-1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 27 16:47:37 2018
  DuplicateSignature:
   package:python2.7:2.7.15~rc1-1
   Setting up python2.7 (2.7.15~rc1-1) ...
   Segmentation fault (core dumped)
   dpkg: error processing package python2.7 (--configure):
installed python2.7 package post-installation script subprocess returned 
error exit status 139
  ErrorMessage: installed python2.7 package post-installation script subprocess 
returned error exit status 139
  InstallationDate: Installed on 2018-08-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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.3ubuntu0.1
  SourcePackage: python2.7
  Title: package python2.7 2.7.15~rc1-1 failed to install/upgrade: installed 
python2.7 package post-installation script subprocess returned error exit 
status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1789266/+subscriptions

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


[Touch-packages] [Bug 1788440] Re: A Dell Optiplex will not reboot after a fresh install of Ubuntu 18.04.

2018-08-27 Thread Rex Bouwense
Received the following response from A Raghuram (araghuramindia) to the
question (#672572) that I posed:

"See if the following steps help you:

1) Choose recovery mode from the GRUB menu
2) Choose resume normal boot from the recovery menu
3) If you are able to get the login screen,
after logging in, uncomment the line "WaylandEnable=False" statement in the 
"/etc/gdm3/custom.conf" file and save it
4) Then restart for a normal reboot.

I had the same problem with a non-Dell desktop computer and the above
steps solved it."

This work-around also allows the computer to boot normally.

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

Title:
  A Dell Optiplex will not reboot after a fresh install of Ubuntu 18.04.

Status in lightdm package in Ubuntu:
  New

Bug description:
  Installed Ubuntu 18.04 on a Dell Optiplex but after the withdrawal of
  the flash drive and pressing enter to reboot the computer, the
  computer screen froze just before the login appeared.  The
  installation was repeated with five different flash drives with both
  Ubuntu 18.04 and Ubuntu 18.04.1.  The same result occurred each time.
  After some research, it was discovered that the LightDM has been
  replaced as the default login display manager by GDM3 which apparently
  is a lot heavier.  Although the Dell Optiplex is over ten years old it
  still meets the minimum requirements for the installation of Ubuntu.
  It will install and reboot after installation of all of the Ubuntu
  "flavors" [Kubuntu, Ubuntu Mate, Ubuntu Budgie, Xubuntu, and Lubuntu]
  as well as Ubuntu 16.04.4.If a computer meets the minimum install
  requirements it should be able to install Ubuntu.  As a work around
  the LightDM was installed and made the default login display manager.
  That works as expected.  Is the new default login display manager to
  heavy for some computers to load?

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

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


[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2018-08-27 Thread JR
I have the same issue on Kubuntu 18.04 (upgraded) with my EP650 headset.
This worked a few releases ago. Sound with A2DP works well.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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


[Touch-packages] [Bug 1592948] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2018-08-27 Thread Thomas Mayer
@gf I'm still on 16.04 and plan to upgrade this year.

I think this issue should still be about upgrading from 14.04 to 16.04
because 14.04 still is supported and people still upgrade from 14.04 to
16.04 until EOL.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

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

-- 
Mailing list: https://launchpad.net/~touch-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-27 Thread Phillip Susi
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

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

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

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

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

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 1787799] Re: 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-27 Thread Phillip Susi
Please attach /var/log/apt/term.log


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

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

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 1789266] [NEW] ypackage python2.7 2.7.15~rc1-1 failed to install/upgrade: installed python2.7 package post-installation script subprocess returned error exit status 139

2018-08-27 Thread Sandi Tutic
Public bug reported:

The only thing I did before this happened was shrinking my boot drive
volume

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python2.7 2.7.15~rc1-1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Mon Aug 27 16:47:37 2018
DuplicateSignature:
 package:python2.7:2.7.15~rc1-1
 Setting up python2.7 (2.7.15~rc1-1) ...
 Segmentation fault (core dumped)
 dpkg: error processing package python2.7 (--configure):
  installed python2.7 package post-installation script subprocess returned 
error exit status 139
ErrorMessage: installed python2.7 package post-installation script subprocess 
returned error exit status 139
InstallationDate: Installed on 2018-08-27 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
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.3ubuntu0.1
SourcePackage: python2.7
Title: package python2.7 2.7.15~rc1-1 failed to install/upgrade: installed 
python2.7 package post-installation script subprocess returned error exit 
status 139
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ypackage python2.7 2.7.15~rc1-1 failed to install/upgrade: installed
  python2.7 package post-installation script subprocess returned error
  exit status 139

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The only thing I did before this happened was shrinking my boot drive
  volume

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python2.7 2.7.15~rc1-1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 27 16:47:37 2018
  DuplicateSignature:
   package:python2.7:2.7.15~rc1-1
   Setting up python2.7 (2.7.15~rc1-1) ...
   Segmentation fault (core dumped)
   dpkg: error processing package python2.7 (--configure):
installed python2.7 package post-installation script subprocess returned 
error exit status 139
  ErrorMessage: installed python2.7 package post-installation script subprocess 
returned error exit status 139
  InstallationDate: Installed on 2018-08-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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.3ubuntu0.1
  SourcePackage: python2.7
  Title: package python2.7 2.7.15~rc1-1 failed to install/upgrade: installed 
python2.7 package post-installation script subprocess returned error exit 
status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1789266/+subscriptions

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


[Touch-packages] [Bug 1628314] Re: Cups trouble shooter asked me to run a command that doesn't work

2018-08-27 Thread david braun
ok - I tried the command (su -c 'journalctl -u cups.service
--since="None" --until="2016-09-27 18:17:05"' > troubleshoot-logs.txt)
on my current system (Ubuntu 18.04.1). I think I ran into the same
problem. The "su" command doesn't tell me who's password it's asking for
- turns out it's the superuser password. On my systems there is no
superuser password so that command (su) is doomed to fail regardless.
Cups needs to be updated at least for Ubuntu. Typically Ubuntu
configures the initial user in the sudoers file so someone at least can
become the super user. The command to do that is "sudo". Also becoming
the super user doesn't seem to be necessary. I executed "journalctl -u
cups.service" and it worked fine. Lastly journalctl couldn't parse
"None" or "none" as a time indicator.

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

Title:
  Cups trouble shooter asked me to run a command that doesn't work

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  The Cups trouble shooter claimed it couldn't find log files saying it was 
possible the it wasn't running as an administrator (which was correct). It 
asked me to run
 su -c 'journalctl -u cups.service --since="None" --until="2016-09-27 
18:17:05"' > troubleshoot-logs.txt
  which failed for 2 reasons
  1. I don't know the cups.service password (so I ran the command as root)
  2. the None specification for "--since" is not valid

  Also the cups logs showed that cups couldn't create
  /var/spool/cups/tmp/.hplip but didn't say what caused the failure
  (turns out it already existed - shouldn't be an error!)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 18:41:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-31 (485 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=dadede94-9cd3-484a-963a-db3e27379a9b ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (54 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.512
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551MA
  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/cups/+bug/1628314/+subscriptions

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


[Touch-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu

2018-08-27 Thread sobczyk
*** This bug is a duplicate of bug 1759836 ***
https://bugs.launchpad.net/bugs/1759836

** This bug has been marked a duplicate of bug 1759836
   systemd-udevd consumes 100% of CPU

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

Title:
  udevd keeps binding and unbinding some usb device und uses all cpu

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  It first appeared when I upgraded ubuntu studio to 18.04
  udevd started to use all available cpu.
  now I'm running ubuntu desktop from a usb key and it's still the same  

  udevadm monitor returns:
  KERNEL[2512.539491] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.540201] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566574] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566866] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.567499] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594050] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594310] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.596510] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.620736] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.624606] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.634706] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.3
  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.2
  Architecture: amd64
  CasperVersion: 1.394
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Aug 20 18:54:48 2018
  ExecutablePath: /lib/systemd/systemd-udevd
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  MachineType: Dell Inc. Vostro 3300
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 07JC8T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3300
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-08-27 Thread Fabrizio
Public bug reported:

While upgrading from 16.04.x LTS to 18.04.1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
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.2
Architecture: amd64
Date: Mon Aug 27 18:40:56 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2012-10-13 (2143 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
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.3ubuntu0.1
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: Upgraded to bionic on 2018-08-27 (0 days ago)

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  While upgrading from 16.04.x LTS to 18.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  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.2
  Architecture: amd64
  Date: Mon Aug 27 18:40:56 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2012-10-13 (2143 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  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.3ubuntu0.1
  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: Upgraded to bionic on 2018-08-27 (0 days ago)

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

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


[Touch-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu

2018-08-27 Thread sobczyk
*** This bug is a duplicate of bug 1759836 ***
https://bugs.launchpad.net/bugs/1759836

the bug started at upstream kernel commit
1455cf8dbfd06aa7651dcfccbadb7a093944ca65


** Bug watch added: Linux Kernel Bug Tracker #199035
   https://bugzilla.kernel.org/show_bug.cgi?id=199035

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=199035
   Importance: Unknown
   Status: Unknown

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

Title:
  udevd keeps binding and unbinding some usb device und uses all cpu

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  It first appeared when I upgraded ubuntu studio to 18.04
  udevd started to use all available cpu.
  now I'm running ubuntu desktop from a usb key and it's still the same  

  udevadm monitor returns:
  KERNEL[2512.539491] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.540201] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566574] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.566866] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.567499] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594050] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.594310] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.596510] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.620736] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  KERNEL[2512.624606] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  UDEV  [2512.634706] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.3
  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.2
  Architecture: amd64
  CasperVersion: 1.394
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Aug 20 18:54:48 2018
  ExecutablePath: /lib/systemd/systemd-udevd
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  MachineType: Dell Inc. Vostro 3300
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 07JC8T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3300
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 932882] Re: Update of a printer driver package does not update the PPD files of the existing queues for this driver

2018-08-27 Thread Marcin Juszkiewicz
I no longer own Epson printer nor use Ubuntu. Still have fun reading
comments in this bug every time new LTS gets released.

Six years. Few LTS releases and bug is still present. Amazing.

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

Title:
  Update of a printer driver package does not update the PPD files of
  the existing queues for this driver

Status in cups package in Ubuntu:
  In Progress
Status in gutenprint package in Ubuntu:
  Invalid
Status in cups source package in Precise:
  Invalid
Status in gutenprint source package in Precise:
  Fix Released
Status in cups source package in Quantal:
  Fix Released
Status in gutenprint source package in Quantal:
  Won't Fix

Bug description:
  I needed to print few tickets for travel. But as they did not appeared
  on my printer I took a look at http://localhost:631/ and discovered
  this:

  "The PPD version (5.2.7) is not compatible with Gutenprint
  5.2.8-pre1."

  Had to print to PDF and do printing from MS Windows laptop...

  [Impact] Printers used with Gutenprint do not work for all users who
  update from an older Ubuntu version to Precise.

  [Test Case] To reproduce: Upgrade from Gutenprint 5.2.7 to
  5.2.8~pre1-0ubuntu2 does not update the PPD files of existing queues.
  To test, create a Gutenprint-based print queue on a system with 5.2.7
  then run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  and see that the PPD files are of Gutenprint version 5.2.7. Update to
  5.2.8~pre1-0ubuntu2 and run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  The PPDs are still not upgraded. Update from 5.2.7 or
  5.2.8~pre1-0ubuntu2 to 5.2.8~pre1-0ubuntu2.1 and your PPD files get
  updated to 5.2.8pre1.

  [Regression Potential] Only change is the timestamp of one file. So
  regressions should not be possible.

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

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


[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

2018-08-27 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Incomplete
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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


[Touch-packages] [Bug 1789258] [NEW] drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

2018-08-27 Thread Darko Veberic
Public bug reported:

every now an then the system freezes but eventually comes back to life.
the boot process is especially slow, login greeter takes ages to come up
and then, while there, needs some extra time to unfreeze and actually
allow typing in the password.

the freeze can be easily reproduced each time when switching from
graphics to console (with ctrl-alt-fN) and back. each time the dmesg
gets also gets appended with the error messages that can be found in the
attached text file.

is the workaround really to uninstall intel's xorg drivers?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libdrm-intel1 2.4.91-2
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.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Aug 27 20:03:14 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [17aa:383e]
   Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [17aa:383e]
InstallationDate: Installed on 2018-08-24 (3 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 0769BJG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr
SourcePackage: libdrm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 68ET37WW
dmi.board.name: IEL10
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Lenovo
dmi.product.name: 0769BJG
dmi.product.version: 3000 N200
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "system logs get filled with these timeout error messages"
   
https://bugs.launchpad.net/bugs/1789258/+attachment/5181380/+files/dmesg_errors.txt

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

Title:
  drm:drm_atomic_helper_wait_for_dependencies flip_done timed out

Status in libdrm package in Ubuntu:
  New

Bug description:
  every now an then the system freezes but eventually comes back to
  life. the boot process is especially slow, login greeter takes ages to
  come up and then, while there, needs some extra time to unfreeze and
  actually allow typing in the password.

  the freeze can be easily reproduced each time when switching from
  graphics to console (with ctrl-alt-fN) and back. each time the dmesg
  gets also gets appended with the error messages that can be found in
  the attached text file.

  is the workaround really to uninstall intel's xorg drivers?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libdrm-intel1 2.4.91-2
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Aug 27 20:03:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [17aa:383e]
 Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [17aa:383e]
  InstallationDate: Installed on 2018-08-24 (3 days ago)
  InstallationMedia: U

[Touch-packages] [Bug 1787540] Re: 16.04 to 18.04.1 ubgrade fails because of diversion of org.freedesktop.systemd1.service

2018-08-27 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd-shim
(Ubuntu)

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

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

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

Title:
  16.04 to 18.04.1 ubgrade fails because of diversion of
  org.freedesktop.systemd1.service

Status in systemd-shim package in Ubuntu:
  New

Bug description:
  I ran do-release-upgrade from a terminal. The process eventually
  failed because of "too many errors". The root cause appears to be
  this:

  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

  I appear to have worked around this by manually removing
  /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service,
  purging systemd-shim via `dpkg -P` and then doing `apt-get install
  -f`, which completed without errors. After that, another `apt-get
  dist-upgrade` was apparently enough to complete the upgrade.

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

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


[Touch-packages] [Bug 1787540] [NEW] 16.04 to 18.04.1 ubgrade fails because of diversion of org.freedesktop.systemd1.service

2018-08-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I ran do-release-upgrade from a terminal. The process eventually failed
because of "too many errors". The root cause appears to be this:

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

I appear to have worked around this by manually removing
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service,
purging systemd-shim via `dpkg -P` and then doing `apt-get install -f`,
which completed without errors. After that, another `apt-get dist-
upgrade` was apparently enough to complete the upgrade.

** Affects: systemd-shim (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
16.04 to 18.04.1 ubgrade fails because of diversion of 
org.freedesktop.systemd1.service
https://bugs.launchpad.net/bugs/1787540
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd-shim in Ubuntu.

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


[Touch-packages] [Bug 1788060] Re: du program crashes on /var/lib

2018-08-27 Thread C de-Avillez
Thank you for opening this bug and helping make Ubuntu better.

You refer to "crash" and "abort", but this bug does not have an apport-
generated stacktrace, neither *any* details on how 'du' fails. As it is,
there is not much we can do.

On a standard Ubuntu system, if 'du' crashes, it should generate a file
under /var/crash/, and then apport should automatically kick in and
proposed to report the crash. Did this not happen? If it *does* happen,
then please open a new bug when requested by apport, and refer back in
the to this one.

** Changed in: coreutils (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  du program crashes on /var/lib

Status in coreutils package in Ubuntu:
  Incomplete

Bug description:
  We have an Ubuntu 18 installation using xfs file systems
  user@hostname:~$ df
  Filesystem 1K-blocks Used Available Use% Mounted on
  udev 19896400   1989640   0% /dev
  tmpfs 404008  848403160   1% /run
  /dev/sda19754624  3083376   6671248  32% /
  tmpfs20200320   2020032   0% /dev/shm
  tmpfs   51200  5120   0% /run/lock
  tmpfs20200320   2020032   0% /sys/fs/cgroup
  /dev/sda2   11194368   958336  10236032   9% /var
  tmpfs 4040040404004   0% /run/user/1001
  tmpfs 4040040404004   0% /run/user/601005952

  du aborts when run in /var and /var/lib, but not in any of the subdirectories 
of /var/lib
  I tried rebooting with linux ... init=/bin/bash to run xfs_repair on the 
/var/file system and it found no errors.
  After the repair command, I mounted /var and ran du again with no errors.
  However once I rebooted into the full O/S, du aborted again in /var and 
/var/lib.
  The du and sudo du both abort, but non-privileged du also dumps core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  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
  Date: Mon Aug 20 15:26:49 2018
  InstallationDate: Installed on 2018-06-11 (69 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1789249] [NEW] flickering issue on the startup

2018-08-27 Thread Midhun Das
Public bug reported:

midhun@midhun-das:~$ ispci -v

Command 'ispci' not found, did you mean:

  command 'lspci' from deb pciutils

Try: sudo apt install 


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 27 22:38:43 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.77, 4.15.0-33-generic, x86_64: installed
 oem-touchpad-alps-synaptics, 0.1: added
 openrazer-driver, 2.3.1, 4.15.0-33-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
InstallationDate: Installed on 2018-08-21 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Inspiron 3542
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=8812aa11-5b02-4d29-abbf-d1c2fc0a81c8 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0C3NP7
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  flickering issue on the startup

Status in xorg package in Ubuntu:
  New

Bug description:
  midhun@midhun-das:~$ ispci -v

  Command 'ispci' not found, did you mean:

command 'lspci' from deb pciutils

  Try: sudo apt install 
  

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 22:38:43 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-33-generic, x86_64: installed
   oem-touchpad-alps-synaptics, 0.1: added
   openrazer-driver, 2.3.1, 4.15.0-33-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2018-08-21 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 3542
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=8812aa11-5b02-4d29-abbf-d1c2fc0a81c8 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0C3NP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.versi

[Touch-packages] [Bug 1482786] Re: man-db daily cron job TOCTOU bug when processing catman pages

2018-08-27 Thread Chris Adams
Was the decision made not to backport this to 14.04 and 16.04 LTS?

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

Title:
  man-db daily cron job TOCTOU bug when processing catman pages

Status in apport package in Ubuntu:
  Confirmed
Status in man-db package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  Confirmed
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  The daily mandb cleanup job for old catman pages changes the
  permissions of all non-man files to user man. The problematic code is:

  # expunge old catman pages which have not been read in a week
  if [ -d /var/cache/man ]; then
cd /
if ! dpkg-statoverride --list /var/cache/man >/dev/null 2>1; then
  find /var/cache/man -ignore_readdir_race ! -user man -print0 | \
xargs -r0 chown -f man || true
fi
...

  By creating a hard link and winning the race, user man may escalate
  privileges to user root. See [1] for full explanation.

  man# mkdir -p /var/cache/man/etc
  man# ln /var/crash/.lock /var/cache/man/etc/shadow
  man# ./DirModifyInotify --Watch /var/cache/man/etc --WatchCount 0 --MovePath 
/var/cache/man/etc --LinkTarget /etc
  ... Wait till daily cronjob was run
  man# cp /etc/shadow .
  man# sed -r -e 
's/^root:.*/root:$1$kKBXcycA$w.1NUJ77AuKcSYYrjLn9s1:15462:0:9:7:::/' 
/etc/shadow > x
  man# cat x > /etc/shadow; rm x
  man# su -s /bin/sh (password is 123)
  root# cat shadow > /etc/shadow; chown root /etc/shadow

  
  # lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  # apt-cache policy man-db
  man-db:
Installed: 2.6.7.1-1ubuntu1
Candidate: 2.6.7.1-1ubuntu1
Version table:
   *** 2.6.7.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.6.7.1-1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  [1]
  http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/

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

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


[Touch-packages] [Bug 1789244] [NEW] Sound driver does not appear to show

2018-08-27 Thread Richie Legend
Public bug reported:

Using my Thomson Neo 10, which is a French made notebook with a UK
qwerty keyboard, however it appears all support for this notebook is
that all support is in other languages including french and it is not
clear what the actual drivers are in order to attempt to find a way of
installing it myself.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
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.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 27 17:24:50 2018
InstallationDate: Installed on 2018-08-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2018
dmi.bios.vendor: E.C116CM.Thomson.A01
dmi.bios.version: 5.11
dmi.board.asset.tag: WS_reserve
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: WS_reserve
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnE.C116CM.Thomson.A01:bvr5.11:bd05/18/2018:svnThomson:pnUK-NEO10A-2WH32:pvrWS_reserve:rvnDefaultstring:rnDefaultstring:rvrWS_reserve:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: UK-NEO10A-2WH32
dmi.product.version: WS_reserve
dmi.sys.vendor: Thomson

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

Title:
  Sound driver does not appear to show

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using my Thomson Neo 10, which is a French made notebook with a UK
  qwerty keyboard, however it appears all support for this notebook is
  that all support is in other languages including french and it is not
  clear what the actual drivers are in order to attempt to find a way of
  installing it myself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  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.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 17:24:50 2018
  InstallationDate: Installed on 2018-08-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: E.C116CM.Thomson.A01
  dmi.bios.version: 5.11
  dmi.board.asset.tag: WS_reserve
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: WS_reserve
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnE.C116CM.Thomson.A01:bvr5.11:bd05/18/2018:svnThomson:pnUK-NEO10A-2WH32:pvrWS_reserve:rvnDefaultstring:rnDefaultstring:rvrWS_reserve:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: UK-NEO10A-2WH32
  dmi.product.version: WS_reserve
  dmi.sys.vendor: Thomson

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

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


[Touch-packages] [Bug 932882] Re: Update of a printer driver package does not update the PPD files of the existing queues for this driver

2018-08-27 Thread fabtagon
Same when upgrading to from previous LTS to Bionic.

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

Title:
  Update of a printer driver package does not update the PPD files of
  the existing queues for this driver

Status in cups package in Ubuntu:
  In Progress
Status in gutenprint package in Ubuntu:
  Invalid
Status in cups source package in Precise:
  Invalid
Status in gutenprint source package in Precise:
  Fix Released
Status in cups source package in Quantal:
  Fix Released
Status in gutenprint source package in Quantal:
  Won't Fix

Bug description:
  I needed to print few tickets for travel. But as they did not appeared
  on my printer I took a look at http://localhost:631/ and discovered
  this:

  "The PPD version (5.2.7) is not compatible with Gutenprint
  5.2.8-pre1."

  Had to print to PDF and do printing from MS Windows laptop...

  [Impact] Printers used with Gutenprint do not work for all users who
  update from an older Ubuntu version to Precise.

  [Test Case] To reproduce: Upgrade from Gutenprint 5.2.7 to
  5.2.8~pre1-0ubuntu2 does not update the PPD files of existing queues.
  To test, create a Gutenprint-based print queue on a system with 5.2.7
  then run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  and see that the PPD files are of Gutenprint version 5.2.7. Update to
  5.2.8~pre1-0ubuntu2 and run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  The PPDs are still not upgraded. Update from 5.2.7 or
  5.2.8~pre1-0ubuntu2 to 5.2.8~pre1-0ubuntu2.1 and your PPD files get
  updated to 5.2.8pre1.

  [Regression Potential] Only change is the timestamp of one file. So
  regressions should not be possible.

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

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


[Touch-packages] [Bug 1788461] Re: Wired network problems after upgrade to Bionic

2018-08-27 Thread Brian Murray
** Package changed: apport (Ubuntu) => linux (Ubuntu)

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

Title:
  Wired network problems after upgrade to Bionic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to bionic i have strange problem with wired network. The
  link seems to be up but dhcp does not get address and hangs forever
  and no packet gets through.

  When i swicth on wireless i can connect to my home network and dhcp
  receives address (from the same router in same network) without any
  problem.

  I can see several kind of logs in dmesg:

  martin@BSR480:~$ dmesg | grep eth
  [1.209334] sky2 :07:00.0 eth0: addr 00:24:54:26:b3:27
  [1.233664] sky2 :07:00.0 enp7s0: renamed from eth0

  martin@BSR480:~$ dmesg | grep enp7s0
  [1.233664] sky2 :07:00.0 enp7s0: renamed from eth0
  [6.839456] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
  [6.843546] sky2 :07:00.0 enp7s0: enabling interface
  [6.845103] IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
  [9.180266] sky2 :07:00.0 enp7s0: Link is up at 1000 Mbps, full 
duplex, flow control rx
  [9.180323] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready

  And in another part of the log if i scroll it through i see:

  [ 1384.381388] WARNING: CPU: 2 PID: 5567 at 
/build/linux-wuhukg/linux-4.15.0/net/mac80211/rx.c:629 
ieee80211_rx_napi+0x93b/0xa90 [mac80211]
  [ 1384.381390] Modules linked in: nfsv3 nfs_acl nfs pci_stub vboxpci(OE) 
lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ccm ip6table_filter ip6_tables devlink iptable_filter bnep 
snd_hda_codec_hdmi hid_generic uas usb_storage usbhid hid binfmt_misc 
nvidia_uvm(POE) ir_lirc_codec lirc_dev rtl2832_sdr r820t mn88473 rtl2832 
i2c_mux samsung_laptop intel_powerclamp coretemp kvm_intel 
snd_hda_codec_realtek snd_hda_codec_generic kvm irqbypass snd_hda_intel 
dvb_usb_rtl28xxu crct10dif_pclmul snd_hda_codec crc32_pclmul dvb_usb_v2 
ghash_clmulni_intel uvcvideo
  [ 1384.381422]  dvb_core snd_hda_core pcbc snd_hwdep videobuf2_vmalloc arc4 
videobuf2_memops rc_core videobuf2_v4l2 snd_pcm videobuf2_core btusb videodev 
btrtl btbcm btintel bluetooth media ecdh_generic snd_seq_midi aesni_intel ath9k 
snd_seq_midi_event aes_x86_64 crypto_simd glue_helper cryptd intel_cstate 
snd_rawmidi nvidia(POE) ath9k_common input_leds snd_seq ath9k_hw joydev 
serio_raw ath snd_seq_device mac80211 snd_timer snd intel_ips cfg80211 drm 
soundcore shpchp lpc_ich mac_hid sch_fq_codel cuse parport_pc sunrpc ppdev lp 
parport ip_tables x_tables autofs4 psmouse ahci libahci sky2 video
  [ 1384.381454] CPU: 2 PID: 5567 Comm: PK-Backend Tainted: PW  OE
4.15.0-32-generic #35-Ubuntu
  [ 1384.381455] Hardware name: SAMSUNG ELECTRONICS CO., LTD. R480/R431/R481
 /R480/R431/R481 , BIOS 09SZ.M013.20100525.XW  05/25/2010
  [ 1384.381468] RIP: 0010:ieee80211_rx_napi+0x93b/0xa90 [mac80211]
  [ 1384.381469] RSP: :8c4823d03d10 EFLAGS: 00010246
  [ 1384.381470] RAX: 0001 RBX: 8c48171fe000 RCX: 
0002
  [ 1384.381471] RDX: 0004 RSI:  RDI: 
c108e000
  [ 1384.381472] RBP: 8c4823d03de0 R08: 0001 R09: 
0001
  [ 1384.381472] R10:  R11: 0001 R12: 
8c4816d00760
  [ 1384.381473] R13:  R14:  R15: 
0004
  [ 1384.381474] FS:  7fe00ce54700() GS:8c4823d0() 
knlGS:
  [ 1384.381475] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1384.381476] CR2: 7fdffd1d1000 CR3: 00016ef24005 CR4: 
000206e0
  [ 1384.381477] Call Trace:
  [ 1384.381479]  
  [ 1384.381493]  ? ar9002_hw_antdiv_comb_conf_set+0x67/0x70 [ath9k_hw]
  [ 1384.381499]  ? ath_ant_comb_scan+0x3ec/0xaf0 [ath9k]
  [ 1384.381502]  ath_rx_tasklet+0xa73/0xf90 [ath9k]
  [ 1384.381506]  ath9k_tasklet+0x171/0x250 [ath9k]
  [ 1384.381510]  tasklet_action+0x64/0x110
  [ 1384.381512]  __do_softirq+0xe4/0x2bb
  [ 1384.381514]  irq_exit+0xb8/0xc0
  [ 1384.381516]  do_IRQ+0x8a/0xd0
  [ 1384.381518]  common_interrupt+0x84/0x84
  [ 1384.381518]  
  [ 1384.381520] RIP: 0033:0x7fe00e9a1f58
  [ 1384.381521] RSP: 002b:7fe00ce53950 EFLAGS: 0202 ORIG_RAX: 
ffde
  [ 1384.381522] RAX: 000dd2ba RBX: 7fdffcccaa90 RCX: 
7fdffc147330
  [ 1384.381523] RDX: 7fdff901b000 RSI: 7fdffc147330 RDI: 
7fdffcccaa90
  [ 1384.381523] RBP: 7fdff98b1060 R08: 7fdff901b000 R09: 
7fdff901b000
  [ 1384.381524] R10: c547

[Touch-packages] [Bug 932882] Re: Update of a printer driver package does not update the PPD files of the existing queues for this driver

2018-08-27 Thread fabtagon
** Attachment added: "cups error log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/932882/+attachment/5181329/+files/error_log

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

Title:
  Update of a printer driver package does not update the PPD files of
  the existing queues for this driver

Status in cups package in Ubuntu:
  In Progress
Status in gutenprint package in Ubuntu:
  Invalid
Status in cups source package in Precise:
  Invalid
Status in gutenprint source package in Precise:
  Fix Released
Status in cups source package in Quantal:
  Fix Released
Status in gutenprint source package in Quantal:
  Won't Fix

Bug description:
  I needed to print few tickets for travel. But as they did not appeared
  on my printer I took a look at http://localhost:631/ and discovered
  this:

  "The PPD version (5.2.7) is not compatible with Gutenprint
  5.2.8-pre1."

  Had to print to PDF and do printing from MS Windows laptop...

  [Impact] Printers used with Gutenprint do not work for all users who
  update from an older Ubuntu version to Precise.

  [Test Case] To reproduce: Upgrade from Gutenprint 5.2.7 to
  5.2.8~pre1-0ubuntu2 does not update the PPD files of existing queues.
  To test, create a Gutenprint-based print queue on a system with 5.2.7
  then run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  and see that the PPD files are of Gutenprint version 5.2.7. Update to
  5.2.8~pre1-0ubuntu2 and run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  The PPDs are still not upgraded. Update from 5.2.7 or
  5.2.8~pre1-0ubuntu2 to 5.2.8~pre1-0ubuntu2.1 and your PPD files get
  updated to 5.2.8pre1.

  [Regression Potential] Only change is the timestamp of one file. So
  regressions should not be possible.

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

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


[Touch-packages] [Bug 1785723] Re: Memory leak in systemd-journald

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

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

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

Title:
  Memory leak in systemd-journald

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-journald has 144 MiB resident after 35 days. After a reboot
  this drops to 23 MiB. All logging config is stock except that logs
  rotate monthly, and the machine is not used as a syslog server.

  This is a very lightly loaded web and mail server, < 10 requests per
  hour. /var/log/journal/.../system.journal grows by 10-15 MiB per day,
  mostly logging automated attacks against SSH, SMTP, and random ports.

  The journal daemon uses more memory than all other daemons combined. I
  sure hope this is a leak and not by design ...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug  6 22:54:34 2018
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=5de0cac7-17b6-4a0f-8715-54cfaaa0a9a9 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

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

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


[Touch-packages] [Bug 1789170] Re: /etc/default/console-setup doesn't affect number of TTY's

2018-08-27 Thread Brian Murray
** Package changed: ubuntu => console-setup (Ubuntu)

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

Title:
  /etc/default/console-setup doesn't affect number of TTY's

Status in console-setup package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 18.04.1 LTC
  Release: Release 18.04

  Package: Linux console (tty)

  Expected: 
  Change in ACTIVE_CONSOLES in /etc/default/console-setup will affect number of 
ttys

  Current state:
  When I change ACTIVE_CONSOLE="dev/tty[1-4]" it doesn't affect number of tty's 
available.
  Still there are tty's 1-6. And the number doesn't change.

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

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


[Touch-packages] [Bug 1789170] [NEW] /etc/default/console-setup doesn't affect number of TTY's

2018-08-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Description: Ubuntu 18.04.1 LTC
Release: Release 18.04

Package: Linux console (tty)

Expected: 
Change in ACTIVE_CONSOLES in /etc/default/console-setup will affect number of 
ttys

Current state:
When I change ACTIVE_CONSOLE="dev/tty[1-4]" it doesn't affect number of tty's 
available.
Still there are tty's 1-6. And the number doesn't change.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
/etc/default/console-setup doesn't affect number of TTY's
https://bugs.launchpad.net/bugs/1789170
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to console-setup in Ubuntu.

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


[Touch-packages] [Bug 1788155] Re: Network Manager - dns search domains not taken into account

2018-08-27 Thread Brian Murray
** Tags added: regression-release

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

Title:
  Network Manager - dns search domains not taken into account

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  In NetworkManager, I've set method to "automatic (DHCP) addresses
  only" and a DNS server to "127.0.0.1" and search domains to
  ".x,.team2.intra.x,.x.com"

  But /etc/resolv.conf does not take the search domains into account
  I've tried to reboot, to up/down the link via "nmcli c down" and the gui, to 
restart systemd-resolved ...

  All was working fine before upgrading from 16.04 to 18.04

  
  poil@poil-VirtualBox:~$ nmcli c show  "Connexion filaire 1"
  connection.id:  Connexion filaire 1
  connection.uuid:68e6d50f-aaef-3d56-a9fa-53ca4814cbf9
  connection.stable-id:   --
  connection.type:802-3-ethernet
  connection.interface-name:  --
  connection.autoconnect: oui
  connection.autoconnect-priority:-999
  connection.autoconnect-retries: -1 (default)
  connection.auth-retries:-1
  connection.timestamp:   1534852601
  connection.read-only:   non
  connection.permissions: --
  connection.zone:--
  connection.master:  --
  connection.slave-type:  --
  connection.autoconnect-slaves:  -1 (default)
  connection.secondaries: --
  connection.gateway-ping-timeout:0
  connection.metered: inconnu
  connection.lldp:default
  802-3-ethernet.port:--
  802-3-ethernet.speed:   0
  802-3-ethernet.duplex:  --
  802-3-ethernet.auto-negotiate:  non
  802-3-ethernet.mac-address: 08:00:27:xx:xx:xx
  802-3-ethernet.cloned-mac-address:  --
  802-3-ethernet.generate-mac-address-mask:--
  802-3-ethernet.mac-address-blacklist:   --
  802-3-ethernet.mtu: auto
  802-3-ethernet.s390-subchannels:--
  802-3-ethernet.s390-nettype:--
  802-3-ethernet.s390-options:--
  802-3-ethernet.wake-on-lan: default
  802-3-ethernet.wake-on-lan-password:--
  ipv4.method:auto
  ipv4.dns:   127.0.0.1
  ipv4.dns-search:.x,.team2.intra.x,.x.com
  ipv4.dns-options:   ""
  ipv4.dns-priority:  0
  ipv4.addresses: --
  ipv4.gateway:   --
  ipv4.routes:--
  ipv4.route-metric:  -1
  ipv4.route-table:   0 (unspec)
  ipv4.ignore-auto-routes:non
  ipv4.ignore-auto-dns:   oui
  ipv4.dhcp-client-id:--
  ipv4.dhcp-timeout:  0 (default)
  ipv4.dhcp-send-hostname:oui
  ipv4.dhcp-hostname: --
  ipv4.dhcp-fqdn: --
  ipv4.never-default: non
  ipv4.may-fail:  oui
  ipv4.dad-timeout:   -1 (default)
  ipv6.method:link-local
  ipv6.dns:   --
  ipv6.dns-search:--
  ipv6.dns-options:   ""
  ipv6.dns-priority:  0
  ipv6.addresses: --
  ipv6.gateway:   --
  ipv6.routes:--
  ipv6.route-metric:  -1
  ipv6.route-table:   0 (unspec)
  ipv6.ignore-auto-routes:non
  ipv6.ignore-auto-dns:   non
  ipv6.never-default: non
  ipv6.may-fail:  oui
  ipv6.ip6-privacy:   0 (désactivé)
  ipv6.addr-gen-mode: stable-privacy
  ipv6.dhcp-send-hostname:oui
  ipv6.dhcp-hostname: --
  ipv6.token: --
  proxy.method:   none
  proxy.browser-only: non
  proxy.pac-url:  --
  proxy.pac-script:   --
  GENERAL.NAME:   Connexion filaire 1
  GENERAL.UUID:   68e6d50f-aaef-3d56-a9fa-53ca4814cbf9
  GENERAL.DEVICES:enp0s3
  GENERAL.STATE:  activé
  GENERAL.DEFAULT:oui
  GENERAL.DEFAULT6:   non
  GENERAL.SPEC-OBJECT:--
  GENERAL.VPN:non
  GENERAL.DBUS-PATH

[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

2018-08-27 Thread Brian Murray
** Tags added: regression-update

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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


[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names

2018-08-27 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Interfaces associated with Huawei "hinic" PCI adapters will not be assigned 
predictable names[*] and instead remain using the kernel names (e.g. eth0). 
This can lead to races where the interface names are not the same on every 
boot. For example, in a system with both 2-port hinic and 2-port igb devices, 
the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic 
before igb loaded. But if igb completes loading first, the hinic interfaces 
would be eth2 & eth3.

  [*]
  
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

  [Test Case]
  grep ^eth /proc/net/dev

  [Fix]
  There's an upstream fix that properly associates the hinic interfaces with 
their PCI devices, providing udev with the info it needs to generate a 
predictable name.

  [Regression Risk]
  The big regression risk here is with existing bionic installs w/ hinic 
devices. They will be currently using "eth" names by default, and this change 
will cause those names to change to "enP" names after upgrade. However, in only 
certain configs are those "eth" names reliable (e.g. only NIC in the system is 
a hinic plug-in card). It sucks to introduce such a change in a stable release 
- but users will be bitten by this when they upgrade or transition to the HWE 
kernel anyway if we don't.

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

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


[Touch-packages] [Bug 1789226] [NEW] /lib/systemd/systemd-journald:6:journal_file_move_to_object:journal_file_link_entry_item:journal_file_link_entry:journal_file_append_entry_internal:journal_file_ap

2018-08-27 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: artful bionic vivid wily xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
journald:6:journal_file_move_to_object:journal_file_link_entry_item:journal_file_link_entry:journal_file_append_entry_internal:journal_file_append_entry

Status in systemd package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1789228] [NEW] /lib/systemd/systemd-journald:6:memset:journal_file_append_object:journal_file_append_entry_internal:journal_file_append_entry:write_to_journal

2018-08-27 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: artful bionic kylin-15.04 vivid wily xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
journald:6:memset:journal_file_append_object:journal_file_append_entry_internal:journal_file_append_entry:write_to_journal

Status in systemd package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field

2018-08-27 Thread Bug Watch Updater
** Changed in: poppler
   Status: Confirmed => Unknown

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/poppler/poppler/issues/463.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Albert Astals Cid
You are wasting previous time of people working on poppler doing such a
useless comment, please refrain from commenting on the future unless you
can add something useful to the discussion.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread pioner14
Confirm the issue in last Archlinux 
KDE Frameworks 5.37.0
Qt 5.9.1 (built against 5.9.1)
Okular 1.2.0

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread pioner14
(In reply to nick from comment #39)
> Confirm the issue in last Archlinux 
> KDE Frameworks 5.37.0
> Qt 5.9.1 (built against 5.9.1)
> Okular 1.2.0

The last Foxitreader for Linux (2.4.1.0609)can correctly fill forms with
Cyrilic

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Psy[H[]
Confirming this on current Debian Testing with libpoppler 0.57.0, in
frontends: evince, qpdfview, mupdf.

This bug is 9 years old, confirmed a hundred times and is still in
status "NEW"? This is ridiculous.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Fidanjan-karen
(In reply to Kamil Páral from comment #37)
> There's not even a link to this bugzilla in the bounty description. You're
> not making it easy for people to understand what that bounty is about.
> 
> Also, this is a universal issue about characters not available in the
> embedded fonts or default pdf fonts. This is not just about cyrillic and
> japanese. I'm also hit by this issue very often, and I use central european
> characters. But as long as the bounty description says only cyrillic and
> japanese, I'm not going to increase the reward. Please adjust.

Kamil, thanks for your comment!
Unfortunately, I don't see the way to change the title of the issue, but I 
wrote more general description and added links to this thread and the bug 
627024 at bugzilla.gnome.org.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Kparal
There's not even a link to this bugzilla in the bounty description.
You're not making it easy for people to understand what that bounty is
about.

Also, this is a universal issue about characters not available in the
embedded fonts or default pdf fonts. This is not just about cyrillic and
japanese. I'm also hit by this issue very often, and I use central
european characters. But as long as the bounty description says only
cyrillic and japanese, I'm not going to increase the reward. Please
adjust.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Andrey Skvortsov
(In reply to fidanjan-karen from comment #35)
> https://freedomsponsors.org/issue/807/problem-with-cyrillic-and-japanese-at-
> pdf-forms-evince-okular

I've added myself as a sponsor to the bounty.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Fidanjan-karen
Andrej.Skvortzov, thanks for this link!
I created an issue and invite everyone to sponsor it:
https://freedomsponsors.org/issue/807/problem-with-cyrillic-and-japanese-at-pdf-forms-evince-okular

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Andrey Skvortsov
You can create bounty for this for example here:
https://freedomsponsors.org/

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Zyx1984
The same issue exists on Fedora 25 even if latest poppler 0.52 is
compiled and installed.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Fidanjan-karen
Guys, can we set some reward for the hero who will solve this? 
This bug seems rather difficult, since it remains for so many years. And, of 
course, it delivers lots of pain to russian and japanese users.
Are there something like Mozilla-Russia «Bug Bounty» program? 
http://mozilla-russia.org/contribute/bounty-en.html

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Andrey Skvortsov
Confirm the issue in Gnome 3.20.1 in Debian/Testing.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Dront78-m
(In reply to Alexander from comment #24)
> So 8 years passed and no fix for this?

this is a gnome devs and they breaking my caps switch every new release ))
so the pdf is much harder to fix here, just use mupdf

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Pavel Kozlov
poppler version 0.45.0

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Pavel Kozlov
Guy, do you have any updates?
I am experiencing the same issue with okular.

Okular version 0.25.0 (KDE 4.14.24)

I can assist with anything may help you to fix this bug.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Murz
Same problem reproduced with displaying PDF form in fresh Firefox and
Chrome web browsers, that use JS rendering. So the problem is in PDF
document - PDF document don't embed non-cyrillic font letters in PDF
file. For this cases is better to display symbols via some default font,
instead of missing letters.

So can we add workaround for "warning: layoutText: cannot convert
U+65E5" - replace font for this symbol to system default?

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Anton Kochkov
Is there any hope to fix it properly?

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1288182]

2018-08-27 Thread Kjeld Flarup
I tested with this form:
http://archive.mid.ru//bul_ns_en.nsf/uvedomlenie.pdf

Foxit Reader for Linux works fine, no need to use Wine
So does google-chrome, it even edits the forms.
Firefox fails, but prints a ? for every cyrillic letter

Im quite sure that this problem can be solved with some font knowlegde.
Somehow it must be possible to find ut which Cyrillic font is used in
the document, and then make some kind of font substitution in the
system.

But weel, I found two working alternatives, so I do not need to fill in
these documents by hand this summer :-)

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Unknown
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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


[Touch-packages] [Bug 1628314] Re: Cups trouble shooter asked me to run a command that doesn't work

2018-08-27 Thread david braun
Hi gf,
Nope - can't help. I no longer run Ubuntu 16 and there's no user "journalctl" 
on my system. Sorry

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

Title:
  Cups trouble shooter asked me to run a command that doesn't work

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  The Cups trouble shooter claimed it couldn't find log files saying it was 
possible the it wasn't running as an administrator (which was correct). It 
asked me to run
 su -c 'journalctl -u cups.service --since="None" --until="2016-09-27 
18:17:05"' > troubleshoot-logs.txt
  which failed for 2 reasons
  1. I don't know the cups.service password (so I ran the command as root)
  2. the None specification for "--since" is not valid

  Also the cups logs showed that cups couldn't create
  /var/spool/cups/tmp/.hplip but didn't say what caused the failure
  (turns out it already existed - shouldn't be an error!)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 18:41:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-31 (485 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=dadede94-9cd3-484a-963a-db3e27379a9b ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (54 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.512
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551MA
  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/cups/+bug/1628314/+subscriptions

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


[Touch-packages] [Bug 1789204] [NEW] Problems with GeForce GT 710

2018-08-27 Thread Johann Schaeuble
Public bug reported:

The adapter ZOTAC GeForce GT710 was inserted.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
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: Mon Aug 27 14:21:44 2018
DistUpgraded: 2018-08-15 10:35:36,467 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Matrox Electronics Systems Ltd. MGA G200EV [102b:0530] (prog-if 00 [VGA 
controller])
   Subsystem: IBM MGA G200EV [1014:0369]
 NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710] [19da:5360]
InstallationDate: Installed on 2011-01-28 (2767 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
Lsusb:
 Bus 001 Device 004: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
 Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM System x3200 M3 -[7328EAG]-
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=f1c34310-6932-4182-8543-5ef4ab214681 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-15 (12 days ago)
dmi.bios.date: 06/21/2010
dmi.bios.vendor: IBM Corp.
dmi.bios.version: -[GYE136AUS-1.07]-
dmi.board.asset.tag: (none)
dmi.board.name: 69Y1171
dmi.board.vendor: IBM
dmi.board.version: SIT
dmi.chassis.asset.tag: none
dmi.chassis.type: 7
dmi.chassis.vendor: IBM
dmi.chassis.version: none
dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[GYE136AUS-1.07]-:bd06/21/2010:svnIBM:pnSystemx3200M3-[7328EAG]-:pvr05:rvnIBM:rn69Y1171:rvrSIT:cvnIBM:ct7:cvrnone:
dmi.product.family: System X
dmi.product.name: System x3200 M3 -[7328EAG]-
dmi.product.version: 05
dmi.sys.vendor: IBM
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: Mon Aug 27 11:37:49 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft  Microsoft Basic Optical Mouse v2.0  MOUSE, id 8
 inputLITE-ON Technology USB NetVista Full Width Keyboard. KEYBOARD, id 
9
xserver.errors:
 Failed to load module "mga" (module does not exist, 0)
 Failed to load module "mga" (module does not exist, 0)
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug bionic compiz-0.9 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/1789204

Title:
  Problems with GeForce GT 710

Status in xorg package in Ubuntu:
  New

Bug description:
  The adapter ZOTAC GeForce GT710 was inserted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  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: Mon Aug 27 14:21:44 2018
  DistUpgraded: 2018-08-15 10:35:36,467 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or 
directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics

[Touch-packages] [Bug 1132033] Re: Gnome-Shell activities shows black background

2018-08-27 Thread Bug Watch Updater
** Changed in: cairo
   Status: Confirmed => Unknown

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

Title:
  Gnome-Shell activities shows black background

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Incomplete
Status in fglrx-installer package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The Gnome-Shell activities view shows a solid black background while
  using fglrx in raring. I have found that this solid black background
  is only when you have "file manager handle the desktop" enabled. If
  you turn off the file manager handling the desktop, you can then see
  the background image in the activities view.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 22 23:04:29 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'font-name' b"'Ubuntu 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2012-11-24 (91 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release 
amd64(20121023)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to raring on 2013-02-21 (1 days ago)

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

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


Re: [Touch-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so

2018-08-27 Thread Zikaras
I did the way you recommended. I wrote sudo apt update to the terminal.
Then I wrote sudo apt -f full-upgrade. Now all is well. And the red sign
disappeared. Thank you very much. You are a smart person.
Sometime later, there is still a need to resolve the issue with bluetooth.
Turns on and sees devices but can not transmit data and access an access
point from another device. I can not use the device when there is no WI-FI
and I need the internet. The phone could provide mobile data, but it does
not succeed.

2018-08-27, pr, 13:31 Daniel van Vugt 
rašė:

> 1. If you could help us to debug the sound problem some more, please try
> changing "realtime-scheduling" to "yes" and confirm that re-introduces
> the bug.
>
> 2. Your red icon is a different bug, most likely (usually) caused by
> failed or broken updates...
>(i) Try removing all PPAs from the system using 'ppa-purge'.
>(ii) Try: sudo apt update ; sudo apt -f full-upgrade
>(iii) Log a new bug.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1788471
>
> Title:
>   There is no sound when you turn on the tube. Sometimes the sound is. I
>   do not understand why this is so
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   There is no sound when you turn on the tube. Sometimes the sound is. I
>   do not understand why this is so
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: pulseaudio 1:11.1-1ubuntu7.1
>   Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p',
> '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1',
> '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit
> code 1:
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Aug 22 22:04:28 2018
>   InstallationDate: Installed on 2018-08-13 (8 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20180105.1)
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago)
>   dmi.bios.date: 08/07/2017
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 5.11
>   dmi.board.asset.tag: Default string
>   dmi.board.name: Default string
>   dmi.board.vendor: AMI Corporation
>   dmi.board.version: Default string
>   dmi.chassis.asset.tag: Default string
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Default string
>   dmi.chassis.version: Default string
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
>   dmi.product.family: Default string
>   dmi.product.name: Default string
>   dmi.product.version: Default string
>   dmi.sys.vendor: Default string
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788471/+subscriptions
>

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

Title:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 22 22:04:28 2018
  InstallationDate: Installed on 2018-08-13 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendo

[Touch-packages] [Bug 1132033]

2018-08-27 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/cairo/cairo/issues/120.

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

Title:
  Gnome-Shell activities shows black background

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Incomplete
Status in fglrx-installer package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The Gnome-Shell activities view shows a solid black background while
  using fglrx in raring. I have found that this solid black background
  is only when you have "file manager handle the desktop" enabled. If
  you turn off the file manager handling the desktop, you can then see
  the background image in the activities view.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 22 23:04:29 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'font-name' b"'Ubuntu 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2012-11-24 (91 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release 
amd64(20121023)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to raring on 2013-02-21 (1 days ago)

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

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


[Touch-packages] [Bug 1647452] Re: package cups-client (not installed) failed to install/upgrade: conflicting packages - not installing cups-client

2018-08-27 Thread gf
Thanks for the update, R.W. 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/1647452

Title:
  package cups-client (not installed) failed to install/upgrade:
  conflicting packages - not installing cups-client

Status in cups package in Ubuntu:
  Invalid

Bug description:
  don't know its number, sorry.  It was a suggestion from AskUbuntu to
  solve the problem of inability to print after attempted upgrade
  ('aborted' it said, and still sort of is)--claimed a conflict with
  'lprng,' which synaptic cannot remove.  I'm lost and still can't
  print.  RW

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-client (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Dec  5 19:56:28 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-05  19:56:26
   Commandline: /usr/sbin/synaptic
   Requested-By: rick (1000)
   Install: cups-bsd:amd64 (2.1.3-4, automatic), cups-client:amd64 (2.1.3-4)
   Remove: lprng:amd64 (3.8.B-2)
  ErrorMessage: conflicting packages - not installing cups-client
  InstallationDate: Installed on 2010-07-24 (2326 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 33: 
Read_file_list: cannot stat required or included file '/etc/printcap' - No such 
file or directory
  MachineType: Acer Aspire 7715Z
  Papersize: letter
  PpdFiles:
   EPSON-XP-520-Series-2: Epson XP-520 Series - epson-inkjet-printer-escpr 
1.6.1-1lsb3.2 (Seiko Epson Corporation LSB 3.2)
   EPSON-XP-520-Series: Epson XP-520 Series - epson-inkjet-printer-escpr 
1.6.1-1lsb3.2 (Seiko Epson Corporation LSB 3.2)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic 
root=UUID=643fe961-079c-4a9b-adc3-43baa7757a53 ro quiet splash 
init=/sbin/upstart
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic 
root=UUID=643fe961-079c-4a9b-adc3-43baa7757a53 ro quiet splash 
init=/sbin/upstart
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-client (not installed) failed to install/upgrade: 
conflicting packages - not installing cups-client
  UpgradeStatus: Upgraded to xenial on 2016-08-25 (101 days ago)
  dmi.bios.date: 12/16/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.04
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 7715Z
  dmi.board.vendor: Acer
  dmi.board.version: V3.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V3.04
  dmi.modalias: 
dmi:bvnAcer:bvrV3.04:bd12/16/2009:svnAcer:pnAspire7715Z:pvrV3.04:rvnAcer:rnAspire7715Z:rvrV3.04:cvnAcer:ct10:cvrV3.04:
  dmi.product.name: Aspire 7715Z
  dmi.product.version: V3.04
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1687177] Re: Samsung-M267x-297x moves print head shortly, but does not print test page

2018-08-27 Thread gf
Thanks for the update, Claudio. 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/1687177

Title:
  Samsung-M267x-297x moves print head shortly, but does not print test
  page

Status in cups package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 29 09:38:19 2017
  Lpstat: device for Samsung-M267x-287x: ipp://192.168.1.5
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung-M267x-287x.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Samsung-M267x-287x.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=aba55381-a22e-41e7-94a0-56e2cc5c1971 ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0206
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M PLUS/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0206:bd04/05/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x: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/1687177/+subscriptions

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


[Touch-packages] [Bug 1661575] Re: printer doesn't print anymore

2018-08-27 Thread gf
Thanks for the update, Jacques. 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/1661575

Title:
  printer doesn't print anymore

Status in cups package in Ubuntu:
  Invalid

Bug description:
  printer doesn't print anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Feb  3 12:02:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [144d:c07f]
  InstallationDate: Installed on 2016-07-06 (212 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=4915e0c4-9b44-4791-91a6-f7ea13097772 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 03KP.M008.20100927.LDG
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: R540/R580/R780/SA41/E452/E852
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 03KP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: R540/R580/R780/SA41/E452/E852
  dmi.product.version: 03KP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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 Feb  3 11:54:03 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1661263] Re: printer

2018-08-27 Thread gf
Thanks for the update, Blain. 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/1661263

Title:
  printer

Status in cups package in Ubuntu:
  Invalid

Bug description:
  i cant configure my printers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Feb  2 15:21:47 2017
  DistUpgraded: 2016-08-02 10:45:18,499 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3034]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3034]
  InstallationDate: Installed on 2016-01-03 (395 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Hewlett-Packard HP Compaq dc7900 Small Form Factor
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=afddea74-5fdf-4357-a40e-f790f5c89633 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (184 days ago)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G1 v01.16
  dmi.board.asset.tag: CZC92914YN
  dmi.board.name: 3031h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC92914YN
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G1v01.16:bd03/05/2009:svnHewlett-Packard:pnHPCompaqdc7900SmallFormFactor:pvr:rvnHewlett-Packard:rn3031h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc7900 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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: Thu Feb  2 16:19:43 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

2018-08-27 Thread Łukasz Zemczak
** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

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

Bug description:
  [Impact]
  Ubuntu users who have installed on ZFS devices.

  [Test case]
  -- upgrade --
  1) install 16.04 using ZFS as rootfs.
  2) upgrade to 18.04

  -- initramfs update --
  1) install Ubuntu, using ZFS as a rootfs.
  2) run "sudo update-initramfs -u"

  Without the patch, you should see a warning from mkinitramfs:

  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  With initramfs-tools patched, you should not see the warning, and
  instead have additional kernel modules added to the initramfs that are
  required to support the block devices that host the ZFS pools.

  [Regression Potential]
  This change is limited to behavior for ZFS filesystems. Likely regressions 
might include loading a kernel module that conflicts with another that is 
required at boot but not blacklisted, causing unexpected behavior on the 
system, or failure to find the necessary kernel modules or ZFS pools, possibly 
leading to an initramfs that does not contain the necessary modules yet has not 
shown a warning on screen to indicate that might be the issue.

  ---

  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  mqueue on /dev/m

[Touch-packages] [Bug 1769682] Please test proposed package

2018-08-27 Thread Łukasz Zemczak
Hello Mathieu, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Won't Fix
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in netplan.io source package in Bionic:
  Fix Released
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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


[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /

2018-08-27 Thread Łukasz Zemczak
Hello Fredrik, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  upgrade of kernel fails with mkinitramfs: failed to determine device
  for /

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

Bug description:
  [Impact]
  Ubuntu users who have installed on ZFS devices.

  [Test case]
  -- upgrade --
  1) install 16.04 using ZFS as rootfs.
  2) upgrade to 18.04

  -- initramfs update --
  1) install Ubuntu, using ZFS as a rootfs.
  2) run "sudo update-initramfs -u"

  Without the patch, you should see a warning from mkinitramfs:

  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  With initramfs-tools patched, you should not see the warning, and
  instead have additional kernel modules added to the initramfs that are
  required to support the block devices that host the ZFS pools.

  [Regression Potential]
  This change is limited to behavior for ZFS filesystems. Likely regressions 
might include loading a kernel module that conflicts with another that is 
required at boot but not blacklisted, causing unexpected behavior on the 
system, or failure to find the necessary kernel modules or ZFS pools, possibly 
leading to an initramfs that does not contain the necessary modules yet has not 
shown a warning on screen to indicate that might be the issue.

  ---

  When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
  root on ZFS I get this error:

  Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic 
/boot/vmlinuz-4.4.0-59-generic
  kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /etc/initramfs-tools/

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for  with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
   subprocess installed post-installation script returned error exit status 2

  version of initramfs-tools is 0.122ubuntu8.8

  Output of mount is:

  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
  rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,n

[Touch-packages] [Bug 1592948] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript wurde durch Signal (Beendet) getötet

2018-08-27 Thread gf
Hi Thomas,
Are you still in Ubuntu version 16.04? Will you be upgrading to 18.04 soon?
Thanks
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/1592948

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript wurde durch Signal (Beendet)
  getötet

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  happened after failed upgrade from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 15 20:25:32 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript wurde durch 
Signal (Beendet) getötet
  InstallationDate: Installed on 2014-11-29 (564 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for FS-1020D: socket://fs1020d.fritz.box:9100
   device for FS-C5150DN: socket://192.168.178.33:9100
   device for FS-C5150DN-COLOR: socket://192.168.178.33:9100
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:6419 Microdia Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5510
  Papersize: a4
  PpdFiles:
   FS-C5150DN-COLOR: Kyocera FS-C5150DN (KPDL)
   FS-C5150DN: Kyocera FS-C5150DN (KPDL)
   FS-1020D: Kyocera Mita FS-1020D
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript wurde durch Signal (Beendet) getötet
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (0 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T00:20:18

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

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


[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

2018-08-27 Thread Thorsten
works perfect!

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Fix Committed

Bug description:
  SRU for bionic:

  Acceptance criteria: An encrypted partition can be decrypted using
  cryptroot-unlock.

  Regression potential: It's not the default method, so unused by the
  majority of people. Besides that the patched script runs fine in
  cosmic.

  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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


[Touch-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so

2018-08-27 Thread Daniel van Vugt
1. If you could help us to debug the sound problem some more, please try
changing "realtime-scheduling" to "yes" and confirm that re-introduces
the bug.

2. Your red icon is a different bug, most likely (usually) caused by failed or 
broken updates...
   (i) Try removing all PPAs from the system using 'ppa-purge'.
   (ii) Try: sudo apt update ; sudo apt -f full-grade
   (iii) Log a new bug.

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

Title:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is no sound when you turn on the tube. Sometimes the sound is. I
  do not understand why this is so

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 22 22:04:28 2018
  InstallationDate: Installed on 2018-08-13 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-08-13 (8 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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

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


  1   2   >