[Touch-packages] [Bug 1663421] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

2017-02-25 Thread corrado venturini
I have this problem on a different destro:
corrado@corrado-z4:~$ inxi -Fx
System:Host: corrado-z4 Kernel: 4.10.0-9-generic x86_64 (64 bit gcc: 6.3.0)
   Desktop: Gnome  (Gtk 3.22.7-1ubuntu4) Distro: Ubuntu Zesty Zapus 
(development branch)
Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: American 
Megatrends v: F3 date: 04/24/2013
CPU:   Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13568
   clock speeds: max: 3400 MHz 1: 875 MHz 2: 892 MHz 3: 830 MHz 4: 1806 
MHz
Graphics:  Card: Intel 4th Generation Core Processor Family Integrated Graphics 
Controller bus-ID: 00:02.0
   Display Server: X.Org 1.18.4 drivers: modesetting (unloaded: 
fbdev,vesa)
   Resolution: 1680x1050@59.88hz
   GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 17.0.0 
Direct Rendering: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
   driver: snd_hda_intel bus-ID: 00:1b.0
   Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
   driver: snd_hda_intel bus-ID: 00:03.0
   Sound: Advanced Linux Sound Architecture v: k4.10.0-9-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
   IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 
94:de:80:7e:90:a7
Drives:HDD Total Size: 1000.2GB (1.5% used)
   ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 6.8G (23%) fs: ext4 dev: /dev/sda4
   ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
   Fan Speeds (in rpm): cpu: N/A
Info:  Processes: 220 Uptime: 9 min Memory: 1172.7/7861.2MB Init: systemd 
runlevel: 5 Gcc sys: 6.3.0
   Client: Shell (bash 4.4.51) inxi: 2.3.8 
corrado@corrado-z4:~$

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in ubuntu-mate:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04
  Destro: Ubuntu Mate
  Windows manager: Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  I get this error after usb-gtk-creator finish to upload a os on a usb
  stick.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 10 01:30:13 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-02-06 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=8b97de22-0e3b-4da0-8676-7c8865800def ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1663421] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

2017-02-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in ubuntu-mate:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04
  Destro: Ubuntu Mate
  Windows manager: Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  I get this error after usb-gtk-creator finish to upload a os on a usb
  stick.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 10 01:30:13 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-02-06 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=8b97de22-0e3b-4da0-8676-7c8865800def ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1668008] Re: apport-gtk crashed with SIGSEGV

2017-02-25 Thread Apport retracing service
*** This bug is a duplicate of bug 1552577 ***
https://bugs.launchpad.net/bugs/1552577

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1552577
   apport-gtk crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  New

Bug description:
  Error occurred on first boot Daily Build Ubuntu Desktop 17.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:1000:122:8395118:2017-02-26 00:31:24.667407274 -0600:2017-02-26 
00:31:25.667407274 -0600:/var/crash/_usr_bin_compiz.1000.crash
   640:1000:122:6792304:2017-02-26 00:31:35.076570510 -0600:2017-02-26 
00:31:36.076570510 -0600:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  CurrentDesktop: Unity:Unity7
  Date: Sun Feb 26 00:31:30 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  ExecutableTimestamp: 1486144051
  InstallationDate: Installed on 2017-02-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170225)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcCwd: /home/gene
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fbe38a84889:mov(%rbx),%rdi
   PC (0x7fbe38a84889) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  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/apport/+bug/1668008/+subscriptions

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


Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-25 Thread dkg
On Thu 2017-02-23 16:57:12 -0500, Launchpad Bug Tracker wrote:
>   * Add in libgpgme-dev a libgpgme-pthread.so pointing to libgpgme.so, this
> will fix the build failures of kf5-kdepim-apps-libs when built against 
> this
> gpgme package.

As i wrote when asked on IRC, i think this is the wrong fix for this
problem.

if kf5-kdepim-apps-libs is being built correctly, it should be using
gpgme-config from libgpgme-dev itself to choose how to link, which
should know which .so to link against.

why should this additional symlink be necessary for the build of
kf5-kdepim-apps-libs?

maybe i'm misunderstanding something about the build of
kf5-kdepim-apps-libs.  can you explain more?

   --dkg

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Fix Released

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

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

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


[Touch-packages] [Bug 1668004] [NEW] graphics card not working

2017-02-25 Thread Subash Aryal
Public bug reported:

brightness is at its peak level and i couldnt minimize it

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Feb 26 10:24:13 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
InstallationDate: Installed on 2016-12-21 (66 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Inspiron 5547
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=27b5964a-b584-4adc-b09c-2e3bff484e9a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0598GM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5547:pvrA10:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Inspiron 5547
dmi.product.version: A10
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.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Feb 26 10:12:16 2017
xserver.configfile: default
xserver.errors: intel(0): Unrecognised backlight control interface 'intel'
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4588 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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

Title:
  graphics card not working

Status in xorg package in Ubuntu:
  New

Bug description:
  brightness is at its peak level and i couldnt minimize it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb 26 10:24:13 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
  InstallationDate: Installed on 2016-12-21 (66 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 5547
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=27b5964a-b584-4adc-b09c-2e3bff484e9a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5547:pvrA10:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron 5547
  

[Touch-packages] [Bug 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit

2017-02-25 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering
  Edit

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA
  Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my
  computer, the mouse pointer is somehow "captured" by the last active
  window. I can switch windows via alt-tab but left clicks in the new
  window still won't work, they will only work in the "old" window.

  WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the 
following:
  Section "InputClass"
   Identifier "Jabra"
  MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
   Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0"
  EndSection

  and restart xorg-server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Sep  1 14:47:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  1 11:27:32 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


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

2017-02-25 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-intel
   Status: Confirmed => Invalid

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

Title:
  Intel DRM GPU hang in Kubuntu 15.04

Status in xf86-video-intel:
  Invalid
Status in xorg package in Ubuntu:
  Incomplete

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

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

  
  -- Logcat output --

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

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

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

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


[Touch-packages] [Bug 1667995] [NEW] Auto Login is not working and long screen lock unable to unlock

2017-02-25 Thread Romulo
Public bug reported:

If I enable autologin it did not work (black screen), I need to change
tty and delete lightdm.conf. It can`t recover from long term locking
too, some times it show a black screen, others it returns with a broken
renderization.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 25 23:30:36 2017
InstallationDate: Installed on 2016-09-20 (158 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Auto Login is not working and long screen lock unable to unlock

Status in lightdm package in Ubuntu:
  New

Bug description:
  If I enable autologin it did not work (black screen), I need to change
  tty and delete lightdm.conf. It can`t recover from long term locking
  too, some times it show a black screen, others it returns with a
  broken renderization.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 25 23:30:36 2017
  InstallationDate: Installed on 2016-09-20 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1385863] Re: Constant minimum load of 1.00 after upgrade to 14.10 (Xubuntu)

2017-02-25 Thread Stephen Michael Kellat
** Changed in: procps (Ubuntu)
   Status: New => Invalid

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

Title:
  Constant minimum load of 1.00 after upgrade to 14.10 (Xubuntu)

Status in procps package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I upgraded (from 14.04) to 14.10 (via the graphical upgrade program on 
desktop) on my computer and after that I get a constant load of minimum 1.00 
(read via top).
  It seems to be a bug, because CPU (read via htop) and HDD (read via iotop) 
are idle.

  [Top output shown in an attachment]

  Is there any way to prove that this is a bug?

  Regards

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-02-25 Thread Douglas H. Silva
Any change after 16.04.2? New kernel 4.8...

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1228922] Re: Provide a property to make a ListView header "sticky"

2017-02-25 Thread Adnane Belmadiaf
It was part of Qt Quick 2.4

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

Title:
  Provide a property to make a ListView header "sticky"

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  BlackBerry Cascades (their Qml toolkit) provides a
  "ListHeaderMode.Sticky" property  that would be very welcome in the
  Ubuntu Toolkit. I'll let their docs describe it:

  "We also use the headerMode property to customize the behavior of the
  header items in the list. By using ListHeaderMode.Sticky, when the
  list scrolls and a header reaches the top of the visible area, the
  header stays there (or "sticks") as the list continues to scroll,
  until a new header reaches the top."

  
http://developer.blackberry.com/native/documentation/cascades/ui/lists/lists_create_main_ui.html

  The Unity8 Dash seems to have an internal component that works in a
  similar fashion. Maybe it could be generalized:

  http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/files/head:/plugins/ListViewWithPageHeader/

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

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


[Touch-packages] [Bug 1228922] Re: Provide a property to make a ListView header "sticky"

2017-02-25 Thread Adnane Belmadiaf
It was part of Qt 2.4

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

Title:
  Provide a property to make a ListView header "sticky"

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  BlackBerry Cascades (their Qml toolkit) provides a
  "ListHeaderMode.Sticky" property  that would be very welcome in the
  Ubuntu Toolkit. I'll let their docs describe it:

  "We also use the headerMode property to customize the behavior of the
  header items in the list. By using ListHeaderMode.Sticky, when the
  list scrolls and a header reaches the top of the visible area, the
  header stays there (or "sticks") as the list continues to scroll,
  until a new header reaches the top."

  
http://developer.blackberry.com/native/documentation/cascades/ui/lists/lists_create_main_ui.html

  The Unity8 Dash seems to have an internal component that works in a
  similar fashion. Maybe it could be generalized:

  http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/files/head:/plugins/ListViewWithPageHeader/

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

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


[Touch-packages] [Bug 1228922] Re: Provide a property to make a ListView header "sticky"

2017-02-25 Thread Adnane Belmadiaf
This is already possible with ListView, you can even do more complex
stuff with it, attaching a full demo that explain the usage.

Can someone mark this as invalid ?

** Attachment added: "Main.qml"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1228922/+attachment/4826775/+files/Main.qml

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

Title:
  Provide a property to make a ListView header "sticky"

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  BlackBerry Cascades (their Qml toolkit) provides a
  "ListHeaderMode.Sticky" property  that would be very welcome in the
  Ubuntu Toolkit. I'll let their docs describe it:

  "We also use the headerMode property to customize the behavior of the
  header items in the list. By using ListHeaderMode.Sticky, when the
  list scrolls and a header reaches the top of the visible area, the
  header stays there (or "sticks") as the list continues to scroll,
  until a new header reaches the top."

  
http://developer.blackberry.com/native/documentation/cascades/ui/lists/lists_create_main_ui.html

  The Unity8 Dash seems to have an internal component that works in a
  similar fashion. Maybe it could be generalized:

  http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/files/head:/plugins/ListViewWithPageHeader/

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

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


[Touch-packages] [Bug 1667987] [NEW] Panasonic Toughbook CF-AX2 No Audio

2017-02-25 Thread Patrick Watson
Public bug reported:

The audio chipset is detected in alsamixer but won't output audio
through the speakers, tested on 2 exact same models.

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

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

Title:
  Panasonic Toughbook CF-AX2 No Audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The audio chipset is detected in alsamixer but won't output audio
  through the speakers, tested on 2 exact same models.

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

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


[Touch-packages] [Bug 1636573] Re: xinit flooding syslog

2017-02-25 Thread MoiZie
Finally just updated to Ubuntu 17.04 beta 1 to get rid of this
problem...

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

Title:
  xinit flooding syslog

Status in pyopenssl package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

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

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


[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

2017-02-25 Thread Jarno Suni
How about SRU?

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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


[Touch-packages] [Bug 1667604] Re: Cannot use window controls on a laptop with touchscreen

2017-02-25 Thread Lukáš Tinkl
** Changed in: unity8 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Cannot use window controls on a laptop with touchscreen

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Zesty Desktop up to date on Dell Inspiron 11 3000 with touchscreen

  The user cannot interact with the window controls
  (close/minimize/maximize on the left of the title bar) with his
  fingers. Taping them does nothing but they work fine with the mouse or
  trackpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 24 09:56:57 2017
  InstallationDate: Installed on 2014-07-23 (946 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-15 (100 days ago)

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

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


[Touch-packages] [Bug 1667523] Re: Unable to search in Evince in PDFs opened from Firefox with Firefox AppArmor profile enabled

2017-02-25 Thread Jeremy Nation
Adding the "unix..." line to ubuntu-helpers as you suggested fixed the
search problem in Evince, thanks. What does that line do? I don't know
much about AppArmor.

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

Title:
  Unable to search in Evince in PDFs opened from Firefox with Firefox
  AppArmor profile enabled

Status in apparmor package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.2 LTS with Unity
  Firefox 51.0.1+build2-0ubuntu0.16.04.2
  Evince 3.18.2-1ubuntu4
  AppArmor/apparmor-profiles 2.10.95-0ubuntu2.5

  Steps to reproduce:

  1) Enable AppArmor: service apparmor start
  2) Enable Firefox AppArmor profile: aa-enforce /etc/apparmor.d/usr.bin.firefox
  3) Reload AppArmor: service apparmor reload
  4) Browse to https://help.ubuntu.com/lts/serverguide/serverguide.pdf in 
Firefox
  5) Select "Open with: Document Viewer"
  6) Type ctrl-F "Ubuntu"

  Expected behavior:
  "Ubuntu" appears in the search box at the top and is highlighted in the 
document.

  Observed behavior:
  The search box stays empty and nothing is highlighted in the document.

  Workarounds:
  * Select "Save File" instead of "Open with" and then open the file outside of 
Firefox with Nautilus, terminal etc
  or
  * Disable the Firefox AppArmor profile with "aa-disable 
/etc/apparmor.d/usr.bin.firefox", "service apparmor reload" and then you can 
search after selecting "Open with".

  You may need to restart Firefox and/or Evince after toggling Firefox's
  AppArmor profile for the changes to take effect.

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

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


[Touch-packages] [Bug 1667974] [NEW] app crashed on login and on daily update call

2017-02-25 Thread Paweł Prochal
Public bug reported:

app crashed on login and on daily update call

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unattended-upgrades 0.92ubuntu1.2
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 25 22:53:59 2017
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  app crashed on login and on daily update call

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  app crashed on login and on daily update call

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unattended-upgrades 0.92ubuntu1.2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 25 22:53:59 2017
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667972] [NEW] package udev 231-9ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2017-02-25 Thread André
Public bug reported:

The issue ocours in a system upgrade, it's al I can say right now,
sorry.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: udev 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Sat Feb 25 17:27:33 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
MachineType: Dell Inc. Vostro 3500
ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: systemd
Title: package udev 231-9ubuntu3 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)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 056TK2
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Vostro 3500
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package yakkety

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

Title:
  package udev 231-9ubuntu3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in systemd package in Ubuntu:
  New

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sat Feb 25 17:27:33 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  MachineType: Dell Inc. Vostro 3500
  ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: systemd
  Title: package udev 231-9ubuntu3 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)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 056TK2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Vostro 3500
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1667971] [NEW] package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2017-02-25 Thread André
Public bug reported:

The issue ocours in a system upgrade, it's al I can say right now,
sorry.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: initramfs-tools 0.125ubuntu6.3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Thu Feb 23 10:50:41 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu6.3 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)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  package initramfs-tools 0.125ubuntu6.3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu6.3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Feb 23 10:50:41 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu6.3 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)

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

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


