[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

2016-10-25 Thread Doctor Rover
** Tags added: yakkety

** Description changed:

  Just installed 15.04 fresh from the latest ISO (beta2).
  
  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to
  have regressed in functionality.
  
  In 14.10, I was able to set the output profile either to a2dp or hsp/hfp
  (telephony duplex).
  
  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.
  
  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006
  
- The bug is still present in 16.04 LTS.
+ The bug is still present in 16.04 LTS and 16.10.

** Summary changed:

- [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
+ [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 
16.10 yakkety

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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


[Touch-packages] [Bug 1636499] Re: Some Right Corner Drop-Down Menu Items not working after Proposed Update

2016-10-25 Thread Paul White
** Tags added: zesty

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

Title:
  Some Right Corner Drop-Down Menu Items not working after Proposed
  Update

Status in software-properties package in Ubuntu:
  New

Bug description:
  When I left click on the Drop-Down Menu(name Unknown, because It does not 
Display on my Insignia T.V. Monitor Correctly-Too big).
  If I left mouse click on "About this Computer", nothing seems to happen.
  Same thing if I click on "Ubuntu Help..."
  Or "System Settings..."
  nothing seems to happen.
  If I click below "System Settings", they seem to work.

  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ uname -a
  Linux free-zesty 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  miked@free-zesty:~$

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

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


[Touch-packages] [Bug 1636617] [NEW] lxc set device root size fails silently when out of space

2016-10-25 Thread Brian Morton
Public bug reported:

On 16.04.1, use lxd init with default responses (zfs, loopback, 10G).
Create container with lxc launch. Attempt to resize container root to
20G (larger than loopback file).

lxc set device root size 20G reports no error, but the container still
has a 1.1G root as shown by lxc exec  df -h

It would be ideal to have lxc throw an error of some kind when it does
not have enough space to complete the operation.

For documentation purposes, the fix is to grow the zfs.img file with
truncate, turn on ZFS autoexpand, then perform a zpool online resize.
After adding enough loopback device storage, the set command behaves
identically but achieves the intended result.

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

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

Title:
  lxc set device root size fails silently when out of space

Status in lxc package in Ubuntu:
  New

Bug description:
  On 16.04.1, use lxd init with default responses (zfs, loopback, 10G).
  Create container with lxc launch. Attempt to resize container root to
  20G (larger than loopback file).

  lxc set device root size 20G reports no error, but the container still
  has a 1.1G root as shown by lxc exec  df -h

  It would be ideal to have lxc throw an error of some kind when it does
  not have enough space to complete the operation.

  For documentation purposes, the fix is to grow the zfs.img file with
  truncate, turn on ZFS autoexpand, then perform a zpool online resize.
  After adding enough loopback device storage, the set command behaves
  identically but achieves the intended result.

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

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


[Touch-packages] [Bug 1636617] Re: lxc set device root size fails silently when out of space

2016-10-25 Thread Brian Morton
Makes sense to me, thanks for looking into that!

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

Title:
  lxc set device root size fails silently when out of space

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  On 16.04.1, use lxd init with default responses (zfs, loopback, 10G).
  Create container with lxc launch. Attempt to resize container root to
  20G (larger than loopback file).

  lxc set device root size 20G reports no error, but the container still
  has a 1.1G root as shown by lxc exec  df -h

  It would be ideal to have lxc throw an error of some kind when it does
  not have enough space to complete the operation.

  For documentation purposes, the fix is to grow the zfs.img file with
  truncate, turn on ZFS autoexpand, then perform a zpool online resize.
  After adding enough loopback device storage, the set command behaves
  identically but achieves the intended result.

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

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


[Touch-packages] [Bug 1636617] Re: lxc set device root size fails silently when out of space

2016-10-25 Thread Stéphane Graber
root@castiana:~# zfs set quota=2EB encrypted/lxd/containers/zesty
root@castiana:~# echo $?
0

root@castiana:~# zfs get quota encrypted/lxd/containers/zesty
NAMEPROPERTY  VALUE  SOURCE
encrypted/lxd/containers/zesty  quota 2E local

So as can be seen, ZFS allows settings quotas that far exceed the pool
size and does so without returning an error. There is therefore no way
for LXD to return an error since the operation succeeded.

My guess is that ZFS will always shows your volume total size to be the
smallest of its quota or any of the quota in the tree, including the
tree root (the pool itself).

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

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

Title:
  lxc set device root size fails silently when out of space

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  On 16.04.1, use lxd init with default responses (zfs, loopback, 10G).
  Create container with lxc launch. Attempt to resize container root to
  20G (larger than loopback file).

  lxc set device root size 20G reports no error, but the container still
  has a 1.1G root as shown by lxc exec  df -h

  It would be ideal to have lxc throw an error of some kind when it does
  not have enough space to complete the operation.

  For documentation purposes, the fix is to grow the zfs.img file with
  truncate, turn on ZFS autoexpand, then perform a zpool online resize.
  After adding enough loopback device storage, the set command behaves
  identically but achieves the intended result.

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

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


[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2016-10-25 Thread Matt Schulte
For completeness, I upgraded to 16.04.1, the issue is still present.

I upgraded to the latest xenial-updates packages as of 10/24/16 and the
issue is still present.

I then re-installed with 16.10 and the issue is still present.  I guess
I'll open a new bug for 16.10 and refer back to this one.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

"Reached target Shutdown"

  followed by

"systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

"connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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


[Touch-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

2016-10-25 Thread piratemurray
Confirmed Gedit and Calc display this problem after upgrading 16.04 to
16.10. I am using 367.57 from nvidia-367 as my display driver if that is
useful information?

** Attachment added: "transparent-window-bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+attachment/4767183/+files/transparent-window-bug.png

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1599212] Re: Redundant "+" icon to create new message

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

** Changed in: messaging-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Redundant "+" icon to create new message

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Open Messaging app. Observe there is a "+" icon in header. Pressing this icon 
opens "new message" with empty "To" and "Write a message" fields. 
  The same can be opened from the bottom edge navigation.

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

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


[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2016-10-25 Thread Jamie Strandboge
Just for clarity, I did both the main test case and the extended test
case for im-config. I also noticed that when installing im-config, it
correctly required the updated 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/1580463

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in im-config source package in Xenial:
  Fix Committed
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly 

[Touch-packages] [Bug 1636631] Re: DISC SPACE NONE LEFT

2016-10-25 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

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

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

Title:
  DISC SPACE NONE LEFT

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  DISC NOT ENOUGH SPACE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Tue Oct 25 17:40:32 2016
  DistUpgraded: 2016-10-13 13:22:55,920 DEBUG running apport_crash()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
  InstallationDate: Installed on 2016-09-13 (42 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (12 days ago)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite C655
  dmi.product.version: PSC08U-03C01K
  dmi.sys.vendor: TOSHIBA
  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-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  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 1:1.0.12-2
  xserver.bootTime: Tue Oct 25 14:26:13 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1636631] [NEW] DISC SPACE NONE LEFT

2016-10-25 Thread jonathan
Public bug reported:

DISC NOT ENOUGH SPACE

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
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: Tue Oct 25 17:40:32 2016
DistUpgraded: 2016-10-13 13:22:55,920 DEBUG running apport_crash()
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
   Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
InstallationDate: Installed on 2016-09-13 (42 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA Satellite C655
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (12 days ago)
dmi.bios.date: 07/07/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.70
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite C655
dmi.product.version: PSC08U-03C01K
dmi.sys.vendor: TOSHIBA
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-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
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 1:1.0.12-2
xserver.bootTime: Tue Oct 25 14:26:13 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu yakkety

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

Title:
  DISC SPACE NONE LEFT

Status in xorg package in Ubuntu:
  New

Bug description:
  DISC NOT ENOUGH SPACE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Tue Oct 25 17:40:32 2016
  DistUpgraded: 2016-10-13 13:22:55,920 DEBUG running apport_crash()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
  InstallationDate: Installed on 2016-09-13 (42 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (12 days ago)
  

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2016-10-25 Thread Jamie Strandboge
FYI, im-config is verification-done. I didn't do full SRU testing for
AppArmor. Tyler, when you are done with the SRU testing, feel free to
mark this as verification-done.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in im-config source package in Xenial:
  Fix Committed
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly are 

[Touch-packages] [Bug 1553328] Re: Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

2016-10-25 Thread Daniel van Vugt
** Summary changed:

- Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors or opening the web browser app
+ Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors, webbrowser-app or system settings

** Summary changed:

- Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors, webbrowser-app or system settings
+ Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref() especially 
with multiple monitors, webbrowser-app or system settings

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

Title:
  Mir/Unity8 crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1635775] Re: No sound unity8 apps 16.10

2016-10-25 Thread Daniel van Vugt
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Changed in: canonical-devices-system-image
   Status: New => Incomplete

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

Title:
  No sound unity8 apps 16.10

Status in Canonical System Image:
  Incomplete
Status in media-hub package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Testing on a Lenovo Thinkpad X220T running fresh install of Ubuntu
  16.10. Running Checkbox passes the sound tests (as audio is played),
  but when using unity8 apps no sound comes out. However, sound does
  come out from Libertine containerized apps.

  For example, I can be running the default Browser app playing a video,
  and no sound will come out. However, when playing the same video under
  Firefox or playing music in Pithos in a Libertine container, sound
  works fine.

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

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


[Touch-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens

2016-10-25 Thread Daniel van Vugt
Technically not really a High bug, but we should keep a close eye on the
number of visual regressions in Unity8 compared to Unity7. So that
overall problem is itself High.

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

Title:
  Font/text rendering is irregular and not pixel-aligned on low DPI
  screens

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  New
Status in fontconfig package in Ubuntu:
  Incomplete
Status in freetype package in Ubuntu:
  Incomplete
Status in harfbuzz package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
  unity8 Mir session

  the version of qtdeclarative5-qtmir-plugin is
  0.4.7+16.04.20160104-0ubuntu1

  As you can see from the screenshots the text has low details and, in
  the case of indicators descriptions at the top, almost disappears.

  The text could be fixed by using Text.NativeRendering instead of 
Text.QtRendering for the QML labels on low dpi screens, although text doesn't 
seem to be the only issue here. The icons are definitely lacking detail as well 
(QML Image's smoothing is enabled maybe?).
  Also the dots of the infographic don't look like circles at all, they're 
missing pixels and many of them look like a C more than an O.

  It looks to me like something is setting the wrong resolution, because
  it looks quite bad. But the screenshots are 1366x768 so I think that's
  not the case.

  NOTE: Unity7 looks perfectly fine and detailed

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

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


[Touch-packages] [Bug 1615209] Re: ip crashes after a few times adding and removing network namespaces

2016-10-25 Thread Launchpad Bug Tracker
[Expired for iproute2 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ip crashes after a few times adding and removing network namespaces

Status in iproute2 package in Ubuntu:
  Expired

Bug description:
  # which ip
  /sbin/ip
  # valgrind ip netns add black2
  ==22804== Memcheck, a memory error detector
  ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==22804== Command: ip netns add black2
  ==22804== 
  ==22804== Invalid write of size 1
  ==22804==at 0x4031F43: memcpy (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C83: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804==  Address 0x4227094 is 0 bytes after a block of size 28 alloc'd
  ==22804==at 0x402D17C: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C5E: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804== 
  Cannot create namespace file "/var/run/netns/black2": File exists
  ==22804== 
  ==22804== HEAP SUMMARY:
  ==22804== in use at exit: 28 bytes in 1 blocks
  ==22804==   total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated
  ==22804== 
  ==22804== LEAK SUMMARY:
  ==22804==definitely lost: 0 bytes in 0 blocks
  ==22804==indirectly lost: 0 bytes in 0 blocks
  ==22804==  possibly lost: 0 bytes in 0 blocks
  ==22804==still reachable: 28 bytes in 1 blocks
  ==22804== suppressed: 0 bytes in 0 blocks
  ==22804== Rerun with --leak-check=full to see details of leaked memory
  ==22804== 
  ==22804== For counts of detected and suppressed errors, rerun with: -v
  ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

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

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


[Touch-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

2016-10-25 Thread Jeremy Bicha
Ubuntu 16.10 has network-manager-openvpn 1.2.6-2ubuntu1

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Confirmed => Fix Released

** No longer affects: network-manager-pptp (Ubuntu)

** Also affects: network-manager-pptp (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: network-manager-pptp (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-pptp package in Ubuntu:
  Fix Released
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Fix Released
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

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

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


[Touch-packages] [Bug 1443203] Re: GUFW blocks all incoming VNC connections even if rules allow

2016-10-25 Thread Jamie Strandboge
Can you provide the kernel output right after trying to access the
machine? Eg, on the system with ufw, do:

$ grep -i ufw /var/log/kern.log

or if you have redirected ufw output to go to another log file, attach
that logfile (eg, /var/log/ufw.log).

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

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

Title:
  GUFW blocks all incoming VNC connections even if rules allow

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  I am having a problem with GUFW.  I have it set to block incoming
  connections from everything.  I then set rules to allow incoming
  connections from a VNC client on my local network to a VMWare Player
  VNC setup but no matter what I do with those rules, I cannot connect
  to the VNC server on my machine unless I change the setting for my
  profile to Allow for everything.  Making and applying rules has no
  effect if the "Incoming" setting at the top of the application is set
  to Deny or Reject.

  The only other option is to turn off the firewall entirely for a
  moment for the VNC client to connect, and then turn it back on again
  once a connection is established.  Allowing all incoming connections
  for even a few moments just to use VNC on one port is a security risk.

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

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


[Touch-packages] [Bug 1632602] Re: no adb access under xenial+systemd user build

2016-10-25 Thread Yuan-Chen Cheng
verify the following build have adb after turned on in system-settings.

current build number: 68
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-10-26 00:51:22
version version: 68
version ubuntu: 20161025
version device: 20161014.0
version custom: 20161025


** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Vicamo Yang (vicamo)

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

** Changed in: android-tools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  no adb access under xenial+systemd user build

Status in Canonical System Image:
  Fix Released
Status in android-tools package in Ubuntu:
  Fix Released

Bug description:
  adb service under user build involves several other parties and is
  currently not implemented.

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

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


[Touch-packages] [Bug 1632272] Re: need writable-path for snappy

2016-10-25 Thread Yuan-Chen Cheng
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Vicamo Yang (vicamo)

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

Title:
  need writable-path for snappy

Status in Canonical System Image:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released

Bug description:
  Snappy writes to /etc/systemd/system, /snap and /var/lib/snapd.

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

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


[Touch-packages] [Bug 1614942] Re: "GLib-CRITICAL" messages keep appearing in log file

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

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

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

Title:
  "GLib-CRITICAL" messages keep appearing in log file

Status in consolekit package in Ubuntu:
  Confirmed

Bug description:
  At regular intervals, errors appear in the log files from consolekit:

  Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: 
GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: 
GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 
1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 
1118 was not found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: consolekit 0.4.6-5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 13:09:22 2016
  InstallationDate: Installed on 2012-03-26 (1606 days ago)
  InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: consolekit
  UpgradeStatus: Upgraded to xenial on 2016-07-27 (23 days ago)

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

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


[Touch-packages] [Bug 1614942] Re: "GLib-CRITICAL" messages keep appearing in log file

2016-10-25 Thread David Hines
Might be the same bug as 1264368.

I'm thinking Manfred Hampl fixed this problem in ConsoleKit2 on Oct 5, 2014. 
Xenial is using consolekit.
https://github.com/ConsoleKit2/ConsoleKit2/commit/0b79d92001450e7f359212d4273100628f6a1693

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

Title:
  "GLib-CRITICAL" messages keep appearing in log file

Status in consolekit package in Ubuntu:
  Confirmed

Bug description:
  At regular intervals, errors appear in the log files from consolekit:

  Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: 
GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: 
GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 
1118 was not found when attempting to remove it
  Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 
1118 was not found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: consolekit 0.4.6-5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 13:09:22 2016
  InstallationDate: Installed on 2012-03-26 (1606 days ago)
  InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: consolekit
  UpgradeStatus: Upgraded to xenial on 2016-07-27 (23 days ago)

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

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


[Touch-packages] [Bug 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop

2016-10-25 Thread Daniel van Vugt
Invalid for Mir: Mir is not related to backlight brightness control.

Invalid for repowerd: Not running at all under Unity8 desktop.

** Changed in: mir
   Status: Incomplete => Invalid

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

** Changed in: repowerd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

Title:
  brightness not changing from either  u-s-s or hardkey on
  unity8-desktop

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in repowerd package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Running unity8-desktop session on my macbookpro which has a hard display 
brightness key, currently it makes no effect. Also, opened 
ubuntu-sytstem-settings and changing the brightness slider also makes no effect.
  sorry for spamming projects, not sure which to log against.

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

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


[Touch-packages] [Bug 1608342] Re: Add a scope to expose native GTK apps (without Xmir)

2016-10-25 Thread Daniel van Vugt
** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  Add a scope to expose native GTK apps (without Xmir)

Status in Canonical System Image:
  Confirmed
Status in unity8-desktop-session:
  New
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Add a scope to expose native GTK apps (without Xmir).

  In future we'll be able to run most GTK apps natively in Mir/Unity8 without 
using Xmir/X11. Some of them kind of work already:
  gedit -- --desktop_file_hint=unity8
  sol -- --desktop_file_hint=unity8

  However we will need a Unity8 scope that exposes the availability of
  such built-in apps to the user.

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

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


[Touch-packages] [Bug 1539011] Re: [regression] Window resizing is very choppy and stutters (border does not smoothly follow the mouse)

2016-10-25 Thread Daniel van Vugt
** Tags added: performance

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

Title:
  [regression] Window resizing is very choppy and stutters (border does
  not smoothly follow the mouse)

Status in Canonical System Image:
  New
Status in QtMir:
  Invalid
Status in Ubuntu UX:
  Confirmed
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Just tried Unity8 desktop for the first time since October and found
  some things don't work as well as before. One of them is window
  resizing, which is now every choppy and stuttering.

  Please also see bug 1540702 so as to not confuse the two.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160122-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 28 18:39:38 2016
  InstallationDate: Installed on 2015-12-03 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8-dash.log: Attempted to deliver an event to a non-existent 
window, ignoring.

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

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


[Touch-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens

2016-10-25 Thread Daniel van Vugt
Found this image today, showing Unity8's font rendering next to GTK's:
https://launchpadlibrarian.net/290523497/IMG_1258.JPG

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
   Importance: Medium => High

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

Title:
  Font/text rendering is irregular and not pixel-aligned on low DPI
  screens

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  New
Status in fontconfig package in Ubuntu:
  Incomplete
Status in freetype package in Ubuntu:
  Incomplete
Status in harfbuzz package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and
  unity8 Mir session

  the version of qtdeclarative5-qtmir-plugin is
  0.4.7+16.04.20160104-0ubuntu1

  As you can see from the screenshots the text has low details and, in
  the case of indicators descriptions at the top, almost disappears.

  The text could be fixed by using Text.NativeRendering instead of 
Text.QtRendering for the QML labels on low dpi screens, although text doesn't 
seem to be the only issue here. The icons are definitely lacking detail as well 
(QML Image's smoothing is enabled maybe?).
  Also the dots of the infographic don't look like circles at all, they're 
missing pixels and many of them look like a C more than an O.

  It looks to me like something is setting the wrong resolution, because
  it looks quite bad. But the screenshots are 1366x768 so I think that's
  not the case.

  NOTE: Unity7 looks perfectly fine and detailed

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

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


[Touch-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor

2016-10-25 Thread Daniel van Vugt
** Changed in: nautilus (Ubuntu)
 Assignee: Sebastien Bacher (seb128) => (unassigned)

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

Title:
  [yakkety] desktop is black and/or flickering after plugging in a
  second monitor

Status in compiz package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
  Graphic chips:
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06)
  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] 
[10de:139b] (rev ff)

  Desktop wallpaper on extended display shows black background only, and
  the hdmi detection is very unstable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-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
  Date: Fri Sep 23 05:30:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-09-20 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  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 1:1.0.12-2

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

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


[Touch-packages] [Bug 1634888] Re: Problems switching VTs

2016-10-25 Thread Daniel van Vugt
** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir (Ubuntu)
 Assignee: Chris Halse Rogers (raof) => (unassigned)

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

Title:
  Problems switching VTs

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  I've hit an issue where LightDM trying to switch directly from a USC-
  owned VT to an X-owned VT crashes X instead and doesn't switch VTs
  after all.

  I'm not sure exactly where the problem lies or exactly what the root
  cause is.  But here's my reproduction steps:

  1) bileto host-upgrade 1679 # upgrades unity8 to have an in-session 
lockscreen -- you must be in vivid, xenial, or zesty
  2) sudo apt update && sudo apt upgrade
  3) sudo apt install unity8-desktop-session
  4) Reboot
  5) Log one user into a unity7 session.
  6) Switch users and log a separate user into a unity8 session.
  7) In unity8, press Ctrl+L to show the in-session lockscreen and switch to 
the unity7 user.
  8) Usually this breaks things and the switch doesn't happen.  Sometimes it 
will work in which case switch back and forth until it does.

  That's a bit of a pain, I understand.  It's just the how I hit this
  bug.  I think switching directly from a USC-owned VT to an X-owned VT
  is hitting a new and odd code path.

  What happens under the cover that I've found is that X fails during
  EnterVT and aborts.  Which confuses everyone else, including lightdm.

  RAOF says "The hypothesis is that Mir fails to drop master for
  whatever reason, which results in it (correctly) NAKing the VT switch.
  (We call drmDropMaster, but that can fail; if it does, we throw an
  exception, (silently) catch it, and NAK the VT switch)"

  I have a USC log with MIR_SERVER_DISPLAY_REPORT=log set (though I
  can't see any display report spew...?) but it's not very revealing:
  http://paste.ubuntu.com/23348320

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

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


[Touch-packages] [Bug 1636305] Re: [Feature Request] Emoticon Menu For Text Fields In Desktop Mode

2016-10-25 Thread Daniel van Vugt
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Changed in: canonical-devices-system-image
   Importance: Undecided => Wishlist

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [Feature Request] Emoticon Menu For Text Fields In Desktop Mode

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  When in desktop mode it's difficult to enter emojis when typing.

  I propose that when you right-click in a text field an additional
  field in the menu pop ups, where you can choose an emoticon either
  from a big list or categorized in sub menus.

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

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


[Touch-packages] [Bug 1635928] Re: If a window is too small, GTK menus do not display correctly

2016-10-25 Thread Daniel van Vugt
Interesting problem. I would have thought that at some stage GTK menus
should be able to extend beyond the parent window. Although while
they're being rendered natively within it, that can never happen.

** Summary changed:

- if a window is too small, menus do not display correctly
+ If a window is too small, GTK menus do not display correctly

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

** Changed in: mir
   Status: New => Invalid

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

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

Title:
  If a window is too small, GTK menus do not display correctly

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

Bug description:
  if a window is too small, menus do not display correctly (eg with
  gedit, look at the screenshot)

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

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


[Touch-packages] [Bug 1636697] [NEW] tracker-miner-fs

2016-10-25 Thread electrocoder
Public bug reported:


Ubuntu 16.10 tracker-miner-fs 100% of CPU and 700mb RAM.

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

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

Title:
  tracker-miner-fs

Status in tracker package in Ubuntu:
  New

Bug description:
  
  Ubuntu 16.10 tracker-miner-fs 100% of CPU and 700mb RAM.

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

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


[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-10-25 Thread Daniel van Vugt
I think the attached recent branches have solved this in general. It's
still failing in Brandon's branches only, but probably for good reason.

** Changed in: mir
   Status: In Progress => Fix Committed

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

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

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


[Touch-packages] [Bug 1633390] Re: unity 8 login stalls

2016-10-25 Thread Daniel van Vugt
Oh! It looks like your problem might simply be that the default graphics
drivers are not installed...

Please run:
   sudo apt install mir-graphics-drivers-desktop
and then reboot/try again.

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

Title:
  unity 8 login stalls

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

Bug description:
  Contrary to other login problems with Unity 8 (as installed by default
  in Ubuntu 16.10), I'm not getting a black screen when trying to log
  in. After entering my password the login screen just sort of hangs;
  I'm left with the login GUI (which is frozen) and the top panel (which
  I can use) to display the suspend / restart options. I left it running
  for quite a while, but nothing happened. I can log in to the default
  environment easily.

  I'm running a System 76 Meerkat, having upgraded from Ubuntu 16.04 without 
wiping my system drive.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-01 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags: third-party-packages yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1633390] Re: unity 8 login stalls

2016-10-25 Thread Daniel van Vugt
Thanks, but the required info is still missing.

The critical file from 15 October unity-system-compositor.log is zero
bytes, and your unity8 logs have not been touched since 5 October. So it
sounds like unity-system-compositor.log will hold the answer. Please try
copying it again as root (sudo).

-rw-r- nthnrssllnsr/nthnrssllnsr 14272 2016-10-02 17:38 bug/unity8.log.4.gz
-rw-r- nthnrssllnsr/nthnrssllnsr  1843 2016-10-05 22:45 
bug/unity8-dash.log.2.gz
-rw-r- nthnrssllnsr/nthnrssllnsr 25256 2016-10-02 14:35 
bug/unity8-dash.log.6.gz
-rw-r- nthnrssllnsr/nthnrssllnsr   120 2016-10-11 05:22 
bug/unity8-filewatcher.log.1.gz
-rw-r- nthnrssllnsr/nthnrssllnsr  4278 2016-10-05 21:43 bug/unity8.log.3.gz
-rw-r- nthnrssllnsr/nthnrssllnsr 11025 2016-10-02 17:38 
bug/unity8-dash.log.5.gz
-rw-r- nthnrssllnsr/nthnrssllnsr  1230 2016-10-05 22:48 
bug/unity8-dash.log.1.gz
-rw-r- nthnrssllnsr/nthnrssllnsr63 2016-10-02 07:12 bug/unity8.log.6.gz
-rw-r- nthnrssllnsr/nthnrssllnsr 23743 2016-10-05 22:44 bug/unity8.log.2.gz
-rw-r- nthnrssllnsr/nthnrssllnsr94 2016-10-02 17:38 
bug/unity8-dash.log.4.gz
drwxr-xr-x nthnrssllnsr/nthnrssllnsr 0 2016-10-20 04:56 bug/
-rw-r- nthnrssllnsr/nthnrssllnsr  4101 2016-10-02 17:38 bug/unity8.log.5.gz
-rw-r- nthnrssllnsr/nthnrssllnsr   583 2016-10-05 22:47 bug/unity8.log.1.gz
-rw--- nthnrssllnsr/nthnrssllnsr 0 2016-10-15 03:43 
bug/unity-system-compositor.log
-rw-r- nthnrssllnsr/nthnrssllnsr   788 2016-10-05 21:42 
bug/unity8-dash.log.3.gz

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

Title:
  unity 8 login stalls

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

Bug description:
  Contrary to other login problems with Unity 8 (as installed by default
  in Ubuntu 16.10), I'm not getting a black screen when trying to log
  in. After entering my password the login screen just sort of hangs;
  I'm left with the login GUI (which is frozen) and the top panel (which
  I can use) to display the suspend / restart options. I left it running
  for quite a while, but nothing happened. I can log in to the default
  environment easily.

  I'm running a System 76 Meerkat, having upgraded from Ubuntu 16.04 without 
wiping my system drive.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-01 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags: third-party-packages yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1636689] [NEW] package sasl2-bin 2.1.26.dfsg1-14build1 [modified: usr/bin/sasl-sample-client usr/sbin/sasl-sample-server] failed to install/upgrade: subprocess installed post-ins

2016-10-25 Thread Kumaran A
Public bug reported:

First of all, I am not sure if this is a bug. This page opened when I
tried to report using Apport. The following is the message that appears
during boot:

"Saslauthd service always exits with status 2."

The following is the output of "systemctl status saslauthd.service":

● saslauthd.service - LSB: saslauthd startup script
   Loaded: loaded (/etc/init.d/saslauthd; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2016-10-26 09:13:49 IST; 2min 
45s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 26683 ExecStart=/etc/init.d/saslauthd start (code=exited, status=2)

Oct 26 09:13:49 kumaran-desktop systemd[1]: Starting LSB: saslauthd startup 
script...
Oct 26 09:13:49 kumaran-desktop systemd[26683]: saslauthd.service: Executing: 
/etc/init.d/saslauthd start
Oct 26 09:13:49 kumaran-desktop saslauthd[26683]: /etc/init.d/saslauthd: 67: 
/etc/default/saslauthd: Syntax error: Unterminated quoted string
Oct 26 09:13:49 kumaran-desktop systemd[1]: saslauthd.service: Control process 
exited, code=exited status=2
Oct 26 09:13:49 kumaran-desktop systemd[1]: Failed to start LSB: saslauthd 
startup script.
Oct 26 09:13:49 kumaran-desktop systemd[1]: saslauthd.service: Unit entered 
failed state.
Oct 26 09:13:49 kumaran-desktop systemd[1]: saslauthd.service: Failed with 
result 'exit-code'.

The following troubleshooting steps are tried:
1) Removed and purged sasl2-bin & resinstalled
2) Tried restarting the service using terminal after system boot
3) Performed the steps in the following link once again from start to finish:
https://help.ubuntu.com/community/Postfix

I am using postfix and sasl not on a server but on a desktop mainly for
internal mail transfers and for cron job facilitation purposes.

I am new to Ubuntu and *nix operating systems. I am learning by trial
and error. This service was running OK before.

I am running Ubuntu 16.04.1 LTS Desktop on my system.

Thanks,
Kumaran A

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sasl2-bin 2.1.26.dfsg1-14build1 [modified: usr/bin/sasl-sample-client 
usr/sbin/sasl-sample-server]
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_4_0_43_63_generic_13
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 sasl2-bin: Install
 sasl2-bin: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct 26 09:13:42 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: cyrus-sasl2
Title: package sasl2-bin 2.1.26.dfsg1-14build1 [modified: 
usr/bin/sasl-sample-client usr/sbin/sasl-sample-server] failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.saslauthd: 2016-09-14T08:04:22.466595

** Affects: cyrus-sasl2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package sasl2-bin 2.1.26.dfsg1-14build1 [modified: usr/bin/sasl-
  sample-client usr/sbin/sasl-sample-server] failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  First of all, I am not sure if this is a bug. This page opened when I
  tried to report using Apport. The following is the message that
  appears during boot:

  "Saslauthd service always exits with status 2."

  The following is the output of "systemctl status saslauthd.service":

  ● saslauthd.service - LSB: saslauthd startup script
 Loaded: loaded (/etc/init.d/saslauthd; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Wed 2016-10-26 09:13:49 IST; 2min 
45s ago
   Docs: man:systemd-sysv-generator(8)
Process: 26683 ExecStart=/etc/init.d/saslauthd start (code=exited, status=2)

  Oct 26 09:13:49 kumaran-desktop systemd[1]: Starting LSB: saslauthd startup 
script...
  Oct 26 09:13:49 kumaran-desktop systemd[26683]: saslauthd.service: Executing: 
/etc/init.d/saslauthd start
  Oct 26 09:13:49 kumaran-desktop saslauthd[26683]: /etc/init.d/saslauthd: 67: 
/etc/default/saslauthd: Syntax error: Unterminated quoted string
  Oct 26 09:13:49 kumaran-desktop systemd[1]: saslauthd.service: Control 
process exited, code=exited status=2
  Oct 26 09:13:49 kumaran-desktop systemd[1]: Failed to start LSB: saslauthd 
startup script.
  Oct 26 09:13:49 kumaran-desktop systemd[1]: saslauthd.service: Unit entered 
failed state.
  Oct 26 09:13:49 kumaran-desktop systemd[1]: saslauthd.service: Failed with 
result 'exit-code'.

  The following 

[Touch-packages] [Bug 1583469] Re: Screen jitters/flickers wildly - Unity8 screen does not fit the physical screen

2016-10-25 Thread Daniel van Vugt
** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

Title:
  Screen jitters/flickers wildly - Unity8 screen does not fit the
  physical screen

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I set the BQ M10 device in Desktop mode yesterday evening.

  After that i used the tablet mode. Then i went to sleep. As i turned
  on my device i got the flickering in the video.

  I restarted the device. The flickering was gone.

  The device is on the image version: r108

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

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


[Touch-packages] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

2016-10-25 Thread Daniel van Vugt
** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Triaged

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  Triaged
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

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

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


[Touch-packages] [Bug 1627942] Re: unity8 of 16.10 can't start, keep black screen, lenovo R61i

2016-10-25 Thread Daniel van Vugt
It now appears Mir can support your system just fine (unity-system-
compositor.log):

[2016-09-27 13:48:33.471796] GLRenderer: GL vendor: Intel Open Source 
Technology Center
[2016-09-27 13:48:33.471847] GLRenderer: GL renderer: Mesa DRI Intel(R) 965GM 
[2016-09-27 13:48:33.471882] GLRenderer: GL version: OpenGL ES 2.0 Mesa 12.0.3
[2016-09-27 13:48:33.471922] GLRenderer: GLSL version: OpenGL ES GLSL ES 1.0.16

However the above segfaults in unity8-dash and also:

[2016-09-27:13:32:42.951] QEGLPlatformContext: eglSwapBuffers failed:
3000

both suggest that Qt/Unity8 has trouble supporting your graphics chip.
Looks like we will need to get hold of a Core 2 Duo system to test...

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

Title:
  unity8 of 16.10 can't start, keep black screen, lenovo R61i

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

Bug description:
  I only install openbox, LXQT and Unity8 session.
  LxQt is fine.

  After input password,
  The screen is black few seconds.
  Next in screen there are is a small rectangle with text "Scope".
  Next In the rectangle there is a ubuntu arc logo is rolling.
  Next the rolling logo is frozen.
  Next all are black few seconds.
  From a ssh console ,I can see the cpu rate of unity8, unity8.dash or applet.y 
is very high(70% --100%)

  And again and again.

  If anybody need more info, comments on the issue.
  This is its upstart.log:

  [2016-09-27:13:35:18.182] qtmir.screens: ScreensModel::ScreensModel
  [2016-09-27 13:35:18.198252] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.24.0)
  [2016-09-27 13:35:18.198494] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.24.0)
  [2016-09-27:13:35:18.200] qtmir.mir: MirServer created
  [2016-09-27:13:35:18.200] qtmir.mir: Command line arguments passed to Qt: 
("unity8", "--mode=full-shell")
  [2016-09-27:13:35:18.203] QSocketNotifier: Can only be used with threads 
started with QThread
  [2016-09-27 13:35:18.204972] mirserver: Starting
  [2016-09-27 13:35:18.254431] mirserver: Using nested cursor
  [2016-09-27 13:35:18.255972] mirserver: Initial display configuration:
  [2016-09-27 13:35:18.258509] mirserver:   0.30: LVDS 14.0" 300x190mm
  [2016-09-27 13:35:18.258591] mirserver: Current mode 1280x800 60.00Hz
  [2016-09-27 13:35:18.258637] mirserver: Preferred mode 1280x800 
60.00Hz
  [2016-09-27 13:35:18.258672] mirserver: Logical position +0+0
  [2016-09-27 13:35:18.258716] mirserver:   0.40: unused VGA
  [2016-09-27 13:35:18.258755] mirserver:   0.43: unused DVI-D
  [2016-09-27:13:35:18.259] qtmir.mir: 
PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x7f5b6c204630)
  [2016-09-27:13:35:18.259] qtmir.mir: SessionListener::SessionListener - this= 
SessionListener(0x7f5b6c204540)
  [2016-09-27:13:35:18.261] qtmir.mir: 
MirWindowManagerImpl::MirWindowManagerImpl
  [2016-09-27 13:35:18.263049] mirserver: Mir version 0.24.0
  [2016-09-27:13:35:18.263] qtmir.screens: QtCompositor::start
  [2016-09-27:13:35:18.342] qtmir.screens: ScreensModel::update
  [2016-09-27:13:35:18.343] qtmir.sensor: Screen - nativeOrientation is: 
Qt::ScreenOrientation(LandscapeOrientation)
  [2016-09-27:13:35:18.344] qtmir.sensor: Screen - initial currentOrientation 
is: Qt::ScreenOrientation(LandscapeOrientation)
  [2016-09-27:13:35:18.355] qtmir.screens: Added Screen with id 30 and geometry 
QRect(0,0 1280x800)
  [2016-09-27:13:35:18.355] qtmir.screens: Screen::setMirDisplayBuffer 
Screen(0x5570d2904f40) 0x7f5b6c1d2ca0 0x7f5b6c2028f0
  [2016-09-27:13:35:18.355] qtmir.screens: 
===
  [2016-09-27:13:35:18.355] qtmir.screens: Screen(0x5570d2904f40) - id: 30 
geometry: QRect(0,0 1280x800) window: 0x0 type: "LVDS" scale: 1
  [2016-09-27:13:35:18.355] qtmir.screens: 
===
  [2016-09-27:13:35:18.484] qtmir.applications: 
UnityApplicationPlugin::registerTypes - this= 
UnityApplicationPlugin(0x7f5b40047ba0) uri= Unity.Application
  [2016-09-27:13:35:20.824] Using "/etc/ubuntu/devices.conf" as device 
configuration file
  [2016-09-27:13:35:20.832] QObject: Cannot create children for a parent that 
is in a different thread.
  (Parent is DashCommunicator(0x5570d2a8fbf0), parent's thread is 
QThread(0x5570d28a83f0), current thread is DashCommunicator(0x5570d2a8fbf0)
  [2016-09-27:13:35:20.833] unity.topsurfacelist: TopLevelSurfaceList()
  [2016-09-27:13:35:20.834] qtmir.surfaces: MirSurfaceItem::MirSurfaceItem
  [2016-09-27:13:35:20.842] 
file:///usr/share/unity8//Components/Showable.qml:43: Error: Cannot assign to 
non-existent property "target"
  [2016-09-27:13:35:20.843] 
file:///usr/share/unity8//Components/Showable.qml:42: Error: Cannot assign to 
non-existent property "target"
  [2016-09-27:13:35:20.891] Fail to connect with 

[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

2016-10-25 Thread Daniel van Vugt
I've now replaced the whole PC and kept the old harddrive. But this bug
remains even in the new system. Again unplugging my USB DVB tuner is the
workaround.

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  SRU TEST CASE (upower)
  --
  On affected machines, unity-settings-daemon crashes immediately on login, as 
due to a kernel bug upowerd takes a very long time to start. With the fixed 
package the crash is fixed. Power status information will still be wrong, but 
at least theme, hotkeys, and all other unity-settings-daemon functionality will 
work.

  This can be synthetically tested with:

     DBUS_SYSTEM_BUS_ADDRESS=foo upower --dump

  With the current xenial version this causes a segfault, while with the
  fix you get a proper error message.

  Fix: https://cgit.freedesktop.org/upower/commit/?id=932a6a39e3
 https://cgit.freedesktop.org/upower/commit/?id=4e83fabac
  (The second one is not crucial, but provides a much better failure mode for 
the "upower" CLI tool).

  Regression potential: This changes the core behaviour of libupower.
  The patch is carefully written to be backwards compatible to the
  extent possible, but changing the behaviour is necessary to fix this
  bug (see commit log for details). Thus clients such as unity-control-
  center, unity-settings-daemon, or mate-power-manager should be tested
  as part of the verification.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1636651] [NEW] Nvidia HDMI audio problem.[MS-7851, Nvidia GPU 1c HDMI/DP, Digital Out, HDMI] Sound is distorted

2016-10-25 Thread Vicente Serra
Public bug reported:

Maybe I need to update alsa or something?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D7p:   capirote   2355 F...m pulseaudio
 /dev/snd/controlC1:  capirote   2355 F pulseaudio
 /dev/snd/controlC0:  capirote   2355 F pulseaudio
 /dev/snd/seq:capirote   3842 F chromium-browse
CurrentDesktop: Unity
Date: Wed Oct 26 01:15:25 2016
InstallationDate: Installed on 2014-12-16 (678 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GF119 HDMI Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [MS-7851, Nvidia GPU 1c HDMI/DP, Digital Out, HDMI] Sound is distorted
UpgradeStatus: Upgraded to xenial on 2016-07-03 (114 days ago)
dmi.bios.date: 03/30/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V10.6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81I (MS-7851)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd03/30/2015:svnMSI:pnMS-7851:pvr2.0:rvnMSI:rnH81I(MS-7851):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7851
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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

Title:
  Nvidia HDMI audio problem.[MS-7851, Nvidia GPU 1c HDMI/DP, Digital
  Out, HDMI] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Maybe I need to update alsa or something?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D7p:   capirote   2355 F...m pulseaudio
   /dev/snd/controlC1:  capirote   2355 F pulseaudio
   /dev/snd/controlC0:  capirote   2355 F pulseaudio
   /dev/snd/seq:capirote   3842 F chromium-browse
  CurrentDesktop: Unity
  Date: Wed Oct 26 01:15:25 2016
  InstallationDate: Installed on 2014-12-16 (678 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GF119 HDMI Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [MS-7851, Nvidia GPU 1c HDMI/DP, Digital Out, HDMI] Sound is distorted
  UpgradeStatus: Upgraded to xenial on 2016-07-03 (114 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81I (MS-7851)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd03/30/2015:svnMSI:pnMS-7851:pvr2.0:rvnMSI:rnH81I(MS-7851):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7851
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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


[Touch-packages] [Bug 1573115] Re: No Speakers Sound in Ubuntu 16.04

2016-10-25 Thread zoltron
** Package changed: compiz-plugins-main (Ubuntu) => alsa-driver (Ubuntu)

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

Title:
  No Speakers Sound in Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I recently installed Ubuntu 16.04 and I'm having a problem with my audio 
device.
  *The internal mic is working properly
  *The external output (headphones) is working properly too.
  *But the internal speakers doesn't work.

  I tried on the live version of 16.04 and I had the same issue.

  Information of my laptop:

  lspci  -v:

  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition 
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 39
Memory at f7f0 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  aplay -l:

   Lista de PLAYBACK dispositivos hardware 
  tarjeta 0: PCH [HDA Intel PCH], dispositivo 0: Generic Analog [Generic Analog]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0
  tarjeta 0: PCH [HDA Intel PCH], dispositivo 3: Generic Digital [Generic 
Digital]
Subdispositivos: 1/1
Subdispositivo #0: subdevice #0

  Attached you can see the alsamixer configuration which shows the
  speaker volume. In capture view the audio is also in 100%

  I have no idea how to solve it. I used the same laptop with 14.04LTS
  without this problem.

  Regards

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

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


[Touch-packages] [Bug 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl

2016-10-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1553328 ***
https://bugs.launchpad.net/bugs/1553328

Actually comment #7 suggests you're experiencing the same nouveau
instability as other people; see bug 1553328. So I'll make this a
duplicate of that.

If you continue to experience other issues like "ASSERT:
eglSwapBuffers..." then please un-duplicate this.


** This bug has been marked a duplicate of bug 1553328
   Mir crashes on nouveau (nv50) in pushbuf_kref() especially with multiple 
monitors

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

Title:
  Unity 8 Desktop Preview System Settings do not work on nouveau
  [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file
  ../../../src/ubuntumirclient/glcontext.cpp, line 239]

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When I try to open System Settings, the Ubuntu logo keeps turning and nothing 
happens.
  I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I 
use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with 
English (US) language settings, because Unity 8 does not work well when I use 
my own account with my language settings.

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

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


[Touch-packages] [Bug 1631627] Re: Unity 8 freezes on Nouveau

2016-10-25 Thread Daniel van Vugt
Hannie, you are probably experiencing bug 1553328 if the problems start
with the web browser app.

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

Title:
  Unity 8 freezes on Nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes
  after I do some clicking around the desktop (using Browser, System
  Settings and the like), I am running it on Nouveau driver for GTX970M,
  I refrained from installing proprietary drivers to test Unity 8, but
  it is unusable and after it freezes I can only power off my laptop as
  nothing works. Is this a known issue? Also Unity 7 does not load at
  all, but I will post a separate bug for that.

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

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


[Touch-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor

2016-10-25 Thread Daniel van Vugt
Yep, that's one of two workarounds mentioned in comment #10.

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

Title:
  [yakkety] desktop is black and/or flickering after plugging in a
  second monitor

Status in compiz package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
  Graphic chips:
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06)
  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] 
[10de:139b] (rev ff)

  Desktop wallpaper on extended display shows black background only, and
  the hdmi detection is very unstable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-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
  Date: Fri Sep 23 05:30:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-09-20 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  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 1:1.0.12-2

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

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


[Touch-packages] [Bug 1584894] Re: unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU

2016-10-25 Thread Daniel van Vugt
** Changed in: mir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  unity-system-compositor crashes on start-up with "Mir fatal error:
  Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  (separated from bug 1118903)
  unity-system-compositor crashes on start-up with "Mir fatal error: Failed to 
schedule page flip" on VirtualBox Graphics Adapter

  ---

  can not login to Unity8

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 23 19:20:43 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-19 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:

  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  version.libdrm: libdrm2 2.4.68-1
  version.lightdm: lightdm 1.19.0-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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


[Touch-packages] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

2016-10-25 Thread Daniel van Vugt
Indeed, the current state of VM support for Mir/Unity8 is:

(1) QXL works already (modulo that mouse problem, please log a new bug)
(2) VirtualBox will be next (aiming before 17.04): bug 1584894
(3) Generalised software rendering on fbdev or SimpleDRM later (still hoping 
for 17.04): this bug 1118903

** Changed in: mir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

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

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


[Touch-packages] [Bug 1631627] Re: Unity 8 freezes on Nouveau

2016-10-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1553328 ***
https://bugs.launchpad.net/bugs/1553328

I meant to say "I don't think we're going to get anywhere with Nouveau
on Unity8"

** This bug has been marked a duplicate of bug 1553328
   Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors or opening the web browser app

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

Title:
  Unity 8 freezes on Nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes
  after I do some clicking around the desktop (using Browser, System
  Settings and the like), I am running it on Nouveau driver for GTX970M,
  I refrained from installing proprietary drivers to test Unity 8, but
  it is unusable and after it freezes I can only power off my laptop as
  nothing works. Is this a known issue? Also Unity 7 does not load at
  all, but I will post a separate bug for that.

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

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


[Touch-packages] [Bug 1631627] Re: Unity 8 freezes on Nouveau

2016-10-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1553328 ***
https://bugs.launchpad.net/bugs/1553328

I don't think we're going to get anywhere with Unity8 till bug 1553328
is fixed. And most people here seem to be experiencing that.

So duplicate of bug 1553328 until further notice.

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

Title:
  Unity 8 freezes on Nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes
  after I do some clicking around the desktop (using Browser, System
  Settings and the like), I am running it on Nouveau driver for GTX970M,
  I refrained from installing proprietary drivers to test Unity 8, but
  it is unusable and after it freezes I can only power off my laptop as
  nothing works. Is this a known issue? Also Unity 7 does not load at
  all, but I will post a separate bug for that.

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

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


[Touch-packages] [Bug 1573115] [NEW] No Speakers Sound in Ubuntu 16.04

2016-10-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I recently installed Ubuntu 16.04 and I'm having a problem with my audio device.
*The internal mic is working properly
*The external output (headphones) is working properly too.
*But the internal speakers doesn't work.

I tried on the live version of 16.04 and I had the same issue.

Information of my laptop:

lspci  -v:

00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Dell 6 Series/C200 Series Chipset Family High Definition 
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 39
Memory at f7f0 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

aplay -l:

 Lista de PLAYBACK dispositivos hardware 
tarjeta 0: PCH [HDA Intel PCH], dispositivo 0: Generic Analog [Generic Analog]
  Subdispositivos: 1/1
  Subdispositivo #0: subdevice #0
tarjeta 0: PCH [HDA Intel PCH], dispositivo 3: Generic Digital [Generic Digital]
  Subdispositivos: 1/1
  Subdispositivo #0: subdevice #0

Attached you can see the alsamixer configuration which shows the speaker
volume. In capture view the audio is also in 100%

I have no idea how to solve it. I used the same laptop with 14.04LTS
without this problem.

Regards

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


** Tags: alsa audio intel pulseaudio series sound speakers
-- 
No Speakers Sound in Ubuntu 16.04
https://bugs.launchpad.net/bugs/1573115
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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


[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

2016-10-25 Thread David Hines
@Manfred you may have fix this problem in ConsoleKit2 on Oct 5, 2014. Is this 
related?
https://github.com/ConsoleKit2/ConsoleKit2/commit/0b79d92001450e7f359212d4273100628f6a1693

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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


[Touch-packages] [Bug 1553328] Re: Mir crashes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors

2016-10-25 Thread Daniel van Vugt
I guess even with a single display, multi-threaded apps like the web
browser could still trigger this nouveau crash or similar by rendering
from multiple threads.

There's a comment here suggesting the same crash might also happen in some 
processes like webbrowser-app even under Unity7:
  
https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1595238/comments/15
which further supports the theory.

Based on upstream's comment
https://bugs.freedesktop.org/show_bug.cgi?id=92438#c39 I would expect
nouveau to continue to crash under both multi-monitor and other multi-
threaded rendering conditions (like webbrowser-app?).

** Summary changed:

- Mir crashes on nouveau (nv50) in pushbuf_kref() especially with multiple 
monitors
+ Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors

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

Title:
  Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with
  multiple monitors or opening the web browser app

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1553328] Re: Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors or opening the web browser app

2016-10-25 Thread Daniel van Vugt
** Summary changed:

- Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors
+ Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with 
multiple monitors or opening the web browser app

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

Title:
  Mir/Unity8 crashes on nouveau (nv50) in pushbuf_kref() especially with
  multiple monitors or opening the web browser app

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1636236] Re: /usr/bin/unity8:11:QListData::begin:QList:qtmir::ApplicationManager::findApplicationWithPid:qtmir::ApplicationManager::findApplicationWithSession:qtmir::ApplicationM

2016-10-25 Thread Michał Sawicz
** Package changed: unity8 (Ubuntu) => qtmir (Ubuntu)

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

Title:
  
/usr/bin/unity8:11:QListData::begin:QList:qtmir::ApplicationManager::findApplicationWithPid:qtmir::ApplicationManager::findApplicationWithSession:qtmir::ApplicationManager::findApplicationWithSession

Status in qtmir package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

2016-10-25 Thread Hansen
I confirm this on buntu 16.04.1 LTS

Lenovo L450 Core i5
Network controller: Intel Corporation Wireless 7265 (rev 59)

network-manager:
  Installed: 1.2.2-0ubuntu0.16.04.3
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
 *** 1.2.2-0ubuntu0.16.04.3 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

After reawakening from suspend nm-applet has crashed show ethernet double 
arrows instead of nm-applet indicator.
Restarting nm-applet with 'killall nm-applet ; nm-applet' as workaround fixes 
it.

This bug has been reported twice before, affects more than 100 users but
hasn't been fixed and it seems that nobody are working on it.

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: 

[Touch-packages] [Bug 1636381] [NEW] Details views in dialogs are too small

2016-10-25 Thread Wolf Rogner
Public bug reported:

Details views in dialogs are too small, the viewing height is approx. 15px.
My machine has a screen resolution of 2880x1800 on 15". I have to adjust the 
scaling to 1,62 to be able to read text. This leads to just half a line 
displayed in the viewing slot.

Initially I reported this issue with deja-dup
(https://bugs.launchpad.net/bugs/1635197) but this issue also shows up
on several other dialog boxes (e.g. system updates - download of repos,
...).

Thus I presume it either to be related with Unity or xorg.

If you need additional information to identity the source, let me know.

This behaviour is new to 16.10 and can be reproduced on any machine that
I have access to.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog:
 
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: Tue Oct 25 07:59:44 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.8.0-26-generic, x86_64: installed
 nvidia-367, 367.57, 4.8.0-26-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
InstallationDate: Installed on 2016-10-22 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
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-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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 1:1.0.12-2
xserver.bootTime: Mon Oct 24 16:16:55 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6

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


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

** Attachment added: "Screenshot from 2016-10-25 08-09-38.png"
   
https://bugs.launchpad.net/bugs/1636381/+attachment/4766783/+files/Screenshot%20from%202016-10-25%2008-09-38.png

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

Title:
  Details views in dialogs are too small

Status in xorg package in Ubuntu:
  New

Bug description:
  Details views in dialogs are too 

[Touch-packages] [Bug 1636305] Re: [Feature Request] Emoticon Menu For Text Fields In Desktop Mode

2016-10-25 Thread Michał Sawicz
Adding ubuntu-keyboard as a potential input helper for hardware
keyboard.

** Package changed: unity8 (Ubuntu) => ubuntu-ui-toolkit (Ubuntu)

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

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

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

Title:
  [Feature Request] Emoticon Menu For Text Fields In Desktop Mode

Status in Ubuntu UX:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When in desktop mode it's difficult to enter emojis when typing.

  I propose that when you right-click in a text field an additional
  field in the menu pop ups, where you can choose an emoticon either
  from a big list or categorized in sub menus.

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

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


[Touch-packages] [Bug 1255610] Re: 100% CPU usage with "initctl emit plymouth-ready" process

2016-10-25 Thread Felix Moreno
Same problem in Ubuntu 16.10...

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

Title:
  100% CPU usage with "initctl emit plymouth-ready" process

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  root   977 99.1  2.7  98668 93964 ?R12:59 453:31
  initctl emit plymouth-ready

  this makes my CPU very hot, I don't know how to debug deeper. Any
  ideas?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Wed Nov 27 20:46:04 2013
  InstallationDate: Installed on 2012-03-12 (625 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=d0d8bf63-cf4c-479f-9091-1f14156a902f ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (37 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: 
'/etc/at.deny']
  modified.conffile..etc.init.d.networking: [modified]
  mtime.conffile..etc.init.d.networking: 2013-08-27T01:19:11
  upstart.upstart-file-bridge.log:
   Job got added /com/ubuntu/Upstart/jobs/unicast_2dlocal_2davahi
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2dcrash
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2drelease

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

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


[Touch-packages] [Bug 1397685] Re: git gnutls_handshake() failed: A TLS packet with unexpected length was received.

2016-10-25 Thread Nikos
git.kernel.org is configured to only allow TLS with elliptic curve
ciphersuites. Given that gnutls 2.12.x doesn't support elliptic curves,
it cannot connect to that site.

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

Title:
  git gnutls_handshake() failed: A TLS packet with unexpected length was
  received.

Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  Platform: Ubuntu 14.04, ppc64le (Power 8 LE), git version: 1:1.9.1-1
  When accessing a public repository over HTTPS, I get the following error:
  $ git clone --no-checkout https://git.fedorahosted.org/git/lvm2.git lvm2
  Cloning into 'lvm2'...
  fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.git/': 
gnutls_handshake() failed: A TLS packet with unexpected length was received.

  Accessing the same public repository from a different machine running
  in a different network - also Ubuntu 14.04, but running on x86-64, the
  commands executed with no errors. Both platforms have the same git
  version (dpkg -l | grep git)

  I checked online for an explanation. Found this:
  
http://askubuntu.com/questions/186847/error-gnutls-handshake-falied-when-connecting-to-https-servers

  According to that, Gnu TLS may have some issues when proxies
  (firewalls?) are present on the network path to the repositories. The
  recommended solution is to rebuild git using OpenSSL instead of TLS. I
  tried it and got to a different error ("Unknown SSL protocol error").

  Can you please fix git to make it work correctly?

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

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


[Touch-packages] [Bug 1397685] Re: git gnutls_handshake() failed: A TLS packet with unexpected length was received.

2016-10-25 Thread chenzero
Thanks!
I also tried on another machine, that also error.
It looks like a server configuration issue.
I will report to kernel.org later.

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

Title:
  git gnutls_handshake() failed: A TLS packet with unexpected length was
  received.

Status in git package in Ubuntu:
  Confirmed
Status in gnutls26 package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  Platform: Ubuntu 14.04, ppc64le (Power 8 LE), git version: 1:1.9.1-1
  When accessing a public repository over HTTPS, I get the following error:
  $ git clone --no-checkout https://git.fedorahosted.org/git/lvm2.git lvm2
  Cloning into 'lvm2'...
  fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.git/': 
gnutls_handshake() failed: A TLS packet with unexpected length was received.

  Accessing the same public repository from a different machine running
  in a different network - also Ubuntu 14.04, but running on x86-64, the
  commands executed with no errors. Both platforms have the same git
  version (dpkg -l | grep git)

  I checked online for an explanation. Found this:
  
http://askubuntu.com/questions/186847/error-gnutls-handshake-falied-when-connecting-to-https-servers

  According to that, Gnu TLS may have some issues when proxies
  (firewalls?) are present on the network path to the repositories. The
  recommended solution is to rebuild git using OpenSSL instead of TLS. I
  tried it and got to a different error ("Unknown SSL protocol error").

  Can you please fix git to make it work correctly?

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

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


[Touch-packages] [Bug 1621373] Re: Turkey terminated DST

2016-10-25 Thread omerfarukbzkrt
Dear All,

How to install and download dst patches on Ubuntu 14.04?İs it possible to write 
step by step?
Thanks ,

Best Regards,

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

Title:
  Turkey terminated DST

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Precise:
  Fix Released
Status in tzdata source package in Trusty:
  Fix Released
Status in tzdata source package in Xenial:
  Fix Released

Bug description:
  Hi,

  Turkey switched to permanent GMT+3 and terminated DST. Winter time
  changes will not applied at 2016-10-30.

  Turkish:
  Government publication: 
http://www.resmigazete.gov.tr/eskiler/2016/09/20160908-2.pdf
  http://aa.com.tr/tr/gunun-basliklari/kis-saati-uygulamasi-sona-erdi/642856

  English:
  
http://aa.com.tr/en/todays-headlines/turkey-to-implement-daylight-saving-time-year-round/642894

  The changes has been committed to tz project.
  https://github.com/eggert/tz/commit/3e31dbe52b8730ed762880e88bf4c68ac00b8cc3

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

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


[Touch-packages] [Bug 1636395] [NEW] dnsmasq not working with OpenVPN

2016-10-25 Thread QkiZ
Public bug reported:

I'm using OpenVPN configured with Network Manager. My VPN have a DNS
server configured by OpenVPN and config pushed by it while connecting.
This server is not registered by dnsmasq so domain names are not
resolved but pinging by IP address works. When I test name resolving by
pointing to DNS server (172.16.1.1) from VPN provider it's works. For
example:

$ host google.com 172.16.1.1
Using domain server:
Name: 172.16.1.1
Address: 172.16.1.1#53
Aliases: 

google.com has address 172.217.0.174
google.com has IPv6 address 2607:f8b0:400b:807::200e
google.com mail is handled by 30 alt2.aspmx.l.google.com.
google.com mail is handled by 20 alt1.aspmx.l.google.com.
google.com mail is handled by 40 alt3.aspmx.l.google.com.
google.com mail is handled by 10 aspmx.l.google.com.
google.com mail is handled by 50 alt4.aspmx.l.google.com.

But if I test without pointing DNS server is not working:

$ host google.com
;; connection timed out; no servers could be reached

My /etc/resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1

To repair this bug I have to kill dnsmasq and it's automatically
reloaded.

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


** Tags: dnsmasq

** Attachment added: "dnsmasq"
   https://bugs.launchpad.net/bugs/1636395/+attachment/4766832/+files/dnsmasq

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

Title:
  dnsmasq not working with OpenVPN

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  I'm using OpenVPN configured with Network Manager. My VPN have a DNS
  server configured by OpenVPN and config pushed by it while connecting.
  This server is not registered by dnsmasq so domain names are not
  resolved but pinging by IP address works. When I test name resolving
  by pointing to DNS server (172.16.1.1) from VPN provider it's works.
  For example:

  $ host google.com 172.16.1.1
  Using domain server:
  Name: 172.16.1.1
  Address: 172.16.1.1#53
  Aliases: 

  google.com has address 172.217.0.174
  google.com has IPv6 address 2607:f8b0:400b:807::200e
  google.com mail is handled by 30 alt2.aspmx.l.google.com.
  google.com mail is handled by 20 alt1.aspmx.l.google.com.
  google.com mail is handled by 40 alt3.aspmx.l.google.com.
  google.com mail is handled by 10 aspmx.l.google.com.
  google.com mail is handled by 50 alt4.aspmx.l.google.com.

  But if I test without pointing DNS server is not working:

  $ host google.com
  ;; connection timed out; no servers could be reached

  My /etc/resolv.conf:
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.1.1

  To repair this bug I have to kill dnsmasq and it's automatically
  reloaded.

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

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


[Touch-packages] [Bug 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

2016-10-25 Thread David DIDIER
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.7.10 kernel-bug-exists-upstream-4.8.4

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

Title:
  [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 13 21:49:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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: Tue Sep 13 21:14:29 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Touch-packages] [Bug 1578951] Re: Libreoffice is crashing causing the session to be booted back to the login screen

2016-10-25 Thread Lorenzo
I could always replicate the crash opening a CSV file. Activating OpenGl
renderer is a workaround.

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

Title:
  Libreoffice is crashing causing the session to be booted back to the
  login screen

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I click in a diolog box in Libreoffice, I get a black dialog screen 
flashing followed by a crash. It goes back to the logon screen within a few 
seconds.
  So if after a crash I click in any of the options to recover a document, it 
crashes again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May  6 09:55:58 2016
  DistUpgraded: 2016-04-25 20:55:16,587 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   nvidia-304, 304.131, 4.2.0-35-generic, x86_64: installed
   nvidia-304, 304.131, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  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:05cb]
  InstallationDate: Installed on 2015-05-14 (357 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9b27492d-b9b9-44b6-aa52-282b2cdd909f ro splash screen vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago)
  dmi.bios.date: 08/28/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/28/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67+git1603170630.49041c~gd~w
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.3~git1603190730.a100d8~gd~w
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.3~git1603190730.a100d8~gd~w
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1623339] Re: The system is running in low-graphics mode (Ubuntu 16.04, ARM64 platform, AST2400 VGA chip)

2016-10-25 Thread Ron Wu
Hi madbiologist,

Thank you very much for your reply.
I have put the ast_dp501_fw.bin into "/lib/firmware" and reboot Ubuntu but I 
still see "The system is running in low-graphics mode".
Also still see 'Failed to load module "ast" (module does not exist, 0)' in 
Xorg.o.log
It seems a VGA driver issue. We will request FAE of ASPEED Co. to check the VGA 
driver issue.

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

Title:
  The system is running in low-graphics mode  (Ubuntu 16.04, ARM64
  platform, AST2400 VGA chip)

Status in xorg package in Ubuntu:
  New

Bug description:
  I use netboot to install Ubuntu 16.04 in Cavium ThunderX 8800 platform
  (ARM64 core) with AST2400 VGA chip and I see "The system is running in
  low graphics mode". How can I fix this issue?

  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 aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Sep 14 14:02:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
  MachineType: Cavium ThunderX CRB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=513a25ac-9bd5-49b5-a6cb-4298036c6abd ro splash quiet vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  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 N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Sep  8 09:56:09 2016
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Touch-packages] [Bug 1567841] Re: One of my two graphics cards has started to freeze the screen

2016-10-25 Thread Carl-Johan Kjellander
I have tried the daily-current, and I could not reproduce the bug by
running it for 20 hours, and usually I can trigger the bug within an
hour.

But, I could get the livecd to match my current setup exactly. For one
thing it uses unity and not gnome-shell, and I can't install things
temporarily with apt-get. So I had to use a statically compiled chromium
instead of google chrome.

I have found two ways of triggering the bug, and it is still there on
"Ubuntu 14.04.5 LTS", and that is by letting one of these two links run
for a long time in google chrome.

http://xkcd.com/1663/
 or
https://vicandblood.itch.io/dopesmoker

And it only happens with Chrome and not Firefox.

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:04bb]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1626220] Re: please remove openjpeg

2016-10-25 Thread Flames_in_Paradise
** Tags added: kubuntu zesty

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

Title:
  please remove openjpeg

Status in calligra package in Ubuntu:
  New
Status in ffmpeg package in Ubuntu:
  New
Status in kimageformats package in Ubuntu:
  New
Status in openjpeg package in Ubuntu:
  New

Bug description:
  It looks like openjpeg packages openjpeg 1.5.2, while openjpeg2
  packages openjpeg 2.1.1. I don't think we want both packaged. It looks
  like Debian has removed openjpeg from testing and unstable.

  Thanks

  $ reverse-depends -b src:openjpeg
  Reverse-Build-Depends
  =
  * calligra  (for libopenjpeg-dev)
  * ffmpeg(for libopenjpeg-dev)
  * kimageformats (for libopenjpeg-dev)

  $ reverse-depends src:openjpeg
  Reverse-Depends
  ===
  * krita (for libopenjpeg5)
  * libavcodec-extra57(for libopenjpeg5)
  * libavcodec57  (for libopenjpeg5)

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

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


[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

2016-10-25 Thread Nikita Yerenkov-Scott
** Changed in: ubuntu-gnome
 Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott)

** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott)

** Changed in: accountsservice (Ubuntu Xenial)
 Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott)

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in accountsservice source package in Xenial:
  Triaged
