[Touch-packages] [Bug 1406945] Re: Difference between lxc autostart from init script and manual lxc-start call

[Serge Hallyn]

Could you show the result of

sudo which lxc-start
sudo whereis lxc-start
sudo env

** Changed in: lxc (Ubuntu)
   Status: New = Incomplete

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

Title:
  Difference between lxc autostart from init script and manual lxc-start
  call

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  According to
  https://answers.launchpad.net/ubuntu/+source/lxc/+question/255408,
  there seem to be a difference between `lxc start` and the autostart
  feature lxc.start.auto.

  On my Ubuntu 14.10, I have problem starting up containers manually,
  but autostarting the same containers works without problems. I cannot
  see a difference, the file /etc/init/lxc-instance.conf is very simple
  and doesn't set any important additional environment variables.

  The log output is as follows

  # lxc-start -n vm-mycontainer -F 
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make / rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /dev rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /dev/pts rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /dev/shm rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /dev/mqueue rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /dev/hugepages rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /run rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /run/lock rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /run/user rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /run/user/23001/gvfs rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/kernel/security rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/systemd rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/cpuset rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/cpu,cpuacct rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/memory rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/devices rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/freezer rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/net_cls,net_prio rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/blkio rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/perf_event rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 3884 Permission denied - Failed to 
make /sys/fs/cgroup/hugetlb rslave
  lxc-start: conf.c: remount_all_slave: 3885 Continuing...
  lxc-start: conf.c: remount_all_slave: 

[Touch-packages] [Bug 1383870] Re: [phone-app] + [messaging-app] + [address-book-app] list tug actions should collapse after user moves view

[Ubuntu Phone Apps Jenkins Bot]

Fix committed into lp:music-app at revision 773, scheduled for release
in music-app, milestone music-app-14.10-week-40

** Changed in: music-app
   Status: In Progress = Fix Committed

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

Title:
  [phone-app] + [messaging-app] + [address-book-app] list tug actions
  should collapse after user moves view

Status in Address Book App:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Music application for Ubuntu devices:
  Fix Committed
Status in Ubuntu UX bugs:
  Fix Committed
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  build r120

  Steps to reproduce:
  1. open phone app
  2. carry out a bottom edge swipe to access your RECENT
  3. swipe any list item to the left or right
  4. now scroll your list view a little bit down or up, make sure the list item 
actions stay in view

  Actual Result: the actions remain on the screen, they only collapse if
  it hides behind the header or bottom of the view

  Expected result: if user starts to scroll the list view while a list item 
shows additional actions, the list item should collapse.
  Users are carrying out a different actions in that case and are likely not 
being interested anymore in the revealed list item actions.

  Same behaviour applies for the messaging app and the address-book-app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1383870/+subscriptions

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

[Touch-packages] [Bug 1367495] Re: Bridge still not created if bind9 is on

[Serge Hallyn]

note i don't think this is a dup of bug 1240757 as you had original
speculated, because you do not seem to have any bind9 or dnsmasq
listening on 10.0.3.1.

Please attach your /etc/default/lxc-net file.  Your lxc-net.log file
showed an error opening /etc/lxc/dnsmasq.conf, but the line which would
set that configuration file is commented out in the shipped /etc/default
/lxc-net.

** Changed in: lxc (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Bridge still not created if bind9 is on

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  This is probably a dup of bug 1240757, created just so I could upload
  the data requested in that bug report.

  On a fresh, probably vanilla, ubuntu 14.04 server, I tried using ubuntu 
14.04's default lxc.
  It created containers fine, but they failed to start, complaining
lxc-start: failed to attach 'veth9HNUS9' to the bridge 'lxcbr0' : No such 
device
  /var/log/upstart/lxc-net.log says
dnsmasq: failed to create listening socket for 10.0.3.1: Address already in 
use

  This didn't happen on a desktop 14.04 instance, where bind9 is not
  installed by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Tue Sep  9 16:39:34 2014
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1409200] [NEW] HWCursor artifacts on custom cursors using Intel driver

[Raúl Arellano]

Public bug reported:

In fresh install (even in live cd) when accessing some app / website
that use custom cursor, it wil artifact, the cursor turns to a box with
trailers pointers and diferent background.

Example: when visiting http://foro.elhacker.net (spanish forum) 
http://postimg.org/image/wlza8fbvd/

Also happens when using VirtualBox with Windows (see Attachment) 
http://postimg.org/image/8zzsr4cen/
(Virtual Machine downloaded from 
https://www.modern.ie/es-es/virtualization-tools  - Windows 7 with IE 9)

A workarround is disable HWCursor using xorg.conf or xorg.conf.d files.
But that wont let me do multiple monitor with two gpu's (discrete gpu
and intel igpu)

Hardware:
Asus P8H77-M PRO
Intel i5 2500

Other Info
Description:Ubuntu 14.10
Release:14.10

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Jan 10 00:37:19 2015
InstallationDate: Installed on 2014-10-24 (77 days ago)
InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

** Attachment added: Mouse pointer artifact in VirtualBox
   
https://bugs.launchpad.net/bugs/1409200/+attachment/4294988/+files/instant%C3%A1nea2.png

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

Title:
  HWCursor artifacts on custom cursors using Intel driver

Status in xorg package in Ubuntu:
  New

Bug description:
  In fresh install (even in live cd) when accessing some app / website
  that use custom cursor, it wil artifact, the cursor turns to a box
  with trailers pointers and diferent background.

  Example: when visiting http://foro.elhacker.net (spanish forum) 
  http://postimg.org/image/wlza8fbvd/

  Also happens when using VirtualBox with Windows (see Attachment) 
  http://postimg.org/image/8zzsr4cen/
  (Virtual Machine downloaded from 
https://www.modern.ie/es-es/virtualization-tools  - Windows 7 with IE 9)

  A workarround is disable HWCursor using xorg.conf or xorg.conf.d
  files. But that wont let me do multiple monitor with two gpu's
  (discrete gpu and intel igpu)

  Hardware:
  Asus P8H77-M PRO
  Intel i5 2500

  Other Info
  Description:Ubuntu 14.10
  Release:14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Jan 10 00:37:19 2015
  InstallationDate: Installed on 2014-10-24 (77 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 950494] Re: [Macbook Air 3, 2] headset mic not recognized

[chrisolof]

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

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

Title:
  [Macbook Air 3,2] headset mic not recognized

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  == Summary ==
  Since upgrading a MacBook Air from 11.10 to 12.04 the headset microphone is 
no longer recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon1864 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xd328 irq 16'
     Mixer name : 'Nvidia MCP89 HDMI'
     Components : 'HDA:10134206,106b3d00,00100301 
HDA:10de000c,10de0101,00100200'
     Controls  : 36
     Simple ctrls  : 12
  Date: Thu Mar  8 21:09:23 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac 
(20111012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: Upgraded to precise on 2012-03-05 (3 days ago)
  dmi.bios.date: 11/18/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA31.88Z.0061.B01.1011181342
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-942C5DF58193131B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir3,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942C5DF58193131B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B:
  dmi.product.name: MacBookAir3,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1409117] Re: GPG does not verify keys received when using --recv-keys leaving communicaiton with key servers vulnerable to MITM

[Bug Watch Updater]

** Changed in: gnupg
   Status: Unknown = Fix Released

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

Title:
  GPG does not verify keys received when using --recv-keys leaving
  communicaiton with key servers vulnerable to MITM

Status in GNU Privacy Guard:
  Fix Released
Status in gnupg package in Ubuntu:
  Fix Released
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in gnupg source package in Lucid:
  Confirmed
Status in gnupg2 source package in Lucid:
  Confirmed
Status in gnupg source package in Precise:
  Confirmed
Status in gnupg2 source package in Precise:
  Confirmed
Status in gnupg source package in Trusty:
  Confirmed
Status in gnupg2 source package in Trusty:
  Confirmed
Status in gnupg source package in Utopic:
  Confirmed
Status in gnupg2 source package in Utopic:
  Fix Released
Status in gnupg source package in Vivid:
  Fix Released
Status in gnupg2 source package in Vivid:
  Fix Released
Status in gnupg package in Debian:
  Unknown

Bug description:
  The patch from http://bugs.gnupg.org/gnupg/issue1579 is critical and
  should be backported to 12.04; right now, it is not.

  This leaves 12.04 users of GPG2 vulnerable to MITM attacks on gpg2
  --recv-keys. See https://evil32.com/ for an example (the text that is
  striked out; the gpg2 package on 12.04 is still vulnerable).

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

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

[Touch-packages] [Bug 1406925] Re: lxc-start fails due to insufficient permission for creating netdev

[Serge Hallyn]

Thanks for taking the time to report this bug.  Certainly as root you
should be able to attach devices to lxcbr0.

Could you please

1. show the result of 'ifconfig -a' and 'brctl show'
2. do 'sudo lxc-start -n Ubuntu-12.04.5-i386 -f -l trace -o lxc.debug' and 
attach lxc.debug here
3. try:
  sudo lxc-create -t download -n p1 -- -d ubuntu -r trusty -a i386
  sudo lxc-start -n p1
and let us know whether that succeeds.

** Changed in: lxc (Ubuntu)
   Importance: Undecided = High

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

Title:
  lxc-start fails due to insufficient permission for creating netdev

Status in lxc package in Ubuntu:
  New

Bug description:
  After installing an lxc with `sudo lxc-create -n Ubuntu-12.04.5-i386
  -t /usr/share/lxc/templates/lxc-ubuntu -- --release precise --mirror
  http://richtercloud.de:3142/de.archive.ubuntu.com/ubuntu --arch i386`,
  starting the container with `sudo lxc-start -n Ubuntu-12.04.5-i386
  --foreground` fails due to the following error:

  lxc-start: conf.c: instanciate_veth: 2817 failed to attach 'vethY1J1I1' 
to the bridge 'lxcbr0' : Operation not permitted
  lxc-start: conf.c: lxc_create_network: 3100 failed to create netdev
  lxc-start: start.c: lxc_spawn: 829 failed to create the network
  lxc-start: start.c: __lxc_start: 1087 failed to spawn 
'Ubuntu-12.04.5-i386'
  lxc-start: lxc_start.c: main: 337 The container failed to start.
  lxc-start: lxc_start.c: main: 341 Additional information can be obtained 
by setting the --logfile and --logpriority options.

  It should be possible to start the container right away after
  installation of the apt package and handle eventually necessary setup
  tasks (of permissions, etc.) in `debconf`.

  Currently it's necessary to comment out all `lxc.network.*` entries in
  the container configuration file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lxc 1.1.0~alpha2-0ubuntu3
  ProcVersionSignature: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/proc/version_signature'
  Uname: Linux 3.17.7-031707-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  1 14:31:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to utopic on 2014-12-28 (4 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  upstart.lxc-net.override: manual

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

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

[Touch-packages] [Bug 884121] Re: Printer stops on German double quotes

[Launchpad Bug Tracker]

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

** Changed in: cups (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Printer stops on German double quotes

Status in cups package in Ubuntu:
  Expired

Bug description:
  Hardware: Konica-Minolta PagePro 1300W
  Software: min12xxw 0.0.9-3ubuntu2 on Kubuntu 10.04
  Input: Text file text.txt containing „German double quotes“, created with 
AltGr+v and AltGr+b
  Command line: lpr -P PagePro text.txt
  Result: Print job in status „Angehalten“ (stopped), no printing
  “Print again“ also falls into “stopped“ status

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

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

[Touch-packages] [Bug 1238989] Re: does not restart on upgrade

[Launchpad Bug Tracker]

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

** Changed in: url-dispatcher (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  does not restart on upgrade

Status in URL Dispatcher:
  Incomplete
Status in url-dispatcher package in Ubuntu:
  Expired

Bug description:
  url-dispatcher service should restart when upgraded

To manage notifications about this bug go to:
https://bugs.launchpad.net/url-dispatcher/+bug/1238989/+subscriptions

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

[Touch-packages] [Bug 1409222] [NEW] kubuntu live desktop iso xorg crashes upon launching installer

[gregrwm]

Public bug reported:

sit down at certain computer that runs xubuntu and lubuntu ISOs just fine, but 
crashes the kubuntu ISO.
download kubuntu 14.04.1 desktop iso.
boot it.
when the live desktop appears, switch to a virtual console.
type in ubuntu-bug xorg, without a CR, to be ready.
switch back to the live desktop.
launch the installer.
xorg crashes.
switch back to the virtual console.  hit CR (thus launching ubuntu-bug).  do 
these several times, because there's no apparent response.
eventually the lockup dissolves, and i see the ubuntu-bug interaction, which 
absorbed the extra CRs by repeating it's query about whether to send the report.
meanwhile xorg is relaunched into a login screen.
switch back to the virtual console.  send the report.  it's this one.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
Date: Sat Jan 10 06:58:55 2015
LiveMediaBuild: Kubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

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

Title:
  kubuntu live desktop iso xorg crashes upon launching installer

Status in xorg package in Ubuntu:
  New

Bug description:
  sit down at certain computer that runs xubuntu and lubuntu ISOs just fine, 
but crashes the kubuntu ISO.
  download kubuntu 14.04.1 desktop iso.
  boot it.
  when the live desktop appears, switch to a virtual console.
  type in ubuntu-bug xorg, without a CR, to be ready.
  switch back to the live desktop.
  launch the installer.
  xorg crashes.
  switch back to the virtual console.  hit CR (thus launching ubuntu-bug).  do 
these several times, because there's no apparent response.
  eventually the lockup dissolves, and i see the ubuntu-bug interaction, which 
absorbed the extra CRs by repeating it's query about whether to send the report.
  meanwhile xorg is relaunched into a login screen.
  switch back to the virtual console.  send the report.  it's this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CasperVersion: 1.340
  Date: Sat Jan 10 06:58:55 2015
  LiveMediaBuild: Kubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1409117] Re: GPG does not verify keys received when using --recv-keys leaving communicaiton with key servers vulnerable to MITM

[Bug Watch Updater]

** Changed in: gnupg (Debian)
   Status: Unknown = Fix Released

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

Title:
  GPG does not verify keys received when using --recv-keys leaving
  communicaiton with key servers vulnerable to MITM

Status in GNU Privacy Guard:
  Fix Released
Status in gnupg package in Ubuntu:
  Fix Released
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in gnupg source package in Lucid:
  Confirmed
Status in gnupg2 source package in Lucid:
  Confirmed
Status in gnupg source package in Precise:
  Confirmed
Status in gnupg2 source package in Precise:
  Confirmed
Status in gnupg source package in Trusty:
  Confirmed
Status in gnupg2 source package in Trusty:
  Confirmed
Status in gnupg source package in Utopic:
  Confirmed
Status in gnupg2 source package in Utopic:
  Fix Released
Status in gnupg source package in Vivid:
  Fix Released
Status in gnupg2 source package in Vivid:
  Fix Released
Status in gnupg package in Debian:
  Fix Released

Bug description:
  The patch from http://bugs.gnupg.org/gnupg/issue1579 is critical and
  should be backported to 12.04; right now, it is not.

  This leaves 12.04 users of GPG2 vulnerable to MITM attacks on gpg2
  --recv-keys. See https://evil32.com/ for an example (the text that is
  striked out; the gpg2 package on 12.04 is still vulnerable).

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

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

[Touch-packages] [Bug 1069064]

[Sndirsch-u]

Product is no longer supported. In case the issue is still reproducable
on a maintainerd product (at that momement: openSUSE 13.1 or later),
feel free to reopen.

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

Title:
  Screen keeps blinking after boot up

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in openSUSE:
  Won't Fix

Bug description:
  Hi,

  I tried installing ubuntu quantal on my acer 5002 laptop with sis
  card. But on boot from usb screen keeps flickering with only mouse
  pointer shows up on whole screen.

  I tried xubuntu as well and result is same.
  --- 
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  Package: xorg 1:7.6+12ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Tags:  precise ubuntu
  Uname: Linux 3.2.0-32-generic-pae i686
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 597509] Re: Volume adjustment bar's mouse-over highlight not displaying correctly