[Touch-packages] [Bug 1667973] [NEW] package udev 231-9ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2017-02-25 Thread André
Public bug reported:

The issue ocours in a system upgrade, it's al I can say right now,
sorry.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: udev 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Sat Feb 25 17:27:33 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
MachineType: Dell Inc. Vostro 3500
ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: systemd
Title: package udev 231-9ubuntu3 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)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 056TK2
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Vostro 3500
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package yakkety

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

Title:
  package udev 231-9ubuntu3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in systemd package in Ubuntu:
  New

Bug description:
  The issue ocours in a system upgrade, it's al I can say right now,
  sorry.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sat Feb 25 17:27:33 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  MachineType: Dell Inc. Vostro 3500
  ProcKernelCmdLine: 
file=/cdrom/multiboot/lubuntu-16.10-desktop-amd64/preseed/lubuntu.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/lubuntu-16.10-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/lubuntu-16.10-desktop-amd64/casper/ 
initrd=/multiboot/lubuntu-16.10-desktop-amd64/casper/initrd.lz quiet splash --- 
locale=pt_BR keyboard-configuration/layoutcode?=br 
keyboard-configuration/modelcode?=abnt2
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: systemd
  Title: package udev 231-9ubuntu3 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)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 056TK2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3500:pvrA12:rvnDellInc.:rn056TK2:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Vostro 3500
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1409133] Re: Heavy black flickering with Intel graphics after VT switching from X to Mir

2017-02-25 Thread Bug Watch Updater
** Changed in: linux
   Status: Incomplete => Won't Fix

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

Title:
  Heavy black flickering with Intel graphics after VT switching from X
  to Mir

Status in Linux:
  Won't Fix
Status in Mir:
  Invalid
Status in linux package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Invalid

Bug description:
  After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 
1, the demo server really flickers black quite a lot (entire screen, pointer 
included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic 
at the same time, if it's because of that, please mark invalid.
  --- 
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  william5932 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 3249CTO
  Package: mir
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.140
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Tags:  vivid
  Uname: Linux 3.18.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev 
sambashare sbuild sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET35WW (1.05 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 603128] Re: python-magic is incomplete on Ubuntu LTS?

2017-02-25 Thread Pander
** Tags removed: yakkety

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

Title:
  python-magic is incomplete on Ubuntu LTS?

Status in file package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file

  I'm running Ubuntu 10.04 LTS.

  I installed python-magic with: sudo apt-get install python-magic (the
  file that gets installed is python-magic_5.03-5ubuntu1_i386.deb)

  However, when I start Python (version 2.6.5) and I "import magic" and
  I then do "dir(magic)", it seems as though the module does not contain
  all the definitions that I can see on python-magic's github repo (i.e.
  the Ubuntu package seems outdated):

  ['MAGIC_APPLE', 'MAGIC_CHECK', 'MAGIC_COMPRESS', 'MAGIC_CONTINUE',
  'MAGIC_DEBUG', 'MAGIC_DEVICES', 'MAGIC_ERROR', 'MAGIC_MIME',
  'MAGIC_MIME_ENCODING', 'MAGIC_MIME_TYPE', 'MAGIC_NONE',
  'MAGIC_NO_CHECK_APPTYPE', 'MAGIC_NO_CHECK_CDF',
  'MAGIC_NO_CHECK_COMPRESS', 'MAGIC_NO_CHECK_ELF',
  'MAGIC_NO_CHECK_ENCODING', 'MAGIC_NO_CHECK_SOFT',
  'MAGIC_NO_CHECK_TAR', 'MAGIC_NO_CHECK_TEXT', 'MAGIC_NO_CHECK_TOKENS',
  'MAGIC_PRESERVE_ATIME', 'MAGIC_RAW', 'MAGIC_SYMLINK', '__doc__',
  '__file__', '__name__', '__package__', 'error', 'open']

  What's up? Am I doing something wrong?

  Joubert

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

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


[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread Ubuntu Foundations Team Bug Bot
The attachment "lp1667227_quick_fix_gtk_grab_remove.gtk+3.22.8.patch"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  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/gnome-terminal/+bug/1667227/+subscriptions

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


[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-02-25 Thread Mark van den Nieuwenhuizen
inxi -N: Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network 
Adapter
   driver: ath9k
   Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   driver: r8169


** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+attachment/4826661/+files/lsusb.txt

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

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

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


[Touch-packages] [Bug 1667968] [NEW] Ubuntu 16.10 kernel 4.8.0-39 No network connectivity

2017-02-25 Thread JerryLumpkins
Public bug reported:

My last kernel update changed something that is causing the network
manager to fail to load anything but the lo device.

If I reboot into the previous kernel (4.8.0-38) everything works fine.

I'm not certain that this issue is related to the NetworkManger or the
Kernel, but the bottom line is I have not ethernet when I boot using the
latest kernel.

This is one of three computers I built a few years back.
It's based on an Asus motherboard: P5G41T-M LX PLUS, BIOS 050210/21/2011
The eth0 NIC is on the motherboard.

Any info you need, I will try and provide.
Any help you might offer would be appreciated.

I run apt-get update followed by apt-get dist-upgrade every day.
This is the first time I've had a serious problem as a byproduct of updating.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 16.10 kernel 4.8.0-39  No network connectivity

Status in network-manager package in Ubuntu:
  New

Bug description:
  My last kernel update changed something that is causing the network
  manager to fail to load anything but the lo device.

  If I reboot into the previous kernel (4.8.0-38) everything works fine.

  I'm not certain that this issue is related to the NetworkManger or the
  Kernel, but the bottom line is I have not ethernet when I boot using
  the latest kernel.

  This is one of three computers I built a few years back.
  It's based on an Asus motherboard: P5G41T-M LX PLUS, BIOS 050210/21/2011
  The eth0 NIC is on the motherboard.

  Any info you need, I will try and provide.
  Any help you might offer would be appreciated.

  I run apt-get update followed by apt-get dist-upgrade every day.
  This is the first time I've had a serious problem as a byproduct of updating.

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

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


[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-02-25 Thread Mark van den Nieuwenhuizen
I did test 1.2.6-0ubuntu0.16.04.1 and my observation is that the network
applet is shown correctly and is functional as expected in about 70% of
the resume situations. In the other cases killing and restarting the
applet is a work around.

I also tested the network manager on Manjaro 16.10.3 and Korora 25. Both
of them showed the behavior this SRU tries to fix.

My laptop:

Linux mark-Aspire-ES1-512 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

Attached is the output of inxi -N, lsusb -vvv, lspci -vvvnn


** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+attachment/4826660/+files/lspci.txt

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

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

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


[Touch-packages] [Bug 1667929] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-02-25 Thread Jerome Carlier
As requested
/var/lib/dpkg/alternatives/pico 

** Attachment added: "/var/lib/dpkg/alternatives/pico"
   
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1667929/+attachment/4826658/+files/pico

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

Title:
  package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in nano package in Ubuntu:
  New

Bug description:
  it crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Feb 25 14:28:00 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-25  14:01:31
   Commandline: aptdaemon role='role-commit-packages' sender=':1.34'
   Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), 
linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), 
xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), 
linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 
(4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 
2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), 
linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68)
  DuplicateSignature:
   package:nano:2.5.3-2ubuntu2
   Setting up nano (2.5.3-2ubuntu2) ...
   update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid 
