date:20160519

** Branch linked: lp:~xnox/ubuntu-meta/lp1577833

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

Title:
  Support statement for packages within Ubuntu 16.04 LTS should have the
  5 Y statement

Status in Ubuntu on IBM z Systems:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  We detected following information

  Manuell Installation in Standard-Mode (not Expert Mode)with following
  selection: standard system utilities, OpenSSH server, Basic Ubuntu
  server for s390-tools:

  Following information are provided by the ubuntu-support-status tool.

  Supported until January 2017 (9m):
  libpfm4 s390-tools sysconfig-hardware 

  Supported until April 2019 (3y):
  discover discover-data libdiscover2 

  The assumption is, the 16.04 LTS will have 5 year support for each
  package within release/main

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

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

[Touch-packages] [Bug 1577833] Re: Support statement for packages within Ubuntu 16.04 LTS should have the 5 Y statement

2016-05-19 Thread Dimitri John Ledkov

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  Support statement for packages within Ubuntu 16.04 LTS should have the
  5 Y statement

Status in Ubuntu on IBM z Systems:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  We detected following information

  Manuell Installation in Standard-Mode (not Expert Mode)with following
  selection: standard system utilities, OpenSSH server, Basic Ubuntu
  server for s390-tools:

  Following information are provided by the ubuntu-support-status tool.

  Supported until January 2017 (9m):
  libpfm4 s390-tools sysconfig-hardware 

  Supported until April 2019 (3y):
  discover discover-data libdiscover2 

  The assumption is, the 16.04 LTS will have 5 year support for each
  package within release/main

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

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

Re: [Touch-packages] [Bug 1419637] Re: package bluez 4.101-0ubuntu13 failed to install/upgrade: unable to create `/lib/udev/hid2hci.dpkg-new' (while processing `./lib/udev/hid2hci'): Permission denied

2016-05-19 Thread Sanat Kumar Panda

Hi,

Thanks for this valuable information.

Thanks
ᐧ

On Thu, May 19, 2016 at 9:04 PM, Konrad Zapałowicz <
konrad.zapalow...@canonical.com> wrote:

> This is reported against an old version of Ubuntu and many things has
> changed since then. Because of that we won't fix this issue however if
> this behavior repeats on a modern version please fill a bug report
> against it and we will take it from there.
>
> ** Changed in: bluez (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1419637
>
> Title:
>   package bluez 4.101-0ubuntu13 failed to install/upgrade: unable to
>   create `/lib/udev/hid2hci.dpkg-new' (while processing
>   `./lib/udev/hid2hci'): Permission denied
>
> Status in bluez package in Ubuntu:
>   Invalid
>
> Bug description:
>   Can't install anything due broken Virtualbox package.
>   It's showing "cannot remove `/lib/udev/VBoxCreateUSBNode.sh': Permission
> denied" error.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.04
>   Package: bluez 4.101-0ubuntu13
>   ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
>   Uname: Linux 3.13.0-45-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.6
>   Architecture: amd64
>   Date: Mon Feb  9 13:18:33 2015
>   DuplicateSignature: package:bluez:4.101-0ubuntu13:unable to create
> `/lib/udev/hid2hci.dpkg-new' (while processing `./lib/udev/hid2hci'):
> Permission denied
>   ErrorMessage: unable to create `/lib/udev/hid2hci.dpkg-new' (while
> processing `./lib/udev/hid2hci'): Permission denied
>   InstallationDate: Installed on 2013-08-03 (554 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64
> (20130424)
>   InterestingModules: rfcomm bnep btusb bluetooth
>   MachineType: Dell Inc. Dell System Inspiron N4110
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic
> root=UUID=7a566367-a394-482f-b05c-8da185c3bb4e ro quiet splash vt.handoff=7
>   SourcePackage: bluez
>   Title: package bluez 4.101-0ubuntu13 failed to install/upgrade: unable
> to create `/lib/udev/hid2hci.dpkg-new' (while processing
> `./lib/udev/hid2hci'): Permission denied
>   UpgradeStatus: Upgraded to trusty on 2015-01-12 (27 days ago)
>   dmi.bios.date: 01/09/2012
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A10
>   dmi.board.name: 05TM8C
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA10:bd01/09/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1:
>   dmi.product.name: Dell System Inspiron N4110
>   dmi.sys.vendor: Dell Inc.
>   hciconfig:
>hci0:Type: BR/EDR  Bus: USB
> BD Address: 4C:EB:42:21:A9:89  ACL MTU: 310:10  SCO MTU: 64:8
> DOWN
> RX bytes:507 acl:0 sco:0 events:23 errors:0
> TX bytes:329 acl:0 sco:0 commands:22 errors:0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1419637/+subscriptions
>

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

Title:
  package bluez 4.101-0ubuntu13 failed to install/upgrade: unable to
  create `/lib/udev/hid2hci.dpkg-new' (while processing
  `./lib/udev/hid2hci'): Permission denied

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Can't install anything due broken Virtualbox package.
  It's showing "cannot remove `/lib/udev/VBoxCreateUSBNode.sh': Permission 
denied" error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Feb  9 13:18:33 2015
  DuplicateSignature: package:bluez:4.101-0ubuntu13:unable to create 
`/lib/udev/hid2hci.dpkg-new' (while processing `./lib/udev/hid2hci'): 
Permission denied
  ErrorMessage: unable to create `/lib/udev/hid2hci.dpkg-new' (while processing 
`./lib/udev/hid2hci'): Permission denied
  InstallationDate: Installed on 2013-08-03 (554 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Dell System Inspiron N4110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=7a566367-a394-482f-b05c-8da185c3bb4e ro quiet splash vt.handoff=7
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13 failed to install/upgrade: unable to 
create `/lib/udev/hid2hci.dpkg-new' (while processing `./lib/udev/hid2hci'): 
Permission denied
  UpgradeStatus: Upgraded to trusty on 2015-01-12 (27 days ago)
  dmi.bios.date: 01/09/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.boar

[Touch-packages] [Bug 1577833] [NEW] Support statement for packages within Ubuntu 16.04 LTS should have the 5 Y statement

You have been subscribed to a public bug:

We detected following information

Manuell Installation in Standard-Mode (not Expert Mode)with following
selection: standard system utilities, OpenSSH server, Basic Ubuntu
server for s390-tools:

Following information are provided by the ubuntu-support-status tool.

Supported until January 2017 (9m):
libpfm4 s390-tools sysconfig-hardware 

Supported until April 2019 (3y):
discover discover-data libdiscover2 

The assumption is, the 16.04 LTS will have 5 year support for each
package within release/main

** Affects: ubuntu-z-systems
 Importance: Undecided
 Status: New

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bot-comment bugnameltc-141010 severity-medium 
targetmilestone-inin1610
-- 
Support statement for packages within Ubuntu 16.04 LTS should have the 5 Y 
statement
https://bugs.launchpad.net/bugs/1577833
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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 1549507] Re: vim in xenial not compiled with python support

2016-05-19 Thread Olli Niemi

I just tried vim-nox (is that for "no X"?) and it seems Python 3 support
works there. I had to use the "let g:UltiSnipsUsePythonVersion = 3"
definition there because the autodetection did not work. For Powerline I
installed powerline and python3-powerline packages and used the
following configuration:

let powerlinecmd=substitute(system("which powerline"), '\n\+$', '', '')
if !empty(glob(powerlinecmd))
python3 from powerline.vim import setup as powerline_setup
python3 powerline_setup()
python3 del powerline_setup
endif

Also: vim-plug seems to be working in parallel mode with no
configuration needed. The default Python is still version 2 in Ubuntu so
version 3 needs to be defined manually.

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

Title:
  vim in xenial not compiled with python support

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  vim in xenial as of Feb 24, 2016 is missing python support. This has
  been present in all previous builds of vim at least since 14.04. For
  me, this makes the vundle-installed plugin ultisnips complain as
  follows:

  UltiSnips requires py >= 2.7 or py3
  Press ENTER or type command to continue

  I'm requesting that vim be modified to include python support

  Ubuntu xenial snapshot:
  vim --version |grep python
  +cryptv  +linebreak   -python  +viminfo
  +cscope  +lispindent  -python3 +vreplace

  Ubuntu 14.04
  vim --version |grep pyth
  +cryptv  +linebreak   +python  +viminfo
  +cscope  +lispindent  -python3 +vreplace
  Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim   
 -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl
-L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil 
-lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions

  
  Ubuntu Xenial vim version complete details

  root@ubuntu1604:/tmp # vim --version
  VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 11:55:21)
  Included patches: 1-963
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +farsi   +mouse_netterm   +syntax
  +arabic  +file_in_path+mouse_sgr   +tag_binary
  +autocmd +find_in_path-mouse_sysmouse  +tag_old_static
  -balloon_eval+float   +mouse_urxvt -tag_any_white
  -browse  +folding +mouse_xterm -tcl
  ++builtin_terms  -footer  +multi_byte  +terminfo
  +byte_offset +fork()  +multi_lang  +termresponse
  +cindent +gettext -mzscheme+textobjects
  -clientserver-hangul_input+netbeans_intg   +title
  -clipboard   +iconv   +path_extra  -toolbar
  +cmdline_compl   +insert_expand   -perl+user_commands
  +cmdline_hist+jumplist+persistent_undo +vertsplit
  +cmdline_info+keymap  +postscript  +virtualedit
  +comments+langmap +printer +visual
  +conceal +libcall +profile +visualextra
  +cryptv  +linebreak   -python  +viminfo
  +cscope  +lispindent  -python3 +vreplace
  +cursorbind  +listcmds+quickfix+wildignore
  +cursorshape +localmap+reltime +wildmenu
  +dialog_con  -lua +rightleft   +windows
  +diff+menu-ruby+writebackup
  +digraphs+mksession   +scrollbind  -X11
  -dnd +modify_fname+signs   -xfontset
  -ebcdic  +mouse   +smartindent -xim
  +emacs_tags  -mouseshape  -sniff   -xsmp
  +eval+mouse_dec   +startuptime -xterm_clipboard
  +ex_extra+mouse_gpm   +statusline  -xterm_save
  +extra_search-mouse_jsbterm   -sun_workshop-xpm
 system vimrc file: "$VIM/vimrc"
   user vimrc file: "$HOME/.vimrc"
   2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
  Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=1
  Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -o vim-lm -ltinfo -lnsl  -lselinux -lacl -lattr -lgpm 
-ldl

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vim 2:7.4.963-1ubuntu4
  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
  Date: Wed Feb 24 22:15:56 2016
  Ec2AMI: ami-ac3cdecc
  Ec2AMIManifest: (unknown)

[Touch-packages] [Bug 1583858] Re: I can't do apt update

2016-05-19 Thread Anders Trier Olesen

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

** This bug is no longer a duplicate of bug 1583862
   apt-get update hangs after hit/get
** This bug has been marked a duplicate of bug 1579712
   Refresh hangs indefinitely, appstreamcli using 100% CPU

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

Title:
  I can't do apt update

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  It stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 20 09:30:08 2016
  InstallationDate: Installed on 2016-04-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576870] Re: bridge-utils manpage contains incorrect max for portprio