[Launchpad Bug Tracker]

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

** Changed in: ido (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Volume adjustment bar's mouse-over highlight not displaying correctly

Status in Indicator Display Objects:
  Incomplete
Status in ido package in Ubuntu:
  Expired

Bug description:
  Note: volume adjustment bar refers to the rectangular bar that can
  be clicked and dragged horizontally to adjust the users' system's
  volume level up or down.

  Expected behavior: The user should be able to adjust system volume by
  clicking anywhere on the volume adjustment bar and moving their
  mouse/trackpad left or right.

  Actual behavior: When attempting to click the volume adjustment bar,
  the bar can only be clicked, it appears, from the top 50% of the bar
  itself to 50% above the bar. It looks like the bar's selection area
  has been pushed up half of the bar's vertical length. In other
  words, rather than clicking the actual adjustment bar to adjust system
  volume, the user can only click the top vertical 50% of the bar itself
  and another 50% of the bar's total height above the bar itself to
  adjust volume.

  See the attached screenshot for a visual depiction of the explained
  behavior.

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

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

[Touch-packages] [Bug 647438] Re: Volume slider widget hotspot issues

[Launchpad Bug Tracker]

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

** Changed in: ido (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Volume slider widget hotspot issues

Status in Indicator Display Objects:
  Incomplete
Status in ido package in Ubuntu:
  Expired

Bug description:
  This is a subtle bug, but it has affected me many times nonetheless.

  I'm using the default Ubuntu 10.04 theme, and when you click on
  certain parts of the 'handle' in the volume control slider it actually
  jumps right, as if you had clicked on the 'track' to the right of it.

  It seems only a small area does this, but it is pretty damn annoying
  when you are trying to drag the handle to a lower volume, and it
  actually jumps to a higher one.

  To recreate:

  1. Click the volume icon to open the volume control panel.
  2. Move the mouse over the slider handle at the top. You should see the hover 
highlight. Move the mouse down slowly until the highlight just goes away. This 
happens in about the middle.
  3. Click. Instead of grabbing the handle, it jumps to the right.

  I made a video of this which I can upload if you can't recreate it.

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

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

[Touch-packages] [Bug 596162] Re: Volume Control Highlight Bug

[Launchpad Bug Tracker]

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

** Changed in: ido (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Volume Control Highlight Bug

Status in Indicator Display Objects:
  Incomplete
Status in Sound Menu:
  Invalid
Status in ido package in Ubuntu:
  Expired

Bug description:
  I'm running Maverick with Indicator Applet 0.4.2. When I click on the
  volume control on the desktop, it brings up the volume slider. By
  default in Maverick the slider is now black and when the mouse tip
  hovers over the slider it turns to a grayish brown color. When it
  turns to this lighter color, you can slide the volume up and down. For
  me the slider click box seems to be a half step above the slider icon.
  The entire bottom have of the slider does not work for me and I can
  move the slider when I left click above the slider icon.

  There is another bug that may be fixed if the click box is moved down
  to match the slider icon. For me, If my mouse is just below the
  halfway point on the slider icon and the slider is black and I left
  click, the volume will go up until I lift off of my mouse or I reach
  max volume. Most of the bottom area does not work but this is a small
  area just below the half way point of the slider.

  Earlier today when I was wearing my headphones I wanted to turn the
  volume down because it was to loud. So I used my mouse to try and turn
  the volume down, but it went up. I had to throw my headphones off
  because it became to loud. I hit that small area just below the half
  way point of the slider

  I checked and this bug is not present in Lucid Lynx.

  In the attachment the green area is where the slider works for me and
  the red area makes the volume go up when I click it.

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

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

[Touch-packages] [Bug 950494] Re: [Macbook Air 3, 2] headset mic not recognized

[chrisolof]

Hello,

I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus
Logic CS4208 and would love to get the microphone part of the TRRS
connector working.  Mac OS picks up and utilizes the TRRS headset mic
without issue so I know the hardware is a go.

Running sudo hda-jack-sense-test -a results in:

Traceback (most recent call last):
  File /usr/bin/hda-jack-sense-test, line 47, in module
codec = HDACodec(cardindex, codecindex)
  File /usr/share/snd-hda-tools/hda_codec.py, line 1036, in __init__
self.parse_proc()
  File /usr/share/snd-hda-tools/hda_codec.py, line 1135, in parse_proc
self.proc_codec = HDACodecProc(self.card, self.device, file)
  File /usr/share/snd-hda-tools/hda_proc.py, line 479, in __init__
self.parse(proc_file)
  File /usr/share/snd-hda-tools/hda_proc.py, line 677, in parse
node.add_digital(line[11:]) 
  File /usr/share/snd-hda-tools/hda_proc.py, line 296, in add_digital
self.wrongfile('unknown dig1 bit %s' % repr(b))
  File /usr/share/snd-hda-tools/hda_proc.py, line 143, in wrongfile
raise ValueError, wrong proc file format (%s) % msg
ValueError: wrong proc file format (unknown dig1 bit 'KAE')

So not really sure where to go from here.  I opened up hdajackretask to find 
four pins:
Green Headphone
Pin ID: 0x10
Headphone

Internal Speaker
Pin ID: 0x12
Internal speaker

Pink Mic
Pin ID: 0x18
Not connected

Internal Mic
Pin ID: 0x1c
Internal mic

Unplugging and replugging the headset changes the Output device in sound
settings from Headphones to Speakers so that works, but nothing in the
input tab ever changes.  It always lists two devices:  Internal
Microphone and Microphone.  Both of these seem to actually be the
internal microphone in the mac - either works without the headset
connected at all.

So I'm not really sure how to proceed from here, but I'd be happy to run
whatever diagnostic tests might prove useful and/or even contribute code
toward a fix - but I just have no idea where to start.  Is it as simple
as just finding the right pin and telling the system to use it as a
microphone?

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

Title:
  [Macbook Air 3,2] headset mic not recognized

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  == Summary ==
  Since upgrading a MacBook Air from 11.10 to 12.04 the headset microphone is 
no longer recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon1864 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xd328 irq 16'
     Mixer name : 'Nvidia MCP89 HDMI'
     Components : 'HDA:10134206,106b3d00,00100301 
HDA:10de000c,10de0101,00100200'
     Controls  : 36
     Simple ctrls  : 12
  Date: Thu Mar  8 21:09:23 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64+mac 
(20111012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: Upgraded to precise on 2012-03-05 (3 days ago)
  dmi.bios.date: 11/18/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA31.88Z.0061.B01.1011181342
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-942C5DF58193131B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir3,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942C5DF58193131B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B:
  dmi.product.name: MacBookAir3,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1069064] Re: Screen keeps blinking after boot up

[Bug Watch Updater]

** Changed in: xorg (openSUSE)
   Status: In Progress = Won't Fix

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

Title:
  Screen keeps blinking after boot up

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in openSUSE:
  Won't Fix

Bug description:
  Hi,

  I tried installing ubuntu quantal on my acer 5002 laptop with sis
  card. But on boot from usb screen keeps flickering with only mouse
  pointer shows up on whole screen.

  I tried xubuntu as well and result is same.
  --- 
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  Package: xorg 1:7.6+12ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Tags:  precise ubuntu
  Uname: Linux 3.2.0-32-generic-pae i686
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1406925] Re: lxc-start fails due to insufficient permission for creating netdev

[Serge Hallyn]

(Note that I cannot reproduce this here;  sudo lxc-create -t ubuntu -n
p1 -- -r precise -a i386 results in a working container for me.  So we
need to figure out what is differnet in your environment.)

** Changed in: lxc (Ubuntu)
   Status: New = Incomplete

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

Title:
  lxc-start fails due to insufficient permission for creating netdev

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  After installing an lxc with `sudo lxc-create -n Ubuntu-12.04.5-i386
  -t /usr/share/lxc/templates/lxc-ubuntu -- --release precise --mirror
  http://richtercloud.de:3142/de.archive.ubuntu.com/ubuntu --arch i386`,
  starting the container with `sudo lxc-start -n Ubuntu-12.04.5-i386
  --foreground` fails due to the following error:

  lxc-start: conf.c: instanciate_veth: 2817 failed to attach 'vethY1J1I1' 
to the bridge 'lxcbr0' : Operation not permitted
  lxc-start: conf.c: lxc_create_network: 3100 failed to create netdev
  lxc-start: start.c: lxc_spawn: 829 failed to create the network
  lxc-start: start.c: __lxc_start: 1087 failed to spawn 
'Ubuntu-12.04.5-i386'
  lxc-start: lxc_start.c: main: 337 The container failed to start.
  lxc-start: lxc_start.c: main: 341 Additional information can be obtained 
by setting the --logfile and --logpriority options.

  It should be possible to start the container right away after
  installation of the apt package and handle eventually necessary setup
  tasks (of permissions, etc.) in `debconf`.

  Currently it's necessary to comment out all `lxc.network.*` entries in
  the container configuration file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lxc 1.1.0~alpha2-0ubuntu3
  ProcVersionSignature: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/proc/version_signature'
  Uname: Linux 3.17.7-031707-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  1 14:31:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to utopic on 2014-12-28 (4 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  upstart.lxc-net.override: manual

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

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

[Touch-packages] [Bug 1409166] [NEW] Can't add monitor: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 65

[Neal McBurnett]

Public bug reported:

My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.  I
had the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned above
it.  From Settings I tried to add a Samsung monitor to the right of the
Viewsonic, via a DVI-to-HDMI passive connector, and got this dialog box
when I hit Apply:

   The selected configuration for displays could not be applied
   could not set the configuration for CRTC 65

I clicked OK and got another dialog box:
   Failed to apply configuration: %s
   Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

Previously it had worked to set up all three like this.

This is on Trusty 64-bit, up-to-date with upgrades.
 
This bug seems similar to #1304627, but it seemed cleanest to get all the right 
information reported via ubuntu-bug.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jan  9 15:35:57 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2203]
InstallationDate: Installed on 2015-01-01 (8 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET96WW (2.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET96WW(2.56):bd10/22/2013:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Jan  8 07:07:01 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2.6

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

Title:
  Can't add monitor:
  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
  could not set the configuration for CRTC 65

Status in xorg package in Ubuntu:
  New

Bug description:
  My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.
  I had the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned
  above it.  From Settings I tried to add a Samsung monitor to the right
  of the Viewsonic, via a DVI-to-HDMI passive connector, and got this
  dialog box when I hit Apply:

 The selected configuration for displays could not be applied
 could not set the configuration for CRTC 65

  I clicked OK and got another dialog box:
 Failed to apply configuration: %s
 Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

  Previously it had worked to set up all three like this.

  This is on Trusty 64-bit, up-to-date with 

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Colan Schwartz]

I somewhat like the idea of tagging this as a security issue.  Maybe
that'll get more traction.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Compiz:
  New
Status in Accelerated Xorg driver for nVidia cards:
  New
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in binary-driver-fglrx package in Ubuntu:
  New
Status in intel-linux-graphics-installer package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in binary-driver-fglrx source package in Precise:
  New
Status in intel-linux-graphics-installer source package in Precise:
  New
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Precise:
  New
Status in binary-driver-fglrx source package in Quantal:
  New
Status in intel-linux-graphics-installer source package in Quantal:
  New
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix
Status in xserver-xorg-video-nouveau source package in Quantal:
  New

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Pat McGowan]

acceptableInput would work if the validator was extended to include a
length check

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1409047] [NEW] Bluetooth audio not working with Volvo multimedia

[Jonas G. Drange]

Public bug reported:

Calls work just fine, which is in the Telephone part of the car's UI.
When changing to Multimedia mode and pairing with a Nexus 4, no audio is 
played, nor is any audio playable later through the phone's own speakers.

This is a 2012 Volvo S60 (Norwegian)

Steps to reproduce:
1. Pair with car multimedia system
2. Confirm that the car display shows Playing on Nexus 4 (or something to 
that effect)
3. Play song

What I expected to happen:
Audio should have been played through the car's speakers

What happened instead:
No audio was played
Playing any audio, even after turning off bluetooth, does not work

Phone:
mako using Vivid @ r58

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

** Description changed:

  Calls work just fine, which is in the Telephone part of the car's UI.
  When changing to Multimedia mode and pairing with a Nexus 4, no audio is 
played, nor is any audio playable later through the phone's own speakers.
  
  This is a 2012 Volvo S60 (Norwegian)
  
  Steps to reproduce:
  1. Pair with car multimedia system
- 2. Play song
+ 2. Confirm that the car display shows Playing on Nexus 4 (or something to 
that effect)
+ 3. Play song
  
  What I expected to happen:
  Audio should have been played through the car's speakers
  
  What happened instead:
  No audio was played
  Playing any audio, even after turning off bluetooth, does not work
  
  Phone:
  mako using Vivid @ r58

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

Title:
  Bluetooth audio not working with Volvo multimedia

Status in bluez package in Ubuntu:
  New

Bug description:
  Calls work just fine, which is in the Telephone part of the car's UI.
  When changing to Multimedia mode and pairing with a Nexus 4, no audio is 
played, nor is any audio playable later through the phone's own speakers.

  This is a 2012 Volvo S60 (Norwegian)

  Steps to reproduce:
  1. Pair with car multimedia system
  2. Confirm that the car display shows Playing on Nexus 4 (or something to 
that effect)
  3. Play song

  What I expected to happen:
  Audio should have been played through the car's speakers

  What happened instead:
  No audio was played
  Playing any audio, even after turning off bluetooth, does not work

  Phone:
  mako using Vivid @ r58

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

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

[Touch-packages] [Bug 1319655] Re: getopt example in docs incorrectly implies /bin/sh may not be used (PATCH)

[Launchpad Bug Tracker]

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

** Changed in: util-linux (Ubuntu)
   Status: New = Confirmed

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

Title:
  getopt example in docs incorrectly implies /bin/sh may not be used
  (PATCH)

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  getopt(1) works with /bin/sh, bash, and probably other Bourne-ish
  shells (as well as csh-family shells with the appropriate option).

  However the included examples give the impression that something about
  getopt(1) makes it incompatible with /bin/sh, leading one to assume
  that scripts MUST use bash instead of sh.The author probably meant
  merely that the bash example would not work with tcsh; however less-
  experienced script writers might not find that to be obvious.

  First of all, the Bourne-syntax example unnecessarily uses bash, i.e.
  leading one to wonder why the more-universal sh shell could not be
  used.   And there is a comment in the example saying This program
  will only work with bash(1).

  
  SUGGESTED IMPROVEMENT (patch attached):

  . Rename /usr/share/doc/util-linux/examples/getopt-parse.bash to
  getopt-parse.sh

  . Change the example to use /bin/sh instead of bash, and change the
  comment to say that that example works only with sh-compatible shells,
  including bash.


  P.S.  The --shell option to getopt(1) accepts arguments 'sh', 'bash',
  'csh', and 'tcsh', however internally there is no difference between
  'sh' and 'bash' (or between 'csh' and 'tcsh').   See source code at
  https://kernel.googlesource.com/pub/scm/utils/util-linux/util-
  linux/+/v2.22.2/misc-utils/getopt.c

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: util-linux 2.20.1-5.1ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed May 14 21:00:48 2014
  InstallationDate: Installed on 2013-08-06 (282 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to saucy on 2013-10-24 (202 days ago)

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

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

[Touch-packages] [Bug 1405691] Re: No sound from subwoofer on Asus N551JM

[Launchpad Bug Tracker]

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

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

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

Title:
  No sound from subwoofer on Asus N551JM

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On Asus N551JM there is no sound from external subwoofer on fresh
  Kubuntu 14.10 installation. There is no Bass speaker in alsamixer.
  Adding options snd-hda-intel model=asus-mode4 to /etc/modprobe.d
  /alsa-base.conf makes Bass speaker appears in alsamixer but I was
  unable to make it play any sound. On Win8 works out-of-box.

  Alsa-base version: 1.0.25+dfsg-0ubuntu4.

  Howto fix: redirect pin 0x1a to Internal speaker (back) using
  HDAJackRetask on codec Realtek ALC668. Contents of /lib/firmware/hda-
  jack-retask.fw:

  [codec]
  0x10ec0668 0x1043177d 0

  [pincfg]
  0x12 0x90a60130
  0x14 0x90170110
  0x15 0x04211020
  0x16 0x4000
  0x18 0x41f0
  0x19 0x41f0
  0x1a 0x90170152
  0x1b 0x41f0
  0x1d 0x40c6832d
  0x1e 0x41f0
  0x1f 0x41f0

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

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

[Touch-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs

[Ted Gould]

** Also affects: url-dispatcher (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: url-dispatcher (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: url-dispatcher (Ubuntu)
   Status: New = In Progress

** Changed in: url-dispatcher (Ubuntu RTM)
   Status: New = In Progress

** Changed in: url-dispatcher (Ubuntu)
 Assignee: (unassigned) = Ted Gould (ted)

** Changed in: url-dispatcher (Ubuntu RTM)
 Assignee: (unassigned) = Ted Gould (ted)

** Branch linked: lp:~ted/url-dispatcher/intent-pkg-domain

** Branch linked: lp:~ted/url-dispatcher/intent-pkg-domain-trunk

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

Title:
  Google Maps and Here Maps should handle custom intent:// URLs

Status in The Webapps-core project:
  New
Status in Web Browser App:
  New
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu RTM:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Invalid

Bug description:
  ubuntu-rtm image 184

  The maps apps in the system should register and respond to appropriate
  urls from the browser (not sure of the format, map:// or directions://
  - need to check)

  Steps to reproduce:
  1) open browser
  2) type Asai Belmont MA in the url bar and press enter
  3) this will do a google search for the resturant
  4) click on the Directions button

  Expected result:
  - One of the maps apps should open displaying directions for the resturant

  Actual results:
  - no app is launched

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

-- 
Mailing list: https://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 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Jonas G. Drange]

ken.vand...@canonical.com wrote:

 A slight improvement, instead of changing confirmButton.enabled with
 onTextChanged, you can use the acceptableInput property to control
 enabled for confirmButton.

Do we get a chance to restrict passcode input to exactly four digits, then?
The input mask did this for us, while the IntValidator does not.
​

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

-- 
Mailing list: https://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 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Jonas G. Drange]

Maybe we'll just change bottom to 1000.

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Pat McGowan]

