[Touch-packages] [Bug 1389813] Re: package grub-common 2.02~beta2-15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Anton Alexandrenok]

Affects my Ubuntu 17.10 (x86_64 Linux 4.13.0-32-generic) on installing
grub-common (2.02~beta3-4ubuntu7.1)

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

Title:
  package grub-common 2.02~beta2-15 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in insserv package in Ubuntu:
  Confirmed

Bug description:
  just tried to upgrade and got this

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: grub-common
  ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  Date: Wed Nov  5 15:38:34 2014
  DuplicateSignature: package:grub-common:2.02~beta2-15:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-02-16 (626 days ago)
  InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=2665a74f-e44f-4589-8554-2c954223116f ro quiet splash vt.handoff=7
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-15 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-11-05 (0 days ago)

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

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Daniel van Vugt]

** Description changed:

  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
- /var/crash files).
+ /var/crash files). This issue was first mentioned in bug 1746653. But
+ then I noticed my machine doing it too...
  
  This is despite:
  
  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0
  
  So really there are two problems:
  
  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:
  
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
-  640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
-  640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
-  640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
-  640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
-  640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
+  640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
+  640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
+  640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
+  640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
+  640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 

[Touch-packages] [Bug 1747412] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1742403
   package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to 
install/upgrade: installed network-manager-config-connectivity-ubuntu package 
post-installation script subprocess returned error exit status 1

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: sub-processo script post-installation
  instalado retornou estado de saída de erro 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  This issue happened when i tried to update.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb  5 09:54:10 2018
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-05-28 (252 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.0.1 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.100 metric 
100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  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.1
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: sub-processo script post-installation instalado 
retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME   UUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexão cabeada 1  e9be19de-58c5-300b-8d8c-7c5a5c25ded5  802-3-ethernet  
1517832180  seg 05 fev 2018 10:03:00 -02  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexão cabeada 1  e9be19de-58c5-300b-8d8c-7c5a5c25ded5  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   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/1747412/+subscriptions

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

[Touch-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll

[Reuben Lifshay]

https://bugs.freedesktop.org/show_bug.cgi?id=104960

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

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

Title:
  Razer Naga Chroma wheel tilt being remapped to vertical scroll

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7)
  are being remapped to scroll up and down (buttons 4, and 5) as per
  xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems

   Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  7 14:25:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1303]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 5986: Acer, Inc
   Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04nRSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.version: galp2
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80-1~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  7 14:21:19 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Kai-Heng Feng]

ryan,

Can you attach the output of `find /sys/devices -name 
'link_power_management_policy' | xargs grep .`?
Thanks!

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts 

[Touch-packages] [Bug 1736858] Re: package python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Launchpad Bug Tracker]

[Expired for libxml2 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 127

Status in libxml2 package in Ubuntu:
  Expired

Bug description:
  can't install it

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  Date: Thu Dec  7 12:47:53 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-12-03 (3 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
127
  UpgradeStatus: Upgraded to zesty on 2017-12-04 (2 days ago)

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Gunnar Hjalmarsson]

I'm on a slippery slope here; should probably have kept quiet. But it
was your mentioning of qt which triggered me to post a couple of
comments, since people tend to use some qt apps also in Ubuntu.

Anyway, my view in comment #1 still stands. ;)

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Jeremy Bicha]

Gunnar, could you test the apps before saying we need Symbola?

Firefox, Chromium, and LibreOffice don't need Symbola. Firefox uses an
embedded version of EmojiOne currently. Chromium will probably
eventually support Noto.

See https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492/23 and
24 for some relevant upstream bug report links.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1747421] Re: Bluetooth does not start

[Daniel van Vugt]

It appears you have recurring "pcieport" errors in your kernel log (see
CurrentDmesg.txt and JournalErrors.txt).

This looks like a hardware fault (I've had the same issue myself... with
a faulty PCIe card slot). But in case it's not a hardware fault, let's
start by assigning the issue to the Linux kernel.

P.S. You will also need to have package 'linux-firmware' installed. So
in case that makes a difference, please try 'sudo apt install linux-
firmware' and then reboot.


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

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

** Summary changed:

- Bluetooth does not start
+ Bluetooth does not start (and also recurring "pcieport :00:1c.5: PCIe Bus 
Error: ")

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

Title:
  Bluetooth does not start (and also recurring "pcieport :00:1c.5:
  PCIe Bus Error: ")

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth does not start turn it on and notting happens 
  i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


  
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
  14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
  14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
  14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@Laurentiu:/home/laufer# apt-cache policy bluez
  bluez:
Installed: 5.46-0ubuntu3
Candidate: 5.46-0ubuntu3
Version table:
   *** 5.46-0ubuntu3 500
  500 http://ro.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  root@Laurentiu:/home/laufer#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb  5 15:00:42 2018
  InstallationDate: Installed on 2018-02-04 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=87b1ca1a-1586-47e4-83a2-c81e7e67ca79 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.304:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 64:6E:69:20:D4:7E  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1225 acl:0 sco:0 events:122 errors:0
TX bytes:23230 acl:0 sco:0 commands:124 errors:0

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Gunnar Hjalmarsson]

Also Ubuntu users install qt apps, don't they? And FF and LO are
important exceptions. The archive size of fonts-symbola is 1.2 MiB.

How about including both in desktop-common for now?

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Daniel van Vugt]

In case it's not clear to all readers yet; Xwayland and gnome-shell are
co-dependent processes. If one crashes then the other will also crash.
So we need apport to be capable of handling both crashes simultaneously.

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: linux (Ubuntu)

** No longer affects: mutter (Ubuntu)

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

@ddstreet

Could you please review V3 again?

Thanks in advance!

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

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

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

[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

For V3.

It seems that g_variant_unref(value); part is needed.

Added it again and no memory leaks.

in g_variant_lookup_value, it calls g_variant_get_child_value

so as you said. it need to be unref value as well i think.

Thanks.

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Jeremy Bicha]

Gunnar, Kubuntu and Lubuntu Next are free to install fonts-symbola if
they want. (But they should really talk to Qt about getting color emoji
support working everywhere too!)

The benefit of installing Noto Color Emoji by default is so that color
emoji will work out of the box with any GTK+ app (with a few exceptions
like Chromium, Firefox and LibreOffice). Color Emoji is advertised as an
Ubuntu 18.04 LTS feature.

The benefit of not installing Symbola by default is that it's unneeded.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1741473] Re: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:am

[Launchpad Bug Tracker]

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

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

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

Title:
  package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a
  tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está
  no pacote libdrm-amdgpu1:amd64
  2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1

Status in libdrm package in Ubuntu:
  Confirmed

Bug description:
  automatic login

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdrm-common 2.4.83-1~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan  3 15:20:41 2018
  Dependencies:
   
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgTerminalLog:
   A preparar para desempacotar .../libdrm-common_2.4.83-1~16.04.1_all.deb ...
   A descompactar libdrm-common (2.4.83-1~16.04.1) ...
   dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libdrm-common_2.4.83-1~16.04.1_all.deb (--unpack):
a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no 
pacote libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1
  ErrorMessage: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que 
também está no pacote libdrm-amdgpu1:amd64 
2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1
  GraphicsCard:
   Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [8086:2042]
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
  InstallationDate: Installed on 2017-04-10 (269 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=2ecae89c-893b-4efc-b110-7c907b246eb6 ro quiet splash nomodeset 
acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libdrm
  Title: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a 
tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote 
libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HOH6110H.86A.0011.2012.0530.1036
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61HO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG62445-103
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0011.2012.0530.1036:bd05/30/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-103:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 10:45:50 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button 

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Simon Quigley]

I agree with Gunnar, I'm -1 with both my Lubuntu and Kubuntu hats on if
this means a regression for Qt-based desktops.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Gunnar Hjalmarsson]

If qt does not support fonts-noto-color-emoji, replacing would be a
regression, especially for Kubuntu, and may not be a good idea. I
understand that the packages don't conflict to each other. What's the
drawback with keeping it as is for now, and install both packages in
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/1746310

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Christopher M. Penalver]