Status in gnome-control-center source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Triaged

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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

2016-10-25 Thread Pander
** Tags added: zesty

-- 
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 1636476] [NEW] package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

2016-10-25 Thread ΙΩΑΝΝΗΣ ΔΑΝΔΟΥΛΑΚΗΣ
Public bug reported:

It usually happens while start up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libfontconfig1:i386 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Oct 21 23:46:28 2016
DuplicateSignature:
 package:libfontconfig1:i386:2.11.94-0ubuntu1.1
 Unpacking linux-libc-dev:amd64 (4.4.0-45.66) over (4.4.0-42.62) ...
 dpkg: error processing package libfontconfig1:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-08-11 (440 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: fontconfig
Title: package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-04-29 (178 days ago)

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


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in fontconfig package in Ubuntu:
  New

Bug description:
  It usually happens while start up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfontconfig1:i386 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 21 23:46:28 2016
  DuplicateSignature:
   package:libfontconfig1:i386:2.11.94-0ubuntu1.1
   Unpacking linux-libc-dev:amd64 (4.4.0-45.66) over (4.4.0-42.62) ...
   dpkg: error processing package libfontconfig1:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-08-11 (440 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package libfontconfig1:i386 2.11.94-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (178 days ago)

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

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


[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

2016-10-25 Thread Launchpad Bug Tracker
This bug was fixed in the package glibc - 2.23-0ubuntu4

---
glibc (2.23-0ubuntu4) xenial; urgency=medium

  * debian/rules.d/tarball.mk: Apply --no-renames to make the diff readable.
  * debian/patches/git-updates.diff: Update from release/2.23/master branch:
- Include fix for potential makecontext() hang on ARMv7 (CVE-2016-6323)
- Include fix for SEGV in sock_eq with nss_hesiod module (LP: #1571456)
- Include malloc fixes, addressing multithread deadlocks (LP: #1630302)
- debian/patches/hurd-i386/cvs-libpthread.so.diff: Dropped, upstreamed.
- debian/patches/any/submitted-argp-attribute.diff: Dropped, upstreamed.
- debian/patches/hurd-i386/tg-hurdsig-fixes-2.diff: Rebased to upstream.
  * debian/patches/ubuntu/local-altlocaledir.diff: Updated to latest version
from Martin that limits scope to LC_MESSAGES, fixing segv (LP: #1577460)
  * debian/patches/any/cvs-cos-precision.diff: Fix cos() bugs (LP: #1614966)
  * debian/testsuite-xfail-debian.mk: Allow nptl/tst-signal6 to fail on ARM.

 -- Adam Conrad   Fri, 14 Oct 2016 00:00:34 -0600

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

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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


[Touch-packages] [Bug 1577460] Update Released

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

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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


[Touch-packages] [Bug 537970] Re: Evince does not print images in some pdf files.

2016-10-25 Thread Till Kamppeter
** Changed in: cups (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Evince does not print images in some pdf files.

Status in Poppler:
  Confirmed
Status in cups package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New
Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: evince

  Evince fails to print the image in .pdf file.

  It shows up correctly in preview, acroread prints it properly.

  To reproduce:

  1) Download this here invoice: 
http://www.mlink.net.pl/~imachine/faktura_24_2010_12-03-2010.pdf
  2) Preview in Evince - company logo is here.
  3) Print - company logo is not on paper.

  Frustrating, used to work, just stopped at some point, too far back in
  time now to find out tho :/

  Cheers!

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Mar 12 10:58:00 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/evince
  NonfreeKernelModules: nvidia
  Package: evince 2.29.91-0ubuntu2
  ProcEnviron:
   SHELL=/bin/bash
   LANG=pl_PL.utf8
   LANGUAGE=pl_PL:pl:en_GB:en
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: evince
  Uname: Linux 2.6.32-16-generic x86_64

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

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


[Touch-packages] [Bug 1636505] [NEW] No play or pause option for vid.me

2016-10-25 Thread Chloe Johnson
Public bug reported:

Vidme is a video hosting website.

When I go to vidme and tap on a video to watch, it takes me to the
videos web page and shows me anthumbnail,.

Expectation: There to be a play/pause button with a timeline on that
page so you can watch the video there.

What happens: You have to open the video in a new tab to be able to play
the videos.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No play or pause option for vid.me

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Vidme is a video hosting website.

  When I go to vidme and tap on a video to watch, it takes me to the
  videos web page and shows me anthumbnail,.

  Expectation: There to be a play/pause button with a timeline on that
  page so you can watch the video there.

  What happens: You have to open the video in a new tab to be able to
  play the videos.

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

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


[Touch-packages] [Bug 1521745] Re: sshd will fail to start or restart if non-default Port option is incorrectly put after a non-default ListenAddress

2016-10-25 Thread Robie Basak
> So, yes, my configuration is invalid, but the behavior of sshd when
this happens and the experience around it could use improvement. If it
detects that the configuration is invalid, it should flag it as such and
make it obvious from the logs/stdout/stdterr rather than letting the
process try to restart and falsely report that it restarted
successfully, because it didn't.

This seems reasonable, but as you point out it would be something that
would need to be done upstream. I don't think it's appropriate for
Ubuntu to deviate from upstream on this behaviour.

To set expectations I'll set this bug Won't Fix for Ubuntu, as I don't
think we'd accept patches for this. But if upstream make related
changes, we could change the bug status to track the availability of
those changes in Ubuntu at that point.

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

** Tags added: needs-upstream-report

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

Title:
  sshd will fail to start or restart if non-default Port option is
  incorrectly put after a non-default ListenAddress

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  I have a system where the default listening port is changed for sshd,
  done at the bottom of my sshd_config.  I recently changed the
  ListenAddress from its default (unset, which listens on all
  interfaces) to bind to a specific IP.  The resulting relevant snippet
  of my sshd_config was:

  ListenAddress my_ip_here
  Port 12345

  I then restarted ssh with /etc/init.d/ssh restart and found that ssh
  was not listening.

  Re-reading the manpage, I see this:

  ListenAddress
   Specifies the local addresses sshd(8) should listen on.  The fol‐
   lowing forms may be used:

 ListenAddress host|IPv4_addr|IPv6_addr
 ListenAddress host|IPv4_addr:port
 ListenAddress [host|IPv6_addr]:port

   If port is not specified, sshd will listen on the address and all
   prior Port options specified.  The default is to listen on all
   local addresses.  Multiple ListenAddress options are permitted.
   Additionally, any Port options must precede this option for non-
   port qualified addresses.

  On a hunch, I remove the Port line and simply change my relevant
  config to:

  ListenAddress my_ip_here:12345

  sshd then restarted just fine.

  In looking at the logs, I see:

  Dec  1 11:40:26 jhart-laptop kernel: [1207947.954263] init: ssh main process 
(26655) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.954277] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.957687] init: ssh main process 
(26658) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.957703] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.961094] init: ssh main process 
(26661) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.961115] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.964835] init: ssh main process 
(26664) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.964852] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.968028] init: ssh main process 
(26667) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.968043] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.971004] init: ssh main process 
(26670) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.971021] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.974044] init: ssh main process 
(26673) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.974087] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.977853] init: ssh main process 
(26676) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.977868] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.980928] init: ssh main process 
(26679) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.980944] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.984059] init: ssh main process 
(26682) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.984075] init: ssh main process 
ended, respawning
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.987118] init: ssh main process 
(26685) terminated with status 255
  Dec  1 11:40:26 jhart-laptop kernel: [1207947.987132] init: ssh respawning 