We can define a custom validator, not sure if there is also a way to
combine validators

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Launchpad Bug Tracker]

** Branch linked: lp:~jonas-drange/ubuntu-system-settings/security-pass-
input-fix-1357548

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1404304] Re: placing a second call from messaging-app/address-book does not work

[Launchpad Bug Tracker]

This bug was fixed in the package dialer-app -
0.1+15.04.20150108-0ubuntu1

---
dialer-app (0.1+15.04.20150108-0ubuntu1) vivid; urgency=low

  [ Tiago Salem Herrmann ]
  * Emergency mode refactor. Use two page stacks: one for normal mode
and another for emergency mode. (LP: #1404304, #1359337, #1400836)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 08 Jan 2015 
21:30:49 +

** Changed in: dialer-app (Ubuntu)
   Status: New = Fix Released

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

Title:
  placing a second call from messaging-app/address-book does not work

Status in Dialer app for Ubuntu Touch:
  New
Status in dialer-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu RTM:
  New

Bug description:
  rtm build 184

  Steps to reproduce:
  - open dialer app and make a call
  - wait until the call is active
  - Switch to messaging app or contacts app
  - select a contact from either app, expand the contact and press the Call 
icon

  Expected results:
  - the dialer app should move to the foreground and show the keypad view with 
the number populated

  Actual results:
  - the dialer app moves to the foreground and shows the existing live call view

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1404304/+subscriptions

-- 
Mailing list: https://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 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Jonas G. Drange]

How though? There is no Validator qml element, nor does IntValidator expose
anything of interest [1].

[1] http://doc.qt.io/qt-5/qml-qtquick-intvalidator-members.html

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1372061] Re: SMS notification: time format not translatable

[Michał Sawicz]

** Branch linked: lp:~nick-dedekind/ubuntu-ui-toolkit/lp1378821.time-
translation

** Branch linked: lp:~nick-dedekind/ubuntu-settings-components/lp1378821
.time-translation

** Branch linked: lp:~nick-dedekind/unity8/lp1378821.time-translation

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

** Also affects: ubuntu-settings-components (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New = In Progress

** Changed in: ubuntu-settings-components (Ubuntu)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

Title:
  SMS notification: time format not translatable

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu Translations:
  Triaged
Status in telephony-service package in Ubuntu:
  Invalid
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in ubuntu-settings-components package in Ubuntu RTM:
  New
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  See the attached screenshot. The time for the notification seems to be
  hardcoded to hh:mm - mm, d. This works well for the US, but it's not
  a format that is used in all other countries. In Spain, for example,
  the date would rather be d mm.

  The time format needs to be marked for translation.

  Not sure from which project the notifications come from, for some
  reason I seem to remember they were moved to u-s-s, but if it's the
  wrong project/package, please reassign. Thanks!

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

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

[Touch-packages] [Bug 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Pat McGowan]

acceptableInput doesn't ensure 4 digits which is why I used the length check, 
and there is no way to specify minimum length.
Using 1000 as a bottom would not allow a 0 in the first digit so do not think 
that works.

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1366829] Re: 7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ

[Paul Donohue]

Pull request has been accepted upstream.

Since there are now a bunch of upstream commits involved in the complete
fix, I'm attaching an updated 11-fix-infinite-loop-openvz-vms.patch file
for the ubuntu packages which contains all the necessary changes.

I also posted updated ubuntu package branches here: 
https://code.launchpad.net/~s-launchpad-paulsd-com/rsyslog/
But feel free to ignore my branch merge requests if you would prefer to update 
the package branches yourself.

** Patch added: 11-fix-infinite-loop-openvz-vms.patch
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+attachment/4294715/+files/11-fix-infinite-loop-openvz-vms.patch

** Patch removed: imklog.patch
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+attachment/4294218/+files/imklog.patch

** Patch removed: Upstream fix
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+attachment/4254548/+files/patch

** Patch removed: imkmsg.patch
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+attachment/4294219/+files/imkmsg.patch

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

Title:
  7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  Fix Committed
Status in rsyslog source package in Utopic:
  Fix Committed

Bug description:
  Test Case
  -
  * Install rsyslog 7.4.4-1ubuntu2.1 on an Ubuntu system that runs inside an 
OpenVZ container (If necessary, use ProxMox to quickly establish an OpenVZ 
container environment)
  * Verify that '$KLogPermitNonKernelFacility on' is set in /etc/rsyslog.conf
  * Restart rsyslog to make sure any changes to the binaries/config are picked 
up
  * Run 'top' and observe that the rsyslogd process is running at 100% CPU. 
When working properly, the rsyslogd process should generally be idle.

  -

  After updating  rsyslog from 7.4.4-1ubuntu2 to 7.4.4-1ubuntu2.1 the rsyslogd 
process started to take all the CPU on my machine.
  The modification made by this release is described in #127, it is the 
activation of KLogPermitNonKernelFacility option.
  I don't know exactly the effect of this option but it seems to have a 
permanent effect : even after downgrading the package or manually removing the 
option from /etc/rsyslog.conf the issue remains.
  My syslog is full of :
  Sep  8 10:28:40 sentry rsyslogd: imklog: error reading kernel log - shutting 
down: Bad file descriptor
  Sep  8 10:28:40 sentry rsyslogd: message repeated 498 times: [imklog: error 
reading kernel log - shutting down: Bad file descriptor]
  Sep  8 10:28:46 sentry rsyslogd-2177: rsyslogd[internal_messages]: 519517 
messages lost due to rate-limiting
  I guess this is what causes the CPU load.

  I am running Ubuntu 14.04.1 LTS in an OpenVZ container on Proxmox 3.2. The 
kernel is 2.6.32-28-pve
  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.1
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 2.6.32-28-pve x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Colan Schwartz]

If this bug has been fixed, maybe we should push for bug #989588?
That's the only other one that's still open.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 1319655] Re: getopt example in docs incorrectly implies /bin/sh may not be used (PATCH)

[Ubuntu Foundations Team Bug Bot]