This bug was fixed in the package bridge-utils - 1.5-9ubuntu2

---
bridge-utils (1.5-9ubuntu2) yakkety; urgency=medium

  * debian/ifupdown.sh:
- Handle bridge params which use port and value (LP: #1576876)
  * debian/bridge-utils-interface.5:
- Update max, default value for path cost (LP: #1576870)
- Update unsettable gcint value for newer kernels (LP: #1576858)

 -- Ryan Harper   Thu, 05 May 2016 10:38:12
-0500

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

Title:
  bridge-utils manpage contains incorrect max for portprio

Status in bridge-utils package in Ubuntu:
  Fix Released

Bug description:
  1. % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2. % apt-cache policy bridge-utils
  bridge-utils:
Installed: 1.5-9ubuntu1
Candidate: 1.5-9ubuntu1
Version table:
   *** 1.5-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3.  % brtctl setportprio br0 eth1 64; echo $?
  0

  4. # brctl setportprio br0 eth1 128 
  set port priority failed: Numerical result out of range

  The manpage (bridge-utils-interfaces) says that bridge_portprio has a
  default value of 128.  However, the default is infact 32.
  Additionally,  no value higher than 32 can be set.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bridge-utils 1.5-9ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Fri Apr 29 16:08:33 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-01-01 (119 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: bridge-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576876] Re: bridge-utils: /etc/network/if-pre-up.d/bridge doesn't handle multiple stanzas of bridge_portprio

This bug was fixed in the package bridge-utils - 1.5-9ubuntu2

---
bridge-utils (1.5-9ubuntu2) yakkety; urgency=medium

  * debian/ifupdown.sh:
- Handle bridge params which use port and value (LP: #1576876)
  * debian/bridge-utils-interface.5:
- Update max, default value for path cost (LP: #1576870)
- Update unsettable gcint value for newer kernels (LP: #1576858)

 -- Ryan Harper   Thu, 05 May 2016 10:38:12
-0500

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

Title:
  bridge-utils: /etc/network/if-pre-up.d/bridge doesn't handle multiple
  stanzas of bridge_portprio

Status in bridge-utils package in Ubuntu:
  Fix Released

Bug description:
  1. % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2. % apt-cache policy bridge-utils
  bridge-utils:
Installed: 1.5-9ubuntu1
Candidate: 1.5-9ubuntu1
Version table:
   *** 1.5-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3. with a bridge stanza like this:

  auto br0
  iface br0 inet static
  address 192.168.14.2/24
  bridge_ports eth1 eth2
  bridge_portprio eth1 28
  bridge_portprio eth2 16

  After ifup br0, /sys/class/net/br0/brif/eth2/priority should be 16.

  4.

  /etc/network/if-pre-up.d/bridge executes:

  brctl setportprio br0 eth1 28 eth2 16

  which succeeds in setting eth1 to 28, but does not apply a setting to
  eth2

  
  Instead, we need to iterate over the ports (in case there is more than one 
port per bridge)

  
  # diff -u bridge.orig bridge
  --- bridge.orig 2016-04-29 21:52:34.785204215 +
  +++ bridge  2016-04-29 21:51:47.237066594 +
  @@ -134,7 +134,11 @@
   
 if [ "$IF_BRIDGE_PORTPRIO" ]
 then
  -brctl setportprio $IFACE $IF_BRIDGE_PORTPRIO
  +echo "$IF_BRIDGE_PORTPRIO" | {
  +  while read PORT PRIO; do  
  +brctl setportprio $IFACE $PORT $PRIO
  +  done
  +}
 fi
   
 if [ "$IF_BRIDGE_STP" ]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bridge-utils 1.5-9ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Fri Apr 29 16:45:30 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-01-01 (119 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: bridge-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576858] Re: brctl provides no way to set gc_timer value of a bridge

This bug was fixed in the package bridge-utils - 1.5-9ubuntu2

---
bridge-utils (1.5-9ubuntu2) yakkety; urgency=medium

  * debian/ifupdown.sh:
- Handle bridge params which use port and value (LP: #1576876)
  * debian/bridge-utils-interface.5:
- Update max, default value for path cost (LP: #1576870)
- Update unsettable gcint value for newer kernels (LP: #1576858)

 -- Ryan Harper   Thu, 05 May 2016 10:38:12
-0500

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

Title:
  brctl provides no way to set gc_timer value of a bridge

Status in bridge-utils package in Ubuntu:
  Fix Released

Bug description:
  1.

  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy bridge-utils
  bridge-utils:
Installed: 1.5-9ubuntu1
Candidate: 1.5-9ubuntu1
Version table:
   *** 1.5-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. % brctl setgcint br0 2
  Should set the gc_timer value of a bridge, value printed out via brctl 
showstp br0

  % brctl showstp br0 | grep gc
   topology change timer 0.00 gc timer  
84.08

  4.  % brctl setgcint br0 2
  never heard of command [setgcint]
  Usage: brctl [commands]
  commands:
addbr   add bridge
delbr   delete bridge
addif   add interface to bridge
delif   delete interface from bridge
hairpin   {on|off}turn hairpin on/off
setageing set ageing time
setbridgeprio set bridge priority
setfd set bridge forward delay
sethello  set hello time
setmaxage set max message age
setpathcost set path cost
setportprio set port priority
show[  ]show a list of bridges
showmacsshow a list of mac addrs
showstp show bridge stp info
stp  {on|off}   turn stp on/off

  
  Checking source code of bridge-utils, there seems to be no code that lets one 
actually set this value, nor does it appear that the kernel ioctl interface 
allows for modifying gc_timer, (it appears to be a read-only field).

  This must mean the documentation included in bridge-utils
  (specifically in bridge-utils-interfaces manpage about including a
  bridge_gcint value in /etc/network/interfaces to control this is
  incorrect.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bridge-utils 1.5-9ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Fri Apr 29 15:53:52 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2016-01-01 (119 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: bridge-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1581106] Re: [yakkety regression] lightdm fails to install in a minimal environment

2016-05-19 Thread Robert Ancell

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

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

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

Title:
  [yakkety regression] lightdm fails to install in a minimal environment

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1581106] Re: [yakkety regression] lightdm fails to install in a minimal environment

** Branch linked: lp:lightdm

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

Title:
  [yakkety regression] lightdm fails to install in a minimal environment

Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1292990] Re: lightdm overrides dh_installinit in debian/rules and shouldn't

2016-05-19 Thread Robert Ancell

Based on Martins issue I've reverted this change and added a comment.

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

Title:
  lightdm overrides dh_installinit in debian/rules and shouldn't

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  The debian/rules for lightdm includes the following:

  override_dh_installinit:
  dh_installinit --no-start

  This appears to have been in place since the beginning of the
  package's history, with no reason given.  And the result of this
  override is that if you install lightdm on a running system, lightdm
  will not be automatically started at install time like it should be.

  Please drop this override from the package.

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

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

[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

2016-05-19 Thread Ubuntu Foundations Team Bug Bot

The attachment "upower-always-get-kbd-brightness.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Touch-packages] [Bug 1583883] Re: lightdm blocks login screen on non-english layout

2016-05-19 Thread Robert Ancell

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  lightdm blocks login screen on non-english layout

Status in unity package in Ubuntu:
  New

Bug description:
  Sometimes lightdm pops up after the sleep mode and proposes its own
  login screen without ability to change keyboard layout. How to fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 19 10:41:43 2016
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (41 days ago)

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

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

[Touch-packages] [Bug 1583862] Re: apt-get update hangs after hit/get

2016-05-19 Thread Robert Hooker

killing appstream and changing archives apparently fixes it according to
the reddit thread

** Package changed: apt (Ubuntu) => appstream (Ubuntu)

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

Title:
  apt-get update hangs after hit/get

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  After typing "sudo apt-get update" the following happens, but then it hangs:
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease  
 
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
 
  Hit:4 http://dl.google.com/linux/chrome/deb stable Release
 
  Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease   
 
  Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB] 
  Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease
 
  Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease   
 
  Fetched 281 kB in 0s (366 kB/s)

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt:
Installed: 1.2.10ubuntu1
Candidate: 1.2.10ubuntu1
Version table:
   *** 1.2.10ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 21:42:52 2016
  InstallationDate: Installed on 2016-04-27 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1559780] Re: package libpam-runtime 1.1.8-3.1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

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

Title:
  package libpam-runtime 1.1.8-3.1ubuntu3.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in pam package in Ubuntu:
  Expired

Bug description:
  I don't know what happened

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libpam-runtime 1.1.8-3.1ubuntu3.2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 20 18:31:34 2016
  DuplicateSignature: package:libpam-runtime:1.1.8-3.1ubuntu3.2:subprocess 
installed post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2012-06-18 (1371 days ago)
  InstallationMedia: Ubuntu  "Precise" - Build amd64 LIVE Binary 20120426-22:45
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: pam
  Title: package libpam-runtime 1.1.8-3.1ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to wily on 2015-12-12 (99 days ago)

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

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

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-05-19 Thread Arup

For now following Richard's advice I installed lsb by adding trusty
repository. After that I removed the trusty repo. So far no issues and
printer and printer utility working fine after driver install for my
Epson L800. This seems to be the only viable working solution till
Canonical fixes this.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

2016-05-19 Thread Daniel van Vugt

** Also affects: mir/0.23
   Importance: Undecided
   Status: New

** Changed in: mir/0.23
   Status: New => Triaged

** Changed in: mir/0.23
   Importance: Undecided => High

** Changed in: mir/0.23
Milestone: None => 0.23.1

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.23 series:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

2016-05-19 Thread kevin gunn

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Changed in: canonical-devices-system-image
Milestone: None => 12

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.23 series:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1583883] [NEW] lightdm blocks login screen on non-english layout

2016-05-19 Thread anatoly techtonik

Public bug reported:

Sometimes lightdm pops up after the sleep mode and proposes its own
login screen without ability to change keyboard layout. How to fix it?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 19 10:41:43 2016
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-07 (41 days ago)

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

Title:
  lightdm blocks login screen on non-english layout

Status in lightdm package in Ubuntu:
  New

Bug description:
  Sometimes lightdm pops up after the sleep mode and proposes its own
  login screen without ability to change keyboard layout. How to fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 19 10:41:43 2016
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (41 days ago)

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

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

[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.

2016-05-19 Thread Christopher M. Penalver

gouri, could you please provide the bugzilla number for the report you
filed?

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

Title:
Suspend to ram causes some glyphs to draw consistently wrong or even
appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.

Status in xorg package in Ubuntu:
Triaged

Bug description:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.

Cannot use nvidia proprietary driver as a workaround (does not work at
all).

# Context
Laptop, using "intel" (or "nouveau" ?) driver.
Expected: all glyphs rendered correctly.
Observed: some glyphs not rendered correctly

* reproducible: sometimes, eventually. Problem comes and go, severity
varies from one glyph (see
2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all
text on screen fully unreadable (see
2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png
)

* *some* glyphs are affected. For example, letter 'a' of a certain
size will be replaced by colored garbage at many places where it
appears (see
2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png
), but other 'a' with different size, italic, bold, etc will be
unaffected.

* in some applications (e.g. xfce whisker menu), some glyphs are
rendered correctly or not depending on the direction of mouse
hovering. See video
2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 .

* in menu of gtk application, some glyphs are "fixed" by opening the
menu, but not all. For example, in xfce4-terminal, letter A of
"Affichage" and its menu content as well as "Aide" is affected.
Opening "Affichage" menu does not fix anything. Opening "Aide" menu
fixes the "A" of "Aide". Changing window size reactivates the bug on
"A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-
bug.mp4 .

* text under icons on desktop is affected, but shadows are not. See

2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png

# Affected applications
* xfce whisker menu,
* xfce4-terminal (nealy all screenshots)
* firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png
2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png
),
* thunderbird (see
2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ),
* emacs (see
2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png
and subsequent ),
* superswitcher ( a gtk/gdk app)
* *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are
affected.

# Additional information
This looks like a cache corruption somewhere.
On IRC #pango, someone suggested a bug in Intel driver.
Running `xfce4-appearance-settings` and there changing any of:
* antialiasing enable/disable,
* hinting strength,
* subpixel alignment
* or dpi
immediately cures the bug (see
2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png
)

Setting back the exact same parameters immediately reactivates the bug
(see

2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png).

It is believed that keeping any new settings for a while will have the
bug reoccur.

It is not like bug 1536751. That one affects rendering quality of
*all* glyphs, at all times, depending on dpi. This is not the case
here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by
garbage or absent), not always.

---
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated
Graphics Controller [1043:177d]
Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d]
InstallationDate: Installed on 2016-02-03 (26 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
MachineType: ASUSTeK COMPUTER INC. N551JK
Package: xorg 1:7.7+13ubuntu1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed
root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet splash vt.handoff=7
ProcVersionSignatu

[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Description changed:

- In Dell or ThinkPad notebooks with keyboard backlight, the keybindings
- to control the keyboard backlight don't emit any event to the userland,
+ In Dell or ThinkPad (for these you need a kernel which includes fix for
+ lp:1574498) notebooks with keyboard backlight, the keybindings to
+ control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.
  
  Steps to reproduce:
-  0) ensure your keyboard backlight is on, and 
-  gdbus call --system --dest org.freedesktop.UPower \
-   --object-path /org/freedesktop/UPower/KbdBacklight \
-   --method org.freedesktop.UPower.KbdBacklight.GetBrightness
- returns a value != from 0. If not, just call the SetBrightness
- method with a positive value, to turn on the backlight.
-
- Now turn off the keyboard backlight (or set it to another level) 
- using the laptop keys, and run:
-  gsettings set org.gnome.desktop.session idle-delay 1
- to make things easier to test.
+  0) ensure your keyboard backlight is on, and
+  gdbus call --system --dest org.freedesktop.UPower \
+   --object-path /org/freedesktop/UPower/KbdBacklight \
+   --method org.freedesktop.UPower.KbdBacklight.GetBrightness
+ returns a value != from 0. If not, just call the SetBrightness
+ method with a positive value, to turn on the backlight.
  
-  2) Wait one second and the screensaver should start. Wait the screen to
- be turned off. If you just changed the brightness level at the step above,
- once the screen is turned off, also the keyboard backlight should be 
turned off too.
+ Now turn off the keyboard backlight (or set it to another level)
+ using the laptop keys, and run:
+  gsettings set org.gnome.desktop.session idle-delay 1
+ to make things easier to test.
  
-  3) Now press a key or move the mouse.
+  2) Wait one second and the screensaver should start. Wait the screen to
+ be turned off. If you just changed the brightness level at the step above,
+ once the screen is turned off, also the keyboard backlight should be 
turned off too.
+ 
+  3) Now press a key or move the mouse.
  
  Expected behavior:
  
-  4) The keyboard backlight should be set back to the previous level (so it 
should stay off
- or go back to the level you set before the idle timeout happened).
+  4) The keyboard backlight should be set back to the previous level (so it 
should stay off
+ or go back to the level you set before the idle timeout happened).
  
  Actual behavior:
  
