[Touch-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Markward Kufleitner]

Still comes up just after logging in to cinnamon.

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

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

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1712639] Re: nfs-kernel-server doesn't wait on (luks) encrypted fs on startup

[Steve Langasek]

** Package changed: nfs-utils (Ubuntu) => systemd (Ubuntu)

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

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

Title:
  nfs-kernel-server doesn't wait on (luks) encrypted fs on startup

Status in systemd package in Ubuntu:
  New

Bug description:
  nfs-kernel-server fails on startup when the exported FS is on an
  encrypted partition that requires a password entry.

  Currently nfs-kernel-server must be restarted in order to export the
  FS.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nfs-kernel-server 1:1.3.4-2.1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Aug 23 20:31:02 2017
  InstallationDate: Installed on 2014-05-30 (1181 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: nfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1726555] Re: Use mainstream theme solution for gnome-terminal, drop patch

[Daniel van Vugt]

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  Use mainstream theme solution for gnome-terminal, drop patch

Status in Ubuntu theme:
  New
Status in gnome-terminal package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to-
  some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and
  Radiance themes' apps/gnome-terminal.css relies on this to get the
  desired look for the notebook widget.

  Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be
  necessary. It's just an additional burden to carry this patch, plus an
  unnecessary complication for those who wish to manually compile gnome-
  terminal for whatever reason.

  gnome-terminal.css should ideally be modified to use the CSS names
  provided by mainstream gnome-terminal, and once done, the gnome-
  terminal patch can be dropped.

  Upstream references:
  https://bugzilla.gnome.org/show_bug.cgi?id=765590
  https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6
  https://bugzilla.gnome.org/show_bug.cgi?id=788044

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

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

[Touch-packages] [Bug 1573693] Re: Microphone is not working

[Daniel van Vugt]

** Tags added: mic

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

Title:
  Microphone is not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Microphone is not working on ASUS X552L laptop.

  Just installed latest ubuntu version 16.04 LTS

  After installed Skype, tried a test call, sound was very low volume.
  Tried to adjust microphone volume with the slider, mic went dead for
  good, no sound at all. tried to reinstall alsa package

  apt-get remove --purge alsa-base pulseaudio

  and install it again, nothing works.

  Did not work on older ubuntu version either.

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  alsa-base:
Telepítve: 1.0.25+dfsg-0ubuntu5
Jelölt:1.0.25+dfsg-0ubuntu5
Verziótáblázat:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  pulseaudio:
Telepítve: 1:8.0-0ubuntu3
Jelölt:1:8.0-0ubuntu3
Verziótáblázat:
   *** 1:8.0-0ubuntu3 500
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irma   1425 F pulseaudio
   /dev/snd/pcmC1D0c:   irma   1425 F...m pulseaudio
   /dev/snd/controlC1:  irma   1425 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 22 18:17:49 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.509
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.509:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1712639] [NEW] nfs-kernel-server doesn't wait on (luks) encrypted fs on startup

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

nfs-kernel-server fails on startup when the exported FS is on an
encrypted partition that requires a password entry.

Currently nfs-kernel-server must be restarted in order to export the FS.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nfs-kernel-server 1:1.3.4-2.1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Aug 23 20:31:02 2017
InstallationDate: Installed on 2014-05-30 (1181 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: nfs-utils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful third-party-packages
-- 
nfs-kernel-server doesn't wait on (luks) encrypted fs on startup
https://bugs.launchpad.net/bugs/1712639
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1668445] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: подпроцесс
  установлен сценарий post-removal возвратил код ошибки 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  can't upgrade-distr from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   xubuntu-desktop: Purge
   ubuntu-desktop: Purge
   lightdm: Purge
  Architecture: amd64
  Date: Thu Feb 23 00:43:32 2017
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  InstallationDate: Installed on 2015-02-02 (754 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: lightdm
  Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 1
  UpgradeStatus: Upgraded to trusty on 2017-02-26 (0 days ago)

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

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

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

[Daniel C Aragao]

Public bug reported:

This problem occur: 
- when I input USB stick
- When I have click about system (more details of Ubuntu)
- Using normally, so open a video then system log off or freeze.

I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM login
screen.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Oct 24 00:44:02 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
InstallationDate: Installed on 2017-10-19 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P06RCX.075.160311.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KW3BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 370E4K
dmi.product.version: P06RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful freeze ubuntu wayland-session

** Attachment added: "System log"
   https://bugs.launchpad.net/bugs/1726682/+attachment/4990043/+files/Problems

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem occur: 
  - when I input USB stick
  - When I have click about system (more details of Ubuntu)
  - Using normally, so open a video then system log off or freeze.

  I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM
  login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 24 00:44:02 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: 

[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center

[David Gil]

I tried to address the user issue part using the virtual machine version
of Ubuntu 17.10. It is still the same.

** Attachment added: "vokoscreen-2017-10-24_11-42-07.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+attachment/4990035/+files/vokoscreen-2017-10-24_11-42-07.mkv

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

Title:
  pptp vpn cannot be easily connected in gnome network manager and gnome
  control center

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I tried to reactivate a VPN (for PPTP) several times again and again
  using PPTP, and it is just that it just suddenly turns off every time
  I try to turn on. There is no process ongoing for PPTP.

  I tried to use an OpenVPN plugin for VPN, it works depending on the
  VPN server.

  I depend on VPN a lot especially on FreeVPN PPTP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 07:48:21 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1725055/+subscriptions

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

[Touch-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen

[Daniel van Vugt]

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

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  nautilus lacks file search in the gnome activities screen

Status in gnome-shell package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  I used to search a file and access it immediately using Ubuntu 16.04
  LTS and some other distributions of GNOME. However, this time, almost
  only folders are shown in the file search.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 08:23:44 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen

[David Gil]

I got this instead though...

** Attachment added: "Screenshot from 2017-10-24 11-20-30.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990023/+files/Screenshot%20from%202017-10-24%2011-20-30.png

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

Title:
  nautilus lacks file search in the gnome activities screen

Status in gnome-desktop package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I used to search a file and access it immediately using Ubuntu 16.04
  LTS and some other distributions of GNOME. However, this time, almost
  only folders are shown in the file search.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 08:23:44 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen

[David Gil]

I wish that the effect here in Ubuntu 7.10 GNOME Shell search is the
same as this when it is integrated in the files. I upgraded to Ubuntu
7.10 expecting for this.

** Attachment added: "Selection_009.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990022/+files/Selection_009.png

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

Title:
  nautilus lacks file search in the gnome activities screen

Status in gnome-desktop package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I used to search a file and access it immediately using Ubuntu 16.04
  LTS and some other distributions of GNOME. However, this time, almost
  only folders are shown in the file search.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 08:23:44 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center

[David Gil]

If that could be the case, I updated the bug report to NetworkManager
component of GNOME instead.
https://bugzilla.gnome.org/show_bug.cgi?id=789341


** Attachment added: "Selection_008.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+attachment/4990011/+files/Selection_008.png

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

Title:
  pptp vpn cannot be easily connected in gnome network manager and gnome
  control center

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I tried to reactivate a VPN (for PPTP) several times again and again
  using PPTP, and it is just that it just suddenly turns off every time
  I try to turn on. There is no process ongoing for PPTP.

  I tried to use an OpenVPN plugin for VPN, it works depending on the
  VPN server.

  I depend on VPN a lot especially on FreeVPN PPTP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 07:48:21 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1725055/+subscriptions

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

[Touch-packages] [Bug 1726634] Re: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users

[Daniel van Vugt]

It looks like you're logging in as root, is that correct?


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

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

Title:
  the sound laptop speaker is not working and it sound interface isnt
  showing in "sound" app. sound works perfectly in other users

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  the sound laptop speaker is not working and it sound interface isnt
  showing in "sound" app. sound works perfectly in other users

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maximum2935 F chrome
maximum7304 F AudioThread
  CurrentDesktop: Unity
  Date: Mon Oct 23 19:05:32 2017
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.asset.tag: MAXIMUM
  dmi.board.name: 05GRXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: MAXIMUM
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5530 non-vPro
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Daniel van Vugt]

It continues... bug 1726608

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Touch-packages] [Bug 1726318] Re: Destructive actions on headerbar aren't properly themed

[Daniel van Vugt]

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Destructive actions on headerbar aren't properly themed

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  On simple scan (for example) there's a .destructive-action button in
  the headerbar and it's not drawn as red unless the button is hovered,
  clicked or unfocused. It also uses inconsistent gradients

  [ Test case ]

  1. Run gnome-scan
  2. Start a scan session (or use the inspector to set the "Stop" button as 
visible)
  3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered)

  [ Regression Potential]

  Destructive buttons in headerbar could be broken

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

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Daniel van Vugt]

Thanks for your testing.

Yes, we already have PulseAudio 11 planned for inclusion in Ubuntu
18.04. It would have been included in Ubuntu 17.10, but PulseAudio 11.0
was released too late in the cycle.

** Tags added: pulse11

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

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

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1726320] Re: suggested and destructive colours are too bright

[Daniel van Vugt]