The attachment patch.txt seems to be a patch.  If it isn't, please
remove the patch flag from the attachment, remove the patch tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  getopt example in docs incorrectly implies /bin/sh may not be used
  (PATCH)

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  getopt(1) works with /bin/sh, bash, and probably other Bourne-ish
  shells (as well as csh-family shells with the appropriate option).

  However the included examples give the impression that something about
  getopt(1) makes it incompatible with /bin/sh, leading one to assume
  that scripts MUST use bash instead of sh.The author probably meant
  merely that the bash example would not work with tcsh; however less-
  experienced script writers might not find that to be obvious.

  First of all, the Bourne-syntax example unnecessarily uses bash, i.e.
  leading one to wonder why the more-universal sh shell could not be
  used.   And there is a comment in the example saying This program
  will only work with bash(1).

  
  SUGGESTED IMPROVEMENT (patch attached):

  . Rename /usr/share/doc/util-linux/examples/getopt-parse.bash to
  getopt-parse.sh

  . Change the example to use /bin/sh instead of bash, and change the
  comment to say that that example works only with sh-compatible shells,
  including bash.


  P.S.  The --shell option to getopt(1) accepts arguments 'sh', 'bash',
  'csh', and 'tcsh', however internally there is no difference between
  'sh' and 'bash' (or between 'csh' and 'tcsh').   See source code at
  https://kernel.googlesource.com/pub/scm/utils/util-linux/util-
  linux/+/v2.22.2/misc-utils/getopt.c

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: util-linux 2.20.1-5.1ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed May 14 21:00:48 2014
  InstallationDate: Installed on 2013-08-06 (282 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to saucy on 2013-10-24 (202 days ago)

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

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

[Touch-packages] [Bug 1309247] Re: Cannot add any account using Online Accounts on 14.04

[Davide Mannarelli]

Same bugs like Carla Sella.
I noted this: istalling and logging in gnome-shell the problem disappear 
because the system don't use online-accounts-preferences.

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

Title:
  Cannot add any account using Online Accounts on 14.04

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  When attempting to add an account i.e: facebook, google, etc., the
  first thing that pops out is Please authorize your Facebook account
  but there's only a blank page. The page does not load.

  Using Ubuntu 14.04

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

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

[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)

[Daniel van Vugt]

The problem could also be the incorrect selection of a MirPixelFormat.

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

Title:
  Ubuntu Desktop Next fails to start; just black screen and mouse
  pointer (unity8.log: std::exception::what: Failed to create shared EGL
  context)

Status in Mir:
  Invalid
Status in Qt integration with the Mir display server:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Desktop Next fails to start. I just get a black screen and mouse 
pointer. So unity-system-compositor is working fine. Only the nested unity8 
can't run:
  unity8.log: std::exception::what: Failed to create shared EGL context

  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.

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

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

[Touch-packages] [Bug 1408931] [NEW] screen flickers and dies

[Kahztiy]

Public bug reported:

the screen flickers and dies while in a shaded mode the background can
be visible while plugged in to an external screen resolves the fault(?)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/1'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec  1 19:58:28 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
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 Jan  9 09:52:30 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G98M [GeForce 9200M GS] [10de:06e8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell Device [1028:0271]
 NVIDIA Corporation C79 [GeForce 9400M G] [10de:0866] (rev b1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Device [1028:0271]
InstallationDate: Installed on 2014-06-12 (210 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Dell Inc. Studio XPS 1340
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=9fbe7da3-1b46-429c-ad85-741ee3aa20bb ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.asset.tag: 1234567890
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd04/08/2011:svnDellInc.:pnStudioXPS1340:pvrA15:rvnDellInc.:rn:rvrA15:cvnDellInc.:ct8:cvrA15:
dmi.product.name: Studio XPS 1340
dmi.product.version: A15
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jan  9 09:44:31 2015
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/fb0: No such file or directory
 open /dev/dri/card2: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.6

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

Title:
  screen flickers and dies

Status in xorg package in Ubuntu:
  New

Bug description:
  the screen flickers and dies while in a shaded mode the background can
  be visible while plugged in to an external screen resolves the
  fault(?)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/1'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec  1 19:58:28 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  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 Jan  9 09:52:30 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  

[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)

[Daniel van Vugt]

I'm not quite sure what QtMir is doing to trigger this. I've tried hacks
to Mir directly to try and emulate what it might be doing, but my hacks
result in nested servers starting and running perfectly still.

Something about QtMir I'm failing to emulate...

** Tags added: nested

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

Title:
  Ubuntu Desktop Next fails to start; just black screen and mouse
  pointer (unity8.log: std::exception::what: Failed to create shared EGL
  context)

Status in Mir:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Desktop Next fails to start. I just get a black screen and
  mouse pointer. So unity-system-compositor is working fine. Only the
  nested unity8 can't run:

  unity8.log:
  ~~~
  ()
  [1420794321.348507] (II) SharedLibrary: Loading libmirplatform5driver.so
  qtmir.mir: MirServer created
  [1420794321.423199] (II) Server: Starting
  libEGL warning: unsupported platform (null)
  ERROR: 
/build/buildd/mir-0.10.0+15.04.20150107.2/src/server/graphics/nested/nested_display.cpp(85):
 Throw in function void 
mir::graphics::nested::detail::EGLDisplayHandle::initialize(MirPixelFormat)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: Failed to create shared EGL context

  ERROR: QMirServer - Mir failed to start
  terminate called after throwing an instance of 
'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::logic_error
 '
what():  Cannot use configuration before apply_settings() call
  ~~~

  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.

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

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

[Touch-packages] [Bug 1408593] Re: X server disables acceleartion or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid)

[Wladimir Mutel]

booted this : linux-image-3.19.0-031900rc3-generic  
3.19.0-031900rc3.201501060135
with this : xserver-xorg-video-intel  2:2.99.916+git20141119-1~exp1ubuntu1

they work well, with all desktop effects.
so this is isolated to 3.18

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

Title:
  X server disables acceleartion or turns off output (makes screen
  black) after kernel upgrade to v3.18 (Ubuntu Vivid)

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after reboot into kernel 3.18 (3.18.0-8.9)

  with Intel driver version 2:2.99.916+git20141119-1~exp1ubuntu1 it disables 
output / blacks the screen and puts in the log :
  [37.179] (II) GLX: Initialized DRI2 GL provider for screen 0
  [37.215] (WW) intel(0): Failed to submit rendering commands, trying again 
with outputs disabled.
  (then refuses to switch local VTs both by [Ctrl-]Alt-Fn and by chvt in remote 
logins)

  after reverting to 2:2.99.914-1~exp1ubuntu6 it puts :
  [41.679] (II) GLX: Initialized DRI2 GL provider for screen 0
  [41.711] (EE) intel(0): Failed to submit rendering commands, disabling 
acceleration.
  (then allows to log in bu with desktop composition effects disabled)

  after reboot back into kernel 3.16.0-28.38 , both *.916 and *.914
  drivers work well

  probably this bug should also be attached to kernel package v3.18

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan  8 11:23:52 2015
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mwg1214 F pulseaudio
  CRDA:
   country UA: DFS-UNSET
(2400 - 2483 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(5150 - 5350 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: Acer Aspire 
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=9bc29087-2e9e-4bf9-bea1-2540902b5ae3 ro rootflags=commit=3600 
transparent_hugepage=always init=/lib/systemd/systemd
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.140
  Tags:  vivid vivid
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout disk kvm lpadmin netdev plugdev 
sambashare src
  _MarkForUpload: True
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV10_CS
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)

[Daniel van Vugt]

Reproduced on a third machine, where I could get a copy of the log file
off.

** Description changed:

- Ubuntu Desktop Next fails to start. I just get a black screen and mouse 
pointer. So unity-system-compositor is working fine. Only the nested unity8 
can't run:
- unity8.log: std::exception::what: Failed to create shared EGL context
+ Ubuntu Desktop Next fails to start. I just get a black screen and mouse
+ pointer. So unity-system-compositor is working fine. Only the nested
+ unity8 can't run:
+ 
+ unity8.log:
+ ~~~
+ ()
+ [1420794321.348507] (II) SharedLibrary: Loading libmirplatform5driver.so
+ qtmir.mir: MirServer created
+ [1420794321.423199] (II) Server: Starting
+ libEGL warning: unsupported platform (null)
+ ERROR: 
/build/buildd/mir-0.10.0+15.04.20150107.2/src/server/graphics/nested/nested_display.cpp(85):
 Throw in function void 
mir::graphics::nested::detail::EGLDisplayHandle::initialize(MirPixelFormat)
+ Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
+ std::exception::what: Failed to create shared EGL context
+ 
+ ERROR: QMirServer - Mir failed to start
+ terminate called after throwing an instance of 
'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::logic_error
 '
+   what():  Cannot use configuration before apply_settings() call
+ ~~~
  
  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.

** Attachment added: unity8.log
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408910/+attachment/4294511/+files/unity8.log

** Changed in: mir
   Status: Invalid = Incomplete

** Changed in: mir
   Status: Incomplete = Confirmed

** Changed in: qtmir
   Status: Triaged = Confirmed

** Changed in: qtmir (Ubuntu)
   Status: Triaged = Confirmed

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Confirmed

** Changed in: mir
Milestone: None = 0.11.0

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

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

Title:
  Ubuntu Desktop Next fails to start; just black screen and mouse
  pointer (unity8.log: std::exception::what: Failed to create shared EGL
  context)

Status in Mir:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Desktop Next fails to start. I just get a black screen and
  mouse pointer. So unity-system-compositor is working fine. Only the
  nested unity8 can't run:

  unity8.log:
  ~~~
  ()
  [1420794321.348507] (II) SharedLibrary: Loading libmirplatform5driver.so
  qtmir.mir: MirServer created
  [1420794321.423199] (II) Server: Starting
  libEGL warning: unsupported platform (null)
  ERROR: 
/build/buildd/mir-0.10.0+15.04.20150107.2/src/server/graphics/nested/nested_display.cpp(85):
 Throw in function void 
mir::graphics::nested::detail::EGLDisplayHandle::initialize(MirPixelFormat)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: Failed to create shared EGL context

  ERROR: QMirServer - Mir failed to start
  terminate called after throwing an instance of 
'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::logic_error
 '
what():  Cannot use configuration before apply_settings() call
  ~~~

  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.

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

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

[Touch-packages] [Bug 1404068] Re: No internet connection with Huawei E3272 4G modem

[Bug Watch Updater]

** Changed in: usb-modeswitch-data (Debian)
   Status: Unknown = Fix Released

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

Title:
  No internet connection with Huawei E3272 4G modem

Status in ModemManager (with NetworkManager support):
  Unknown
Status in modemmanager package in Ubuntu:
  New
Status in usb-modeswitch-data package in Ubuntu:
  Invalid
Status in usb-modeswitch-data package in Debian:
  Fix Released

Bug description:
  There is no internet connection. My mobile broadband LTE modem is Huawei 
E3272. Attached a syslog.
  Ubuntu 14.10
  modemmanager 1.2.0-1

  This might contain useful information:
  http://askubuntu.com/questions/525965/huawei-e3272-ubuntu

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

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

[Touch-packages] [Bug 1404068] Re: No internet connection with Huawei E3272 4G modem

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=88224.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-01-09T08:15:21+00:00 Marius B. Kotsbak wrote:

See downstream bug report and attached MM log files at
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1404068

reproduced up to ModemManager 1.4.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1404068/comments/10


On 2015-01-09T08:16:09+00:00 Marius B. Kotsbak wrote:

From the logs, it seems like there is some issue detecting/configuring
the network interface of the modem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1404068/comments/11


** Changed in: modemmanager
   Status: Unknown = Confirmed

** Changed in: modemmanager
   Importance: Unknown = Medium

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

Title:
  No internet connection with Huawei E3272 4G modem

Status in ModemManager (with NetworkManager support):
  Confirmed
Status in modemmanager package in Ubuntu:
  New
Status in usb-modeswitch-data package in Ubuntu:
  Invalid
Status in usb-modeswitch-data package in Debian:
  Fix Released

Bug description:
  There is no internet connection. My mobile broadband LTE modem is Huawei 
E3272. Attached a syslog.
  Ubuntu 14.10
  modemmanager 1.2.0-1

  This might contain useful information:
  http://askubuntu.com/questions/525965/huawei-e3272-ubuntu

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

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

[Touch-packages] [Bug 1408593] Re: X server disables acceleartion or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid)

[Wladimir Mutel]

** Tags added: kernel-fixed-upstream

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

Title:
  X server disables acceleartion or turns off output (makes screen
  black) after kernel upgrade to v3.18 (Ubuntu Vivid)

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after reboot into kernel 3.18 (3.18.0-8.9)

  with Intel driver version 2:2.99.916+git20141119-1~exp1ubuntu1 it disables 
output / blacks the screen and puts in the log :
  [37.179] (II) GLX: Initialized DRI2 GL provider for screen 0
  [37.215] (WW) intel(0): Failed to submit rendering commands, trying again 
with outputs disabled.
  (then refuses to switch local VTs both by [Ctrl-]Alt-Fn and by chvt in remote 
logins)

  after reverting to 2:2.99.914-1~exp1ubuntu6 it puts :
  [41.679] (II) GLX: Initialized DRI2 GL provider for screen 0
  [41.711] (EE) intel(0): Failed to submit rendering commands, disabling 
acceleration.
  (then allows to log in bu with desktop composition effects disabled)

  after reboot back into kernel 3.16.0-28.38 , both *.916 and *.914
  drivers work well

  probably this bug should also be attached to kernel package v3.18

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan  8 11:23:52 2015
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mwg1214 F pulseaudio
  CRDA:
   country UA: DFS-UNSET
(2400 - 2483 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(5150 - 5350 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: Acer Aspire 
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=9bc29087-2e9e-4bf9-bea1-2540902b5ae3 ro rootflags=commit=3600 
transparent_hugepage=always init=/lib/systemd/systemd
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.140
  Tags:  vivid vivid
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout disk kvm lpadmin netdev plugdev 
sambashare src
  _MarkForUpload: True
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV10_CS
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1408924] [NEW] [7G-Series, Realtek ALC282, Speaker, Internal] No sound at all

[Mureed Hussain]

Public bug reported:

No sound

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hussain1851 F pulseaudio
 /dev/snd/controlC1:  hussain1851 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jan  9 13:06:33 2015
InstallationDate: Installed on 2014-11-14 (55 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hussain1851 F pulseaudio
 /dev/snd/controlC1:  hussain1851 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [7G-Series, Realtek ALC282, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to trusty on 2014-11-26 (43 days ago)
dmi.bios.date: 05/08/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: KQ122
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: JWU
dmi.board.vendor: Quanta
dmi.board.version: 01
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: US
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrKQ122:bd05/08/2014:svnHaierComputer:pn7G-Series:pvr03:rvnQuanta:rnJWU:rvr01:cvnQuanta:ct10:cvrUS:
dmi.product.name: 7G-Series
dmi.product.version: 03
dmi.sys.vendor: HaierComputer

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


** Tags: amd64 apport-bug trusty

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

Title:
  [7G-Series, Realtek ALC282, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hussain1851 F pulseaudio
   /dev/snd/controlC1:  hussain1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan  9 13:06:33 2015
  InstallationDate: Installed on 2014-11-14 (55 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hussain1851 F pulseaudio
   /dev/snd/controlC1:  hussain1851 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [7G-Series, Realtek ALC282, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-11-26 (43 days ago)
  dmi.bios.date: 05/08/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: KQ122
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: JWU
  dmi.board.vendor: Quanta
  dmi.board.version: 01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: US
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrKQ122:bd05/08/2014:svnHaierComputer:pn7G-Series:pvr03:rvnQuanta:rnJWU:rvr01:cvnQuanta:ct10:cvrUS:
  dmi.product.name: 7G-Series
  dmi.product.version: 03
  dmi.sys.vendor: HaierComputer

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

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

[Touch-packages] [Bug 1408910] Re: Ubuntu Desktop Next fails to start; just black screen and mouse pointer (unity8.log: std::exception::what: Failed to create shared EGL context)

[Daniel van Vugt]

** Description changed:

  Ubuntu Desktop Next fails to start. I just get a black screen and mouse 
pointer. So unity-system-compositor is working fine. Only the nested unity8 
can't run:
  unity8.log: std::exception::what: Failed to create shared EGL context
  
  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.
- 
- I think this might be a new issue introduced by the upgrade to Mir 0.10
- last night?

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

Title:
  Ubuntu Desktop Next fails to start; just black screen and mouse
  pointer (unity8.log: std::exception::what: Failed to create shared EGL
  context)

Status in Mir:
  Invalid
Status in Qt integration with the Mir display server:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Desktop Next fails to start. I just get a black screen and mouse 
pointer. So unity-system-compositor is working fine. Only the nested unity8 
can't run:
  unity8.log: std::exception::what: Failed to create shared EGL context

  I've also verified mir_proving_server with mir_demo_client_* runs fine
  in another VT.

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

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

[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Geert Uytterhoeven]

Same problem here:
  - No LDAP
  - Dual-monitor setup (Intel HD graphics in i7-4770)
  - Usually two users are logged in graphically (VC 7 and 8)
  - Usually it starts happening for the second user (VC 8):
  - The box on the locked screen shows the user's name,
  - The box does not show the password entry field,
  - There are no icons shown in the top bar (i.e. no way to shutdown).
  - As long as the problem doesn't happen on the other VC, the session on the
problematic VC can be recovered by:
  - Switching to the still working VC (which is in locked screen mode),
  - Clicking on the icon in the upper right corner, and selection Switch
Account Directly selecting the right account in the menu does NOT
work, and merely switches to the problematic VC.
  - A new lightdm session appears. Log in with the account of the user
whose session has problems.
  - The system switches to the problematic VC, and unlocks it.
  - Logging in on text VC1 and running unity --replace unlocks the
problematic VC, but kills compiz.
  - Running compiz --replace in the graphical session restarts compiz, and
locks the screen again, now showing a password entry box.
  - After unlocking the screen, everything works again, but all open windows
have been been moved to the first desktop, so I have to untangle the desktop
clutter manually.

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

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the 
issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see 
comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not 
contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Touch-packages] [Bug 1408963] [NEW] [Kubuntu] Network manager stops working: wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING)

[Peter Ullinger]

Public bug reported:

From time to time, the system loses all wireles networks and kubuntu
network manager applet goes blank - not even one network is shown. All
wifi connections are broken. Rebooting fixes the issue, switching to
WICD on-the-fly enables to continue browsing without rebooting, so it
seems to be no hardware issue or iwl3945 issue.

What to expect: stable connections and flawless network managing.
What happens: so above.

Further informations about the system, the network configuration, the
package version can be found in the attachment, also parts of rsyslog
and dmesg.

Interesting, according to some helpers, are the following lines:
dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.10
Release:14.10
Codename:   utopic

apt-cache policy network-manager
network-manager:
  Installiert:   0.9.8.8-0ubuntu28
  Installationskandidat: 0.9.8.8-0ubuntu28
  Versionstabelle:
 *** 0.9.8.8-0ubuntu28 0
500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

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

** Attachment added: System informations, package informations, network 
informations, dmesg and rsyslog.
   
https://bugs.launchpad.net/bugs/1408963/+attachment/4294556/+files/wifi_failure

** Description changed:

  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
- WICD enables to continue browsing without rebooting, so it seems to be
- no hardware issue or iwl3945 issue.
+ WICD on-the-fly enables to continue browsing without rebooting, so it
+ seems to be no hardware issue or iwl3945 issue.
  
  What to expect: stable connections and flawless network managing.
- What happens: so above. 
+ What happens: so above.
  
  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.
  
  Interessting, acording to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  
- 
  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic
  
- 
  apt-cache policy network-manager
  network-manager:
-   Installiert:   0.9.8.8-0ubuntu28
-   Installationskandidat: 0.9.8.8-0ubuntu28
-   Versionstabelle:
-  *** 0.9.8.8-0ubuntu28 0
- 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installiert:   0.9.8.8-0ubuntu28
+   Installationskandidat: 0.9.8.8-0ubuntu28
+   Versionstabelle:
+  *** 0.9.8.8-0ubuntu28 0
+ 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
+ 100 /var/lib/dpkg/status

** Description changed:

  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.
  
  What to expect: stable connections and flawless network managing.
  What happens: so above.
  
  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.
  
- Interessting, acording to some helpers, are the following lines:
+ Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  
  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic
  
  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

Title:
  [Kubuntu] Network manager stops working: wlan0: deauthenticating
  from... by local choice (Reason: 3=DEAUTH_LEAVING)

Status in network-manager package in Ubuntu:
  New

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are 

[Touch-packages] [Bug 1408741] Re: [network indicator] tapping the currently connected wifi network cause connection to drop and reconnect

[Albert Astals Cid]

I personally like that, my BlackBerry Z10 does the same and it's
relatively useful with my broken router that sometimes from some reason
decides my phone is still connected but doesn't relay any of the traffic
anymore so i have to reconnect.

On the other hand my use case is a corner case because of my broken
hardware i guess :D

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

Title:
  [network indicator] tapping the currently connected wifi network cause
  connection to drop and reconnect

Status in Ubuntu UX bugs:
  New
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Not sure if this desirable or not, but I noticed when I opened the
  networking indicator, and tapped on the currently connected network
  (the green one) that the connection was broken and re-established.

  To see, open shell on device and run ping 8.8.8.8. Watch the output,
  then open network indicator and tap on the currently connected
  network. I see the pings fail for a few seconds.

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

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

[Touch-packages] [Bug 1234722] Re: Most video files are playing with audio only

[Karen]

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Most video files are playing with audio only

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Saucy:
  Won't Fix

Bug description:
  I recorded a video file from Galaxy Nexus (using android) and put it
  on my Ubuntu phone(mako). When I start the video I can only listen to
  the audio i.e. no video.

  1. Download the attached video and paste it in ~/Videos on the phone.
  2. login to the phone from adb, unlock the screen
  3. run: start application APP_ID=mediaplayer-app 
APP_URIS=~/Videos/VID_20131003_172149.mp4

  The mediaplayer comes up there is sound but no video. This was tested
  on mako.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gstreamer1.0-plugins-bad 1.2.0-3ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: armhf
  Date: Thu Oct  3 13:33:35 2013
  InstallationDate: Installed on 2013-10-03 (0 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20131003)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: gst-plugins-bad1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1234722/+subscriptions

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

[Touch-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes

[Stefan Leitner]

This bug looks like this one: https://bugs.launchpad.net/xorg-
server/+bug/1220426

workaround is to use a usb mouse instead of the touchpad.

Nikhil Mahale (nmahale) created a working patch:
https://bugs.launchpad.net/xorg-server/+bug/1220426/comments/171

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

Title:
  when enabled nvidia graphics card, desktop freezes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes occasionally while simply browsing the web, can be recovered 
by ctrl+alt+f1 and ctrl+alt+f7 
  This has been the case in 14.04, and it's still the case in 14.10 (64 bit)
  Asus UX32V
   331.89-0ubuntu5
   *** 331.89-0ubuntu5 0
  500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Oct 29 12:40:01 2014
  DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed
   bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507]
  InstallationDate: Installed on 2014-05-31 (150 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash 
processor.ignore_ppc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 29 12:00:13 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4931 
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

[Geert Uytterhoeven]

   - After unlocking the screen, everything works again, but all open windows
 have been been moved to the first desktop, so I have to untangle the 
 desktop
 clutter manually.

I spoke too soon.

During untangling my desktop after pressing Super-S, I noticed:
  - Some fullscreen evince windows don't want to be moved to another desktop,
they always pop back to desktop 0. It seems they have lost their 
close/minimize/
maximize icons, too.
  - Moving windows after Super-S is slower than usual, and sometimes complety
blocks, so I have to press Super-S twice to continue.
So I gave up and logged out, and can online recommend unity --replace and
compiz --replace to recover critical applications that had been left open.

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

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the 
issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see 
comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not 
contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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

[Touch-packages] [Bug 1408958] [NEW] Calendar alarm notifications have no buttons, on screen for short while

[Alan Pope ]

Public bug reported:

Using krillin #186 from ubuntu-touch/ubuntu-rtm/14.09-proposed
notifications of calendar events are broken.

Previously a calendar event with reminder would trigger a notification
with OK / Snooze buttons, but those buttons are no longer there. In
addition the notification is very short, so getting a screenshot for
this bug was challenging!

Steps to reproduce

1. Flash krillin with 186
2. Install Calendar app
3. Add a calendar entry for sometime soon with a reminder
4. Wait for the notification

Expected behaviour

Notification appears until some arbitrary time out or user clicks a
button

Actual behaviour

Notification appears without buttons, and only for a brief period.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: indicator-datetime 13.10.0+15.04.20141210~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Fri Jan  9 09:41:35 2015
InstallationDate: Installed on 2015-01-08 (1 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150108-030204)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug armhf utopic

** Attachment added: device-2015-01-09-094004.png
   
https://bugs.launchpad.net/bugs/1408958/+attachment/4294549/+files/device-2015-01-09-094004.png

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

Title:
  Calendar alarm notifications have no buttons, on screen for short
  while

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Using krillin #186 from ubuntu-touch/ubuntu-rtm/14.09-proposed
  notifications of calendar events are broken.

  Previously a calendar event with reminder would trigger a notification
  with OK / Snooze buttons, but those buttons are no longer there. In
  addition the notification is very short, so getting a screenshot for
  this bug was challenging!

  Steps to reproduce

  1. Flash krillin with 186
  2. Install Calendar app
  3. Add a calendar entry for sometime soon with a reminder
  4. Wait for the notification

  Expected behaviour

  Notification appears until some arbitrary time out or user clicks a
  button

  Actual behaviour

  Notification appears without buttons, and only for a brief period.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-datetime 13.10.0+15.04.20141210~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Jan  9 09:41:35 2015
  InstallationDate: Installed on 2015-01-08 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150108-030204)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1383870] Re: [phone-app] + [messaging-app] + [address-book-app] list tug actions should collapse after user moves view

[Andrew Hayzen]

** Also affects: music-app
   Importance: Undecided
   Status: New

** Changed in: music-app
 Assignee: (unassigned) = Andrew Hayzen (andrew-hayzen)

** Changed in: music-app
   Status: New = In Progress

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

Title:
  [phone-app] + [messaging-app] + [address-book-app] list tug actions
  should collapse after user moves view

Status in Address Book App:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Music application for Ubuntu devices:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  build r120

  Steps to reproduce:
  1. open phone app
  2. carry out a bottom edge swipe to access your RECENT
  3. swipe any list item to the left or right
  4. now scroll your list view a little bit down or up, make sure the list item 
actions stay in view

  Actual Result: the actions remain on the screen, they only collapse if
  it hides behind the header or bottom of the view

  Expected result: if user starts to scroll the list view while a list item 
shows additional actions, the list item should collapse.
  Users are carrying out a different actions in that case and are likely not 
being interested anymore in the revealed list item actions.

  Same behaviour applies for the messaging app and the address-book-app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1383870/+subscriptions

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

[Touch-packages] [Bug 1403045] Re: Bottom edge doesn't follow finger

[Michał Sawicz]

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

Title:
  Bottom edge doesn't follow finger

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  * start by quickly pulling up the bottom edge but do not release the finger
  * move the finger slowly up and down

  = the scopes list does follow the up/down movement, but is way off
  from the finger position

  expected:

  The top edge of the scopes list should stick to the finger's position

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

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

[Touch-packages] [Bug 1407620] Re: Large empty space above Manage header during bottom gesture

[Michał Sawicz]

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

Title:
  Large empty space above Manage header during bottom gesture

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Somewhat related to bug #1403045

  Steps:
  * touch the bottom of the screen
  * start moving up slowly

  Expected:
  * top edge of the Manage pane moves with your finger

  Current:
  * a large empty space appears at the bottom and moves with your finger

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20141216.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Mon Jan  5 10:50:14 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141218-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384950] Re: Trusted prompts need to be part of the lifecycle

[Pat McGowan]

part of  bug #1355173, per description

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None = ww03-2015

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

Title:
  Trusted prompts need to be part of the lifecycle

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  In Progress
Status in trust-store package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in mir package in Ubuntu RTM:
  In Progress
Status in qtmir package in Ubuntu RTM:
  Triaged

Bug description:
  After we fix bug #1355173, we'll be leaking trusted prompts in the
  sense that when an app gets unfocused (and potentially killed
  subsequently), the trusted prompts will be left running, not suspended
  with the app. We should apply the same rules to the whole app
  container (can we use ual? add the prompts to the pgroup/cgroup?).

  This needs an escape route, too, for trusted helpers to be able to
  kill prompts as they need to.

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

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

[Touch-packages] [Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0

[Michał Sawicz]

** Changed in: unity8 (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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1403758

Title:
  Unity8 shows black screen with Qt 5.4.0

Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With bug #1403511 taken care of in Qt, apps do not anymore crash with
  Qt 5.4 and device does not anymore go into reboot loop. However,
  nothing is visible on the screen.

  It seems unity8, unity8-dash etc are all running. unity8.log attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1403758/+subscriptions

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

[Touch-packages] [Bug 1383870] Re: [phone-app] + [messaging-app] + [address-book-app] list tug actions should collapse after user moves view

[Launchpad Bug Tracker]

** Branch linked: lp:~andrew-hayzen/music-app/fix-1383870-scroll-close-
actions

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

Title:
  [phone-app] + [messaging-app] + [address-book-app] list tug actions
  should collapse after user moves view

Status in Address Book App:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Music application for Ubuntu devices:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  build r120

  Steps to reproduce:
  1. open phone app
  2. carry out a bottom edge swipe to access your RECENT
  3. swipe any list item to the left or right
  4. now scroll your list view a little bit down or up, make sure the list item 
actions stay in view

  Actual Result: the actions remain on the screen, they only collapse if
  it hides behind the header or bottom of the view

  Expected result: if user starts to scroll the list view while a list item 
shows additional actions, the list item should collapse.
  Users are carrying out a different actions in that case and are likely not 
being interested anymore in the revealed list item actions.

  Same behaviour applies for the messaging app and the address-book-app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1383870/+subscriptions

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

[Touch-packages] [Bug 1402597] Re: unity8 scope shell reboots on twitter trending

[Pat McGowan]

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

** Changed in: canonical-devices-system-image
Milestone: None = ww05-2015

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

Title:
  unity8 scope shell reboots on twitter trending

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu RTM:
  New

Bug description:
  Repoduction steps:
  1) go to today scope
  2) click on one of the twitter tredding items
  3) read content
  4) click back arrow to go back to today scope

  The leads *sometimes* to a frozen dash shell freezing and sometime
  later rebooting.  I was able to reproduce this several times in 1 hour
  of use:

  some logs for the scope registry:
  http://paste.ubuntu.com/9520578/

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

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

[Touch-packages] [Bug 1408103] Re: Telephony seems to think I'm on a permanent call, ringer never plays, just the beep-beep of an awaiting call

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None = ww03-2015

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

Title:
  Telephony seems to think I'm on a permanent call, ringer never plays,
  just the beep-beep of an awaiting call

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Telephony Service:
  In Progress
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  New

Bug description:
  For some time now, on both rtm and vivid, I don't get incoming call or
  message sounds, just the beep beep of the awaiting call, as if I was
  on a permanent call.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20141212-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Tue Jan  6 22:10:47 2015
  InstallationDate: Installed on 2014-12-17 (20 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141217-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1373517] Re: [sdk] invoked search in apps should display for BACK and not X

[Launchpad Bug Tracker]

** Branch linked: lp:~renatofilho/messaging-app/fix-1373517

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

Title:
  [sdk] invoked search in apps should display  for BACK and not X

Status in Address Book App:
  In Progress
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Invalid
Status in Ubuntu UX bugs:
  Fix Committed
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Address Book or Messaging apps
  2. Tap in the main landing view(s) the Search icon
  3. Actual result: a X icon is displayed on the left hand side for 
cancelling the search action

  4. Expected result: a  BACK icon should be displayed, as currently
  on the dash

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1373517/+subscriptions

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

[Touch-packages] [Bug 1409096] [NEW] ubuntu-bug synaptic fails due to UnicodeDecodeError while reading dmesg

[Karl-Philipp Richter]

Public bug reported:

invoking `ubuntu-bug synaptic` causes

$ ubuntu-bug synaptic
 AUTHENTICATING FOR com.ubuntu.apport.root-info ===
Authentication is required to collect system information for this problem 
report
Authenticating as: richter,,, (richter)
Password: 
 AUTHENTICATION COMPLETE ===
ERROR: hook /usr/share/apport/package-hooks/source_synaptic.py crashed:
Traceback (most recent call last):
  File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
symb['add_info'](report, ui)
TypeError: add_info() takes 1 positional argument but 2 were given

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File /usr/lib/python3/dist-packages/apport/report.py, line 202, in 
_run_hook
symb['add_info'](report)
  File /usr/share/apport/package-hooks/source_synaptic.py, line 15, in 
add_info
'CurrentDmesg.txt': 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'})
  File /usr/lib/python3/dist-packages/apport/hookutils.py, line 469, in 
attach_root_command_outputs
buf = f.read().strip()
  File /usr/lib/python3.4/codecs.py, line 313, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 
2531522: invalid continuation byte

after I entered my user password at the prompt.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apport 2.14.7-0ubuntu8
Uname: Linux 3.19.0-031900rc3-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan  9 20:11:56 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-03 (6 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: apport
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  ubuntu-bug synaptic fails due to UnicodeDecodeError while reading
  dmesg

Status in apport package in Ubuntu:
  New

Bug description:
  invoking `ubuntu-bug synaptic` causes

  $ ubuntu-bug synaptic
   AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: richter,,, (richter)
  Password: 
   AUTHENTICATION COMPLETE ===
  ERROR: hook /usr/share/apport/package-hooks/source_synaptic.py crashed:
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception
  occurred:

  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport/report.py, line 202, in 
_run_hook
  symb['add_info'](report)
File /usr/share/apport/package-hooks/source_synaptic.py, line 15, in 
add_info
  'CurrentDmesg.txt': 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'})
File /usr/lib/python3/dist-packages/apport/hookutils.py, line 469, in 
attach_root_command_outputs
  buf = f.read().strip()
File /usr/lib/python3.4/codecs.py, line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 
2531522: invalid continuation byte

  after I entered my user password at the prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apport 2.14.7-0ubuntu8
  Uname: Linux 3.19.0-031900rc3-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  9 20:11:56 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-03 (6 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: apport
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384749] Re: Detected X, Y coordinates for touch event on text field is off

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
Milestone: None = ww03-2015

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

Title:
  Detected X,Y coordinates for touch event on text field is off

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New

Bug description:
  Tapping on a word in a text input seems to select the word below,
  rather than the one I intended to select

  The Y seems to be lower by approx. 1 GU

  Reproduce by
  - Go to messages and tap on message filed
  - Enter 4 rows of content
  - Tap on a word in the second row
  - The word below is often selected

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

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

[Touch-packages] [Bug 1403205] Re: Gallery does not handle .gif files

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/gallery-app

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

Title:
  Gallery does not handle .gif files

Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress

Bug description:
  Gallery app does not display .gif files on the collection.

  Test Case:
  1. Import a .gif file (i.e. Saving from Gmail, Browser or manually copying to 
the ~/Pictures folder) 
  2. Open gallery-app after the import is finished

  Expected result
  Verify that the photo is saved in the gallery app, and a thumbnail is 
generated.

  Current result:
  The photo is saved on the folder but no thumbanil is generated

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1403205/+subscriptions

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

[Touch-packages] [Bug 1406952] Re: systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

[mark wade]

I neglected to say I've restored the original
/lib/udev/hwdb.d/60-keyboard.hwdb with all its entries intact and have
rebooted a few times with no errors.  Next error I'll touch the file and
reboot and see.

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

Title:
  systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  during boot systemd-udevd reports:  Error calling EVIOCSKEYCODE:
  Invalid argument

  error message has been noted during boot and collected via dmesg. No
  device name associated with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu20.9
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan  1 17:16:55 2015
  InstallationDate: Installed on 2013-05-01 (609 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1404309] Re: contact expansion incorrect when keyboard visible

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-keyboard

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

Title:
  contact expansion incorrect when keyboard visible

Status in Address Book App:
  In Progress
Status in Ubuntu Keyboard:
  In Progress
Status in address-book-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in address-book-app package in Ubuntu RTM:
  New
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  rtm build 184 on krillin

  Steps to reproduce:
  - open address book app
  - click on search button
  - click on one of the contacts at the top of the results to expand it

  Expected results:
  - the contact will expand and the keyboard will be dismissed

  Actual results:
  - the contact expands then immediately close and the keyboard is dismissed

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1404309/+subscriptions

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

[Touch-packages] [Bug 1403048] Re: clicking the departments header to collapse the list, flicks to another scope too easily

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
  clicking the departments header to collapse the list, flicks to
  another scope too easily

Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  I often open the departments list, but then close it again by tapping
  the list header (currently selected department) again. Unlike the rest
  of the menu, it does propagate touch events to the dash behind it and
  if the tap does a small horizontal movement, it flicks to another
  scope.

  expected:
  The whole departments menu should consume touch events to prevent this from 
happening

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

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

[Touch-packages] [Bug 1401213] Re: Can't enter passphrase in unity8 wizard

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
  Can't enter passphrase in unity8 wizard

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  In the unity8/vivid version of the welcome wizard, the OSK doens't
  appear on the passphrase screen.

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

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

[Touch-packages] [Bug 1384278] Re: Impossible to change enter button without unfocusing the textfield

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-keyboard

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

Title:
  Impossible to change enter button without unfocusing the textfield

Status in Ubuntu Keyboard:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu RTM:
  In Progress

Bug description:
  In webbrowser app we want to change enter icon on keyboard following
  what's the address in the addressbar. So if the url in addressbar is
  the same of page url we want the reload icon, if not we want the enter
  icon.

  Unfortunately to change icon we need to reload the keyboard, and to do
  this we need to unfocus and focus again the textfield, that isn't a
  viable way.

  This is the code I tried, and it isn't calculate in realtime
  InputMethod.extensions: {
   enterKeyIconSource: actionStatus == reload ? reload : 
keyboard-enter
  }

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

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

[Touch-packages] [Bug 1408819] Re: unity8 crashed with SIGABRT in g_assertion_message() when launching calculator from quicklist

[Launchpad Bug Tracker]

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

** Changed in: qtubuntu (Ubuntu)
   Status: New = Confirmed

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

Title:
  unity8 crashed with SIGABRT in g_assertion_message() when launching
  calculator from quicklist

Status in QT Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in qtmir package in Ubuntu RTM:
  Triaged

Bug description:
  Steps:
  * add calculator app to launcher
  * long-press on the calculator item in the launcher
  * tap the top action Calculator
  * repeat if necessary

  Expected:
  * calculator is launched or focused

  Current:
  * unity8 aborts due to some utf8 encoding issue

  ProblemType: Crash
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150107~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Jan  8 23:18:50 2015
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1420625961
  InstallationDate: Installed on 2014-12-18 (21 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  ProcCmdline: unity8
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1408819] Re: unity8 crashed with SIGABRT in g_assertion_message() when launching calculator from quicklist

[Michał Sawicz]

** Package changed: unity8 (Ubuntu RTM) = qtmir (Ubuntu RTM)

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

Title:
  unity8 crashed with SIGABRT in g_assertion_message() when launching
  calculator from quicklist

Status in QT Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in qtmir package in Ubuntu RTM:
  Triaged

Bug description:
  Steps:
  * add calculator app to launcher
  * long-press on the calculator item in the launcher
  * tap the top action Calculator
  * repeat if necessary

  Expected:
  * calculator is launched or focused

  Current:
  * unity8 aborts due to some utf8 encoding issue

  ProblemType: Crash
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150107~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Jan  8 23:18:50 2015
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1420625961
  InstallationDate: Installed on 2014-12-18 (21 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  ProcCmdline: unity8
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1390709] Re: Wifi doesn'r reconnect after waking from sleep

[Launchpad Bug Tracker]

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

Title:
  Wifi doesn'r reconnect after waking from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking
  up from sleep mode. After Update reconnect fails with wlan0: aborting
  authentication with 1c:c6:3c:95:e7:74 by local choice (Reason:
  3=DEAUTH_LEAVING).

  I worked around this by killing wpa_supplicant with a script in
  /etc/pm/sleep.d

  
  #!/bin/sh

  case $1 in
  thaw|resume) 
  { killall wpa_supplicant ; } 2/dev/null
  ;;
  *)
  ;;
  esac

  exit $?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu28
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Nov  8 11:43:15 2014
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-19 (567 days ago)
  InstallationMedia: Kubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  IpRoute:
   default via 192.168.138.251 dev wlan0  proto static 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.138.0/24 dev wlan0  proto kernel  scope link  src 192.168.138.143  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago)
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1367906] Re: Contact search doesn't match accented names