** Attachment removed: ""nouveau" related entries in "kern.log""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.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/1649566

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed on 2013-01-21 (1838 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro 

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[ryan eckenrode]

I can confirm this fix worked for me.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged laptop-mode-tools the system starts successfully
  on battery.

  The user installed a fresh instance of 17.10 on a 2nd M2 

[Touch-packages] [Bug 1747333] Re: apparmor rules deny lease backup

[Seth Arnold]

These are not AppArmor messages. AppArmor messages clearly say
apparmor="DENIED" or apparmor="ALLOWED" or similar.

Audit message 1702 is generated when an application trips a link restriction 
denial:
https://github.com/torvalds/linux/blob/master/kernel/audit.c#L2254

The "linkat" version of the message comes from:
https://github.com/torvalds/linux/blob/master/fs/namei.c#L968

If you want to enable the unsafe hardlink behaviour you can set a sysctl
to do so. (This is a homework problem left for the reader.)

Audit message 1302 reports a filename:
https://github.com/torvalds/linux/blob/master/include/uapi/linux/audit.h#L89

Since this is the next audit record after the 1702 message, I believe
this is just reporting *which* file was involved in the previous unsafe
link behaviour.

Thanks

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

Title:
  apparmor rules deny lease backup

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  
  Occasionally, I see this in my logs:

  Feb  4 02:27:07 giskard2 dhcpd[11485]: Can't backup lease database
  /var/lib/dhcp/dhcpd.leases to /var/lib/dhcp/dhcpd.leases~: Operation
  not permitted

  Feb  4 02:27:07 giskard2 kernel: [237980.192671] audit: type=1702 
audit(1517711227.717:14): op=linkat ppid=1 pid=11485 auid=4294967295 uid=111 
gid=121 euid=111 suid=111 fsuid=111 egid=121
  sgid=121 fsgid=121 tty=(none) ses=4294967295 comm="dhcpd" 
exe="/usr/sbin/dhcpd" res=0

  Feb  4 02:27:07 giskard2 kernel: [237980.192686] audit: type=1302 
audit(1517711227.717:15): item=0 name="/var/lib/dhcp/dhcpd.leases" 
inode=3932557 dev=08:01 mode=0100644 ouid=0 ogid=121
  rdev=00:00 nametype=NORMAL cap_fp= cap_fi= 
cap_fe=0 cap_fver=0

  
  Essentially indicating that the apparmor profile has declined to allow a 
backup leases file to be created. However, the files does appear to be created. 
I am unsure why the message is being logged (is the file being created 
correctly? -- I do not know enough of dhcpd to tell).

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  
  # dpkg -l | grep dhcp
  ii  isc-dhcp-client 4.3.3-5ubuntu12.7 
 amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common 4.3.3-5ubuntu12.7 
 amd64common files used by all of the isc-dhcp packages
  ii  isc-dhcp-server 4.3.3-5ubuntu12.7 
 amd64ISC DHCP server for automatic IP address assignment
  ii  wide-dhcpv6-client  20080615-16   
 amd64DHCPv6 client for automatic IPv6 hosts configuration

  # dpkg -l | grep apparmor
  ii  apparmor2.10.95-0ubuntu2.7
 amd64user-space parser utility for AppArmor
  ii  apparmor-utils  2.10.95-0ubuntu2.7
 amd64utilities for controlling AppArmor
  ii  libapparmor-perl2.10.95-0ubuntu2.7
 amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.10.95-0ubuntu2.7
 amd64changehat AppArmor library
  ii  python3-apparmor2.10.95-0ubuntu2.7
 amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.10.95-0ubuntu2.7
 amd64AppArmor library Python3 bindings

  # ls -la /var/lib/dhcp
  total 16
  drwxrwsr-x  2 root dhcpd 4096 Feb  5 01:57 .
  drwxr-xr-x 52 root root  4096 Oct  3  2016 ..
  -rw-r--r--  1 root dhcpd 1003 Feb  5 02:27 dhcpd.leases
  -rw-r--r--  1 root dhcpd 1631 Feb  5 01:57 dhcpd.leases~

  
  # find /etc/apparmor
  /etc/apparmor
  /etc/apparmor/init
  /etc/apparmor/init/network-interface-security
  /etc/apparmor/init/network-interface-security/sbin.dhclient
  /etc/apparmor/init/network-interface-security/usr.sbin.ntpd
  /etc/apparmor/severity.db
  /etc/apparmor/parser.conf
  /etc/apparmor/logprof.conf
  /etc/apparmor/subdomain.conf

  # find /etc/apparmor.d/
  /etc/apparmor.d/
  /etc/apparmor.d/usr.sbin.dhcpd
  /etc/apparmor.d/sbin.dhclient
  /etc/apparmor.d/usr.sbin.rsyslogd
  /etc/apparmor.d/usr.sbin.tcpdump
  /etc/apparmor.d/usr.sbin.named
  /etc/apparmor.d/abstractions
  /etc/apparmor.d/abstractions/ubuntu-helpers
  /etc/apparmor.d/abstractions/kde
  /etc/apparmor.d/abstractions/dbus-session
  /etc/apparmor.d/abstractions/nis
  /etc/apparmor.d/abstractions/base
  /etc/apparmor.d/abstractions/apparmor_api
  /etc/apparmor.d/abstractions/apparmor_api/examine
  /etc/apparmor.d/abstractions/apparmor_api/introspect
  

[Touch-packages] [Bug 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
  as the Schenker XMG U507, the System76's Serval WS (2017 model), the
  Eurocom Sky X4E2, among others.

  The sound card is the Realtek ALC898 with the following output
  configuration:

  1. One SPDIF/headphone combo jack (to the right)
  2. One Line Out.
  3. One Line-In.
  4. One Mic-In.

  Background information:

  On Windows, one can use the Realtek HD Audio control panel pop-up menu
  on jack detection to set the output type when an audio device is
  plugged in to an appropriate jack, combined with Sound Blaster X-Fi
  MB5 software to enable post-processing effects such as Bass, noise
  cancellation, etc.

  What I have tried so far:

  1. Setting the model definition at /etc/modprobe.d/sound.conf with the
  following entries:

  options snd-hda-intel model=no-primary-hp enable=1 index=0

  Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
  also has the same (or a similar) ESS Sabre Audio DAC component.

  Expected behavior:

  When plugged into the microphone jack, the ESS Sabre DAC should be
  activated and sound should be routed to the headset.

  Observed anomaly:

  Sound comes out through the speakers instead.

  However, the line-out output works. In that case, when plugged into
  the line out, Audio works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.14.0 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lin2199 F pulseaudio
   /dev/snd/controlC0:  lin2199 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Nov 13 17:34:53 2017
  InstallationDate: Installed on 2017-07-25 (111 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1812 F pulseaudio
lin2199 F pulseaudio
   /dev/snd/controlC0:  gdm1812 F pulseaudio
lin2199 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.06.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxDM2(-G)
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxDM2(-G)
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

> 3) As per your snipped log, it looks like you are grabbing logs from your 
> install. What is 
> needed are the logs/video from booting 
> http://cdimage.ubuntu.com/daily-live/current/.

You are right. All attachments come from the installation, not the
"current" Ubuntu.

I see no chance to get the DVD debugged: the failure is very early -
likely immediately after the BIOS has passed control to the DVD.
"https://wiki.ubuntu.com/DebuggingKernelBoot; remains unapplicable, as
no boot loader is involved (which would allow me to set boot parameters)
or as the problem already occurs before the loader on the DVD gets
activated.

Likely, something went wrong with burning the DVD. I will try (probably
tomorrow) to burn with a different device (I already tried with 2
different DVDs to exclude media failures).

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
 

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

** Attachment added: "Full dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049379/+files/dmesg

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed on 2013-01-21 (1838 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro nouveau.config=NvMSI=0
  

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

** Attachment added: "Full "kern.log""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049380/+files/kern.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/1649566

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed on 2013-01-21 (1838 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro nouveau.config=NvMSI=0
  

[Touch-packages] [Bug 1725351] Re: Systemd - Remote DOS of systemd-resolve service

[Marc Deslauriers]

Hello. Yes, USN-3558-1 included the fix for Ubuntu 16.04 LTS for
environments where systemd-resolved is manually enabled. Thanks.

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

Title:
  Systemd - Remote DOS of systemd-resolve service

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Hello,

  We would like to report a vulnerability about systemd which allows to
  DOS the systemd-resolve service.

  The vulnerability is described in the attached PDF file.

  Sincerely,
  Thomas IMBERT
  Sogeti ESEC R

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

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

[Touch-packages] [Bug 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility

[Eric G]

Still seems to be a problem for 16.04.

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

   Jan  5 08:56:16 simon-laptop rsyslogd-: command
  'KLogPermitNonKernelFacility' is currently not permitted - did you
  already set it via a RainerScript command (v6+ config)? [v8.14.0 try
  http://www.rsyslog.com/e/ ]

  Error  is described as "legacy parameter no longer permitted".

  This legacy parameter causes config syntax checks (rsyslogd -N1) to
  fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.14.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  6 15:47:15 2016
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

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

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

[Touch-packages] [Bug 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work

[Eric G]

Still seems to be a problem for 16.04.

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

Title:
  New style permitnonkernelfacility imklog option inside module()
  doesn't work

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw)

  There are two ways to load the imklog module and pass it an option
  (PermitNonKernelFacility in this case).

  a) legacy
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  
  b) "new style", also referred to as "v6+":
  module(load="imklog" permitnonkernelfacility="on")

  For a while the ubuntu package was using a mix: loading the module
  with the new style, but setting the option via the legacy method. In
  bug #1531622 this was fixed for yakkety+.

  Problem is, upstream isn't honouring the new style option setting due
  to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477

  With the legacy config:
  #module(load="imklog" permitnonkernelfacility="on")
  $ModLoad imklog
  $KLogPermitNonKernelFacility on

  I get kernel messages in /var/log/syslog:
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  root@nsn7:~# echo andreas-was-here > /dev/kmsg
  root@nsn7:~# grep andreas-was-here /var/log/syslog
  Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
  root@nsn7:~#

  But with this new v6 config style:
  module(load="imklog" permitnonkernelfacility="on") # provides kernel logging 
support
  #$ModLoad imklog
  #$KLogPermitNonKernelFacility on

  The text doesn't show up in /var/log/syslog. That's the upstream bug.

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

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

[Touch-packages] [Bug 1725351] Re: Systemd - Remote DOS of systemd-resolve service

[David Glasser]

@mdeslaur: Should I interpret the release of
https://usn.ubuntu.com/usn/usn-3558-1/ as saying that the answer to my
question in comment 19 is that yes, now we are getting the response?

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

Title:
  Systemd - Remote DOS of systemd-resolve service

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Hello,

  We would like to report a vulnerability about systemd which allows to
  DOS the systemd-resolve service.

  The vulnerability is described in the attached PDF file.

  Sincerely,
  Thomas IMBERT
  Sogeti ESEC R

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

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

[Touch-packages] [Bug 1745810] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

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

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sun Jan 28 00:49:05 2018
  ErrorMessage: triggers looping, abandoned
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=5d3f26c9-f26e-4726-b062-a1cb855198e5 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [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
   
   3 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-27 (0 days ago)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Christopher M. Penalver]

Dieter Maurer:
1) Regarding logs, please don't cut, snip, extract, etc. Attach them in full.

2) To advise, please post dmesg in full.

3) As per your snipped log, it looks like you are grabbing logs from
your install. What is needed are the logs/video from booting
http://cdimage.ubuntu.com/daily-live/current/ .

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed on 2013-01-21 (1838 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Touch-packages] [Bug 1746947] Re: failing autopkgtest due to password issue by nss

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 2:3.35-2ubuntu2

---
nss (2:3.35-2ubuntu2) bionic; urgency=medium

  * d/p/lp1746947-revert-switch-default-to-sql.patch: the switch of the
default is still causing too much issues in consumers of nss.
So until resolved revert the switched default (LP: #1746947)

nss (2:3.35-2ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- When building with -O3, build with -Wno-error=maybe-uninitialized.
  * Added Changes:
- d/libnss3.links: make freebl3 available as library (LP: #1744328)
  + d/control: add dh-exec to Build-Depends
  + d/rules: make mkdir tolerate debian/tmp existing (due to dh-exec)

nss (2:3.35-2) unstable; urgency=medium

  * nss/lib/freebl/Makefile: Build Hacl_Poly1305_64.o on arm64.

nss (2:3.35-1) unstable; urgency=medium

  * New upstream release.

nss (2:3.34.1-1) unstable; urgency=medium

  * New upstream release.

 -- Christian Ehrhardt   Mon, 05 Feb
2018 11:36:07 +0100

** Changed in: nss (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  failing autopkgtest due to password issue by nss

Status in freeipa package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  I was failed by autopkgtests of freeipa, but not the old "ip route output 
changed" case.
  Like: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/f/freeipa/20180201_161632_c9091@/log.gz

  It essentially does this and fails:
  $ apt install freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib python-ipaserver python-ipatests

  Containers:
  Bionic-as-is: installs ok
  Bionic-Proposed: installs ok

  In LP Infra:
  dpkg: error processing package freeipa-client (--configure):
   installed freeipa-client package post-installation script subprocess 
returned error exit status 1

  Use Pinning to get the autopkgtest style:
  # cat /etc/apt/preferences.d/nssonlyproposed
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  Package: libnss3 libnss3-tools libnss3-dev libnss3-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 1002
  Bionic-nss-only-from-Proposed: TRIGGERS the issue

  freeipa-client is in the postinst calling this:
  python2 -c 'from ipapython.certdb import update_ipa_nssdb; update_ipa_nssdb()'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 64, in 
update_ipa_nssdb
  create_ipa_nssdb()
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 53, in 
create_ipa_nssdb
  db.create_db(pwdfile)
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 149, in 
create_db
  self.run_certutil(["-N", "-f", password_filename])
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 142, in 
run_certutil
  return ipautil.run(new_args, stdin, **kwargs)
File "/usr/lib/python2.7/dist-packages/ipapython/ipautil.py", line 515, in 
run
  raise CalledProcessError(p.returncode, arg_string, str(output))
  subprocess.CalledProcessError: Command '/usr/bin/certutil -d /etc/ipa/nssdb 
-N -f /etc/ipa/nssdb/pwdfile.txt' returned non-zero exit status 255

  
  That is - if called alone complaining about the passwd:
  # /usr/bin/certutil -d /etc/ipa/nssdb -N -f /etc/ipa/nssdb/pwdfile.txt
  Invalid password.
  certutil: Could not set password for the slot: SEC_ERROR_BAD_PASSWORD: The 
security password entered is incorrect.

  
  Note that there is a related freeipa fix in later versions:
 freeipa (4.6.2-4) unstable; urgency=medium 
  

  
   * client.postinst: Migrate from old nssdb only if it exists.

  And since that change freeipa has:
  if [ -f /etc/ipa/nssdb/cert8.db ]; then
  around the call.

  It also changed the import slightly - now the python being:

  python2 -c 'from ipaclient.install.client import update_ipa_nssdb;
  update_ipa_nssdb()'

  That in the "all-proposed" case with the cert8.db file copied over is still 
failing but differently:
  /usr/bin/certutil -d /etc/ipa/nssdb -L -f /etc/ipa/nssdb/pwdfile.txt
  certutil: function failed: SEC_ERROR_BAD_DATABASE: security library: bad 
database.

  The merge of nss was a minor bump 3.34->3.35
  Also this is the nss version from Debian with the freeipa version from 
Debian. They seem to work together there.

  I don't fully understand it yet - so filing this bug for a discussion.
  I need the help of tjaalton who did the freeipa changes - maybe he knows what 
is going on.

  Do 

[Touch-packages] [Bug 1744328] Re: libfreebl3.so should be public, not in the nss subdir

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 2:3.35-2ubuntu2

---
nss (2:3.35-2ubuntu2) bionic; urgency=medium

  * d/p/lp1746947-revert-switch-default-to-sql.patch: the switch of the
default is still causing too much issues in consumers of nss.
So until resolved revert the switched default (LP: #1746947)

nss (2:3.35-2ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- When building with -O3, build with -Wno-error=maybe-uninitialized.
  * Added Changes:
- d/libnss3.links: make freebl3 available as library (LP: #1744328)
  + d/control: add dh-exec to Build-Depends
  + d/rules: make mkdir tolerate debian/tmp existing (due to dh-exec)

nss (2:3.35-2) unstable; urgency=medium

  * nss/lib/freebl/Makefile: Build Hacl_Poly1305_64.o on arm64.

nss (2:3.35-1) unstable; urgency=medium

  * New upstream release.

nss (2:3.34.1-1) unstable; urgency=medium

  * New upstream release.

 -- Christian Ehrhardt   Mon, 05 Feb
2018 11:36:07 +0100

** Changed in: nss (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 nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  Fix Released
Status in nss package in Debian:
  New

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Jeremy Bicha]

** Description changed:

  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).
  
  It's a transitional package now depending on fonts-symbola.
  
  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."
  
  It was added to the seeds in LP: #1137630 explicitly for emoji support.
  
  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.
  
  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.
  
  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB
  
  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?
  
  The only other Color Emoji font I expect to be available in Ubuntu soon
  is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.
+ 
+ Screenshots of Noto Color Emoji and EmojiTwo are at
+ https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492
+ 
+ ubuntu-release list proposal:
+ https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

  Screenshots of Noto Color Emoji and EmojiTwo are at
  https://community.ubuntu.com/t/try-color-emoji-in-18-04/1492

  ubuntu-release list proposal:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004276.html

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

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

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

** Attachment added: ""nouveau" related entries in "kern.log""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.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/1649566

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed on 2013-01-21 (1838 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: i386
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro 

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

> Then please post the results requested in
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/comments/21
> so it may be reviewed.

Comment 21:
>> If still reproducible, please post results following:

>> https://wiki.ubuntu.com/DebuggingKernelBoot
This is not applicable as booting is successful

>> https://wiki.ubuntu.com/DebuggingSystemCrash
I reproduced the crash and tried "Alt+SysRq+1" followed by "Alt+SysRq+t".
As the display was frozen with the blue-white pattern I did not see a 
traceback. After reboot,
I found in "kern.log":

Feb  5 19:05:10 localhost kernel: [ 4756.501608] nouveau :00:0d.0: bus: 
MMIO write of 01b20001 FAULT at 00b020
Feb  5 19:05:11 localhost kernel: [ 4758.190584] nouveau :00:0d.0: bus: 
MMIO write of  FAULT at 00b020
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb
  5 19:07:22 localhost kernel: [0.00] Initializing cgroup subsys cpuset

I see many further "MMIO write of  FAULT at 00b0[12]0" in "kern.log"
(I will attach the extract of "nouveau" messages from "kern.log").

Obiously, the kernel is in a very bad state. Do you see a good chance
that a crash kernel would get activated in the situation above?

> Did you checksum the ISO you downloaded?
Yes

> If so and it passed, you can make an ISO of what you burned and checksum this 
> to confirm it burned correctly via a terminal:
> sudo dd if=/dev/sdX of=file.iso

Surprisingly "sudo dd if=/dev/sr0 of=file.iso" ("sr0" corresponds to my DVD 
drive)
resulted in a much larger "file.iso" than the original Ubuntu ISO file (I 
aborted the copy after "file.iso" grew up to about 2.7 GB (the Ubuntu ISO is 
about 1.5 GB)).
When I mount the burned ISO file, the "properties" menu and "du -s" tell me the 
correct size (thus, the "dd" copy may do something wrong).

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x 

[Touch-packages] [Bug 1747487] [NEW] Sonido

[luis Rodriguez]

Public bug reported:

No me reproduce sonido

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb  5 12:24:37 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0767]
InstallationDate: Installed on 2018-01-14 (21 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 5567
ProcEnviron:
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 01W6F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Feb  5 12:20:03 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1317 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  Sonido

Status in xorg package in Ubuntu:
  New

Bug description:
  No me reproduce sonido

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb  5 12:24:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-01-14 (21 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5567
  ProcEnviron:
   LANGUAGE=es_CR:es
   PATH=(custom, no user)
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1311503] Re: compiz crashes with segfault error in libnux-graphics

[James Deck]

Echoing WHK's comment.

"apt-get -y reinstall libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgdk-
pixbuf2.0-common && reboot" solved the problem.

uname
Linux fcs-server 4.4.0-112-generic #135~14.04.1-Ubuntu SMP Tue Jan 23 20:41:48 
U 

lspci
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] [1002:6778] (prog-if 
00 [VGA controller])

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

Title:
  compiz crashes with segfault error in libnux-graphics

Status in Nux:
  Invalid
Status in nux package in Ubuntu:
  Invalid

Bug description:
  When I login compiz crashes with a segfault error in libnux-graphics.
  My screen turns blue (with nouveau driver) or with white blocks
  (nvidia current driver). In dmesg the following messages are shown:

  [  808.965220] compiz[7568]: segfault at b0 ip 7f9246244a0f sp 
7fff0a7a1450 error 4 in libnux-graphics-4.0.so.0.6.0[7f92461f8000+cb000]
  [  813.851368] compiz[7722]: segfault at b0 ip 7f34215bca0f sp 
7fffe2e356d0 error 4 in libnux-graphics-4.0.so.0.6.0[7f342157+cb000]

  I only get this error with my Nvidia GTX 460 card. I do not get these
  errors with my radeon and intel video cards (my other pc and laptop).
  All running latest Trusty 14.04.

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

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

[Touch-packages] [Bug 1747476] [NEW] apport-collect needs python-qtpy and python-apport dependency issue on kubuntu

[Peridot]

Public bug reported:

apport-collect did not work until both packages were installed. The
errors you get are not helpful and I only arrived at this solution after
searching around online and basically wild guessing.

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

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

Title:
  apport-collect needs python-qtpy and python-apport dependency issue on
  kubuntu

Status in apport package in Ubuntu:
  New

Bug description:
  apport-collect did not work until both packages were installed. The
  errors you get are not helpful and I only arrived at this solution
  after searching around online and basically wild guessing.

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

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Brian Murray]

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

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

** Tags added: rls-bb-incoming

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1368911] Re: Apport crashes when writing to stderr: UnicodeEncodeError: 'ascii' codec can't encode character '\xc1' in position 130: ordinal not in range(128)

[Peridot]

This bug is still there on bionic dailies and the patch still works.

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

Title:
  Apport crashes when writing to stderr: UnicodeEncodeError: 'ascii'
  codec can't encode character '\xc1' in position 130: ordinal not in
  range(128)

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Apport is invoked by the kernel via /proc/sys/kernel/core_pattern and
  crashes when writing some message to stderr:

  ERROR: ERROR: apport (pid 23175) Fri Sep 12 22:51:58 2014: Unhandled 
exception:
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 367, in 
  (info['ExecutablePath'], info['ProcCmdline']))
File "/usr/share/apport/apport", line 99, in error_log
  apport.error('apport (pid %s) %s: %s', os.getpid(), time.asctime(), msg)
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 44, in error
  sys.stderr.write(msg % args)
  UnicodeEncodeError: 'ascii' codec can't encode character '\xc1' in position 
130: ordinal not in range(128)
  ERROR: apport (pid 23175) Fri Sep 12 22:51:58 2014: pid: 23175, uid: 1000, 
gid: 1000, euid: 0, egid: 0
  ERROR: apport (pid 23175) Fri Sep 12 22:51:58 2014: environment: environ({})

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep 12 22:57:13 2014
  InstallationDate: Installed on 2014-05-20 (115 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  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/1368911/+subscriptions

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

[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.1

---
systemd (229-4ubuntu21.1) xenial-security; urgency=medium

  * SECURITY UPDATE: remote DoS in resolved (LP: #1725351)
- debian/patches/CVE-2017-15908.patch: fix loop on packets with pseudo
  dns types in src/resolve/resolved-dns-packet.c.
- CVE-2017-15908
  * SECURITY UPDATE: access to automounted volumes can lock up
(LP: #1709649)
- debian/patches/CVE-2018-1049.patch: ack automount requests even when
  already mounted in src/core/automount.c.
- CVE-2018-1049

 -- Marc Deslauriers   Thu, 01 Feb 2018
07:42:30 -0500

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

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

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

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

Title:
  229 backport for  race between explicit mount and handling automount

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 Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  In systemd prior to 234 a race exists between .mount and .automount units 
such that automount requests from kernel may not be serviced by systemd 
resulting in kernel holding the mountpoint and any processes that try to use 
said mount will hang. A race like this may lead to denial of service, until 
mount points are unmounted.

  [Testcase]
  Create a race between .mount and .automount units, such that automout request 
is serviced after .mount unit has been started. Observe a hang.
  More detailed steps are available at 
https://github.com/systemd/systemd/pull/5916

  [Butfix]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/e7d54bf58789545a9eb0b3964233defa0b007318

  [Regression Potential]
  The underlying logic of starting/stopping/triggering units is unchanged. 
However, there the logic as to when to send automout_send_ready() is relaxed, 
such that it is always sent whenever unit is already mounted. This is done to 
explicitly cope with late arrival of the incoming [aircraft] automount request.

  [Original Bug report / request]

  Hi,

  We have a blocking issue in systemd for the following release

  ```
  NAME="Ubuntu"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.3 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ```

  This release runs systemd229, we are affected by the following auto-
  mouting race condition

  ```
  https://github.com/systemd/systemd/pull/5916
  ```

  Is back porting  the fix to the release 229 an option?

  Regards.

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

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

[Touch-packages] [Bug 1747474] Re: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in poppler package in Ubuntu:
  New

Bug description:
  Impossible to remove and re-install.
  Message :
  libpoppler-glib8:amd64 (--configure)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libpoppler-glib8:amd64 0.57.0-2ubuntu4.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   linux-firmware:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb  5 18:15:06 2018
  DpkgTerminalLog:
   Preparing to unpack .../linux-firmware_1.169.3_all.deb ...
   Unpacking linux-firmware (1.169.3) over (1.169.2) ...
   dpkg: error processing package libpoppler-glib8:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:libpoppler-glib8:amd64:0.57.0-2ubuntu4.2
   Unpacking linux-firmware (1.169.3) over (1.169.2) ...
   dpkg: error processing package libpoppler-glib8:amd64 (--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-08-06 (182 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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.1
  SourcePackage: poppler
  Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.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/poppler/+bug/1747474/+subscriptions

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

[Touch-packages] [Bug 1747474] [NEW] package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[BRUN]

Public bug reported:

Impossible to remove and re-install.
Message :
libpoppler-glib8:amd64 (--configure)

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libpoppler-glib8:amd64 0.57.0-2ubuntu4.2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 linux-firmware:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Feb  5 18:15:06 2018
DpkgTerminalLog:
 Preparing to unpack .../linux-firmware_1.169.3_all.deb ...
 Unpacking linux-firmware (1.169.3) over (1.169.2) ...
 dpkg: error processing package libpoppler-glib8:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature:
 package:libpoppler-glib8:amd64:0.57.0-2ubuntu4.2
 Unpacking linux-firmware (1.169.3) over (1.169.2) ...
 dpkg: error processing package libpoppler-glib8:amd64 (--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-08-06 (182 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.1
SourcePackage: poppler
Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.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)

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


** Tags: amd64 apport-package artful

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

Title:
  package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in poppler package in Ubuntu:
  New

Bug description:
  Impossible to remove and re-install.
  Message :
  libpoppler-glib8:amd64 (--configure)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libpoppler-glib8:amd64 0.57.0-2ubuntu4.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   linux-firmware:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb  5 18:15:06 2018
  DpkgTerminalLog:
   Preparing to unpack .../linux-firmware_1.169.3_all.deb ...
   Unpacking linux-firmware (1.169.3) over (1.169.2) ...
   dpkg: error processing package libpoppler-glib8:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:libpoppler-glib8:amd64:0.57.0-2ubuntu4.2
   Unpacking linux-firmware (1.169.3) over (1.169.2) ...
   dpkg: error processing package libpoppler-glib8:amd64 (--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-08-06 (182 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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.1
  SourcePackage: poppler
  Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.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/poppler/+bug/1747474/+subscriptions

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

[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Hans Joachim Desserud]

** Tags removed: zesty
** Tags added: bionic

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  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
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1747429] Re: package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de

[Hans Joachim Desserud]

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

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

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

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

Title:
  package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar
  sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Stoping direct

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-4build1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb  5 10:28:56 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.26:i386
  InstallationDate: Installed on 2017-09-13 (145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.26:i386
  UpgradeStatus: Upgraded to bionic on 2017-12-03 (63 days ago)

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

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

[Touch-packages] [Bug 1747242] Re: All host keys work except ed25519

[Enkouyami]

** Description changed:

  Changing the sshd_config file to use the ed25519 host key exclusively
- causes the server to reject all connections.
+ causes the server to reject all connections, even from localhost.
  
  Excerpt from my config file:
  #HostKey /etc/ssh/ssh_host_rsa_key
  #HostKey /etc/ssh/ssh_host_ecdsa_key
  HostKey /etc/ssh/ssh_host_ed25519_key
  
  I tried setting each one individually then restarting the sshd service
  and it only states that the connection has been reset when I use
  ed25519.
  
  I've tried connecting from localhost, another Ubuntu 16.04 computer with
  OpenSSH_7.5p1, and localhost on the other computer.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 04:36:44 2018
  InstallationDate: Installed on 2017-11-30 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  All host keys work except ed25519

Status in openssh package in Ubuntu:
  New

Bug description:
  Changing the sshd_config file to use the ed25519 host key exclusively
  causes the server to reject all connections, even from localhost.

  Excerpt from my config file:
  #HostKey /etc/ssh/ssh_host_rsa_key
  #HostKey /etc/ssh/ssh_host_ecdsa_key
  HostKey /etc/ssh/ssh_host_ed25519_key

  I tried setting each one individually then restarting the sshd service
  and it only states that the connection has been reset when I use
  ed25519.

  I've tried connecting from localhost, another Ubuntu 16.04 computer
  with OpenSSH_7.5p1, and localhost on the other computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 04:36:44 2018
  InstallationDate: Installed on 2017-11-30 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20120223'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog to /var/log/syslog-20120223
  running postrotate script
  removing old log /var/log/syslog-20111219.gz

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log needs rotating
  considering log /var/log/auth.log
log needs rotating
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
   

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Chris Rainey]

Never mind, found it:  https://bugs.launchpad.net/launchpad/+bug/1747469

Sorry for the SPAM!

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Christopher M. Penalver]

Dieter Maurer:
>"I tried, but the resulting DVD does not boot:"

Then please post the results requested in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/comments/21
so it may be reviewed.

>"-- maybe, because it is for for the x64 platform while I typically use
the i386 platform (however, my AMD Sempron should support x64)"

Your CPU supports x64 as per AMD -> https://www.amd.com/en-
us/products/processors/desktop/sempron-cpu#

>"-- maybe due to a burning problem (the burning has been surprisingly
fast; just some 10 s)."

Did you checksum the ISO you downloaded? If so and it passed, you can make an 
ISO of what you burned and checksum this to confirm it burned correctly via a 
terminal:
sudo dd if=/dev/sdX of=file.iso

Where X is the letter for your cd drive.

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed 

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Chris Rainey]

OK  so I'm _really_ glad to see the work on this bug progressing
and, as such, I've been attempting to "add myself" to this bug's
"affected user" list. However, I have _not_ been able to do so for the
past 2-weeks with the error message:  "timeout, please try again later".
Does anybody know how to create a bug-report for Launchpad, itself?

Screenshot of bug, attached.

** Attachment added: "Timeout error after clicking the "me too" button"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/5049260/+files/Screenshot_2018-02-05_10-19-35.png

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1747242] Re: All host keys work except ed25519

[Enkouyami]

** Description changed:

- Changing the sshd_config file to use exclusively the ed25519 host key
- type causes the server to reject all connections.
+ Changing the sshd_config file to use the ed25519 host key exclusively
+ causes the server to reject all connections.
  
  Excerpt from my config file:
  #HostKey /etc/ssh/ssh_host_rsa_key
  #HostKey /etc/ssh/ssh_host_ecdsa_key
- HostKey /etc/ssh/Japan_ssh_host_ed25519_key
+ HostKey /etc/ssh/ssh_host_ed25519_key
  
  I tried setting each one individually then restarting the sshd service
  and it only states that the connection has been reset when I use
  ed25519.
+ 
+ I've tried connecting from localhost, another Ubuntu 16.04 computer with
+ OpenSSH_7.5p1, and localhost on the other computer.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 04:36:44 2018
  InstallationDate: Installed on 2017-11-30 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  All host keys work except ed25519

Status in openssh package in Ubuntu:
  New

Bug description:
  Changing the sshd_config file to use the ed25519 host key exclusively
  causes the server to reject all connections.

  Excerpt from my config file:
  #HostKey /etc/ssh/ssh_host_rsa_key
  #HostKey /etc/ssh/ssh_host_ecdsa_key
  HostKey /etc/ssh/ssh_host_ed25519_key

  I tried setting each one individually then restarting the sshd service
  and it only states that the connection has been reset when I use
  ed25519.

  I've tried connecting from localhost, another Ubuntu 16.04 computer
  with OpenSSH_7.5p1, and localhost on the other computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 04:36:44 2018
  InstallationDate: Installed on 2017-11-30 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1747242] Re: All host keys work except ed25519

[Enkouyami]

I tried on another computer running Ubuntu 16.04 and have the same
problem.

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

Title:
  All host keys work except ed25519

Status in openssh package in Ubuntu:
  New

Bug description:
  Changing the sshd_config file to use exclusively the ed25519 host key
  type causes the server to reject all connections.

  Excerpt from my config file:
  #HostKey /etc/ssh/ssh_host_rsa_key
  #HostKey /etc/ssh/ssh_host_ecdsa_key
  HostKey /etc/ssh/Japan_ssh_host_ed25519_key

  I tried setting each one individually then restarting the sshd service
  and it only states that the connection has been reset when I use
  ed25519.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 04:36:44 2018
  InstallationDate: Installed on 2017-11-30 (66 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

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

Title:
  zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Incomplete
Status in zlib package in Ubuntu:
  New

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+subscriptions

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

[Touch-packages] [Bug 1733870] Re: [Ubuntu 18.10] Add GDB support to access/display POWER8 registers

[Manoj Iyer]

** Changed in: gdb (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

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

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

Title:
  [Ubuntu 18.10] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  Incomplete
Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+subscriptions

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

[Touch-packages] [Bug 1591833] Re: [Featue] Upgrade Openssl for Intel QAT (quickassist-technology)

[Dimitri John Ledkov]

This is now in progress.

** Changed in: openssl (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: openssl (Ubuntu)
Milestone: later => ubuntu-18.02

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

Title:
  [Featue] Upgrade Openssl for Intel QAT (quickassist-technology)

Status in intel:
  New
Status in openssl package in Ubuntu:
  In Progress
Status in openssl package in Debian:
  Fix Released

Bug description:
  In order to support Intel QAT, please upgrade Openssl package from
  1.0.2 to 1.1.0

  HW: Purley-4s

  Upstream schedule:
     Openssl: 1.1.0

  Target release: 18.04

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

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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Stefan Bader]

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Committed
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New
Status in vzctl package in Ubuntu:
  New
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1746310] Re: Drop fonts-symbola from platform?

[Treviño]

I'm ok with replacing.

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

Title:
  Drop fonts-symbola from platform?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ttf-ancient-fonts-symbola is a recommends in platform.bionic desktop-
  common so it's installed for every Ubuntu desktop flavor (Kubuntu,
  Lubuntu, Ubuntu, etc.).

  It's a transitional package now depending on fonts-symbola.

  The package description is
  "This package includes the Symbola font, which contains special symbols and 
emoji characters which are encoded in the Unicode Standard 9.0."

  It was added to the seeds in LP: #1137630 explicitly for emoji
  support.

  Ubuntu Desktop (and Ubuntu Budgie and Ubuntu MATE) now include fonts-
  noto-color-emoji for this instead.

  GTK+ in Ubuntu 18.04 supports color emoji. Qt does not.

  fonts-symbola has installed-size 3,178 kB according to apt
  fonts-noto-color-emoji has installed-size 7,277 kB

  Should we replace fonts-symbola with fonts-noto-color-emoji? Or should
  we drop it entirely?

  The only other Color Emoji font I expect to be available in Ubuntu
  soon is EmojiTwo. EmojiTwo lags behind in supporting the latest emoji
  standards.

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

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

[Touch-packages] [Bug 1747429] [NEW] package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente d

[Paulinho Cariri]

Public bug reported:

Stoping direct

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-4build1
Uname: Linux 4.15.1-041501-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Mon Feb  5 10:28:56 2018
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.26:i386
InstallationDate: Installed on 2017-09-13 (145 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: perl
Title: package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.26:i386
UpgradeStatus: Upgraded to bionic on 2017-12-03 (63 days ago)

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


** Tags: amd64 apport-package bionic package-from-proposed

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

Title:
  package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar
  sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Stoping direct

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-4build1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb  5 10:28:56 2018
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.26:i386
  InstallationDate: Installed on 2017-09-13 (145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-4build1 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.26:i386
  UpgradeStatus: Upgraded to bionic on 2017-12-03 (63 days ago)

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

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

[Touch-packages] [Bug 1747421] [NEW] Bluetooth does not start

[Laur]

Public bug reported:

Bluetooth does not start turn it on and notting happens 
i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
root@Laurentiu:/home/laufer# apt-cache policy bluez
bluez:
  Installed: 5.46-0ubuntu3
  Candidate: 5.46-0ubuntu3
  Version table:
 *** 5.46-0ubuntu3 500
500 http://ro.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
root@Laurentiu:/home/laufer#

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluez 5.46-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Feb  5 15:00:42 2018
InstallationDate: Installed on 2018-02-04 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. X541UVK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=87b1ca1a-1586-47e4-83a2-c81e7e67ca79 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X541UVK.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X541UVK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.304:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X541UVK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 64:6E:69:20:D4:7E  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1225 acl:0 sco:0 events:122 errors:0
TX bytes:23230 acl:0 sco:0 commands:124 errors:0

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

Title:
  Bluetooth does not start

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth does not start turn it on and notting happens 
  i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


  
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
  14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
  14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
  14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@Laurentiu:/home/laufer# apt-cache policy bluez
  

[Touch-packages] [Bug 1747421] Re: Bluetooth does not start

[Laur]

im new at ubuntu but i like it more then windows10 and since i cant
install windows 7 dude to leptop restrictions this is better:D all the
support is apreciated

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

Title:
  Bluetooth does not start

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth does not start turn it on and notting happens 
  i have an asus x541uv with rtl8723be its wifi and bluetooth in 1 bord wifi 
works 


  
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:27 kernel: pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=0001/2000
  14:14:27 kernel: pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e5(Receiver ID)
  14:14:27 bluetoothd: Failed to set mode: Failed (0x03)
  14:14:26 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:19 kernel: Bluetooth: hci0 urb 9b2d21447180 failed to resubmit (113)
  14:14:17 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:14:11 pulseaudio: [pulseaudio] pid.c: Daemon already running.
  14:14:07 kernel: pcieport :00:1c.5:[ 0] Receiver Error (First)
  14:13:59 lightdm: PAM adding faulty module: pam_kwallet5.so

  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@Laurentiu:/home/laufer# apt-cache policy bluez
  bluez:
Installed: 5.46-0ubuntu3
Candidate: 5.46-0ubuntu3
Version table:
   *** 5.46-0ubuntu3 500
  500 http://ro.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  root@Laurentiu:/home/laufer#

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb  5 15:00:42 2018
  InstallationDate: Installed on 2018-02-04 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. X541UVK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=87b1ca1a-1586-47e4-83a2-c81e7e67ca79 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541UVK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541UVK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.304:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541UVK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 64:6E:69:20:D4:7E  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1225 acl:0 sco:0 events:122 errors:0
TX bytes:23230 acl:0 sco:0 commands:124 errors:0

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

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

[Touch-packages] [Bug 1378117] Re: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()

[Launchpad Bug Tracker]

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

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

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

Title:
  ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Unclear what went wrong.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Mon Oct  6 15:05:41 2014
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2011-05-04 (1251 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to utopic on 2014-09-15 (21 days ago)
  UserGroups: adm admin autopilot cdrom dialout libvirtd lpadmin pkcs11 plugdev 
sambashare sbuild sudo vboxusers

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

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

[Touch-packages] [Bug 1359110] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

[Launchpad Bug Tracker]

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  on 14.10

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 20 09:35:05 2014
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2014-05-29 (82 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
  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/ibus/+bug/1359110/+subscriptions

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

[Touch-packages] [Bug 1379822] Re: ibus-ui-gtk3 crashed with SIGABRT

[Launchpad Bug Tracker]

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

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

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  happens on every start!

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Oct 10 17:09:08 2014
  Disassembly: => 0x7f461004dd27:   Cannot access memory at address 
0x7f461004dd27
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2013-01-14 (633 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT
  UpgradeStatus: Upgraded to utopic on 2014-09-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1747416] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1747416/+attachment/5049145/+files/Stacktrace.txt

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

Title:
  ibus-ui-gtk3 crashed with signal 5

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1747416] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1747416/+attachment/5049147/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  ibus-ui-gtk3 crashed with signal 5

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1747416] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1747416/+attachment/5049146/+files/StacktraceSource.txt

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

Title:
  ibus-ui-gtk3 crashed with signal 5

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1747416] ibus-ui-gtk3 crashed with signal 5

[Apport retracing service]

StacktraceTop:
 g_settings_set_property (object=0x560dfb6a1750, prop_id=, 
value=, pspec=) at ../../../../gio/gsettings.c:590
 object_set_property (nqueue=0x560dfb71cd60, value=, 
pspec=0x560dfb6dcee0, object=0x560dfb6a1750) at 
../../../../gobject/gobject.c:1439
 g_object_new_internal (class=class@entry=0x560dfb727b10, 
params=params@entry=0x7ffd35404e20, n_params=n_params@entry=1) at 
../../../../gobject/gobject.c:1831
 g_object_new_valist (object_type=94618053194976, 
first_property_name=first_property_name@entry=0x7f93a102bbc0 "schema-id", 
var_args=var_args@entry=0x7ffd35404f70) at ../../../../gobject/gobject.c:2120
 g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x7f93a102bbc0 "schema-id") at 
../../../../gobject/gobject.c:1640

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

Title:
  ibus-ui-gtk3 crashed with signal 5

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1747416] [NEW] ibus-ui-gtk3 crashed with signal 5

[Wellington Torrejais da Silva]

Public bug reported:

ibus-ui-gtk3 crashed with signal 5
After login, after boot.

When loading desktop(Lxde)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu1
ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
Uname: Linux 4.14.0-3-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Mon Feb  5 10:19:38 2018
ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
InstallationDate: Installed on 2016-08-02 (551 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
Signal: 5
SourcePackage: ibus
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ()
Title: ibus-ui-gtk3 crashed with signal 5
UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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


** Tags: amd64 apport-crash bionic

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

Title:
  ibus-ui-gtk3 crashed with signal 5

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1747411] [NEW] Change of default database file format to SQL

[ChristianEhrhardt]

Public bug reported:

nss in version 3.35 in upstream changed [2] the default file format [1] (if no 
explicit one is specified).
For now we reverted that change in bug 1746947 until all packages depending on 
it are ready to work with that correctly.

This bug here is about to track when the revert can be dropped.
Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

[1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
[2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

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

** Affects: dogtag-pki (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: libapache2-mod-nss (Ubuntu)
 Importance: Undecided
 Status: New

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

** Summary changed:

- Change of default database file format
+ Change of default database file format to SQL

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

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

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

** Also affects: dogtag-pki (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libapache2-mod-nss (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Change of default database file format to SQL

Status in certmonger package in Ubuntu:
  New
Status in corosync package in Ubuntu:
  New
Status in dogtag-pki package in Ubuntu:
  New
Status in freeipa package in Ubuntu:
  New
Status in libapache2-mod-nss package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New

Bug description:
  nss in version 3.35 in upstream changed [2] the default file format [1] (if 
no explicit one is specified).
  For now we reverted that change in bug 1746947 until all packages depending 
on it are ready to work with that correctly.

  This bug here is about to track when the revert can be dropped.
  Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

  [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
  [2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

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

[Touch-packages] [Bug 1747412] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saí

[wagner schneider]

Public bug reported:

This issue happened when i tried to update.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Feb  5 09:54:10 2018
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-05-28 (252 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 192.168.0.1 dev enp2s0 proto static metric 100 
 169.254.0.0/16 dev enp2s0 scope link metric 1000 
 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.100 metric 100
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PackageArchitecture: all
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.1
RfKill:
 
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: sub-processo script post-installation instalado retornou 
estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME   UUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
 Conexão cabeada 1  e9be19de-58c5-300b-8d8c-7c5a5c25ded5  802-3-ethernet  
1517832180  seg 05 fev 2018 10:03:00 -02  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexão cabeada 1  e9be19de-58c5-300b-8d8c-7c5a5c25ded5  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 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

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: sub-processo script post-installation
  instalado retornou estado de saída de erro 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  This issue happened when i tried to update.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb  5 09:54:10 2018
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-05-28 (252 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.0.1 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.100 metric 
100
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  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.1
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to 

[Touch-packages] [Bug 1746947] Re: failing autopkgtest due to password issue by nss

[ChristianEhrhardt]

Built with said change - and now testing against the nss in the ppa (should all 
work):
- install 4.4 (ppa) -> OK
- install 4.6 (proposed + ppa) -> OK
- old python call against 4.4 (ppa) -> OK
- new python call against 4.6 (proposed + ppa) -> OK

I dupped Corosync on here, so lets verify it fixes that as well
- install corosync-qnetd as in proposed (should fail) -> FAIL
- install corosync-qnetd with ppa (should work) -> OK


This was a bit of a panic exercise for me :-)
After breaking things with nss which isn't my home turf I wanted to get rid of 
it asap.
Thanks to Timo to keep me in line with our discussions so it ended up as a much 
more reasonable fix.
Uploading the fixed 3.35 version now ...

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

Title:
  failing autopkgtest due to password issue by nss

Status in freeipa package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I was failed by autopkgtests of freeipa, but not the old "ip route output 
changed" case.
  Like: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/f/freeipa/20180201_161632_c9091@/log.gz

  It essentially does this and fails:
  $ apt install freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib python-ipaserver python-ipatests

  Containers:
  Bionic-as-is: installs ok
  Bionic-Proposed: installs ok

  In LP Infra:
  dpkg: error processing package freeipa-client (--configure):
   installed freeipa-client package post-installation script subprocess 
returned error exit status 1

  Use Pinning to get the autopkgtest style:
  # cat /etc/apt/preferences.d/nssonlyproposed
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  Package: libnss3 libnss3-tools libnss3-dev libnss3-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 1002
  Bionic-nss-only-from-Proposed: TRIGGERS the issue

  freeipa-client is in the postinst calling this:
  python2 -c 'from ipapython.certdb import update_ipa_nssdb; update_ipa_nssdb()'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 64, in 
update_ipa_nssdb
  create_ipa_nssdb()
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 53, in 
create_ipa_nssdb
  db.create_db(pwdfile)
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 149, in 
create_db
  self.run_certutil(["-N", "-f", password_filename])
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 142, in 
run_certutil
  return ipautil.run(new_args, stdin, **kwargs)
File "/usr/lib/python2.7/dist-packages/ipapython/ipautil.py", line 515, in 
run
  raise CalledProcessError(p.returncode, arg_string, str(output))
  subprocess.CalledProcessError: Command '/usr/bin/certutil -d /etc/ipa/nssdb 
-N -f /etc/ipa/nssdb/pwdfile.txt' returned non-zero exit status 255

  
  That is - if called alone complaining about the passwd:
  # /usr/bin/certutil -d /etc/ipa/nssdb -N -f /etc/ipa/nssdb/pwdfile.txt
  Invalid password.
  certutil: Could not set password for the slot: SEC_ERROR_BAD_PASSWORD: The 
security password entered is incorrect.

  
  Note that there is a related freeipa fix in later versions:
 freeipa (4.6.2-4) unstable; urgency=medium 
  

  
   * client.postinst: Migrate from old nssdb only if it exists.

  And since that change freeipa has:
  if [ -f /etc/ipa/nssdb/cert8.db ]; then
  around the call.

  It also changed the import slightly - now the python being:

  python2 -c 'from ipaclient.install.client import update_ipa_nssdb;
  update_ipa_nssdb()'

  That in the "all-proposed" case with the cert8.db file copied over is still 
failing but differently:
  /usr/bin/certutil -d /etc/ipa/nssdb -L -f /etc/ipa/nssdb/pwdfile.txt
  certutil: function failed: SEC_ERROR_BAD_DATABASE: security library: bad 
database.

  The merge of nss was a minor bump 3.34->3.35
  Also this is the nss version from Debian with the freeipa version from 
Debian. They seem to work together there.

  I don't fully understand it yet - so filing this bug for a discussion.
  I need the help of tjaalton who did the freeipa changes - maybe he knows what 
is going on.

  Do we have to:
  - rebuild freeipa against newer nss?
  - just mark something as bad test
  - something completely else?

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

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

[Touch-packages] [Bug 1747388] Re: patch for multipath disks

[James Page]

** Package changed: udev (Ubuntu) => lvm2 (Ubuntu)

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

Title:
  patch for multipath disks

Status in OpenStack ceph-osd charm:
  Invalid
Status in lvm2 package in Ubuntu:
  New

Bug description:
  According to this page:

  https://patchwork.kernel.org/patch/9826353/

  there is a bug in ceph that affects the use of FibreChannel disks.

  The following patch to file hooks/ceph_hooks.py, fixes it:

  *** hooks/ceph_hooks.py   2018-02-02 16:15:40.304388602 +0100
  --- hooks/ceph_hooks.py~  2018-02-02 16:18:47.304401004 +0100
  ***
  *** 369,378 

   @hooks.hook('storage.real')
   def prepare_disks_and_activate():
  - # patch for missing dm devices
  - # see: https://patchwork.kernel.org/patch/9826353/
  - patch_persistent_storage_rules()
  - 
   osd_journal = get_journal_devices()
   check_overlap(osd_journal, set(get_devices()))
   log("got journal devs: {}".format(osd_journal), level=DEBUG)
  --- 369,374 
  ***
  *** 558,579 
   log('Updating status.')

  
  - # patch for missing dm devices
  - from subprocess import check_call
  - 
  - 
  - CEPH_PERSITENT_STORTAGE_RULES = 
'/lib/udev/rules.d/60-persistent-storage.rules'
  - 
  - 
  - def patch_persistent_storage_rules():
  - if os.path.isfile(CEPH_PERSITENT_STORTAGE_RULES):
  - check_call(['sed', '-i', 's/KERNEL!="loop/KERNEL!="dm*|loop/',
  - CEPH_PERSITENT_STORTAGE_RULES])
  - log('Patched %s' % CEPH_PERSITENT_STORTAGE_RULES)
  - else:
  - log('Missing %s' % CEPH_PERSITENT_STORTAGE_RULES)
  - 
  - 
   if __name__ == '__main__':
   try:
   hooks.execute(sys.argv)
  --- 554,559 ——

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1747388/+subscriptions

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

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

> 1) To see if this is already resolved in Ubuntu, could you please test 
> http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

I tried, but the resulting DVD does not boot:
   -- maybe, because it is for for the x64 platform while I typically use the 
i386 platform
   (however, my AMD Sempron should support x64)
   -- maybe due to a burning problem (the burning has been surprisingly fast; 
just some 10 s).

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell]
  DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] 
[1849:03d6]
  InstallationDate: Installed on 2013-01-21 (1838 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 

[Touch-packages] [Bug 1747394] Re: libvirtd crashed with SIGSEGV in xmlHashLookup3__internal_alias()

[ChristianEhrhardt]

Hi Sosha,
the crash itself is in libxml2 so I add a bug task for that.

>From the libvirt POV this seems to be in a stage where it initializes its 
>state drivers.
virStateInitialize iterates on drivers and calls stateInitialize of the 
respective backend.

I can't see from your trace which that is, but I assume this triggers right 
when you start libvirtd?
If so did you register special backends?
The following is the list of drivers with such a function

0 bhyve_driver.c 1753 .stateInitialize = bhyveStateInitialize,
2 interface_backend_netcf.c  1139 .stateInitialize = netcfStateInitialize,
3 interface_backend_udev.c   1211 .stateInitialize = udevStateInitialize,
4 libxl_driver.c 6594 .stateInitialize = libxlStateInitialize,
5 lxc_driver.c   5590 .stateInitialize = lxcStateInitialize,
6 bridge_driver.c4272 .stateInitialize = networkStateInitialize,
7 node_device_hal.c   778 .stateInitialize = nodeStateInitialize,
8 node_device_udev.c 2070 .stateInitialize = nodeStateInitialize,
9 nwfilter_driver.c   640 .stateInitialize = nwfilterStateInitialize,
a qemu_driver.c 21355 .stateInitialize = qemuStateInitialize,
b remote_driver.c8648 .stateInitialize = remoteStateInitialize,
c secret_driver.c 578 .stateInitialize = secretStateInitialize,
d storage_driver.c   2743 .stateInitialize = storageStateInitialize,
0 uml_driver.c   3020 .stateInitialize = umlStateInitialize,
1 vz_driver.c4171 .stateInitialize = vzStateInitialize,
2 xen_driver.c269 .stateInitialize = xenUnifiedStateInitialize,

Since it has netcf entries down the stack trace I can only assume it is the 
init of netcf.
That would be in netcfStateInitialize

There is calls ncf_init and the lib also has libxml2 bindings.
I fail to derive more from the stack trace as-is, but that already meand we 
should also add a task for netcf.

I wonder:
1. is this reproducible on e.g. every restart of libvirtd?
2. do you have any non-default network configuration on the system or in 
libvirt that might be what we would need to reproduce that?

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

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

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

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

Title:
  libvirtd crashed with SIGSEGV in xmlHashLookup3__internal_alias()

Status in libvirt package in Ubuntu:
  Incomplete
Status in libxml2 package in Ubuntu:
  New
Status in netcf package in Ubuntu:
  New

Bug description:
  after upgrade packages...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libvirt-daemon 4.0.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb  5 04:19:29 2018
  ExecutablePath: /usr/sbin/libvirtd
  InstallationDate: Installed on 2017-09-02 (156 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcAttrCurrent: /usr/sbin/libvirtd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7ff92a1ee4b5 :mov
0x28(%rbx),%eax
   PC (0x7ff92a1ee4b5) ok
   source "0x28(%rbx)" (0xdc9b6a9060306869) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libvirt
  StacktraceTop:
   xmlHashLookup () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
  Title: libvirtd crashed with SIGSEGV in xmlHashLookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1747388] [NEW] patch for multipath disks

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

According to this page:

https://patchwork.kernel.org/patch/9826353/

there is a bug in ceph that affects the use of FibreChannel disks.

The following patch to file hooks/ceph_hooks.py, fixes it:

*** hooks/ceph_hooks.py 2018-02-02 16:15:40.304388602 +0100
--- hooks/ceph_hooks.py~2018-02-02 16:18:47.304401004 +0100
***
*** 369,378 

 @hooks.hook('storage.real')
 def prepare_disks_and_activate():
- # patch for missing dm devices
- # see: https://patchwork.kernel.org/patch/9826353/
- patch_persistent_storage_rules()
- 
 osd_journal = get_journal_devices()
 check_overlap(osd_journal, set(get_devices()))
 log("got journal devs: {}".format(osd_journal), level=DEBUG)
--- 369,374 
***
*** 558,579 
 log('Updating status.')


- # patch for missing dm devices
- from subprocess import check_call
- 
- 
- CEPH_PERSITENT_STORTAGE_RULES = 
'/lib/udev/rules.d/60-persistent-storage.rules'
- 
- 
- def patch_persistent_storage_rules():
- if os.path.isfile(CEPH_PERSITENT_STORTAGE_RULES):
- check_call(['sed', '-i', 's/KERNEL!="loop/KERNEL!="dm*|loop/',
- CEPH_PERSITENT_STORTAGE_RULES])
- log('Patched %s' % CEPH_PERSITENT_STORTAGE_RULES)
- else:
- log('Missing %s' % CEPH_PERSITENT_STORTAGE_RULES)
- 
- 
 if __name__ == '__main__':
 try:
 hooks.execute(sys.argv)
--- 554,559 ——

** Affects: charm-ceph-osd
 Importance: Undecided
 Status: Invalid

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

-- 
patch for multipath disks
https://bugs.launchpad.net/bugs/1747388
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lvm2 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 1747128] Re: RM: obsolete product

[Dimitri John Ledkov]

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

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

Title:
  RM: obsolete product

Status in mediascanner2 package in Ubuntu:
  Triaged

Bug description:
  mediascanner2 was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:mediascanner2
  No reverse dependencies found

  $ reverse-depends -b src:mediascanner2
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1746947] Re: failing autopkgtest due to password issue by nss

[ChristianEhrhardt]

I was discussing this with Timo and he correctly pointed out that reverting [1] 
might be enough.
This would allow to get all fixes of 3.35, but at the same time not run into 
this bug here all over the place.

Building with that for some test runs.

[1]: https://github.com/nss-
dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

Title:
  failing autopkgtest due to password issue by nss

Status in freeipa package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I was failed by autopkgtests of freeipa, but not the old "ip route output 
changed" case.
  Like: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/f/freeipa/20180201_161632_c9091@/log.gz

  It essentially does this and fails:
  $ apt install freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib python-ipaserver python-ipatests

  Containers:
  Bionic-as-is: installs ok
  Bionic-Proposed: installs ok

  In LP Infra:
  dpkg: error processing package freeipa-client (--configure):
   installed freeipa-client package post-installation script subprocess 
returned error exit status 1

  Use Pinning to get the autopkgtest style:
  # cat /etc/apt/preferences.d/nssonlyproposed
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  Package: libnss3 libnss3-tools libnss3-dev libnss3-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 1002
  Bionic-nss-only-from-Proposed: TRIGGERS the issue

  freeipa-client is in the postinst calling this:
  python2 -c 'from ipapython.certdb import update_ipa_nssdb; update_ipa_nssdb()'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 64, in 
update_ipa_nssdb
  create_ipa_nssdb()
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 53, in 
create_ipa_nssdb
  db.create_db(pwdfile)
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 149, in 
create_db
  self.run_certutil(["-N", "-f", password_filename])
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 142, in 
run_certutil
  return ipautil.run(new_args, stdin, **kwargs)
File "/usr/lib/python2.7/dist-packages/ipapython/ipautil.py", line 515, in 
run
  raise CalledProcessError(p.returncode, arg_string, str(output))
  subprocess.CalledProcessError: Command '/usr/bin/certutil -d /etc/ipa/nssdb 
-N -f /etc/ipa/nssdb/pwdfile.txt' returned non-zero exit status 255

  
  That is - if called alone complaining about the passwd:
  # /usr/bin/certutil -d /etc/ipa/nssdb -N -f /etc/ipa/nssdb/pwdfile.txt
  Invalid password.
  certutil: Could not set password for the slot: SEC_ERROR_BAD_PASSWORD: The 
security password entered is incorrect.

  
  Note that there is a related freeipa fix in later versions:
 freeipa (4.6.2-4) unstable; urgency=medium 
  

  
   * client.postinst: Migrate from old nssdb only if it exists.

  And since that change freeipa has:
  if [ -f /etc/ipa/nssdb/cert8.db ]; then
  around the call.

  It also changed the import slightly - now the python being:

  python2 -c 'from ipaclient.install.client import update_ipa_nssdb;
  update_ipa_nssdb()'

  That in the "all-proposed" case with the cert8.db file copied over is still 
failing but differently:
  /usr/bin/certutil -d /etc/ipa/nssdb -L -f /etc/ipa/nssdb/pwdfile.txt
  certutil: function failed: SEC_ERROR_BAD_DATABASE: security library: bad 
database.

  The merge of nss was a minor bump 3.34->3.35
  Also this is the nss version from Debian with the freeipa version from 
Debian. They seem to work together there.

  I don't fully understand it yet - so filing this bug for a discussion.
  I need the help of tjaalton who did the freeipa changes - maybe he knows what 
is going on.

  Do we have to:
  - rebuild freeipa against newer nss?
  - just mark something as bad test
  - something completely else?

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

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

[Touch-packages] [Bug 1746947] Re: failing autopkgtest due to password issue by nss

[ChristianEhrhardt]

For a better overview and to make a decision (as a +really version always sucks 
to some extend) I did some tests:
- built nss 3.34 with the freebl3 change in ppa [1] as 
2:3.35-2ubuntu1+really3.34-1ubuntu2
- set up some containers to test
- ran the sequence of installs/commands that freeipa tests would do

I did so in different combinations:
1. freeipa 4.4.4 + nss 3.34-1ubuntu1 (as bionic is)
2. freeipa 4.6.3 + nss 3.35-1ubuntu1 (full bionic proposed)
3. freeipa 4.4.4 + nss 3.35-1ubuntu1 (as tested by autopkgtest by pinning)
4. freeipa 4.4.4 + nss 3.35-2ubuntu1+really3.34-1ubuntu2 (ppa)
5. freeipa 4.6.3 + nss 3.35-2ubuntu1+really3.34-1ubuntu2 (proposed + ppa)

I tested:
- the install that fails in the autopkgtest
  $ apt install freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common
freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib
python-ipaserver python-ipatests
- the python call that fails (old & new form of it as it needs an additional 
import in 4.6.2)
  python2 -c 'from ipapython.certdb import update_ipa_nssdb; update_ipa_nssdb()'
  python2 -c 'from ipaclient.install.client import update_ipa_nssdb; 
update_ipa_nssdb()'

 #1 install#2 old python #3 new python
1.   okokfail (4.4 has only old 
import)
2.   ok (skip) fail (4.6 need new import)ok
3.   fail  fail (nss format) fail (4.4 has only old 
import)
4.   okokfail (4.4 has only old 
import)
5.   ok (skip) fail (4.6 need new import)ok

So an nss upload should work as planned with both verserions:
- freeipa 4.4 (case 4. #2)
- freeipa 4.6 (case 5. #3)
- and both cases would install (4./5. #1).

Due to the hint by Timo (thanks) I found [1] which explains a bit what is going 
on.
That is a nice change to be made in nss, but not unplanned and unprepared.
Some consuming packages need to be adapted first, and that was not what I 
intended by picking a new minor version. So that as well points to an upload 
reverting the move to 3.35.

Get me right - the move to 3.35 and the new file format should be done
at some point, but not now unplanned (it accidentally slipped in by the
merge) - so I'm uploading 2:3.35-2ubuntu1+really3.34-1ubuntu2 to un-
break it for now.

[1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql

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

Title:
  failing autopkgtest due to password issue by nss

Status in freeipa package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I was failed by autopkgtests of freeipa, but not the old "ip route output 
changed" case.
  Like: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/f/freeipa/20180201_161632_c9091@/log.gz

  It essentially does this and fails:
  $ apt install freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib python-ipaserver python-ipatests

  Containers:
  Bionic-as-is: installs ok
  Bionic-Proposed: installs ok

  In LP Infra:
  dpkg: error processing package freeipa-client (--configure):
   installed freeipa-client package post-installation script subprocess 
returned error exit status 1

  Use Pinning to get the autopkgtest style:
  # cat /etc/apt/preferences.d/nssonlyproposed
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  Package: libnss3 libnss3-tools libnss3-dev libnss3-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 1002
  Bionic-nss-only-from-Proposed: TRIGGERS the issue

  freeipa-client is in the postinst calling this:
  python2 -c 'from ipapython.certdb import update_ipa_nssdb; update_ipa_nssdb()'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 64, in 
update_ipa_nssdb
  create_ipa_nssdb()
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 53, in 
create_ipa_nssdb
  db.create_db(pwdfile)
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 149, in 
create_db
  self.run_certutil(["-N", "-f", password_filename])
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 142, in 
run_certutil
  return ipautil.run(new_args, stdin, **kwargs)
File "/usr/lib/python2.7/dist-packages/ipapython/ipautil.py", line 515, in 
run
  raise CalledProcessError(p.returncode, arg_string, str(output))
  subprocess.CalledProcessError: Command '/usr/bin/certutil -d /etc/ipa/nssdb 
-N -f /etc/ipa/nssdb/pwdfile.txt' returned non-zero exit status 255

  
  That is - if called alone complaining about the passwd:
  # /usr/bin/certutil -d /etc/ipa/nssdb -N -f 

[Touch-packages] [Bug 1747390] Re: package libidn11:amd64 1.32-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libidn11:amd64 1.32-3ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libidn package in Ubuntu:
  New

Bug description:
  it happens all the time, I think it's when I boot my computer...
  Everything seems to work quite ok, but there is always this bug crash
  report ! thx !

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libidn11:amd64 1.32-3ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  2 11:54:41 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libidn11:amd64:1.32-3ubuntu1.2
   Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
   dpkg: error processing package libidn11:amd64 (--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-04-12 (298 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libidn
  Title: package libidn11:amd64 1.32-3ubuntu1.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/libidn/+bug/1747390/+subscriptions

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

[Touch-packages] [Bug 1747390] [NEW] package libidn11:amd64 1.32-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[sandra Eno]

Public bug reported:

it happens all the time, I think it's when I boot my computer...
Everything seems to work quite ok, but there is always this bug crash
report ! thx !

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libidn11:amd64 1.32-3ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb  2 11:54:41 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
DuplicateSignature:
 package:libidn11:amd64:1.32-3ubuntu1.2
 Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
 dpkg: error processing package libidn11:amd64 (--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-04-12 (298 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libidn
Title: package libidn11:amd64 1.32-3ubuntu1.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)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libidn11:amd64 1.32-3ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libidn package in Ubuntu:
  New

Bug description:
  it happens all the time, I think it's when I boot my computer...
  Everything seems to work quite ok, but there is always this bug crash
  report ! thx !

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libidn11:amd64 1.32-3ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Feb  2 11:54:41 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libidn11:amd64:1.32-3ubuntu1.2
   Setting up libc6-dev:amd64 (2.23-0ubuntu10) ...
   dpkg: error processing package libidn11:amd64 (--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-04-12 (298 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libidn
  Title: package libidn11:amd64 1.32-3ubuntu1.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/libidn/+bug/1747390/+subscriptions

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

[Touch-packages] [Bug 1746947] Re: failing autopkgtest due to password issue by nss

[ChristianEhrhardt]

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

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

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

Title:
  failing autopkgtest due to password issue by nss

Status in freeipa package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I was failed by autopkgtests of freeipa, but not the old "ip route output 
changed" case.
  Like: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/f/freeipa/20180201_161632_c9091@/log.gz

  It essentially does this and fails:
  $ apt install freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-common freeipa-client freeipa-admintools freeipa-tests python-ipaclient 
python-ipalib python-ipaserver python-ipatests

  Containers:
  Bionic-as-is: installs ok
  Bionic-Proposed: installs ok

  In LP Infra:
  dpkg: error processing package freeipa-client (--configure):
   installed freeipa-client package post-installation script subprocess 
returned error exit status 1

  Use Pinning to get the autopkgtest style:
  # cat /etc/apt/preferences.d/nssonlyproposed
  Package: *
  Pin: release a=bionic
  Pin-Priority: 1001
  Package: libnss3 libnss3-tools libnss3-dev libnss3-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 1002
  Bionic-nss-only-from-Proposed: TRIGGERS the issue

  freeipa-client is in the postinst calling this:
  python2 -c 'from ipapython.certdb import update_ipa_nssdb; update_ipa_nssdb()'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 64, in 
update_ipa_nssdb
  create_ipa_nssdb()
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 53, in 
create_ipa_nssdb
  db.create_db(pwdfile)
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 149, in 
create_db
  self.run_certutil(["-N", "-f", password_filename])
File "/usr/lib/python2.7/dist-packages/ipapython/certdb.py", line 142, in 
run_certutil
  return ipautil.run(new_args, stdin, **kwargs)
File "/usr/lib/python2.7/dist-packages/ipapython/ipautil.py", line 515, in 
run
  raise CalledProcessError(p.returncode, arg_string, str(output))
  subprocess.CalledProcessError: Command '/usr/bin/certutil -d /etc/ipa/nssdb 
-N -f /etc/ipa/nssdb/pwdfile.txt' returned non-zero exit status 255

  
  That is - if called alone complaining about the passwd:
  # /usr/bin/certutil -d /etc/ipa/nssdb -N -f /etc/ipa/nssdb/pwdfile.txt
  Invalid password.
  certutil: Could not set password for the slot: SEC_ERROR_BAD_PASSWORD: The 
security password entered is incorrect.

  
  Note that there is a related freeipa fix in later versions:
 freeipa (4.6.2-4) unstable; urgency=medium 
  

  
   * client.postinst: Migrate from old nssdb only if it exists.

  And since that change freeipa has:
  if [ -f /etc/ipa/nssdb/cert8.db ]; then
  around the call.

  It also changed the import slightly - now the python being:

  python2 -c 'from ipaclient.install.client import update_ipa_nssdb;
  update_ipa_nssdb()'

  That in the "all-proposed" case with the cert8.db file copied over is still 
failing but differently:
  /usr/bin/certutil -d /etc/ipa/nssdb -L -f /etc/ipa/nssdb/pwdfile.txt
  certutil: function failed: SEC_ERROR_BAD_DATABASE: security library: bad 
database.

  The merge of nss was a minor bump 3.34->3.35
  Also this is the nss version from Debian with the freeipa version from 
Debian. They seem to work together there.

  I don't fully understand it yet - so filing this bug for a discussion.
  I need the help of tjaalton who did the freeipa changes - maybe he knows what 
is going on.

  Do we have to:
  - rebuild freeipa against newer nss?
  - just mark something as bad test
  - something completely else?

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Released
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Launchpad Bug Tracker]

This bug was fixed in the package modemmanager - 1.6.4-1ubuntu0.16.04.1

---
modemmanager (1.6.4-1ubuntu0.16.04.1) xenial; urgency=medium

  * Backport to xenial (LP: #1725190).
  * debian/control: bump down debhelper to xenial vesion.

 -- Łukasz 'sil2100' Zemczak   Tue, 28 Nov
2017 12:40:02 +0100

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

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Released
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

[Vincenzo Do]

Any updates on this bug? Is there a fix on the way? I'm experiencing
this problem on 16.04 Ubuntu.

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

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20120223'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog to /var/log/syslog-20120223
  running postrotate script
  removing old log /var/log/syslog-20111219.gz

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log needs rotating
  considering log /var/log/auth.log
log needs rotating
  considering log /var/log/user.log
log 

[Touch-packages] [Bug 1747128] Re: RM: obsolete product

[Will Cooke]

+1 to remove.  This was a part of Unity 8 which we dropped from the
archive, so this can go too.

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

Title:
  RM: obsolete product

Status in mediascanner2 package in Ubuntu:
  Triaged

Bug description:
  mediascanner2 was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:mediascanner2
  No reverse dependencies found

  $ reverse-depends -b src:mediascanner2
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  ModemManager uses a wrong plugin for Dell DW5818/5819

Status in OEM Priority Project:
  Fix Released
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  * Dell Wireless DW5818/5819 modems showed an incorrect signal strength
  and were using a ttyUSB* port for data connections instead of the MBIM
  device (which provides better performance).

  Since linux-4.4.0-98, the kernel additionally loads gcserial driver
  for Dell Wireless DW5818/5819. The reason behind it is to support
  firmware switching and upgrading. However, the change makes
  ModemManager use Gobi plugin for this two modules. With Gobi plugin,
  the modules could establish data links, but it failed to retrieve the
  signal state. And it caused the mmcli and nm-applet giving wrong
  signal strength. The modules support the MBIM protocol, so
  ModemManager should use Dell plugin for these two modules.

  I have worked out a patch to forbid these two modules in Gobi plugin,
  and it does work well.

  [Test Case]

  Current MM:
  * Create connection with 
  $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn 
  * Without the patched package, mmcli shows, with an active connection (see 
comment #2):
  primary port: 'ttyUSB2'
  signal quality: '0' (recent)

  Patched MM:
  * Create connection with 
  $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn 
  * With the patched package, mmcli shows, with an active connection (see 
comment #7):
  primary port: 'cdc-wdm0'
  signal quality: '38' (cached)

  [Regression Potential]

  The patch simply adds the Sierra modems VID/PIDs to the list of
  forbidden ids in the Gobi plugin, so the possibility of a regression
  is very small: only products with said VID/PID will be affected.

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

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

[Touch-packages] [Bug 1746949] Re: Terminal lags (low FPS) the whole desktop when fast output

[Jean-Louis Dupond]

The following commit fixes the issue for 90%:
https://git.gnome.org/browse/vte/commit/?id=809e79770

its not as fast as it was on X, but its useable now :)

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

Title:
  Terminal lags (low FPS) the whole desktop when fast output

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

Bug description:
  Hi,

  When using Wayland and gnome-terminal, the performance/fps of the
  whole desktop is real low when gnome-terminal outputs alot of data.

  This happens when you cat some logfile for example, or do a tail -f on a 
quickly growing file.
  The whole desktop feels sluggish then.

  This is only the case on Wayland. on X-Server it goes perfectly!

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Yuan-Chen Cheng]

fix release as LP: #1725190 does.

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

** Changed in: oem-priority/xenial
   Status: Fix Committed => Fix Released

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

  - wait landing: LP: #1725190

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

[Egmont Koblinger]

Well, the title can be changed :) Anyway, it's not worth further
discussing, rather than working on the actual bug. Let's get back to
business...

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Launchpad Bug Tracker]

This bug was fixed in the package libqmi - 1.16.2-1ubuntu0.16.04.1

---
libqmi (1.16.2-1ubuntu0.16.04.1) xenial; urgency=medium

  * Backport to xenial (LP: #1725190).
  * debian/control: bump down debhelper to xenial vesion.

 -- Łukasz 'sil2100' Zemczak   Tue, 28 Nov
2017 12:55:17 +0100

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

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

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Committed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Launchpad Bug Tracker]

This bug was fixed in the package libmbim - 1.14.0-1ubuntu0.16.04.1

---
libmbim (1.14.0-1ubuntu0.16.04.1) xenial; urgency=medium

  * Backport to xenial (LP: #1725190).

 -- Łukasz 'sil2100' Zemczak   Tue, 28 Nov
2017 13:02:56 +0100

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Committed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

[Daniel van Vugt]

Yes we do do that sometimes. However there was an additional reason to
keep this one other than its age; the title is much more helpful and
specific. By comparison "gnome-terminal graphic artifact" could refer to
any number of different problems.

An accurate title is crucial in helping people to find existing bugs and
avoid logging more duplicates. And so it brings more people together
faster, leading to speedier resolutions, hopefully.

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Touch-packages] [Bug 1725190] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for modemmanager 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 modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Fix Committed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Released
Status in libqmi source package in Xenial:
  Fix Released
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Touch-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

[Egmont Koblinger]

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

Thanks, it's pretty clear now that the bug is present on X11 only.

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

Title:
  gnome-terminal graphic artifact

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  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: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  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/1724250/+subscriptions

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

[Egmont Koblinger]

(Daniel, may I please kindly recommend that next time when one of the
bugs contains all the information present in the other plus much-much
more then mark it as duplicate the other way around, even if
chronologically incorrect? IMO that's much more useful for continuing to
work on it and hopefully getting it fixed eventually. Thanks!)

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Jens Greifenhagen]

I found another workaround, that works fine without changing package versions 
or DNS servers.
It is tested with the issues I had with openconnect for NM.

it is "just" killing the dnsmasq instance and it gets restarted
automatically which then results in a working system again. It easy and
not pretty, but works. Then only (perhaps) noticeable interruption is a
few seconds where DNS is not working 15 seconds after the connection has
been established:

$ cat /etc/NetworkManager/dispatcher.d/99-openconnect-dnsmasq-bug
#!/bin/bash
set -e
# force restart of dnsmasq on vpn connect

if [[ "$1" =~ "vpn" ]] && [ $2 = "up" ]
then
  if [ -e /var/run/NetworkManager/dnsmasq.pid ]
  then
$( sleep 15 && /bin/kill -15 $(cat /var/run/NetworkManager/dnsmasq.pid) )
  fi
fi

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

[Egmont Koblinger]

Please see the duplicate bug 1724250 for some hopefully precious
investigation I've done so far.

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  
file:///home/castilhos/Imagens/Captura%20de%20tela%20de%202017-09-19%2012-43-54.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+subscriptions

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

[Touch-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

[Michael Vescovo]

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

ok so my home machine says wayland and does not have the problem. So
maybe something with x11.

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

Title:
  gnome-terminal graphic artifact

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  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: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  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/1724250/+subscriptions

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

[Touch-packages] [Bug 1747303] Re: Missing man pages of all packages which offer some

[Julian Andres Klode]

No, it's not apt.

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

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

Title:
  Missing man pages of all packages which offer some

Status in Ubuntu:
  Invalid

Bug description:
  First of all, I installed Ubuntu 18.04 from the base package listed
  here: http://cdimage.ubuntu.com/ubuntu-base/daily/current/ . It's now
  a full working station with Ubuntu-Mate desktop. The problem are the
  manual pages which aren't installed, many of them. Here are the
  dictionary entries of /usr/share/man/man1:

  $ ls -la  /usr/share/man/man1
  drwxr-xr-x  2 root root 4096 Jan 30 22:36 ./
  drwxr-xr-x 26 root root 4096 Jan 18 14:23 ../
  lrwxrwxrwx  1 root root   27 Jan 20 16:27 java.1.gz -> 
/etc/alternatives/java.1.gz
  lrwxrwxrwx  1 root root   26 Jan 20 16:27 jjs.1.gz -> 
/etc/alternatives/jjs.1.gz
  lrwxrwxrwx  1 root root   30 Jan 20 16:27 keytool.1.gz -> 
/etc/alternatives/keytool.1.gz
  lrwxrwxrwx  1 root root   27 Jan 20 16:27 orbd.1.gz -> 
/etc/alternatives/orbd.1.gz
  lrwxrwxrwx  1 root root   30 Jan 20 16:27 pack200.1.gz -> 
/etc/alternatives/pack200.1.gz
  lrwxrwxrwx  1 root root   33 Jan 20 16:27 policytool.1.gz -> 
/etc/alternatives/policytool.1.gz
  lrwxrwxrwx  1 root root   27 Jan 20 16:27 rmid.1.gz -> 
/etc/alternatives/rmid.1.gz
  lrwxrwxrwx  1 root root   34 Jan 20 16:27 rmiregistry.1.gz -> 
/etc/alternatives/rmiregistry.1.gz
  lrwxrwxrwx  1 root root   33 Jan 20 16:27 servertool.1.gz -> 
/etc/alternatives/servertool.1.gz
  lrwxrwxrwx  1 root root9 Jan 30 22:36 sh.1.gz -> dash.1.gz
  lrwxrwxrwx  1 root root   32 Jan 20 16:27 tnameserv.1.gz -> 
/etc/alternatives/tnameserv.1.gz
  lrwxrwxrwx  1 root root   32 Jan 20 16:27 unpack200.1.gz -> 
/etc/alternatives/unpack200.1.gz
  -rw-r--r--  1 root root0 Jan 21 00:47 vmware.1.gz

  When I install the manpages-dev package, the package management shows me all 
fine:
  # apt install --reinstall manpages-dev
  # dpkg -L manpages-dev
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/manpages-dev
  /usr/share/man
  /usr/share/man/man2
  /usr/share/man/man2/_exit.2.gz
  /usr/share/man/man2/_syscall.2.gz
  /usr/share/man/man2/accept.2.gz
  ...
  /usr/share/man/man3/scalbnf.3.gz
  /usr/share/man/man3/scalbnl.3.gz
  /usr/share/man/man3/scandirat.3.gz
  ...and so on...

  But the /usr/share/man/man3 directory is still empty:
  # ls -la /usr/share/man/man3
  insgesamt 8
  drwxr-xr-x  2 root root 4096 Jan 18 14:23 .
  drwxr-xr-x 26 root root 4096 Jan 18 14:23 ..

  And btw the /usr/share/man/man2 directory doesn't exist.
  Are there any new configuration changes in 18.04 which supresses man page 
installation? I didn't know about a similar behavior in 17.10 and before.

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Sven Eppler]

The problem dissappeard for me after using the Ubuntu 16.04. HWE-Kernel
instead the default one.

Found the solution to this via another (similar) bug:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1573959

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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