[Touch-packages] [Bug 1811248] Re: systemd--networkd mounts denied for lxc guest

2019-07-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  systemd--networkd mounts denied for lxc guest

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7
  Guest Arch Linux | systemd 240.0

  After having upgraded in the guest systemd from 239.370 to 240.0 the
  host's AA is exhibiting

  > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED"
  operation="mount" info="failed flags match" error=-13 profile="lxc-
  container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw,
  rslave"

  and the guest

  > systemd-networkd.service: Failed to set up mount namespacing: Permission 
denied
  > systemd-networkd.service: Failed at step NAMESPACE spawning 
/usr/lib/systemd/systemd-networkd: Permission denied

  According to lxc bug tracker https://github.com/lxc/lxc/issues/2778

  > While we'd like to allow such mounts we cannot do so until the
  apparmor_parser is fixed to handle them correctly.

  other cross references

  https://github.com/systemd/systemd/issues/11371
  https://bugs.archlinux.org/task/61313

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

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


[Touch-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services

2019-07-16 Thread Daniel van Vugt
Thanks for the bug report.

Please tell us what version of Ubuntu you are using. Then please report
the problem to the BlueZ developers at:

  https://bugzilla.kernel.org (Product: Drivers, Component: Bluetooth)

and then tell us the new bug ID.

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

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

Title:
  segfault when CCD are present in two different HOG services

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Hello everyone,

  We are currently developing a device that contains two HID services.
  That device, as it is right now, is properly functioning on Windows & Android.
  However, when pairing the device on Linux running bluez 5.50 we do get 
segfaults (see attached files).
  Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt 
services and 1 device information service.
  With trial and error, we managed to find that we wouldn't get any crash as 
long as only 1 HOG service was present.

  Here's the interesting part. The two HOG services are made as follows:
  - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / 
boot INPUT + OUTPUT / HID information / HID Control point
  - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID 
information / HID control point

  Looking at the write_ccc in the call stacks we wondered if the
  callbacks subscribing to notifications for the INPUT reports were
  causing this issue.

  We therefore changed the raw HID over gatt (and its report map) to
  remove the INPUT report and change it into 1 OUTPUT report (leading to
  2 OUTPUT reports): no crash.

  We therefore hypothesize that the segfault occurs when subscribing to
  notification on a second HOG service...

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

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


[Touch-packages] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

2019-07-16 Thread Daniel van Vugt
Oh, you said that downgrade was a workaround.

So in that case this sounds like a bug in libgl1-mesa-
dri_19.0.2-1ubuntu1.1~18.04.1_amd64.deb

** Tags added: regression-update

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

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

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

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

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Touch-packages] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)

2019-07-16 Thread Daniel van Vugt
Before we debug anything here, one of your packages is broken, which
might be relevant:

  libgl1-mesa-dri 18.0.0~rc5-1ubuntu1

It should be version 19. To fix this please run:

  sudo apt update
  sudo apt full-upgrade

If that doesn't fix it then download and install the missing package:

  https://launchpad.net/ubuntu/+archive/primary/+files/libgl1-mesa-
dri_19.0.2-1ubuntu1.1~18.04.1_amd64.deb