too fast, stopped

  ProblemType: Bug
  DistroRelease: Ubuntu 

[Touch-packages] [Bug 1636395] Re: dnsmasq not working with OpenVPN

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

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

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

Title:
  dnsmasq not working with OpenVPN

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  I'm using OpenVPN configured with Network Manager. My VPN have a DNS
  server configured by OpenVPN and config pushed by it while connecting.
  This server is not registered by dnsmasq so domain names are not
  resolved but pinging by IP address works. When I test name resolving
  by pointing to DNS server (172.16.1.1) from VPN provider it's works.
  For example:

  $ host google.com 172.16.1.1
  Using domain server:
  Name: 172.16.1.1
  Address: 172.16.1.1#53
  Aliases: 

  google.com has address 172.217.0.174
  google.com has IPv6 address 2607:f8b0:400b:807::200e
  google.com mail is handled by 30 alt2.aspmx.l.google.com.
  google.com mail is handled by 20 alt1.aspmx.l.google.com.
  google.com mail is handled by 40 alt3.aspmx.l.google.com.
  google.com mail is handled by 10 aspmx.l.google.com.
  google.com mail is handled by 50 alt4.aspmx.l.google.com.

  But if I test without pointing DNS server is not working:

  $ host google.com
  ;; connection timed out; no servers could be reached

  My /etc/resolv.conf:
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.1.1

  To repair this bug I have to kill dnsmasq and it's automatically
  reloaded.

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

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


