date:20180822

** Changed in: logrotate (Debian)
   Status: New => Fix Released

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

Title:
  logrotate never recovers if the statefile is corrupted

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Released
Status in logrotate source package in Xenial:
  Fix Released
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate source package in Artful:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  [Impact]

  logrotate never recovers if the statefile is corrupted unless you
  remove it or fix the corruption by hand.

  Impact scenarios :

  - System could eventually run out of disk space on a separate
  partition if mounted in "/var" or specifically "/var/log" or even
  worst if "/var/log" is on the same partition as "/" it could create
  even more damage if by any chance the partition is running out of free
  space.

  - System keep updating the same files over and over, creating large
  size logfiles.

  - ...

  [Test Case]

  - Install logrotate
  - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate 
the statefile "var/lib/logrotate/status"
  - Modify "/var/lib/logrotate/status" by removing the first line in order to 
corrupt the file
  - Re-run "/etc/cron.daily/logrotate" and one will get the following error : 
"error: bad top line in state file /var/lib/logrotate/status" every time you 
run logrotate

  Unless you remove the statefile and start again or fix the corruption
  by hand.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Regression Potential]

   * Risk of potential regression is low, and IMHO couldn't be worst
  than the actual situation where logrotate simply doesn't recover from
  a corrupt statefile.

   * The current patch does recover (after verification) and has been
  through some upstream CI validation, community feedbacks, et al.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Other Info]

  * Upstream commit:
  
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

  * Upstream bug:
  https://github.com/logrotate/logrotate/issues/45

  * Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592

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

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

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-22 Thread Bin Li

@Daniel,

 Got it, and the issue 412 was fixed. I will work on the patch today.
Thanks a lot!

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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

[Touch-packages] [Bug 808894] Re: Certain characters are not rendered correctly when selected (highlighted)

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

Title:
  Certain characters are not rendered correctly when selected
  (highlighted)

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen via
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/808894/+attachment/2202502/+files/testfile.pdf
  is when one highlights the first three lines, it doesn't mis-highlight
  the words.

  What happens instead is certain letters are not visible as per
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/808894/+attachment/2202506/+files/screenshot.png
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  CheckboxSubmission: 9e6554c36969a101b9e0e3075c8ffbe0
  CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
  Date: Mon Jul 11 18:38:00 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=fr_FR:en
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 808894]

2018-08-22 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/350.

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

Title:
  Certain characters are not rendered correctly when selected
  (highlighted)

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen via
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/808894/+attachment/2202502/+files/testfile.pdf
  is when one highlights the first three lines, it doesn't mis-highlight
  the words.

  What happens instead is certain letters are not visible as per
  
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/808894/+attachment/2202506/+files/screenshot.png
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  CheckboxSubmission: 9e6554c36969a101b9e0e3075c8ffbe0
  CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
  Date: Mon Jul 11 18:38:00 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=fr_FR:en
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1788510] Re: error luego de actualizar ubuntu 18.04

** Tags added: radeon

** Summary changed:

- error luego de actualizar ubuntu 18.04
+ [radeon] error luego de actualizar ubuntu 18.04

** Package changed: xorg (Ubuntu) => compiz (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/1788510

Title:
  [radeon] error luego de actualizar ubuntu 18.04

Status in compiz package in Ubuntu:
  New

Bug description:
  se congela escritorio

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 22 19:34:38 2018
  DistUpgraded: 2018-08-22 07:17:57,952 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] 
[1002:791f] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems RS690M [Radeon Xpress 
1200/1250/1270] [1179:ff60]
  InstallationDate: Installed on 2018-08-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: TOSHIBA Satellite A305D
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=9b46ee1c-18a4-4f7d-93a8-e0d1c81c43b0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago)
  dmi.bios.date: 09/16/2008
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd09/16/2008:svnTOSHIBA:pnSatelliteA305D:pvrPSAH0U-00P008:rvnTOSHIBA:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite A305D
  dmi.product.version: PSAH0U-00P008
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Aug 22 18:47:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_tra

The bug is either in gtk+3.0 or in mutter. But since it's the gnome-
shell process crashing we should also keep a task for that so that
others can find the bug.

** Summary changed:

- gnome-shell crashed with SIGABRT in g_assertion_message()
+ gnome-shell crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from 
gdk_x11_display_error_trap_pop_internal() from 
meta_input_settings_x11_set_tablet_keep_aspect()

** Information type changed from Private to Public

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

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Triaged

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

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

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr("assertion failed: (trap->end_sequence ==
  0)") from gdk_x11_display_error_trap_pop_internal() from
  meta_input_settings_x11_set_tablet_keep_aspect()

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Crash happened when I tried to use Wacom stylus on Dell 7285
  touchscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug 23 03:55:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-04-20 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   ?? ()
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to cosmic on 2018-04-20 (124 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty

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

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

[Touch-packages] [Bug 1788500] Re: power goes off on laptop

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

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

Title:
  power goes off on laptop

Status in linux package in Ubuntu:
  New

Bug description:
  my laptop keeps powering off on it's own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 22 16:18:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1179:ff10]
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1179:ff10]
  InstallationDate: Installed on 2016-12-13 (617 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: TOSHIBA Satellite A205
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=e4590063-6da5-42db-86b2-bfd532bc73c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.70
  dmi.board.name: SANTA ROSA CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.70:bd11/06/2007:svnTOSHIBA:pnSatelliteA205:pvrPSAF3U-0PV00V:rvnIntelCorporation:rnSANTAROSACRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Satellite A205
  dmi.product.version: PSAF3U-0PV00V
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 22 16:02:15 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13893 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://launchpad.net/~touch-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

Please run this command all on one line:

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

and then reboot. Does that fix the problem?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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 450410] Re: Uses deprecated dpkg --print-installation-architecture

2018-08-22 Thread Matthias Klumpp

Fixed for a while already.

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

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

Title:
  Uses deprecated dpkg --print-installation-architecture

Status in makedev package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: makedev

  MAKEDEV uses dpkg --print-installation-architecture, but this is
  deprecated.  Just use --print-architecture instead. It is the same bug
  as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536540 .

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

-- 
Mailing list: https://launchpad.net/~touch-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

It appears your pulseaudio is not running, which is why there is no
sound:

!!Sound Servers on this system
!!

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

-- 
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 1788398] Re: xserver falls back to software rendering (Onboard AST GPU not used)

I think that's correct. The AST2500 looks like only a 2D graphics chip
and isn't a "GPU". So Xorg needs to use software rendering there.

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

** Changed in: xorg-server (Ubuntu)
   Status: New => 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/1788398

Title:
  xserver falls back to software rendering (Onboard AST GPU not used)

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  This is a workstation with AST2500 onboard GPU. It should be used to
  do the graphics rendering, while the NVIDIA cards are for HPC
  purposes. Nvidia driver is installed with --no-opengl-files option.

  libegl-mesa0 package did not solve the issue as described in earlier
  bug reports on this topic.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..18.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:18:00.0'
  .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:3b:00.0'
  .proc.driver.nvidia.gpus..86.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:86:00.0'
  .proc.driver.nvidia.gpus..af.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:af:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.44  Wed Jul 11 16:51:49 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Aug 22 14:28:05 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  InstallationDate: Installed on 2018-08-16 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Supermicro SYS-7049GP-TRT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b9187a62-ace4-4992-aef4-eb6c731ec1be ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11DPG-QT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd11/29/2017:svnSupermicro:pnSYS-7049GP-TRT:pvr0123456789:rvnSupermicro:rnX11DPG-QT:rvr1.02:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SYS-7049GP-TRT
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/1788398/+subscriptions

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

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

Yes, the patch in comment #7 is only a workaround but that might be as
good as it gets while no developer ever has access to the hardware.

Please reformat the gdm3 patch with more details about what's being
fixed, and then:

1. Attach a patch for Ubuntu 18.10, and subscribe 'ubuntu-sponsors'.