Ubuntu purple! :)

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  suggested and destructive colours are too bright

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  IMO, so feel free to close this if you disagree, the suggested and
  destructive (green and red) colours that are used in GTK UIs are too
  bright.

  Attached is a screenshot from Marco that shows them both. (It's a
  faked up example, usually you don't see them together like that.)

  They draw the eye too much I think. It should be a hint for where you
  might or might not want to click, but not something that grabs your
  attention.

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

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

[Touch-packages] [Bug 1716184] Re: failure of xrandr to find any outputs

[gjs]

I got the bios upgraded, but the problem has not gone away.  
I hope someone would look into this problem.  The machine is usable, but I 
cannot
access any display output except default, as described in the the original bug
report.  I can demonstrate that the hardware is correctly working by changing 
the 
bios setting to boot using the hdmi display, but then the laptop screen does 
not 
work and xrandr does not find it.

The current machine state is as follows:

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x4F0E8000.

Handle 0x, DMI type 222, 14 bytes
OEM-specific Type
Header and Data:
DE 0E 00 00 01 99 00 03 10 01 20 02 30 03
Strings:
Memory Init Complete
End of DXE Phase
BIOS Boot Complete

Handle 0x0001, DMI type 14, 8 bytes
Group Associations
Name: Intel(R) Silicon View Technology
Items: 1
0x ()

Handle 0x0002, DMI type 134, 13 bytes
OEM-specific Type
Header and Data:
86 0D 02 00 17 07 17 20 00 00 00 00 00

Handle 0x0003, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 2

Handle 0x0004, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0003
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: Row Of Chips
Set: None
Locator: ChannelA-DIMM0
Bank Locator: BANK 0
Type: LPDDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2133 MHz
Manufacturer: Micron
Serial Number: 
Asset Tag: None
Part Number: MT52L1G32D4PG-093 
Rank: 2
Configured Clock Speed: 2133 MHz
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.2 V

Handle 0x0005, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0003
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: Row Of Chips
Set: None
Locator: ChannelB-DIMM0
Bank Locator: BANK 2
Type: LPDDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2133 MHz
Manufacturer: Micron
Serial Number: 
Asset Tag: None
Part Number: MT52L1G32D4PG-093 
Rank: 2
Configured Clock Speed: 2133 MHz
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.2 V

Handle 0x0006, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x000
Ending Address: 0x003
Range Size: 16 GB
Physical Array Handle: 0x0003
Partition Width: 2

Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 kB
Maximum Size: 128 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Parity
System Type: Unified
Associativity: 8-way Set-associative

Handle 0x0008, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 4-way Set-associative

Handle 0x0009, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3 Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 4096 kB
Maximum Size: 4096 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 16-way Set-associative

Handle 0x000A, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: E9 06 08 00 FF FB EB BF
Signature: Type 0, Family 6, Model 142, Stepping 9
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)

[Touch-packages] [Bug 1716184] Re: failure of xrandr to find any outputs

[gjs]

** Description changed:

  I have a very new Lenovo X1 Yoga 2nd edition, with oled display.
  The exact model is 20JECTO1WW.
  The BIOS is N1NET27W.  I am running a vanilla Ubuntu 16.04
  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  
  uname -a
  Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  
  Until recently things worked quite well.  But on August 26 I got an update 
from Ubuntu and
  things began to decay.
  
  In particular, I can no longer display except on the built-in display:  For 
example, xrandr
  cannot find any outputs, even though this laptop has a (working) HDMI output 
port.
  
  xrandr --verbose
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440
  default connected primary 2560x1440+0+0 (0x272) normal (normal) 0mm x 0mm
-   Identifier: 0x271
-   Timestamp:  33974
-   Subpixel:   unknown
-   Clones:
-   CRTC:   0
-   CRTCs:  0
-   Transform:  1.00 0.00 0.00
-   0.00 1.00 0.00
-   0.00 0.00 1.00
-  filter: 
-   _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0 
-   2560x1440 (0x272) 342.835MHz *current
- h: width  2560 start0 end0 total 2560 skew0 clock 
133.92KHz
- v: height 1440 start0 end0 total 1440   clock  93.00Hz
+  Identifier: 0x271
+  Timestamp:  33974
+  Subpixel:   unknown
+  Clones:
+  CRTC:   0
+  CRTCs:  0
+  Transform:  1.00 0.00 0.00
+  0.00 1.00 0.00
+  0.00 0.00 1.00
+ filter:
+  _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0
+   2560x1440 (0x272) 342.835MHz *current
+ h: width  2560 start0 end0 total 2560 skew0 clock 
133.92KHz
+ v: height 1440 start0 end0 total 1440   clock  93.00Hz
  
  Notice there are no (even disconnected) outputs other than default.
  
  Another symptom is that system restart always turns off the power rather
  than rebooting.
  
  I looked at the manifest of the update that seems to have caused trouble and 
the only
- suspicious entry is a microcode update from Intel.  
+ suspicious entry is a microcode update from Intel.
  Here is the entry from the apt history log:
  
  Start-Date: 2017-08-26  17:54:05
  Commandline: aptdaemon role='role-commit-packages' sender=':1.87'
  Upgrade: intel-microcode:amd64 (3.20151106.1, 3.20170707.1~ubuntu16.04.0),
  
  I hope that someone knows what is the problem here.  I am stumped.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  .tmp.unity_support_test.1:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Sep  9 18:54:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:224e]
+  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:224e]
  InstallationDate: Installed on 2017-07-27 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd 
-  Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd
+  Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20JECTO1WW
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET27W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  

[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[spike speigel]

Hello, I just started seeing this on Ubuntu 17.10.

** Tags added: artful

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/ubuntu/+source/iptables/+bug/1556419/+subscriptions

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

[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[spike speigel]

nf_conntrack: default automatic helper assignment has been turned off
for security reasons and CT-based  firewall rule not found. Use the
iptables CT target to attach helpers instead.

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

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/ubuntu/+source/iptables/+bug/1556419/+subscriptions

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Andres Rodriguez]

@Mark,

I do have access (just tested). I'll give it a try tomorrow! Thanks!

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): 

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

[Brian Murray]

Public bug reported:

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

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

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 17:43:06 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-01-16 (1741 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  crash reports still sent to LP on artful

Status in apport package in Ubuntu:
  New

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 17:43:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[John Center]

I added a comment about this new fix on
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495.  One thing
I wanted to add here, for the first time shutdown completed
successfully.  In fact, I was a little startled when it happened.  :-)
It powered off at the end of shutdown, instead of hanging at the
"Reached target Shutdown" message.

One question: Does this mean that Ubuntu 18.04 will use mdadm by default
during installation instead of dmraid?  I really hope so.  It's a real
pain to do it manually.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 

[Touch-packages] [Bug 1726013] Re: systemd-resolved crashed with SIGABRT in log_assert_failed_realm()

[Seth Arnold]

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

** Information type changed from Public Security to Public

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

Title:
  systemd-resolved crashed with SIGABRT in log_assert_failed_realm()

Status in systemd package in Ubuntu:
  New

Bug description:
  Appairs error messge at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:44:22 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2017-10-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. N552VX
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=457b2a84-bb47-47c1-ae79-2e76186547a7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed_realm () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-234.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-234.so
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-resolved crashed with SIGABRT in log_assert_failed_realm()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N552VX.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N552VX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN552VX.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N552VX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1725933] Re: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-loader" (condiviso), diverso da altre ista

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to
  install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-
  loader" (condiviso), diverso da altre istanze del pacchetto
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libunity9 7.1.4+17.10.20170605-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 11:39:29 2017
  ErrorMessage: tentata sovrascrittura di "/usr/bin/unity-scope-loader" 
(condiviso), diverso da altre istanze del pacchetto libunity9:i386
  InstallationDate: Installed on 2017-10-12 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: libunity
  Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to 
install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-loader" 
(condiviso), diverso da altre istanze del pacchetto libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725651] Re: package passwd 1:4.2-3.2ubuntu1.17.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  package passwd 1:4.2-3.2ubuntu1.17.04.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in shadow package in Ubuntu:
  New

Bug description:
  hello

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: passwd 1:4.2-3.2ubuntu1.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Jun  2 13:42:41 2017
  DpkgTerminalLog:
   dpkg: error processing package passwd (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-02 (171 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: shadow
  Title: package passwd 1:4.2-3.2ubuntu1.17.04.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Mark Shuttleworth]

I think Andres has access to the GMAAS, would appreciate if he could 
verify the fix there. If not, let me know and I can try it.

Thanks!

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of 

[Touch-packages] [Bug 1726634] [NEW] the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users

[M G]

Public bug reported:

the sound laptop speaker is not working and it sound interface isnt
showing in "sound" app. sound works perfectly in other users

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.4
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  maximum2935 F chrome
  maximum7304 F AudioThread
CurrentDesktop: Unity
Date: Mon Oct 23 19:05:32 2017
InstallationDate: Installed on 2017-10-19 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.asset.tag: MAXIMUM
dmi.board.name: 05GRXT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: MAXIMUM
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5530 non-vPro
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  the sound laptop speaker is not working and it sound interface isnt
  showing in "sound" app. sound works perfectly in other users

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  the sound laptop speaker is not working and it sound interface isnt
  showing in "sound" app. sound works perfectly in other users

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maximum2935 F chrome
maximum7304 F AudioThread
  CurrentDesktop: Unity
  Date: Mon Oct 23 19:05:32 2017
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.asset.tag: MAXIMUM
  dmi.board.name: 05GRXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: MAXIMUM
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5530 non-vPro
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1726627] [NEW] Pulse audio sink changes from HDMI when starting new Xsession for game

[Steve Barcomb]

Public bug reported:

I have speakers built into my monitor and if I am using 'alsa_output
.pci-_02_00.1.hdmi-stereo-extra1' as my default sink, audio plays
correctly.

I have set up a .desktop file to launch a game in a new xsession using the 
following:
  /usr/bin/xinit /usr/bin/wine /mnt/1tb/WoW/WoW.exe -- :3 vt8

If I run this script, pulseaudio changes the sink to 'alsa_output.pci-
_00_1b.0.iec958-stereo' automatically, so I get no audio from my
application via my monitor.  If I hook a device to the s/pdif port I do
get the audio.  I am a member of the 'audio' group and this worked
properly in 17.04 but has broken after a clean install of 17.10.

$ pacmd list-sinks | grep name:
name:  <-what I 
want to stay as default
name:  <-what the sink 
switches to when starting a second X session.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  sbarcomb   1993 F pulseaudio
 /dev/snd/controlC0:  sbarcomb   1993 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 18:48:48 2017