[Touch-packages] [Bug 1633643] Re: unnecessary dependency upon isc-dhcp-client

2016-10-25 Thread Mathieu Trudel-Lapierre
The changes were reverted.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  unnecessary dependency upon isc-dhcp-client

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  with xenial-updates, there is suddenly a dependency [isc-dhcp-client]
  not previously there.  please mark this as
  recommends/suggests/enhances instead of as a depends, as it is not
  critical to the core functionality of the software.  since ubuntu now
  defaults to installing recommends unless configured otherwise, this
  compromise accommodates both the unskilled users as well as those who
  know what they are doing and have disabled automatic installation of
  suggested packages.

  1] >lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2] >apt-cache policy initramfs-tools
  initramfs-tools:
Installed: 0.122ubuntu8.3
Candidate: 0.122ubuntu8.3
Version table:
   *** 0.122ubuntu8.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.122ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  3] i expected to not be forced to install unnecessary packages
  4] i was forced to

  thanks

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

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


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

2016-10-25 Thread Matthew General
I am also affected. Broken both on a fresh install and an upgrade, dns
for things behind the vpn do not resolve.

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

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

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Incomplete

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

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

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

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


[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

2016-10-25 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Released
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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


[Touch-packages] [Bug 1636530] [NEW] initramfs config script mixes IPv4 and IPv6 data in the net-$iface.conf file

2016-10-25 Thread Mathieu Trudel-Lapierre
Public bug reported:

[Impact]
To support the previous behavior with ipconfig, dhclient now ships a config 
script for the initramfs which is meant to write out /run/net-(interface 
name).conf, which may be read by later initramfs scripts to configure a remote 
rootfs or other networked features. Data for both IPv4 and IPv6 are written out 
to the same file, which can lead to confusion and incorrect behavior.

[Test case]
1) Boot a system with an iscsi rootfs on a network where no DHCP server answers.