2. When the fix (workaround) has been released to 18.10 then we can
start on the SRU process to get the fix into 18.04
(https://wiki.ubuntu.com/StableReleaseUpdates#Procedure).

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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

[Touch-packages] [Bug 1788383] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

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

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


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

** This bug has been marked a duplicate of bug 1748565
   Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [  320.201884] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Kind regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 22 08:20:18 2018
  InstallationDate: Installed on 2017-10-13 (312 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.3-041803-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  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.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:4815 acl:0 sco:0 events:107 errors:0
    TX bytes:5444 acl:0 sco:0 commands:68 errors:0

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

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

[Touch-packages] [Bug 1788523] Re: package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency problem - not installing e2fsprogs

2018-08-22 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 e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1788523

Title:
  package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency
  problem - not installing e2fsprogs

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Failed along with many other things, during 18.04 upgrade.  libzstd.so
  seemed to be the start of all the failures.  manually installing that
  and then running apt --fix-now install or whatever seemed to get
  things in a good state again.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-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
  Date: Wed Aug 22 19:34:18 2018
  ErrorMessage: pre-dependency problem - not installing e2fsprogs
  InstallationDate: Installed on 2017-10-27 (299 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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: e2fsprogs
  Title: package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency 
problem - not installing e2fsprogs
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)

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

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

[Touch-packages] [Bug 1788523] [NEW] package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency problem - not installing e2fsprogs

2018-08-22 Thread Chris Rogers

Public bug reported:

Failed along with many other things, during 18.04 upgrade.  libzstd.so
seemed to be the start of all the failures.  manually installing that
and then running apt --fix-now install or whatever seemed to get things
in a good state again.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: e2fsprogs 1.44.1-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
Date: Wed Aug 22 19:34:18 2018
ErrorMessage: pre-dependency problem - not installing e2fsprogs
InstallationDate: Installed on 2017-10-27 (299 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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: e2fsprogs
Title: package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency 
problem - not installing e2fsprogs
UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)

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

Title:
  package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency
  problem - not installing e2fsprogs

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Failed along with many other things, during 18.04 upgrade.  libzstd.so
  seemed to be the start of all the failures.  manually installing that
  and then running apt --fix-now install or whatever seemed to get
  things in a good state again.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: e2fsprogs 1.44.1-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
  Date: Wed Aug 22 19:34:18 2018
  ErrorMessage: pre-dependency problem - not installing e2fsprogs
  InstallationDate: Installed on 2017-10-27 (299 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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: e2fsprogs
  Title: package e2fsprogs 1.44.1-1 failed to install/upgrade: pre-dependency 
problem - not installing e2fsprogs
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)

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

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

[Touch-packages] [Bug 314506]

2018-08-22 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/110.

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

Title:
  Error: Illegal entry in bfchar block in ToUnicode CMap

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

Bug description:
  Binary package hint: evince

  It took a long time to load a poster.pdf .

  This is the error it showed in terminal .

  ~$ evince poster.pdf 
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap

  
  When it did show, it is/was sort of grainy. 

  
  If there is some sort font which is missing, it should show in some 
understandable manner.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: evince 2.25.4-0ubuntu2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_IN
  SourcePackage: evince
  Uname: Linux 2.6.28-4-generic i686

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

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

[Touch-packages] [Bug 314506] Re: Error: Illegal entry in bfchar block in ToUnicode CMap

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

Title:
  Error: Illegal entry in bfchar block in ToUnicode CMap

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

Bug description:
  Binary package hint: evince

  It took a long time to load a poster.pdf .

  This is the error it showed in terminal .

  ~$ evince poster.pdf 
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap
  Error: Illegal entry in bfchar block in ToUnicode CMap

  
  When it did show, it is/was sort of grainy. 

  
  If there is some sort font which is missing, it should show in some 
understandable manner.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: evince 2.25.4-0ubuntu2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_IN
  SourcePackage: evince
  Uname: Linux 2.6.28-4-generic i686

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

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

[Touch-packages] [Bug 475889] Re: Arial Narrow: not recognised

** Changed in: fontconfig
   Status: Confirmed => Unknown

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

Title:
  Arial Narrow: not recognised

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  Confirmed
Status in fontconfig package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: fontconfig

  I installed Arial Narrow by copying the TTF files from my windows font
  directory.

  after running fc-cache -f, font dialogs show duplicate entries for
  each style, but no narrow styles, see screenshot. Both duplicates
  select the same variant.

  gnome-font-viewer shows the fonts correctly, and display as style
  "Narrow", for all 4 variants. For the regular arial fonts, the styles
  are "Regular", "Bold", "Italic" and "Bold Italic"

  Steps to reproduce:
   - copy the fonts from the windows install:
  $ cd /usr/share/fonts/truetype/other/
  $ sudo cp /windows/C/WINDOWS/Fonts/ARIALN*

   - set correct permissions
  $ sudo chmod 644 ARIALN*

  - update font cache
  $ fc-cache -fv

  expected result:
  font dialogs show regular and narrow variants for Arial, or a separate font 
Arial Narrow

  obtained result
  font dialogs show duplicate entries for each style.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Nov  5 22:33:35 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  Package: fontconfig 2.6.0-1ubuntu12
  ProcEnviron:
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: fontconfig
  Uname: Linux 2.6.31-14-generic i686

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

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

[Touch-packages] [Bug 475889]

2018-08-22 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/fontconfig/fontconfig/issues/38.

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

Title:
  Arial Narrow: not recognised

Status in Fontconfig:
  Unknown
Status in fontconfig package in Ubuntu:
  Confirmed
Status in fontconfig package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: fontconfig

  I installed Arial Narrow by copying the TTF files from my windows font
  directory.

  after running fc-cache -f, font dialogs show duplicate entries for
  each style, but no narrow styles, see screenshot. Both duplicates
  select the same variant.

  gnome-font-viewer shows the fonts correctly, and display as style
  "Narrow", for all 4 variants. For the regular arial fonts, the styles
  are "Regular", "Bold", "Italic" and "Bold Italic"

  Steps to reproduce:
   - copy the fonts from the windows install:
  $ cd /usr/share/fonts/truetype/other/
  $ sudo cp /windows/C/WINDOWS/Fonts/ARIALN*

   - set correct permissions
  $ sudo chmod 644 ARIALN*

  - update font cache
  $ fc-cache -fv

  expected result:
  font dialogs show regular and narrow variants for Arial, or a separate font 
Arial Narrow

  obtained result
  font dialogs show duplicate entries for each style.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Nov  5 22:33:35 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  Package: fontconfig 2.6.0-1ubuntu12
  ProcEnviron:
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: fontconfig
  Uname: Linux 2.6.31-14-generic i686

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

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

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

2018-08-22 Thread Matthias Klumpp

FWIW, I ran into that issue today as well, and it was really annoying. So I 
fixed in in Debian in a generic way, so this should work for every container 
solution out there.
It requires systemd-detect-virt (systemd) to be installed prior to installing 
makedev though (which usually is the case).

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Released
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Released
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

-- 
Mailing list: https://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 1762961] Re: Screen corruption

2018-08-22 Thread Hamish Farrant

I wasn't getting any colour glitches, just sections of th screen that
weren't getting updated, might be a different bug

On Wed, 22 Aug 2018, 21:31 anarcho, <1762...@bugs.launchpad.net> wrote:

> Hello Hamish,
> Besides XRender what other configurations do you have in the Compositor or
> otherwise.
> I am experiencing green and red static over desktop icons and sometimes
> screen fracturing/tearing of the wallpaper.
>
> Kubuntu 18.04 Precision 5520
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1762961
>
> Title:
>   Screen corruption
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   By default, kubuntu uses the OpenGL for the rendering backend (2.0 or
>   3.1) when it was in these modes, it'd show forms of screen corruption
>
>   for example a loading bar might flicker between a longer and a shorter
> bar
>   or a combo box would seemingly not respond, and then suddenly do
> something unexpected
>   text entered would vanish then reappear
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: xorg 1:7.7+19ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
>   Uname: Linux 4.13.0-21-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   CasperVersion: 1.387
>   CompositorRunning: None
>   Date: Wed Apr 11 18:40:36 2018
>   DistUpgraded: Fresh install
>   DistroCodename: artful
>   DistroVariant: ubuntu
>   DkmsStatus:
>bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
>nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
>   ExtraDebuggingInterest: No
>   GraphicsCard:
>Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell Device [1028:07bf]
>  Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
>   LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64
> (20180105.2)
>   MachineType: Dell Inc. Precision 5520
>   ProcEnviron:
>LANGUAGE=
>TERM=xterm-256color
>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 maybe-ubiquity quiet splash
> ---
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/30/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.5.0
>   dmi.board.name: 0R6JFH
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: Precision
>   dmi.product.name: Precision 5520
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.83-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20170309-0ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762961/+subscriptions
>

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

Title:
  Screen corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  By default, kubuntu uses the OpenGL for the rendering backend (2.0 or
  3.1) when it was in these modes, it'd show forms of screen corruption

  for example a loading bar might flicker between a longer and a shorter bar
  or a combo box would seemingly not respond, and then suddenly do something 
unexpected
  text entered would vanish then reappear

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CompositorRunning: None
  Date: Wed Apr 11 18:40:36 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07bf]
 Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
  LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

2018-08-22 Thread Eric Desrochers

Another package scenario, using "zsh" this time:

$ apt-get install zsh=5.1.1-1ubuntu2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 zsh : Depends: zsh-common (= 5.1.1-1ubuntu2) but 5.1.1-1ubuntu2.2 is to be 
installed
E: Unable to correct problems, you have held broken packages.


I'm currently compiling the 'apt' upstream source code to test using the latest 
and greatest 'apt' version and see by any chance if that behaviour is still 
present using latest version.

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1788520] [NEW] multiple boot problems if /usr is on a logical volume

2018-08-22 Thread valerio

Public bug reported:

xubuntu 18.04.1

After standard installation with LVM, I created further LVs, namely for
/usr, /var, /tmp and /home.

The boot delays about 30 seconds waiting for /usr, this delay is caused by 
wait-for-root.
Also, the /usr volume can not be defined by its label in fstab, it fails to 
find it at boot time.

It seems both problem are caused because wait-for-root is called before
the /usr LV is activated, adding "vgchange -a y" in "init" just before
calling mountfs for /usr allows the boot to complete if /usr is defined
by its label, and eliminates the delay if it is pointed by the
/dev/mapper/ device.

** Affects: initramfs-tools (Ubuntu)
 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/1788520

Title:
  multiple boot problems if /usr is on a logical volume

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  xubuntu 18.04.1

  After standard installation with LVM, I created further LVs, namely
  for /usr, /var, /tmp and /home.

  The boot delays about 30 seconds waiting for /usr, this delay is caused by 
wait-for-root.
  Also, the /usr volume can not be defined by its label in fstab, it fails to 
find it at boot time.

  It seems both problem are caused because wait-for-root is called
  before the /usr LV is activated, adding "vgchange -a y" in "init" just
  before calling mountfs for /usr allows the boot to complete if /usr is
  defined by its label, and eliminates the delay if it is pointed by the
  /dev/mapper/ device.

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

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

[Touch-packages] [Bug 1357529] Re: Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

No problem, Robert. Take your time 
Hope you love the new version of Ubuntu
:) 
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/1357529

Title:
  Magenta Toner Icon is yellow and Yellow Toner Icon is magenta

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I've a Brother-HL-3070CW LED printer. When fetching Printer Properties
  and selecting Ink/Toner Levels I observe the Magenta Toner Icon is
  yellow and Yellow Toner Icon is magenta. So it's difficult to see what
  toner cartridge is high or low because I don't know it the Icon is
  correct or the Text Below the Icon is correct.

  package=cups

  loodje@moosker:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  loodje@moosker:~$ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.1
Candidate: 1.7.2-0ubuntu1.1
Version table:
   *** 1.7.2-0ubuntu1.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  loodje@moosker:~$ 

  Expectation: Icon graphic colour matches text description
  Happened: They do not match - see attachment: Screenshot from 2014-08-15 
12:46:47.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Fri Aug 15 12:37:31 2014
  InstallationDate: Installed on 2014-08-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Brother-HL-3070CW: 
dnssd://Brother%20HL-3070CW%20series._pdl-datastream._tcp.local/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Brother-HL-3070CW: Brother HL-3070CW BR-Script3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed 
root=UUID=4e93e58f-0253-43ba-b7b0-62d336278e07 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1542865] Re: Samsung ML1915 USB printer not detected by cups

Thanks for the update, Marco. 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/1542865

Title:
  Samsung ML1915 USB printer not detected by cups

Status in cups package in Ubuntu:
  Invalid

Bug description:
  My printer stopped working. I tried to remove it from installed
  devices, but I'm unable to add it again since it isn't detected
  anymore. Some command outputs:

  tail -f /var/log/syslog:

  Feb  7 15:48:14 piubuntu udev-add-printer: PPD: 
lsb/usr/cupsfilters/textonly.ppd; Status: 3
  Feb  7 15:48:14 piubuntu kernel: [  803.704139] usb 3-2: USB disconnect, 
device number 15
  Feb  7 15:48:14 piubuntu kernel: [  803.704489] usblp0: removed
  Feb  7 15:48:14 piubuntu udev-configure-printer: remove 
/devices/pci:00/:00:1d.1/usb3/3-2
  Feb  7 15:48:22 piubuntu kernel: [  810.984138] audit: type=1400 
audit(1454856502.255:124): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=3519 comm="cups-deviced" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.984160] audit: type=1400 
audit(1454856502.255:125): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=3519 comm="cups-deviced" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.985259] audit: type=1400 
audit(1454856502.255:126): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=2084 comm="cupsd" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.985277] audit: type=1400 
audit(1454856502.255:127): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=2084 comm="cupsd" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.985495] parport0: lp tried to release 
parport when not owner
  Feb  7 15:48:22 piubuntu kernel: [  810.985910] parport0: lp tried to release 
parport when not owner
  Feb  7 15:49:14 piubuntu kernel: [  862.808058] usb 3-2: new full-speed USB 
device number 16 using uhci_hcd
  Feb  7 15:49:14 piubuntu kernel: [  862.983104] usb 3-2: New USB device 
found, idVendor=04e8, idProduct=3297
  Feb  7 15:49:14 piubuntu kernel: [  862.983115] usb 3-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Feb  7 15:49:14 piubuntu kernel: [  862.983122] usb 3-2: Product: ML-191x 
252x Series
  Feb  7 15:49:14 piubuntu kernel: [  862.983128] usb 3-2: Manufacturer: 
Samsung Electronics Co., Ltd.
  Feb  7 15:49:14 piubuntu kernel: [  862.983134] usb 3-2: SerialNumber: 
Z2L9BKEZ600533N.
  Feb  7 15:49:14 piubuntu kernel: [  862.990262] usblp 3-2:1.0: usblp0: USB 
Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3297
  Feb  7 15:49:14 piubuntu mtp-probe: checking bus 3, device 16: 
"/sys/devices/pci:00/:00:1d.1/usb3/3-2"
  Feb  7 15:49:14 piubuntu mtp-probe: bus: 3, device: 16 was not an MTP device
  Feb  7 15:49:14 piubuntu udev-configure-printer: add 
/devices/pci:00/:00:1d.1/usb3/3-2
  Feb  7 15:49:14 piubuntu udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.1/usb3/3-2
  Feb  7 15:49:14 piubuntu udev-configure-printer: MFG:Samsung MDL:ML-191x 252x 
Series SERN:- serial:Z2L9BKEZ600533N.
  Feb  7 15:49:15 piubuntu kernel: [  864.032213] usblp0: removed
  Feb  7 15:49:15 piubuntu kernel: [  864.046284] usblp 3-2:1.0: usblp0: USB 
Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3297
  Feb  7 15:49:17 piubuntu udev-configure-printer: URI contains USB serial 
number
  Feb  7 15:49:17 piubuntu udev-configure-printer: URI match: 
usb://Samsung/ML-191x%20252x%20Series?serial=Z2L9BKEZ600533N.
  Feb  7 15:49:17 piubuntu kernel: [  866.018157] audit: type=1400 
audit(1454856557.291:128): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=3606 comm="cups-deviced" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:49:17 piubuntu kernel: [  866.018179] audit: type=1400 
audit(1454856557.291:129): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=3606 comm="cups-deviced" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:49:17 piubuntu kernel: [  866.019187] audit: type=1400 
audit(1454856557.291:130): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=2084 comm="cupsd" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:49:17 piubuntu kernel: [  866.019205] audit: type=1400 
audit(1454856557.291:131): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=2084 comm="cupsd" requested_mask="send" 
denied_mask="send" signal=term

[Touch-packages] [Bug 1243367] Re: tar complains about changed directory which hasn't changed

2018-08-22 Thread Don Hirst

It is now going on 5 years and this bug is still alive and well.  I'm
trying to migrate off of 14.04.5, and need to use tar for creating
backups of folders and files to analyze for migration purposes.  This
bug is getting in the way of my work.  I copied the live folder / files
to an intermediate folder / files, and tried to use tar on that, no
luck; it errors out almost immediately.