status
   dpkg: error processing package nano (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nano
  Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15
** Patch added: "lp1667227_quick_fix_gtk_grab_remove.gtk+3.22.8.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1667227/+attachment/4826656/+files/lp1667227_quick_fix_gtk_grab_remove.gtk+3.22.8.patch

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  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/gnome-terminal/+bug/1667227/+subscriptions

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


[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15
Bug can be detected by "Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion 
'GTK_IS_WIDGET (widget)' failed" messages, when mate-terminal or gnome-terminal 
are started from another console (with option --disable-factory) and keyboard 
shortcuts are edited.
I have such messages with gtk+3 (upstream) versions 3.16.7, 3.18.9, 3.20.9, 
3.22.8; valgrind can detect invalid reads (use after free) from 
window_group_cleanup_grabs -> gtk_widget_get_toplevel.

Simple, but potentially incorrect patch corrects this bug (both Gtk-CRITICAL 
messages and valgrind detections/SIGSEGVs) in mate-terminal and gnome-terminal 
(bug #1667232). It is tested with gtk+3 3.16.7, 3.18.9, 3.20.9, 3.22.8.
Just call _gtk_window_group_remove_grab from gtkmain.c:gtk_grab_remove twice, 
additional call with default window group, to clear all possible references to 
the widget from the grabs list:

diff --git a/gtk/gtkmain.c b/gtk/gtkmain.c
index 3152971256..681cb2bec9 100644
--- a/gtk/gtkmain.c
+++ b/gtk/gtkmain.c
@@ -2274,6 +2274,9 @@ gtk_grab_remove (GtkWidget *widget)
 
   group = gtk_main_get_window_group (widget);
   _gtk_window_group_remove_grab (group, widget);
+  // quick workaround for lp #1667227, lp #1667232
+  _gtk_window_group_remove_grab (gtk_window_get_group (NULL), widget);
+
   new_grab_widget = gtk_window_group_get_current_grab (group);
 
   gtk_grab_notify (group, NULL, widget, new_grab_widget, FALSE);

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  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/gnome-terminal/+bug/1667227/+subscriptions

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


[Touch-packages] [Bug 1667963] [NEW] QuiteRSS AppArmor profile

2017-02-25 Thread Raúl Vidal
Public bug reported:

Test plan:
1. Boot application.
2. Add feed
3. Update feeds
4. Read some feed.
5. Open link in external browser.
6. Click to view page inside QuiteRSS.
7. Export feeds.
8. Go to preferences, change something.
9. Hide window (minimize it)
9. Use notification area menu to show update feeds, show window.
10. Close application.

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

** Attachment added: "usr.bin.quiterss"
   
https://bugs.launchpad.net/bugs/1667963/+attachment/4826650/+files/usr.bin.quiterss

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

Title:
  QuiteRSS AppArmor profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Test plan:
  1. Boot application.
  2. Add feed
  3. Update feeds
  4. Read some feed.
  5. Open link in external browser.
  6. Click to view page inside QuiteRSS.
  7. Export feeds.
  8. Go to preferences, change something.
  9. Hide window (minimize it)
  9. Use notification area menu to show update feeds, show window.
  10. Close application.

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

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


[Touch-packages] [Bug 1663995] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-02-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The crash report showed up after booting into the Ubuntu zesty gnome-
  box VM.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Wed Feb  8 17:55:08 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2016-12-12 (62 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161212)
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic 
root=UUID=94725cee-90e1-46f9-9302-b95a819cb4a2 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55a182679ec0, argc=1, argv=0x7ffca3d913b8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffca3d913a8) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.0.0-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.0.0-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

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


[Touch-packages] [Bug 1667958] [NEW] Mouse becomes erratiic after a while

2017-02-25 Thread unknown
Public bug reported:

Standard external usb mouse, after the system has been up for a variable time, 
sometimes a few hours sometimes 2 days the mouse does not properly move around 
the screen and it also does not properly respond to right and left click, it 
will take many attempts before the button presses are recognised.
A reboot does fix it, but it should not need rebooting so often.

xorg was used because it seems to be the xorg mouse drivers that are in
use.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Feb 25 18:15:16 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Skylake Integrated Graphics 
[1458:d000]
InstallationDate: Installed on 2016-05-03 (297 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=4db7fc40-87b9-494c-8c02-5b4c4ff8abc8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5j
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-UD5-CF
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: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5j:bd01/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170X-UD5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Feb 23 07:57:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   30934 
 vendor BNQ
xserver.version: 2:1.18.4-0ubuntu0.2

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

Title:
  Mouse becomes erratiic after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  Standard external usb mouse, after the system has been up for a variable 
time, sometimes a few hours sometimes 2 days the mouse does not properly move 
around the screen and it also does not properly respond to right and left 
click, it will take many attempts before the button presses are recognised.
  A reboot does fix it, but it should not need rebooting so often.

  xorg was used because it seems to be the xorg mouse drivers that are
  in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Feb 25 18:15:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too 

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15
gtk_main_get_window_group function return different results for
gtk_grab_add and gtk_grab_remove, but widget address was same in both
functions:

  if (GTK_IS_WINDOW (toplevel))
return gtk_window_get_group (GTK_WINDOW (toplevel));
  else
return gtk_window_get_group (NULL);

On gtk_grab_add window group is 0x55b0b160 for widget 0x55e50780:
Thread 1 "mate-terminal" hit Breakpoint 3, gtk_main_get_window_group 
(widget=0x55e50780) at ././gtk/gtkmain.c:2
025
2025  if (GTK_IS_WINDOW (toplevel))
$2044 (widget) = 0x55e50780
$2045 (toplevel) = 0x55e50780
$2046 (*widget) = {parent_instance = {g_type_instance = {g_class = 
0x55e5e800}, ref_count = 1, qdata = 0x2}, priv = 0x555
555e50690}
$2047 (*widget.priv) = {..., window = 0x0, registered_windows = 0x0, parent = 
0x0, event_contr
ollers = 0x0, accessible = 0x0}
#0  gtk_main_get_window_group (widget=0x55e50780) at ././gtk/gtkmain.c:2025
#1  0x771f3bb3 in gtk_grab_add (widget=0x55e50780) at 
././gtk/gtkmain.c:2231
#2  0x770ac1d1 in gtk_cell_renderer_accel_start_editing 
(cell=0x55845270, event=0x55d416f0, widget=
0x55e183f0, path=0x55e57720 "2:0", background_area=0x7fffc2e0, 
cell_area=0x7fffc2e0, flags=(unknown
: 0)) at ././gtk/gtkcellrendereraccel.c:497
#3  0x770a92dd in gtk_cell_renderer_start_editing (cell=0x55845270, 
event=0x55d416f0, widget=0x
55e183f0, path=0x55e57720 "2:0", background_area=0x7fffc2e0, 
cell_area=0x7fffc2e0, flags=(unknown: 0)) 
at ././gtk/gtkcellrenderer.c:921
#4  0x7709d47e in gtk_cell_area_activate_cell (area=0x55e0d140, 
widget=0x55e183f0, renderer=0x55845270, event=0x55d416f0, 
cell_area=0x7fffc380, flags=(unknown: 0)) at ././gtk/gtkcellarea.c:3432
#5  0x77096407 in gtk_cell_area_real_event (area=0x55e0d140, 
context=0x55e26850, widget=0x55e183f0, event=0x55d416f0, 
cell_area=0x7fffc570, flags=(unknown: 0)) at ././gtk/gtkcellarea.c:1101