Current behavior:
dhclient -6 results may be written out to the /run/net-$iface.conf file which 
would cause the boot process to continue, thinking it's done.

Expected behavior:
boot should only continue once a network is found (through DHCP, BOOTP, etc.).

[Regression potential]
This changes is not expected to cause any kind of regression. Use of isc-dhcp 
has been reverted in initramfs-tools, and as such the affected code paths would 
not be run.

** Affects: isc-dhcp (Ubuntu)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: isc-dhcp (Ubuntu Xenial)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: Triaged

** Affects: isc-dhcp (Ubuntu Yakkety)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: Triaged

** Affects: isc-dhcp (Ubuntu Zesty)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Also affects: isc-dhcp (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: isc-dhcp (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: isc-dhcp (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: isc-dhcp (Ubuntu Yakkety)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: isc-dhcp (Ubuntu Zesty)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  initramfs config script mixes IPv4 and IPv6 data in the
  net-$iface.conf file

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Xenial:
  Triaged
Status in isc-dhcp source package in Yakkety:
  Triaged
Status in isc-dhcp source package in Zesty:
  In Progress

Bug description:
  [Impact]
  To support the previous behavior with ipconfig, dhclient now ships a config 
script for the initramfs which is meant to write out /run/net-(interface 
name).conf, which may be read by later initramfs scripts to configure a remote 
rootfs or other networked features. Data for both IPv4 and IPv6 are written out 
to the same file, which can lead to confusion and incorrect behavior.

  [Test case]
  1) Boot a system with an iscsi rootfs on a network where no DHCP server 
answers.

  Current behavior:
  dhclient -6 results may be written out to the /run/net-$iface.conf file which 
would cause the boot process to continue, thinking it's done.

  Expected behavior:
  boot should only continue once a network is found (through DHCP, BOOTP, etc.).

  [Regression potential]
  This changes is not expected to cause any kind of regression. Use of isc-dhcp 
has been reverted in initramfs-tools, and as such the affected code paths would 
not be run.

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

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


[Touch-packages] [Bug 1636469] [NEW] software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
Public bug reported:

miked@free-zesty:~$ lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
miked@free-zesty:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
Codename:   zesty
miked@free-zesty:~$ 

miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
sudo: unable to resolve host free-zesty: Resource temporarily unavailable
software-properties-gtk:
  Installed: 0.96.24.7
  Candidate: 0.96.24.7
  Version table:
 *** 0.96.24.7 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
100 /var/lib/dpkg/status
miked@free-zesty:~$ 

I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
A crash happened instead.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: software-properties-gtk 0.96.24.7
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 25 03:28:13 2016
InstallationDate: Installed on 2016-04-03 (205 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  New

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
When I start Software Updater, I get "The software is up to date." Dialog Box.
When I click on the "Settings" Button.
It Crashes, instead of opening the Settings for me. 

** Attachment added: "ScreenShot of Button to click on to get reproduceable 
Crash"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1636469/+attachment/4766916/+files/Screenshot%20from%202016-10-25%2004-06-22.png

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636473] [NEW] random cursor jumps when clicking on dell xps 13

2016-10-25 Thread s.illes79
Public bug reported:

1 out of 20-40 clicks on the touch pad results in a pointer jump and a
"random" click.

Hard to reproduce, but mostly happens when I use my middle finger to
move the cursor and click with index finger. Sometimes the double touch
of middle/index finger is interpreted as mouse move, the jump is more or
less the same distance as if i had moved the index to the middle finger
position.

Cheers

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Tue Oct 25 22:04:10 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:0704]
InstallationDate: Installed on 2016-09-08 (46 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.4
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
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.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
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: Sat Oct 22 20:20:44 2016
xserver.configfile: default
xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5193 
 vendor SHP
xserver.version: 2:1.18.4-0ubuntu0.1

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

Title:
  random cursor jumps when clicking on dell xps 13

Status in xorg package in Ubuntu:
  New

Bug description:
  1 out of 20-40 clicks on the touch pad results in a pointer jump and a
  "random" click.

  Hard to reproduce, but mostly happens when I use my middle finger to
  move the cursor and click with index finger. Sometimes the double
  touch of middle/index finger is interpreted as mouse move, the jump is
  more or less the same distance as if i had moved the index to the
  middle finger position.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Oct 25 22:04:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  InstallationDate: Installed on 2016-09-08 (46 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
gksudo gedit /usr/share/python-apt/templates/Ubuntu.info

miked@free-zesty:~$ gksudo gedit /usr/share/python-
apt/templates/Ubuntu.info

It just sits there, and does nothing, but the cursor flashes.


** Attachment added: "Screenshot of my computer doing what looks like nothing 
but Flashing cursor."
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1636469/+attachment/4766949/+files/Screenshot%20from%202016-10-25%2004-31-22.png

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
miked@free-zesty:~$ sudo software-properties-gtk
sudo: unable to resolve host free-zesty: Resource temporarily unavailable
[sudo] password for miked: 
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or 
directory
Unable to init server: Could not connect: Connection refused
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or 
directory
Unable to init server: Could not connect: Connection refused
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 101, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
self.reload_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
599, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in 
get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/zesty
miked@free-zesty:~$ 

miked@free-zesty:~$ sudo nano /usr/share/python-apt/templates/Ubuntu.info
nano worked.

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636506] [NEW] formatValue shouldn't be blanked in Menus.SliderMenu

2016-10-25 Thread Jonas G. Drange
Public bug reported:

Repro:
Use Menus.SliderMenu

What happens:
Can't set formatValue

What should happen:
A property should be aliasd' to the internal slider's formatValue.

Usecase:
Any, it is no longer the case that formatValue is deprecated (according to [1]).

[1]
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.Slider
/#formatValue-method

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

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

Title:
  formatValue shouldn't be blanked in Menus.SliderMenu

Status in ubuntu-settings-components package in Ubuntu:
  New

Bug description:
  Repro:
  Use Menus.SliderMenu

  What happens:
  Can't set formatValue

  What should happen:
  A property should be aliasd' to the internal slider's formatValue.

  Usecase:
  Any, it is no longer the case that formatValue is deprecated (according to 
[1]).

  [1]
  https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.Slider
  /#formatValue-method

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

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


[Touch-packages] [Bug 1602828] [NEW] Fingerprint enrollment UI should ask user to “Tap” not “Swipe”

2016-10-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Swipe is misleading.

** Affects: ubuntu-settings-components (Ubuntu)
 Importance: Undecided
 Assignee: Jonas G. Drange (jonas-drange)
 Status: Fix Committed

-- 
Fingerprint enrollment UI should ask user to “Tap” not “Swipe”
https://bugs.launchpad.net/bugs/1602828
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu.

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


[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

2016-10-25 Thread Nikita Yerenkov-Scott
So this update should be backported in to prior releases as I can
confirm that it does now fix the problem, I think that it didn't work
for me immediately because of a local issue on my system caused by
something else earlier.

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in accountsservice source package in Xenial:
  Triaged
Status in gnome-control-center source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Triaged

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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


[Touch-packages] [Bug 1553353] Re: tail'ing a file in a script session hangs

2016-10-25 Thread Bug Watch Updater
** Changed in: util-linux (Debian)
   Status: Confirmed => Fix Released

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

Title:
  tail'ing a file in a script session hangs

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:

  1) Start script session (same issue when script is saving to /dev/null)
  script # or: script /dev/null
  2) Tail a file
  tailf /var/log/syslog
  3) Press "Enter" 2 times
  4) Notice the script process taking 100% CPU

  This regression was introduced upstream by this commit:
  https://git.kernel.org/cgit/utils/util-linux/util-
  linux.git/commit/?id=54c6611d6f7b73609a5331f4d0bcf63c4af6429e

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy util-linux bsdutils coreutils
  util-linux:
    Installed: 2.27.1-4ubuntu1
    Candidate: 2.27.1-4ubuntu1
    Version table:
   *** 2.27.1-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.27.1-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  bsdutils:
    Installed: 1:2.27.1-4ubuntu1
    Candidate: 1:2.27.1-4ubuntu1
    Version table:
   *** 1:2.27.1-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2.27.1-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  coreutils:
    Installed: 8.25-2ubuntu2
    Candidate: 8.25-2ubuntu2
    Version table:
   *** 8.25-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  4 15:14:15 2016
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1446729] Re: youtube videos should pause when tab moved to background