and reboot.

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

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

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

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

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
  session started crashing just after the login. In xorg logs, I see
  this:

  [15.338] (WW) modeset(0): Page flip failed: Invalid argument
  [15.338] (EE) modeset(0): present flip failed
  [15.397] (WW) modeset(0): Page flip failed: Invalid argument
  [15.397] (EE) modeset(0): present flip failed
  [15.418] (WW) modeset(0): Page flip failed: Invalid argument
  [15.419] (EE) modeset(0): present flip failed
  [15.440] (WW) modeset(0): Page flip failed: Invalid argument
  [15.440] (EE) modeset(0): present flip failed
  [15.460] (WW) modeset(0): Page flip failed: Invalid argument
  [15.460] (EE) modeset(0): present flip failed
  [15.975] (WW) modeset(0): Page flip failed: Invalid argument
  [15.976] (EE) modeset(0): present flip failed
  [16.039] (WW) modeset(0): Page flip failed: Invalid argument
  [16.040] (EE) modeset(0): present flip failed
  [16.064] (WW) modeset(0): Page flip failed: Invalid argument
  [16.064] (EE) modeset(0): present flip failed
  [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
  0:11(2): error: value of type vec4 cannot be assigned to variable of type 
error
  0:12(2): error: `color1' undeclared
  0:12(2): error: value of type vec4 cannot be assigned to variable of type 
error

  [16.096] Program source:
  #ifdef GL_ES
  precision mediump float;
  #endif
  #define ATLAS_DIM_INV 0.0009765625
  varying vec2 glyph_pos;
  uniform vec4 fg;
  uniform sampler2D atlas;
  void main() {
 vec4 mask = texture2D(atlas, glyph_pos);
 vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
  }
  [16.096] (EE)
  Fatal server error:
  [16.096] (EE) GLSL compile failure

  Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
  18.0.0~rc5-1ubuntu1 helps.

  Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

  On the host, the GPU is Intel Haswell:

  00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
  E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  [8086:0412] (rev 06)

  The CPU is Intel(R) Core(TM) i7-4770S CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 20:52:03 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  

[Touch-packages] [Bug 1836773] Re: .

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

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

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

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

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

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

Title:
  .

Status in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 16 11:02:21 2019
  DistUpgraded: 2018-09-19 03:54:26,681 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:110f]
  InstallationDate: Installed on 2017-06-13 (763 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Aspire E5-475
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic 
root=UUID=4c1137ae-751e-401f-b13c-f08f19f96990 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-19 (300 days ago)
  dmi.bios.date: 03/29/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: AntMan_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-475
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  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: Tue Sep 18 19:57:00 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1836756] Re: Xorg freeze

2019-07-16 Thread Daniel van Vugt
Next time the freeze happens, please:

1. Tell us if the mouse pointer still moves?

2. Reboot, log in again and run:

   journalctl -b-1 > prevboot.txt

   and send us the resulting file 'prevboot.txt'.


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

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

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  i have to hard reboot the system for ubuntu froze,so please fix the
  bug .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 19:42:53 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
  InstallationDate: Installed on 2019-04-01 (105 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2213
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 096C11405F00050660180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131

2019-07-16 Thread Steve Langasek
Fixed in -proposed:

(Reading database ... 21788 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.10_amd64.deb ...
Unpacking base-files (9.4ubuntu4.10) over (9.4ubuntu4.8) ...
Processing triggers for man-db (2.7.5-1) ...
Not building database; man-db/auto-update is not 'true'.
Setting up base-files (9.4ubuntu4.10) ...
Running in chroot, ignoring request.
/usr/sbin/policy-rc.d returned 101, not running 'start motd-news.service'
Running in chroot, ignoring request.
/usr/sbin/policy-rc.d returned 101, not running 'start motd-news.timer'

Marking this verification-done, and also closing this bug since it was a
proposed-only regression.

** Changed in: base-files (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

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

Title:
  9.4ubuntu4.9: Broken package because of missing "#" @
  /var/lib/dpkg/info/base-files.postinst +131

Status in base-files package in Ubuntu:
  Invalid
Status in base-files source package in Xenial:
  Fix Released

Bug description:
  Trying to install this on xenial results in:

  
  Setting up base-files (9.4ubuntu4.9) ...
  /var/lib/dpkg/info/base-files.postinst: 131: 
/var/lib/dpkg/info/base-files.postinst: Automatically: not found
  dpkg: error processing package base-files (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   base-files
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Because there is a missing comment "#" at the beginning of line 131 of 
/var/lib/dpkg/info/base-files.postinst, ie:

  Automatically added by dh_systemd_start
  ^-- # ?

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

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


[Touch-packages] [Bug 1836444] Re: Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main)

2019-07-16 Thread Mathew Hodson
** Changed in: qt4-x11 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main)

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Please merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable
  (main)

  I cannot work on this merge myself. I filed this bug as a reference.

  Explanation of the Ubuntu delta:
* Merge with Debian since qtchooser has versioned Breaks. (LP: #1584654)
* Add one more macro to qt4-x11 moc to fix failing to parse BOOST_JOIN.
* No-change rebuild for libpng soname change.
* Rebuild against libmysqlclient20.
* Merge with Debian; remaining changes:
  - Pass list-missing to dh_install instead of fail-missing, since we don't
install the QtWebkit headers
  - Make sure libqt4-opengl-dev depends on gles libs for armel and armhf
  - Do not package ibase/firebird and sqlite2 package
+ remove from debian/control
+ libqt4-sql doesn't recommend libqt4-sql-ibase and libqt4-sql-sqlite2
  - Also exclude webkit examples from dh_shlibdeps
  - Do not build libqt4-phonon, disable in debian/control
  - Add debian/Trolltech.conf and install it in libqtcore4.install
  - Build with -no-neon on armel and armhf
  - Build with -no-javascript-jit on arm64
  - Add patches:
+ kubuntu_10_ibus_input_method.diff
+ kubuntu_12_fix_stack_protector.diff
+ kubuntu_28_xi2.1.patch
+ kubuntu_30_translucent_drag_pixmap.diff
+ kubuntu_37_cups_settings.diff
+ kubuntu_39_fix_medium_font.diff
+ kubuntu_40_disable_neon.patch
+ kubuntu_43_no_meego_helper.patch
+ kubuntu_93_disable_overlay_scrollbars.diff
+ kubuntu_94_xinput_valuators_fix.diff
+ kubuntu_95_qt_disable_bounce.diff
+ kubuntu_97_a11y_qt_and_qml_backport.diff
+ kubuntu_98_a11y_fix_crash.diff
+ kubuntu_glib-honor-ExcludeSocketNotifiers-flag.diff
+ kubuntu_qclipboard_delay.diff
+ kubuntu_qclipboard_fix_recursive.diff
  - Drop powerpc_designer_gstabs.diff, it breaks powerpc
* Update symbols files.

  Changelog entries since current eoan version 4:4.8.7+dfsg-7ubuntu1:

  qt4-x11 (4:4.8.7+dfsg-18) unstable; urgency=medium

* Team upload.

[ Edward Betts ]
* debian/NEWS: Replace UNRELEASED with unstable.

[ Alexander Volkov ]
* Backport some vulnerability fixes from Qt 5 (closes: #923003).
  - CVE-2018-15518: double free or corruption in QXmlStreamReader.
  - CVE-2018-19869: Qt Svg crash when parsing malformed url reference.
  - CVE-2018-19870: NULL pointer dereference in QGifHandler.
  - CVE-2018-19871: QTgaFile CPU exhaustion.
  - CVE-2018-19872: crash when parsing a malformed PPM image.
  - CVE-2018-19873: QBmpHandler segfault on malformed BMP file.

   -- Dmitry Shachnev   Fri, 12 Apr 2019 23:10:28
  +0300

  qt4-x11 (4:4.8.7+dfsg-17) unstable; urgency=medium

* Add fix-build-icu59.patch from OpenSuse. Fixes build with icu59
 (Closes: #898542). Thanks John Paul Adrian Glaubitz for digging the
 patch!
* Put the source package in section oldlibs. We do not expect new
  developments with qt4-x11.
* Update Vcs-[Git Browser] to the new location in salsa.debian.org.

   -- Lisandro Damián Nicanor Pérez Meyer   Tue, 15
  May 2018 13:24:10 -0300

  qt4-x11 (4:4.8.7+dfsg-16) unstable; urgency=medium

* Update symbols files with buildds' logs.
* Add a patch by Manuel A. Fernandez Montecelo to provide riscv64 support
 (Closes: #897667).

   -- Lisandro Damián Nicanor Pérez Meyer   Fri, 04
  May 2018 22:53:17 -0300

  qt4-x11 (4:4.8.7+dfsg-15) unstable; urgency=medium

* Actually upload it to unstable.

   -- Lisandro Damián Nicanor Pérez Meyer   Wed, 18
  Apr 2018 17:45:31 -0300

  qt4-x11 (4:4.8.7+dfsg-14) experimental; urgency=medium

* Update symbols files with buildds' logs.
* Add NEWS.Debian to explicitely tell users of the OpenSSL 1.1 patch.

   -- Lisandro Damián Nicanor Pérez Meyer   Wed, 18
  Apr 2018 16:30:10 -0300

  qt4-x11 (4:4.8.7+dfsg-13) experimental; urgency=medium

* Add extra patch from Dmitry Eremin-Solenikov to make Qt4 work with
  OpenSSL 1.1 (Closes: #873275).
* Recommend default-libmysqlclient-dev instead of libmysqlclient-dev.

   -- Lisandro Damián Nicanor Pérez Meyer   Fri, 10
  Nov 2017 15:36:11 -0300

  qt4-x11 (4:4.8.7+dfsg-12) experimental; urgency=medium

* Add openssl_1.1.patch to let Qt4 use OpenSSL 1.1 (Closes: #828522).
  - Switch libssl-1.0-dev to libssl-dev to use OpenSSL 1.1.
* Update symbols files with current build log.

   -- Lisandro Damián Nicanor Pérez Meyer   Tue, 15
  Aug 2017 13:25:00 -0300

  qt4-x11 (4:4.8.7+dfsg-11) unstable; urgency=medium


[Touch-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic

2019-07-16 Thread Mathew Hodson
** Changed in: gconf (Ubuntu)
   Importance: Undecided => High

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

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

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

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


[Touch-packages] [Bug 1836809] [NEW] segfault when CCD are present in two different HOG services

2019-07-16 Thread Mathieu Stephan
Public bug reported:

Hello everyone,

We are currently developing a device that contains two HID services.
That device, as it is right now, is properly functioning on Windows & Android.
However, when pairing the device on Linux running bluez 5.50 we do get 
segfaults (see attached files).
Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt 
services and 1 device information service.
With trial and error, we managed to find that we wouldn't get any crash as long 
as only 1 HOG service was present.

Here's the interesting part. The two HOG services are made as follows:
- standard keyboard over gatt: protocole mode / report map / 1 INPUT report / 
boot INPUT + OUTPUT / HID information / HID Control point
- raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID 
information / HID control point

Looking at the write_ccc in the call stacks we wondered if the callbacks
subscribing to notifications for the INPUT reports were causing this
issue.

We therefore changed the raw HID over gatt (and its report map) to
remove the INPUT report and change it into 1 OUTPUT report (leading to 2
OUTPUT reports): no crash.

We therefore hypothesize that the segfault occurs when subscribing to
notification on a second HOG service...

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

** Attachment added: "callstacks.txt"
   
https://bugs.launchpad.net/bugs/1836809/+attachment/5277531/+files/callstacks.txt

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

Title:
  segfault when CCD are present in two different HOG services

Status in bluez package in Ubuntu:
  New

Bug description:
  Hello everyone,

  We are currently developing a device that contains two HID services.
  That device, as it is right now, is properly functioning on Windows & Android.
  However, when pairing the device on Linux running bluez 5.50 we do get 
segfaults (see attached files).
  Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt 
services and 1 device information service.
  With trial and error, we managed to find that we wouldn't get any crash as 
long as only 1 HOG service was present.

  Here's the interesting part. The two HOG services are made as follows:
  - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / 
boot INPUT + OUTPUT / HID information / HID Control point
  - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID 
information / HID control point

  Looking at the write_ccc in the call stacks we wondered if the
  callbacks subscribing to notifications for the INPUT reports were
  causing this issue.

  We therefore changed the raw HID over gatt (and its report map) to
  remove the INPUT report and change it into 1 OUTPUT report (leading to
  2 OUTPUT reports): no crash.

  We therefore hypothesize that the segfault occurs when subscribing to
  notification on a second HOG service...

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

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


[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2019-07-16 Thread Till Kamppeter
Lukasz, I do not see any problems with this package, neither on the

https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic

page nor on

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html

which are the regressions actually caused?

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  

[Touch-packages] [Bug 1836773] [NEW] .

2019-07-16 Thread mario munoz
Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jul 16 11:02:21 2019
DistUpgraded: 2018-09-19 03:54:26,681 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:110f]
InstallationDate: Installed on 2017-06-13 (763 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Acer Aspire E5-475
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic 
root=UUID=4c1137ae-751e-401f-b13c-f08f19f96990 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-19 (300 days ago)
dmi.bios.date: 03/29/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: AntMan_SK
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SKL
dmi.product.name: Aspire E5-475
dmi.product.version: V1.01
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
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: Tue Sep 18 19:57:00 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  .

Status in xorg package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul 16 11:02:21 2019
  DistUpgraded: 2018-09-19 03:54:26,681 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:110f]
  InstallationDate: Installed on 2017-06-13 (763 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Aspire E5-475
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic 
root=UUID=4c1137ae-751e-401f-b13c-f08f19f96990 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-19 (300 days ago)
  dmi.bios.date: 03/29/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: AntMan_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-475
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  

[Touch-packages] [Bug 1836772] [NEW] Xorg crash on 3d-enabled virgl (Haswell host)

2019-07-16 Thread Alexander E. Patrakov
Public bug reported:

I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see this:

[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type error

[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
   vec4 mask = texture2D(atlas, glyph_pos);
   vec4 source = fg;
  color0 = source * mask;
  color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure

Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.

Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.

On the host, the GPU is Intel Haswell:

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200
v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412]
(rev 06)

The CPU is Intel(R) Core(TM) i7-4770S CPU.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
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 crash ubuntu

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/bugs/1836772/+attachment/5277429/+files/Xorg.0.log.old

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

Title:
  Xorg crash on 3d-enabled virgl (Haswell host)

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running a KVM virtual machine with 3D acceleration (virgl). The
  host is Arch 

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

2019-07-16 Thread Douglas Silva
The solution is right here, so simple to apply. Why is this ignored? No
one else suspends their machines? Merge the necessary polkit rule,
please.

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

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


[Touch-packages] [Bug 1836722] Re: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

2019-07-16 Thread Jamie Strandboge
This looks to be a local system issue with python3-minimal being removed
and then the prerm scripts from various programs failing due to
debhelper scripts that the package use can't find the required binaries.

Removing python3.6-minimal (3.6.8-1~16.04.york1) ...
Unlinking and removing bytecode for runtime python3.6
Removing qml-module-io-thp-pyotherside:amd64 (1.4.0-2) ...
Removing ubuntu-minimal (1.361) ...
Removing ubuntu-system-service (0.3) ...
/var/lib/dpkg/info/ubuntu-system-service.prerm: 6: 
/var/lib/dpkg/info/ubuntu-system-service.prerm: py3clean: not found
dpkg: error processing package ubuntu-system-service (--remove):
 subprocess installed pre-removal script returned error exit status 127
/var/lib/dpkg/info/ubuntu-system-service.postinst: 6: 
/var/lib/dpkg/info/ubuntu-system-service.postinst: py3compile: not found
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 127
Removing ufw (0.35-0ubuntu2) ...
Skip stopping firewall: ufw (not enabled)
/var/lib/dpkg/info/ufw.prerm: 15: /var/lib/dpkg/info/ufw.prerm: py3clean: not 
found
dpkg: error processing package ufw (--remove):
 subprocess installed pre-removal script returned error exit status 127

I'm not sure how you got into this state (I see a 3.6.8-1~16.04.york1
python3.6-minimal package being removed-- it is possible the ppa in
question has packages that don't have their dependencies setup). I
suggest installing 'python3-minimal' then running 'sudo apt-get -f
install' and then remove any packages you aren't interested in.

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

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

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Not able to use system. pip crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Tue Jul 16 14:33:11 2019
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2019-07-10 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-07-16 Thread Balaji Duraisamy
Public bug reported:

i have to hard reboot the system for ubuntu froze,so please fix the bug
.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 19:42:53 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
InstallationDate: Installed on 2019-04-01 (105 days ago)
InstallationMedia:
 
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
 Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.23
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2213
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.35
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 096C11405F00050660180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
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 freeze 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/1836756

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  i have to hard reboot the system for ubuntu froze,so please fix the
  bug .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 19:42:53 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
  InstallationDate: Installed on 2019-04-01 (105 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash 

[Touch-packages] [Bug 1658836] Re: /usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

2019-07-16 Thread Dmitry Shachnev
https://codereview.qt-project.org/c/qt/qtbase/+/188320 says that the fix
is included in Qt 5.9.0 and later versions (see the “Included in”
button).

As the latest Ubuntu LTS release has Qt 5.9.5, I think we can close
this.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  
/usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

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

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

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

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


[Touch-packages] [Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

2019-07-16 Thread Dmitry Shachnev
Hi Dima!

This looks like https://bugreports.qt.io/browse/QTBUG-58508 to me.
According to that bug, it is fixed in Qt 5.11, however the change is too
large to backport to 5.9.

Exporting QML_DISABLE_DISK_CACHE=1 should help as a workaround — can you
try that?

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

Bug description:
  The console output:

  $ twinkle 
  QApplication: invalid style override passed, ignoring it.
  Language name: "en"
  mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
  *** stack smashing detected ***:  terminated
  Aborted (core dumped)
  $

  I've attached a strace output file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: twinkle 1:1.10.1+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 16 15:29:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-11 (309 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: twinkle
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1836738] [NEW] avahi-daemon takes 100% cpu over many minutes

2019-07-16 Thread Angela
Public bug reported:

Rarely the processor locks onto avahi-deamon processes and doesn't
release. This can happen when the PC is not being used. Only the high
fan speed alerts me. I cannot repeat it will but it repeats itself
naturally.

I find in syslog lots of withdrawing and then registering IPv6 address
records

ul 16 13:47:01 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for 2a02:8010:9014:1:a165:d30c:a46d:fb67 on wlp2s0.*.
Jul 16 13:47:01 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fd00::1:a165:d30c:a46d:fb67 on wlp2s0.*.
Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address record 
for 2a02:8010:9014:1:f61:d516:83f5:6f4b on wlp2s0.
Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address record 
for fdc0:9f09:7835:1:befa:c254:e399:600 on wlp2s0.
Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address record 
for fd00::1:4a28:976d:1601:df6b on wlp2s0.
Jul 16 13:49:14 angela-XPS13-9333 kernel: [21448.679978] IPv6: 
ipv6_create_tempaddr: retry temporary address regeneration
Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fd00::1:4a28:976d:1601:df6b on wlp2s0.*.
Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for 2a02:8010:9014:1:f61:d516:83f5:6f4b on wlp2s0.*.
Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fdc0:9f09:7835:1:befa:c254:e399:600 on wlp2s0.*.
Jul 16 13:49:16 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fdc0:9f09:7835:1:a5b6:b0b2:d3ab:cf92 on wlp2s0.*.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: avahi-daemon 0.7-4ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 13:36:05 2019
InstallationDate: Installed on 2019-05-08 (68 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Taken at time of 100% CPU use"
   
https://bugs.launchpad.net/bugs/1836738/+attachment/5277391/+files/avahi_bug.zip

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

Title:
  avahi-daemon takes 100% cpu over many minutes

Status in avahi package in Ubuntu:
  New

Bug description:
  Rarely the processor locks onto avahi-deamon processes and doesn't
  release. This can happen when the PC is not being used. Only the high
  fan speed alerts me. I cannot repeat it will but it repeats itself
  naturally.

  I find in syslog lots of withdrawing and then registering IPv6 address
  records

  ul 16 13:47:01 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for 2a02:8010:9014:1:a165:d30c:a46d:fb67 on wlp2s0.*.
  Jul 16 13:47:01 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fd00::1:a165:d30c:a46d:fb67 on wlp2s0.*.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address 
record for 2a02:8010:9014:1:f61:d516:83f5:6f4b on wlp2s0.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address 
record for fdc0:9f09:7835:1:befa:c254:e399:600 on wlp2s0.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Withdrawing address 
record for fd00::1:4a28:976d:1601:df6b on wlp2s0.
  Jul 16 13:49:14 angela-XPS13-9333 kernel: [21448.679978] IPv6: 
ipv6_create_tempaddr: retry temporary address regeneration
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fd00::1:4a28:976d:1601:df6b on wlp2s0.*.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for 2a02:8010:9014:1:f61:d516:83f5:6f4b on wlp2s0.*.
  Jul 16 13:49:14 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fdc0:9f09:7835:1:befa:c254:e399:600 on wlp2s0.*.
  Jul 16 13:49:16 angela-XPS13-9333 avahi-daemon[856]: Registering new address 
record for fdc0:9f09:7835:1:a5b6:b0b2:d3ab:cf92 on wlp2s0.*.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: avahi-daemon 0.7-4ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 13:36:05 2019
  InstallationDate: Installed on 2019-05-08 (68 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Touch-packages] [Bug 1069285] Re: Unnecessary horizontal scrolling in Additional Drivers page

2019-07-16 Thread Matthew Paul Thomas
Spec updated
:
“The listbox should not scroll horizontally; each radio button label
should wrap to multiple lines if necessary.”

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Unnecessary horizontal scrolling in Additional Drivers page

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The Additional Drivers page generally has a short list containing
  options with long labels, such as "Using X.Org X server - AMD/ATI
  display driver wrapper from xserver-xorg-video-ati (open source,
  tested)". Some of these labels are very similar for the first 50
  characters or so.

  Many labels go well beyond the default width for the dialog, resulting
  in a horizontal scrollbar. Meanwhile, there is all sorts of vertical
  space that could easily accommodate the information. It would be
  easier to work with this dialog if the labels were word wrapped,
  instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1069285/+subscriptions

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


[Touch-packages] [Bug 1836722] Re: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

2019-07-16 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 ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1836722

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in ufw package in Ubuntu:
  New

Bug description:
  Not able to use system. pip crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Tue Jul 16 14:33:11 2019
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2019-07-10 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

2019-07-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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


[Touch-packages] [Bug 1836721] [NEW] Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

2019-07-16 Thread Roman Shipovskij
Public bug reported:

Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04.

~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

~# uname -a
Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

~# lspci -nn -k -d ::0300
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

mesa: 19.0.2-1ubuntu1.1~18.04.1

X crashes with message:
 i965: Failed to submit batchbuffer: Invalid argument

The same issue was after updating mesa from 18.0 to 18.2:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

I have tried the same fix and it works for me:
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic i386 regression-update

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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


[Touch-packages] [Bug 1836722] [NEW] package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

2019-07-16 Thread Sayali Deokate
Public bug reported:

Not able to use system. pip crashed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ufw 0.35-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Tue Jul 16 14:33:11 2019
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
InstallationDate: Installed on 2019-07-10 (5 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.32
SourcePackage: ufw
Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in ufw package in Ubuntu:
  New

Bug description:
  Not able to use system. pip crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Tue Jul 16 14:33:11 2019
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2019-07-10 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

2019-07-16 Thread Dima
The previous gdb was with qt 5.9.5+dfsg-0ubuntu2.1 from ubuntu-security.
This one is with qt 5.9.5+dfsg-0ubuntu2.3 from proposed updates.

** Attachment added: "gdb-qt-proposed(5.9.5+dfsg-0ubuntu2.3).txt"
   
https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+attachment/5277334/+files/gdb-qt-proposed%285.9.5+dfsg-0ubuntu2.3%29.txt

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

Bug description:
  The console output:

  $ twinkle 
  QApplication: invalid style override passed, ignoring it.
  Language name: "en"
  mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
  *** stack smashing detected ***:  terminated
  Aborted (core dumped)
  $

  I've attached a strace output file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: twinkle 1:1.10.1+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 16 15:29:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-11 (309 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: twinkle
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

2019-07-16 Thread Dima
Thank YOU, tremendous super cosmo-heroes.

** Attachment added: "gdb-with-qt-dbgsymbols.txt"
   
https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+attachment/5277333/+files/gdb-with-qt-dbgsymbols.txt

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

Bug description:
  The console output:

  $ twinkle 
  QApplication: invalid style override passed, ignoring it.
  Language name: "en"
  mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
  *** stack smashing detected ***:  terminated
  Aborted (core dumped)
  $

  I've attached a strace output file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: twinkle 1:1.10.1+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr 16 15:29:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-11 (309 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: twinkle
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-07-16 Thread Daniel van Vugt
I'll dig into this tomorrow.

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Other Info]

  SRU sponsorship tracked in bug 1556439.

  [Original Report]

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-07-16 Thread Daniel van Vugt
Actually, that looks impossible. Maybe someone has built their own with
the same version?

** Tags removed: verification-failed-bionic
** Tags added: verification-needed-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/1663528

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Other Info]

  SRU sponsorship tracked in bug 1556439.

  [Original Report]

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se

2019-07-16 Thread Daniel van Vugt
There have been no reports of this crash in the proposed version:

https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month=1%3A11.1-1ubuntu7.3

But related bug 1663528 is another story.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1556439

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-07-16 Thread Daniel van Vugt
It appears there have been two occurrences of this crash even with the
proposed version:

https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month=1%3A11.1-1ubuntu7.3

** Tags removed: verification-needed-bionic
** Tags added: verification-failed-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/1663528

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Other Info]

  SRU sponsorship tracked in bug 1556439.

  [Original Report]

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-07-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  update-notifier doesn't respect "automatically check for updates:
  Never"

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Eoan:
  Confirmed

Bug description:
  This has been a long-standing problem with various ubuntu
  installations, and I'm sensing some reticence in doing anything about
  it. This attitude also seems to be purposeful to try to cajole updates
  on people who make bad choices due to confusion/fud/paranoia.

  apt install fails due to:

  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

  A great deal of networking is taking place despite setting automatic
  upgrades to "never". Cycling this doesn't seem to do anything. This
  action is hostile to programmers and the setting should be respected.

  Wisdom on threads is to let it update until it's out of updates, and
  then it supposedly respects the "never" flag, but the experience I'm
  having is much more non-deterministic. have been using 19.04 for weeks
  now and still get the background notifier using data and getting in
  the way of aptitude package installations. I prefer manual update &&
  upgrade once my code is ready to push.

  Is there another way around this or are people just living with it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions

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


[Touch-packages] [Bug 1836701] [NEW] ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory

2019-07-16 Thread xiaotong.t...@gmail.com
Public bug reported:

ipmitool failed in-band
#ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such 
file or directory

And it work out-band:
# ipmitool -H {theip} -I lanplus -U {user} -P {passwd} lan print
Set in Progress : Set Complete
Auth Type Support   : NONE MD2 MD5 PASSWORD
Auth Type Enable: Callback : MD2 MD5 PASSWORD
: User : MD2 MD5 PASSWORD
: Operator : MD2 MD5 PASSWORD
: Admin: MD2 MD5 PASSWORD
: OEM  : MD2 MD5 PASSWORD
IP Address Source   : DHCP Address
...

But the file exist:
# ls -al /dev/ipmi0
crw--- 1 root root 240, 0 Jul 16 13:55 /dev/ipmi0
# cat /proc/devices | grep ipmidev
240 ipmidev

packages that I installed:
# dpkg -l | grep ipmi
ii  freeipmi-common   1.4.11-1.1ubuntu4.1   
amd64GNU implementation of the IPMI protocol - common files
ii  ipmitool  1.8.18-5ubuntu0.1 
amd64utility for IPMI control with kernel driver or LAN interface 
(daemon)
ii  libfreeipmi16 1.4.11-1.1ubuntu4.1   
amd64GNU IPMI - libraries
ii  libopenipmi0  2.0.22-1.1ubuntu2.1   
amd64Intelligent Platform Management Interface - runtime
ii  openipmi  2.0.22-1.1ubuntu2.1   
amd64Intelligent Platform Management Interface (for servers)

the mods:
# lsmod| grep ipmi_
ipmi_devintf   20480  0
ipmi_poweroff  16384  0
ipmi_watchdog  28672  0
ipmi_ssif  32768  0
ipmi_si61440  0
ipmi_msghandler53248  6 
ipmi_devintf,ipmi_si,nvidia,ipmi_watchdog,ipmi_ssif,ipmi_poweroff

the kernel:
# uname -a
Linux A16969628514217 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

the ubuntu version:
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"

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

** Description changed:

  ipmitool failed in-band
  ipmitool lan print
  Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such 
file or directory
  
  And it work out-band:
  # ipmitool -H {theip} -I lanplus -U {user} -P {passwd} lan print
  Set in Progress : Set Complete
- Auth Type Support   : NONE MD2 MD5 PASSWORD 
- Auth Type Enable: Callback : MD2 MD5 PASSWORD 
- : User : MD2 MD5 PASSWORD 
- : Operator : MD2 MD5 PASSWORD 
- : Admin: MD2 MD5 PASSWORD 
- : OEM  : MD2 MD5 PASSWORD 
+ Auth Type Support   : NONE MD2 MD5 PASSWORD
+ Auth Type Enable: Callback : MD2 MD5 PASSWORD
+ : User : MD2 MD5 PASSWORD
+ : Operator : MD2 MD5 PASSWORD
+ : Admin: MD2 MD5 PASSWORD
+ : OEM  : MD2 MD5 PASSWORD
  IP Address Source   : DHCP Address
  ...
  
  packages that I installed:
  # dpkg -l | grep ipmi
  ii  freeipmi-common   1.4.11-1.1ubuntu4.1   
amd64GNU implementation of the IPMI protocol - common files
  ii  ipmitool  1.8.18-5ubuntu0.1 
amd64utility for IPMI control with kernel driver or LAN interface 
(daemon)
  ii  libfreeipmi16 1.4.11-1.1ubuntu4.1   
amd64GNU IPMI - libraries
  ii  libopenipmi0  2.0.22-1.1ubuntu2.1   
amd64Intelligent Platform Management Interface - runtime
  ii  openipmi  2.0.22-1.1ubuntu2.1   
amd64Intelligent Platform Management Interface (for servers)
  
  the mods:
  # lsmod| grep ipmi_
  ipmi_devintf   20480  0
  ipmi_poweroff  16384  0
  ipmi_watchdog  28672  0
  ipmi_ssif  32768  0
  ipmi_si61440  0
  ipmi_msghandler53248  6 
ipmi_devintf,ipmi_si,nvidia,ipmi_watchdog,ipmi_ssif,ipmi_poweroff
+ 
+ the kernel:
+ # uname -a
+ Linux A16969628514217 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
+ 
+ the ubuntu version:
+ # cat /etc/lsb-release 
+ DISTRIB_ID=Ubuntu
+ DISTRIB_RELEASE=18.04
+ DISTRIB_CODENAME=bionic
+ DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"

** Description changed:

  ipmitool failed in-band
  ipmitool lan print
  Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such 
file or directory
  
  And it work out-band:
  # ipmitool -H {theip} -I lanplus -U {user} -P {passwd} lan print
  Set in Progress : Set Complete
  Auth Type Support   : NONE MD2 MD5 PASSWORD
  Auth Type Enable   

[Touch-packages] [Bug 1658836] Re: /usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

2019-07-16 Thread Frédéric Brière
Reassigning to qtdeclarative-opensource-src; I'll let them confirm in
which version the fix was introduced.

** Package changed: twinkle (Ubuntu) => qtdeclarative-opensource-src
(Ubuntu)

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

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

Title:
  
/usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in twinkle package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1658836] [NEW] /usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer

2019-07-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

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

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial
-- 
/usr/bin/twinkle:11:QBasicAtomicOps:QBasicAtomicInteger:QtSharedPointer::ExternalRefCountData::getAndRef:QWeakPointer:QPointer
https://bugs.launchpad.net/bugs/1658836
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtdeclarative-opensource-src in Ubuntu.

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