I am running as root and trying to create an archive of /etc.  
The error says:  tar: ./.: file changed as we read it

My instance is running as a VM in VBox

SCP:  Ubuntu 14.04.5, up-to-date
TAR:  tar --version says:  tar (GNU tar) 1.27.1

Suggestions welcomed.

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

Title:
  tar complains about changed directory which hasn't changed

Status in tar package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 14.04 dev with tar 1.26+dfsg-8 and sometimes I'm
  seeing the message "tar: .: file changed as we read it" which seems to
  not be true. This bugs seems to be very difficult to reproduce and
  even the reproducing behavior is really annoying. As I got today on
  testing the chance for easy reproducing I have made a look with
  inotifywait what is happening:

  sworddragon@ubuntu:~$ mkdir tmp
  sworddragon@ubuntu:~$ inotifywait -mr tmp &
  [1] 12445
  sworddragon@ubuntu:~$ Setting up watches.  Beware: since -r was given, this 
may take a while!
  Watches established.
  ^C
  sworddragon@ubuntu:~$ cd tmp
  sworddragon@ubuntu:~/tmp$ tar --exclude "*\.tar" -zcf test.tar .
  tmp/ OPEN,ISDIR 
  tmp/ CREATE test.tar
  tmp/ OPEN test.tar
  tar: .: file changed as we read it
  tmp/ CLOSE_NOWRITE,CLOSE,ISDIR 
  tmp/ MODIFY test.tar
  tmp/ CLOSE_WRITE,CLOSE test.tar
  sworddragon@ubuntu:~/tmp$ rm test.tar
  tmp/ DELETE test.tar
  sworddragon@ubuntu:~/tmp$ tar --exclude "*\.tar" -cf test.tar .
  tmp/ CREATE test.tar
  tmp/ OPEN test.tar
  tmp/ OPEN,ISDIR 
  tmp/ CLOSE_NOWRITE,CLOSE,ISDIR 
  tmp/ MODIFY test.tar
  tmp/ CLOSE_WRITE,CLOSE test.tar
  sworddragon@ubuntu:~/tmp$ rm test.tar
  tmp/ DELETE test.tar
  sworddragon@ubuntu:~/tmp$ tar --exclude "*\.tar" -zcf test.tar .
  tmp/ OPEN,ISDIR 
  tmp/ CREATE test.tar
  tmp/ OPEN test.tar
  tar: .: file changed as we read it
  tmp/ CLOSE_NOWRITE,CLOSE,ISDIR 
  tmp/ MODIFY test.tar
  tmp/ CLOSE_WRITE,CLOSE test.tar
  sworddragon@ubuntu:~/tmp$ tar --exclude "*\.tar" -zcf test.tar .
  tmp/ OPEN,ISDIR 
  tmp/ MODIFY test.tar
  tmp/ OPEN test.tar
  tmp/ CLOSE_NOWRITE,CLOSE,ISDIR 
  tmp/ MODIFY test.tar
  tmp/ CLOSE_WRITE,CLOSE test.tar

  
  The bug only appears if a compression is activated (even with -J) and the tar 
archive doesn't already exist (tested both multiple times). The curious is if 
I'm closing the terminal and open it again I'm not able to reproduce this 
anymore. The bug will then randomly appear whenever I'm using tar.

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

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

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

2018-08-22 Thread Val

** Attachment added: "Refer to comment #4."
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1788192/+attachment/5179421/+files/successful%20installation%20of%20pending%20updates%20thanks%20to%20a%20manual%20execution%20of%20plasma-discover.txt

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

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

Status in base-files package in Ubuntu:
  Incomplete

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

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

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

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

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

2018-08-22 Thread Val

UPDATE to comment #3.
Executing plasma-discover from a terminal magically solved the issue!
I'll now attach a copy of what displayed in my terminal (see file "successful 
installation of pending updates thanks to a manual execution of 
plasma-discover.txt").

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

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

Status in base-files package in Ubuntu:
  Incomplete

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

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

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

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

[Touch-packages] [Bug 1788510] [NEW] error luego de actualizar ubuntu 18.04

2018-08-22 Thread silvio matera

Public bug reported:

se congela escritorio

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Aug 22 19:34:38 2018
DistUpgraded: 2018-08-22 07:17:57,952 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] 
[1002:791f] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems RS690M [Radeon Xpress 
1200/1250/1270] [1179:ff60]
InstallationDate: Installed on 2018-08-21 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: TOSHIBA Satellite A305D
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=9b46ee1c-18a4-4f7d-93a8-e0d1c81c43b0 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago)
dmi.bios.date: 09/16/2008
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.70
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd09/16/2008:svnTOSHIBA:pnSatelliteA305D:pvrPSAH0U-00P008:rvnTOSHIBA:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: Satellite A305D
dmi.product.version: PSAH0U-00P008
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Aug 22 18:47:27 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: radeon

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


** Tags: apport-bug bionic i386 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/1788510

Title:
  error luego de actualizar ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  se congela escritorio

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 22 19:34:38 2018
  DistUpgraded: 2018-08-22 07:17:57,952 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] 
[1002:791f] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems RS690M [Radeon Xpress 
1200/1250/1270] [1179:ff60]
  InstallationDate: Installed on 2018-08-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: TOSHIBA Satellite A305D
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=9b46ee1c-18a4-4f7d-93a8-e0d1c81c43b0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago)
  dmi.bios.date: 09/16/2008
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

2018-08-22 Thread Val

Same severe issue here - Kubuntu 18.04.1, recently upgraded from 16.04.5 
without problems.
Since base-files 10.1ubuntu2.2 was released, it's been impossible to install it 
via Discover. No user password is asked for in order to install the update. 
Discover just hangs, even preventing the disconnection from my Plasma session 
("Disconnection canceled by /usr/bin/plasma-discover") - I have to kill the 
plasma-discover process manually in order to shutdown or reboot my PC.
Additional package updates came in for installation today (now a total of 7 
package updates pending installation), the issue persists of course, base-files 
10.1ubuntu2.2 prevents the installation of all other package updates.
This bug needs to be taken in account very seriously, I'm afraid novice users 
will get stuck with their graphical update manager (be it Discover or not), 
unable to install any more package updates from August 21st until this issue 
gets fixed.
Do you need additional information about my own configuration files (in order 
to analyze the cause of this issue) or should I test an "apt update" in a 
terminal without waiting?
Thank you.

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

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

Status in base-files package in Ubuntu:
  Incomplete

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

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

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

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

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

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

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

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

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

Title:
  apt behaviour with strict dependencies

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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

[Touch-packages] [Bug 772214] Re: default state file location is wrong in manpage

** Changed in: logrotate (Debian)
   Status: New => Fix Released

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

Title:
  default state file location is wrong in manpage

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate package in Debian:
  Fix Released

Bug description:
  Binary package hint: logrotate

  manpage says that /var/lib/logrotate.status is the default state file,
  but it's actually /var/lib/logrotate/status

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

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

[Touch-packages] [Bug 1780680] Re: Older version in bionic than in xenial

2018-08-22 Thread Anders Kaseorg

Older versions in bionic than in xenial, as of now:

fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29


** Summary changed:

- Older version in artful than in xenial
+ Older version in bionic than in xenial

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

** Changed in: wireless-regdb (Ubuntu)
   Status: New => Fix Released

** Changed in: python-pyvmomi (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Older version in bionic than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  Won't Fix
Status in libdrm package in Ubuntu:
  Won't Fix
Status in linux-meta-azure package in Ubuntu:
  New
Status in linux-meta-gcp package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix
Status in patch package in Ubuntu:
  Invalid
Status in python-pyvmomi package in Ubuntu:
  Invalid
Status in snapcraft package in Ubuntu:
  Fix Released
Status in wireless-regdb package in Ubuntu:
  Fix Released

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

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

2018-08-22 Thread Boris Rybalkin

Ubuntu 18.04.1 LTS

console-cyrillic is not installed.

console-setup 1.178ubuntu2.6
keyboard-configuration 1.178ubuntu2.6 

"sudo kbd_mode -s" fixes it for some time.

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

Title:
  Alt-f2 switches to virtual terminal 2

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

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

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

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

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

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

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

[Touch-packages] [Bug 1788500] [NEW] power goes off on laptop

2018-08-22 Thread Henrietta Rodriguez

Public bug reported:

my laptop keeps powering off on it's own.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
Uname: Linux 4.4.0-133-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Aug 22 16:18:40 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1179:ff10]
   Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1179:ff10]
InstallationDate: Installed on 2016-12-13 (617 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: TOSHIBA Satellite A205
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=e4590063-6da5-42db-86b2-bfd532bc73c8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.70
dmi.board.name: SANTA ROSA CRB
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.70:bd11/06/2007:svnTOSHIBA:pnSatelliteA205:pvrPSAF3U-0PV00V:rvnIntelCorporation:rnSANTAROSACRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Satellite A205
dmi.product.version: PSAF3U-0PV00V
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Aug 22 16:02:15 2018
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13893 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  power goes off on laptop

Status in xorg package in Ubuntu:
  New

Bug description:
  my laptop keeps powering off on it's own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 22 16:18:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1179:ff10]
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1179:ff10]
  InstallationDate: Installed on 2016-12-13 (617 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)

[Touch-packages] [Bug 941917] Re: package libgl1-mesa-glx 7.10.2-0ubuntu2.1 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 2

cleaning up

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

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

Title:
  package libgl1-mesa-glx 7.10.2-0ubuntu2.1 failed to install/upgrade:
  il sottoprocesso vecchio script di post-installation ha restituito lo
  stato di errore 2

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  package libglu1-mesa: problemi con le dipendenze - lasciato non
  configurato

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: libgl1-mesa-glx 7.10.2-0ubuntu2.1
  Uname: Linux 3.0.0generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sat Feb 25 14:30:27 2012
  DistUpgraded: Log time: 2011-10-13 18:39:30.458791
  DistroCodename: natty
  DistroVariant: ubuntu
  ErrorMessage: il sottoprocesso vecchio script di post-installation ha 
restituito lo stato di errore 2
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: mesa
  Title: package libgl1-mesa-glx 7.10.2-0ubuntu2.1 failed to install/upgrade: 
il sottoprocesso vecchio script di post-installation ha restituito lo stato di 
errore 2
  UpgradeStatus: Upgraded to natty on 2011-10-13 (136 days ago)
  version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2.1
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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

[Touch-packages] [Bug 1371834] Re: Chrome causes segfault in i965_dri.so

should be fixed by now

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Chrome causes segfault in i965_dri.so

Status in Chromium Browser:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in Debian:
  Fix Released

Bug description:
  Running chrome 38.0.2125.66-1 on Ubuntu 14.10, on Lenovo X230

  When I start a new instance of chrome, it cannot enable WebGL. I have
  reported that bug separately to chrome at
  https://code.google.com/p/chromium/issues/detail?id=416207

  I suspect the cause of the bug is in mesa, as dmesg contains evidence
  of a segfault:

  [31979.398090] chrome[24013]: segfault at 20 ip 7fbbd5ca5d83 sp 
7fffd7669ab0 error 4 in i965_dri.so[7fbbd59c4000+50a000]
  [31979.585606] chrome[24104]: segfault at 20 ip 7f7550c26d83 sp 
7fff970b4630 error 4 in i965_dri.so[7f7550945000+50a000]
  [31979.737378] chrome[24117]: segfault at 20 ip 7ffd06e45d83 sp 