At time of gtk_grab_remove, when event is delivered to widget 0x55e50780 
from gtk_main_do_event, its toplevel was 0x55ddb0d0
Thread 1 "mate-terminal" hit Breakpoint 3, gtk_main_get_window_group 
(widget=0x55e50780) at ././gtk/gtkmain.c:2025
2025  if (GTK_IS_WINDOW (toplevel))
$2092 (widget) = 0x55e50780
$2093 (toplevel) = 0x55ddb0d0
$2094 (*widget) = {parent_instance = {g_type_instance = {g_class = 
0x55e5e800}, ref_count = 7, qdata = 0x55ecf180}, priv = 0x55e50690}
$2095 (*widget.priv) = {, window = 0x55e507e0, registered_windows = 
0x5595
7d00, parent = 0x55e183f0, event_controllers = 0x0, accessible = 
0x55e1d320}
#0  gtk_main_get_window_group (widget=0x55e50780) at ././gtk/gtkmain.c:2025
#1  0x771f3d8c in gtk_grab_remove (widget=0x55e50780) at 
././gtk/gtkmain.c:2286
#2  0x770ac56b in gtk_cell_editable_event_box_key_press_event 
(widget=0x55e50780, event=0x55e473c0)
 at ././gtk/gtkcellrendereraccel.c:645


Parent of the widget was changed by gtk_tree_view_multipress_gesture_pressed -> 
.. -> gtk_cell_area_activate_cell -> gtk_cell_area_add_editable -> ..signal.. 
-> gtk_tree_view_column_add_editable_callback -> _gtk_tree_view_add_editable -> 
gtk_tree_view_put -> gtk_widget_set_parent

So, gtk_cell_area_activate_cell of gtk+3 (3.22.7) has incorrect order of 
actions which broke gtk_grab_add / gtk_grab_remove pair
https://github.com/GNOME/gtk/blob/6cc08d60efeb02afc0d67982c3dc205dfd16d7cd/gtk/gtkcellarea.c#L3388

3428   gtk_cell_renderer_start_editing (renderer,
...
3444   gtk_cell_area_add_editable (area, priv->focus_cell, editable_widget, 
cell_area);

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  

[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

2017-02-25 Thread yzp15
** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  New

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  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/gnome-terminal/+bug/1667227/+subscriptions

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


[Touch-packages] [Bug 1333228] Re: [sdk] Clicking on checkbox label should toggle the checkbox

2017-02-25 Thread Adnane Belmadiaf
@mpt can you please share the specification ?

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

Title:
  [sdk] Clicking on checkbox label should toggle the checkbox

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  For instance, take the "Connec to " pop-up dialog. When I touch 
the:
  [   ] Show password
  checkbox *label*, I'd expect the checkbox to toggle. I shouldn't need to have 
to exactly touch the checkbox box, which is a small area.

   (currently Canonical-only link): “As with a
  switch or radio button, when a checkbox has a label, it should be
  clickable/tappable together with the checkbox itself.”

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

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


[Touch-packages] [Bug 1333228] Re: [sdk] Clicking on checkbox label should toggle the checkbox

2017-02-25 Thread Adnane Belmadiaf
** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Adnane Belmadiaf (daker)

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

Title:
  [sdk] Clicking on checkbox label should toggle the checkbox

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  For instance, take the "Connec to " pop-up dialog. When I touch 
the:
  [   ] Show password
  checkbox *label*, I'd expect the checkbox to toggle. I shouldn't need to have 
to exactly touch the checkbox box, which is a small area.

   (currently Canonical-only link): “As with a
  switch or radio button, when a checkbox has a label, it should be
  clickable/tappable together with the checkbox itself.”

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

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


[Touch-packages] [Bug 1333228] Re: [sdk] Clicking on checkbox label should toggle the checkbox

2017-02-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~daker/ubuntu-ui-toolkit/fix.1333228

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

Title:
  [sdk] Clicking on checkbox label should toggle the checkbox

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  For instance, take the "Connec to " pop-up dialog. When I touch 
the:
  [   ] Show password
  checkbox *label*, I'd expect the checkbox to toggle. I shouldn't need to have 
to exactly touch the checkbox box, which is a small area.

   (currently Canonical-only link): “As with a
  switch or radio button, when a checkbox has a label, it should be
  clickable/tappable together with the checkbox itself.”

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

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


Re: [Touch-packages] [Bug 1667751] Re: Confined binaries running in namespaces unable to read their executable

2017-02-25 Thread Simon Déziel
Thanks Seth. A general solution covering most cases would be great as
tweaking existing profiles would involve many SRUs and inevitably, new
profiles not working inside containers would show up.

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

Title:
  Confined binaries running in namespaces unable to read their
  executable

Status in apparmor package in Ubuntu:
  New

Bug description:
  It seems that binaries confined by Apparmor attempt to read their own
  executable when running in a namespace/container. This breaks many
  profiles that are working perfectly well outside of namespaces.


  
  Original description:

  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even
  the kernel so please re-assign if needed.

  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:

  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536

  This prevents rsyslog from starting in the said container:

  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
     Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
   Docs: man:rsyslogd(8)
     http://www.rsyslog.com/doc/
    Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
   Main PID: 232 (code=exited, status=127)

  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed 
state.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
  Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.

  I don't know why rsyslog wants to read its own binary but it seems to
  really want to.

  Both the host and the guest are up to date Xenials. Please not that
  the host runs the kernel from -proposed.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
  linux-image-4.4.0-65-generic:
    Installed: 4.4.0-65.86
    Candidate: 4.4.0-65.86
    Version table:
   *** 4.4.0-65.86 100
  100 /var/lib/dpkg/status
  apparmor:
    Installed: 2.10.95-0ubuntu2.5
    Candidate: 2.10.95-0ubuntu2.5
    Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 12:17:34 2017
  InstallationDate: Installed on 2016-12-19 (66 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog: Feb 24 11:04:10 jupiter dbus[1812]: [system] AppArmor D-Bus mediation 
is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667943] [NEW] HP Pavilion x2, kernel 4.10, PCI/internal sound card not detected

2017-02-25 Thread Erkan ÜNLÜTÜRK
Public bug reported:

The problem continues !!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sat Feb 25 18:59:11 2017
InstallationDate: Installed on 2017-02-17 (8 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 813E
dmi.board.vendor: HP
dmi.board.version: 34.11
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd08/29/2016:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.11:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion x2 Detachable
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug xenial

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

Title:
  HP Pavilion x2, kernel 4.10, PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The problem continues !!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.10.0-041000-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Feb 25 18:59:11 2017
  InstallationDate: Installed on 2017-02-17 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd08/29/2016:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.11:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


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

2017-02-25 Thread Apport retracing service
*** This bug is a duplicate of bug 1666193 ***
https://bugs.launchpad.net/bugs/1666193

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  just logging on zesty. the latest patch level. The latest future
  kernel (linux-
  image-4.10.0-041000-generic_4.10.0-041000.201702191831_amd64).

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 24 22:12:06 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2017-02-19 (5 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170218)
  MachineType: Dell Inc. Inspiron 5548
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic.efi.signed 
root=UUID=d3325c4b-a547-4eeb-9118-d15583cfeed2 ro
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed () from /lib/systemd/libsystemd-shared-232.so
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-232.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-232.so
  Title: systemd-resolved crashed with SIGABRT in log_assert_failed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/12/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 03P3GD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn03P3GD:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.name: Inspiron 5548
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

2017-02-25 Thread Edward Gibbs
Well, it was not a firmware update that fixed it.  I'm on Qubes 4.2
right now and it still has the problem,  Qubes is using Xfce 4.12 as
it's desktop manager, which I believe is Ubuntu based.  Some update to
Ubuntu must have fixed the problem and it hasn't been rolled into the
Xfce version Qubes is using.

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 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: Mon Feb 13 18:15:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2017-01-07 (37 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001SUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Feb 13 18:15:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1667929] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-02-25 Thread Benno Schulenberg
Please attach the file /var/lib/dpkg/alternatives/pico .

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

Title:
  package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in nano package in Ubuntu:
  New

Bug description:
  it crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Feb 25 14:28:00 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-25  14:01:31
   Commandline: aptdaemon role='role-commit-packages' sender=':1.34'
   Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), 
linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), 
xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), 
linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 
(4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 
2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), 
linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68)
  DuplicateSignature:
   package:nano:2.5.3-2ubuntu2
   Setting up nano (2.5.3-2ubuntu2) ...
   update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid 