InstallationDate: Installed on 2017-10-19 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: GP104 High Definition Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Sound works for a while, then breaks
Title: [hostname-R4, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] fails after a 
while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2013
dmi.bios.vendor: Alienware
dmi.bios.version: A11
dmi.board.name: 07JNH0
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.chassis.version: 00
dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
dmi.product.family: 0
dmi.product.name: Aurora-R4
dmi.product.version: 00
dmi.sys.vendor: Alienware

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


** Tags: amd64 apport-bug artful

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

Title:
  Pulse audio sink changes from HDMI when starting new Xsession for game

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have speakers built into my monitor and if I am using 'alsa_output
  .pci-_02_00.1.hdmi-stereo-extra1' as my default sink, audio plays
  correctly.

  I have set up a .desktop file to launch a game in a new xsession using the 
following:
/usr/bin/xinit /usr/bin/wine /mnt/1tb/WoW/WoW.exe -- :3 vt8

  If I run this script, pulseaudio changes the sink to 'alsa_output.pci-
  _00_1b.0.iec958-stereo' automatically, so I get no audio from my
  application via my monitor.  If I hook a device to the s/pdif port I
  do get the audio.  I am a member of the 'audio' group and this worked
  properly in 17.04 but has broken after a clean install of 17.10.

  $ pacmd list-sinks | grep name:
name:  <-what I 
want to stay as default
name:  <-what the sink 
switches to when starting a second X session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sbarcomb   1993 F pulseaudio
   /dev/snd/controlC0:  sbarcomb   1993 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 18:48:48 2017
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: GP104 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Sound works for a while, then breaks
  Title: [hostname-R4, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A11
  dmi.board.name: 07JNH0
  

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

[Alvin Cura]

Ditto here for PJSingh5000.  I had added a google account as well.

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

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

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

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

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

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

[Touch-packages] [Bug 1720517] Re: Software and Updates /Other Software greys out when clicking on "Canonical Partners"

[enolive]

encountered it after an update to 17.10 as well.
My workaround for now is to start software-properties-gtk using gksu

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

Title:
  Software and Updates /Other Software greys out when clicking on
  "Canonical Partners"

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  "Other Software" only works after having clicked on "Ubuntu Software",
  "Updates", etc and changing some settings on those pages.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.16
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 30 10:44:47 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2017-09-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725847] Re: libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without _GLIBCXX_USE_C99

[Andrew Paxie]

Ah, I get it now.

g++-4.8 is part of universe in artful, meaning "Community supported",
not officially supported by Canonical.

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

Title:
  libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without
  _GLIBCXX_USE_C99

Status in gcc-4.8 package in Ubuntu:
  Won't Fix

Bug description:
  Test program compiled on Artful Aardvark Ubuntu 17.10.

  $ which g++-4.8
  /usr/bin/g++-4.8

  $ /usr/bin/g++-4.8 --version
  g++-4.8 (Ubuntu 4.8.5-4ubuntu6) 4.8.5
  Copyright (C) 2015 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  $ /usr/bin/g++-4.8 -std=c++11 -x c++ - <
  #include 
  int main()
  {
std::cout << std::to_string(0) << '\n';
return 0;
  }
  EOF 

  Expected result

  compile without errors, output 0

  Actual result

  : In function ‘int main()’:
  :5:16: error: ‘to_string’ is not a member of ‘std’

  Supposed cause

  _GLIBCXX_USE_C99 is not set in 
  /usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h
  in package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu6)

  Further information

  Test program compiles and runs on Zesty Zapus with package
  libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1725847/+subscriptions

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

[Touch-packages] [Bug 1573693] Re: Microphone is not working

[simzy39]

I've a Lenovo Flex 3, and the mic does not work with a fresh install of
Ubuntu 17.10. I had to instal PulseAudioVolumeControl and move the 'From
Left' setting all the way left, and keep the 'From Right' setting higher
in order for it to work.

But then Chrome autoadjusts the internal mic volume when I do any conferencing 
in the browser.
See: 
https://askubuntu.com/questions/967674/how-do-i-stop-audiopulsevolumecontrol-auto-adjusting-itself-so-my-mic-works

Here Chrome blames Ubuntu:
https://bugs.chromium.org/p/chromium/issues/detail?id=435112=2=0=100==ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified==

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

Title:
  Microphone is not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Microphone is not working on ASUS X552L laptop.

  Just installed latest ubuntu version 16.04 LTS

  After installed Skype, tried a test call, sound was very low volume.
  Tried to adjust microphone volume with the slider, mic went dead for
  good, no sound at all. tried to reinstall alsa package

  apt-get remove --purge alsa-base pulseaudio

  and install it again, nothing works.

  Did not work on older ubuntu version either.

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  alsa-base:
Telepítve: 1.0.25+dfsg-0ubuntu5
Jelölt:1.0.25+dfsg-0ubuntu5
Verziótáblázat:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  pulseaudio:
Telepítve: 1:8.0-0ubuntu3
Jelölt:1:8.0-0ubuntu3
Verziótáblázat:
   *** 1:8.0-0ubuntu3 500
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irma   1425 F pulseaudio
   /dev/snd/pcmC1D0c:   irma   1425 F...m pulseaudio
   /dev/snd/controlC1:  irma   1425 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 22 18:17:49 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.509
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.509:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1726614] Re: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989449/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989451/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989454/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989455/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989456/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989457/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726614/+attachment/4989458/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1724277

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-addressbook-factory-subprocess crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Probably coming from a background process

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evolution-data-server 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 22:55:52 2017
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess
  InstallationDate: Installed on 2017-09-22 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess 
--factory google --bus-name 
org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx5547x3 --own-path 
/org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/5547/3
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () at 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1511439] Re: webbrowser-app apparmor policy fails to load on desktop

[Martin]

In ubuntu 17.10, apparmor.service did not start because video.d, audio.d
and graphics.d could not be loaded.

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

Title:
  webbrowser-app apparmor policy fails to load on desktop

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  $ sudo apparmor_parser -r /etc/apparmor.d/usr.bin.webbrowser-app
  AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in 
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open 
'/usr/share/apparmor/hardware/graphics.d'
  $
  $ sudo aa-status|grep webbrowser
  $

  This was tested on xenial but affects wily too if it is shipping the
  policy.

  The problem is that apparmor-easyprof-ubuntu normally ships these 
directories, but it is not installed by default on the desktop image. I suggest 
shipping these empty directories via the webbrowser-app's packaging:
  - /usr/share/apparmor/hardware/audio.d
  - /usr/share/apparmor/hardware/graphics.d
  - /usr/share/apparmor/hardware/video.d

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511439/+subscriptions

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

[Touch-packages] [Bug 1726609] Re: gdebi crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

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

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1726609/+attachment/4989402/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1726609/+attachment/4989403/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 1303147

** Information type changed from Private to Public

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

Title:
  gdebi crashed with apt.cache.LockFailedException in _fetch_archives():
  Failed to lock /var/cache/apt/archives/lock

Status in gdebi package in Ubuntu:
  New

Bug description:
  installing dropbox

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-core 0.9.5.7+nmu1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 23 17:37:34 2017
  ExecutablePath: /usr/share/gdebi/gdebi
  InstallationDate: Installed on 2017-10-22 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi dropbox_2015.10.28_amd64.deb
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/bin/gdebi', 'dropbox_2015.10.28_amd64.deb']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: gdebi
  Title: gdebi crashed with apt.cache.LockFailedException in _fetch_archives(): 
Failed to lock /var/cache/apt/archives/lock
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

On an Ubuntu 14.04 system I edited my sources.list file to have
-proposed enabled and modified all trusty entries to xenial. After which
I ran 'sudo apt-get dist-upgrade' and successfully upgraded to Ubuntu
16.04 with -proposed enabled and the new version of cracklib-runtime
being installed.

>From /var/log/apt-term.log:

Preparing to unpack .../cracklib-runtime_2.9.2-1ubuntu1_amd64.deb ...
Unpacking cracklib-runtime (2.9.2-1ubuntu1) over (2.9.1-1build1) ...
Setting up cracklib-runtime (2.9.2-1ubuntu1) ...


Setting to v-done for xenial.

** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1681231

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Released
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1723272] Re: apport-bug unable to init server, dumps core

[Paul]

@nrbrtx Yeah, Launchpad has had some timeout issue for over a week now.
However ...

This bug isn't a duplicate of bug 1713313. That bug is filed against
Wayland in general, and odds on it won't get fixed because this
feature/misfeature is intentional in Wayland's architecture. Other
distros are sticking to it. See
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1713313/comments/44

This bug is filed against apport-bug itself, which is where changes will
need to be made if/when bug 1713313 is Wontfixed.

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

Title:
  apport-bug unable to init server, dumps core

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, apport-bug fails with the follow error:

  # apport-bug
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  Calling apport-cli directly works just fine. The problem seems to be a
  general Xwayland permission issue, since nothing can connect to the
  display server if sudo/su is used:

  $ sudo xclock
  No protocol specified
  Error: Can't open display: :0
  $ xauth list
  xauth:  file /home/user/.Xauthority does not exist

  If that's the way things are going to be in Ubuntu from now on, we
  need to make apport-bug a bit smarter in the way it decides whether to
  use the GUI version or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 
+1100:2017-10-13 09:46:23.546417474 
+1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
  Date: Fri Oct 13 09:49:17 2017
  InstallationDate: Installed on 2016-12-02 (313 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)

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

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

[Touch-packages] [Bug 1726595] [NEW] Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10

[thomas duriez]

Public bug reported:

OBSERVED BEHAVIOR:
Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

REPRODUCE THE BUG:

You need matlab (my version is R2017a) to reproduce the bug. I suspect
any version >= 2014b would reproduce the bug (HG2 framework), and maybe
any version.

1. Connect to self (or from other machine) with X forwarding:
$ ssh -X user@localhost

2. Launch matlab
$ matlab &

3. Plot something
>> plot(1,1)

ADDITIONAL INFORMATION
- Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
- No ressources seem to be used. 
- Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
- Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
- Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
- This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: openssh-client 1:7.5p1-10
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Oct 23 17:44:23 2017
ExecutablePath: /usr/bin/ssh
InstallationDate: Installed on 2017-08-25 (59 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
SourcePackage: openssh
UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
modified.conffile..etc.ssh.ssh_config: [modified]
mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

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


** Tags: amd64 apport-bug artful

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

Title:
  Running Matlab (R) from ssh session with X forwarding doesn't work
  anymore in 17.10

Status in openssh package in Ubuntu:
  New

Bug description:
  OBSERVED BEHAVIOR:
  Matlab stays in busy state when using some functions like "plot" or even 
"exit", while executing through a ssh tunnel with X11 forwarding. 

  REPRODUCE THE BUG:

  You need matlab (my version is R2017a) to reproduce the bug. I suspect
  any version >= 2014b would reproduce the bug (HG2 framework), and
  maybe any version.

  1. Connect to self (or from other machine) with X forwarding:
  $ ssh -X user@localhost

  2. Launch matlab
  $ matlab &

  3. Plot something
  >> plot(1,1)

  ADDITIONAL INFORMATION
  - Normal behavior would be appearance of a new window and a single point at 
position (1,1). 
  - No ressources seem to be used. 
  - Opening a figure alone is possible. (>> figure). Opening other windows from 
the graphical user interface is possible 
  - Opening Matlab without the java machine seems to work, but matlab relies 
heavily on java. At least "exit" which doesn't work with java, works without 
java.
  - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything.
  - This used to work perfectly for as long as I have been using Ubuntu (since 
2012).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-client 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct 23 17:44:23 2017
  ExecutablePath: /usr/bin/ssh
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  modified.conffile..etc.ssh.ssh_config: [modified]
  mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560

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

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

[Touch-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus

[Sebastien Bacher]

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

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

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

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

Title:
  Thumbnails too small in 'open file' dialog nautilus

Status in Nautilus:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When trying to upload image files to e.g. websites like marktplaats.nl
  (kind of ebay) I get  very, very small image thumbnails. There seems
  no way to enlarge these thumbnails. All options only work if Nautilus
  is used stand alone, but not with the open file dialog that is being
  used to upload files.

  I have attached a screen dump just to show what I mean.

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

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

[Touch-packages] [Bug 1723272] Re: apport-bug unable to init server, dumps core

[Norbert]

Thanks for reporting. It's already known - see bug 1713313.
Please mark as duplicate (I got timeout issue).

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

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

Title:
  apport-bug unable to init server, dumps core

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, apport-bug fails with the follow error:

  # apport-bug
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  No protocol specified
  Unable to init server: Could not connect: Connection refused
  Segmentation fault (core dumped)

  Calling apport-cli directly works just fine. The problem seems to be a
  general Xwayland permission issue, since nothing can connect to the
  display server if sudo/su is used:

  $ sudo xclock
  No protocol specified
  Error: Can't open display: :0
  $ xauth list
  xauth:  file /home/user/.Xauthority does not exist

  If that's the way things are going to be in Ubuntu from now on, we
  need to make apport-bug a bit smarter in the way it decides whether to
  use the GUI version or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 
+1100:2017-10-13 09:46:23.546417474 
+1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
  Date: Fri Oct 13 09:49:17 2017
  InstallationDate: Installed on 2016-12-02 (313 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)

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

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

[Touch-packages] [Bug 1175608] [NEW] Thumbnails too small in 'open file' dialog nautilus

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When trying to upload image files to e.g. websites like marktplaats.nl
(kind of ebay) I get  very, very small image thumbnails. There seems no
way to enlarge these thumbnails. All options only work if Nautilus is
used stand alone, but not with the open file dialog that is being used
to upload files.

I have attached a screen dump just to show what I mean.

** Affects: nautilus
 Importance: Wishlist
 Status: In Progress

** Affects: gtk+3.0 (Ubuntu)
 Importance: Wishlist
 Status: Triaged

-- 
Thumbnails too small in 'open file' dialog nautilus
https://bugs.launchpad.net/bugs/1175608
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[demizer]

Trying the above fix does not work for 17.10. This is highly
unfortunate.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1726571] [NEW] cpu fan speed freezes

[Jesse Geens]

Public bug reported:

cpu fan speed always freezes at 525RPM

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.24
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Oct 23 22:24:18 2017
InstallationDate: Installed on 2015-08-06 (809 days ago)
InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 2550W1E
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=81f09e4c-e8db-48d1-9083-0ef6bfbec68f ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET48WW (1.24 )
dmi.board.name: 2550W1E
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr81ET48WW(1.24):bd12/10/2010:svnLENOVO:pn2550W1E:pvrThinkPadL512:rvnLENOVO:rn2550W1E:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2550W1E
dmi.product.version: ThinkPad L512
dmi.sys.vendor: LENOVO

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


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

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

Title:
  cpu fan speed freezes

Status in systemd package in Ubuntu:
  New

Bug description:
  cpu fan speed always freezes at 525RPM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.24
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct 23 22:24:18 2017
  InstallationDate: Installed on 2015-08-06 (809 days ago)
  InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 2550W1E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=81f09e4c-e8db-48d1-9083-0ef6bfbec68f ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET48WW (1.24 )
  dmi.board.name: 2550W1E
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr81ET48WW(1.24):bd12/10/2010:svnLENOVO:pn2550W1E:pvrThinkPadL512:rvnLENOVO:rn2550W1E:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2550W1E
  dmi.product.version: ThinkPad L512
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

On an Ubuntu 16.04 system I installed the version of cracklib-runtime
from -proposed and performed the following tests:

Test A
--
1) Install cracklib-runtime from -proposed.
2) Reinstall dictionaries-common and verify that the trigger is called

Test B
--
1) With the version of cracklib-runtime from -proposed installed, confirm that 
a distribution upgrade to next supported release succeeds.

Both of them succeeded. The apt-term.log of the distribution upgrade:
Preparing to unpack .../cracklib-runtime_2.9.2-3_amd64.deb ...^M
Unpacking cracklib-runtime (2.9.2-3) over (2.9.2-1ubuntu1) ...^M

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Released
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1725980] Re: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

Could you please try these commands and see if they help solve the
problem:

sudo apt update
sudo apt install --reinstall libheimntlm0-heimdal:i386
sudo apt -f install

Please let us know how it goes.

Thanks!

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

Title:
  package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-
  4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad
  inconsistent state; you should  reinstall it before attempting
  configuration

Status in heimdal package in Ubuntu:
  New

Bug description:
  not updated

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Oct 22 09:37:53 2017
  DuplicateSignature:
   package:libheimntlm0-heimdal:i386:1.7~git20150920+dfsg-4ubuntu1.16.04.1
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libheimntlm0-heimdal:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-06 (229 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: heimdal
  Title: package libheimntlm0-heimdal:i386 
1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725850] Re: systemd-journald crashed with SIGABRT in journal_file_rotate_suggested()

[Sebastien Bacher]

the error is
"systemd-journald.service: Watchdog timeout (limit 3min)!"

which seems to match https://github.com/systemd/systemd/issues/1353

** Information type changed from Private to Public

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

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

Title:
  systemd-journald crashed with SIGABRT in
  journal_file_rotate_suggested()

Status in systemd package in Ubuntu:
  New

Bug description:
  System was in sleep mode, I logged back in and this system error was
  waiting for me.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 09:34:50 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Alienware Alienware X51 R3
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   journal_file_rotate_suggested () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-journald crashed with SIGABRT in 
journal_file_rotate_suggested()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.0
  dmi.board.name: 026CD3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.0:bd09/11/2015:svnAlienware:pnAlienwareX51R3:pvr:rvnAlienware:rn026CD3:rvrA00:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware X51 R3
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1725865] Re: Network shows Cable Unplugged

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Network shows Cable Unplugged

Status in network-manager package in Ubuntu:
  New

Bug description:
  This was working perfectly on 17.04, but after installing 17.10 from
  scratch, the wired network is not detected. It simply shows as Cable
  Unplugged when in fact there is the same cable still connected
  directly to the router. This same computer has Windows 10 and it
  detects the network correctly. I also tested Fedora and it detected
  the network correctly (The wired one). I am currently using only the
  Wireless connection because of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 17:59:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
  
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1681231] Update Released

[Steve Langasek]

The verification of the Stable Release Update for cracklib2 has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Released
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

This bug was fixed in the package cracklib2 - 2.9.2-3ubuntu1

---
cracklib2 (2.9.2-3ubuntu1) zesty; urgency=medium

  * Migrate triggers to interest-noawait to avoid trigger-cycles (Closes:
#859307, LP: #1681231)

 -- Brian Murray   Fri, 20 Oct 2017 16:52:55 -0700

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

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Released
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1726555] Re: Use mainstream theme solution for gnome-terminal, drop patch

[Egmont Koblinger]

** Package changed: light-themes (Ubuntu) => ubuntu-themes (Ubuntu)

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

Title:
  Use mainstream theme solution for gnome-terminal, drop patch

Status in gnome-terminal package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to-
  some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and
  Radiance themes' apps/gnome-terminal.css relies on this to get the
  desired look for the notebook widget.

  Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be
  necessary. It's just an additional burden to carry this patch, plus an
  unnecessary complication for those who wish to manually compile gnome-
  terminal for whatever reason.

  gnome-terminal.css should ideally be modified to use the CSS names
  provided by mainstream gnome-terminal, and once done, the gnome-
  terminal patch can be dropped.

  Upstream references:
  https://bugzilla.gnome.org/show_bug.cgi?id=765590
  https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6
  https://bugzilla.gnome.org/show_bug.cgi?id=788044

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

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