-  5) The backlight is set to the level it had at point 0).
+  5) The backlight is set to the level it had at point 0).

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the l

[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Branch linked: lp:~3v1n0/unity-settings-daemon/kbd-brightness-update

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

** Patch added: "upower-always-get-kbd-brightness.debdiff"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+attachment/440/+files/upower-always-get-kbd-brightness.debdiff

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Touch-packages] [Bug 1583858] Re: I can't do apt update

2016-05-19 Thread no

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

** This bug has been marked a duplicate of bug 1583862
   apt-get update hangs after hit/get

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

Title:
  I can't do apt update

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  It stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 20 09:30:08 2016
  InstallationDate: Installed on 2016-04-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583862] Re: apt-get update hangs after hit/get

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

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

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

Title:
  apt-get update hangs after hit/get

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After typing "sudo apt-get update" the following happens, but then it hangs:
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease  
 
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
 
  Hit:4 http://dl.google.com/linux/chrome/deb stable Release
 
  Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease   
 
  Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB] 
  Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease
 
  Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease   
 
  Fetched 281 kB in 0s (366 kB/s)

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt:
Installed: 1.2.10ubuntu1
Candidate: 1.2.10ubuntu1
Version table:
   *** 1.2.10ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 21:42:52 2016
  InstallationDate: Installed on 2016-04-27 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583858] Re: I can't do apt update

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

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

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

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

Title:
  I can't do apt update

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  It stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 20 09:30:08 2016
  InstallationDate: Installed on 2016-04-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583861] [NEW] Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

Public bug reported:

In Dell or ThinkPad notebooks with keyboard backlight, the keybindings
to control the keyboard backlight don't emit any event to the userland,
about the state change, nor they request userland to change it (as it
happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
events), this causes unity/gnome-settings daemon not to restore the
proper backlight after idle.

Steps to reproduce:
 0) ensure your keyboard backlight is on, and 
 gdbus call --system --dest org.freedesktop.UPower \
  --object-path /org/freedesktop/UPower/KbdBacklight \
  --method org.freedesktop.UPower.KbdBacklight.GetBrightness
returns a value != from 0. If not, just call the SetBrightness
method with a positive value, to turn on the backlight.
   
Now turn off the keyboard backlight (or set it to another level) 
using the laptop keys, and run:
 gsettings set org.gnome.desktop.session idle-delay 1
to make things easier to test.

 2) Wait one second and the screensaver should start. Wait the screen to
be turned off. If you just changed the brightness level at the step above,
once the screen is turned off, also the keyboard backlight should be turned 
off too.

 3) Now press a key or move the mouse.

Expected behavior:

 4) The keyboard backlight should be set back to the previous level (so it 
should stay off
or go back to the level you set before the idle timeout happened).

Actual behavior:

 5) The backlight is set to the level it had at point 0).

** Affects: dell-sputnik
 Importance: Undecided
 Status: New

** Affects: upower
 Importance: Unknown
 Status: Unknown

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Medium
 Status: New

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

** Affects: upower (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

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

** Also affects: upower via
   https://bugs.freedesktop.org/show_bug.cgi?id=95457
   Importance: Unknown
   Status: Unknown

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: unity-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Summary changed:

- Keyboard backlight isn't properly reset after idle on systems with hardwired 
configuration
+ Keyboard backlight isn't properly restored after idle on systems with 
hardwired configuration

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  In Dell or ThinkPad notebooks with keyboard backlight, the keybindings
  to control the keyboard backlight don't emit any event to the
  userland, about the state change, nor they request userland to change
  it (as it happens in other models which emits
  KEY_KBDILLUM{UP,DOWN,TOGGLE} events), this causes unity/gnome-settings
  daemon not to restore the proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and 
   gdbus call --system --dest org.freedesktop.UPower \
--object-path /org/freedesktop/UPower/KbdBacklight \
--method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.
 
  Now turn off the keyboard backlight (or set it to another level) 
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyb

[Touch-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

I've moved the part related to idle backlight reset to bug #1583861

** No longer affects: upower (Ubuntu)

** No longer affects: upower (Ubuntu Xenial)

** No longer affects: upower

** Patch removed: "upower-always-get-kbd-brightness.debdiff"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+attachment/4665009/+files/upower-always-get-kbd-brightness.debdiff

** Patch removed: "0001-Fixed-dell-laptop-keyboard-backlight.patch"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+attachment/4640489/+files/0001-Fixed-dell-laptop-keyboard-backlight.patch

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Touch-packages] [Bug 1583862] [NEW] apt-get update hangs after hit/get

2016-05-19 Thread no

Public bug reported:

After typing "sudo apt-get update" the following happens, but then it hangs:
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease   
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]   
Hit:4 http://dl.google.com/linux/chrome/deb stable Release 
Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease
Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB] 
Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease 
Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease
Fetched 281 kB in 0s (366 kB/s)

Description:Ubuntu 16.04 LTS
Release:16.04

apt:
  Installed: 1.2.10ubuntu1
  Candidate: 1.2.10ubuntu1
  Version table:
 *** 1.2.10ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.10ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 19 21:42:52 2016
InstallationDate: Installed on 2016-04-27 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  apt-get update hangs after hit/get

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After typing "sudo apt-get update" the following happens, but then it hangs:
  Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease  
 
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]  
 
  Hit:4 http://dl.google.com/linux/chrome/deb stable Release
 
  Hit:5 http://apt.postgresql.org/pub/repos/apt xenial-pgdg InRelease   
 
  Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 
kB] 
  Hit:9 http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu xenial InRelease
 
  Hit:10 https://deb.nodesource.com/node_6.x xenial InRelease   
 
  Fetched 281 kB in 0s (366 kB/s)

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt:
Installed: 1.2.10ubuntu1
Candidate: 1.2.10ubuntu1
Version table:
   *** 1.2.10ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 21:42:52 2016
  InstallationDate: Installed on 2016-04-27 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1534501] Re: dnsmasq error logs fill up storage drive memory

2016-05-19 Thread Steve Langasek

This appears to be a conflict between network-manager's integration with
dnsmasq-base, and the dnsmasq package.

If there isn't a specific reason for the dnsmasq package to be installed
on your system, the straightforward workaround is to remove dnsmasq with
'apt purge dnsmasq'.

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

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

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

Title:
  dnsmasq error logs fill up storage drive memory

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid
Status in rsyslog package in Ubuntu:
  Invalid

Bug description:
  snippet of logs.

  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.397836] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.407691] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket 
for 127.0.1.1: Address already in use
  Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq exited with 