2016-10-25 Thread Chloe Johnson
I back the other one, if I wanted my yputube videos to pause while doing
stuff Id use the youtube app without keeping it running in background
using ubuntu tweak tool.

Know thats another option though, if you want to listen to videos of any
forum you can keep apps awfrom sleeping using ubuntu tweak tool.

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

Title:
  youtube videos should pause when tab moved to background

Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  both krillin and vivid have this issue:

  1) open browser
  2) open video in youtube.com and start playing it
  3) swipe up from bottom and select an existing tab or create a new tab

  Expected result:
  - the video in the background should pause and the new tab should be displayed

  Actual result:
  - the video keeps playing in the background even after the new tab is loaded

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

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


[Touch-packages] [Bug 1602828] Re: Fingerprint enrollment UI should ask user to “Tap” not “Swipe”

2016-10-25 Thread Jonas G. Drange
** Project changed: ubuntu-settings-components => ubuntu-settings-
components (Ubuntu)

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Fingerprint enrollment UI should ask user to “Tap” not “Swipe”

Status in ubuntu-settings-components package in Ubuntu:
  Fix Released

Bug description:
  Swipe is misleading.

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

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


[Touch-packages] [Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image

2016-10-25 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-touch-session -
0.108+16.10.20161014-0ubuntu1

---
ubuntu-touch-session (0.108+16.10.20161014-0ubuntu1) yakkety; urgency=medium

  [ Alexandros Frantzis ]
  * Keep the display on during boot (LP: #1623853) (LP: #1623853)

 -- Łukasz Zemczak   Fri, 14 Oct 2016
07:48:51 +

** Changed in: ubuntu-touch-session (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Device appears to be off after updating to 15Sept2016's rc-proposed
  image

Status in Canonical System Image:
  In Progress
Status in repowerd package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released

Bug description:
  Krillin, rc-proposed/bq-aquaris.en r429

  Description:
  Many people, myself included, are reporting that their devices seemed to have 
turned off after upgrading to today's rc-proposed

  In my case it was an updated from r428 to r429.
  The device rebooted to install the upgrade, then at one point I noticed the 
display was off and not responding to PwrKey.
  I had for force shutdown via press-holding PwrKey.

  A few community members reported the same problem on Arale (MX4) and
  Freiza (M10), so it seems to be device-independent.

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread dino99
Glad you finally found how to do it !!!
As its not a bug per se, but an unknowledged basic skill, this report is closed.

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

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
Thanks Dino99

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

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636503] [NEW] recovery mode gets borked after some time out

2016-10-25 Thread mike
Public bug reported:

(Linux mint 18 / Xenial)

after booting in recovery mode from grub.
If you just wait 30-60seconds, a new stream of messages appear and something 
gets messed up, you can't use recovery mode any more, you have to do a hard 
reboot.

You don't need to do something in particular for this to happen, simply
some time out occurs.

---

more precisely, one of the messages say(copied manually):

"[FAILED] Failed to start Console System on Startup logging.
see 'systemctl status console-kit-log-system-start.service' for more details.

It seams, it tries to launch a second recovery mode on top of the
previous one after the error.



I confirm, this is happening on both my PC linux mint 18 64bits, laptop
linux mint 18 32bits and some one else from a forum on a ThinkPad X201
with Mint 18 KDE 64-bit.

On my systems, both are fully up to date, 32 and 64 bit. Kernels don't
seam to change anything.

systemd version 229-4ubuntu11

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

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

Title:
  recovery mode gets borked after some time out

Status in systemd package in Ubuntu:
  New

Bug description:
  (Linux mint 18 / Xenial)

  after booting in recovery mode from grub.
  If you just wait 30-60seconds, a new stream of messages appear and something 
gets messed up, you can't use recovery mode any more, you have to do a hard 
reboot.

  You don't need to do something in particular for this to happen,
  simply some time out occurs.

  ---

  more precisely, one of the messages say(copied manually):

  "[FAILED] Failed to start Console System on Startup logging.
  see 'systemctl status console-kit-log-system-start.service' for more details.

  It seams, it tries to launch a second recovery mode on top of the
  previous one after the error.

  

  I confirm, this is happening on both my PC linux mint 18 64bits,
  laptop linux mint 18 32bits and some one else from a forum on a
  ThinkPad X201 with Mint 18 KDE 64-bit.

  On my systems, both are fully up to date, 32 and 64 bit. Kernels don't
  seam to change anything.

  systemd version 229-4ubuntu11

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

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


[Touch-packages] [Bug 1619720] Re: Unity8 sometimes crashes after Bluetooth reconnect

2016-10-25 Thread pedaliero2012
Hi,
unity crashes When I try to log on
Especially when the mouse is in motion and the login screen is not yet visible


rc-proposed
Bq M10 FHD
Logitech M535 Bluetooth Mouse + Logitech K480 Bluetooth Keyboard

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

Title:
  Unity8 sometimes crashes after Bluetooth reconnect

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - In System Settings, pair a Bluetooth keyboard and mouse.
  - Wait some minutes so keyboard and mouse suspend.
  - Reboot the device.
  - Start typing on the password prompt and move the mouse.

  Expected result.
  - User can log in.

  Actual result.
  - Unity8 crashes.

  It's not an accurate test case but has happened at least three times
  in similar scenarios which involve waking up the keyboard (or mouse?).

  current build number: 180
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en

  With silo 37.

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread dino99
Be sure that  /usr/share/python-apt/templates/Ubuntu.info has been
upgraded with the zesty blocks

https://ubuntuforums.org/showthread.php?t=2227121

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

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
It's read only.
Do I have to login to root to fix it.

miked@free-zesty:~$ sudo gedit /usr/share/python-apt/templates/Ubuntu.info
sudo: unable to resolve host free-zesty: Resource temporarily unavailable
[sudo] password for miked: 
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or 
directory
Unable to init server: Could not connect: Connection refused

(gedit:21423): Gtk-WARNING **: cannot open display: :0
miked@free-zesty:~$

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
gksudo gedit /usr/share/python-apt/templates/Ubuntu.info
does not work on my computer.
I can click and open the file.
This is a better link to the fix.
https://wiki.ubuntu.com/U+1/tester-wiki

I have never had to do this before, so it seems like a Regression to me.

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
That Fixed it.

** Attachment added: "Sacreenshot of the Window that should of came up the 
first time."
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1636469/+attachment/4766955/+files/Screenshot%20from%202016-10-25%2005-03-27.png

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  software-properties-gtk:
Installed: 0.96.24.7
Candidate: 0.96.24.7
Version table:
   *** 0.96.24.7 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status
  miked@free-zesty:~$ 

  I expected to open the Software & Updates, (under System Settings, on Right 
corner drop-down menu, I can't tell you the name of the drop-down menu, because 
my screen does not display right.), by clicking on Icon.
  A crash happened instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 25 03:28:13 2016
  InstallationDate: Installed on 2016-04-03 (205 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to zesty on 2016-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1636469] Re: software-properties-gtk crashes, not working right on click

2016-10-25 Thread miked
Go to:
https://wiki.ubuntu.com/U%2B1/common-problems#Software-Properties-Gtk_doesn.27t_work

If Read-Only(gksu or gksudo does not work, you can use "nano" to edit it.)
miked@free-zesty:~$ sudo nano /usr/share/python-apt/templates/Ubuntu.info
Highlight, Copy, and Paste with Mouse, into Terminal.(after 
name@computername:~$)

"Software-Properties-Gtk doesn't work"

After running the above command, especially very early in the
development cycle could stop Software & Updates (software-properties-
gtk) from running. To solve the problem, insert the following text in
/usr/share/python-apt/templates/Ubuntu.info:

Suite: zesty
RepositoryType: deb
BaseURI: http://ports.ubuntu.com/ubuntu-ports/
MatchURI: ports.ubuntu.com/ubuntu-ports
BaseURI-amd64: http://archive.ubuntu.com/ubuntu
MatchURI-amd64: archive.ubuntu.com/ubuntu
BaseURI-i386: http://archive.ubuntu.com/ubuntu
MatchURI-i386: archive.ubuntu.com/ubuntu
MirrorsFile-amd64: Ubuntu.mirrors
MirrorsFile-i386: Ubuntu.mirrors
Description: Ubuntu 17.04 'zesty zapus'
Component: main
CompDescription: Officially supported
CompDescriptionLong: Canonical-supported free and open-source software
Component: universe
CompDescription: Community-maintained
CompDescriptionLong: Community-maintained free and open-source software
Component: restricted
CompDescription: Non-free drivers
CompDescriptionLong: Proprietary drivers for devices
Component: multiverse
ParentComponent: universe
CompDescription: Restricted software
CompDescriptionLong: Software restricted by copyright or legal issues

Suite: zesty
ParentSuite: zesty
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Ubuntu 17.04 'zesty zapus'

Suite: zesty
RepositoryType: deb
MatchName: .*
BaseURI: cdrom:\[Ubuntu.*16.
MatchURI: cdrom:\[Ubuntu.*16.10
Description: Cdrom with Ubuntu 17.04 'zesty zapus'
Available: False
Component: main
CompDescription: Officially supported
Component: restricted
CompDescription: Restricted copyright

Suite: zesty
Official: false
RepositoryType: deb
BaseURI: http://archive.canonical.com
MatchURI: archive.canonical.com
Description: Canonical Partners
Component: partner
CompDescription: Software packaged by Canonical for their partners
CompDescriptionLong: This software is not part of Ubuntu.

Suite: zesty
Official: false
RepositoryType: deb
BaseURI: http://extras.ubuntu.com
MatchURI: extras.ubuntu.com
Description: Independent
Component: main
CompDescription: Provided by third-party software developers
CompDescriptionLong: Software offered by third party developers.

Suite: zesty-security
ParentSuite: zesty
RepositoryType: deb
BaseURI: http://ports.ubuntu.com/ubuntu-ports/
MatchURI: ports.ubuntu.com/ubuntu-ports
BaseURI-amd64: http://security.ubuntu.com/ubuntu/
MatchURI-amd64: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI-i386: http://security.ubuntu.com/ubuntu/
MatchURI-i386: archive.ubuntu.com/ubuntu|security.ubuntu.com
Description: Important security updates

Suite: zesty-security
ParentSuite:zesty
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: 
archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports|security.ubuntu.com
Description: Important security updates

Suite: zesty-updates
ParentSuite: zesty
RepositoryType: deb
Description: Recommended updates

Suite:zesty-updates
ParentSuite: zesty
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Recommended updates

Suite: zesty-proposed
ParentSuite: zesty
RepositoryType: deb
Description: Pre-released updates

Suite: zesty-proposed
ParentSuite: zesty
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Pre-released updates

Suite: zesty-backports
ParentSuite: zesty
RepositoryType: deb
Description: Unsupported updates

Suite: zesty-backports
ParentSuite: zesty
RepositoryType: deb-src
BaseURI: http://archive.ubuntu.com/ubuntu/
MatchURI: archive.ubuntu.com/ubuntu|ports.ubuntu.com/ubuntu-ports
Description: Unsupported updates

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

Title:
  software-properties-gtk crashes, not working right on click

Status in software-properties package in Ubuntu:
  New

Bug description:
  miked@free-zesty:~$ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  miked@free-zesty:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty
  miked@free-zesty:~$ 

  miked@free-zesty:~$ sudo apt-cache policy software-properties-gtk
  sudo: unable to resolve host free-zesty: Resource temporarily unavailable
  

  1   2   >