[Touch-packages] [Bug 1726555] [NEW] Use mainstream theme solution for gnome-terminal, drop patch

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to-
some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and
Radiance themes' apps/gnome-terminal.css relies on this to get the
desired look for the notebook widget.

Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be
necessary. It's just an additional burden to carry this patch, plus an
unnecessary complication for those who wish to manually compile gnome-
terminal for whatever reason.

gnome-terminal.css should ideally be modified to use the CSS names
provided by mainstream gnome-terminal, and once done, the gnome-terminal
patch can be dropped.

Upstream references:
https://bugzilla.gnome.org/show_bug.cgi?id=765590
https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6
https://bugzilla.gnome.org/show_bug.cgi?id=788044

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful
-- 
Use mainstream theme solution for gnome-terminal, drop patch
https://bugs.launchpad.net/bugs/1726555
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes in Ubuntu.

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

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

[Oliver Gerhardt]

Also happens after adding a Microsoft account. I just upgraded from
16.04 to 17.10. It is a bit annoying but the added Accounts are working
well.

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

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

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

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

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

On an Ubuntu 16.04 system I edited my sources.list file to have
-proposed enabled and modify all xenial entries to zesty. After which I
ran 'sudo apt-get dist-upgrade' and successfully upgraded to Ubuntu
17.04 with -proposed enabled and the new version of cracklib-runtime
being installed.

bdmurray@clean-xenial-amd64:~$ apt-cache policy cracklib-runtime
cracklib-runtime:
  Installed: 2.9.2-3ubuntu1
  Candidate: 2.9.2-3ubuntu1
  Version table:
 *** 2.9.2-3ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 2.9.2-3 500
500 http://192.168.10.7/ubuntu zesty/main amd64 Packages


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

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Committed
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

On an Ubuntu 17.04 system I installed the version of cracklib-runtime
from -proposed and performed the following tests:

Test A
--
1) Install cracklib-runtime from -proposed.
2) Reinstall dictionaries-common and verify that the trigger is called

Test B
--
1) With the version of cracklib-runtime from -proposed installed, confirm that 
a distribution upgrade to next supported release succeeds.

Both of them succeeded.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Committed
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1726497] Re: nautilus crashed with SIGABRT in wl_abort()

[Sebastien Bacher]

** Information type changed from Private to Public

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

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

Title:
  nautilus crashed with SIGABRT in wl_abort()

Status in wayland package in Ubuntu:
  New

Bug description:
  This crash occurred when I was browsing my folders.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 08:55:31 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   wl_proxy_marshal_array_constructor_versioned () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   wl_proxy_marshal () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGABRT in 
wl_proxy_marshal_array_constructor_versioned()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1714803] Re: Search list in resolv.conf breaks resolving for that domain

[ts]

I seem to have a similar (the same) problem. Ubuntu 17.10 - sleep and
resume leaves the resolv.conf with a "search" directive that breaks name
resolution for any name within the domains mentioned in the search
directive.

Trying to resolve any name fails, as e.g.:

% systemd-resolve 
: resolve call failed: No appropriate name servers or 
networks for name found

Deleting the search directive and restarting the networking service
resolves things temporarily (until the next suspend/resume loop).

I've removed the request for search directives from the dhcpclient.conf,
and this works fine the first start, but suspend/resume leads some
service to add the search directive again, and name resolution breaks.

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

Title:
  Search list in resolv.conf breaks resolving for that domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.04
  systemd 232-21ubuntu5

  Adding a domain to the search list in /etc/resolv.conf breaks
  resolving for that domain. Not only does the search list not get used
  as expected, but host names in the domain cannot be resolved by
  systemd-resolved at all.

  I just ran into this after upgrading from ubuntu 16.04 to 17.04 which
  enabled systemd-resolved. I have for a long time used resolveconf to
  add a 'search my-domain'-line to my /etc/resolv.conf.

  
  Example of expected behaviour. With Googles DNS server (8.8.8.8) and 
ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve 
can resolve www.ubuntu.com and www:

  $ cat /etc/resolv.conf 
  nameserver 8.8.8.8
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   501 IN  A   91.189.89.115
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   382 IN  A   91.189.89.103
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.89.115
  
  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  $ systemd-resolve www
  www: 91.189.90.59
   (www.ubuntu.com)
  
  -- Information acquired via protocol DNS in 3.8ms.
  -- Data is authenticated: no

  Ubuntu 17.04 default config, with the systemd-resolved name server in
  /etc/resolv.conf and no search list. www.ubuntu.com can still be
  resolved correctly:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  ;; ANSWER SECTION:
  www.ubuntu.com.   482 IN  A   91.189.89.110
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: 91.189.90.58
  
  -- Information acquired via protocol DNS in 18.2ms.
  -- Data is authenticated: no

  Broken behaviour, using the systemd-resolved name server and specify
  ubuntu.com in search list. Resolving fails for www.ubuntu.com and www,
  both using dig (DNS) and using sytemd-resolve:

  $ cat /etc/resolv.conf
  nameserver 127.0.0.53
  search ubuntu.com
  $ dig +nostat +nocmd www.ubuntu.com
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ dig +search +nostat +nocmd www
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50588
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;www.ubuntu.com.  IN  A
  
  $ systemd-resolve www.ubuntu.com
  www.ubuntu.com: resolve call failed: 

[Touch-packages] [Bug 1726536] Re: Cant resume after suspend/sleep

[Dario]

Added boot-suspend-reboot journal log.

** Attachment added: "boot-suspend-reboot.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1726536/+attachment/4989034/+files/boot-suspend-reboot.log

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

Title:
  Cant resume after suspend/sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  1) 17.10 
  2) 3.26.1-0ubuntu4
  3) Pressing any button wakes computer from suspend/sleep, expecting GDM login 
screen.
  4) Waking up computer from suspend does nothing, screen remains black as it 
doesn't getting any signal (HDD led is blinking as if computer is doing 
something). Need to hard reset computer at that point.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 20:39:29 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  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.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.85+git1710210630.e580be~gd~a
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1726497] [NEW] nautilus crashed with SIGABRT in wl_abort()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This crash occurred when I was browsing my folders.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 08:55:31 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-21 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 wl_proxy_marshal_array_constructor_versioned () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
 wl_proxy_marshal () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGABRT in 
wl_proxy_marshal_array_constructor_versioned()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: wayland (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash artful wayland-session
-- 
nautilus crashed with SIGABRT in wl_abort()
https://bugs.launchpad.net/bugs/1726497
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1726535] Re: totem crashed with SIGSEGV in wl_proxy_add_listener()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988977/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988979/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988984/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988985/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988986/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988987/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726535/+attachment/4988988/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1723130
   totem crashed with SIGSEGV in wl_proxy_add_listener()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with SIGSEGV in wl_proxy_add_listener()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  - Testing out Ubuntu 17.10 on a T60 with 945GM 
  - Totem crashes on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 21:37:45 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-08-23 (61 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f874e7c777c : testb  
$0x4,0x28(%rdi)
   PC (0x7f874e7c777c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1726536] [NEW] Cant resume after suspend/sleep

[Dario]

Public bug reported:

1) 17.10 
2) 3.26.1-0ubuntu4
3) Pressing any button wakes computer from suspend/sleep, expecting GDM login 
screen.
4) Waking up computer from suspend does nothing, screen remains black as it 
doesn't getting any signal (HDD led is blinking as if computer is doing 
something). Need to hard reset computer at that point.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 20:39:29 2017
DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
InstallationDate: Installed on 2017-08-25 (59 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-AR
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.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.85+git1710210630.e580be~gd~a
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful third-party-packages 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/1726536

Title:
  Cant resume after suspend/sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  1) 17.10 
  2) 3.26.1-0ubuntu4
  3) Pressing any button wakes computer from suspend/sleep, expecting GDM login 
screen.
  4) Waking up computer from suspend does nothing, screen remains black as it 
doesn't getting any signal (HDD led is blinking as if computer is doing 
something). Need to hard reset computer at that point.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 20:39:29 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (59 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

OK so instead of using a new or old kernel and to avoid issues with
other drivers (like Nvidia breaking with the 4.14 RC version) and based
on your feedback, I only then focused on PulseAudio. I noted that Ubuntu
17.10 is using the PulseAudio from January which is 10.0 instead of the
11.1 from September. So I grabbed the 11.1 one, downloaded the needed
dependencies and compiled the whole thing like this:


1. Make sure the Source repository is enabled since it comes disabled by 
default from the Software & Updates App.

2. Install all dependencies needed

sudo apt-get build-dep pulseaudio && sudo apt-get install checkinstall
git libpulse-dev

3. Set all the flags and settings

CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall"

CXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall"

CPPFLAGS="-D_FORTIFY_SOURCE=2"

LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--no-as-needed -lxcb"

./configure --build=x86_64-linux-gnu  --prefix=/usr
--includedir="\${prefix}/include" --mandir="\${prefix}/share/man"
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var
--libexecdir="\${prefix}/lib/pulseaudio" --srcdir=. --disable-
maintainer-mode --disable-dependency-tracking --disable-silent-rules
--enable-x11 --disable-hal --libdir=\${prefix}/lib/x86_64-linux-gnu
--with-module-dir=\${prefix}/lib/pulse-11.1/modules --disable-oss-
wrapper

NOTE: The above is based on PulseAudio 11.1 so if you look at the final
line it says pulse-11.1 just to help with knowing which version is
handled.

After this a simple

make -j8 (In my case)

Then

sudo make install

then reboot or kill pulseaudio. After that I have tested during the past
3 hours and have had no issues whatsoever. This solved a crackling
issues that happened every 3-5 minutes. The disconnecting and
reconnecting issues that in 3 hours would have happened about 30 times
or more. A sound issue in calls, even other members hearing me can hear
me better and no crackling sound in the back. And while testing with
steam and youtube, there was no drop in sound.

For now this is a better solution but if other bugs appear in regards to
sound issues, most probably updating to 11.1 (The whole 11.x versions
fixed several issues I was having on both, a wireless headset and the
USB connected headset). Hope this information helps along.

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Touch-packages] [Bug 1710604] Re: New release 7.55.1