error: Network access problem (address in use; permissions; etc) (2)
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
child quit unexpectedly; refreshing DNS
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: starting 
dnsmasq...
  Jan 15 00:28:24 localhost NetworkManager[1211]:   dnsmasq not available 
on the bus, can't update servers.
  Jan 15 00:28:24 localhost NetworkManager[1211]:  [1452846504.419365] 
[dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: 
Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such 
name
  Jan 15 00:28:24 localhost NetworkManager[1211]:   DNS: plugin dnsmasq 
update failed
  Jan 15 00:28:24 localhost NetworkManager[1211]:   Writing DNS 
information to /sbin/resolvconf
  Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create 
listening socket for 127.

[Touch-packages] [Bug 1583858] [NEW] I can't do apt update

2016-05-19 Thread 賴家亨

Public bug reported:

It stuck.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.10ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 20 09:30:08 2016
InstallationDate: Installed on 2016-04-22 (27 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  I can't do apt update

Status in apt package in Ubuntu:
  New

Bug description:
  It stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.10ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 20 09:30:08 2016
  InstallationDate: Installed on 2016-04-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices

2016-05-19 Thread Rolf Leggewie

@All, please let us know what your current status with regards to this
ticket. Are you still affected?

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

Title:
  bluetooth-wizard doesn't find any devices

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  I have just upgrade to Quantal from Precise.
  I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and 
mouse. They worked without problems before the upgrade, but now they don't. I 
removed them and tried to add them again, but the bluetooth-wizard is stuck 
searching for devices, and doesn't find any.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-bluetooth 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 11:45:37 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago)

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

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

[Touch-packages] [Bug 1567448] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: a tentar sobre-escrever '/usr/include/i386-linux-gnu/zconf.h', que também está no pacote lib32z1-

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

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

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

Title:
  package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: a
  tentar sobre-escrever '/usr/include/i386-linux-gnu/zconf.h', que
  também está no pacote lib32z1-dev 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  the title say everything

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 10:52:50 2016
  ErrorMessage: a tentar sobre-escrever '/usr/include/i386-linux-gnu/zconf.h', 
que também está no pacote lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2016-04-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: zlib
  Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: a 
tentar sobre-escrever '/usr/include/i386-linux-gnu/zconf.h', que também está no 
pacote lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices

2016-05-19 Thread Rolf Leggewie

Konrad, that's premature.  This problem was reported for example against
trusty which until very recently was the latest LTS.  Please stop
closing tickets just because they are old.  You can always ask if people
are still affected by this problem and then close the ticket if there is
no response.

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

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

Title:
  bluetooth-wizard doesn't find any devices

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  I have just upgrade to Quantal from Precise.
  I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and 
mouse. They worked without problems before the upgrade, but now they don't. I 
removed them and tried to add them again, but the bluetooth-wizard is stuck 
searching for devices, and doesn't find any.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-bluetooth 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 11:45:37 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago)

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

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

[Touch-packages] [Bug 1583816] Re: package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to '/usr/incl

2016-05-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Invalid

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

Title:
  package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to
  install/upgrade: cannot copy extracted data for
  './usr/include/c++/4.8/bits/unordered_set.h' to
  '/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end
  of file or stream

Status in gcc-4.8 package in Ubuntu:
  Invalid

Bug description:
  flashplayer is anytime do not connected, so browser is broken and
  closed the window.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-85.129-lowlatency 3.13.11-ckt36
  Uname: Linux 3.13.0-85-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Thu May 19 23:45:06 2016
  DuplicateSignature: package:libstdc++-4.8-dev:4.8.4-2ubuntu1~14.04.1:cannot 
copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2016-04-15 (34 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: gcc-4.8
  Title: package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1565265] Re: Wifi disabled after resume from suspend on Dell Latitude E7450

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wifi disabled after resume from suspend on Dell Latitude E7450

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  New

Bug description:
  Steps to reproduce:
  1) Connect to network via wifi
  2) Suspend your notebook
  3) Resume from suspend - wifi will be disabled and you have to turn wifi 
manually

  HW: Dell Latitude E7450

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  network-manager:
Instalovaná verze: 1.0.4-0ubuntu10
Kandidát:  1.0.4-0ubuntu10
Tabulka verzí:
   *** 1.0.4-0ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  What happened: wifi is turned off after resume from suspend.
  Expected: wifi should be on after resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.370
  CurrentDesktop: Unity
  Date: Sat Apr  2 12:05:05 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH 
   Petrikovi   fc08f65c-260b-43b9-ae5d-df784e87ffd2  802-11-wireless  
1459598679  So 2. duben 2016, 12:04:39 UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  -- -- 
 
   Wired connection 1  62835f6a-985f-4f05-afa3-e0fe1f31de93  802-3-ethernet   
1459598635  So 2. duben 2016, 12:03:55 UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
   wlp2s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 990776] Re: USB audio device (Audioengine AW1) detected but when selected does not work

2016-05-19 Thread Juancho

I confirm this bug is still present on an up to date kubuntu 16.04.

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

Title:
  USB audio device (Audioengine AW1) detected but when selected does not
  work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The Audioengine device shows up in Sound Settings but when it is
  selected, the signal continues to run through the default
  speakers/headphones.

  The device worked fine in 11.10. I've upgraded 'over the air' to 12.04
  LTS.

  aplay -l:
  List of PLAYBACK Hardware Devices **
  card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
  card 1: AW1 [Audioengine AW1], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  lsusb (with Audioengine device):
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 004: ID 046d:c05a Logitech, Inc. Optical Mouse M90
  Bus 002 Device 004: ID 08bb:2704 Texas Instruments Japan

  lsusb (without Audioengine device):
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 004: ID 046d:c05a Logitech, Inc. Optical Mouse M90

  
  2012-04-28 22:55:08 (124 KB/s) - `alsa-info.sh' saved [27247]

  ALSA Information Script v 0.4.60
  

  This script visits the following commands/files to collect diagnostic
  information about your ALSA installation and sound related hardware.

dmesg
lspci
lsmod
aplay
amixer
alsactl
/proc/asound/
/sys/class/sound/
~/.asoundrc (etc.)

  The information is located at http://www.alsa-
  project.org/db/?f=8fcbb2056f939b60022b48910ee50772f31b9875

  
  sudo lspci -v:
  00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express Memory Controller Hub (rev 03)
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=09 
Kernel driver in use: agpgart-intel

  00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at dc10 (32-bit, non-prefetchable) [size=512K]
I/O ports at 1800 [size=8]
Memory at c000 (32-bit, prefetchable) [size=256M]
Memory at dc20 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at  [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel driver in use: i915
Kernel modules: intelfb, i915

  00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0
Memory at dc18 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2

  00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition 
Audio Controller (rev 02)
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at dc24 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel

  00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: d600-d7ff
Prefetchable memory behind bridge: d000-d1ff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Sony Corporation Device 8212
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel

[Touch-packages] [Bug 990776] Re: USB audio device (Audioengine AW1) detected but when selected does not work

2016-05-19 Thread Juancho

And the reboot workaround doesn't work.

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

Title:
  USB audio device (Audioengine AW1) detected but when selected does not
  work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The Audioengine device shows up in Sound Settings but when it is
  selected, the signal continues to run through the default
  speakers/headphones.

  The device worked fine in 11.10. I've upgraded 'over the air' to 12.04
  LTS.

  aplay -l:
  List of PLAYBACK Hardware Devices **
  card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
  card 1: AW1 [Audioengine AW1], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  lsusb (with Audioengine device):
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 004: ID 046d:c05a Logitech, Inc. Optical Mouse M90
  Bus 002 Device 004: ID 08bb:2704 Texas Instruments Japan

  lsusb (without Audioengine device):
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 004: ID 046d:c05a Logitech, Inc. Optical Mouse M90

  
  2012-04-28 22:55:08 (124 KB/s) - `alsa-info.sh' saved [27247]

  ALSA Information Script v 0.4.60
  

  This script visits the following commands/files to collect diagnostic
  information about your ALSA installation and sound related hardware.

dmesg
lspci
lsmod
aplay
amixer
alsactl
/proc/asound/
/sys/class/sound/
~/.asoundrc (etc.)

  The information is located at http://www.alsa-
  project.org/db/?f=8fcbb2056f939b60022b48910ee50772f31b9875

  
  sudo lspci -v:
  00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express Memory Controller Hub (rev 03)
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=09 
Kernel driver in use: agpgart-intel

  00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at dc10 (32-bit, non-prefetchable) [size=512K]