7fffc989f440 error 4 in i965_dri.so[7ffd06b64000+50a000]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dri 10.2.6-1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Sep 20 11:17:41 2014
  DistUpgraded: 2014-09-02 14:59:08,481 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  MachineType: LENOVO 23301B9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-16-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet crashkernel=384M-:128M 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to utopic on 2014-09-02 (17 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23301B9
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn23301B9:pvrThinkPadX230:rvnLENOVO:rn23301B9:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23301B9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Sep 19 15:45:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4204 
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1371834/+subscriptions

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

[Touch-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU

should be fixed by now

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Google Chrome crash with mesa 10.3 on Intel GPU

Status in Chromium Browser:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  When I start google-chrome on my Ubuntu 14.10 system the process it
  uses to test for a working GPU crashes and then Chrome falls back to
  software rendering.

  In chrome://gpu/ I get:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only, hardware acceleration unavailable
  Flash Stage3D: Software only, hardware acceleration unavailable
  Flash Stage3D Baseline profile: Software only, hardware acceleration 
unavailable
  Compositing: Software only, hardware acceleration unavailable
  Multiple Raster Threads: Unavailable
  Rasterization: Software only, hardware acceleration unavailable
  Threaded Rasterization: Unavailable
  Video Decode: Software only, hardware acceleration unavailable
  Video Encode: Software only, hardware acceleration unavailable
  WebGL: Unavailable

  Driver Bug Workarounds
  clear_uniforms_before_first_program_use
  count_all_in_varyings_packing
  disable_ext_occlusion_query
  disable_post_sub_buffers_for_onscreen_surfaces
  scalarize_vec_and_mat_constructor_args

  Problems Detected
  GPU process was unable to boot: GPU access is disabled in chrome://settings.
  Disabled Features: all
  [...]

  In Ubuntu 14.04 (and also previous versions), on the same laptop, the
  exact same Google Chrome used to work perfectly with GPU acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dri 10.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
    * Setting sensors limits   [240G
  [234G[ OK ]
    * Setting up X socket directories...   [240G
  [234G[ OK ]
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Fri Oct  3 17:48:09 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: kubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0494]
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Oct  2 13:54:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8685
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1377220/+subscriptions

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

[Touch-packages] [Bug 1740183] Re: Consider removing libmir* from mesa

fixed since bionic

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

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

Title:
  Consider removing libmir* from mesa

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Linking to libmir* seems to be of no value & is a roadblock to some things, 
ex. chromecast support in vlc.
  Myself see no change when mesa is not patched for mir, if there is no value 
anymore then please remove from build.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl1-mesa 17.2.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
  Uname: Linux 4.14.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Dec 26 17:24:41 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-17-generic, x86_64: installed
   bbswitch, 0.8, 4.14.0-13-generic, x86_64: installed
   nvidia-381, 381.22, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2017-11-09 (47 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171108)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed 
root=UUID=ca35bdd1-3efc-4356-aa79-7226240b6d57 ro quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1+ppa
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-0ubuntu0~ppa0~18.04.0
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1760566] Re: mesa does not include vaExportSurfaceHandle support for vaapi

bionic has had 18.0.5 for a while now

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  mesa does not include vaExportSurfaceHandle support for vaapi

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa
  misses one tiny patch to make modern AMD GPUs work with VAAPI on
  wayland / gbm / mir. We tried to get this into final 18.0 but was not
  yet accepted. The change itself is a minor. Without it a certain
  feature is not available.

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

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

[Touch-packages] [Bug 1780680] Re: Older version in artful than in xenial

not that an interim release would get the same backports anyway..
upgrades are expected to happen to the next LTS and not elsewhere

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  Won't Fix
Status in libdrm package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Touch-packages] [Bug 1780449] Re: [regression] i965 graphics corruption after recent xenial updates

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

** This bug has been marked a duplicate of bug 1780664
   Recent libgl-mesa graphics update prevents drop down list menu appearing in 
apps like firefox three line/bar menu icon

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

Title:
  [regression] i965 graphics corruption after recent xenial updates

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

Bug description:
  I am using Ubuntu 16.04.4 LTS. Since the original release two years
  ago it was working absolutely fine on a variety of machines. Now, on
  this particular machine I have two monitors:

  1. Dell 24" 1200x1920 (portrait) connected via D-SUB/VGA port
  2. AOC 28" 1920x1080 (landscape) connected via DVI-D

  I have made an upgrade today and the following packages were upgraded:

  https://paste.ubuntu.com/p/5cf8hq6JQK/

  Note that the list includes mesa libraries and xserver-xorg* packages
  which are most suspect.

  Here is my /var/log/Xorg.0.log:

  https://paste.ubuntu.com/p/tB6yGhDT2S/

  Here is the output of "sudo lspci -vvx":

  https://paste.ubuntu.com/p/VVctSFwFSm/

  As you can see, there is nothing special about this machine: a pretty
  vanilla desktop with i5-3570K cpus (NOT overclocked!) and 16GB RAM.
  Oh, I forgot to say what actually happens and why the system is
  unusable: even if I create a single gnome-terminal window (say on the
  Dell monitor) after a couple of seconds (of typing in the terminal)
  large size rectangles appear on the other monitor. And if I start
  Chrome (on a monitor different from the one gnome-terminal is running
  on) then bits of the terminal sometimes appear on one of Chrome's tabs
  and vice versa, i.e. bits (rectangular shape) of Chrome's tabs appear
  on the terminal. Sometimes the content of the terminal gets corrupted.
  And all this happens reasonably quickly (on the order of 5-10
  seconds), which means you can't do any work at all. Also, creating
  other windows (I started pavucontrol in the background) makes the mess
  even worse, i.e. they all keep overwriting each other's rendering
  context.

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

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

[Touch-packages] [Bug 1762007] Re: package libgl1-mesa-dri:i386 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

the logs don't show anything either, closing

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

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

Title:
  package libgl1-mesa-dri:i386 17.2.8-0ubuntu0~16.04.1 failed to
  install/upgrade: problèmes de dépendances - laissé non configuré

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Sorry I have no additional information to give you

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri:i386 17.2.8-0ubuntu0~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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 Apr  6 18:27:16 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: problèmes de dépendances - laissé non configuré
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2017-07-29 (251 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: MSI MS-7817
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=997afd32-9fe6-460d-b7cc-378729e31b24 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: mesa
  Title: package libgl1-mesa-dri:i386 17.2.8-0ubuntu0~16.04.1 failed to 
install/upgrade: problèmes de dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd07/18/2014:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Sat Apr  7 16:54:45 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputPixArt HP Mobile USB Optical Mouse MOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1780680] Re: Older version in artful than in xenial

artful is dead

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

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

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

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  Won't Fix
Status in libdrm package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

well, there's probably a regression in the nouveau driver then.. does
18.04 have the same issue or not?

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

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

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

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

Bug description:
  error message 18.04 installation failed. message scrolled away before
  detail could b copied. lots of warning/failed messages having to do
  with 'frontend.'

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Aug 20 08:46:27 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2012-08-26 (2185 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago)

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

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

[Touch-packages] [Bug 1788486] [NEW] apt behaviour with strict dependencies

2018-08-22 Thread Eric Desrochers

Public bug reported:

[Impact]

We notice that situation while investigating a security update using
Landscape, but it also applies to 'apt' outside the Landscape context.

'apt' should be smarter to detect/install packages with strict
dependencies such as systemd[1] when a version is specified for upgrade
(Ex: $ apt-get install systemd=229-4ubuntu-21.1).

It should automatically install the dependencies (if any) from that same
version as well instead of failing trying to install the highest version
available (if any) while installing the specified version for the one
mentionned :


$ apt-get install systemd=229-4ubuntu-21.1

"systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
=

To face that problem :
- Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
- Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
- Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
- The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

Using systemd is a good reproducer, I'm sure finding other package with
the same situation is easy.

It has been easily reproduced with systemd on Xenial and Bionic so far.

[1] debian/control
Depends: ${shlibs:Depends},
${misc:Depends},
libsystemd0 (= ${binary:Version}),
...

[Workaround]
If package + dependencies are specified, the upgrade work just fine :

Ex: $ apt-get install systemd=229-4ubuntu-21.1
libsystemd0=229-4ubuntu-21.1

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

** Affects: apt (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: apt (Ubuntu Bionic)
 Importance: Undecided
 Status: New


** Tags: sts

** Description changed:

  [Impact]
  
  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.
  
  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for upgrade
  (Ex: apt-get install systemd=229-4ubuntu-21.1". It should automatically
  install the package from that same version for dependencies too instead
  of failing trying to install the highest version available if any :
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4
  is to be installed"
  
- 
  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
- - The upgrade should only specify version for one package, without 
dependencies. (Ex: systemd without libsystemd0 depends)
+ - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)
  
  Using systemd is a good reproducer, I'm sure finding other package with
  the same situation is easy.
  
  It has been easily reproduced with systemd on Xenial and Bionic so far.
  
+ [Workaround]
+ If package + dependencies are specified, the upgrade work just fine :
+ apt-get install systemd=229-4ubuntu-21.1 libsystemd0=229-4ubuntu-21.1
+ 
+ 
  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

** Tags added: sts

** Description changed:

  [Impact]
  
  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.
  
  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for upgrade
  (Ex: apt-get install systemd=229-4ubuntu-21.1". It should automatically
  install the package from that same version for dependencies too instead
  of failing trying to install the highest version available if any :
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4
  is to be installed"
  
  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)
  
  Using systemd is a good reproducer, I'm sure finding other package with
  the same situation is easy.
  
  It has been easily reproduced with systemd on Xenial and Bionic so far.
  
- [Workaround]
- If

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  All kde applications shipped with ubuntu and particularly kubuntu
  bionic print via the qt print dialog, that, unfortunately, does not
  seem to respect the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1
  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: KDE
  Date: Mon Jun 11 10:23:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1641 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions

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

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

2018-08-22 Thread Jan Daciuk

I have just wasted 16 pages of paper.

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  All kde applications shipped with ubuntu and particularly kubuntu
  bionic print via the qt print dialog, that, unfortunately, does not
  seem to respect the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1
  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: KDE
  Date: Mon Jun 11 10:23:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1641 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions

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

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2018-08-22 Thread Daniel Novotny

I am also using nouveau

01:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K2200] 
(rev a2)
Subsystem: NVIDIA Corporation GM107GL [Quadro K2200]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma

2018-08-22 Thread Nate Graham

Thank you!

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

Title:
  cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix
  image slideshows in KDE Plasma

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src source package in Bionic:
  New

Bug description:
  KDE Plasma is affected by a Qt bug that causes image slideshows to
  leak memory, eventually exhausting all available memory and crashing
  the system: https://bugs.kde.org/show_bug.cgi?id=368838

  This principally affects people who use the popular slideshow
  wallpaper feature. Thankfully, there's a Qt patch to fix it the issue:
  https://codereview.qt-project.org/#/c/224684/

  It's slated to go into Qt 5.11. We should strongly consider cherry-
  picking it into 5.9.x to get this important fix into our users' hands
  as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions

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

[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma

2018-08-22 Thread Dmitry Shachnev

You are right. The bug was fixed upstream in 5.11 so I marked the Cosmic
task as fixed. For Bionic, I opened a new task and it is not fixed.

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

Title:
  cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix
  image slideshows in KDE Plasma

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src source package in Bionic:
  New

Bug description:
  KDE Plasma is affected by a Qt bug that causes image slideshows to
  leak memory, eventually exhausting all available memory and crashing
  the system: https://bugs.kde.org/show_bug.cgi?id=368838

  This principally affects people who use the popular slideshow
  wallpaper feature. Thankfully, there's a Qt patch to fix it the issue:
  https://codereview.qt-project.org/#/c/224684/

  It's slated to go into Qt 5.11. We should strongly consider cherry-
  picking it into 5.9.x to get this important fix into our users' hands
  as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so

2018-08-22 Thread Zikaras

Public bug reported:

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

** 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/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:
  New

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 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2018-08-22 Thread Curtis Gedak

@Timo, I am using Intel HD Graphics and no longer experience issues as
described in this report.

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

[Touch-packages] [Bug 1787570] Re: 18.04 loudspeaker not working headphones ok

2018-08-22 Thread sr123456789

** Description changed:

  Upgraded from 16.04 LTS to 18.04 LTS main speaker output no longer
  works. headphone socket on front of PC works ok.
  
  Tried the tips in #1770429 with no effect.
  
  Clean install with format, with no options or changes implemented.
  
  I tried to compile the latest alsa driver from the alsa project but the
  system objected with 'patch not installed' even it was installed.
  
  The system is:
  
  Manufacturer:  NOVATECH LTD
  Product Name:  PC-X002115
  Product Version:   V1.0
  Firmware Version:  F8
  Board Vendor:  Gigabyte Technology Co., Ltd.
  Board Name:Z97M-D3H
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  Kernel release:4.15.0-32-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes
  
- 
  !!ALSA Version
  !!
  
  Driver version: k4.15.0-32-generic
  Library version:1.1.3
  Utilities version:  1.1.3
  
  with a 128G SSD and 1T HDD.

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

Title:
  18.04 loudspeaker not working headphones ok

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Upgraded from 16.04 LTS to 18.04 LTS main speaker output no longer
  works. headphone socket on front of PC works ok.

  Tried the tips in #1770429 with no effect.

  Clean install with format, with no options or changes implemented.

  I tried to compile the latest alsa driver from the alsa project but
  the system objected with 'patch not installed' even it was
  installed.

  The system is:

  Manufacturer:  NOVATECH LTD
  Product Name:  PC-X002115
  Product Version:   V1.0
  Firmware Version:  F8
  Board Vendor:  Gigabyte Technology Co., Ltd.
  Board Name:Z97M-D3H

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Kernel release:4.15.0-32-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  !!ALSA Version
  !!

  Driver version: k4.15.0-32-generic
  Library version:1.1.3
  Utilities version:  1.1.3

  with a 128G SSD and 1T HDD.

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

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

[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma

2018-08-22 Thread Nate Graham

Am I missing something? There is nothing to fix in qtdeclarative-
opensource-src for Cosmic since it has Qt 5.11, and Qt 5.11 simply
includes the fix by default.

This bug tracks cherry-picking the fix into the version of
qtdeclarative-opensource-src that's in Bionic.

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

Title:
  cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix
  image slideshows in KDE Plasma

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src source package in Bionic:
  New

Bug description:
  KDE Plasma is affected by a Qt bug that causes image slideshows to
  leak memory, eventually exhausting all available memory and crashing
  the system: https://bugs.kde.org/show_bug.cgi?id=368838

  This principally affects people who use the popular slideshow
  wallpaper feature. Thankfully, there's a Qt patch to fix it the issue:
  https://codereview.qt-project.org/#/c/224684/

  It's slated to go into Qt 5.11. We should strongly consider cherry-
  picking it into 5.9.x to get this important fix into our users' hands
  as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1761016/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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-22 Thread mmm

lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

uname -a
Linux BSR480 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

-- 
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 apport package in Ubuntu:
  New

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:

[Touch-packages] [Bug 1788459] Re: gssproxy in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd

2018-08-22 Thread Robert Taylor

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

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

** Summary changed:

- gssproxy  in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
+ gssproxy  crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd

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

Title:
  gssproxy  crashes in libselinux.so.1 on Ubuntu 18.04 when called by
  rpc.gssd

Status in gssproxy package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New

Bug description:
  
  I have apache configured to perform a kerberized NFS4 mount using rpc.gssd 
and gssproxy.   

  If I request a web page that requires NFS4 access, then gssproxy
  crashes, reporting a segfault in libselinux.so.1 and the web request
  generates a 403 error.

  gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150
  error 4 in libselinux.so.1[7f2f5bb0d000+25000]

  If I run gssproxy at debug level = 3, and then load a web page, I can
  see the uid/principal request for www-data come in from rpc.gssd:

  # gssproxy -d --debug-level=3 -i -C /etc/gssproxy

  [2018/08/22 17:51:40]: Debug Enabled (level: 3)
  [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) 
[2018/08/22 17:52:06]:  connected (fd = 10)[2018/08/22 17:52:06]:  (pid = 4548) 
(uid = 33) (gid = 33)Segmentation fault (core dumped)

  Since gssproxy is required to initiate kerberos principals for any
  local application services - Ubuntu 18.04 does not currently support
  running application services with NFS4 kerberos dependencies.  This
  has a fairly significant impact on anyone attempting to implement
  kerberos on Ubuntu 18.04

  
  Ubuntu 18.04.1 LTS
  gssproxy 0.8.0-1
  libselinux1:amd64 2.7-2build2
  libgssrpc4:amd64 1.16-2build1

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

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

[Touch-packages] [Bug 1768026] Re: echo message hides cursor

2018-08-22 Thread Wuh Orp

It would be nice if someone could update the Vim package and fix this
issue. Patch 1476 fixes this bug, and it was broken in patch 1449, which
is just a little bit before the patch the Bionic package uses.

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

Title:
  echo message hides cursor

Status in vim:
  Fix Released
Status in vim package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/w0rp/ale/issues/1536#issuecomment-385056702
  upstream bug https://github.com/vim/vim/issues/2612

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim 2:8.0.1453-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 14:16:35 2018
  InstallationDate: Installed on 2017-05-17 (347 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: vim
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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-22 Thread mmm

I also tried to switch off ipv6 following this arcticle
http://www.webupd8.org/2010/05/how-to-disable-ipv6-in-ubuntu-1004.html
but with no change on the system behavior.

-- 
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 apport package in Ubuntu:
  New

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
  [

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2018-08-22 Thread David McKelvie

I am using nouveau

lspci -k says

01:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K620] 
(rev a2)
Subsystem: NVIDIA Corporation GM107GL [Quadro K620]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] Wired network problems after upgrade to Bionic

2018-08-22 Thread mmm

Public bug reported:

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 R11: 70c1 R12: 00010ffb
[ 1384.381525] R13: 7fe00ce53ac0 R14: 7fe00ce539d0 R15: cccd
[ 1384.381526] Code: c4 48 85 c0 0f 84 80 fa ff ff 48 8b 95 70 ff ff ff 4c 8b 
b3 d8 00 00 00 44 8b 85 60 ff ff ff 4c 8b ba d8 00 00 00 e9 42 f9 ff ff <0f> 0b 
48 89 df e8 3b 3d f7 c4 e9 98 f7 ff ff 48 89 de 4c 89 e7 
[ 1384.381549] ---[ end trace 7a6e1aa94a655d72 ]---

** Affects: apport (Ubuntu)
 Importance:

[Touch-packages] [Bug 1788457] [NEW] SRU of LXC 3.0.2 (upstream bugfix release)

2018-08-22 Thread Stéphane Graber

Public bug reported:

LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
- CVE 2018-6556: verify netns fd in lxc-user-nic
- fixed a range of bugs found by Coverity
- lxc-usernsexec: cleanup and bugfixes
- log: add CMD_SYSINFO()
- log: add CMD_SYSERROR()
- state: s/sleep()/nanosleep()/
- lxclock: improve file locking
- lxccontainer: improve file locking
- lxccontainer: fix F_OFD_GETLK checks
- netlink: add __netlink_{send,recv,transaction}
- netns: allocate network namespace id
- MAINTAINERS: add Wolfgang Bumiller
- pam_cgfs: cleanups
- log: add default log priority
- tree-wide: pass unsigned long to prctl()
- macro: add new macro header
- conf: mount devpts without “max” on EINVAL
- tree-wide: handle EINTR in read() and write()
- tree-wide: replace pipe() with pipe2()
- confile: split mount options into flags and data
- conf: improve rootfs setup
- autotools: default to -Wvla -std=gnu11
- tree-wide: remove VLAs
- tree-wide: replace strtok_r() with lxc_iterate_parts()
- utils: add lxc_iterate_parts()
- apparmor: allow start-container to change to lxc-**
- apparmor: update current profiles
- apparmor: Allow /usr/lib* paths for mount and pivot_root
- conf: the atime flags are locked in userns
- conf: handle partially functional device nodes
- conf: create /dev directory
- autotools: build both a shared and static liblxc
- namespace: add api to convert namespaces to standard identifiers
- tree-wide: set MSG_NOSIGNAL
- tree-wide: use mknod() to create dummy files
- cgfsng: respect lxc.cgroup.use
- cgroups: remove is_crucial_cgroup_subsystem()
- tree-wide: remove unneeded log prefixes
- tests: cleanup all tests
- terminal: set FD_CLOEXEC on pty file descriptors
- conf: simplify lxc_setup_dev_console()
- tools: rework tools
- autodev: adapt to changes in Linux 4.18
- log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS* macro
- log: add lxc_log_strerror_r macro
- network: unpriv lxc will run lxc.net.[i].script.up now
- conf: only use newuidmap and newgidmap when necessary
- autotools: support tls in cross-compile

Just like Ubuntu itself, upstream releases long term support releases,
as is 3.0 and then periodic point releases including all the accumulated
bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to xenial-
backports as well, making sure we have the same version everywhere.

** Affects: lxc (Ubuntu)
 Importance: High
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Affects: lxc (Ubuntu Xenial)
 Importance: High
 Assignee: Stéphane Graber (stgraber)
 Status: Triaged

** Affects: lxc (Ubuntu Bionic)
 Importance: High
 Assignee: Stéphane Graber (stgraber)
 Status: Triaged

** Affects: lxc (Ubuntu Cosmic)
 Importance: High
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Also affects: lxc (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: lxc (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: lxc (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: lxc (Ubuntu Cosmic)
   Status: New => Triaged

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

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

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

** Changed in: lxc (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Bionic)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Cosmic)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  SRU of LXC 3.0.2 (upstream bugfix release)

Status in lxc package in Ubuntu:
  In Progress
Status in lxc source package in Xenial:
  Triaged
Status in lxc source package in Bionic:
  Triaged
Status in lxc source package in Cosmic:
  In Progress

Bug description:
  LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
  - CVE 2018-6556: verify netns fd in

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-08-22 Thread Tim Johnston

I tried downgrading wpa-supplicant (mentioned by Lauwie), and it did not
help this.

If Petr is correct, the fix would actually require downgrading OpenSSL
(or whatever used to supply the missing 3DES cipher prior to Bionic),
right?

What's the Ubuntu equivalent of the Fedora workaround for this? ($
update-crypto-policies --set LEGACY)

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions

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

[Touch-packages] [Bug 1788448] [NEW] CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

2018-08-22 Thread Joseph Yasi

*** This bug is a security vulnerability ***

Public security bug reported:

There are 3 security issues reported in libx11 that are fixed upstream
in libx11 1.6.6.

Bugs announced:
https://lists.x.org/archives/xorg-announce/2018-August/002915.html

Release announcement of libx11 1.6.6 with commits fixing them listed:
https://lists.x.org/archives/xorg-announce/2018-August/002916.html

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

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

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

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

** Information type changed from Private Security to Public Security

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

Title:
  CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

Status in libx11 package in Ubuntu:
  New

Bug description:
  There are 3 security issues reported in libx11 that are fixed upstream
  in libx11 1.6.6.

  Bugs announced:
  https://lists.x.org/archives/xorg-announce/2018-August/002915.html

  Release announcement of libx11 1.6.6 with commits fixing them listed:
  https://lists.x.org/archives/xorg-announce/2018-August/002916.html

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

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

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

so you all are using nouveau?

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

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

[Touch-packages] [Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

2018-08-22 Thread hsinclair

The driver works properly. However, the configuration is what's at issue
(therefore an apt problem). The configuration that's forcible enforced
in the xorg.conf.d directory doesn't take into account that some devices
have dual video cards. My issue was that there is an onboard Intel video
chipset and also a NVidia discrete video adapter in my laptop. The
kernel detects Intel and NVidia video cards and loads the Intel
drivers... When the X-Windows system loads it detects the NVidia video
card and attempts to load the X-Server system for it, but the underling
modules haven't been loaded into the system and therefore loads the the
black screen.

If you go into the xorg.conf.d and modify the 10-nvidia.conf files to
add the [Option "PrimaryGPU" "true"] line then it works, but because
these files are not configured in the package as configuration files
they are overwritten on every update.

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

Title:
  Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?

Status in apt package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Using the April 19th daily build of Kubuntu 18.04 I installed the
  Nvidia drivers via the following command.

  sudo ubuntu-drivers autoinstall

  The install process proceeds fine and after a logout process I get a
  black screen.  I tried this on the April 17th daily build of bionic
  and a reboot also results in a black screen.

  The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE
  After I installed latest Nvidia driver-390 and tried to boot after shutting 
down once I faced a black screen problem. since, I'm a noob but something 
related to nvidia drivers couldn't be started. Then I followed 
https://askubuntu.com/a/968692/802490
  While following these instructions re-installing of nvidia drivers failed. 
The only things that worked is purging the drivers and changing 
"WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install 
nvidia drivers again but I'm afraid that this will lead to that problem again. 
Can anyone help in re-installing the driver such that I won't face that 
problem?  END QUOTE

  THE WORK AROUND

  Use Ctrl-Alt-f6 to get to a login prompt.
  Login
  run  "startx"

  The x server will start and Nvidia drivers will function.

  THE PROBLEM
  When I try to run SDDM I get an error (Which I will try to copy down to add 
to this bug when I am on a different computer than the one I am reporting the 
bug about.).

  Installing lightDM does not work... it installs but is either will not
  run or will not actually start a x session.

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

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

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2018-08-22 Thread David McKelvie

I reverted to the correct behaviour by

cd /home/david/DisplayBug-Jul7-2018

sudo dpkg -i \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

sudo apt-mark hold \
libegl1-mesa \
libgbm1 \
libgl1-mesa-dri \
libwayland-egl1-mesa \
mesa-vdpau-drivers

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

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

2018-08-22 Thread Cristian Aravena Romero

Hello Brian Murray,

First run the program 'whoopsie' then run 'systemctl status apport-
autoreport.service' and no longer throw the error...


caravena@caravena-530u3c-530u4c:/var/crash$ whoopsie
caravena@caravena-530u3c-530u4c:/var/crash$ systemctl status 
apport-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: inactive (dead) since Wed 2018-08-22 10:15:46 -03; 3h 24min ago
  Process: 11093 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=0/SUCCESS)
 Main PID: 11093 (code=exited, status=0/SUCCESS)

ago 22 10:15:46 caravena-530u3c-530u4c systemd[1]: Starting Process error 
reports when automatic reporting is enabled...
ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: 
/var/crash/_usr_bin_gnome-control-center.1000.crash already marked for upload, 
skipping
ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: 
/var/crash/_usr_lib_telepathy_telepathy-idle.1000.crash already marked for 
upload, skipping
ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: 
/var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping
ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: 
/var/crash/_usr_bin_Xwayland.1000.crash already marked for upload, skipping
ago 22 10:15:46 caravena-530u3c-530u4c whoopsie-upload-all[11093]: All reports 
processed
ago 22 10:15:46 caravena-530u3c-530u4c systemd[1]: Started Process error 
reports when automatic reporting is enabled.

kind regards,
--
Cristian Aravena Romero (caravena)

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

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

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2018-08-22 Thread David McKelvie

The update to xserver-xorg-core 2:1.18.4-0ubuntu0.8 doesnt seem to fix
the menu bug for me.

I apt-mark unheld libegl1-mesa libgbm1 libgl1-mesa-dri libwayland-
egl1-mesa mesa-vdpau-drivers

Did an update. Checked that I had xserver-xorg-core 2:1.18.4-0ubuntu0.8
installed

Rebooted.

Then bug is back. Icons on Gimp Tool menu turns black and/red on mouse over. 
Popup menu in emacs (when closing emacs window with unsaved files) does not 
display some buttons until you mouse over them. Popup menu for software updater 
has black background instead of white.

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

2018-08-22 Thread Scott Moser

here is a pastebin of boot with systemd debugging.
 http://paste.ubuntu.com/p/vGTRh6WB3B/

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

Title:
  transient systemd ordering cycle in boot with overlayroot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  open-iscsi test utilizes overlayroot to boot a cloud-image with root
  filesystem on a read-only iscsi server.

  The /etc/fstab file in the image looks like this:
    LABEL=cloudimg-rootfs   /ext4   defaults0 0
    #LABEL=UEFI /boot/efi   vfatdefaults0 0

  when init takes over from the initramfs, we have

    /proc/cmdline:
  nomodeset iscsi_initiator=maas-enlist
  iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
  iscsi_target_port=3260 iscsi_initiator=maas-enlist
  ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
  
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
  overlayroot=tmpfs console=ttyS0
  ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash

    /etc/fstab:
  # cat /etc/fstab
  #
  #  This fstab is in an overlay. The real one can be found at
  #  /media/root-ro/etc/fstab
  #  The original entry for '/' and other mounts have been updated to be 
placed
  #  under /media/root-ro.
  #  To permanently modify this (or any other file), you should change-root 
into
  #  a writable view of the underlying filesystem using:
  #  sudo overlayroot-chroot
  #
  #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
  /media/root-ro/ / overlay 
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
  #LABEL=UEFI /boot/efi vfat defaults 0 0

   /root/root-ro/etc/fstab:
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  #LABEL=UEFI /boot/efi   vfatdefaults0 0

   /proc/mounts:
     sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
     proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
     udev /dev devtmpfs 
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
     devpts /dev/pts devpts 
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
     tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
     /dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 
/media/root-ro ext4 ro,relatime 0 0
     tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
     overlayroot / overlay 
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 0 0

   /proc/1/mountinfo:
     21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
     22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
     23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev 
rw,size=233748k,nr_inodes=58437,mode=755
     24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
     25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs 
rw,size=49288k,mode=755
     26 28 8:1 / /media/root-ro ro,relatime - ext4 
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
     27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
     28 0 0:24 / / ro,relatime - overlay overlayroot 
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_

  overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
  read-only mount of block device on mount point '$ROOTMNT'
  (ROOTMNT=/root). In order to set up the overlayroot, it does the
  following:

   mkdir /media/root-ro /media/root-rw # in the initramfs
   mount -t tmpfs tmpfs-root /media/root-rw
   mkdir /media/root-rw/overlay-workdir/_
   mount --move $ROOTMNT /media/root-ro
   mount -t overlay -o 
lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 overlayroot /root
   mkdir $ROOTMNT/media/root-ro
   mkdir $ROOTMNT/media/root-rw
   mount --move /media/root-ro "${ROOTMNT}/media/root-ro"
   mount --move /media/root-rw "${ROOTMNT}/media/root-rw"

   # then, if 'ro' on the command line, it mounts /root read-only.
   mount -o remount,ro $ROOTMNT

  The script then exits, as ROOTMNT is now set up with a read-only mount
  of the overlayroot.  All the mounts it has done have been moved
  under ROOTMNT.

  On failure systemd reports:
     [  104.098833] systemd[1]: media-root\x2dro.mount: Found ordering cycle on 
-.mount/start
     [  104.109897] systemd[1]: media-root\x2dro.mount: Found dependency on 
media-root\x2dro.mount/start
     [  104.121386] systemd[1]: media-root\x2dro.mount: Unable to break cycle 
starting with media-root\x2dro.mount/start
     [  104.137591] systemd[1]: Requested transaction contains an unfixable 
cyclic ordering dependency: Resource deadlock avoided

  On

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

2018-08-22 Thread Rex Bouwense

Public bug reported:

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?

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

-- 
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 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

Launchpad has imported 11 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103652.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-11-09T15:28:49+00:00 Laurent Bigonville wrote:

Hi,

The following bug has been reported in debian:

===

Dear Maintainer,
fontconfig now requires nano second mtime precision on files in order to
validate their freshness. squashfs does not seem to support nano second
mtime precision causing any Desktop ISO's made with live-build to regenrate
the font cache at the desktop startup leading to a very slow time to desktop.

===

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880574

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/0


On 2017-11-10T03:37:29+00:00 Akiro wrote:

Hmm, what does "not seem to support" really mean here? are you
generating a cache on non-squashfs and using it on squashfs then?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/1


On 2017-11-10T08:40:51+00:00 Laurent Bigonville wrote:

I believe that what bug reporter means is that the cache is added to the
squashfs during the build of the livecd and at boot when FC tries to
check the freshness of the cache it decides that it needs to be updated
and then write a fresh one to the unionfs (I suppose)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/2


On 2017-11-10T09:39:56+00:00 Akiro wrote:

Can you give me a log of FC_DEBUG=16 fc-cache prior to boot the desktop?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/3


On 2018-04-04T10:40:22+00:00 Jean-Baptiste Lallement wrote:

Created attachment 138574
output of FC_DEBUG=16 fc-cache

I attached the output of FC_DEBUG=16 fc-cache before booting to an Ubuntu 
Desktop Live Session. This is a follow-up of the issue reported in LP 
(https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836) where, according 
to latest comments), the font cache is regenerated when the user session 
starts. 
Let me know if you need more information.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/9


On 2018-04-04T13:15:41+00:00 Iain Lane wrote:

Created attachment 138578
cache: If nsec is zero, don't use it for comparisons

I made a (stupid?) patch. Is this a reliable way to go about falling
back from nsec to non-nsec? I couldn't find a way to actually ask the
question of the system directly.

We're particularly interested because this is a big cause of live image
boot slowness on Ubuntu. This patch works as intended; the cache isn't
regenerated on live system boot any more.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/13


On 2018-04-04T21:33:55+00:00 Alistair Buxton wrote:

The problem as I understand it:

1. You have /usr/share/fonts/* on ext4 or similar FS with nanos.
2. /usr/share/fonts has a timestamp like 1522818676.601423551.
3. You run fontconfig and it stores the timestamp in the cache file.
4. You build a squashfs from the FS. Squashfs does not support nanos.
5. The timestamp of /usr/share/fonts inside the squashfs becomes 1522818676.0.
6. Installer boots and fontconfig sees the mismatched time stamps so rebuilds 
the cache in the live user's home directory - which is wiped at reboot.
7. During install the squashfs is copied back to an ext4 FS.
8. User reboots and logs in.
9. /usr/share/fonts is now on a filesystem which supports nanos, but the 
original time stamp nanos has been lost.
10. Fontconfig decides the cache is out of date and rebuilds it again, in the 
new user's home directory. This happens each time a newly created user logs in, 
until such time as a postinst script rebuilds the system font cache.

Note steps 9 and 10 only happen on Xubuntu and maybe some other
flavours, but not Ubuntu.

This means that even if you could ask the system whether the filesystem
supports nanos, that wouldn't be enough. It is possible for the
timestamp information to be lost/mutated through squashfs, and then
copied back to a filesystem with nanos, and then there is no way to
determine whether that has happened or not.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1749546/comments/15

[Touch-packages] [Bug 1788435] [NEW] Backport Workaround for Content-Encoding: None

2018-08-22 Thread canavan

Public bug reported:

With the upgrade to curl 7.58.0 in Ubuntu 18.04, the behavior of libcurl
has changed when CURLOPT_ACCEPT_ENCODING is set to values other than
NULL, and an unknown encoding is used by the server. Previously, curl
would decode "gzip" and "deflate" (and now "br") and quietly pass any
other, unknown encoding. Now it returns (61) "Unrecognized content
encoding type...".

There's a specific workaround, already released in curl 7.59.0 for the
problem we encountered after upgrading, namely that some servers use
"None" instead of "Identity" to indicate transparent / no encoding:

https://github.com/curl/curl/commit/f886cbfe9c3055999d8174b2eedc826d0d9a54f1

Please backport this patch to Ubuntu 18.04.

Discussion on the libcurl mailing list:
https://curl.haxx.se/mail/lib-2018-08/0192.html

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

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

Title:
  Backport Workaround for Content-Encoding: None

Status in curl package in Ubuntu:
  New

Bug description:
  With the upgrade to curl 7.58.0 in Ubuntu 18.04, the behavior of
  libcurl has changed when CURLOPT_ACCEPT_ENCODING is set to values
  other than NULL, and an unknown encoding is used by the server.
  Previously, curl would decode "gzip" and "deflate" (and now "br") and
  quietly pass any other, unknown encoding. Now it returns (61)
  "Unrecognized content encoding type...".

  There's a specific workaround, already released in curl 7.59.0 for the
  problem we encountered after upgrading, namely that some servers use
  "None" instead of "Identity" to indicate transparent / no encoding:

  https://github.com/curl/curl/commit/f886cbfe9c3055999d8174b2eedc826d0d9a54f1

  Please backport this patch to Ubuntu 18.04.

  Discussion on the libcurl mailing list:
  https://curl.haxx.se/mail/lib-2018-08/0192.html

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

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

[Touch-packages] [Bug 779130] Re: debconf refuses to die

2018-08-22 Thread Phillip Susi

Wow... 7 years and no response.

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

Title:
  debconf refuses to die

Status in debconf package in Ubuntu:
  New

Bug description:
  Binary package hint: debconf

  Sometimes I go to install mdadm on the livecd and forget to add --no-
  install-recommends so it tries to pull in postfix.  The debconf for
  postfix comes up and I realize my mistake and want to abort, but
  debconf ignores ctrl-c as well as ctrl-z, and even closing the
  terminal window does not kill it, so it holds the apt lock open and
  needs manually killed.

  Trying to reproduce the behavior with dpkg-reconfigure it still
  ignores ctrl-c and ctrl-z, but does die when closing the terminal
  window.

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

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

[Touch-packages] [Bug 1784218] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128

2018-08-22 Thread Phillip Susi

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

** This bug has been marked a duplicate of bug 1780913
   package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade: installed 
grub-efi-amd64 package post-installation script subprocess returned error exit 
status 128

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 128

Status in debconf package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New

Bug description:
  I was booting into Ubuntu, using the default option in grub, and was
  able to enter my password in the login screen, but the displays
  started flickering a lot, and there were a lot of repeated text
  messages (it switched into text mode).  I finally did a hard reset and
  tried booting into ubuntu - generic which seemed to work.  There was a
  prompt from apt to update, so I did, and then I got this error
  message.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.2
  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
  Date: Sun Jul 29 06:00:14 2018
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2017-11-11 (259 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=a68c1ee5-ce8a-4eed-b95f-7625f3118746 ro quiet splash vt.handoff=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.3
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 128
  UpgradeStatus: Upgraded to bionic on 2018-06-23 (35 days ago)

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

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

[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2018-08-22 Thread Curtis Gedak

Daniel, the KDE menu bar colour problem I experienced and noted in bug
#1780664 also went away when I upgraded to the new xorg-server.

I had to reboot and upgrade all my packages twice in order to get the
latest.  You might try checking to ensure that you have all the latest
packages.

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

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

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

[Touch-packages] [Bug 1786629] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1

2018-08-22 Thread Phillip Susi

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

** This bug has been marked a duplicate of bug 1780913
   package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade: installed 
grub-efi-amd64 package post-installation script subprocess returned error exit 
status 128

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 1

Status in debconf package in Ubuntu:
  New

Bug description:
  while upgrading to Ubantu 18.04 version pc hanged and it did not orked
  even after leaving for hours

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.2
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug 11 22:33:39 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-04-30 (103 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed 
root=UUID=51e2afee-e9ee-4527-adf4-853e7c5827d5 ro acpi_rev_override quiet 
splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (0 days ago)

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

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

[Touch-packages] [Bug 1788188] Re: transient systemd ordering cycle in boot with overlayroot

2018-08-22 Thread Scott Moser

I pushed a branch up to
 
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/bug/1788188-debug
that Christian and I are trying to get some additional debug information out of 
a failure.

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

Title:
  transient systemd ordering cycle in boot with overlayroot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  open-iscsi test utilizes overlayroot to boot a cloud-image with root
  filesystem on a read-only iscsi server.

  The /etc/fstab file in the image looks like this:
    LABEL=cloudimg-rootfs   /ext4   defaults0 0
    #LABEL=UEFI /boot/efi   vfatdefaults0 0

  when init takes over from the initramfs, we have

    /proc/cmdline:
  nomodeset iscsi_initiator=maas-enlist
  iscsi_target_name=tgt-boot-test-2abbnj iscsi_target_ip=10.0.12.2
  iscsi_target_port=3260 iscsi_initiator=maas-enlist
  ip=maas-enlist:BOOTIF ro net.ifnames=0 BOOTIF_DEFAULT=eth0
  
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1
  overlayroot=tmpfs console=ttyS0
  ds=nocloud-net;seedfrom=http://10.0.12.2:32600/ init=/bin/bash

    /etc/fstab:
  # cat /etc/fstab
  #
  #  This fstab is in an overlay. The real one can be found at
  #  /media/root-ro/etc/fstab
  #  The original entry for '/' and other mounts have been updated to be 
placed
  #  under /media/root-ro.
  #  To permanently modify this (or any other file), you should change-root 
into
  #  a writable view of the underlying filesystem using:
  #  sudo overlayroot-chroot
  #
  #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
  /media/root-ro/ / overlay 
lowerdir=/media/root-ro/,upperdir=/media/root-rw/over0
  #LABEL=UEFI /boot/efi vfat defaults 0 0

   /root/root-ro/etc/fstab:
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  #LABEL=UEFI /boot/efi   vfatdefaults0 0

   /proc/mounts:
     sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
     proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
     udev /dev devtmpfs 
rw,nosuid,relatime,size=233748k,nr_inodes=58437,mode=755 0 0
     devpts /dev/pts devpts 
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
     tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=49288k,mode=755 0 0
     /dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 
/media/root-ro ext4 ro,relatime 0 0
     tmpfs-root /media/root-rw tmpfs rw,relatime 0 0
     overlayroot / overlay 
ro,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 0 0

   /proc/1/mountinfo:
     21 28 0:20 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw
     22 28 0:4 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
     23 28 0:6 / /dev rw,nosuid,relatime - devtmpfs udev 
rw,size=233748k,nr_inodes=58437,mode=755
     24 23 0:21 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
     25 28 0:22 / /run rw,nosuid,noexec,relatime - tmpfs tmpfs 
rw,size=49288k,mode=755
     26 28 8:1 / /media/root-ro ro,relatime - ext4 
/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-2abbnj-lun-1-part1 ro
     27 28 0:23 / /media/root-rw rw,relatime - tmpfs tmpfs-root rw
     28 0 0:24 / / ro,relatime - overlay overlayroot 
ro,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_

  overlayroot's scripts/init-bottom/overlayroot script [1] inherits a
  read-only mount of block device on mount point '$ROOTMNT'
  (ROOTMNT=/root). In order to set up the overlayroot, it does the
  following:

   mkdir /media/root-ro /media/root-rw # in the initramfs
   mount -t tmpfs tmpfs-root /media/root-rw
   mkdir /media/root-rw/overlay-workdir/_
   mount --move $ROOTMNT /media/root-ro
   mount -t overlay -o 
lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 overlayroot /root
   mkdir $ROOTMNT/media/root-ro
   mkdir $ROOTMNT/media/root-rw
   mount --move /media/root-ro "${ROOTMNT}/media/root-ro"
   mount --move /media/root-rw "${ROOTMNT}/media/root-rw"

   # then, if 'ro' on the command line, it mounts /root read-only.
   mount -o remount,ro $ROOTMNT

  The script then exits, as ROOTMNT is now set up with a read-only mount
  of the overlayroot.  All the mounts it has done have been moved
  under ROOTMNT.

  On failure systemd reports:
     [  104.098833] systemd[1]: media-root\x2dro.mount: Found ordering cycle on 
-.mount/start
     [  104.109897] systemd[1]: media-root\x2dro.mount: Found dependency on 
media-root\x2dro.mount/start
     [  104.121386] systemd[1]: media-root\x2dro.mount: Unable to break cycle 
starting with media-root\x2dro.mount/start
     [

[Touch-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2018-08-22 Thread Theo Linkspfeifer

Julian, thanks for the detailed comment.

I assume that the only way to somewhat work around this problem is to
change the recommendation orders:

lightdm: recommend lightdm-gtk-greeter | unity-greeter | ...
xfce4-session: recommend light-locker | xscreensaver

This may cause trouble and unexpected behavior for non Xubuntu users
though.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1783571] Re: Set Yaru as default

2018-08-22 Thread Khurshid Alam

Unity Bug (MP attached) bug #1787572

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

Title:
  Set Yaru as default

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-sounds package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Set Yaru as default ubuntu 18.10 theme.

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

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

[Touch-packages] [Bug 993292] Re: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all

2018-08-22 Thread madbiologist

** No longer affects: poppler

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

Title:
  pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs
  them all

Status in poppler package in Ubuntu:
  New

Bug description:
  pdftotext -htmlmeta does miss metadata from PDF catalog. pdfinfo does
  output all values known:

  e.g. a pdfinfo output:

  Title:  Titel
  Author: Word
  Creator:WordToPDF 2.4 build 127
  Producer:   AFPL Ghostscript 8.54
  CreationDate:   Fri Jul  2 09:14:02 2007
  ModDate:Fri Jul  2 09:14:02 2007
  Tagged: no
  Pages:  6
  Encrypted:  no
  Page size:  595 x 842 pts (A4)
  File size:  104664 bytes
  Optimized:  no
  PDF version:1.3

  in contrast the meta section of the pdftotext -htmlmeta output:

  
  Titel
  
  
  
  
  

  
  Does not match and miss some meta data.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: poppler-utils 0.16.7-2ubuntu2
  Uname: Linux 3.3.3-030303-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed May  2 15:44:06 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac 
(20110427.1)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: poppler
  UpgradeStatus: Upgraded to oneiric on 2012-02-16 (76 days ago)

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

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

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

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

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

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

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

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

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

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

[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

2018-08-22 Thread Jeff Powell

That fix is great, but not for those going through a new install of
18.04. I had to let the entire installation process finish before I
could do anything about those messages at all, and their are dozens of
them that go by. Given this is a new problem in this theme in 18.04 (at
least as far as I know) and was definitely not present in 16.04, the
issue should be addressed to avoid errors during installation of (or
upgrade to) 18.04. Your fix can't be made until one of those is done.

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

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

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

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

[Touch-packages] [Bug 993292] Re: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all

2018-08-22 Thread madbiologist

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

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

Title:
  pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs
  them all

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  New

Bug description:
  pdftotext -htmlmeta does miss metadata from PDF catalog. pdfinfo does
  output all values known:

  e.g. a pdfinfo output:

  Title:  Titel
  Author: Word
  Creator:WordToPDF 2.4 build 127
  Producer:   AFPL Ghostscript 8.54
  CreationDate:   Fri Jul  2 09:14:02 2007
  ModDate:Fri Jul  2 09:14:02 2007
  Tagged: no
  Pages:  6
  Encrypted:  no
  Page size:  595 x 842 pts (A4)
  File size:  104664 bytes
  Optimized:  no
  PDF version:1.3

  in contrast the meta section of the pdftotext -htmlmeta output:

  
  Titel
  
  
  
  
  

  
  Does not match and miss some meta data.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: poppler-utils 0.16.7-2ubuntu2
  Uname: Linux 3.3.3-030303-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed May  2 15:44:06 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac 
(20110427.1)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: poppler
  UpgradeStatus: Upgraded to oneiric on 2012-02-16 (76 days ago)

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

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

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

Merci pour la mise à jour, Ymaigret. Je vais fermer le ticket maintenant.
:)
G

Closed per reporter's feedback.

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

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

Status in cups package in Ubuntu:
  Incomplete

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

  Merci

  Maigret Yvan

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

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

[Touch-packages] [Bug 1563594] Re: epson printer begins printing but the ubuntu says "stopped"

Thanks for the update, Mike. I will close the ticket now. 
:)
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/1563594

Title:
  epson printer begins printing but the ubuntu says "stopped"

Status in cups package in Ubuntu:
  Invalid

Bug description:
  2. laptop@laptop-HP-Pavilion:~$ lsmod | grep usb
  usblp  24576  0 
  usb_storage69632  1 uas
  usbhid 53248  0 
  hid   110592  3 hid_generic,usbhid

  3. laptop@laptop-HP-Pavilion:~$ tail -f /var/log/syslog
  Mar 29 19:24:28 laptop-HP-Pavilion kernel: [ 1570.910012] usblp1: removed
  Mar 29 19:24:28 laptop-HP-Pavilion kernel: [ 1570.927392] usblp 1-5:1.1: 
usblp1: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
  Mar 29 19:31:17 laptop-HP-Pavilion kernel: [ 1979.855077] usb 1-5: USB 
disconnect, device number 5
  Mar 29 19:31:17 laptop-HP-Pavilion kernel: [ 1979.860379] usblp1: removed
  Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: remove 
/devices/pci:00/:00:12.2/usb1/1-5
  Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: URI of detected 
printer: usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, 
normalized: epson et 2550 series serial 57424e4b3033373518 interface 1
  Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: URI of print 
queue: ecblp:/var/run/ecblp0, normalized: ecblp var run ecblp0
  Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: URI of print 
queue: usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, 
normalized: epson et 2550 series serial 57424e4b3033373518 interface 1
  Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: Queue 
ipp://localhost:631/printers/EPSON-ET-2550-Series has matching device URI
  Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/EPSON-ET-2550-Series as the corresponding device 
was unplugged or turned off

  4. Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.052099] usb 1-5: new 
high-speed USB device number 6 using ehci-pci
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192441] usb 1-5: New USB 
device found, idVendor=04b8, idProduct=1106
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192463] usb 1-5: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192475] usb 1-5: Product: 
EPSON ET-2550 Series
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192486] usb 1-5: 
Manufacturer: EPSON
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192495] usb 1-5: 
SerialNumber: 57424E4B3033373518
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.204576] usblp 1-5:1.1: 
usblp1: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.205595] usb-storage 
1-5:1.2: USB Mass Storage device detected
  Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.205919] scsi host10: 
usb-storage 1-5:1.2
  Mar 29 19:32:34 laptop-HP-Pavilion mtp-probe: checking bus 1, device 6: 
"/sys/devices/pci:00/:00:12.2/usb1/1-5"
  Mar 29 19:32:34 laptop-HP-Pavilion mtp-probe: bus: 1, device: 6 was not an 
MTP device
  Mar 29 19:32:34 laptop-HP-Pavilion udev-configure-printer: add 
/devices/pci:00/:00:12.2/usb1/1-5
  Mar 29 19:32:34 laptop-HP-Pavilion udev-configure-printer: device devpath is 
/devices/pci:00/:00:12.2/usb1/1-5
  Mar 29 19:32:34 laptop-HP-Pavilion udev-configure-printer: MFG:EPSON 
MDL:ET-2550 Series SERN:- serial:57424E4B3033373518
  Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.207085] scsi 10:0:0:0: 
Direct-Access EPSONStorage  1.00 PQ: 0 ANSI: 2
  Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.207708] sd 10:0:0:0: 
Attached scsi generic sg2 type 0
  Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.221908] sd 10:0:0:0: [sdb] 
Attached SCSI removable disk
  Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.274797] usblp1: removed
  Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.286627] usblp 1-5:1.1: 
usblp1: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
  Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI contains USB 
serial number
  Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI match: 
usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1
  Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI of detected 
printer: usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, 
normalized: epson et 2550 series serial 57424e4b3033373518 interface 1
  Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI of print 
queue: ecblp:/var/run/ecblp0, normalized: ecblp var run ecblp0
  Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI of

[Touch-packages] [Bug 1565982] Re: MakeModel gets erased from printers.conf from time to time

Thanks for the update, Gabriel. I will close the ticket now.
:)
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/1565982

Title:
  MakeModel gets erased from printers.conf from time to   time

Status in cups package in Ubuntu:
  Invalid

Bug description:
  
  Using printers.conf from an ansible module for fact collection, I noticed 
that a printer's MakeModel randomly disappears from printers.conf.

  The bug has already been fixed upstream and it's easy to backport:

  https://www.cups.org/pipermail/cups/2014-December/026601.html

  Attached is the same patch from the link, applied to the current
  sources in trusty (1.7.2-0ubuntu1.7).

  $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  $ apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.7
Candidate: 1.7.2-0ubuntu1.7
Version table:
   *** 1.7.2-0ubuntu1.7 0
  500 http://ar.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Apr  4 16:52:50 2016
  Lpstat:
   device for q_other: socket://q_other
   device for q_other2: socket://q_other2
   device for q_other3: socket://q_other3
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Papersize: a4
  PpdFiles:
   q_other2: Generic PCL 3 Printer Foomatic/pcl3 (recommended)
   q_other: Generic PCL 3 Printer Foomatic/pcl3 (recommended)
   q_other3: Generic PCL 3 Printer Foomatic/pcl3 (recommended)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/xvda2 ro elevator=noop root=/dev/xvda1 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1788398] [NEW] xserver falls back to software rendering (Onboard AST GPU not used)

2018-08-22 Thread Hendrik

Public bug reported:

This is a workstation with AST2500 onboard GPU. It should be used to do
the graphics rendering, while the NVIDIA cards are for HPC purposes.
Nvidia driver is installed with --no-opengl-files option.

libegl-mesa0 package did not solve the issue as described in earlier bug
reports on this topic.

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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..18.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:18:00.0'
.proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:3b:00.0'
.proc.driver.nvidia.gpus..86.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:86:00.0'
.proc.driver.nvidia.gpus..af.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:af:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.44  Wed Jul 11 16:51:49 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CompositorRunning: None
Date: Wed Aug 22 14:28:05 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
InstallationDate: Installed on 2018-08-16 (6 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Supermicro SYS-7049GP-TRT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b9187a62-ace4-4992-aef4-eb6c731ec1be ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X11DPG-QT
dmi.board.vendor: Supermicro
dmi.board.version: 1.02
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd11/29/2017:svnSupermicro:pnSYS-7049GP-TRT:pvr0123456789:rvnSupermicro:rnX11DPG-QT:rvr1.02:cvnSupermicro:ct1:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: SYS-7049GP-TRT
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
nvidia-settings:
 ERROR: Unable to load info from any available system
 
 
 ERROR: Unable to load info from any available system
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 possible-manual-nvidia-install resolution 
software-rendering ubuntu xserver

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

Title:
  xserver falls back to software rendering (Onboard AST GPU not used)

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a workstation with AST2500 onboard GPU. It should be used to
  do the graphics rendering, while the NVIDIA cards are for HPC
  purposes. Nvidia driver is installed with --no-opengl-files option.

  libegl-mesa0 package did not solve the issue as described in earlier
  bug reports on this topic.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..18.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:18:00.0'
  .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:3b:00.0'
  .proc.driver.nvidia.gpus..86.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:86:00.0'
  .proc.driver.nvidia.gpus..af.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:af:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.44  Wed Jul 11 16:51:49 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7.3

[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.26

2018-08-22 Thread Sebastien Bacher

The update is still in Debian/experimental and require a transition
https://release.debian.org/transitions/html/auto-exiv2.html
Unsure if it's worth trying to do in Ubuntu before Debian though

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

Title:
  Update to exiv2 version 0.26

Status in exiv2 package in Ubuntu:
  Triaged

Bug description:
  0.26 was released in April

  http://www.exiv2.org/whatsnew.html

  "This release contains a large collection of new features, new lenses
  and bugfixes across all areas of Exiv2. "

  Presumably debian stretch freeze interfered with a prompter update

  Currently in debian exp here:

  https://packages.debian.org/experimental/exiv2

  I was hoping to to get a new feature release of the very popular
  Digikam (5.7.0) into artful under a FFE, but that has bumped the
  minimum exiv2 build depend from 0.25 -> 0.26.

  If due to rdeps etc an update in artful turns out not to be possible,
  I would like to target this for early in 18.04 LTS cycle.

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2018-08-22 Thread Alexander Adam

This issue still appears on Ubuntu 18.04.

The variant "options snd-hda-intel single_cmd=1 probe_mask=1 model=dell-
headset-multi" doesn't work and the Pin override with hdajackretask
doesn't work neither.

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1513448] Re: DB Update failed, database locked

2018-08-22 Thread Julian Andres Klode

AFAIUI, that's apt-xapian-index

** Package changed: apt (Ubuntu) => apt-xapian-index (Ubuntu)

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

Title:
  DB Update failed, database locked

Status in apt-xapian-index package in Ubuntu:
  New

Bug description:
  Every day at around 0630 GMT I get output from the daily cron job:

  ```
  Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  ```

  Reporting:

  ```
  /etc/cron.daily/apt:
  DB Update failed, database locked
  ```

  I have unattended-upgrades installed and set up if that is of any
  relevance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.8
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Thu Nov  5 11:56:40 2015
  InstallationDate: Installed on 2014-11-28 (341 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1639815] Re: apt list output format

2018-08-22 Thread Donjan Rodic

Thanks for your clarification.
Not to draw this out, but to briefly address your points:

* can be field 2 without any drawback when passing it on
* 'apt list' produces search output preferable to 'apt search' (anecdotal and 
ymmv: both users I've discussed this with agree)
* could have been a chance to clean up a rarely used part of the interface

apt still lacks the convenience of other tools: apt-cache, aptitude and
yum all sport more comfortable search.

It seems the decision is made and this report has run its course...
could you please hint about the chance of the apt dev team accepting
design changing patches?

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

Title:
  apt list output format

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  I'm trying to get used to the new 'apt' utility and have three
  wishlist items (don't want to clutter the tracker with multiple
  feature requests) in descending priority:

  1. apt list firefox
  In the output, can we please have a space after the package name, before the 
slash?
  A very convenient feature of apt-cache/aptitude is to search for a package, 
then double click + middle click the name of a result to speedily select it and 
paste it into the current prompt (which is prepared with e.g. an install, show 
or depends command).
  'apt list' appends '/repo,XXX' (where XXX is most often garbage... ehm, I 
mean strings like 'now' or again 'other_repo,now') right after the package 
name, which makes the double click select more than just a package name.
  E.g. 'apt policy firefox/yakkety-updates' fails.
  This would also be more convenient for awk scripts (despite the stable 
interface warning).

  2. apt list fox
  Can we please have substring matching by default (or a storable user pref) 
for 'apt list'? 
  'apt search' is _way_ too noisy (the three line output per package instead of 
one line is just clutter).
  But 'apt list' doesn't match like 'apt-cache search' (or aptitude). The 
alternative is defaulting to 'apt l **' and then filling in between the 
asterisks, or resorting to 'apt l|grep' as standard 'apt-cache search' 
replacement.
  I don't see the justification for the current exact searching in only the 
package names. And there's still 'apt search' for searching the description.

  3. apt sh
  A minor complaint: all current apt commands complete once they are tabbed 
when their string becomes unique, and append a space. Only 'apt show' in 16.10 
(as opposed to 16.04) does not due to the undocumented showsrc command. This 
often leads to 'apt showfirefox' after writing 'apt shfirefox', because 
it's inconsistent with the other commands.
  So, find another name for showsrc?

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

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

[Touch-packages] [Bug 1788400] [NEW] package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být přeinstalován.

2018-08-22 Thread Michal Janošík

Public bug reported:

Problem for update. I not install for update and not search update.
Error for Secure (8).

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libdca0:amd64 0.0.5-10
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: Sun Aug 19 21:09:24 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
ErrorMessage: balík je ve velmi nekonzistentním stavu - před pokusem o 
konfiguraci by měl by být přeinstalován.
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: libdca
Title: package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve 
velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být 
přeinstalován.
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve
  velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být
  přeinstalován.

Status in libdca package in Ubuntu:
  New

Bug description:
  Problem for update. I not install for update and not search update.
  Error for Secure (8).

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libdca0:amd64 0.0.5-10
  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: Sun Aug 19 21:09:24 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ErrorMessage: balík je ve velmi nekonzistentním stavu - před pokusem o 
konfiguraci by měl by být přeinstalován.
  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: libdca
  Title: package libdca0:amd64 0.0.5-10 failed to install/upgrade: balík je ve 
velmi nekonzistentním stavu - před pokusem o konfiguraci by měl by být 
přeinstalován.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1512785] Re: Apt request to remove compiz and others on update

2018-08-22 Thread Julian Andres Klode

You can tell apt what to do by adding additional package names to an
upgrade/install/dist-upgrade/remove command, suffixed by + to
keep/install or - to keep away/remove.

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

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

Title:
  Apt request to remove compiz and others on update

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Hi 
  I added manual willy repo and was proceed to upgrade to wily manualy.
  On synaptic when try to upgrade apt package on aditional changes  compiz , 
compiz-core was removed after upgrade i do not want this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apt 1.0.9.7ubuntu4.2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CurrentDesktop: MATE
  Date: Tue Nov  3 18:27:57 2015
  SourcePackage: apt
  UpgradeStatus: Upgraded to wily on 2015-11-02 (0 days ago)

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

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

[Touch-packages] [Bug 1788391] [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-22 Thread NickKnatterton

Public bug reported:

Error appered after Upgrade from 16.4 LTS to 18.4 LTS

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Aug 22 13:40:02 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2013-12-21 (1704 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.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-22 (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/1788391

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:
  Error appered after Upgrade from 16.4 LTS to 18.4 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Aug 22 13:40:02 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-12-21 (1704 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.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-22 (0 days ago)

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

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

[Touch-packages] [Bug 1639815] Re: apt list output format

2018-08-22 Thread Julian Andres Klode

No, just the output format as is makes more sense than the suggestions:

* pkg/release is valid syntax that can be passed to commands (even /now is 
valid)
* it's a list command, so it should not perform a search
* showsrc is a very old name, it's not going to change.

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

Title:
  apt list output format

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  I'm trying to get used to the new 'apt' utility and have three
  wishlist items (don't want to clutter the tracker with multiple
  feature requests) in descending priority:

  1. apt list firefox
  In the output, can we please have a space after the package name, before the 
slash?
  A very convenient feature of apt-cache/aptitude is to search for a package, 
then double click + middle click the name of a result to speedily select it and 
paste it into the current prompt (which is prepared with e.g. an install, show 
or depends command).
  'apt list' appends '/repo,XXX' (where XXX is most often garbage... ehm, I 
mean strings like 'now' or again 'other_repo,now') right after the package 
name, which makes the double click select more than just a package name.
  E.g. 'apt policy firefox/yakkety-updates' fails.
  This would also be more convenient for awk scripts (despite the stable 
interface warning).

  2. apt list fox
  Can we please have substring matching by default (or a storable user pref) 
for 'apt list'? 
  'apt search' is _way_ too noisy (the three line output per package instead of 
one line is just clutter).
  But 'apt list' doesn't match like 'apt-cache search' (or aptitude). The 
alternative is defaulting to 'apt l **' and then filling in between the 
asterisks, or resorting to 'apt l|grep' as standard 'apt-cache search' 
replacement.
  I don't see the justification for the current exact searching in only the 
package names. And there's still 'apt search' for searching the description.

  3. apt sh
  A minor complaint: all current apt commands complete once they are tabbed 
when their string becomes unique, and append a space. Only 'apt show' in 16.10 
(as opposed to 16.04) does not due to the undocumented showsrc command. This 
often leads to 'apt showfirefox' after writing 'apt shfirefox', because 
it's inconsistent with the other commands.
  So, find another name for showsrc?

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

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

[Touch-packages] [Bug 1782417] Re: package libperl5.26 5.26.2-6 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5