[Launchpad Bug Tracker]

** Branch linked: lp:~renatofilho/messaging-app/fix-1367906

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

Title:
  Contact search doesn't match accented names

Status in Address Book App:
  In Progress
Status in Address Book Service:
  In Progress
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Messaging App:
  In Progress
Status in address-book-app package in Ubuntu:
  In Progress
Status in address-book-service package in Ubuntu:
  In Progress
Status in address-book-app package in Ubuntu RTM:
  In Progress
Status in address-book-service package in Ubuntu RTM:
  New

Bug description:
  If I have a contact with an accent in the name, for example Fábio or
  José, and I search for the names without the accent (fabio or jose),
  there is no match to the existing contacts.

  The search should match unaccented search terms to accented results
  (a should match á, ã, and so on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1367906/+subscriptions

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

[Touch-packages] [Bug 1270579] Re: Ubuntu should have an upstart job for saving/restoring backlight level on laptops

[Norbert]

** Description changed:

+ Dear all!
+ 
  I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7, 
Sabayon, Mageia 4.
  Many of them are based on systemd.
  It does not matter what init system they use, but all of them have very 
usefull script (or binary program, I don't know) for saving and restoring 
backlight level on laptop.
  
  In these distros there is a script for save and restore backlight levels for 
two video-cards (acpi_video0 and acpi_video1). During system boot it is 
indicated as follows:
  
  [  OK  ] Started Load/Save Screen Backlight Brightness of acpi_video1.
  [  OK  ] Started Load/Save Screen Backlight Brightness of acpi_video0.
  .
  
- I have a draft version, which works normally on my VAIO F13Z1R laptop with 
Ubuntu 12.04.4. It is in attachment.
- You can use it unmodified or modify it for compatibility or something. I made 
symlinks for it:
- ln -s /etc/init.d/brightness /etc/rc0.d/S25backlight
- ln -s /etc/init.d/brightness /etc/rcS.d/S25backlight
- ln -s /etc/init.d/brightness /etc/rc6.d/S25backlight
+ =
  
- For details you can read my comment on askubuntu
- (http://askubuntu.com/a/227553/66509).
+ Steps to reproduce:
+ 1. User boots laptop (cold boot, not wake from suspend)
+ 2. User sets comfortable backlight level
+ 3. User ends his/her work by shutting down the laptop (not suspend, so 
backlight level is not saved)
+ 4. Go to 1 (another cold boot with reseted backlight level).
  
- I think that having a script for saving and restoring backlight level is very 
useful for laptop Ubuntu users.
- So, please, add such init script to default Ubuntu installation.
+ =
+ 
+ According to the list of duplicates and bug heat this bug/feature
+ request is very important.
+ 
+ As you know laptop market share is gigantic (see for example 
http://www.statista.com/statistics/276772/ultrabook-share-of-global-notebook-market-since-2011/
 for stats).
+ Also Ubuntu and Debian market share are increasing.
+ 
+ So I can't believe why this usability fault exists in Ubuntu (and Debian) for 
years.
+ It seems that guys from `systemd` understand the problem correctly (sooner or 
later - on 14 Aug 2013, see 
https://github.com/systemd/systemd/commits/56f64d95763a799ba4475daf44d8e9f72a1bd474/src/backlight/backlight.c
 ), but `upstart` and `sysvinit` developers not.
+ 
+ As you can remember I tried to fix the problem by myself (see my comment on 
askubuntu 
http://askubuntu.com/questions/151651/brightness-is-reset-to-maximum-on-every-restart/227553#227553)
 - I created first version of an init script for saving and restoring backlight 
level (on 10 Dec 2012 - two years ago).
+ It had one disadvantage - it operates only when laptop has one graphical 
adaptor and its name was hardcoded to the script (*acpi_video0* in my case).
+ 
+ So today I present new version of a script - it can save and restore 
backlight levels of all graphical, adaptors, which are found in 
`/sys/class/backlight/*`.
+ The init script with symlink are packed to archive (see attachment to comment 
#18 - 
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1270579/+attachment/4288756/+files/upstart_brightness.tar.gz
 ).
+ The script is tested on Ubuntu Precise 12.04.5 and Ubuntu Trusty 14.04.1.
+ 
+ 
+ Please note: if you have installed its previous version (see comment #15) - 
you can remove its files with commands:
+  sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness
+ then extract new version with commands:
+  sudo tar -zxvf upstart_brightness.tar.gz -C /
+ 
+ 
+ I hope my script will help somebody.
+ Thanks for testing!
+ 
+ =
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

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

Title:
  Ubuntu should have an upstart job for saving/restoring backlight level
  on laptops

Status in elementary OS:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in The Linux Mint Distribution:
  New
Status in Ubuntu MATE:
  Opinion
Status in systemd package in Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  New
Status in sysvinit package in Debian:
  New

Bug description:
  Dear all!

  I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7, 
Sabayon, Mageia 

[Touch-packages] [Bug 1270579] Re: Ubuntu should have an upstart job for saving/restoring backlight level on laptops

[Norbert]

** Description changed:

  Dear all!
  
  I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7, 
Sabayon, Mageia 4.
  Many of them are based on systemd.
  It does not matter what init system they use, but all of them have very 
usefull script (or binary program, I don't know) for saving and restoring 
backlight level on laptop.
  
  In these distros there is a script for save and restore backlight levels for 
two video-cards (acpi_video0 and acpi_video1). During system boot it is 
indicated as follows:
  
  [  OK  ] Started Load/Save Screen Backlight Brightness of acpi_video1.
  [  OK  ] Started Load/Save Screen Backlight Brightness of acpi_video0.
  .
  
  =
  
  Steps to reproduce:
  1. User boots laptop (cold boot, not wake from suspend)
  2. User sets comfortable backlight level
  3. User ends his/her work by shutting down the laptop (not suspend, so 
backlight level is not saved)
  4. Go to 1 (another cold boot with reseted backlight level).
  
  =
  
  According to the list of duplicates and bug heat this bug/feature
  request is very important.
  
  As you know laptop market share is gigantic (see for example 
http://www.statista.com/statistics/276772/ultrabook-share-of-global-notebook-market-since-2011/
 for stats).
  Also Ubuntu and Debian market share are increasing.
  
  So I can't believe why this usability fault exists in Ubuntu (and Debian) for 
years.
  It seems that guys from `systemd` understand the problem correctly (sooner or 
later - on 14 Aug 2013, see 
https://github.com/systemd/systemd/commits/56f64d95763a799ba4475daf44d8e9f72a1bd474/src/backlight/backlight.c
 ), but `upstart` and `sysvinit` developers not.
  
  As you can remember I tried to fix the problem by myself (see my comment on 
askubuntu 
http://askubuntu.com/questions/151651/brightness-is-reset-to-maximum-on-every-restart/227553#227553)
 - I created first version of an init script for saving and restoring backlight 
level (on 10 Dec 2012 - two years ago).
  It had one disadvantage - it operates only when laptop has one graphical 
adaptor and its name was hardcoded to the script (*acpi_video0* in my case).
  
- So today I present new version of a script - it can save and restore 
backlight levels of all graphical, adaptors, which are found in 
`/sys/class/backlight/*`.
- The init script with symlink are packed to archive (see attachment to comment 
#18 - 
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1270579/+attachment/4288756/+files/upstart_brightness.tar.gz
 ).
+ So on 2014-12-28 I presented new version of a script - it can save and 
restore backlight levels of all graphical, adaptors, which are found in 
`/sys/class/backlight/*`.
+ The init script with symlink aPlease note: ire packed to archive (see 
attachment to comment #18 - 
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1270579/+attachment/4288756/+files/upstart_brightness.tar.gz
 ).
  The script is tested on Ubuntu Precise 12.04.5 and Ubuntu Trusty 14.04.1.
  
- 
- Please note: if you have installed its previous version (see comment #15) - 
you can remove its files with commands:
-  sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness
+ If you have installed its previous version (from comment #15) - you can 
remove its files with commands:
+  sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness
  then extract new version with commands:
-  sudo tar -zxvf upstart_brightness.tar.gz -C /
- 
+  sudo tar -zxvf upstart_brightness.tar.gz -C /
  
  I hope my script will help somebody.
  Thanks for testing!
+ 
+ To Ubuntu developers: please contact me if you are ready to include and
+ distribute my script to 12.04 and 14.04 deb-pakages.
  
  =
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

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

Title:
  Ubuntu should have an upstart job for saving/restoring backlight level
  on laptops

Status in elementary OS:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in The Linux Mint Distribution:
  New
Status in Ubuntu MATE:
  Opinion
Status in systemd package in Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  New
Status in sysvinit package in Debian:
  New

Bug description:
  Dear 

[Touch-packages] [Bug 1409081] Re: /etc/init.d/pcscd works only at first start.

[Wolf Pichler]

Since this is my first fault report here I probably made the mistake to
assign it to pcsc-cyberjack instead to pcscd = trying to fix it right
now 

** Package changed: pcsc-cyberjack (Ubuntu) = pcsc-lite (Ubuntu)

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

Title:
  /etc/init.d/pcscd works only at first start.

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  /etc/init.d/pcscd * resp. service pcscd * works only at first start.
  In all other cases it just does nothing resp. starts one more pcscd.

  Examples:

  root@liberty:/etc# service pcscd start
  root@liberty:/etc# ps -ef|grep pcscd
  root  3850  1884  0 16:09 pts/10   00:00:00 /usr/sbin/pcscd

  root@liberty:/etc# service pcscd start
  root@liberty:/etc# ps -ef|grep pcscd
  root  3850  1884  0 16:09 pts/10   00:00:01 /usr/sbin/pcscd
  root  5230  1884  0 17:49 pts/10   00:00:00 /usr/sbin/pcscd

  root@liberty:/etc# service pcscd stop
  root@liberty:/etc# ps -ef|grep pcscd
  root  3850  1884  0 16:09 pts/10   00:00:01 /usr/sbin/pcscd
  root  5230  1884  0 17:49 pts/10   00:00:00 /usr/sbin/pcscd

  root@liberty:/etc# /etc/init.d/pcscd stop
  root@liberty:/etc# ps -ef|grep pcscd
  root  3850  1884  0 16:09 pts/10   00:00:01 /usr/sbin/pcscd
  root  5230  1884  0 17:49 pts/10   00:00:00 /usr/sbin/pcscd

  root@liberty:/etc# service pcscd restart
   * Restarting PCSC Lite resource manager pcscd
  [ OK ] 
  root@liberty:/etc# ps -ef|grep pcscd
  root  3850  1884  0 16:09 pts/10   00:00:01 /usr/sbin/pcscd
  root  5230  1884  0 17:49 pts/10   00:00:00 /usr/sbin/pcscd
  root  5295  1884  0 17:52 pts/10   00:00:00 /usr/sbin/pcscd

  ###

  The problem is caused by these lines in /etc/init.d/pcscd:

  # create $IPCDIR with correct access rights
  rm -rf $IPCDIR
  mkdir $IPCDIR
  chgrp pcscd $IPCDIR
  chmod g+w $IPCDIR

  Since PIDFILE=$IPCDIR/$NAME.pid it will be deleted by the first of these 
commands and
  start-stop-daemon in /etc/init.d/pcscd using option --pidfile $PIDFILE 
can not work anymore.

  Commenting the lines above makes the script work as expected (or at
  least as expected by _me_).

  ###

  Another minor problem is the line chgrp pcscd $IPCDIR in the init script: 
Group pcscd does not exist.
  Creating the group myself does not change anything, neither positive nor 
negative -
  except for the fact that the group is then set on $IPCDIR:

  wolf@liberty:/run$ ls -ld pcscd
  drwxr-xr-x 2 root pcscd 80 Dez 22 17:52 pcscd

  wolf@liberty:/run$ ls -l pcscd
  total 4
  srw-rw-rw- 1 root root 0 Dez 22 17:52 pcscd.comm
  -rw-r--r-- 1 root root 6 Dez 22 17:52 pcscd.pid

  ###

  pcscd --version
  pcsc-lite version 1.8.10.
  Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com.
  Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr.
  Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr.
  Report bugs to mus...@lists.musclecard.com.
  Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev 
usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd 
configdir=/etc/reader.conf.d

  apt-cache policy pcscd
  pcscd:
Installed: 1.8.10-1ubuntu1
Candidate: 1.8.10-1ubuntu1
Version table:
   *** 1.8.10-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  OS: Ubuntu 14.04 64bit
  3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session

[Michał Sawicz]

** Changed in: qtmir (Ubuntu RTM)
 Assignee: (unassigned) = Michał Sawicz (saviq)

** Changed in: unity8 (Ubuntu RTM)
 Assignee: (unassigned) = Michał Sawicz (saviq)

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

Title:
  Switching windows with a Trusted Prompt Session active loses the
  trusted prompt session

Status in the base for Ubuntu mobile products:
  In Progress
Status in Mir:
  Fix Released
Status in Qt integration with the Mir display server:
  In Progress
Status in Online Accounts setup for Ubuntu Touch:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  In Progress
Status in trust-store package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Invalid
Status in mir package in Ubuntu RTM:
  Triaged
Status in qtmir package in Ubuntu RTM:
  Triaged

Bug description:
  
  When we create a trusted prompt session over an application, let's say a 
small dialog, and then switch applications, when we switch back to the original 
application the dialog is not overlayed on top of the original application. The 
program providing the dialog seems happy, and is still running, but visually it 
is not there.

  We notice this when using the payments UI which overlays ontop of the
  dash. In some cases we need to show Online Accounts which runs as an
  independent application and causes a switching behavior. When
  returning back to the dash the Payment UI is not visible. It also
  happens if the Payment UI is visible and you switch applications using
  the right swipe.

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

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

[Touch-packages] [Bug 1385331] Re: Notification LED stays on when no messages in notification center

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150109.2-0ubuntu1

---
unity8 (8.02+15.04.20150109.2-0ubuntu1) vivid; urgency=low

  [ Michał Sawicz ]
  * We don't need the SIGSTOP in main() any more.
  * Add a test to make sure the shell always starts disabled until it is
enabled by a complete PAM interaction.

  [ Leo Arias ]
  * Added an autopilot test for the edges demo.

  [ Nick Dedekind ]
  * Unhook Lights interface from indicator widgets (LP: #1385331)

  [ Albert Astals ]
  * Fix going to scopes when the Manage Dash is open (LP: #1403464)
  * QSortFilterProxyModelQML - UnitySortFilterProxyModelQML
  * Clip the Scopes List header
  * Fix ScopesList not being under finger
  * Make waitForRendering with no item fail instead of crash
  * Disable Dash horizontal scroll while Navigation InverseMouseArea is
pressed (LP: #1403048)
  * Test: Make sure the mouse area is enabled before clicking into it
  * Test: We actually need to click on the customBackButton and not on
backButton
  * Test: By default mouseX act on the middle

  [ Michael Terry ]
  * Don't block handling power events on loading the greeter's qml and
the background image.
  * Show OSK above the wizard. (LP: #1401213)
  * Unify the name of the Greeter DBus test, make it use our standard
binary test macro (which also nicely exports xml results), and make
the test a little more robust against timing issues.
  * Add a test to make sure the shell always starts disabled until it is
enabled by a complete PAM interaction.

  [ Martin Pitt ]
  * tests: Fix Notify.Notification.add_action invocation to work also
with unpatched libnotify API. (LP: #1223401)

  [ Rodney Dawes ]
  * Depend on :native version of g++ to allow cross-compiling to work.
(LP: #1353855)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 09 Jan 2015 
10:43:06 +

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

Title:
  Notification LED stays on when no messages in notification center

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Observed the notification LED staying on even though there were no
  notifications in the indicators and the notification icon was greyed
  out.

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

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

[Touch-packages] [Bug 1223401] Re: [0.7.6] the add_action api changed creating issues for clients

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.02+15.04.20150109.2-0ubuntu1

---
unity8 (8.02+15.04.20150109.2-0ubuntu1) vivid; urgency=low

  [ Michał Sawicz ]
  * We don't need the SIGSTOP in main() any more.
  * Add a test to make sure the shell always starts disabled until it is
enabled by a complete PAM interaction.

  [ Leo Arias ]
  * Added an autopilot test for the edges demo.

  [ Nick Dedekind ]
  * Unhook Lights interface from indicator widgets (LP: #1385331)

  [ Albert Astals ]
  * Fix going to scopes when the Manage Dash is open (LP: #1403464)
  * QSortFilterProxyModelQML - UnitySortFilterProxyModelQML
  * Clip the Scopes List header
  * Fix ScopesList not being under finger
  * Make waitForRendering with no item fail instead of crash
  * Disable Dash horizontal scroll while Navigation InverseMouseArea is
pressed (LP: #1403048)
  * Test: Make sure the mouse area is enabled before clicking into it
  * Test: We actually need to click on the customBackButton and not on
backButton
  * Test: By default mouseX act on the middle

  [ Michael Terry ]
  * Don't block handling power events on loading the greeter's qml and
the background image.
  * Show OSK above the wizard. (LP: #1401213)
  * Unify the name of the Greeter DBus test, make it use our standard
binary test macro (which also nicely exports xml results), and make
the test a little more robust against timing issues.
  * Add a test to make sure the shell always starts disabled until it is
enabled by a complete PAM interaction.

  [ Martin Pitt ]
  * tests: Fix Notify.Notification.add_action invocation to work also
with unpatched libnotify API. (LP: #1223401)

  [ Rodney Dawes ]
  * Depend on :native version of g++ to allow cross-compiling to work.
(LP: #1353855)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 09 Jan 2015 
10:43:06 +

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

Title:
  [0.7.6] the add_action api changed creating issues for clients

Status in libnotify package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  That upstream change seems an api change:
  
https://git.gnome.org/browse/libnotify/commit/?id=2b4ab4d22f42dd264a4ddfa68b02bba0d6c71b0b

  Simple testcase:

  from gi.repository import GLib, Notify

  def action_callback():
  print action_id
  notification = Notify.Notification.new(, , )
  notification.add_action(one, two, action_callback, None, None)

  that code worked before and is complaining about the number of
  arguments (5 instead of 6) after the update

  We reverted the change because it was creating problems in unity8
  tests (and likely in code in the archive).

  Before dropping the revert we should probably figure out if:
  - the upstream change is correct is buggy
  - why the number of argument changed (it seems from the commit it shouldn't)
  - what in the archive use that api and needs to be ported
  - how we can make code support both old/new apis at the same time

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

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

[Touch-packages] [Bug 1408819] Re: unity8 crashed with SIGABRT in g_assertion_message() when launching calculator from quicklist

[Michał Sawicz]

** Package changed: url-dispatcher (Ubuntu) = qtubuntu (Ubuntu)

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

Title:
  unity8 crashed with SIGABRT in g_assertion_message() when launching
  calculator from quicklist

Status in QT Ubuntu:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in qtmir package in Ubuntu RTM:
  Triaged

Bug description:
  Steps:
  * add calculator app to launcher
  * long-press on the calculator item in the launcher
  * tap the top action Calculator
  * repeat if necessary

  Expected:
  * calculator is launched or focused

  Current:
  * unity8 aborts due to some utf8 encoding issue

  ProblemType: Crash
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150107~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Jan  8 23:18:50 2015
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1420625961
  InstallationDate: Installed on 2014-12-18 (21 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  ProcCmdline: unity8
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1408593] Re: X server disables acceleartion or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid)

[Joseph Salisbury]

Thanks for testing.  We can perform a Reverse bisect to identify the
commit that fixes this in 3.19.  First, can you also test the latest
3.18 upstream kernel to see if it already has the fix?  It can be
downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.2-vivid/

** Tags added: needs-bisect

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

Title:
  X server disables acceleartion or turns off output (makes screen
  black) after kernel upgrade to v3.18 (Ubuntu Vivid)

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after reboot into kernel 3.18 (3.18.0-8.9)

  with Intel driver version 2:2.99.916+git20141119-1~exp1ubuntu1 it disables 
output / blacks the screen and puts in the log :
  [37.179] (II) GLX: Initialized DRI2 GL provider for screen 0
  [37.215] (WW) intel(0): Failed to submit rendering commands, trying again 
with outputs disabled.
  (then refuses to switch local VTs both by [Ctrl-]Alt-Fn and by chvt in remote 
logins)

  after reverting to 2:2.99.914-1~exp1ubuntu6 it puts :
  [41.679] (II) GLX: Initialized DRI2 GL provider for screen 0
  [41.711] (EE) intel(0): Failed to submit rendering commands, disabling 
acceleration.
  (then allows to log in bu with desktop composition effects disabled)

  after reboot back into kernel 3.16.0-28.38 , both *.916 and *.914
  drivers work well

  probably this bug should also be attached to kernel package v3.18

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan  8 11:23:52 2015
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mwg1214 F pulseaudio
  CRDA:
   country UA: DFS-UNSET
(2400 - 2483 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(5150 - 5350 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: Acer Aspire 
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=9bc29087-2e9e-4bf9-bea1-2540902b5ae3 ro rootflags=commit=3600 
transparent_hugepage=always init=/lib/systemd/systemd
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.140
  Tags:  vivid vivid
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout disk kvm lpadmin netdev plugdev 
sambashare src
  _MarkForUpload: True
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV10_CS
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1319655] Re: getopt example in docs incorrectly implies /bin/sh may not be used (PATCH)

[Brian Murray]

** Changed in: util-linux (Ubuntu)
   Importance: Undecided = Low

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

Title:
  getopt example in docs incorrectly implies /bin/sh may not be used
  (PATCH)

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  getopt(1) works with /bin/sh, bash, and probably other Bourne-ish
  shells (as well as csh-family shells with the appropriate option).

  However the included examples give the impression that something about
  getopt(1) makes it incompatible with /bin/sh, leading one to assume
  that scripts MUST use bash instead of sh.The author probably meant
  merely that the bash example would not work with tcsh; however less-
  experienced script writers might not find that to be obvious.

  First of all, the Bourne-syntax example unnecessarily uses bash, i.e.
  leading one to wonder why the more-universal sh shell could not be
  used.   And there is a comment in the example saying This program
  will only work with bash(1).

  
  SUGGESTED IMPROVEMENT (patch attached):

  . Rename /usr/share/doc/util-linux/examples/getopt-parse.bash to
  getopt-parse.sh

  . Change the example to use /bin/sh instead of bash, and change the
  comment to say that that example works only with sh-compatible shells,
  including bash.


  P.S.  The --shell option to getopt(1) accepts arguments 'sh', 'bash',
  'csh', and 'tcsh', however internally there is no difference between
  'sh' and 'bash' (or between 'csh' and 'tcsh').   See source code at
  https://kernel.googlesource.com/pub/scm/utils/util-linux/util-
  linux/+/v2.22.2/misc-utils/getopt.c

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: util-linux 2.20.1-5.1ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed May 14 21:00:48 2014
  InstallationDate: Installed on 2013-08-06 (282 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to saucy on 2013-10-24 (202 days ago)

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

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

[Touch-packages] [Bug 1408593] Re: X server disables acceleartion or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid)

[William Hua]

Thank you, booting 3.19.0-031900rc3-generic fixed this for me too.

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

Title:
  X server disables acceleartion or turns off output (makes screen
  black) after kernel upgrade to v3.18 (Ubuntu Vivid)

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  after reboot into kernel 3.18 (3.18.0-8.9)

  with Intel driver version 2:2.99.916+git20141119-1~exp1ubuntu1 it disables 
output / blacks the screen and puts in the log :
  [37.179] (II) GLX: Initialized DRI2 GL provider for screen 0
  [37.215] (WW) intel(0): Failed to submit rendering commands, trying again 
with outputs disabled.
  (then refuses to switch local VTs both by [Ctrl-]Alt-Fn and by chvt in remote 
logins)

  after reverting to 2:2.99.914-1~exp1ubuntu6 it puts :
  [41.679] (II) GLX: Initialized DRI2 GL provider for screen 0
  [41.711] (EE) intel(0): Failed to submit rendering commands, disabling 
acceleration.
  (then allows to log in bu with desktop composition effects disabled)

  after reboot back into kernel 3.16.0-28.38 , both *.916 and *.914
  drivers work well

  probably this bug should also be attached to kernel package v3.18

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan  8 11:23:52 2015
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mwg1214 F pulseaudio
  CRDA:
   country UA: DFS-UNSET
(2400 - 2483 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(5150 - 5350 @ 40), (N/A, 20), (N/A), NO-OUTDOOR
(57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc
  InstallationDate: Installed on 2009-11-01 (1893 days ago)
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MachineType: Acer Aspire 
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=9bc29087-2e9e-4bf9-bea1-2540902b5ae3 ro rootflags=commit=3600 
transparent_hugepage=always init=/lib/systemd/systemd
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.140
  Tags:  vivid vivid
  Uname: Linux 3.16.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout disk kvm lpadmin netdev plugdev 
sambashare src
  _MarkForUpload: True
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV10_CS
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Jamie Strandboge]

There are multiple tasks still open for this bug. Can they be closed or
are there still things to do?

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

Title:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

Status in android package in Ubuntu:
  Fix Released
Status in android-tools package in Ubuntu:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  Fix Released
Status in linux-mako package in Ubuntu:
  Confirmed
Status in android package in Ubuntu RTM:
  Fix Released
Status in android-tools package in Ubuntu RTM:
  In Progress
Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM:
  Fix Released
Status in linux-mako package in Ubuntu RTM:
  Confirmed

Bug description:
  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot.
  We've already fixed several bugs in the apparmor and click-apparmor
  and made both more robust in the face of corruption and we've reduced
  the impact when there is a corrupted profile, but we've still not
  found the cause of the corruption. This corruption can still affect
  real-world devices: if a profile in /var/lib/apparmor/profiles is
  corrupted and the cache file is out of date, then the profile won't
  compile and that app/scope won't start.

  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.

  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.

  The security team and the kernel team have discussed this a lot and
  Colin King is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:

  I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:

  http://paste.ubuntu.com/8648109/

  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:

  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1

  In the paste you'll notice that in step 6 the profiles were
  successfully created by the installation of the packages, then
  verified, then copied aside, then apparmor_parser and aa-clickhook
  diverted, then rebooted, only to have the profiles in
  /var/lib/apparmor/profiles be different than what was copied aside. It
  would be nice to verify on your device as well (I reproduced several
  times here) and verify the reproducer algorithm. I think this suggests
  this is a kernel issue and not userspace.

  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

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

[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data

[Jamie Strandboge]

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
   Status: In Progress = Won't Fix

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

Title:
  add directory allowing scopes and apps to share data

Status in the base for Ubuntu mobile products:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in click-reviewers-tools package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu source package in Utopic:
  Won't Fix
Status in unity-scopes-api source package in Utopic:
  New
Status in apparmor-easyprof-ubuntu source package in Vivid:
  Fix Released
Status in click-reviewers-tools source package in Vivid:
  In Progress
Status in unity-scopes-api source package in Vivid:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
  Fix Released

Bug description:
  Summary says it all, just need to decide on the directory. I propose using 
this rule:
    # Allow scopes to share data with the app shipped in the same click
    owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
    owner @{HOME}/.local/share/@{APP_PKGNAME}/**  mrkl,

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

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

[Touch-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs

[Olivier Tilloy]

I tested Ted’s branch that implements my suggestion for url-dispatcher
on a device, and it works up to the point that clicking on an intent://
link in the browser launches the google maps webapp.

However at this point the app just displays a blank surface because the
webview is trying to load an intent:// URL, which it doesn’t know how to
handle, so it delegates it to the system (URL dispatcher), which
dispatches it to the app again, and so on indefinitely (thus using up
CPU, making the app unresponsive and eventually crashing unity8).

So we really need a mechanism in the webapp-container to allow
individual webapps to specify a way to rewrite URLs they are invoked
with. The google maps webapp would then rewrite the intent:// URL to a
https://maps.google.com/* URL.

** Also affects: url-dispatcher
   Importance: Undecided
   Status: New

** No longer affects: url-dispatcher

** Changed in: webbrowser-app
   Status: New = Confirmed

** Changed in: webbrowser-app (Ubuntu)
   Status: Invalid = Confirmed

** Changed in: webbrowser-app (Ubuntu RTM)
   Status: Invalid = Confirmed

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

Title:
  Google Maps and Here Maps should handle custom intent:// URLs

Status in The Webapps-core project:
  New
Status in Web Browser App:
  In Progress
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in url-dispatcher package in Ubuntu RTM:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  ubuntu-rtm image 184

  The maps apps in the system should register and respond to appropriate
  urls from the browser (not sure of the format, map:// or directions://
  - need to check)

  Steps to reproduce:
  1) open browser
  2) type Asai Belmont MA in the url bar and press enter
  3) this will do a google search for the resturant
  4) click on the Directions button

  Expected result:
  - One of the maps apps should open displaying directions for the resturant

  Actual results:
  - no app is launched

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

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

[Touch-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs

[Alexandre Abreu]

** Changed in: webbrowser-app
   Status: Confirmed = In Progress

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

Title:
  Google Maps and Here Maps should handle custom intent:// URLs

Status in The Webapps-core project:
  New
Status in Web Browser App:
  In Progress
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in url-dispatcher package in Ubuntu RTM:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  ubuntu-rtm image 184

  The maps apps in the system should register and respond to appropriate
  urls from the browser (not sure of the format, map:// or directions://
  - need to check)

  Steps to reproduce:
  1) open browser
  2) type Asai Belmont MA in the url bar and press enter
  3) this will do a google search for the resturant
  4) click on the Directions button

  Expected result:
  - One of the maps apps should open displaying directions for the resturant

  Actual results:
  - no app is launched

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

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

[Touch-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs

[Launchpad Bug Tracker]

** Branch linked: lp:~osomon/webapps-core/gmaps-intent-hook

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

Title:
  Google Maps and Here Maps should handle custom intent:// URLs

Status in The Webapps-core project:
  In Progress
Status in Web Browser App:
  In Progress
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in url-dispatcher package in Ubuntu RTM:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  ubuntu-rtm image 184

  The maps apps in the system should register and respond to appropriate
  urls from the browser (not sure of the format, map:// or directions://
  - need to check)

  Steps to reproduce:
  1) open browser
  2) type Asai Belmont MA in the url bar and press enter
  3) this will do a google search for the resturant
  4) click on the Directions button

  Expected result:
  - One of the maps apps should open displaying directions for the resturant

  Actual results:
  - no app is launched

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

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

[Touch-packages] [Bug 1328975] Re: libc6: getaddrinfo() sends DNS queries to random file descriptors

[John Morales]

** Changed in: eglibc (Ubuntu Trusty)
   Status: Confirmed = New

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

Title:
  libc6: getaddrinfo() sends DNS queries to random file descriptors

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Trusty:
  New
Status in glibc source package in Trusty:
  Invalid

Bug description:
  There is an upstream report for debian here https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=722075 which has been fixed in eglibc
  2.19.1 which is now in debian jessie/sid.  See that upstream report
  for a short program which replicates the bug.  I was able to replicate
  the bug on Ubuntu 14.04 using that test script.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jun 11 16:32:43 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  Ec2AMI: ami-30837058
  Ec2AMIManifest: 
ubuntu-us-east-1/images/ubuntu-trusty-14.04-amd64-server-20140607.1.manifest.xml
  Ec2AvailabilityZone: us-east-1a
  Ec2InstanceType: c3.2xlarge
  Ec2Kernel: aki-919dcaf8
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eglibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 846407] Re: xrdp is not able to transmitt unity desktop correct - different clients

[Launchpad Bug Tracker]

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

** Changed in: x2goclient (Ubuntu)
   Status: New = Confirmed

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

Title:
  xrdp is not able to transmitt unity desktop correct - different
  clients

Status in Posix RDP server:
  Unknown
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in x2goclient package in Ubuntu:
  Confirmed
Status in xrdp package in Ubuntu:
  Confirmed

Bug description:
  After login nothing is shown except desktop wallpaper

  Steps to repeat

  1. sudo apt-get install xrdp
  2. Install CoRD 
http://sourceforge.net/projects/cord/files/cord/0.5.5/CoRD_0.5.5.zip/download
  3. Login to the server using CoRD

  Expected result:

  Unity desktop with menus, taskbars, etc.

  Actual result:

  Unity desktop wallpaper

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

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

[Touch-packages] [Bug 1357548] Re: [settings] Empty PIN/password/passphrase field appears to contain 4 characters

[Pat McGowan]

Here's the better way

validator: RegExpValidator { regExp: /\d{4}/ }
onTextChanged: confirmButton.enabled = acceptableInput

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

Title:
  [settings] Empty PIN/password/passphrase field appears to contain 4
  characters

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu RTM:
  Confirmed

Bug description:
  minor interrelated issues  probably needs design input
  1) visual inconsistency of the pin text box prompt shows 4 bullets implying 
needing 4 characters, but the passphrase is text box is empty
  2) selecting the pin text box prompt, the bullets remain, and don't respond 
to delete, they don't disappear once typing begins (i would think dissappear on 
text box selection)
  3) having a show password would be nice

  
  Desired resolution: Passcode/password fields should never contain bullets 
when you haven't entered anything in them.

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

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

[Touch-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs

[Alexandre Abreu]

** Changed in: webapps-core
 Assignee: (unassigned) = Olivier Tilloy (osomon)

** Changed in: webapps-core
   Status: New = In Progress

** Changed in: webapps-core
   Importance: Undecided = High

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

Title:
  Google Maps and Here Maps should handle custom intent:// URLs

Status in The Webapps-core project:
  In Progress
Status in Web Browser App:
  In Progress
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in url-dispatcher package in Ubuntu RTM:
  In Progress
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  ubuntu-rtm image 184

  The maps apps in the system should register and respond to appropriate
  urls from the browser (not sure of the format, map:// or directions://
  - need to check)

  Steps to reproduce:
  1) open browser
  2) type Asai Belmont MA in the url bar and press enter
  3) this will do a google search for the resturant
  4) click on the Directions button

  Expected result:
  - One of the maps apps should open displaying directions for the resturant

  Actual results:
  - no app is launched

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

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

[Touch-packages] [Bug 1403464] Re: Left-edge / home does not close Manage Dash

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/unity8

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

Title:
   Left-edge / home does not close Manage Dash

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  The Manage Dash should be closed on  Left-edge / home press

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

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

[Touch-packages] [Bug 1367906] Re: Contact search doesn't match accented names

[Bill Filler]

** Also affects: address-book-service
   Importance: Undecided
   Status: New

** Also affects: address-book-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: address-book-service (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: address-book-service (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: address-book-service
   Status: New = In Progress

** Changed in: address-book-app (Ubuntu)
   Status: New = In Progress

** Changed in: address-book-app (Ubuntu RTM)
   Status: New = In Progress

** Changed in: address-book-service (Ubuntu)
   Status: New = In Progress

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

Title:
  Contact search doesn't match accented names

Status in Address Book App:
  In Progress
Status in Address Book Service:
  In Progress
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Messaging App:
  In Progress
Status in address-book-app package in Ubuntu:
  In Progress
Status in address-book-service package in Ubuntu:
  In Progress
Status in address-book-app package in Ubuntu RTM:
  In Progress
Status in address-book-service package in Ubuntu RTM:
  New

Bug description:
  If I have a contact with an accent in the name, for example Fábio or
  José, and I search for the names without the accent (fabio or jose),
  there is no match to the existing contacts.

  The search should match unaccented search terms to accented results
  (a should match á, ã, and so on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1367906/+subscriptions

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

[Touch-packages] [Bug 1384278] Re: Impossible to change enter button without unfocusing the textfield

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-keyboard -
0.99.trunk.phablet2+15.04.20150108-0ubuntu1

---
ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150108-0ubuntu1) vivid; urgency=low

  [ CI Train Bot ]
  * Resync trunk

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Renato Araujo Oliveira Filho ]
  * Make sure that changes on InputMethod.extensions property get
propagated to maliit. (LP: #1384278)

  [ Michael Sheldon ]
  * Fix keyboard visibility reporting (LP: #1404309)
  * Extend existing autopilot tests to more thoroughly test each layout,
add new tests for extended keys and .com key and fix crash when
using keyboard after autopilot tests have been run.
  * Speed up individual backspaces and switch between individual and
word backspace based on 3 words having been deleted instead of 3
seconds having passed. (LP: #1347488)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 08 Jan 2015 
18:07:56 +

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

Title:
  Impossible to change enter button without unfocusing the textfield

Status in Ubuntu Keyboard:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu RTM:
  In Progress

Bug description:
  In webbrowser app we want to change enter icon on keyboard following
  what's the address in the addressbar. So if the url in addressbar is
  the same of page url we want the reload icon, if not we want the enter
  icon.

  Unfortunately to change icon we need to reload the keyboard, and to do
  this we need to unfocus and focus again the textfield, that isn't a
  viable way.

  This is the code I tried, and it isn't calculate in realtime
  InputMethod.extensions: {
   enterKeyIconSource: actionStatus == reload ? reload : 
keyboard-enter
  }

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

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

[Touch-packages] [Bug 1404309] Re: contact expansion incorrect when keyboard visible

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-keyboard -
0.99.trunk.phablet2+15.04.20150108-0ubuntu1

---
ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150108-0ubuntu1) vivid; urgency=low

  [ CI Train Bot ]
  * Resync trunk

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Renato Araujo Oliveira Filho ]
  * Make sure that changes on InputMethod.extensions property get
propagated to maliit. (LP: #1384278)

  [ Michael Sheldon ]
  * Fix keyboard visibility reporting (LP: #1404309)
  * Extend existing autopilot tests to more thoroughly test each layout,
add new tests for extended keys and .com key and fix crash when
using keyboard after autopilot tests have been run.
  * Speed up individual backspaces and switch between individual and
word backspace based on 3 words having been deleted instead of 3
seconds having passed. (LP: #1347488)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 08 Jan 2015 
18:07:56 +

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New = Fix Released

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

Title:
  contact expansion incorrect when keyboard visible

Status in Address Book App:
  In Progress
Status in Ubuntu Keyboard:
  In Progress
Status in address-book-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in address-book-app package in Ubuntu RTM:
  New
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  rtm build 184 on krillin

  Steps to reproduce:
  - open address book app
  - click on search button
  - click on one of the contacts at the top of the results to expand it

  Expected results:
  - the contact will expand and the keyboard will be dismissed

  Actual results:
  - the contact expands then immediately close and the keyboard is dismissed

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1404309/+subscriptions

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

[Touch-packages] [Bug 1347488] Re: Backspace should accelerate for single letters as well as words

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-keyboard -
0.99.trunk.phablet2+15.04.20150108-0ubuntu1

---
ubuntu-keyboard (0.99.trunk.phablet2+15.04.20150108-0ubuntu1) vivid; urgency=low

  [ CI Train Bot ]
  * Resync trunk

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Renato Araujo Oliveira Filho ]
  * Make sure that changes on InputMethod.extensions property get
propagated to maliit. (LP: #1384278)

  [ Michael Sheldon ]
  * Fix keyboard visibility reporting (LP: #1404309)
  * Extend existing autopilot tests to more thoroughly test each layout,
add new tests for extended keys and .com key and fix crash when
using keyboard after autopilot tests have been run.
  * Speed up individual backspaces and switch between individual and
word backspace based on 3 words having been deleted instead of 3
seconds having passed. (LP: #1347488)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 08 Jan 2015 
18:07:56 +

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New = Fix Released

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

Title:
  Backspace should accelerate for single letters as well as words

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu Keyboard:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  Currently the backspace only accelerates when it starts deleting
  words, so deleting a very long string of characters which are unbroken
  by spaces takes a long time.

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

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

[Touch-packages] [Bug 1403205] Re: Gallery does not handle .gif files

[Launchpad Bug Tracker]

This bug was fixed in the package gallery-app -
0.0.67+15.04.20150108.1-0ubuntu1

---
gallery-app (0.0.67+15.04.20150108.1-0ubuntu1) vivid; urgency=low

  [ Bill Filler ]
  * update framework version

  [ Arthur Mello ]
  * Add some checks to make sure the file has good metadata before
changing it
  * Make gallery display files that are not supported by QImageWriter or
that do not have metadata Disable the editing options for files that
are not supported by QImageWriter (LP: #1403205)

  [ Florian Boucault ]
  * Support videos from SD card by adding /media/phablet folder to the
video directories.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 08 Jan 2015 
20:32:57 +

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

Title:
  Gallery does not handle .gif files

Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  Gallery app does not display .gif files on the collection.

  Test Case:
  1. Import a .gif file (i.e. Saving from Gmail, Browser or manually copying to 
the ~/Pictures folder) 
  2. Open gallery-app after the import is finished

  Expected result
  Verify that the photo is saved in the gallery app, and a thumbnail is 
generated.

  Current result:
  The photo is saved on the folder but no thumbanil is generated

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1403205/+subscriptions

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