I/O ports at 1800 [size=8]
Memory at c000 (32-bit, prefetchable) [size=256M]
Memory at dc20 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at  [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel driver in use: i915
Kernel modules: intelfb, i915

  00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0
Memory at dc18 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2

  00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition 
Audio Controller (rev 02)
Subsystem: Sony Corporation Device 8212
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at dc24 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd-hda-intel

  00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 
(rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: d600-d7ff
Prefetchable memory behind bridge: d000-d1ff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Sony Corporation Device 8212
Capabilities: [a0] Power Management version 2
Capabilities: [100] Virtual Channel
Capabilities: [180] R

[Touch-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted

2016-05-19 Thread Bug Watch Updater

** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Critical

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

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2016-05-19 Thread Chuck McManis

I've run both my systems monitor's through a full
idle->blank->sleep->wakeup cycle by setting the power managment settings
to do that, and with this patch they both have come back. The final step
will be to leave them overnight and verify I can wake them both up in
the morning. Will update when I've done that.

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2016-05-19 Thread Jan

** Also affects: xfce4-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583821] [NEW] Applications shuffling around on desktops after screen lock

2016-05-19 Thread Richard Merren

Public bug reported:

I use multiple desktops to organize open applications. Also, I am
currently using multiple monitors. If I arrange my applications (e.g.
Chrome on the laptop screen of desktop one, Geany on the attached
monitor on desktop 1, another chrome on the laptop screen of desktop 2,
another app on the attached monitor on desktop 2) and then lock the
screen, when I unlock all of the applications have moved around.
Sometimes they all move to desktop 1, sometimes they are resized and
half off the screen. But they are rarely on the same screen and desktop
that I left them on.

This is new behavior since the latest version upgrade. Previously,
applications stayed on the screens where I left them.

Some requested info:

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

apt-cache policy xorg
xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
 *** 1:7.7+13ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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: Thu May 19 17:17:20 2016
DistUpgraded: 2016-04-29 20:29:44,172 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
InstallationDate: Installed on 2014-12-03 (532 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 80H1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-30 (19 days ago)
dmi.bios.date: 09/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: B9CN12WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Edge 15
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Edge 15
dmi.modalias: 
dmi:bvnLENOVO:bvrB9CN12WW:bd09/28/2014:svnLENOVO:pn80H1:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
dmi.product.name: 80H1
dmi.product.version: Lenovo Edge 15
dmi.sys.vendor: LENOVO
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-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
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 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue May 17 10:15:01 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1103 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2

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

Title:
  Applications shuffling around on desktops after screen lock

Status in xorg package in Ubuntu:
  New

Bug description:
  I use multiple desktops to organize open applications. Also, I am
  currently using multiple monitors. If I arrange my applications (e.g.
  Chrome on the laptop screen of desktop one, Geany on the attached
  monitor on desktop 1, another chrome on the laptop screen of desktop
  2, another app on the attached monitor on desktop 2) and then lock the
  screen, when I unlock all of the applications have moved around.
  Sometimes they all move to desktop 1, sometimes they are resized and
  half off the screen. But they are rarely on the same screen and
  desktop that I left them on.

  This is new behavior since the latest version upgrade. Previously,
  applications stayed on the screens where I left them.

  Some requested info:

  $ lsb

[Touch-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

2016-05-19 Thread Matthias König

This is weird: I have reverted the changes I made according to #47 but
the bug is still fixed, even though you say that it's not yet in the
updates? Is there a logical explanation to this?

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in upower source package in Xenial:
  New

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Touch-packages] [Bug 1583816] Re: package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to '/usr/incl

2016-05-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to
  install/upgrade: cannot copy extracted data for
  './usr/include/c++/4.8/bits/unordered_set.h' to
  '/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end
  of file or stream

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  flashplayer is anytime do not connected, so browser is broken and
  closed the window.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-85.129-lowlatency 3.13.11-ckt36
  Uname: Linux 3.13.0-85-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Thu May 19 23:45:06 2016
  DuplicateSignature: package:libstdc++-4.8-dev:4.8.4-2ubuntu1~14.04.1:cannot 
copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2016-04-15 (34 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: gcc-4.8
  Title: package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583816] [NEW] package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to '/usr/in

2016-05-19 Thread Transsportler

Public bug reported:

flashplayer is anytime do not connected, so browser is broken and closed
the window.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1
ProcVersionSignature: Ubuntu 3.13.0-85.129-lowlatency 3.13.11-ckt36
Uname: Linux 3.13.0-85-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Thu May 19 23:45:06 2016
DuplicateSignature: package:libstdc++-4.8-dev:4.8.4-2ubuntu1~14.04.1:cannot 
copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
ErrorMessage: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2016-04-15 (34 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.13
SourcePackage: gcc-4.8
Title: package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to
  install/upgrade: cannot copy extracted data for
  './usr/include/c++/4.8/bits/unordered_set.h' to
  '/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end
  of file or stream

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  flashplayer is anytime do not connected, so browser is broken and
  closed the window.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-85.129-lowlatency 3.13.11-ckt36
  Uname: Linux 3.13.0-85-lowlatency x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Thu May 19 23:45:06 2016
  DuplicateSignature: package:libstdc++-4.8-dev:4.8.4-2ubuntu1~14.04.1:cannot 
copy extracted data for './usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2016-04-15 (34 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: gcc-4.8
  Title: package libstdc++-4.8-dev 4.8.4-2ubuntu1~14.04.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/include/c++/4.8/bits/unordered_set.h' to 
'/usr/include/c++/4.8/bits/unordered_set.h.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583811] [NEW] counter errors

2016-05-19 Thread Nkesiga Clinton

Public bug reported:

crashes every time i open the program

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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: Fri May 20 00:45:08 2016
DistUpgraded: 2016-04-22 19:43:28,958 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
InstallationDate: Installed on 2016-04-21 (28 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eef45c1e-af31-4ce5-8129-e78ceef66f1b ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-22 (27 days ago)
dmi.bios.date: 10/23/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2213
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.46
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd10/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097611405F0610180:rvnHewlett-Packard:rn2213:rvr57.46:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 097611405F0610180
dmi.sys.vendor: Hewlett-Packard
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-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
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 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu May 19 22:05:40 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5547 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2

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

Title:
  counter errors

Status in xorg package in Ubuntu:
  New

Bug description:
  crashes every time i open the program

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Fri May 20 00:45:08 2016
  DistUpgraded: 2016-04-22 19:43:28,958 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
  InstallationDate: Installed on 2016-04-21 (28 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eef45c1e-af31-4ce5-8129-e78ceef66f1b ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (27 days ago)
  dmi.bios.date: 10/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.bo

[Touch-packages] [Bug 1583810] [NEW] Keyboard shortcuts randomly changes (seems to be qwerty/azerty related)

2016-05-19 Thread da2

Public bug reported:

In Ubuntu 16.04, when you hold Super key for some seconds, it displays a
panel giving the current shortcuts.

If I look for the "expose window" shortcut, sometimes it's Super+Z and
sometimes it's Super+W. It doesn't seem to change from a shortcut use to
the next one, but rather from one boot to the next one, but I'm not
sure.

I use a AZERTY keyboard layout, and the Z and W are one of the letters
that swap between AZERTY and QWERTY.

I don't know what triggers the choice of one or the other, maybe this is
at Unity boot. I suspects that sometimes it initializes the shortcuts
*before* the keyboard layout, and sometimes *after*, but that's just a
user point of view.

One day I will expose windows with Super+Z and another day with Super+W,
without to change anything in keyboard layout or shortcuts.

-
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
-
$ apt-cache policy keyboard-configuration 
keyboard-configuration:
  Installé : 1.108ubuntu15
  Candidat : 1.108ubuntu15
 Table de version :
 *** 1.108ubuntu15 500
500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
-
Expected : Shortcuts should never change without an user intervention
-

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 19 23:31:14 2016
InstallationDate: Installed on 2016-04-22 (27 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Keyboard shortcuts randomly changes (seems to be qwerty/azerty
  related)

Status in console-setup package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04, when you hold Super key for some seconds, it displays
  a panel giving the current shortcuts.

  If I look for the "expose window" shortcut, sometimes it's Super+Z and
  sometimes it's Super+W. It doesn't seem to change from a shortcut use
  to the next one, but rather from one boot to the next one, but I'm not
  sure.

  I use a AZERTY keyboard layout, and the Z and W are one of the letters
  that swap between AZERTY and QWERTY.

  I don't know what triggers the choice of one or the other, maybe this
  is at Unity boot. I suspects that sometimes it initializes the
  shortcuts *before* the keyboard layout, and sometimes *after*, but
  that's just a user point of view.

  One day I will expose windows with Super+Z and another day with
  Super+W, without to change anything in keyboard layout or shortcuts.

  -
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  -
  $ apt-cache policy keyboard-configuration 
  keyboard-configuration:
Installé : 1.108ubuntu15
Candidat : 1.108ubuntu15
   Table de version :
   *** 1.108ubuntu15 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status
  -
  Expected : Shortcuts should never change without an user intervention
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 23:31:14 2016
  InstallationDate: Installed on 2016-04-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1579512] Re: Hotspot Access Point mode fails for 802.11a (5GHz) band

2016-05-19 Thread Bug Watch Updater

** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Medium

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

Title:
  Hotspot Access Point mode fails for 802.11a (5GHz) band

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  On a clean 16.04 amd64 install a Managed mode Access Point 'Hotspot'
  fails to initialize when the frequency band is set to 802.11a 5GHz.
  "Automatic" or "2.4GHz" both work (using 802.11g).

  $ lspci -nnk -s 02:00.0
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 
[8086:095a] (rev 59)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5100]
  Kernel driver in use: iwlwifi
  Kernel modules: iwlwifi

  $ journalctl -u NetworkManager.service
  ...
  [1462706989.5477] (wlp2s0): using nl80211 for WiFi device control
  [1462706989.5562] device (wlp2s0): driver supports Access Point (AP) mode
  ...
  [1462708489.5782] Config: added 'ssid' value 'TJ'
  [1462708489.5782] Config: added 'mode' value '2'
  [1462708489.5782] Config: added 'frequency' value '5180'
  [1462708489.5783] Config: added 'freq_list' value '5035 5040 5045 5055 5060 
5080 5170 5180 5190 5200 5210 5220 5230 5240 5250 5260 5280 5290 5300 5320 5500 
5520 5540 5560 5580 5600 5620 5640 5660 5680 5700 5745 5760 5765 5785 5800 5805 
5825 4915 4920 4925 4935 4945 4960 4980'
  [1462708489.5783] Config: added 'key_mgmt' value 'WPA-PSK'
  [1462708489.5783] Config: added 'psk' value ''
  [1462708489.5966] sup-iface[0x16a8ac0,wlp2s0]: config: set interface ap_scan 
to 2
  [1462708515.0203] device (wlp2s0): Activation: (wifi) Hotspot network 
creation took too long, failing activation
  [1462708515.0204] device (wlp2s0): state change: config -> failed (reason 
'supplicant-timeout') [50 120 11]
  [1462708515.0207] manager: NetworkManager state is now DISCONNECTED
  ...

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

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

[Touch-packages] [Bug 1583801] [NEW] No sound via headphones (headset) when Ubuntu boots with them plugged in [XPS 15 9550]

2016-05-19 Thread SKYWATCHER

Public bug reported:

The bug is twofold, first when computer boots if the headset (headphones
with built-in mic, one audio jack) is plugged in, then there is no sound
(via headphones or otherwise). If you plug headphones out and back in,
then it usually works as expected.

The second scenario is the same, except that plugging out and back in
again doesn't help. In that case, I just restart the laptop, then plug
them back in again and it works.

In all cases, microphone works.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  crunch 3248 F pulseaudio
CurrentDesktop: Unity
Date: Thu May 19 22:13:20 2016
InstallationDate: Installed on 2016-05-07 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  crunch 3248 F pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all
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: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in [XPS 15 9550]

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  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: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

2016-05-19 Thread TenLeftFingers

Thanks Pat McGowan, you are correct - I can only get it going by
stopping and restarting. I'll give that a try and report back.

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted

2016-05-19 Thread nemith

Added upstream bug.

** Bug watch added: GNOME Bug Tracker #766684
   https://bugzilla.gnome.org/show_bug.cgi?id=766684

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=766684
   Importance: Unknown
   Status: Unknown

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

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

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

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1389336] Re: Use geoclue-2.0

This bug was fixed in the package empathy - 3.12.11-0ubuntu4

---
empathy (3.12.11-0ubuntu4) yakkety; urgency=medium

  * Drop Revert-geoclue-2.0.patch and switch to geoclue-2.0 (LP: #1389336)
  * Enable geoclue and map support now that empathy is in universe
  * Drop 47_git_activate_with_platform_data.patch,
git_correct_display_messages.patch and git_no_nautilus_sendto.patch:
This has been merged upstream some times ago.
  * Remove empathy-dbg package and rely on automatic dbgsym package

 -- Laurent Bigonville   Thu, 19 May 2016 18:29:12
+0200

** Changed in: empathy (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Use geoclue-2.0

Status in empathy package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in libunity-webapps package in Ubuntu:
  Confirmed
Status in qtlocation-opensource-src package in Ubuntu:
  Triaged
Status in ubuntu-geoip package in Ubuntu:
  Confirmed
Status in webkitgtk package in Ubuntu:
  Confirmed
Status in qtlocation-opensource-src package in Debian:
  Fix Released

Bug description:
  Geoclue2 (source package geoclue-2.0) is a separate, parallel-
  installable version of geoclue1 (source package geoclue).  We will
  likely shortly have both in main (see MIR bug 1388294) and it would be
  great to be able to demote geoclue1 to universe and only support one
  version of the service.

  The packages associated with this bug all have a reverse depends on
  geoclue1 in some form or patches to remove support for geoclue-2.0
  because it wasn't in main yet (e.g. gnome-settings-daemon).

  Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial.
  But we have at least six months to do it.

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

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

[Touch-packages] [Bug 1577139] Re: Can't login, Failed to authentificate

2016-05-19 Thread scellow

Any news on this?

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

Title:
  Can't login, Failed to authentificate

Status in unity8 package in Ubuntu:
  New

Bug description:
  Fresh 16.04 install

  I installed unity8 session and i tried to login

  I enter my password, i press login, then i get a black screen, then it
  comes back to login screen without error message, no buttons, if i
  press ESC on my keyboard i can see the error message:

  "Failed to authentificate"

  
  unity8  v. 8.12+16.04.20160401-0ubuntu1
  unity8-desktop-session-mir v. 1.0.12+15.10.20150609-0ubuntu1

  If you need more info don't hesitate to ask

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

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

[Touch-packages] [Bug 1567389] Re: OpenVPN connections should allow username and password

This bug was fixed in the package ubuntu-settings-components -
0.7+16.04.20160427-0ubuntu1

---
ubuntu-settings-components (0.7+16.04.20160427-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * Resync trunk.

  [ jonas-drange ]
  * Make Cancel/Ok buttons visible always Add support for TLS, Password,
Password+TLS and Static auth types. (LP: #1558531, #1567389)

 -- ci-train-...@canonical.com (Jonas G. Drange)  Wed, 27 Apr 2016
12:32:16 +

** Changed in: ubuntu-settings-components (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-settings-components
in Ubuntu.
https://bugs.launchpad.net/bugs/1567389

Title:
  OpenVPN connections should allow username and password

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Incomplete
Status in ubuntu-settings-components package in Ubuntu:
  Fix Released

Bug description:
  When configuring a VPN connection, there is no "username" field in
  which to enter one's username (an e-mail address, in my case).

  --

  Reproduce:
  - Access the VPN settings (Apps Scope-->System Settings-->VPN-->Add Manual 
Configuration...).
  - Attempt to enter username.

  Result:
  - There is no field in which to enter one's username.

  Expectation:
  - To be able to specify a username for one's VPN connection, as per their 
respective VPN subscription.

  --

  bq Aquaris E5 HD Ubuntu Edition:
  * OS build number: OTA-10
  * Ubuntu Image part: 20160401.1
  * Ubuntu build description: Ubuntu 15.04 - armhf (20160401-184657)
  * Device Image part: 20160329-a9bacdb
  * Device build description: VEGETA01A-S23A_BQ_L100EN_2011_160401
  * Customization Image part: 20160324--36-54-vivid

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

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

[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap

2016-05-19 Thread Paul Larson

I'll keep running to see if I can reproduce it again.

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

Title:
  kernel BUG on snap disconnect from within a snap

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

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

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

@tenleffingers to clarify you can only get the app working again by
stopping it and restarting it? if thats the case its not merely a focus
issue and sounds like the app itself is hung

We might now try to reflash if you are ok with that.
1 - flash stable channel without a full wipe
2 - if that doesn't clear the issue, back up your user home and flash with 
--wipe
3 - if that fixes it, restore the user home and see if it stays fixed or 
reappears

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap

2016-05-19 Thread John Johansen

No, which means its a race of some kind

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

Title:
  kernel BUG on snap disconnect from within a snap

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

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

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

[Touch-packages] [Bug 1470080] Re: Broken icon in indicator when iphone attached

2016-05-19 Thread Sadi Yumuşak

Matthew, I don't know, I've just suggested it as a possible workaround
or whatever it might be called.

I've reported my problem here: https://bugs.launchpad.net/bugs/1556622 which 
was marked as duplicate of this bug report, and I can confirm that the problem 
I've first seen with iPad is the same as iPhone.
The "missing icon" image in the indicator appears only when any such Apple 
device is being charged.
If it's fully charged it only appears in the power menu, and in both cases - as 
far as I can see - its menu item simply has no icon instead of a "missing icon" 
image as can be seen in my screenshot there.

I could even suggest having the same behavior as other devices such as a
Kindle or an Android mobile phone, which are not shown anywhere in the
power indicator - neithe in the indicator or its menu - as they show
their own power status anyway.

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

Title:
  Broken icon in indicator when iphone attached

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Running wily with an iPhone 4 (but I doubt it matters which rev of
  iphone) attached, I see a combined battery gauge for desktop and phone
  in the indicator. Unfortunately the icon is broken / missing when the
  phone is attached, like it's missing a small version of the icon you
  see in system settings -> power.

  See screenshot (next to 61%)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20150522-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 30 12:10:40 2015
  InstallationDate: Installed on 2014-06-16 (379 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2015-05-09 (51 days ago)

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

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

[Touch-packages] [Bug 1583776] [NEW] :)

2016-05-19 Thread Mario Alberto Gomez Fuentes

Public bug reported:

support server xorg :P

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-37.43~14.04.1-generic 4.2.8-ckt10
Uname: Linux 4.2.0-37-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
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: Thu May 19 13:01:10 2016
DistUpgraded: 2016-05-19 02:48:50,231 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
   Subsystem: Gateway, Inc. Device [107b:0700]
InstallationDate: Installed on 2016-05-19 (0 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
MachineType: Gateway MD2614u
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=e7d9d851-bd97-427c-9ab9-2094e3f857be ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2016-05-19 (0 days ago)
dmi.bios.date: 01/14/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 9A.06
dmi.board.vendor: Gateway
dmi.board.version: 9A.06
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.version: Rev.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9A.06:bd01/14/2008:svnGateway:pnMD2614u:pvrRev1:rvnGateway:rn:rvr9A.06:cvnGateway:ct8:cvrRev.1:
dmi.product.name: MD2614u
dmi.product.version: Rev 1
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu May 19 12:47:13 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: radeon

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


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

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

Title:
  :)

Status in xorg package in Ubuntu:
  New

Bug description:
  support server xorg :P

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-37.43~14.04.1-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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: Thu May 19 13:01:10 2016
  DistUpgraded: 2016-05-19 02:48:50,231 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
 Subsystem: Gateway, Inc. Device [107b:0700]
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Gateway MD2614u
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=e7d9d851-bd97-427c-9ab9-2094e3f857be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2016-05-19 (0 days ago)
  dmi.bios.date: 01/14/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9A.06
  dmi.board.vendor: Gateway
  dmi.board.version: 9A.06
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9A.06:bd01/14/2008:svnGateway:pnMD2614u:pvrRev1:rvnGateway:rn:rvr9A.06:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: MD2614u
  dmi.product.version: Rev 1
  dmi.sys.vendor: Gatewa

Re: [Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2016-05-19 Thread Chuck McManis

This has worked to re-display my screen power is removed and then
re-applied to the monitor, I'm doing further testing to see if it also
fixes the issue with lockscreen blanking and sleeping.

On Thu, May 19, 2016 at 8:25 AM, Jan  wrote:
> Please try the patch mentioned here:
> https://bugs.launchpad.net/bugs/1308105
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1581302
>
> Title:
>   Monitor remains blanked with Intel Graphics
>
> Status in lightdm package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display 
> Port or HDMI
>   Running Xubuntu 16.04 - latest all current patches
>
>   Sometimes the monitor remains blanked even when the session has
>   reactivated.
>
>   I have been able to reproduce this problem by letting the monitor
>   remain in the 'blanked' state for > 60 minutes, or powering off the
>   monitor. When the monitor is powered back on and the session is woken
>   up with mouse or keyboard input, it does wake up but the monitor
>   remains blanked.
>
>   I was able to prove to myself the session was awake by leaving it with
>   terminal opened to full screen with VIM running on an NFS mounted file
>   system. I could type and save at the black monitor screen and see that
>   the file got updates from a different system. So the session is "live"
>   but the computer has forgotten to re-establish the DisplayPort link.
>
>   An error appears in the lightdm logs about setting a CRTC, if you
>   activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
>   --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
>   you ssh in from a different machine, tell bash to export DISPLAY=:0
>   (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
>   screen turns on again! This also happens on a Gigabyte BRIX system
>   (same NUC reference design but in that case a core i3 rather than a
>   Core i7).
>
>   To reproduce, turn off the monitor, wait an hour, and turn it on
>   again.
>
>   You can also kill HUP the lightdm process and that will restart a new
>   session (but open windows in the previous session are lost).
>
>   So interesting questions, why does typing xrandr "locally" give you
>   the error but running it from an ssh session work?
>
>   Since xrandr and restarting the session can both "fix" the problem,
>   the driver seems to know how to turn the display on if told correctly.
>
>   How can I find out where the code is getting the CRTC error?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: lightdm 1.18.1-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu May 12 20:33:01 2016
>   InstallationDate: Installed on 2016-05-08 (4 days ago)
>   InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
> (20160420.1)
>   LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
>   LightdmLog:
>[+80180.09s] DEBUG: Seat seat0 changes active session to
>[+80189.53s] DEBUG: Seat seat0 changes active session to 64
>[+80222.67s] DEBUG: Seat seat0 changes active session to c4
>[+80222.67s] DEBUG: Session c4 is already active
>   SourcePackage: lightdm
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581302/+subscriptions

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWE

[Touch-packages] [Bug 1583773] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()

2016-05-19 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-source-registry crashed with SIGSEGV in g_slice_alloc()

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

Bug description:
  All this was automatically generated. I was not aware of any problem.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 19 19:47:01 2016
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2014-09-17 (610 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fd8bb50928a :mov
0x8(%rdx),%rbx
   PC (0x7fd8bb50928a) ok
   source "0x8(%rdx)" (0x7fd8a402b60008) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_type_info_get () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_builder_end () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev postgres sambashare sudo www-data

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

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

[Touch-packages] [Bug 1582662] Re: no cellular connection and settings

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

Title:
  no cellular connection and settings

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  New

Bug description:
  no cellular connection and settings (arale/rc-proposed)
  i have no idea how to reproduce this bug but it already happened 3 times to 
me, the cellular icon (indicator) is gone and also the the "Cellular" entry 
from System Settings/Network (see screenshot). when it happens i can't dial or 
receive calls. the most annoying thing is that i am not allays aware that i 
don't have cell connection since the only giveaway is the missing cell icon.

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

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

[Touch-packages] [Bug 1510382] Re: Window contents (and mouse cursors) become randomly blurry (or clear) after moving around

2016-05-19 Thread Daniel d'Andrada

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

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

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

Title:
  Window contents (and mouse cursors) become randomly blurry (or clear)
  after moving around

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

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

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

[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

2016-05-19 Thread cmcanulty

confirmed no fix yet for xubuntu 16.04 this is a non starter for the
library as users must be auto logged in or the librarians have to run
around and login every machine

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  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
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510382] Re: Window contents (and mouse cursors) become randomly blurry (or clear) after moving around

** Branch linked: lp:~dandrader/unity8/pixelAlignedWindow

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

Title:
  Window contents (and mouse cursors) become randomly blurry (or clear)
  after moving around

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

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

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

[Touch-packages] [Bug 1583079] Re: Drop depedencies on qtdeclarative5-* transitional packages

2016-05-19 Thread Rodney Dawes

** Changed in: pay-service (Ubuntu)
   Importance: Undecided => Medium

** Changed in: pay-service (Ubuntu)
   Status: New => In Progress

** Changed in: pay-service (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: ubuntuone-credentials (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntuone-credentials (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntuone-credentials (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

Title:
  Drop depedencies on qtdeclarative5-* transitional packages

Status in webapps-sprint:
  Confirmed
Status in address-book-app package in Ubuntu:
  New
Status in camera-app package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New
Status in gallery-app package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in notes-app package in Ubuntu:
  New
Status in pay-service package in Ubuntu:
  In Progress
Status in reminders-app package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in u1db-qt package in Ubuntu:
  New
Status in ubuntu-html5-theme package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in ubuntu-ui-extras package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  In Progress
Status in unity-webapps-qml package in Ubuntu:
  New

Bug description:
  With Ubuntu 16.04 LTS as the recommended deadline many packages
  managed to transition to qml-module-xyz package naming from the
  qtdeclarative5-xyz-plugin package naming (bug #1342031). The next step
  is to update all packages that depend on transitioned qtdeclarative5
  -xyz-plugin to depend on the proper qml-module-xyz packages instead.

  The goal is to then drop the transitional packages now that 14.04 LTS
  -> 16.04 LTS upgrades are secured for all the packages that made the
  transition before 16.04 LTS release.

  You can run the following (not 100% complete) to automate this:

  sed -i 's/qtdeclarative5-accounts-plugin/qml-module-ubuntu-onlineaccounts/' 
debian/control
  sed -i 's/qtdeclarative5-qtcontacts-plugin/qml-module-qtcontacts/' 
debian/control
  sed -i 
's/qtdeclarative5-ubuntu-ui-toolkit-plugin/qml-module-ubuntu-components/' 
debian/control
  sed -i 
's/qtdeclarative5-ubuntu-thumbnailer0.1/qml-module-ubuntu-thumbnailer0.1/' 
debian/control
  sed -i 's/qtdeclarative5-qtquick2-plugin/qml-module-qtquick2/' debian/control
  sed -i 
's/qtdeclarative5-online-accounts-client0.1/qml-module-ubuntu-onlineaccounts-client/'
 debian/control
  sed -i 's/qtdeclarative5-window-plugin/qml-module-qtquick-window2/' 
debian/control
  sed -i 
's/qtdeclarative5-xmllistmodel-plugin/qml-module-qtquick-xmllistmodel/' 
debian/control
  sed -i 
's/qtdeclarative5-folderlistmodel-plugin/qml-module-qt-labs-folderlistmodel/' 
debian/control
  sed -i 
's/qtdeclarative5-localstorage-plugin/qml-module-qtquick-localstorage/' 
debian/control
  sed -i 's/qtdeclarative5-test-plugin/qml-module-qttest/' debian/control
  sed -i 's/qtdeclarative5-ubuntu-web-plugin/qml-module-ubuntu-web/' 
debian/control
  sed -i 's/qtdeclarative5-quicklayouts-plugin/qml-module-qtquick-layouts/' 
debian/control

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1583079/+subscriptions

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

2016-05-19 Thread TenLeftFingers

@bfiler Thanks so much. "Rather than swiping the app away .., you can try just 
swiping it to the background .. and then another right edge swipe to make it 
active again."
This doesn't work - it's still 'frozen'.

** Attachment added: "application-legacy-dialer-app-.log"
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1377996/+attachment/4666413/+files/application-legacy-dialer-app-.log

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

2016-05-19 Thread TenLeftFingers

** Attachment added: "system_image_cli_info"
   
https://bugs.launchpad.net/ubuntu-ux/+bug/1377996/+attachment/4666416/+files/system_image_cli_info

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1565717] Re: No connection after returning from area without coverage

@tony the steps to reproduce it are in comment #5, I put my phone in a metal 
pot for 20 seconds.
The bug title is the exact description of the symptom I have, so seems odd to 
make a new bug because doing the same act caused a different state on the 
device.

Bug #1579098 is the same symptom and without an active context so we
already have that

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

Title:
  No connection after returning from area without coverage

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  After moving in an out of my own "faraday cage" an ubuntu phone, NM
  got into an state where *both* WiFi and cellular data were
  disconnected and NM was not able to recover.

  
  * This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 336
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-17 09:19:51
  version version: 336
  version ubuntu: 20160517
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9
  

  Originally reported for:

  NM version:
  network-manager  0.9.10.0-4ubuntu15.1.11

  root@ubuntu-phablet:/home/phablet# system-image-cli -i
  current build number: 298
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-30 16:58:21
  version version: 298
  version ubuntu: 20160330
  version device: 20160323-1467d3c
  version custom: 20160324--36-54-vivid

  phablet@ubuntu-phablet:~$ nmcli d
  DEVICE   TYPE  STATE CONNECTION
  ril_0gsm   connecting (prepare)  /214050030479893/context1
  wlan0wifi  disconnected  --
  ril_1gsm   unavailable   --
  ifb0 ifb   unmanaged --
  ifb1 ifb   unmanaged --
  lo   loopback  unmanaged --
  ip6tnl0  unknown   unmanaged --
  sit0 unknown   unmanaged --
  tunl0unknown   unmanaged --

  phablet@ubuntu-phablet:~$ nmcli c
  NAME   UUID  TYPE 
DEVICE
  WLAN_1609  fe9b17ad-88fa-43b7-bcab-8fbc1985ce42  
802-11-wireless  --
  Wireless   98ff5b6f-b0d9-471a-b867-8a7be51e12c2  
802-11-wireless  --
  Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089  
802-11-wireless  --
  /234304107917083/context1  1f192cdc-ccea-2dc3-fa13-619ed3053828  gsm  
--
  /214321010036211/context1  0992421f-2369-0765-ceaa-ba2a3091e111  gsm  
--
  /214050030479893/context1  d30e4f19-9d00-ab1f-ab43-6d9c1b628556  gsm  
ril_0
  /214019301737411/context1  88b28978-e2fc-6336-8665-b0ae78d321ae  gsm  
--

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  Settings = { Gateway=10.50.83.25 
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0 
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
  Name = Pepephone
  Type = internet
  AccessPointName = gprs.pepephone.com
  Active = 1
  Protocol = ip
  AuthenticationMethod = chap
  Password =
  Preferred = 0
  Username =
  IPv6.Settings = { }

  [ /ril_0/context2 ]
  Name = MMS Pepephone
  Type = mms
  Active = 0
  Settings = { }
  MessageCenter = http://www.pepephone.com
  MessageProxy = 10.138.255.43:8080
  Preferred = 0
  Password =
  AccessPointName = gprs.pepephone.com
  Protocol = ip
  AuthenticationMethod = chap
  Username =
  IPv6.Settings = { }

  phablet@ubuntu-phablet:~$ ifconfig
  ccmni0Link encap:Ethernet  HWaddr 46:23:7c:fb:73:cb
    inet addr:10.50.83.25  Mask:255.0.0.0
    UP RUNNING NOARP  MTU:1500  Metric:1
    RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:603432 (603.4 KB)  TX bytes:193513 (193.5 KB)

  loLink encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:16436  Metric:1
    RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
    TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1733281 (1.7 MB)  TX bytes:1733281 (1.7 MB)

  wlan0 Link encap:Ethernet  HWaddr b8:64:91:47:21:b6
    UP BROADCAST MULTICAST  MTU:1500  Metric:1

[Touch-packages] [Bug 1557981] Re: Selected-Tab Hard to Distinguish in Default Ambiance Theme

2016-05-19 Thread Jeremy Bicha

Ubuntu-themes is the source package now.

** Project changed: light-themes => ubuntu-themes

** Changed in: ubuntu-themes
   Status: New => Confirmed

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

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

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

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New => Confirmed

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

Title:
  Selected-Tab Hard to Distinguish in Default Ambiance Theme

Status in Ubuntu theme:
  Confirmed
Status in Unity:
  Invalid
Status in gnome-system-monitor package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The default Theme in Ubuntu 16.04 is called "Ambiance":
  http://neartalk.com/ss/2016-03-16_005_565x390.png

  When Gnome-System-Monitor is running under the Ambiance theme, you can barely 
distinguish which tab is selected:
  http://neartalk.com/ss/2016-03-16_003_679x497.png

  Compare this with the non-default theme called "Radiance", where the 
selected-tab (in Gnome-System-Monitor) is clearly distinguishable at a glance 
(without eye strain):
  http://neartalk.com/ss/2016-03-16_004_687x497.png

  Which package would be responsible for making the selected-tab more
  distinguishable to the eye in gnome-system-monitor under the default
  Ambiance theme?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-system-monitor 3.18.2-1
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 16 04:38:11 2016
  InstallationDate: Installed on 2016-03-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1557981] [NEW] Selected-Tab Hard to Distinguish in Default Ambiance Theme

You have been subscribed to a public bug:

The default Theme in Ubuntu 16.04 is called "Ambiance":
http://neartalk.com/ss/2016-03-16_005_565x390.png

When Gnome-System-Monitor is running under the Ambiance theme, you can barely 
distinguish which tab is selected:
http://neartalk.com/ss/2016-03-16_003_679x497.png

Compare this with the non-default theme called "Radiance", where the 
selected-tab (in Gnome-System-Monitor) is clearly distinguishable at a glance 
(without eye strain):
http://neartalk.com/ss/2016-03-16_004_687x497.png

Which package would be responsible for making the selected-tab more
distinguishable to the eye in gnome-system-monitor under the default
Ambiance theme?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-system-monitor 3.18.2-1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 16 04:38:11 2016
InstallationDate: Installed on 2016-03-14 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
SourcePackage: gnome-system-monitor
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: ubuntu-themes
 Importance: Undecided
 Status: Confirmed

** Affects: unity
 Importance: Undecided
 Status: Invalid

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


** Tags: amd64 apport-bug xenial
-- 
Selected-Tab Hard to Distinguish in Default Ambiance Theme
https://bugs.launchpad.net/bugs/1557981
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes in Ubuntu.

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

[Touch-packages] [Bug 1583469] Re: Strange behavior after using desktop mode

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Strange behavior after using desktop mode

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

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 1581888] Re: Open command toggles between default paths

2016-05-19 Thread Bug Watch Updater

** Changed in: gtk
   Status: Unknown => Confirmed

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Open command toggles between default paths

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Start gnome-system-log. Click on the gear button and select Open. The
  Open Log dialog opens, showing contents at default path /var/log.
  Dismiss that dialog. Again click the gear button and select Open. The
  same dialog opens, but the path is now ~. Closing and opening the
  dialog repeatedly toggles between the same two paths.

  The behavior changes after the dialog is used to browse to a different
  directory and successfully open a file (but not after simply opening a
  file in the default directory). Then it remembers the last path as the
  default between invocations of gnome-system-log, as expected.

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

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

[Touch-packages] [Bug 1558382] Re: Unmatched contacts displayed in result list when searching for single letter

Search seems totally broken with 1 or 2 letters, 1 letter matches every
entry, 2 letters seemingly random sets of entries

rc proposed on mx4

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

Title:
  Unmatched contacts displayed in result list when searching for single
  letter

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  ~$ system-image-cli -i
  current build number: 272
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-03-16 05:48:58
  version version: 272
  version ubuntu: 20160316
  version device: 20160111-51982fc
  version custom: 1452441600

  
  Reproduce Steps:

  1) Open the Contacts application.
  2) Create some new contacts with the name "", "", "", "", 
"k", "h".
  3) Press search icon.
  4) Search for contact by letter 'T' or 't'.

  Actual Result：
  Not only the matched contacts "", "" are displayed in the result 
list, but also unmatched contacts "", "" are listed.

  Expect Result:
  Contacts should be filtered according to letter 'T' or 't'.

  Notes :Search function can't identify letter "T"and "t" .

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

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

[Touch-packages] [Bug 1558382] Re: Unmatched contacts displayed in result list when searching for single letter

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

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

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

Title:
  Unmatched contacts displayed in result list when searching for single
  letter

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  ~$ system-image-cli -i
  current build number: 272
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2016-03-16 05:48:58
  version version: 272
  version ubuntu: 20160316
  version device: 20160111-51982fc
  version custom: 1452441600

  
  Reproduce Steps:

  1) Open the Contacts application.
  2) Create some new contacts with the name "", "", "", "", 
"k", "h".
  3) Press search icon.
  4) Search for contact by letter 'T' or 't'.

  Actual Result：
  Not only the matched contacts "", "" are displayed in the result 
list, but also unmatched contacts "", "" are listed.

  Expect Result:
  Contacts should be filtered according to letter 'T' or 't'.

  Notes :Search function can't identify letter "T"and "t" .

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

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

[Touch-packages] [Bug 1439784] Re: [apport-kde] apport-collect: Can not import module PyQt5.QtCore

>Problem has re-appeared in 2.20.1-0ubuntu2 (system upgraded to kubuntu 16.04)
I confirm that.

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

Title:
  [apport-kde] apport-collect: Can not import module PyQt5.QtCore

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  I had to use apport-collect in a tty, because in kde it is not usable:

  benedikt@benediktZ50-70 ~ % apport-collect 1439694
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  System : Kubuntu 15.04

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

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

[Touch-packages] [Bug 1451808] Re: apport-collect broken in kubuntu vivid

Tha same: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1569094

** Summary changed:

- apport-collect broken in kubuntu vivid
+ apport-collect broken in kubuntu

** Summary changed:

- apport-collect broken in kubuntu
+ apport-collect error: No module named PyQt5.QtCore

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

Title:
  apport-collect error: No module named PyQt5.QtCore

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  In kubuntu vivid, apport reacts as follows:

  apport-collect 1451277
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  5 14:35:33 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583636] Re: Missing Page.header in APL should cause message or color change

If you mean to temporarily warn the developer (for example with a red
border, which is shown until the fallback header is removed) that the
behavior an app relies on is deprecated, I agree.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  Missing Page.header in APL should cause message or color change

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

Bug description:
  AdaptivePageLayout still supports legacy Page's from 1.2 times that
  don't specify a header. Eventually that's going to stop working.

  addPageToCurrent/NextColumn should show a warning or otherwise
  visually highlight the header if no header is defined, so developers
  will know to update their code.

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

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

[Touch-packages] [Bug 1569094] Re: After upgrade to Xenial, apport-collect fails

And duplicate of:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808

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

Title:
  After upgrade to Xenial, apport-collect fails

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  After upgrading wily -> Xenial, when I run apport-collect with no
  arguments, this is what I get:

  Mon Apr 11 19:53:52 vectro@mirian:~ $ sudo apport-collect
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  This is with apport 2.20.1-0ubuntu1. I assume it is a packaging issue.

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

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

[Touch-packages] [Bug 1569094] Re: After upgrade to Xenial, apport-collect fails

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

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

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

Title:
  After upgrade to Xenial, apport-collect fails

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  After upgrading wily -> Xenial, when I run apport-collect with no
  arguments, this is what I get:

  Mon Apr 11 19:53:52 vectro@mirian:~ $ sudo apport-collect
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  This is with apport 2.20.1-0ubuntu1. I assume it is a packaging issue.

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

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

[Touch-packages] [Bug 1569094] Re: After upgrade to Xenial, apport-collect fails

Looks like old bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784

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

Title:
  After upgrade to Xenial, apport-collect fails

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  After upgrading wily -> Xenial, when I run apport-collect with no
  arguments, this is what I get:

  Mon Apr 11 19:53:52 vectro@mirian:~ $ sudo apport-collect
  ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore

  This is with apport 2.20.1-0ubuntu1. I assume it is a packaging issue.

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

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

[Touch-packages] [Bug 1576741] Re: Upcoming alarm ETA going out of sync

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-yakkety-
landing-059

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

Title:
  Upcoming alarm ETA going out of sync

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

Bug description:
  Similar to Bug #1557571, but for alarms.

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

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

[Touch-packages] [Bug 1577147] Re: SIM PIN screen has a white overlay instead of a dark one

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-yakkety-
landing-059

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

Title:
  SIM PIN screen has a white overlay instead of a dark one

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

Bug description:
  Likely due to r2345 [1] we now have a lightening layer instead of a
  darkening one on the SIM PIN screen - see attachment.

  [1] https://bazaar.launchpad.net/~unity-
  team/unity8/trunk/changes/2354?start_revid=2374

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.12+15.04.20160427.3-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Sun May  1 14:02:18 2016
  InstallationDate: Installed on 2016-04-29 (2 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160429-020305)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8.log:
   [DD 2016-05-01 12:02:07.121200] [player_stub.cpp:184@operator()] 
PlaybackStatusChanged signal arrived via the bus (status: 
PlaybackStatus::stopped)
   Attempted to unregister path (path[0] = core path[1] = ubuntu) which isn't 
registered

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

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

[Touch-packages] [Bug 1582994] Re: Unity 8 flaky test qmltestrunner::Wizard::test_accountPage()

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-yakkety-
landing-059

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

Title:
  Unity 8 flaky test qmltestrunner::Wizard::test_accountPage()

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Failing at for example
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-xenial-ci-train-ppa-service-
  landing-019/xenial/amd64/u/unity8/20160517_191859@/log.gz , succeeding
  on retry.

  ---
  * Start testing of qmltestrunner *
  Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.3.1 20160407)
  PASS   : qmltestrunner::Wizard::initTestCase()
  QWARN  : qmltestrunner::Wizard::test_accountPage() [PERFORMANCE]: Last frame 
took 137 ms to render.
  QWARN  : qmltestrunner::Wizard::test_accountPage() [PERFORMANCE]: Last frame 
took 68 ms to render.
  QWARN  : qmltestrunner::Wizard::test_accountPage() [PERFORMANCE]: Last frame 
took 68 ms to render.
  QWARN  : qmltestrunner::Wizard::test_accountPage() [PERFORMANCE]: Last frame 
took 372 ms to render.
  FAIL!  : qmltestrunner::Wizard::test_accountPage() function returned 
unexpected result
 Actual   (): tzPage
 Expected (): accountPage
 Loc: 
[/tmp/autopkgtest.V8ZdUn/build.wMD/unity8-8.12+16.04.20160504.2/tests/qmltests/Wizard/tst_Wizard.qml(147)]
  QWARN  : qmltestrunner::Wizard::test_accountPage() [PERFORMANCE]: Last frame 
took 111 ms to render.
  PASS   : qmltestrunner::Wizard::test_languageChange()
  QWARN  : qmltestrunner::Wizard::test_languageChange() [PERFORMANCE]: Last 
frame took 111 ms to render.
  PASS   : qmltestrunner::Wizard::test_languageNoChange()
  ...

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

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

[Touch-packages] [Bug 1447839] Re: Unity8 mouse cursor never changes when moving over widgets in app windows

** Branch linked: lp:~ci-train-bot/qtmir/qtmir-ubuntu-yakkety-
landing-059

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

Title:
  Unity8 mouse cursor never changes when moving over widgets in app
  windows

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in QtMir:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Mouse cursor never changes when moving over widgets in app windows
  (e.g. 'I' cursor for a text editor).

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

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

[Touch-packages] [Bug 1564342] Re: The screen should not dim when indicators are open

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-yakkety-
landing-059

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

Title:
  The screen should not dim when indicators are open

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

Bug description:
  Currently, when the indicators are opened, the rest of the screen is
  dimmed. In light of convergence, this doesn't make sense for larger
  screens and should be removed.

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

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

[Touch-packages] [Bug 1575893] Re: Toolbar focus & keyboard navigation

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Toolbar focus & keyboard navigation

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Toolbar needs focus for keyboard navigation that works in the same way
  as the Sections.

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

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

[Touch-packages] [Bug 1558018] Re: Scrolling of icons in Toolbar

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Scrolling of icons in Toolbar

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Currently, when the icons do not all fit in the toolbar, an overflow
  button is shown that shows an overflow popover/panel when clicked.
  This needs to be replaced by icon scrolling instead.

  See https://docs.google.com/document/d/1F-zD6CF8YFfA-
  nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

  UX solution:
  
https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.w16v0yn510iy
 is this not what you need?

  https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-
  nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.duaef4xy7sqv

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

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

[Touch-packages] [Bug 1582843] Re: PullToRefreshStyle reference error

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

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

Title:
  PullToRefreshStyle reference error

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  tim@tim-XPS-13-9350:~/dev/ubuntu-ui-toolkit/staging$ source export_qml_dir.sh 
  tim@tim-XPS-13-9350:~/dev/ubuntu-ui-toolkit/staging$ ./gallery.sh 
  
file:///home/tim/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/PullToRefreshStyle.qml:146:
 ReferenceError: view is not defined

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

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

[Touch-packages] [Bug 1566735] Re: Tabs documentation does not mention that Tabs are deprecated