[Hans Joachim Desserud]

curl 7.55.1-1ubuntu2.1 is now available in Ubuntu 17.10 so I believe
this can be marked as fixed.

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

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

Title:
  New release 7.55.1

Status in curl package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  https://curl.haxx.se/changes.html

  "Fixed in 7.55.1 - August 14 2017:
  Bugfixes:

  build: fix 'make install' with configure, install docs/libcurl/* too
  make install: add 8 missing man pages to the installation
  curl: do bounds check using a double comparison
  dist: Add dictserver.py/negtelnetserver.py to release
  digest_sspi: Don't reuse context if the user/passwd has changed
  gitignore: ignore top-level .vs folder
  build: check out *.sln files with Windows line endings
  travis: verify "make install"
  dist: fix the cmake build by shipping cmake_uninstall.cmake.in too
  metalink: fix error: ‘*’ in boolean context, suggest ‘&&’ instead
  configure: use the threaded resolver backend by default if possible
  mkhelp.pl: allow executing this script directly
  maketgz: remove old *.dist files before making the tarball
  openssl: remove CONST_ASN1_BIT_STRING
  openssl: fix "error: this statement may fall through"
  proxy: fix memory leak in case of invalid proxy server name
  curl/system.h: support more architectures (OpenRISC, ARC)
  docs: fix typos
  curl/system.h: add Oracle Solaris Studio
  CURLINFO_TOTAL_TIME: could wrongly return 4200 seconds
  docs: --connect-to clarified
  cmake: allow user to override CMAKE_DEBUG_POSTFIX
  travis: test cmake build on tarball too
  redirect: make it handle absolute redirects to IDN names
  curl/system.h: fix for gcc on PowerPC
  curl --interface: fixed for IPV6 unique local addresses
  cmake: threads detection improvements"

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: curl 7.52.1-5ubuntu1
  Uname: Linux 4.13.0-041300rc4-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 08:45:48 2017
  InstallationDate: Installed on 2017-07-05 (39 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: curl
  UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago)

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

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

[Touch-packages] [Bug 1726504] Re: Was there a change of RemoveIPC semantics in Ubuntu 17.10?

[Hans Joachim Desserud]

** Tags added: artful

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

Title:
  Was there a change of RemoveIPC semantics in Ubuntu 17.10?

Status in systemd package in Ubuntu:
  New

Bug description:
  A few days ago I upgraded my Ubuntu 17.04 to 17.10. Afterwards I found
  that my Oracle XE would no longer start. alert_XE.log said things like

  ORA-27300: OS system dependent operation:semctl failed with status: 22
  ORA-27301: OS failure message: Invalid argument
  ORA-27302: failure occurred at: sskgpwrm1
  ORA-27157: OS post/wait facility removed
  ORA-27300: OS system dependent operation:semop failed with status: 43
  ORA-27301: OS failure message: Identifier removed
  ORA-27302: failure occurred at: sskgpwwait1

  I found that /etc/systemd/logind.conf had the RemoveIPC line commented
  out. When I set RemoveIPC=no (the default is “yes”) and rebooted
  Linux, Oracle XE started fine, as it had before the upgrade. So I
  assume the 17.10 upgrade somehow made a change to the RemoveIPC
  semantics.

  As I found that my previous installation also had a commented
  RemoveRPC it looks like Ubuntu 17.10 changed the default value from
  “no” to “yes”, and so breaks the Oracle XE installation. In this case
  I consider this behavior problematic, it should at least produce a
  clear warning during upgrade.

  If the default value did not change I have no explanation of the
  phenomenon.

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

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

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

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988692/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988696/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988706/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988708/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988709/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988710/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726502/+attachment/4988712/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1719004
   cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in cups package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: 
Assertion `ec >= 0' failed.
  Date: Sun Oct 22 19:54:21 2017
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1506432361
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  KernLog:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: TOSHIBA SATELLITE C50-A
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=5e883c74-2032-428a-8401-4f6a41532a71 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: 
__spawnix: Assertion `ec >= 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.30
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.30:bd03/24/2014:svnTOSHIBA:pnSATELLITEC50-A:pvrPSCJGE-001006G5:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Durban 10BT
  dmi.product.name: SATELLITE C50-A
  dmi.product.version: PSCJGE-001006G5
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1601923] Re: no correct link to qmake

[Hans L]

Also this bug might be related to
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1125612 ?

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

Title:
  no correct link to qmake

Status in Canonical System Image:
  New
Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  Qt5 is installed. I give in in a terminal : qmake
  I get this error: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': 
No such file or directory.
  The link is not correct. qmake is in /usr/lib/x86_64-linux-gnu/qt5/bin/
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1601923/+subscriptions

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

[Touch-packages] [Bug 1601923] Re: no correct link to qmake

[Hans L]

Steps to reproduce:

1) Start with freshly installed, and updated Ubuntu Desktop 16.04.3 LTS 64bit
2) Open terminal and Run "qmake"
  Result: qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No 
such file or directory
  Expected result: The program 'qmake' is currently not installed. You can 
install it by typing: ...

3) Run "sudo apt install qt5-qmake"
4) Run "qmake"
  Result: qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No 
such file or directory
  Expected result: It finds the qt5-qmake that I just installed


 


** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1601923/+attachment/4988667/+files/log.txt

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

Title:
  no correct link to qmake

Status in Canonical System Image:
  New
Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  Qt5 is installed. I give in in a terminal : qmake
  I get this error: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': 
No such file or directory.
  The link is not correct. qmake is in /usr/lib/x86_64-linux-gnu/qt5/bin/
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1601923/+subscriptions

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

[Touch-packages] [Bug 1725686] Re: Computer freezes when logging into Ubuntu 17.10 on Wayland

[Brian Murray]

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

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

Title:
  Computer freezes when logging into Ubuntu 17.10 on Wayland

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When I first installed Ubuntu 17.10, I logged into Wayland and it
  worked fine. There were some minor issues, but it was still
  functional. However, I started screencasting my computer with Ctrl-
  Alt-Shift-R, but my computer became very slow and I decided to shut it
  down. I closed all applications before shutting it down, but forgot to
  stop the screencast.

  Now, when I try to log into Ubuntu 17.10 using Wayland, the screen
  goes gray and my cursor is stuck in the middle of the screen. I can't
  move my cursor at all and the desktop never actually loads. I can
  still transition to other ttys, though, by using the Ctrl-Alt-(F key)
  commands.

  However, logging into Ubuntu on Xorg or Unity still works fine.

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

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

[Touch-packages] [Bug 1726504] [NEW] Was there a change of RemoveIPC semantics in Ubuntu 17.10?

[Renardo]

Public bug reported:

A few days ago I upgraded my Ubuntu 17.04 to 17.10. Afterwards I found
that my Oracle XE would no longer start. alert_XE.log said things like

ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwrm1
ORA-27157: OS post/wait facility removed
ORA-27300: OS system dependent operation:semop failed with status: 43
ORA-27301: OS failure message: Identifier removed
ORA-27302: failure occurred at: sskgpwwait1

I found that /etc/systemd/logind.conf had the RemoveIPC line commented
out. When I set RemoveIPC=no (the default is “yes”) and rebooted Linux,
Oracle XE started fine, as it had before the upgrade. So I assume the
17.10 upgrade somehow made a change to the RemoveIPC semantics.

As I found that my previous installation also had a commented RemoveRPC
it looks like Ubuntu 17.10 changed the default value from “no” to “yes”,
and so breaks the Oracle XE installation. In this case I consider this
behavior problematic, it should at least produce a clear warning during
upgrade.

If the default value did not change I have no explanation of the
phenomenon.

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

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

Title:
  Was there a change of RemoveIPC semantics in Ubuntu 17.10?

Status in systemd package in Ubuntu:
  New

Bug description:
  A few days ago I upgraded my Ubuntu 17.04 to 17.10. Afterwards I found
  that my Oracle XE would no longer start. alert_XE.log said things like

  ORA-27300: OS system dependent operation:semctl failed with status: 22
  ORA-27301: OS failure message: Invalid argument
  ORA-27302: failure occurred at: sskgpwrm1
  ORA-27157: OS post/wait facility removed
  ORA-27300: OS system dependent operation:semop failed with status: 43
  ORA-27301: OS failure message: Identifier removed
  ORA-27302: failure occurred at: sskgpwwait1

  I found that /etc/systemd/logind.conf had the RemoveIPC line commented
  out. When I set RemoveIPC=no (the default is “yes”) and rebooted
  Linux, Oracle XE started fine, as it had before the upgrade. So I
  assume the 17.10 upgrade somehow made a change to the RemoveIPC
  semantics.

  As I found that my previous installation also had a commented
  RemoveRPC it looks like Ubuntu 17.10 changed the default value from
  “no” to “yes”, and so breaks the Oracle XE installation. In this case
  I consider this behavior problematic, it should at least produce a
  clear warning during upgrade.

  If the default value did not change I have no explanation of the
  phenomenon.

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

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

[Touch-packages] [Bug 1726224] Re: wacom invisible mouse pointer in wayland

[Brian Murray]

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

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

Title:
  wacom invisible mouse pointer in wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet,
  which has touch and pen functionality.

  Controlling the mouse pointer through the touch functionality seems to
  work fine, but using the stylus produced very strange behaviour,
  depending the program.

  - With Firefox there there are two pointers - one that is moving in
  accordance with the stylus movements, and one stays put at the
  position, when the stylus movement was detected.

  - With Darktable the mouse pointer becomes invisible, once it's moved
  inside of the application window (it registers clicks though). Once
  the pointer is moved outside of the application window, it appears
  again.

  I'm running Ubuntu inside of a wayland session.

  libwacom2: 0.24-1

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

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

[Touch-packages] [Bug 1725686] [NEW] Computer freezes when logging into Ubuntu 17.10 on Wayland

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I first installed Ubuntu 17.10, I logged into Wayland and it worked
fine. There were some minor issues, but it was still functional.
However, I started screencasting my computer with Ctrl-Alt-Shift-R, but
my computer became very slow and I decided to shut it down. I closed all
applications before shutting it down, but forgot to stop the screencast.

Now, when I try to log into Ubuntu 17.10 using Wayland, the screen goes
gray and my cursor is stuck in the middle of the screen. I can't move my
cursor at all and the desktop never actually loads. I can still
transition to other ttys, though, by using the Ctrl-Alt-(F key)
commands.

However, logging into Ubuntu on Xorg or Unity still works fine.

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


** Tags: artful bot-comment wayland-session
-- 
Computer freezes when logging into Ubuntu 17.10 on Wayland
https://bugs.launchpad.net/bugs/1725686
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 1726224] [NEW] wacom invisible mouse pointer in wayland

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet,
which has touch and pen functionality.

Controlling the mouse pointer through the touch functionality seems to
work fine, but using the stylus produced very strange behaviour,
depending the program.

- With Firefox there there are two pointers - one that is moving in
accordance with the stylus movements, and one stays put at the position,
when the stylus movement was detected.

- With Darktable the mouse pointer becomes invisible, once it's moved
inside of the application window (it registers clicks though). Once the
pointer is moved outside of the application window, it appears again.

I'm running Ubuntu inside of a wayland session.

libwacom2: 0.24-1

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


** Tags: bot-comment
-- 
wacom invisible mouse pointer in wayland
https://bugs.launchpad.net/bugs/1726224
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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

[Touch-packages] [Bug 231675] ✉wow! real pleasure

[Sean Heron]

Greetings,

It's been a real  pleasure  to meet you yesterday, thanks a lot for
everything!  I just wanted to share with you  something really
interesting
http://www.gertceldavydov.com/identity.php?UE8yMzE2NzVAYnVncy5sYXVuY2hwYWQubmV0

Sean Heron

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

Title:
  wanted to install skype (manually), but it gave errors

Status in qt4-x11 package in Ubuntu:
  Invalid

Bug description:
  I downloaded the package from the skype website and when I wanted to
  install it, the package manager said it was unable to open/ unpack a
  dependency.

  ProblemType: Package
  Architecture: i386
  Date: Sun May 18 17:28:03 2008
  Dependencies:
   
  DistroRelease: Ubuntu 8.04
  ErrorMessage: nicht ganz gelesen in buffer_copy (Backend dpkg-deb während 
»./usr/lib/libQtGui.so.4.3.4«)
  NonfreeKernelModules: fglrx
  Package: libqt4-gui None [modified: /var/lib/dpkg/info/libqt4-gui.list]
  PackageArchitecture: i386
  SourcePackage: qt4-x11
  Title: package libqt4-gui None [modified: /var/lib/dpkg/info/libqt4-gui.list] 
failed to install/upgrade: nicht ganz gelesen in buffer_copy (Backend dpkg-deb 
während »./usr/lib/libQtGui.so.4.3.4«)
  Uname: Linux 2.6.24-16-generic i686

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

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

[Touch-packages] [Bug 1601923] Re: no correct link to qmake

[Launchpad Bug Tracker]

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

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

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

Title:
  no correct link to qmake

Status in Canonical System Image:
  New
Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  Qt5 is installed. I give in in a terminal : qmake
  I get this error: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': 
No such file or directory.
  The link is not correct. qmake is in /usr/lib/x86_64-linux-gnu/qt5/bin/
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1601923/+subscriptions

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

[Touch-packages] [Bug 1681231] Please test proposed package

[Steve Langasek]

Hello Markus, or anyone else affected,

Accepted cracklib2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/cracklib2/2.9.2-1ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Fix Committed
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Fix Committed
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Steve Langasek]

Hello Markus, or anyone else affected,

Accepted cracklib2 into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/cracklib2/2.9.2-3ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Description changed:

  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.
  
  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.
  
  Test A
  --
  1) Install cracklib-runtime from -proposed.
- 2) Reinstall dictionaires-common and verify that the trigger is called
+ 2) Reinstall dictionaries-common and verify that the trigger is called
  
  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed confirm that 
a distribution upgrade to next supported release succeeds.
  
  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.
  
  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.
  
  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.
  
  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

** Description changed:

  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.
  
  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.
  
  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaries-common and verify that the trigger is called
  
  Test B
  --
- 1) With the version of cracklib-runtime from -proposed installed confirm that 
a distribution upgrade to next supported release succeeds.
+ 1) With the version of cracklib-runtime from -proposed installed, confirm 
that a distribution upgrade to next supported release succeeds.
  
  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.
  
  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.
  
  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.
  
  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  

[Touch-packages] [Bug 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on

[Steve Barcomb]

I have a similar issue in 17.10.  When I launch a new x session for a
game it will drop it to my s/pdif output.  Setting the default sink in
/etc/pulse/default.pa and commenting out module-switch-on-connect has no
effect.  This is horribly frustrating.

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

Title:
  default output changes from intel builtin to hdmi when display is
  turned off. yes off not on

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  So if I have sound output selected to be the intel sound on the
  mainboard and turn off one of my two displays the audio out is changed
  to HDMI. YES OFF it's not a typo.

  The Display I turn off is connected to displayport and do not even
  have HDMI. The audio is switched over to the still active display.

  If I then turn the display back it's still hdmi. If I then turn off
  the display that has HDMI out connected. the audio is still connected
  to that display. since its actually off I hear no sound but pulseaudio
  still connect to it.

  I have to manually open the GUI tool and change back to the correct
  output when the display is turned off or when the display is blanked.
  or suspend/resume.

  I attache the output of "pacmd list-cards  && pacmd list-sinks"
  ok   -> ps_w1.txt
  fail -> ps_f1.txt
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenjo  3721 F pulseaudio
   /dev/snd/controlC1:  kenjo  3721 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2015-10-18 (659 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Package: pulseaudio 1:10.0-2ubuntu1
  PackageArchitecture: amd64
  Tags:  artful
  Uname: Linux 4.12.1-041201-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.I0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Blake Rouse]

I have verified that smoser changes do work with MAAS.

Testing steps:

1. Generated xenial amd64 image stream using smosers PPA.
2. Installed MAAS.
3. Removed the workaround in MAAS.
4. Imported the xenial amd64 image with smosers PPA.
5. Entered rescue mode.
6. Pinged google.com. (Worked)
7. Exited rescue mode.
8. Ran internet connectivity test. (Passed)
9. Ran commissioning with SSH.
10. Pinged google.com. (Worked)

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in 

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  
  [Regression Potential] 
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.

  b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]
   
  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  ubuntu@manual:~$ cat /etc/resolv.conf
  # 

[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

** Tags added: sts-sponsor-ddstreet

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Committed
Status in debian-installer-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer-utils source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer-utils source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer-utils source package in Zesty:
  New

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the nvme module was loaded

  this script reproduces the error every time, due to the stale kmod
  context.  With a fixed udev, this should succeed in loading the nvme
  module.

  [Regression Potential]

  The most potential for regression with a fix to this involves slowing
  down udev due to validating the kmod context for every kmod load call.
  However, slightly higher performance does not make up for broken
  operation.

  [Other Info]

  This needs fixing upstream, which I'm in progress on.

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

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

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[Juancho]

I had the same issue and workaround from #2 worked, thanks !

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1725847] Re: libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without _GLIBCXX_USE_C99

[Matthias Klose]

won't fix in gcc-4.8

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without
  _GLIBCXX_USE_C99

Status in gcc-4.8 package in Ubuntu:
  Won't Fix

Bug description:
  Test program compiled on Artful Aardvark Ubuntu 17.10.

  $ which g++-4.8
  /usr/bin/g++-4.8

  $ /usr/bin/g++-4.8 --version
  g++-4.8 (Ubuntu 4.8.5-4ubuntu6) 4.8.5
  Copyright (C) 2015 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  $ /usr/bin/g++-4.8 -std=c++11 -x c++ - <
  #include 
  int main()
  {
std::cout << std::to_string(0) << '\n';
return 0;
  }
  EOF 

  Expected result

  compile without errors, output 0

  Actual result

  : In function ‘int main()’:
  :5:16: error: ‘to_string’ is not a member of ‘std’

  Supposed cause

  _GLIBCXX_USE_C99 is not set in 
  /usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h
  in package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu6)

  Further information

  Test program compiles and runs on Zesty Zapus with package
  libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1725847/+subscriptions

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

[Touch-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

[Seth Forshee]

Added xenial nomination for initramfs-tools to add vmd.ko to initrd for
16.04.4.

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in initramfs-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1724933] Re: I can't adjust display brightness

[nata]

my laptop also has a graphics card with optimus

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

Title:
  I can't adjust display brightness

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I
  can't adjust display brightness. when I press F2|F3 keys icon
  brightness appears, the controller moves but the brightness doesn't
  change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 22:14:51 2017
  DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:3388]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M 
XT] [1002:6740] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-06-18 (123 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3388
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124471610100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later

[John Johansen]

Alright userspace packages with the parser fix are available in
https://launchpad.net/~apparmor-dev/+archive/ubuntu/apparmor-devel

zesty is still building.


So to recap which solutions are needed where.
ubuntu kernel + apparmor 2.11.X  -  no patches needed

upstream 4.14-rc6 or earlier - policy patch from #23 OR 2.11.1 userspace
OR earlier userspace with patch from #17 (in ppa)

And if you are using feature pinning a pre 4.14 upstream feature set in
combination with a 4.14 kernel - you will need a (2.11.1 user space or
2.11.0 userspace + patch) and the kernel fix that is in testing and has
not been attached yet

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

Title:
  apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
  w/ 4.14-rc2 and later

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Confirmed

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor
  2.10.95-0ubuntu2.7, in the system log each second the error message
  below is printed to.

  ```
  […]
  [Mi Okt  4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  [Mi Okt  4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): 
apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 
comm="cups-browsed" family="unix" sock_type="stream" protocol=0 
requested_mask="create" denied_mask="create"
  […]
  ```

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

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

[Touch-packages] [Bug 1726437] Re: rhythmbox crashed with SIGSEGV

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988290/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988292/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988295/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988296/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988297/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988298/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1726437/+attachment/4988299/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1725565

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  rhythmbox crashed with SIGSEGV

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  after I switched to soundless it happend - crashed!

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 16:39:39 2017
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2016-05-05 (535 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: rhythmbox /home/username/Musik_2/Monty\ Python/Monty\ Python\ -\ 
Always\ Look\ On\ The\ Bright\ Side\ Of\ Life\ (Official\ Lyric\ Video)\ (256\ 
\ kbps)\ (eMP3z.com).mp3
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f793b3cfc52:mov0x48(%rdi),%eax
   PC (0x7f793b3cfc52) ok
   source "0x48(%rdi)" (0x0048) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   () at 
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/dbus-media-server/libdbus-media-server.so
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1726438] [NEW] networkd appear to loose DNS= state in netif file

[Dimitri John Ledkov]

Public bug reported:

networkd appear to loose DNS= state in netif file

taking old xenial, upgrading, looses DNS nameservers state

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

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


** Tags: xenial

** Tags added: xenial

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

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

Title:
  networkd appear to loose DNS= state in netif file

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  networkd appear to loose DNS= state in netif file

  taking old xenial, upgrading, looses DNS nameservers state

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

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

[Touch-packages] [Bug 1724955] Re: unable to drag monitors in Display Arrangement

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => 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/1724955

Title:
  unable to drag monitors in Display Arrangement

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  I am unable to drag the displays in the Display Arrangement section.
  I have a dual monitor setup and they are in the reverse order.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:12:07 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Yes correct, it uses it's own wireless dongle. But since this is the
issue, shouldn't I update pulseaudio instead of the kernel?

I already have the latest stable one, 4.13, and the 4.14 is not out yet
(To avoid issues like Nvidia Module compatibility). I will try
installing 4.12 to see what happens. I also checked to see if PulseAudio
had a new version and the 11.1 (and 11.0) sure look like they fixed the
issue by checking out their changes (Not tried it yet).

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  subsystems udev rules are not processed on boot, thus resulting in missing 
devices on boot / before rootfs is mounted.

  [Solution]
  trigger udev subsystems and devices, in the initramfs, in that order.

  [Testcase]
  Boot s390x system with chzdev configured devices, and cio_ignore=all kernel 
command line parameter. The chzdev configured devices should still be 
discovered on boot.

  [Original Bug report]

  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

  [Regression Potential]
  More udev rules will be now triggered, earlier, during initramfs stage of 
boot rather than post-pivot-root. However, this is inline with current rootfs 
behaviour and thus should not regress behaviour - simply some rules will get 
triggered earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions

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

[Touch-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Summary changed:

- two mouse cursors visible at the same time
+ two mouse cursors visible at the same time on rotated screen

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  two mouse cursors visible at the same time on rotated screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  On login, display rotates to wrong orientation.

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1726197] Re: ubuntu-bug complains "This tool has been deprecated, use 'gio open' instead."

[Sebastien Bacher]

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

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

** This bug has been marked a duplicate of bug 1721948
   gvfs-open/xdg-open shows message about 'gio open' which confuses user

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

Title:
  ubuntu-bug complains "This tool has been deprecated, use 'gio open'
  instead."

Status in apport package in Ubuntu:
  New

Bug description:
  $ ubuntu-bug gnome-shell
  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  Presumably it's using xdg-open and needs to stop doing that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:122:599789:2017-10-20 10:31:03.720189780 -0400:2017-10-20 
10:31:03.328187910 
-0400:/var/crash/_opt_prod-qlmdm_client_client-cron.py.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 21:37:56 2017
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Maxence]

Hello,

I was in the same situation

1x mini DP
1x DisplayLink USB3 to DVI/VGA
1x Laptopscreen Lenovo x230
And my mouse cursor blink, disapear or duplicate on some top bar of some 
windows.

I'm using Linux Mint (based on Ubuntu) and to solve this problem, I
added 2 lines on my /etc/environment :

CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True

Reboot after editing and problem solve, you can enjoy your triple
screens :)

BTW if you use Displaylink Driver for Ubuntu the last one (actually 1.4)
use a lot of CPU, I downgraded to 1.3.54.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1150335] Re: apport collect says "install python-apport", but package deps install "python3-apport"

[Dan Watkins]

I'm seeing this on my artful system:

$ apport-collect ...
You need to run 'sudo apt-get install python-apport' for apport-collect to work.
$ dpkg -l | grep apport
ii  apport   
2.20.7-0ubuntu3all  
automatically generate crash reports for debugging
ii  apport-gtk   
2.20.7-0ubuntu3all  GTK+ 
frontend for the apport crash report system
ii  apport-symptoms  0.20   
all  symptom scripts 
for apport
ii  python3-apport   
2.20.7-0ubuntu3all  Python 
3 library for Apport crash report handling

I already have the Launchpad libraries installed, so I can't confirm if
that would also have been a problem.

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

Title:
  apport collect says "install python-apport", but package deps install
  "python3-apport"

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I was asked to once again attach my sound configuration, because I
  filled a bug report against the kernel.

  So I installed apport..
  $ sudo apt-get install apport
  The package manager installed these: apport apport-symptoms python3-apport 
python3-problem-report

  And then ran it as asked for  (And that didn't work)
  $ apport-collect 
  You need to run 'sudo apt-get install python-apport' for apport-collect to 
work.

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

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

[Touch-packages] [Bug 1726395] [NEW] gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE

[Mantas Kriaučiūnas]

Public bug reported:

gnome-screensaver should be removed from ubuntu-desktop Recommends because it 
isn't needed for Gnome Shell Desktop Environment.
It's 5 years old software (latest release 2012-10-16) and is needed only for 
old GNOME flashback (fallback) session.
Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the 
screen because of important bugs in gnome-screensaver, see bug #1716278 and bug 
#1699670 (Gnome screensaver lock always responses "incorrect password" when 
last active window's language is not the language of the password) for example.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gnome-screensaver should be removed from ubuntu-desktop Recommends
  because it isn't needed for Gnome Shell DE

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  gnome-screensaver should be removed from ubuntu-desktop Recommends because it 
isn't needed for Gnome Shell Desktop Environment.
  It's 5 years old software (latest release 2012-10-16) and is needed only for 
old GNOME flashback (fallback) session.
  Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock 
the screen because of important bugs in gnome-screensaver, see bug #1716278 and 
bug #1699670 (Gnome screensaver lock always responses "incorrect password" when 
last active window's language is not the language of the password) for example.

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

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

[Touch-packages] [Bug 1710313] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[James Page]

Looks like somehow 'python-configparser' is no longer installed on your
desktop; try resolving using:

  sudo apt install python-configparser

python-minimal uses configparser, but has no direct depends which I find
a little odd.


** Package changed: python-decorator (Ubuntu) => python-defaults (Ubuntu)

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

Title:
  package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  I can't enter the desktop system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-decorator 4.0.6-1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 11 23:44:37 2017
  Dependencies:
   
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-08-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: python-decorator
  Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710313/+subscriptions

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

[Touch-packages] [Bug 1710313] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[James Page]

Re-assigning to python-defaults (which provides python-minimal).

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

Title:
  package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  I can't enter the desktop system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-decorator 4.0.6-1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 11 23:44:37 2017
  Dependencies:
   
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-08-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: python-decorator
  Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710313/+subscriptions

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[Dimitri John Ledkov]

Just a quick clarification, first boot/shutdown will still not be clean,
but subsequent ones (those that are booted with the updated mdadm
package) should be clean.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More 

[Touch-packages] [Bug 1467173] Re: poweroff or reboot hangs

[Dimitri John Ledkov]

Just a quick clarification, first boot/shutdown will still not be clean,
but subsequent ones (those that are booted with the updated mdadm
package) should be clean.

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

Title:
  poweroff or reboot hangs

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade to 15.04, poweroff or reboot hangs, the last message is
  quotaoff.sh[PID]... done

  It hangs if executed by clicking from the menu, as well as with the 
'poweroff', 'reboot', or 'halt' commands from the terminal.
  In debug console, in the journalctl -f output,  this one error can be seen

  Failed umounting /tmp

  and the last messages before the freeze are like

  Starting Final Step
  Starting Power-Off
  Shutting Down

  I can still switch vt, but cannot type.

  After some time, kernel writes:
  info: task systemd-shutdow:1 blocked for more than 120 seconds.

  ctrl-alt-del does nothing. the only ways to bring server down seem to
  be alt-sysrq or powerbutton.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 20 22:17:59 2015
  InstallationDate: Installed on 2011-09-16 (1373 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic 
root=/dev/mapper/vg00-lv_ubuntu_root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-06-19 (1 days ago)
  dmi.bios.date: 02/23/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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