status
   dpkg: error processing package nano (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nano
  Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667928] Re: app drawer, Select All Paste menu (wrong z ordering) it is above the mouse pointer

2017-02-25 Thread dinamic
** Summary changed:

- app drawer, Select All  Paste menu (wrong z ordering) it is about the mouse 
pointer
+ app drawer, Select All  Paste menu (wrong z ordering) it is above the mouse 
pointer

** Description changed:

  ubuntu 17.04 unit8
- app drawer, Select All  Paste menu (wrong z ordering) it is about the mouse 
pointer
+ app drawer, Select All  Paste menu (wrong z ordering) it is above the mouse 
pointer
  
  open the app drawer, right click in the Search, move the mouse pointer
  to the opened menu
  
  see attached screenshot

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

Title:
  app drawer, Select All  Paste menu (wrong z ordering) it is above the
  mouse pointer

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unit8
  app drawer, Select All  Paste menu (wrong z ordering) it is above the mouse 
pointer

  open the app drawer, right click in the Search, move the mouse pointer
  to the opened menu

  see attached screenshot

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

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


[Touch-packages] [Bug 1667931] [NEW] some gtk apps are missing toolbar icons, see transmission, solitaire etc

2017-02-25 Thread dinamic
Public bug reported:

ubuntu 17.04 unity8

some gtk apps are missing toolbar icons, see transmission, solitaire etc

see attached screenshot

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20170225_154112448.png"
   
https://bugs.launchpad.net/bugs/1667931/+attachment/4826531/+files/screenshot20170225_154112448.png

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

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

Title:
  some gtk apps are missing toolbar icons, see transmission, solitaire
  etc

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  some gtk apps are missing toolbar icons, see transmission, solitaire
  etc

  see attached screenshot

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

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


[Touch-packages] [Bug 1667929] Re: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-02-25 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in nano package in Ubuntu:
  New

Bug description:
  it crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Feb 25 14:28:00 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-25  14:01:31
   Commandline: aptdaemon role='role-commit-packages' sender=':1.34'
   Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), 
linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), 
xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), 
linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 
(4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 
2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), 
linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68)
  DuplicateSignature:
   package:nano:2.5.3-2ubuntu2
   Setting up nano (2.5.3-2ubuntu2) ...
   update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid 
status
   dpkg: error processing package nano (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nano
  Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667929] [NEW] package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-02-25 Thread Jerome Carlier
Public bug reported:

it crashed during software update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nano 2.5.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat Feb 25 14:28:00 2017
DpkgHistoryLog:
 Start-Date: 2017-02-25  14:01:31
 Commandline: aptdaemon role='role-commit-packages' sender=':1.34'
 Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), 
linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic)
 Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), 
xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), 
linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 
(4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 
2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), 
linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68)
DuplicateSignature:
 package:nano:2.5.3-2ubuntu2
 Setting up nano (2.5.3-2ubuntu2) ...
 update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid 
status
 dpkg: error processing package nano (--configure):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: nano
Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in nano package in Ubuntu:
  New

Bug description:
  it crashed during software update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Feb 25 14:28:00 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-25  14:01:31
   Commandline: aptdaemon role='role-commit-packages' sender=':1.34'
   Install: linux-headers-4.4.0-64:amd64 (4.4.0-64.85, automatic), 
linux-image-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-image-extra-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic), 
linux-headers-4.4.0-64-generic:amd64 (4.4.0-64.85, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), 
xserver-xorg-video-amdgpu:amd64 (1.1.0-1, 1.1.2-0ubuntu0.16.04.1), 
linux-image-generic:amd64 (4.4.0.62.65, 4.4.0.64.68), tcpdump:amd64 
(4.7.4-1ubuntu1, 4.9.0-1ubuntu1~ubuntu16.04.1), nano:amd64 (2.5.3-2ubuntu1, 
2.5.3-2ubuntu2), gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.1, 1.8.3-1ubuntu0.2), 
linux-generic:amd64 (4.4.0.62.65, 4.4.0.64.68)
  DuplicateSignature:
   package:nano:2.5.3-2ubuntu2
   Setting up nano (2.5.3-2ubuntu2) ...
   update-alternatives: error: /var/lib/dpkg/alternatives/pico corrupt: invalid 
status
   dpkg: error processing package nano (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nano
  Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667930] [NEW] package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

2017-02-25 Thread Nikita Savchenko
Public bug reported:

the error occurred when running apt dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Feb 25 17:33:29 2017
ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
InstallationDate: Installed on 2016-11-22 (94 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс
  новый сценарий pre-removal возвратил код ошибки 1

Status in apport package in Ubuntu:
  New

Bug description:
  the error occurred when running apt dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Feb 25 17:33:29 2017
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2016-11-22 (94 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

2017-02-25 Thread Mathew Hodson
** Changed in: gcc-5 (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: gcc-6 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gcc-5 (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  New
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  New

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

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

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


[Touch-packages] [Bug 1667928] Re: app drawer, Select All Paste menu (wrong z ordering) it is about the mouse pointer

2017-02-25 Thread dinamic
interesting, the menu is not in the screenshot, but it was there (on the
screen), the screenshot just doesn't see the menu, probably a layer
above what screenshots cares

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

Title:
  app drawer, Select All  Paste menu (wrong z ordering) it is about the
  mouse pointer

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unit8
  app drawer, Select All  Paste menu (wrong z ordering) it is about the mouse 
pointer

  open the app drawer, right click in the Search, move the mouse pointer
  to the opened menu

  see attached screenshot

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

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


[Touch-packages] [Bug 1667928] [NEW] app drawer, Select All Paste menu (wrong z ordering) it is about the mouse pointer

2017-02-25 Thread dinamic
Public bug reported:

ubuntu 17.04 unit8
app drawer, Select All  Paste menu (wrong z ordering) it is about the mouse 
pointer

open the app drawer, right click in the Search, move the mouse pointer
to the opened menu

see attached screenshot

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20170225_151538009.png"
   
https://bugs.launchpad.net/bugs/1667928/+attachment/4826515/+files/screenshot20170225_151538009.png

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

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

Title:
  app drawer, Select All  Paste menu (wrong z ordering) it is about the
  mouse pointer

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unit8
  app drawer, Select All  Paste menu (wrong z ordering) it is about the mouse 
pointer

  open the app drawer, right click in the Search, move the mouse pointer
  to the opened menu

  see attached screenshot

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

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


[Touch-packages] [Bug 1664397] Re: Mouse trails and distorted cursor on 2nd monitor

2017-02-25 Thread Edward Gibbs
As requested I downloaded the latest build and ran it from USB.  After
selecting hybrid graphics in BIOS I booted up and was delighted to see
no mouse trails on the 2nd monitor!

I then rebooted back into 16.04 leaving hybrid graphics selected - no
mouse trails!

I think there was an Intel firmware update a week or two ago that I got
on Windows, maybe it updated the Intel graphics firmware?  Whatever
happened I am happy to say that I cannot now duplicate the problem and
hybrid graphics seems to be working properly in both 16.04 and 17.10.

Thanks for your help.

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

Title:
  Mouse trails and distorted cursor on 2nd monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM

  2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid
  Graphics the cursor on the second display is distorted and leaves
  mouse trails that persist for several seconds.  Switching to Nvidia
  graphics cures but Nvidia has other problems (built in display is dim
  and brightness cannot be adjusted).  Interestingly, just opening
  Display settings also cures the problem for as long as the Display
  Setting dialog is open.  Under Windows (10 Pro) Hybrid Graphics does
  not exhibit this problem.

  Ubuntu release is 16.04.2 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.9.0-040900-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 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: Mon Feb 13 18:15:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2017-01-07 (37 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001SUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic 
root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN001SUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Feb 13 18:15:02 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1665286] Re: [unity8][qt] tiled app opens a transparent window "object types editor" when launched

2017-02-25 Thread dinamic
thanks :D nope, it's still the same with silo 2481

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

Title:
  [unity8][qt] tiled app opens a transparent window "object types
  editor" when launched

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  install tiled, apt install tiled
  launch tiled, you'll see a transparent window opened beneath the main window 
called "Object Types Editor"

  see attached screenshot

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

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


[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

2017-02-25 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff for xenial" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1030471] Re: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte

2017-02-25 Thread Gaétan QUENTIN
NO.

I don't think this is the root problem. There is a file  read by
software-property* somewhere which is not  utf-8 compliant. This problem
came after a long working fine system  with 16.04. locale didn't
changed.

Could it be possible to output in the softawre-properties-tgk* code  ,
the read failure "file name"   which is in failure ? Telling it in the
output could be helpfull to track problem.

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

Title:
  software-properties-gtk crashed with UnicodeDecodeError in record():
  'utf-8' codec can't decode byte 0x92 in position 1017: invalid start
  byte

Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  clicked 'settings' in software updater (xubuntu)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: software-properties-gtk 0.91
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Sun Jul 29 10:26:40 2012
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with UnicodeDecodeError in record(): 
'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

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

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


[Touch-packages] [Bug 1388278] Re: WiFi randomly disconnects and won't connect again

2017-02-25 Thread Andrew McCoull
I seem to be getting this on Mint 18 (Cinnamon), Dell Vostro 1700 built-in WiFi 
card. Haven't tried the logout/login test.
Are my syslog outputs of interest here??

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

Title:
  WiFi randomly disconnects and won't connect again

Status in Broadcom 802.11 Linux STA driver:
  New
Status in Linux:
  New
Status in Linux Mint:
  Confirmed
Status in LinuxMint Control Center:
  Confirmed
Status in Network Manager Applet:
  Expired
Status in Additional Linux Wireless Drivers:
  Confirmed
Status in Wireless Tools:
  New
Status in wireless-tools package in Ubuntu:
  Confirmed

Bug description:
  Something odd that I have only seen in Ubuntu, Debian, and derivatives
  thereof affects something that most of us use every day, and can be a
  real hassle to beginners from what I've noticed: Many USB WiFi drivers
  will connect to an access point like usual and after long periods of
  inactivity on the network combined with user inactivity on the PC
  alone is when this problem appears to arise: The WiFi disconnects and
  does not connect again to the same hotspot using the same USB WiFi
  dongle unless the computer is restarted or reset, and a lot of the
  time, that doesn't immediately stop this error and even if so, the
  computer will disconnect yet again not too long from then.

  And why does this happen? It puzzles me. Maybe it's the USB chipset
  inside the WiFi dongle, or maybe it's a communication error between
  the Linux kernel and the automated firewall systems integrated in most
  routers and base stations today, it's hard to say. What I know is that
  this doesn't just happen on my computer, testing done by myself on
  several other computers in different locations using different WiFi
  hardware on Ubuntu, Debian, Linux Mint, or derivatives thereof gets
  the exact same result as I am experiencing now.

  I have gone digging through Debian, Ubuntu, and Linux Mint forums to
  try and find the "cure" patch for my computer or router and the answer
  as to why this is happening, and the best answer I could find is that
  within my system's WiFi Settings, I need to set the BSSID of the
  hotspot I am current using as the MAC address of the router which that
  hotspot is transmitting.

  Upon setting my BSSID to a clone of the Router's MAC address followed
  by a system restart, I noticed instant improvement when it comes to
  connection reliability, speed, and time to connect, yet after days of
  having that MAC as the BSSID, things went back to the usual chaos of
  an unreliable connection that no other device within the household has
  encountered, not even Android telephones and tablets that use much of
  the same underlying Linux code. I performed restarts, updates, more
  updates, resets, and even more derivatives of Debian or Ubuntu and
  this is still more of an issue than ever.

  Via further digging and through a process of trial-and-error, I
  enabled the "IPv4 is required for this connection" check box along
  with changing the BSSID to a clone of the router's MAC address in
  hopes it was a compatibility issue with the "newer" IPv6 Internet
  Protocol architecture in an attempt to basically 'force' the machine
  to get that digital handshake with the router in a more 'legacy' mode
  with IPv4, at least to get some connection. That worked for a bit as
  well, but didn't hold up just like before.

  I am now sitting here at my computer, still experiencing this issue on
  and off, currently having the issue stabilized and stalled at the
  moment with the "IPv4 is required for this connection" check box on,
  NO BSSID set, NO cloned MAC address, and NO "Restrict to Device"
  settings opted-in, hoping this time around this combination of
  settings will work, but it's a game of trial-and-error for me at this
  point now, like mentioned before.

  Has anyone else experienced such terrible connectivity issues only in
  Debian-based distributions recently? I have been using Linux for ages
  now and I feel as if this issue is now just arising within the past
  year, 2014.

  A HardInfo report generated from my computer is attached to this bug
  report. I hope we can figure out a solution soon to get pushed to all
  Debian and Debian-like distros soon! Nobody wants a bad connection.


  Current OS: Linux Mint 17 "Qiana"
  Kernel: Linux 3.13.0-24-generic (x86_64)
  Processor: AMD Phenom II X4 (850)
  RAM: 8GB DDR3

  IWLIST OUTPUT:
  jeb@MINT-PARTITION:~ > sudo iwlist wlan0 scan
  [sudo] password for jeb: 
  wlan0 Scan completed :
Cell 01 - Address: F8:7B:8C:06:57:8D
  Channel:6
  Frequency:2.437 GHz (Channel 6)
  Quality=60/70  Signal level=-50 dBm  
  Encryption key:on
  ESSID:"Belkin-EXT"
  

[Touch-packages] [Bug 1030471] Re: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte

2017-02-25 Thread Julian Andres Klode
Locale wrongly configured. Needs to be UTF-8.

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  software-properties-gtk crashed with UnicodeDecodeError in record():
  'utf-8' codec can't decode byte 0x92 in position 1017: invalid start
  byte

Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  clicked 'settings' in software updater (xubuntu)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: software-properties-gtk 0.91
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Sun Jul 29 10:26:40 2012
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with UnicodeDecodeError in record(): 
'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

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

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


[Touch-packages] [Bug 1667911] [NEW] upgrade to 15 to 16

2017-02-25 Thread JS
Public bug reported:

?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Feb 25 12:00:29 2017
DistUpgraded: 2017-02-25 11:49:54,902 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
InstallationDate: Installed on 2016-12-04 (82 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. XPS13 9333
ProcEnviron:
 LANGUAGE=fr_FR
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-02-25 (0 days ago)
dmi.bios.date: 03/27/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0D13CR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: XPS13 9333
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.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Feb 25 11:55:03 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4933 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.2

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

Title:
  upgrade to 15 to 16

Status in xorg package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Feb 25 12:00:29 2017
  DistUpgraded: 2017-02-25 11:49:54,902 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2016-12-04 (82 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS13 9333
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-02-25 (0 days ago)
  dmi.bios.date: 03/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-25 Thread Andreas Lindhé
** Bug watch added: github.com/nextcloud/nextcloud-snap/issues #178
   https://github.com/nextcloud/nextcloud-snap/issues/178

** Also affects: nextcloud-snap via
   https://github.com/nextcloud/nextcloud-snap/issues/178
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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


[Touch-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-02-25 Thread Starbeamrainbowlabs
*** This bug is a duplicate of bug 1615871 ***
https://bugs.launchpad.net/bugs/1615871

I've discovered that I'm affected by this bug, but *only* when I've got
2 chrome windows open on different desktops (I've got a 2x2 grid of
desktops) on Ubuntu 16.10 - it wasn't doing this on Ubuntu 16.04.

How can this be a duplicate of a webkit bug when chrome doesn't even use
webkit though?

uname -a: Linux Riikaan 4.8.0-39-generic #42-Ubuntu SMP Mon Feb 20
11:47:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Kabylake GT2  (0x5916)
Version: 12.0.6
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Kabylake GT2 
OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.0.6
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 12.0.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10


More information available on request.

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

2017-02-25 Thread Chris Glass
This debdiff should fix the problem.

** Patch added: "debdiff for xenial"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1606600/+attachment/4826417/+files/unattended-debdiff.diff

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1606600] Re: dpkg-reconfigure unattended-upgrades results in update-rc.d warning that start and stop actions are no longer supported

2017-02-25 Thread Chris Glass
I *think* the root of the issue is that the assumption in debian/rules

# we do not want to run the init script in the postinst/prerm, its
#  really only useful on shutdown, see Debian bug #645919
dh_installinit $@ --no-start -- stop 10 0 6 .

is wrong.

It is not only useful on shutdown but also when dpkg-reconfigure is
invoked.

As a strawman fix, I've uploaded a fixed (xenial) package to
https://launchpad.net/~tribaal/+archive/ubuntu/unattended-upgrades

It seems to fix the issue in my limited testing: running "dpkg-
reconfigure -fnoninteractive unattended-upgrades" does apply changes
passed by debconf-set-selections.

I'll attach a debdiff to this bug as well, and open a pull request
upsteam.

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

Title:
  dpkg-reconfigure unattended-upgrades results in update-rc.d warning
  that start and stop actions are no longer supported

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to script a change to the automatic updating of servers,
  and tried the following:

  echo "debconf unattended-upgrades/enable_auto_updates boolean false" | 
debconf-set-selections -
  dpkg-reconfigure -fnoninteractive unattended-upgrades

  The result, however, is a warning message:

  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

  At this point, the change I tried to make seems to be lost. To show
  this in an expanded sequence:

  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: true
  root@brennan:/home/ubuntu# echo "debconf 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
-
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
  * unattended-upgrades/enable_auto_updates: false
  root@brennan:/home/ubuntu# dpkg-reconfigure -fnoninteractive 
unattended-upgrades
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  root@brennan:/home/ubuntu# debconf-show unattended-upgrades
  * unattended-upgrades/enable_auto_updates: true
  * unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

  If I omit the "-fnoninteractive" option to dpkg-reconfigure, I still
  get the warning message, but the change IS accepted and takes effect.
  Of course, this isn't useful in a script that should be run non-
  interactively. I've tried the equivalent commands to reconfigure other
  packages, and they work without error message, so I believe the
  problem is with unattended-upgrades, not with debconf/dpkg-
  reconfigure.

  This problem affects Ubuntu 16.04.1 (and probably 16.04 GA, but I've
  not tested it). It works as expected with Ubuntu 14.04. (That version,
  of course, defeaults to "false" for the unattended-
  upgrades/enable_auto_updates value. I've tested both with the default
  "false" value and after changing it to "true," with successful runs
  both times.)

  Version information, as requested:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90
Version table:
   *** 0.90 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy debconf
  debconf:
Installed: 1.5.58ubuntu1
Candidate: 1.5.58ubuntu1
Version table:
   *** 1.5.58ubuntu1 500
  500 http://192.168.1.2//ubuntu xenial/main amd64 Packages
  500 http://192.168.1.2//ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1570813] Re: Executing "systemctl is-enabled tmp.mount ; echo $?" returns 0 on an error

2017-02-25 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1545707 ***
https://bugs.launchpad.net/bugs/1545707

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

Title:
  Executing "systemctl is-enabled tmp.mount ; echo $?" returns 0 on an
  error

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-4ubuntu4 and figured out
  by this report (
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707 ) if
  executing "systemctl is-enabled tmp.mount ; echo $?" fails 0 is
  returned as shown in this example:

  root@ubuntu:~# systemctl is-enabled tmp.mount ; echo $?
  Failed to get unit file state for tmp.mount: No such file or directory
  0

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

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


[Touch-packages] [Bug 1030471] Re: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte

2017-02-25 Thread Gaétan QUENTIN
ubuntu 16.04:

sudo software-properties-gtk -m -d
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
 PyGIWarning: Gdk was imported without specifying a version first. Use 
gi.require_version('Gdk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import GObject, Gdk, Gtk, Gio, GLib
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
 PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import GObject, Gdk, Gtk, Gio, GLib
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 101, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 172, in __init__
self.show_keys()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 867, in show_keys
for key in self.apt_key.list():
  File "/usr/lib/python3/dist-packages/softwareproperties/AptAuth.py", line 78, 
in list
for line in p:
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xdf in position 3182: 
invalid continuation byte

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

Title:
  software-properties-gtk crashed with UnicodeDecodeError in record():
  'utf-8' codec can't decode byte 0x92 in position 1017: invalid start
  byte

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  clicked 'settings' in software updater (xubuntu)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: software-properties-gtk 0.91
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Sun Jul 29 10:26:40 2012
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with UnicodeDecodeError in record(): 
'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

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

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


[Touch-packages] [Bug 1030471] Re: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte

2017-02-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  software-properties-gtk crashed with UnicodeDecodeError in record():
  'utf-8' codec can't decode byte 0x92 in position 1017: invalid start
  byte

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  clicked 'settings' in software updater (xubuntu)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: software-properties-gtk 0.91
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu6
  Architecture: i386
  Date: Sun Jul 29 10:26:40 2012
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with UnicodeDecodeError in record(): 
'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

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

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


[Touch-packages] [Bug 1617005] Re: [MIR] zmqpp

2017-02-25 Thread Seth Arnold
My apologies for letting this slip.

Considering this came from the zmq project and wouldn't have been
surprising if it had been included in the zeromq3 source package, I
decided to just give this very quick spot-checks and review the
packaging as a sanity check.

Security team ACK for promoting zmqpp to main.

Thanks

** Changed in: zmqpp (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] zmqpp

Status in zmqpp package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe.

  [Rationale]
   * This package is required by unity-scopes-api.

  [Security]
   * No known security issues at this time, it has been in active use on our 
touch devices since a very long time already.

  [Quality assurance]
   * This package comes with a set of unit tests that are all being run during 
build-time.

  [Dependencies]
   Most dependencies are already in main, with only a small nitpick:
   * libboost-test-dev is in universe, but its source boost-defaults is already 
in main.
   * zeromq3 has a MIR filled as well 
(https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1597439)

  [Maintenance]
   * This package is used by Canonical upstream projects so the packaging is 
maintained by Canonical. The upstream code is actively maintained and developed 
by the zeromq team.

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

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