date:20140829

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

---
dialer-app (0.1+14.10.20140829.1-0ubuntu1) utopic; urgency=low

  [ Martin Pitt ]
  * update PO template

  [ Gustavo Pichorim Boiko ]
  * Add All/Missed categories to the call log page. (LP: #1320437)
  * Update the live call designs according to the spec, including the
following changes: hide the header when DTMF keypad is active.
update the visuals and behavior of the multi call and conference
call scenarios. keep the live call view visible for a few seconds
showing the status of an ended call (LP: #1303260)
 -- Ubuntu daily releaseFri, 29 Aug 2014 
22:42:54 +

** Branch linked: lp:ubuntu/utopic-proposed/dialer-app

** Changed in: dialer-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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1303260

Title:
  [dialer-app] implement call end journey

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Ubuntu UX bugs:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  Fix Released

Bug description:
  Whenever I look at the phone after I've stopped the conversation,
  there's a brief time when I can still see the in-call screen, and try
  to press the "end call" button. If the remote party ended the call
  already, the in-call screen "escapes" just as I touch the screen.

  Would be better if the in-call screen remained on screen for a few
  seconds, during which you can see the call length etc., and pressing
  the button would close it. Preferably even in concert with the
  proximity sensor.

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

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

[Touch-packages] [Bug 1320437] Re: Please update the translations template file

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

---
dialer-app (0.1+14.10.20140829.1-0ubuntu1) utopic; urgency=low

  [ Martin Pitt ]
  * update PO template

  [ Gustavo Pichorim Boiko ]
  * Add All/Missed categories to the call log page. (LP: #1320437)
  * Update the live call designs according to the spec, including the
following changes: hide the header when DTMF keypad is active.
update the visuals and behavior of the multi call and conference
call scenarios. keep the live call view visible for a few seconds
showing the status of an ended call (LP: #1303260)
 -- Ubuntu daily releaseFri, 29 Aug 2014 
22:42:54 +

** Branch linked: lp:ubuntu/utopic-proposed/dialer-app

** Changed in: dialer-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 camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1320437

Title:
  Please update the translations template file

Status in Address Book App:
  Fix Released
Status in Camera App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Gallery App:
  Fix Released
Status in Messaging App:
  In Progress
Status in Notes App:
  New
Status in Web Browser App:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  In Progress

Bug description:
  In preparation for the MAE show, there is an ongoing effort to
  translate the UI into Simplified Chinese. For that, we'd need the
  translatable messages in Launchpad to be up-to-date for translators to
  be able to do their work.

  To do this:

  1. Please ensure that all visible user messages are marked for translation 
(i.e. enclosed in the i18n.tr() function)
  2. Run the rule to update the po/$APP.pot file
  3. Commit and push the .pot file

  If the .pot file for a given app is already up-to-date (i.e. no new
  translatable messages added or changed since last update), please feel
  free to mark the associated bug task as invalid.

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

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

[Touch-packages] [Bug 1321079] Re: Intermittent double mouse clicks

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

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

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

Title:
  Intermittent double mouse clicks

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  I occasionally get a double click as a result of a single mouse click.
  I am using my mouse left handed btw and have reversed the buttons. The
  problems started when I switched to the proprietary NVIDIA drivers
  (nvidia-304, proprietary tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.agp.gpu:
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:8x 4x
   Registers:0xff000e1b:0x1f004302
  .proc.driver.nvidia.agp.host.bridge:
   Host Bridge:  PCI device 1039:0661
   Fast Writes:  Not Supported
   SBA:  Supported
   AGP Rates:8x 4x
   Registers:0x1f004e0b:0x0f02
  .proc.driver.nvidia.agp.status:
   Status:   Enabled
   Driver:   AGPGART
   AGP Rate: 8x
   Fast Writes:  Disabled
   SBA:  Enabled
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.88  Wed Mar 27 14:31:12 PDT 
2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,regex,snap,animation,imgpng,unitymtgrabhandles,vpswitch,mousepoll,gnomecompat,place,grid,move,expo,workarounds,ezoom,wall,session,fade,scale,unityshell]
  CompositorRunning: None
  Date: Tue May 20 13:31:39 2014
  DistUpgraded: 2014-02-08 17:38:59,393 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GS] [10de:02e1] (rev a2) 
(prog-if 00 [VGA controller])
  MarkForUpload: True
  ProcKernelCmdLine: root=/dev/sdb1 ro rootdelay=90 nosplash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2014-02-08 (100 days ago)
  dmi.bios.date: 01/18/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: SiS-661
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/18/2006:svn:pn:pvr:rvn:rnSiS-661:rvr:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Tue May 20 08:59:11 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module "modesetting" (module does not exist, 0)
   Failed to load module "modesetting" (module does not exist, 0)
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.14.5-1ubuntu2~saucy1

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

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

[Touch-packages] [Bug 1335850] Re: [Dell Latitude E5530] Mouse Double Clicks on Single Click

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

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

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

Title:
  [Dell Latitude E5530] Mouse Double Clicks on Single Click

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  My Logitech Anywhere MX mouse double clicks on single click.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-24.41-generic 3.11.10.11
  Uname: Linux 3.11.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 30 15:37:28 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:053d]
  InstallationDate: Installed on 2013-11-08 (234 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E5530 non-vPro
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-24-generic 
root=UUID=f97570aa-b595-4d26-a8f0-a3824d59e459 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 05GRXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/07/2013:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5530 non-vPro
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Jun 30 13:09:12 2014
  xserver.configfile: default
  xserver.errors:

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

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

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

[Touch-packages] [Bug 1361384] Re: Alsa and Pulse audio hang system when listening to music

2014-08-29 Thread xerofoify

I will try that but I am not on a laptop or hp desktop. I am on my own
build system.

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

Title:
  Alsa and Pulse audio hang system when listening to music

Status in “alsa-utils” package in Ubuntu:
  New

Bug description:
  I seem to be getting a hang and crash of my system every time I listen to 
music in the background. I have tried both pulseaudio
  and alsa but both crash every day or two. It's rather annoying. I am using 
14.04 Lubuntu and expect the music to not hang my system.
  Nick

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

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

[Touch-packages] [Bug 405294] Re: a2dp skips terribly

2014-08-29 Thread macher

After install drivers for wlan from "Additional Drivers", A2DP stopped
skipping. I hope that it will be also fixing your skipping ;)

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

Title:
  a2dp skips terribly

Status in PulseAudio sound server:
  New
Status in “bluez” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1361384] Re: Alsa and Pulse audio hang system when listening to music

2014-08-29 Thread Badr

OK try to change model=auto in modprobe file to model=laptop or model=hp

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

Title:
  Alsa and Pulse audio hang system when listening to music

Status in “alsa-utils” package in Ubuntu:
  New

Bug description:
  I seem to be getting a hang and crash of my system every time I listen to 
music in the background. I have tried both pulseaudio
  and alsa but both crash every day or two. It's rather annoying. I am using 
14.04 Lubuntu and expect the music to not hang my system.
  Nick

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

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

[Touch-packages] [Bug 405294] Re: a2dp skips terribly

2014-08-29 Thread macher

I have this same problem on Ubuntu GNOME 14.04LTS. I found that in my
case is some conflict between wlan card and bluetooth. After turned off
wlan card, A2DP working without skipping :)

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

Title:
  a2dp skips terribly

Status in PulseAudio sound server:
  New
Status in “bluez” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1363178] Re: PCI/internal sound card not detected

2014-08-29 Thread Raymond

23.105281] hda-intel :04:01.0: Using VIACOMBO position fix
[   23.105323] snd_hda_intel :04:01.0: irq 68 for MSI/MSI-X
[   23.495293] type=1400 audit(1409328266.327:2): apparmor="STATUS" 
operation="profile_load" parent=364 profile="unconfined" name="/sbin/dhclient" 
pid=417 comm="apparmor_parser"
[   23.495303] type=1400 audit(1409328266.327:3): apparmor="STATUS" 
operation="profile_load" parent=364 profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=417 
comm="apparmor_parser"
[   23.495310] type=1400 audit(1409328266.327:4): apparmor="STATUS" 
operation="profile_load" parent=364 profile="unconfined" 
name="/usr/lib/connman/scripts/dhclient-script" pid=417 comm="apparmor_parser"
[   23.495812] type=1400 audit(1409328266.327:5): apparmor="STATUS" 
operation="profile_replace" parent=364 profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=417 
comm="apparmor_parser"
[   23.495820] type=1400 audit(1409328266.327:6): apparmor="STATUS" 
operation="profile_replace" parent=364 profile="unconfined" 
name="/usr/lib/connman/scripts/dhclient-script" pid=417 comm="apparmor_parser"
[   23.496091] type=1400 audit(1409328266.331:7): apparmor="STATUS" 
operation="profile_replace" parent=364 profile="unconfined" 
name="/usr/lib/connman/scripts/dhclient-script" pid=417 comm="apparmor_parser"
[   23.683767] do_IRQ: 0.163 No irq handler for vector (irq -1)
[   23.683790] do_IRQ: 0.163 No irq handler for vector (irq -1)
[   23.683818] do_IRQ: 0.163 No irq handler for vector (irq -1)
[   23.683847] do_IRQ: 0.163 No irq handler for vector (irq -1)
[   23.869505] microcode: CPU1 sig=0x6f2, pf=0x1, revision=0x56
[   23.878464] microcode: Microcode Update Driver: v2.00 
, Peter Oruba
[   23.897357] kvm: disabled by bios
[   23.906260] coretemp coretemp.0: Using relative temperature scale!
[   23.906278] coretemp coretemp.0: Using relative temperature scale!
[   24.116038] hda-intel :04:01.0: Codec #0 probe error; disabling it...


** Summary changed:

- PCI/internal sound card not detected
+ Codec 0 probe error disabling it

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

Title:
  Codec 0 probe error disabling it

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
   Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7318
Flags: fast devsel, IRQ 17
Memory at dfafc000 (32-bit, non-prefetchable) [size=16K]
Capabilities: 

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Aug 29 18:52:16 2014
  InstallationDate: Installed on 2014-07-17 (42 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to trusty on 2014-08-28 (1 days ago)
  dmi.bios.date: 05/02/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7318
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/02/2007:svnMEDIONPC:pnMS-7318:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7318:rvr:cvnMEDIONPC:ct3:cvr:
  dmi.product.name: MS-7318
  dmi.sys.vendor: MEDIONPC

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

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

[Touch-packages] [Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2014-08-29 Thread jox

Sorry, there is a typo (the ".bak" is wrong). Let me correct this:

--
You might also apply the attached patch as follows:

  $ cd /usr/lib/uck
  $ sudo patch -p2 remaster-live-cd.sh < \
  /path/to/fix-uck-missing-initd-scripts-1.patch
--

(Please note that I actually meant "You might *alternatively* apply...".
Not "also". Just to be clear.)

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Trusty:
  Triaged
Status in “systemd” source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note we are also suffering from a failure with update-initramfs, not sure of 
the root cause of that one but I thought I'd mention it in case they were 
related, since they both started happening about the same time, a couple weeks 
ago. (launchpad bug #1317602)
  It all worked ok after the inital releases of 14.04, so something to do with 
a package update since then.

  
  thanks,
  Hamish

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

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

[Touch-packages] [Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

2014-08-29 Thread jox

I have investigated this some more. I will provide a solution for UCK
(Ubuntu Customization Kit) but it might apply to other contexts as well.

It is actually 3 distinct issues:

The main problem is the missing init scripts. This is a result from UCK
deactivating initctl (see also in the output of uck-chroot-rootfs:
"Deactivating initctl..."). This makes invoke-rc.d fail when trying to
run upstart jobs (Ubuntu uses upstart (not init) for the services in
question). The "/etc/init.d/* not found" is a followup error and
actually misleading.

The fix described previously (modifying .prerm/.postinst files) does
work, but it's better to fix it globally and not for each affected
package. I found it's best to do it right in invoke-rc.d. Just change
all "exit 100" to "exit 0" in /usr/sbin/invoke-rc.d (in the chroot!).
That will generally ignore missing init scripts. Don't forget to revert
the change afterwards.

The second problem is the missing /scripts directory ("Can't open
/scripts/casper-functions" error). This can be fixed with the following
command (in the chroot!):

ln -s /usr/share/initramfs-tools/scripts /scripts

The third problem is that the UCK applies a hack on the zz-update-grub
scripts which in my case creates an invalid syntax and thus breaks the
upgrade as well (dependency problems on the linux-image-generic
package). The fix is described in my comment #10.

In order to avoid applying these patches manually each time, I modified
UCK to apply it when entering chroot, and revert it when exiting
(amongst the other stuff that UCK does in these stages). It's all in
/usr/lib/uck/remaster-live-cd.sh.

I made a fork of the UCK source code on github and applied the changes.
You may just get the follwing file

https://raw.githubusercontent.com/jox/UCK/master/libraries/remaster-
live-cd.sh

and replace your /usr/lib/uck/remaster-live-cd.sh with it (this time
*not* in the chroot...).

You might also apply the attached patch as follows:

$ cd /usr/lib/uck
$ sudo patch -p2 remaster-live-cd.sh.bak < \
/path/to/fix-uck-missing-initd-scripts-1.patch

(The path in the patch is different since it is from the source code. Running
patch with -p2 from the directory the file is located will apply it properly.)

You may view the changes on github as well:

Fixed missing /scripts dir in chroot.
https://github.com/jox/UCK/commit/2f14005cd47845d7496e6a2b1bdd72a553fd6be2

Fixed "grub-probe postinst/postrm hack" in chroot.
https://github.com/jox/UCK/commit/d2e2ffbbae80392357b8bf442d28678f9298c52a

Added hack to invoke-rc.d in chroot to ignore missing init scripts.
https://github.com/jox/UCK/commit/4c8277459c42f089fd73e6ae9a25d3e73177f491

Hope this helps

** Patch added: "Patch to apply fixes to /usr/lib/uck/remaster-live-cd.sh"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+attachment/4190563/+files/fix-uck-missing-initd-scripts-1.patch

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

Title:
failure to update libpam-systemd in 14.04 due to missing logind init
script

Status in “systemd” package in Ubuntu:
Fix Released
Status in “systemd” source package in Trusty:
Triaged
Status in “systemd” source package in Utopic:
Fix Released

Bug description:
Hi,

while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
state. 'apt-get -f install' from within the chroot will not fix it,
but if the build is made bootable and put into a iso/VM you can
recover that way in a live session.

the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't
exist) and not /etc/init/systemd-logind.conf (does exist).
?

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
libpam-systemd
1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
3 not fully installed or removed.
Need to get 0 B/25.2 kB of archives.
After this operation, 1024 B of additional disk space will be used.
(Reading database ... 113986 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: warning: subprocess old pre-removal script returned error exit status
100
dpkg: trying script from the new package instead ...
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing archive
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
subprocess new pre-removal script returned error exit status 100
invoke-rc.d: unknown initscript, /et

[Touch-packages] [Bug 1363309] Re: package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64 2.19-0ubuntu6.1 cannot be configured because libc6

2014-08-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64
  2.19-0ubuntu6.1 cannot be configured because libc6

Status in “eglibc” package in Ubuntu:
  New

Bug description:
  I was upragrading my ubuntu 12.04 to ubuntu 14 something and there was
  a power outage. Now I can't open Ubuntu Software Center, I would be
  greatful if someone could help me.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6.1
  ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
  Uname: Linux 3.5.0-54-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Aug 29 19:59:30 2014
  Dependencies:
   gcc-4.6-base 4.6.3-1ubuntu5
   libc6 2.19-0ubuntu6.1
   libgcc1 1:4.6.3-1ubuntu5
   multiarch-support 2.15-0ubuntu10.6
  DuplicateSignature: package:libc6:2.19-0ubuntu6.1:libc6:amd64 2.19-0ubuntu6.1 
cannot be configured because libc6
  ErrorMessage: libc6:amd64 2.19-0ubuntu6.1 cannot be configured because libc6
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64 
2.19-0ubuntu6.1 cannot be configured because libc6
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (6 days ago)

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

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

[Touch-packages] [Bug 1363309] [NEW] package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64 2.19-0ubuntu6.1 cannot be configured because libc6

2014-08-29 Thread Julia

Public bug reported:

I was upragrading my ubuntu 12.04 to ubuntu 14 something and there was a
power outage. Now I can't open Ubuntu Software Center, I would be
greatful if someone could help me.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6 2.19-0ubuntu6.1
ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
Uname: Linux 3.5.0-54-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Fri Aug 29 19:59:30 2014
Dependencies:
 gcc-4.6-base 4.6.3-1ubuntu5
 libc6 2.19-0ubuntu6.1
 libgcc1 1:4.6.3-1ubuntu5
 multiarch-support 2.15-0ubuntu10.6
DuplicateSignature: package:libc6:2.19-0ubuntu6.1:libc6:amd64 2.19-0ubuntu6.1 
cannot be configured because libc6
ErrorMessage: libc6:amd64 2.19-0ubuntu6.1 cannot be configured because libc6
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
MarkForUpload: True
SourcePackage: eglibc
Title: package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64 
2.19-0ubuntu6.1 cannot be configured because libc6
UpgradeStatus: Upgraded to trusty on 2014-08-23 (6 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64
  2.19-0ubuntu6.1 cannot be configured because libc6

Status in “eglibc” package in Ubuntu:
  New

Bug description:
  I was upragrading my ubuntu 12.04 to ubuntu 14 something and there was
  a power outage. Now I can't open Ubuntu Software Center, I would be
  greatful if someone could help me.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6.1
  ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
  Uname: Linux 3.5.0-54-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Aug 29 19:59:30 2014
  Dependencies:
   gcc-4.6-base 4.6.3-1ubuntu5
   libc6 2.19-0ubuntu6.1
   libgcc1 1:4.6.3-1ubuntu5
   multiarch-support 2.15-0ubuntu10.6
  DuplicateSignature: package:libc6:2.19-0ubuntu6.1:libc6:amd64 2.19-0ubuntu6.1 
cannot be configured because libc6
  ErrorMessage: libc6:amd64 2.19-0ubuntu6.1 cannot be configured because libc6
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6.1 failed to install/upgrade: libc6:amd64 
2.19-0ubuntu6.1 cannot be configured because libc6
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (6 days ago)

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

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

[Touch-packages] [Bug 1353171] Re: Misparses dpkg status line, fails to write apport reports

This bug was fixed in the package apt - 1.0.4ubuntu8

---
apt (1.0.4ubuntu8) utopic; urgency=medium

  * apt-pkg/deb/dpkgpm.cc:
- update string matching for dpkg I/O errors. (LP: #1363257)
- properly parse the dpkg status line so that package name is properly set
  and an apport report is created. Thanks to Anders Kaseorg for the patch.
  (LP: #1353171)
 -- Brian MurrayFri, 29 Aug 2014 15:15:17 -0700

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

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

Title:
  Misparses dpkg status line, fails to write apport reports

Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  For a while apt has not been writing apport reports for dpkg
  maintainer script errors. Here’s why:

  • pkgDPkgPM::ProcessDpkgStatusLine sees a line like
  "status: cyrus-clients : error : subprocess installed post-installation 
script returned error exit status 1".
  • StringSplit splits it into
  list == {"status", "cyrus-clients ", "error ", "subprocess installed 
post-installation script returned error exit status 1"}.
  • pkgname is set to Strip(list[1]) == "cyrus-clients".
  • However, the original list[1] == "cyrus-clients " (with a trailing space) 
is passed to WriteApportReport.
  • WriteApport fails to find "cyrus-clients " in the cache, and bails out.

  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libapt-pkg4.12 1.0.4ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  Date: Tue Aug  5 19:19:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1339 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: apt
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (278 days ago)

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

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

[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date

This bug was fixed in the package apt - 1.0.4ubuntu8

---
apt (1.0.4ubuntu8) utopic; urgency=medium

  * apt-pkg/deb/dpkgpm.cc:
- update string matching for dpkg I/O errors. (LP: #1363257)
- properly parse the dpkg status line so that package name is properly set
  and an apport report is created. Thanks to Anders Kaseorg for the patch.
  (LP: #1353171)
 -- Brian MurrayFri, 29 Aug 2014 15:15:17 -0700

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

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  Fix Released
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date

** Branch linked: lp:ubuntu/utopic-proposed/apt

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 1353171] Re: Misparses dpkg status line, fails to write apport reports

** Branch linked: lp:ubuntu/utopic-proposed/apt

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

Title:
  Misparses dpkg status line, fails to write apport reports

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  For a while apt has not been writing apport reports for dpkg
  maintainer script errors. Here’s why:

  • pkgDPkgPM::ProcessDpkgStatusLine sees a line like
  "status: cyrus-clients : error : subprocess installed post-installation 
script returned error exit status 1".
  • StringSplit splits it into
  list == {"status", "cyrus-clients ", "error ", "subprocess installed 
post-installation script returned error exit status 1"}.
  • pkgname is set to Strip(list[1]) == "cyrus-clients".
  • However, the original list[1] == "cyrus-clients " (with a trailing space) 
is passed to WriteApportReport.
  • WriteApport fails to find "cyrus-clients " in the cache, and bails out.

  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libapt-pkg4.12 1.0.4ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  Date: Tue Aug  5 19:19:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1339 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: apt
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (278 days ago)

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

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

[Touch-packages] [Bug 1363301] Re: systemd-logind crashed with SIGABRT

2014-08-29 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT

Status in “systemd” package in Ubuntu:
  New

Bug description:
  error reported after log in.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  Uname: Linux 3.17.0-031700rc2-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  Date: Fri Aug 29 22:51:49 2014
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2014-08-16 (13 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140815)
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: systemd-logind crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1353171] Re: Misparses dpkg status line, fails to write apport reports

Thanks for the patch, I've uploaded it to utopic.

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

Title:
  Misparses dpkg status line, fails to write apport reports

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  For a while apt has not been writing apport reports for dpkg
  maintainer script errors. Here’s why:

  • pkgDPkgPM::ProcessDpkgStatusLine sees a line like
  "status: cyrus-clients : error : subprocess installed post-installation 
script returned error exit status 1".
  • StringSplit splits it into
  list == {"status", "cyrus-clients ", "error ", "subprocess installed 
post-installation script returned error exit status 1"}.
  • pkgname is set to Strip(list[1]) == "cyrus-clients".
  • However, the original list[1] == "cyrus-clients " (with a trailing space) 
is passed to WriteApportReport.
  • WriteApport fails to find "cyrus-clients " in the cache, and bails out.

  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libapt-pkg4.12 1.0.4ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  Date: Tue Aug  5 19:19:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1339 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: apt
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (278 days ago)

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

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

[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date

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

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 1353171] Re: Misparses dpkg status line, fails to write apport reports

** Branch linked: lp:ubuntu/apt

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

Title:
  Misparses dpkg status line, fails to write apport reports

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  For a while apt has not been writing apport reports for dpkg
  maintainer script errors. Here’s why:

  • pkgDPkgPM::ProcessDpkgStatusLine sees a line like
  "status: cyrus-clients : error : subprocess installed post-installation 
script returned error exit status 1".
  • StringSplit splits it into
  list == {"status", "cyrus-clients ", "error ", "subprocess installed 
post-installation script returned error exit status 1"}.
  • pkgname is set to Strip(list[1]) == "cyrus-clients".
  • However, the original list[1] == "cyrus-clients " (with a trailing space) 
is passed to WriteApportReport.
  • WriteApport fails to find "cyrus-clients " in the cache, and bails out.

  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libapt-pkg4.12 1.0.4ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  Date: Tue Aug  5 19:19:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1339 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: apt
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (278 days ago)

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

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

[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date

** Branch linked: lp:ubuntu/apt

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 734221] Re: [Intel Cantiga HDMI] PA test tone failed (alsa tone succeeded)

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

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

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

Title:
  [Intel Cantiga HDMI] PA test tone failed (alsa tone succeeded)

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  all my volume levels are at 100%, but i'm still unable to hear any
  sound from any applications! But, I created a new user and Voila!!! i
  have sound there.. but not in my original user!! i have no idea what
  the problem is... any level of help regarding this would be highly
  appreciated.

  And yeah.. i'm running Ubuntu 10.10 by the way! if that helps

  Thank You
  Abhith K

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abhith 1488 F pulseaudio
   /dev/snd/pcmC0D3p:   abhith 1488 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf470 irq 47'
 Mixer name : 'Conexant CX20561 (Hermosa)'
 Components : 'HDA:80862802,80860101,0010 
HDA:14f15051,17aac001,0010'
 Controls  : 18
 Simple ctrls  : 8
  CheckboxSubmission: 39dad46ca062c64bd3319a356e522123
  CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab
  Date: Sun Mar 13 14:50:12 2011
  InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 
(20101007)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: pulseaudio
  Symptom: audio
  Title: [Intel Cantiga HDMI] PA test tone failed (alsa tone succeeded)
  dmi.bios.date: 04/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 18CN44WW(V2.53)
  dmi.board.name: NITU1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr18CN44WW(V2.53):bd04/19/2010:svnLENOVO:pn2958:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 2958
  dmi.product.version: Lenovo G550
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1325001] Re: improve app startup time

2014-08-29 Thread Tiago Salem Herrmann

** Branch linked: lp:~tiagosh/messaging-app/improve_startup_time

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

Title:
  improve app startup time

Status in Address Book App:
  Fix Released
Status in Camera App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Gallery App:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Web Browser App:
  Fix Released
Status in “address-book-app” package in Ubuntu:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “dialer-app” package in Ubuntu:
  In Progress
Status in “gallery-app” package in Ubuntu:
  Confirmed
Status in “messaging-app” package in Ubuntu:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
  Fix Released

Bug description:
  use the profiling tools in QtCreator and tips suggested by Florian here:
  
https://docs.google.com/a/canonical.com/presentation/d/1H0_Y70jadTwz0bc6VXgZNzD1xsvHEX57lULWRm3-LM4/edit#slide=id.p

  Defer as much as possible to happen until after the UI is displayed

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

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

[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date

I've looked around Launchpad for package failures with the string
"failed to (read|write|seek)" and haven't found any, I've only found
errors regarding "unexpected end of file or stream". The other apport
package failures not showing up may be due to bug 1353171 though.

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  New

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 1359590] Re: Getty's on serial consoles need to be consistent

2014-08-29 Thread Ben Howard

One big thing to consider with this is that some clouds (i.e CloudSigma
and Joyent) use a serial console as a meta-data channel.  In at least
one case, activating a getty on the meta-data channel tty will result in
the instance being unbootable.  For this reason, I think that baking
them into the Cloud Images is probably a bad thing.

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

Title:
  Getty's on serial consoles need to be consistent

Status in Init scripts for use on cloud images:
  Confirmed
Status in “util-linux” package in Ubuntu:
  Confirmed

Bug description:
  In our cloud images today we launch a getty on ttyS0, as long as it's
  not in a container. We don't launch a getty on ttyS1-n even if they
  exist.

  In MAAS, which also uses cloud images, it would often be useful to put
  getty's on the serial port that is mapped to remote serial access,
  such as IPMI SOL. It is however difficult to know which is the correct
  getty.

  Broadly speaking I think we should have a consistent approach to
  getty's. That might mean:

   * launch a getty on each ttySn that passes an stty test (as per ttyS0 
currently)
   * allow cloud-init to prevent some of those, via vendordata or userdata or 
default behaviour per-cloud

  or

   * launch no getty's on ttyS, but
   * allow cloud-init to create them based on vendordata or userdata or default 
behaviour per-cloud

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1359590/+subscriptions

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

[Touch-packages] [Bug 1363214] Re: allow PINs of variable length instead of just 4 digits

2014-08-29 Thread Michał Sawicz

This (4 digit and auto-confirmation) was an explicit and reiterated
design request. Added ubuntu-ux for reflection then.

FWIW the lockscreen will only allow you typing the PIN a few times
before getting locked up for 5 minutes (or reboot...), that should help
slightly with the robustness of the lock.

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

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

Title:
  allow PINs of variable length instead of just 4 digits

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Currently when setting a PIN on the device, it must be 4 digits. This
  is artificially limiting. Other platforms (eg Android) allow longer
  PINs. It has always been my understanding that we should support
  Swipe, Passphrase and PIN where Passphrase and PIN can be arbitrarily
  long.

  However, once longer PINs are supported, we will have to add an Enter
  key. Right now, the lockscreen checks the PIN once 4 digits are added
  so that you don't have to press Enter. I guess this was done for
  usability, but would be a security issue because an attacker can
  easily determine the PIN length, which makes it easier to for an
  attacker to guess the PIN. Eg, if I have a 5 digit PIN set, then an
  attacker need only type '1' and know that the PIN is only five
  characters. Now, a PIN isn't strong to begin with and an automated
  attack could rather quickly brute force PINs, but we shouldn't make it
  easier for someone manually trying to guess the PIN.

  The passphrase lockscreen prompt correctly allows variable length
  passphrases and requires you to press Enter.

  I suggest moving the 'X' up t the left of '0' and an Enter symbol to
  the rigth of '0'.

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

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

[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly

2014-08-29 Thread Jean-Baptiste Lallement

s/which/while/

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

Title:
  unity8 freezes randomly

Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin #205

  [Sorry for the poor description]

  On krillin UI freeze randomly. For example on the screenshot it
  occurred while dragging the greeter to unlock the phone. I was playing
  music, woke up the phone with the power button to turn the display on
  and did a right edge swipe to remove the greeter.

  This has been reported by several people in the past days, but I
  didn't find a pattern to reproduce this bug reliably.

  There is no crash in /var/crash and no apport activity.
  If I press the power button to turn the screen off/on again, the greeter is 
completely displayed (ie. doesn't cover half of the screen like the screenshot) 
but the UI is not responsive to gestures or input events. A long press on the 
power button shows the shutdown dialog but none of the button can be pressed.

  top doesn't show any specific process going crazy

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140822-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: armhf
  Date: Sat Aug 23 14:18:00 2014
  InstallationDate: Installed on 2014-08-23 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140823-020205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly

2014-08-29 Thread Jean-Baptiste Lallement

it happened which the switcher was active, it suddenly froze.

** Attachment added: "gdb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+attachment/4190464/+files/gdb.txt

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

Title:
  unity8 freezes randomly

Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin #205

  [Sorry for the poor description]

  On krillin UI freeze randomly. For example on the screenshot it
  occurred while dragging the greeter to unlock the phone. I was playing
  music, woke up the phone with the power button to turn the display on
  and did a right edge swipe to remove the greeter.

  This has been reported by several people in the past days, but I
  didn't find a pattern to reproduce this bug reliably.

  There is no crash in /var/crash and no apport activity.
  If I press the power button to turn the screen off/on again, the greeter is 
completely displayed (ie. doesn't cover half of the screen like the screenshot) 
but the UI is not responsive to gestures or input events. A long press on the 
power button shows the shutdown dialog but none of the button can be pressed.

  top doesn't show any specific process going crazy

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140822-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: armhf
  Date: Sat Aug 23 14:18:00 2014
  InstallationDate: Installed on 2014-08-23 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140823-020205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date

Reviewing the strings returned by lib/dpkg/buffer.c the following patch
should resolve the issue, although this is still not ideal.

 $ bzr cdiff
=== modified file 'apt-pkg/deb/dpkgpm.cc'
--- apt-pkg/deb/dpkgpm.cc   2014-06-10 19:00:00 +
+++ apt-pkg/deb/dpkgpm.cc   2014-08-29 20:41:09 +
@@ -1668,9 +1668,10 @@
// do not report dpkg I/O errors, this is a format string, so we compare
// the prefix and the suffix of the error with the dpkg error message
vector io_errors;
-   io_errors.push_back(string("failed to read on buffer copy for %s"));
-   io_errors.push_back(string("failed in write on buffer copy for %s"));
-   io_errors.push_back(string("short read on buffer copy for %s"));
+   io_errors.push_back(string("failed to read"));
+   io_errors.push_back(string("failed to write"));
+   io_errors.push_back(string("failed to seek"));
+   io_errors.push_back(string("unexpected end of file or stream"));
 
for (vector::iterator I = io_errors.begin(); I != io_errors.end(); 
++I)

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  New

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 1363257] [NEW] string matching for dpkg I/O errors in dpkgpm.cc is out of date

Public bug reported:

The following error strings are no longer returned by dpkg:

   io_errors.push_back(string("failed to read on buffer copy for %s"));
   io_errors.push_back(string("failed in write on buffer copy for %s"));
   io_errors.push_back(string("short read on buffer copy for %s"));

Subsequently, apport package installation failures are being created for
these types of crashes and they should not be.  Additionally, there is a
new error returned by dpkg ("unexpected end of file or stream" as seen
in bug 1361489) which should also be blocked.

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

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

Title:
  string matching for dpkg I/O errors in dpkgpm.cc is out of date

Status in “apt” package in Ubuntu:
  New

Bug description:
  The following error strings are no longer returned by dpkg:

 io_errors.push_back(string("failed to read on buffer copy for %s"));
 io_errors.push_back(string("failed in write on buffer copy for %s"));
 io_errors.push_back(string("short read on buffer copy for %s"));

  Subsequently, apport package installation failures are being created
  for these types of crashes and they should not be.  Additionally,
  there is a new error returned by dpkg ("unexpected end of file or
  stream" as seen in bug 1361489) which should also be blocked.

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

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

[Touch-packages] [Bug 1359299] Re: utopic 3.16.0-9 iso boots to desktop no unity

2014-08-29 Thread Stephen M. Webb

Yes, that is what bisection does.  It essentially performs a binary
search on all of the dozens to hundreds of patches that go into minor
kernel point releases in an effort to identify the changeset that
resulted in the unwanted behaviour.

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

Title:
  utopic 3.16.0-9 iso boots to desktop no unity

Status in “linux” package in Ubuntu:
  Incomplete
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre.
  Boots 3.16.0-6 amd64 fine, runs compiz 3D fine.  

  Today's amd64 iso download, 20 August, boots to desktop & cursor.  
  No unity.
  Did ubuntu-bug from command line on the booted iso, saved report.

  Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file.

  Planet Ubuntu asked for results on 3.16.0-9 so this is my result.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-9-generic 3.16.0-9.14
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.341
  Date: Wed Aug 20 16:57:57 2014
  LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140820)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper 
iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1353171] Re: Misparses dpkg status line, fails to write apport reports

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

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

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Misparses dpkg status line, fails to write apport reports

Status in “apt” package in Ubuntu:
  Triaged
Status in “apt” source package in Trusty:
  Triaged

Bug description:
  For a while apt has not been writing apport reports for dpkg
  maintainer script errors. Here’s why:

  • pkgDPkgPM::ProcessDpkgStatusLine sees a line like
  "status: cyrus-clients : error : subprocess installed post-installation 
script returned error exit status 1".
  • StringSplit splits it into
  list == {"status", "cyrus-clients ", "error ", "subprocess installed 
post-installation script returned error exit status 1"}.
  • pkgname is set to Strip(list[1]) == "cyrus-clients".
  • However, the original list[1] == "cyrus-clients " (with a trailing space) 
is passed to WriteApportReport.
  • WriteApport fails to find "cyrus-clients " in the cache, and bails out.

  Patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libapt-pkg4.12 1.0.4ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  Date: Tue Aug  5 19:19:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1339 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: apt
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (278 days ago)

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

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

[Touch-packages] [Bug 1316057] Re: webbrowser-app AP failures after UITK upgrade

2014-08-29 Thread Zsombor Egri

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  webbrowser-app AP failures after UITK upgrade

Status in Ubuntu Keyboard:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released

Bug description:
  After the latest ubuntu-ui-toolkit upgrade 5 webbrowser-app tests have
  started failing reliably:

  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/11:20140505:20140501/7864/webbrowser_app/

  Downgrading UITK to 0.1.46+14.04.20140408.1-0ubuntu1 fixes the issue,
  for example testable by running phablet-test-run
  webbrowser_app.tests.test_tabs.TestTabs.test_close_last_open_tab

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

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

[Touch-packages] [Bug 1351537] Re: app preview images cannot be expanded to full size

** Tags added: touch-2014-10-30

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

Title:
  app preview images cannot be expanded to full size

Status in The Unity 8 shell:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  In the Click app store, apps include images to show what they look
  like while running.  This is nice, but I often want to zoom in to see
  the details.  This function works in Ubuntu Software Center and in the
  Android app store, not to mention most other online stores (whether
  for apps or not), but not in Click.

  As a sanity test, I handed an Ubuntu phone to a muggle and asked her
  to find an interesting app and install it.  She found the app store,
  found an app, looked at the previews, and then tried for a couple
  minutes to enlarge the images before giving up.  She was then
  frustrated and didn't bother to actually  tap 'install'.

  We should probably add the ability to view the full image.

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

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

[Touch-packages] [Bug 1340510] Re: session screen seen upon quick power key strike

** Tags added: touch-2014-10-2

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

Title:
  session screen seen upon quick power key strike

Status in Mir:
  Opinion
Status in Mir 0.4 series:
  Won't Fix
Status in Mir 0.5 series:
  Won't Fix
Status in Mir 0.6 series:
  Opinion
Status in Unity System Compositor:
  New
Status in The Unity 8 shell:
  New
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Image #125 on N4

  1) boot phone and unlock phone to display dash
  2) strike power key to blank & unblank screen quickly
  3) the dash is seen instead of lockscreen for a brief moment

  logging against u-s-c as this was fixed, but power policy changes may
  have effected this

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

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

[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text "Empty!" with something more useful

** Tags added: touch-2014-9-11

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

Title:
  [Indicators] replace the text "Empty!" with something more useful

Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “indicator-messages” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  when clearing the menu on this indicator (and others), the text
  "Empty!" is displayed. Can we please remove that and put something
  more useful there. It looks bad. Need advise from design..

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

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

[Touch-packages] [Bug 1306499] Re: Sound indicator is jumpy while music playing (grooveshark)

video easier to see
https://www.youtube.com/watch?v=z-CK1amiJBo

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

Title:
  Sound indicator is jumpy while music playing (grooveshark)

Status in Sound Menu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Open sound indicator
  Try and swipe the volume up and down
  Try and increase/decrease volume with the hardware vol+ & vol- keys
  Note that the slider takes a long time to update, and sometimes leaps 
backwards and forwards despite you only holding one button down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: armhf
  Date: Fri Apr 11 10:39:43 2014
  InstallationDate: Installed on 2014-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140411)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1306499/+subscriptions

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

[Touch-packages] [Bug 1306499] Re: Sound indicator is laggy

retested on image #213 on N4

the slider itself isn't laggy and quite smooth.
however, when a song is playing in grooveshark it can be seen "jumpy".
And after playing with it a bit it does seem to have something to do with 
potentially be queuing events (in Qt?) and reading current volume to draw its 
placement ? (vs ignore current vol if touch even "release" hasn't occured)

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

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

Title:
  Sound indicator is jumpy while music playing (grooveshark)

Status in Sound Menu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Open sound indicator
  Try and swipe the volume up and down
  Try and increase/decrease volume with the hardware vol+ & vol- keys
  Note that the slider takes a long time to update, and sometimes leaps 
backwards and forwards despite you only holding one button down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: armhf
  Date: Fri Apr 11 10:39:43 2014
  InstallationDate: Installed on 2014-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140411)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1306499/+subscriptions

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

[Touch-packages] [Bug 1306499] Re: Sound indicator is laggy

removing tag as the severity/criticality has certainly changed

** Tags removed: rtm14
** Tags added: touch-2014-10-16

** Summary changed:

- Sound indicator is laggy
+ Sound indicator is jumpy while music playing (grooveshark)

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

Title:
  Sound indicator is jumpy while music playing (grooveshark)

Status in Sound Menu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Open sound indicator
  Try and swipe the volume up and down
  Try and increase/decrease volume with the hardware vol+ & vol- keys
  Note that the slider takes a long time to update, and sometimes leaps 
backwards and forwards despite you only holding one button down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: armhf
  Date: Fri Apr 11 10:39:43 2014
  InstallationDate: Installed on 2014-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140411)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1306499/+subscriptions

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

[Touch-packages] [Bug 1349950] Re: Preview header widget doesn't wrap

** Tags added: touch-2014-10-2

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

Title:
  Preview header widget doesn't wrap

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Im populating a preview with text received from the etsy API, and it's
  being run off the screen and not wrapped automatically.  See
  screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.89+14.10.20140624-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 29 12:57:35 2014
  InstallationDate: Installed on 2014-05-09 (81 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to utopic on 2014-06-26 (33 days ago)

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

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

[Touch-packages] [Bug 1342875] Re: Unable to delete currently logged in user

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

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

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

Title:
  Unable to delete currently logged in user

Status in “shadow” package in Ubuntu:
  Confirmed
Status in “shadow” source package in Trusty:
  Confirmed
Status in “shadow” source package in Utopic:
  Confirmed

Bug description:
  A user can not delete themselves using the command 'sudo userdel -rf
  ', this is common in cloud tools that clean up running
  images prior to capture.  A quick test shows that this worked from
  Precise (didn't look back further) to Raring and stopped working with
  Saucy.

  Here's a quick example of the failure (from trusty):
  # sudo adduser test
  # sudo usermod -aG sudo test
  ## As the 'test' user
  # sudo userdel -rf test
  userdel: user test is currently used by process 9600
  userdel: cannot open /etc/subuid
  ## User is not removed

  Previously (output from precise)
  # sudo userdel -rf test
  userdel: user test is currently logged in
  userdel: warning: can't remove /var/mail/test: No such file or directory
  ## User is removed

  This is being run as the last command by tools that remove the
  'ubuntu' user to clean the image prior to capture.  This had
  previously worked and it is preferable that this could be made to work
  again.  The alternative is removal by root, but the root user on cloud
  images is locked down and we would not want the user to enable root to
  run userdel on the risk of it not getting disabled properly prior to
  image capture.

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

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

[Touch-packages] [Bug 1342875] Re: Unable to delete currently logged in user

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

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

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

Title:
  Unable to delete currently logged in user

Status in “shadow” package in Ubuntu:
  Confirmed
Status in “shadow” source package in Trusty:
  Confirmed
Status in “shadow” source package in Utopic:
  Confirmed

Bug description:
  A user can not delete themselves using the command 'sudo userdel -rf
  ', this is common in cloud tools that clean up running
  images prior to capture.  A quick test shows that this worked from
  Precise (didn't look back further) to Raring and stopped working with
  Saucy.

  Here's a quick example of the failure (from trusty):
  # sudo adduser test
  # sudo usermod -aG sudo test
  ## As the 'test' user
  # sudo userdel -rf test
  userdel: user test is currently used by process 9600
  userdel: cannot open /etc/subuid
  ## User is not removed

  Previously (output from precise)
  # sudo userdel -rf test
  userdel: user test is currently logged in
  userdel: warning: can't remove /var/mail/test: No such file or directory
  ## User is removed

  This is being run as the last command by tools that remove the
  'ubuntu' user to clean the image prior to capture.  This had
  previously worked and it is preferable that this could be made to work
  again.  The alternative is removal by root, but the root user on cloud
  images is locked down and we would not want the user to enable root to
  run userdel on the risk of it not getting disabled properly prior to
  image capture.

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

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

[Touch-packages] [Bug 1342875] Re: Unable to delete currently logged in user

2014-08-29 Thread Ben Howard

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

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

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

Title:
  Unable to delete currently logged in user

Status in “shadow” package in Ubuntu:
  Confirmed
Status in “shadow” source package in Trusty:
  Confirmed
Status in “shadow” source package in Utopic:
  Confirmed

Bug description:
  A user can not delete themselves using the command 'sudo userdel -rf
  ', this is common in cloud tools that clean up running
  images prior to capture.  A quick test shows that this worked from
  Precise (didn't look back further) to Raring and stopped working with
  Saucy.

  Here's a quick example of the failure (from trusty):
  # sudo adduser test
  # sudo usermod -aG sudo test
  ## As the 'test' user
  # sudo userdel -rf test
  userdel: user test is currently used by process 9600
  userdel: cannot open /etc/subuid
  ## User is not removed

  Previously (output from precise)
  # sudo userdel -rf test
  userdel: user test is currently logged in
  userdel: warning: can't remove /var/mail/test: No such file or directory
  ## User is removed

  This is being run as the last command by tools that remove the
  'ubuntu' user to clean the image prior to capture.  This had
  previously worked and it is preferable that this could be made to work
  again.  The alternative is removal by root, but the root user on cloud
  images is locked down and we would not want the user to enable root to
  run userdel on the risk of it not getting disabled properly prior to
  image capture.

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

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

[Touch-packages] [Bug 990982] Re: [Multiarch] libfreetype6-dev:i386 dependencies issue

This bug was fixed in the package glibc - 2.19-10ubuntu1

---
glibc (2.19-10ubuntu1) utopic; urgency=medium

  * Merge with Debian unstable, bringing in several CVE fixes (LP: #1362409)
  * Enable systemtap support for Ubuntu which was dropped in Debian for now.
  * Move MIN_KERNEL_SUPPORTED to 2.6.32 on x86 now that hardy PPAs are dead.
  * libc-dev no longer Recommends 'gcc | c-compiler' (LP: #990982, #1005097)

glibc (2.19-10) unstable; urgency=medium

  [ Aurelien Jarno ]
  * debian/rules: drop the i486 to i586 GNU triplet conversion.
  * debian/control.in/main: build-depends on dpkg-dev (>= 1.17.1) and
gcc-4.8 (>= 4.8.3-8) to make sure to get the new i586 GNU triplet on
i386, hurd-i386 and kfreebsd-i386.
  * Remove iconv(1), iconvconfig(8), localedef(1) and sprof(1) manpages,
provided by the manpages packages starting with version 3.71.
  * patches/any/cvs-CVE-2014-5119.diff: New patch from upstream to remove
support for loadable gconv transliteration modules (CVE-2014-5119).

  [ Samuel Thibault ]
  * patches/hurd-i386/cvs-libpthread_guardsize.diff: Fix guard size computation.
Fixes the creation of thousands of threads, and thus pulseaudio testsuite.
Closes: #758671.
  * patches/hurd-i386/cvs-libpthread_std_thread.diff: New patch to deal with
std::thread using __pthread_key_create to detect presence of libpthread.
Fixes build of webkitgtk and most probably other libstdc++-related
failures.
  * patches/hurd-i386/submitted-bind_umask.diff: New patch to fix bind() when
umask is , fixes clamav testsuite. Closes: #759218.

  [ Adam Conrad ]
  * debian/patches/series: Actually apply the submitted arm64 alignment and
setcontext patches mentioned in 2.19-0experimental0 (closes: #759042)

glibc (2.19-9) unstable; urgency=medium

  [ Aurelien Jarno ]
  * debian/rules.d/control.mk: don't add libc6{,-dev}-{armel,armhf}
packages in debian/control as we don't build them in Debian. New dak
code checks for NEW packages directly in debian/control.

glibc (2.19-8) unstable; urgency=medium

  [ Helmut Grohne ]
  * debian/patches/build stage2 without selinux.  Closes: #742640.
  * Don't emit dependencies on libgcc when building stage2.  Closes: #755580.
  * Add a "nobiarch" build profile that inhibits all multilib packages from
being built.  Closes: #745380.

  [ Aurelien Jarno ]
  * debian/patches/arm64/cvs-includes-cleanup.diff: new patch from upstream to
clean sys/user.h and sys/procfs.h.  Closes: #755169.
  * debian/patches/s390/cvs-s390-abi-reversal.diff: new patch backported from
upstream to revert the S/390 jmp_buf/ucontext_t ABI change.
  * Update Turkish debconf translation, by Mert Dirik.  Closes: #757495.
  * Remove ia64 support.  Closes: #756095.
  * Update debian/copyright with the libidn/punycode.{c,h} license.  Closes:
#754731.
  * debian/control/libc: drop Recommends on: gcc | c-compiler.  Closes:
#747933.

glibc (2.19-7) unstable; urgency=high

  * debian/patches/localedata/unsubmitted-tst-setlocale3-ENV.diff: Apply
correct environment for the tst-setlocale3 test to find its locales.

glibc (2.19-6) unstable; urgency=high

  [ Aurelien Jarno ]
  * debian/patches/any/cvs-CVE-2014-0475.diff: fix a directory traversal in
locale environment handling (CVE-2014-0475).
  * debian/patches/any/cvs-setlocale-alloca.diff: Additional setlocale
hardening.
  * debian/control.in/main, debian/sysdeps/linux.mk: drop systemtap support.
sdt.h has been moved to a different location in the latest upload, and
it's not really clear on which architectures systemtap support should
be enabled.

  [ Helmut Grohne ]
  * debian/rules.d/debhelper.mk: fix dh_strip call in stage1.  Closes:
#754350.

  [ Petr Salinger ]
  * kfreebsd/local-sysdeps.diff: update to revision 5490 (from glibc-bsd).
  * kfreebsd/local-fbtl.diff: likewise.
  * update testsuite-checking/expected-results-*-kfreebsd-gnu-*

glibc (2.19-5) unstable; urgency=medium

  [ Aurelien Jarno ]
  * debian/sysdeps/mips*.mk: replace EGLIBC_PASSES into GLIBC_PASSES.
  * debian/patches/alpha/cvs-__pointer_chk_guard.diff: new patch from
upstream to fix testsuite failures on alpha.
  * debian/patches/alpha/local-string-functions.diff: disable strcmp
and strncmp as these functions behaves incorrectly when crossing
pages. This fixes badsalttest in the testsuite.
  * debian/debhelper.in/libc.postinst: don't run "telinit u" under systemd
Closes: #753725.
  * debian/testsuite-checking/expected-results-alpha-linux-gnu-libc: ignore
floating point failures, as alpha is not fully IEEE compliant.  Closes:
#753099.
  * testsuite-checking/expected-results-*s390*: ignore tst-cancelx17.out
failure, it is due to a bug in the test (see BZ #12683).

  [ Helmut Grohne ]
  * Rename the bootstrap stage to DEB_BUILD_PROFILES=stage1 to conform
with https://wiki.debian.org/BuildProfileSpec. (Closes: #752480)
  * Don't try to install xen headers in i386 boo

[Touch-packages] [Bug 1362409] Re: please fix CVE-2014-5119

This bug was fixed in the package glibc - 2.19-10ubuntu1

---
glibc (2.19-10ubuntu1) utopic; urgency=medium

  * Merge with Debian unstable, bringing in several CVE fixes (LP: #1362409)
  * Enable systemtap support for Ubuntu which was dropped in Debian for now.
  * Move MIN_KERNEL_SUPPORTED to 2.6.32 on x86 now that hardy PPAs are dead.
  * libc-dev no longer Recommends 'gcc | c-compiler' (LP: #990982, #1005097)

glibc (2.19-10) unstable; urgency=medium

  [ Aurelien Jarno ]
  * debian/rules: drop the i486 to i586 GNU triplet conversion.
  * debian/control.in/main: build-depends on dpkg-dev (>= 1.17.1) and
gcc-4.8 (>= 4.8.3-8) to make sure to get the new i586 GNU triplet on
i386, hurd-i386 and kfreebsd-i386.
  * Remove iconv(1), iconvconfig(8), localedef(1) and sprof(1) manpages,
provided by the manpages packages starting with version 3.71.
  * patches/any/cvs-CVE-2014-5119.diff: New patch from upstream to remove
support for loadable gconv transliteration modules (CVE-2014-5119).

  [ Samuel Thibault ]
  * patches/hurd-i386/cvs-libpthread_guardsize.diff: Fix guard size computation.
Fixes the creation of thousands of threads, and thus pulseaudio testsuite.
Closes: #758671.
  * patches/hurd-i386/cvs-libpthread_std_thread.diff: New patch to deal with
std::thread using __pthread_key_create to detect presence of libpthread.
Fixes build of webkitgtk and most probably other libstdc++-related
failures.
  * patches/hurd-i386/submitted-bind_umask.diff: New patch to fix bind() when
umask is , fixes clamav testsuite. Closes: #759218.

  [ Adam Conrad ]
  * debian/patches/series: Actually apply the submitted arm64 alignment and
setcontext patches mentioned in 2.19-0experimental0 (closes: #759042)

glibc (2.19-9) unstable; urgency=medium

  [ Aurelien Jarno ]
  * debian/rules.d/control.mk: don't add libc6{,-dev}-{armel,armhf}
packages in debian/control as we don't build them in Debian. New dak
code checks for NEW packages directly in debian/control.

glibc (2.19-8) unstable; urgency=medium

  [ Helmut Grohne ]
  * debian/patches/build stage2 without selinux.  Closes: #742640.
  * Don't emit dependencies on libgcc when building stage2.  Closes: #755580.
  * Add a "nobiarch" build profile that inhibits all multilib packages from
being built.  Closes: #745380.

  [ Aurelien Jarno ]
  * debian/patches/arm64/cvs-includes-cleanup.diff: new patch from upstream to
clean sys/user.h and sys/procfs.h.  Closes: #755169.
  * debian/patches/s390/cvs-s390-abi-reversal.diff: new patch backported from
upstream to revert the S/390 jmp_buf/ucontext_t ABI change.
  * Update Turkish debconf translation, by Mert Dirik.  Closes: #757495.
  * Remove ia64 support.  Closes: #756095.
  * Update debian/copyright with the libidn/punycode.{c,h} license.  Closes:
#754731.
  * debian/control/libc: drop Recommends on: gcc | c-compiler.  Closes:
#747933.

glibc (2.19-7) unstable; urgency=high

  * debian/patches/localedata/unsubmitted-tst-setlocale3-ENV.diff: Apply
correct environment for the tst-setlocale3 test to find its locales.

glibc (2.19-6) unstable; urgency=high

  [ Aurelien Jarno ]
  * debian/patches/any/cvs-CVE-2014-0475.diff: fix a directory traversal in
locale environment handling (CVE-2014-0475).
  * debian/patches/any/cvs-setlocale-alloca.diff: Additional setlocale
hardening.
  * debian/control.in/main, debian/sysdeps/linux.mk: drop systemtap support.
sdt.h has been moved to a different location in the latest upload, and
it's not really clear on which architectures systemtap support should
be enabled.

  [ Helmut Grohne ]
  * debian/rules.d/debhelper.mk: fix dh_strip call in stage1.  Closes:
#754350.

  [ Petr Salinger ]
  * kfreebsd/local-sysdeps.diff: update to revision 5490 (from glibc-bsd).
  * kfreebsd/local-fbtl.diff: likewise.
  * update testsuite-checking/expected-results-*-kfreebsd-gnu-*

glibc (2.19-5) unstable; urgency=medium

  [ Aurelien Jarno ]
  * debian/sysdeps/mips*.mk: replace EGLIBC_PASSES into GLIBC_PASSES.
  * debian/patches/alpha/cvs-__pointer_chk_guard.diff: new patch from
upstream to fix testsuite failures on alpha.
  * debian/patches/alpha/local-string-functions.diff: disable strcmp
and strncmp as these functions behaves incorrectly when crossing
pages. This fixes badsalttest in the testsuite.
  * debian/debhelper.in/libc.postinst: don't run "telinit u" under systemd
Closes: #753725.
  * debian/testsuite-checking/expected-results-alpha-linux-gnu-libc: ignore
floating point failures, as alpha is not fully IEEE compliant.  Closes:
#753099.
  * testsuite-checking/expected-results-*s390*: ignore tst-cancelx17.out
failure, it is due to a bug in the test (see BZ #12683).

  [ Helmut Grohne ]
  * Rename the bootstrap stage to DEB_BUILD_PROFILES=stage1 to conform
with https://wiki.debian.org/BuildProfileSpec. (Closes: #752480)
  * Don't try to install xen headers in i386 boo

[Touch-packages] [Bug 1363207] Re: mallit server running 100% cpu after launching osk in welcome wizard

2014-08-29 Thread Łukasz Zemczak

** Tags added: lt-age-20140829 lt-category-visible lt-prio-medium

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

Title:
  mallit server running 100% cpu after launching osk in welcome wizard

Status in “maliit-framework” package in Ubuntu:
  New

Bug description:
  Image#213 on N4
  fresh flash, haven't run anything, just after welcome wizard 
completedphone got hot & dash was black/missing.
  no crash files. Ran top and see mallit pegging 100%
  camako also seeing uper hot phone when he was testing a mir silo (which is 
why we tested virgin image), he also saw 100% cpu by mallit-server

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

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

[Touch-packages] [Bug 1361384] Re: Alsa and Pulse audio hang system when listening to music

2014-08-29 Thread xerofoify

options snd-usb-audio index=-2
options snd-hda-intel index=1 power_save=1 model=auto vid=1002 pid=aab0
options snd-hda-intel index=0 power_save=1 bdl_pos_adj=128 position_fix=-1 
align_buffer_size=0 model=auto vid=8086 pid=1c20
alias char-major-116 snd
alias snd-card-0 snd-hda-intel
alias snd-card-1 snd-hda-intel
options snd cards_limit=2
Here is my file parts I added as stated. 
This is the output from the command.
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 05)
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cape 
Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] [1002:aab0]
It's still not working and I seem to be fixing something.

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

Title:
  Alsa and Pulse audio hang system when listening to music

Status in “alsa-utils” package in Ubuntu:
  New

Bug description:
  I seem to be getting a hang and crash of my system every time I listen to 
music in the background. I have tried both pulseaudio
  and alsa but both crash every day or two. It's rather annoying. I am using 
14.04 Lubuntu and expect the music to not hang my system.
  Nick

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

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

[Touch-packages] [Bug 1312707] Re: [Dash] Dash should not reset when unfocused

** Tags added: touch-2014-9-25

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

Title:
  [Dash] Dash should not reset when unfocused

Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  1. Open Scopes scope
  2. Select scope
  3. Open result from surfacing or from search, such that Preview will contain 
a button launching a browser
  4. Press the button in the Preview
  5. Browser launches
  6. Swipe the browser away to right.

  What happens:
  Dash 'Apps' section is shown.

  What I expect to happen:
  Dash should show the scope result preview I was viewing. Otherwise I need to 
navigate back, search again, and possibly loose bandwidth and patience.

  --
  Desired resolution:

  See https://sites.google.com/a/canonical.com/unity8dash/navigating-
  the-dash

  Once the Dash is released as an app, the user can return to the
  previous state of the Dash using the right edge interactions. They can
  also tap on the Home button. A long left swipe will take them back to
  the 'Home scope' ie apps scope.

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

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

[Touch-packages] [Bug 1281084] Re: UnicodeDecodeError in is_closing_session

2014-08-29 Thread Václav Šmilauer

Just looking at the approt source, in is_closing_session, the error is
here:

with open('/proc/%s/environ' % pid) as e:
env = e.read().split('\0')

This is normally not a problem with python3, but apport runs for some
reason with the ascii encoding, which will fail when reading utf-8
encoded environment variable (in my case, it is "DEBFULLNAME=Václav
Šmilauer"). So the fix is perhaps

with open('/proc/%s/environ' % pid, encoding='utf-8') as e:
env = e.read().split('\0')

(that's what I did locally) or open the file with 'rb' and work on bytes
object rather than str.

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

Title:
  UnicodeDecodeError in is_closing_session

Status in “apport” package in Ubuntu:
  Confirmed

Bug description:
  From apport.log:

  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: called for pid 11135, 
signal 11, core limit 18446744073709551615
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: script: 
/usr/bin/pydoc2.7, interpreted by /usr/bin/python2.7 (command line 
"/usr/bin/python2.7 /usr/bin/pydoc -k .")
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: Unhandled exception:
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 373, in 
  if is_closing_session(pid, pidstat.st_uid):
File "/usr/share/apport/apport", line 214, in is_closing_session
  env = e.read().split('\0')
File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9786: 
ordinal not in range(128)
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: pid: 11229, uid: 1000, 
gid: 1000, euid: 0, egid: 0
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: environment: environ({})

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CrashReports:
   640:1000:114:120104180:2014-02-13 00:58:41.677010970 +0100:2014-02-13 
00:57:20.989009053 +0100:/var/crash/_opt_firefox_firefox.1000.crash
   640:1000:114:63870076:2014-02-13 00:00:35.972928127 +0100:2014-02-12 
23:59:49.260927017 +0100:/var/crash/_usr_lib_firefox_firefox.1000.crash
   640:1000:114:14175879:2014-02-09 10:23:03.104148831 +0100:2014-02-09 
10:22:57.576148699 +0100:/var/crash/_usr_bin_nautilus.1000.crash
  Date: Mon Feb 17 13:27:00 2014
  InstallationDate: Installed on 2012-05-28 (629 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (131 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2014-02-13T00:58:07.609010

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

-- 
Mailing list: https://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 1362973] Re: package udev 204-5ubuntu20.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

2014-08-29 Thread Dantes

Thank you for you help!
At the moment I cannot log in into the system. It seems the USB ports 
are not available any more and on this computer I do not have any serial 
port to connect the keyboard.

I move the hard disk on which there is the operating system on another 
hardware with serial ports for keyboard and mouse. Now I can log in into 
the system (graphical mode), but I cannot reach my USB key in any of the 
USB ports.

On this system I have also VirtualBox. When I try to run a virtual 
machine an error message is displayed asking to run "sudo 
/etc/init.d/vboxdrv setup" because there is some missing permission and 
it cannot find the kernel modules for VirtualBox and its virtual 
machines. I did the action, but it failed, telling me to read 
/var/log/vbox-install.log (this file is attached to this email)

After some hours during which the pc was on, I run the update utility 
and it found a kernel upgrade. I did the upgrade, then I tried again to 
run the virtualbox command and suddenly it worked! It also asks me to 
reboot the system, but at the moment I am managing the machine through 
TeamViewer: I don't want to reboot the system because I fear to 
definitely loose the contact with the pc. Tomorrow morning I will be 
near the pc, so I will do the reboot and I will send you further details.

I hope all the details in this email will be useful for something, at 
least recreating the situation...

Again, thanks for your support,
Your sincerely,

Samuele

On 29/08/2014 14:19, Ubuntu Foundations Team Bug Bot wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.  Reviewing your log files attached to this bug report it
> seems that a package failed to install due to a segmentation fault in
> the application being used for the package installation process.
> Unfortunately, this bug report isn't very useful in its current state
> and a crash report would be much more useful.  Could you try recreating
> this issue by enabling apport to catch the crash report 'sudo service
> apport start force_start=1' and then trying to install the same package
> again?  This process will create a new bug report so I am marking this
> one as Invalid.  Thanks again for helping out!
>
> [This is an automated message.  I apologize if it reached you
> inappropriately; please just reply to this message indicating so.]
>
> ** Tags added: package-install-segfault
>
> ** Changed in: systemd (Ubuntu)
> Status: New => Invalid
>

** Attachment added: "vbox-install.log"

https://bugs.launchpad.net/bugs/1362973/+attachment/4190391/+files/vbox-install.log

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

Title:
  package udev 204-5ubuntu20.3 failed to install/upgrade: subprocess new
  pre-installation script returned error exit status 2

Status in “systemd” package in Ubuntu:
  Invalid

Bug description:
  I was updating my system when suddenly it crashed down. Which can be
  the problem?

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.3
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules
  Date: Fri Aug 29 10:18:46 2014
  DuplicateSignature: package:udev:204-5ubuntu20.3:subprocess new 
pre-installation script returned error exit status 2
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2014-07-22 (37 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: FUJITSU SIEMENS P35T-FB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5ffc01f-c88b-49f7-bed6-2265b877fd59 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  Title: package udev 204-5ubuntu20.3 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 2
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.03
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P35T-FB
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: V3.03
  dmi.chassis.asset.tag: 0123ABC
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.03:bd09/27/2007:svnFUJITSUSIEMENS:pnP35T-FB:pvrV3.03:rvnFUJITSUSIEMENS:rnP35T-FB:rvrV3.03:cvnFUJITSUSIEMENS:ct3:cvr1.0:
  dmi.product.name: P35T-FB
  dmi.product.version: V3.03
  dmi.sys.vendor: FUJITSU SIEMENS

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

-- 
Mailing list: https://launch

[Touch-packages] [Bug 1281084] Re: UnicodeDecodeError in is_closing_session

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

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

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

Title:
  UnicodeDecodeError in is_closing_session

Status in “apport” package in Ubuntu:
  Confirmed

Bug description:
  From apport.log:

  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: called for pid 11135, 
signal 11, core limit 18446744073709551615
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: script: 
/usr/bin/pydoc2.7, interpreted by /usr/bin/python2.7 (command line 
"/usr/bin/python2.7 /usr/bin/pydoc -k .")
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: Unhandled exception:
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 373, in 
  if is_closing_session(pid, pidstat.st_uid):
File "/usr/share/apport/apport", line 214, in is_closing_session
  env = e.read().split('\0')
File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9786: 
ordinal not in range(128)
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: pid: 11229, uid: 1000, 
gid: 1000, euid: 0, egid: 0
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: environment: environ({})

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CrashReports:
   640:1000:114:120104180:2014-02-13 00:58:41.677010970 +0100:2014-02-13 
00:57:20.989009053 +0100:/var/crash/_opt_firefox_firefox.1000.crash
   640:1000:114:63870076:2014-02-13 00:00:35.972928127 +0100:2014-02-12 
23:59:49.260927017 +0100:/var/crash/_usr_lib_firefox_firefox.1000.crash
   640:1000:114:14175879:2014-02-09 10:23:03.104148831 +0100:2014-02-09 
10:22:57.576148699 +0100:/var/crash/_usr_bin_nautilus.1000.crash
  Date: Mon Feb 17 13:27:00 2014
  InstallationDate: Installed on 2012-05-28 (629 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (131 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2014-02-13T00:58:07.609010

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

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

[Touch-packages] [Bug 1281084] Re: UnicodeDecodeError in is_closing_session

2014-08-29 Thread Václav Šmilauer

Just adding more evidence:

ERROR: apport (pid 23189) Fri Aug 29 21:15:48 2014: called for pid 23182, 
signal 11, core limit 18446744073709551615
ERROR: apport (pid 23189) Fri Aug 29 21:15:48 2014: ignoring implausibly big 
core limit, treating as unlimited
ERROR: apport (pid 23189) Fri Aug 29 21:15:48 2014: executable: /usr/bin/gmsh 
(command line "gmsh")
ERROR: apport (pid 23189) Fri Aug 29 21:15:48 2014: Unhandled exception:
Traceback (most recent call last):
  File "/usr/share/apport/apport", line 391, in 
if is_closing_session(pid, pidstat.st_uid):
  File "/usr/share/apport/apport", line 213, in is_closing_session
env = e.read().split('\0')
  File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 65: 
ordinal not in range(128)
ERROR: apport (pid 23189) Fri Aug 29 21:15:48 2014: pid: 23189, uid: 1000, gid: 
1000, euid: 0, egid: 0
ERROR: apport (pid 23189) Fri Aug 29 21:15:48 2014: environment: environ({})

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

Title:
  UnicodeDecodeError in is_closing_session

Status in “apport” package in Ubuntu:
  Confirmed

Bug description:
  From apport.log:

  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: called for pid 11135, 
signal 11, core limit 18446744073709551615
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: script: 
/usr/bin/pydoc2.7, interpreted by /usr/bin/python2.7 (command line 
"/usr/bin/python2.7 /usr/bin/pydoc -k .")
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: Unhandled exception:
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 373, in 
  if is_closing_session(pid, pidstat.st_uid):
File "/usr/share/apport/apport", line 214, in is_closing_session
  env = e.read().split('\0')
File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9786: 
ordinal not in range(128)
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: pid: 11229, uid: 1000, 
gid: 1000, euid: 0, egid: 0
  ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: environment: environ({})

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CrashReports:
   640:1000:114:120104180:2014-02-13 00:58:41.677010970 +0100:2014-02-13 
00:57:20.989009053 +0100:/var/crash/_opt_firefox_firefox.1000.crash
   640:1000:114:63870076:2014-02-13 00:00:35.972928127 +0100:2014-02-12 
23:59:49.260927017 +0100:/var/crash/_usr_lib_firefox_firefox.1000.crash
   640:1000:114:14175879:2014-02-09 10:23:03.104148831 +0100:2014-02-09 
10:22:57.576148699 +0100:/var/crash/_usr_bin_nautilus.1000.crash
  Date: Mon Feb 17 13:27:00 2014
  InstallationDate: Installed on 2012-05-28 (629 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (131 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2014-02-13T00:58:07.609010

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

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

[Touch-packages] [Bug 1346838] Re: [Notification] an incoming call snap-decision notification does not use/display the secondary icon

** Changed in: unity8
   Status: In Progress => Fix Released

** Changed in: unity8 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [Notification] an incoming call snap-decision notification does not
  use/display the secondary icon

Status in Telephony Service:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in Server and client library for desktop notifications in Unity:
  Triaged
Status in The Unity 8 shell:
  Fix Released
Status in “telephony-service” package in Ubuntu:
  Fix Released
Status in “unity-notifications” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  In the new notification UI design a secondary icon needs to be used in the 
top right corner. This icon helps to indicate what kind of notification is 
received.
  E.g. for messaging this icon can define weather user is receiving an SMS, or 
MMS with video, image or v-card. Please refer to the latest notification spec. 
  
https://docs.google.com/a/canonical.com/document/d/1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz-oeM/edit#heading=h.ihcuz26wprxs

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1346838/+subscriptions

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

[Touch-packages] [Bug 1363226] [NEW] /usr/bin/ubuntu-location-serviced:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:std::__throw_bad_function

2014-08-29 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding location-service.  This problem was most recently seen with
version 2.0.1+14.10.20140825-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/dbd77e211013a84dc9db0bdaf1afe6a51c06a8f9
contains more details.

** Affects: location-service (Ubuntu)
 Importance: Undecided
 Assignee: Thomas Voß (thomas-voss)
 Status: In Progress


** Tags: utopic

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

Title:
  /usr/bin/ubuntu-location-
  
serviced:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_bad_function_call

Status in “location-service” package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding location-service.  This problem was most recently seen with
  version 2.0.1+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/dbd77e211013a84dc9db0bdaf1afe6a51c06a8f9
  contains more details.

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

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

[Touch-packages] [Bug 1363226] Re: /usr/bin/ubuntu-location-serviced:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:std::__throw_bad_function_c

2014-08-29 Thread Thomas Voß

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: location-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 location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1363226

Title:
  /usr/bin/ubuntu-location-
  
serviced:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_bad_function_call

Status in “location-service” package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding location-service.  This problem was most recently seen with
  version 2.0.1+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/dbd77e211013a84dc9db0bdaf1afe6a51c06a8f9
  contains more details.

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

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

[Touch-packages] [Bug 1363214] Re: please allow PINs of variable length and require 'Enter' key when entering PIN

2014-08-29 Thread Jamie Strandboge

** Summary changed:

- require 'Enter' key when entering PIN
+ please allow PINs of variable length and require 'Enter' key when entering PIN

** Description changed:

- If I set a PIN on the device, I am prompted to enter it on screen unlock
- (great!). Right now, the lockscreen checks the PIN as you type so that
- you don't have press Enter. I guess this was done for usability, but it
- is a security issue because an attacker can easily determine the PIN
- length, which makes it easier to for an attacker to guess the PIN. Eg,
- if I have a 2 digit PIN set, then an attacker need only type '111' and
- know that the PIN is only two characters. Now, a PIN isn't strong to
- begin with and an automated attack could rather quickly brute force
- PINs, but we shouldn't make it easier for someone manually trying to
- guess the PIN.
+ Currently when setting a PIN on the device, it must be 4 digits. This is
+ artificially limiting. Other platforms (eg Android) allow longer PINs.
  
- The passphrase lockscreen  promptcorrectly requires you to press Enter.
+ However, once longer PINs are supported, we will have to add an Enter
+ key. Right now, the lockscreen checks the PIN once 4 digits are added so
+ that you don't have to press Enter. I guess this was done for usability,
+ but would be a security issue because an attacker can easily determine
+ the PIN length, which makes it easier to for an attacker to guess the
+ PIN. Eg, if I have a 5 digit PIN set, then an attacker need only type
+ '1' and know that the PIN is only five characters. Now, a PIN isn't
+ strong to begin with and an automated attack could rather quickly brute
+ force PINs, but we shouldn't make it easier for someone manually trying
+ to guess the PIN.
+ 
+ The passphrase lockscreen prompt correctly allows variable length
+ passphrases and requires you to press Enter.
  
  I suggest moving the 'X' up t the left of '0' and an Enter symbol to the
  rigth of '0'.

** Description changed:

  Currently when setting a PIN on the device, it must be 4 digits. This is
  artificially limiting. Other platforms (eg Android) allow longer PINs.
+ It has always been my understanding that we should support Swipe,
+ Passphrase and PIN where Passphrase and PIN can be arbitrarily long.
  
  However, once longer PINs are supported, we will have to add an Enter
  key. Right now, the lockscreen checks the PIN once 4 digits are added so
  that you don't have to press Enter. I guess this was done for usability,
  but would be a security issue because an attacker can easily determine
  the PIN length, which makes it easier to for an attacker to guess the
  PIN. Eg, if I have a 5 digit PIN set, then an attacker need only type
  '1' and know that the PIN is only five characters. Now, a PIN isn't
  strong to begin with and an automated attack could rather quickly brute
  force PINs, but we shouldn't make it easier for someone manually trying
  to guess the PIN.
  
  The passphrase lockscreen prompt correctly allows variable length
  passphrases and requires you to press Enter.
  
  I suggest moving the 'X' up t the left of '0' and an Enter symbol to the
  rigth of '0'.

** Summary changed:

- please allow PINs of variable length and require 'Enter' key when entering PIN
+ allow PINs of variable length instead of just 4 digits

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

Title:
  allow PINs of variable length instead of just 4 digits

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Currently when setting a PIN on the device, it must be 4 digits. This
  is artificially limiting. Other platforms (eg Android) allow longer
  PINs. It has always been my understanding that we should support
  Swipe, Passphrase and PIN where Passphrase and PIN can be arbitrarily
  long.

  However, once longer PINs are supported, we will have to add an Enter
  key. Right now, the lockscreen checks the PIN once 4 digits are added
  so that you don't have to press Enter. I guess this was done for
  usability, but would be a security issue because an attacker can
  easily determine the PIN length, which makes it easier to for an
  attacker to guess the PIN. Eg, if I have a 5 digit PIN set, then an
  attacker need only type '1' and know that the PIN is only five
  characters. Now, a PIN isn't strong to begin with and an automated
  attack could rather quickly brute force PINs, but we shouldn't make it
  easier for someone manually trying to guess the PIN.

  The passphrase lockscreen prompt correctly allows variable length
  passphrases and requires you to press Enter.

  I suggest moving the 'X' up t the left of '0' and an Enter symbol to
  the rigth of '0'.

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

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

[Touch-packages] [Bug 1234947] Re: contacts not honoring language setting (ie, Favourites with US English)

** Changed in: messaging-app
   Status: New => In Progress

** Changed in: messaging-app
   Importance: Undecided => High

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

Title:
  contacts not honoring language setting (ie, Favourites with US
  English)

Status in Address Book App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  Fix Released
Status in Messaging App:
  In Progress
Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  LANG=en_US.UTF-8
  LANGUAGE=en_US:en
  Settings says US English.

  Contacts in the dialer and the contacts app says 'Favourites' instead
  of 'Favorites'.

  $ adb shell system-image-cli -i
  current build number: 78
  device name: mako
  channel: stable
  last update: 2013-10-03 13:05:32
  version version: 78
  version ubuntu: 20131003
  version device: 20131002.1

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

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

[Touch-packages] [Bug 1328513] Re: Preview header title truncated

** Tags added: touch-2014-9-25

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

Title:
  Preview header title truncated

Status in The Savilerow project:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  When developing a news scope. The "title" in the grid card fits the
  news headline, but in the preview (the same text) the title gets
  truncated.

  This looks very strange and makes reading news hard tbh. Shouldnt we
  have a common behaviour (see attached files)

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

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

[Touch-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

2014-08-29 Thread EsAmo

More and more people affected. While Alt + Tab can be a nightmare at
some cases...

It does not have to be different drive - bug exists for different
partition than Linux installation like one occupied by Windows.


Regards & respect.

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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in Nautilus:
  New
Status in Unity:
  Triaged
Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

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

[Touch-packages] [Bug 1350584] Re: keyboard not displayed after returning to app from shell

** Tags added: touch-2014-9-11

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

Title:
  keyboard not displayed after returning to app from shell

Status in The Unity 8 shell:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  seeing this in build 160

  - open messaging-app
  - open a message and click in send field to display keyboard
  - left edge swipe to return to shell
  - click on messaging-app in Apps scope

  Expected result:
  - messaging-app displayed with keyboard visible

  Actual result:
  - messaging-app shown with blank area where keyboard used to be (see 
screenshot)

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

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

[Touch-packages] [Bug 1363207] Re: mallit server running 100% cpu

of course you have to launch osk, like by setting passphrase or
something, don't have to type, just launch it

** Summary changed:

- mallit server running 100% cpu
+ mallit server running 100% cpu after launching osk in welcome wizard

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

Title:
  mallit server running 100% cpu after launching osk in welcome wizard

Status in “maliit-framework” package in Ubuntu:
  New

Bug description:
  Image#213 on N4
  fresh flash, haven't run anything, just after welcome wizard 
completedphone got hot & dash was black/missing.
  no crash files. Ran top and see mallit pegging 100%
  camako also seeing uper hot phone when he was testing a mir silo (which is 
why we tested virgin image), he also saw 100% cpu by mallit-server

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

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

[Touch-packages] [Bug 1363207] Re: mallit server running 100% cpu

after reboot, this didn't seem to occur.
So i re-enabled welcome wizard, and was able to see this happen again.

To re-enable welcome wiz
phablet-shell$ sudo rm 
/home/phablet/.config/ubuntu-system-settings/wizard-has-run
reboot

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

Title:
  mallit server running 100% cpu after launching osk in welcome wizard

Status in “maliit-framework” package in Ubuntu:
  New

Bug description:
  Image#213 on N4
  fresh flash, haven't run anything, just after welcome wizard 
completedphone got hot & dash was black/missing.
  no crash files. Ran top and see mallit pegging 100%
  camako also seeing uper hot phone when he was testing a mir silo (which is 
why we tested virgin image), he also saw 100% cpu by mallit-server

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

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

[Touch-packages] [Bug 1319542] Re: Unity urgent animation needs an adjustable time length.

2014-08-29 Thread Eduards Bezverhijs

I agree with OP, I have a lot of applications opened at the same time, launcher 
size is set to 36 because they don't fit in size 48. At least at size 36 
highlight is not noticeable enough and I miss notifications most of the time.
Also it's quite common that I don't see wiggle because I'm looking away from 
computer like watching birds fly or talking to colleagues or just concentrating 
on something else where my eyes are not near the launcher.
I would say that every 10 - 15 seconds would be good to me, but please don't 
make it hard coded, leave it up to the user to decide, sane defaults can stay 
like they are now - once.
Thanks.

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

Title:
  Unity urgent animation needs an adjustable time length.

Status in Ayatana Design:
  New
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 14.04, fully up to date, Unity Version:
  7.2.0+14.04.20140416-0ubuntu1

  The Unity launcher in my setup is not hidden. It is always visible.

  The current behavior of the urgent animation goes like this:

  1) An application needs attention (such as an instant message through Empathy 
or Skype)
  2) Icon wiggles for about one second
  3) Once the wiggle is over, the icon remains highlighted

  The problem is with step 2. The icon never reinitializes any sort of
  motion to catch the user's eye. People are busy. People are frequently
  multitasking. In a lot of cases, people are using multiple monitors or
  very widescreen monitors and their field of vision is in an entirely
  different place altogether. There really should be some sort of
  repeated motion that takes place to grab the users attention, thereby
  signifying that an application needs attention.

  A few possible solutions would be:

  A) Let the icon wiggle indefinitely until the user clicks on it. This
  is a bit obnoxious, because you have to consider the situations where
  a user might notice it, but might be too deep in a specific project to
  address it right away. This would stand as a potential distraction
  and/or annoyance, though it *would* eliminate the chances of the
  notification going missed.

  B) To allow the user to adjust the time frame in which the wiggle
  animation takes place. That way instead of one second, perhaps the
  user might want it to last 10 seconds, or 30 seconds, etc. There are
  times where I am engaging in an active conversation but switching to
  another application frequently. At times, I miss a message altogether
  despite the fact I'm looking at the screen. This is entirely due to
  the short time frame in which the urgent animation is moving. The
  length of time in which it moves is, more times than not, simply not
  long enough to be noticed. If the one second span could be adjusted,
  and say I have it set to 5 seconds, or 10 seconds, surely I would
  notice it.

  C) The most optimum solution in my opinion is to make the urgent
  animation continually come up over a specified span of time. Example,
  I receive a notification from Empathy, but I miss it. It wiggles and
  shortly thereafter stops wiggling, thereby just sitting idle but with
  the icon highlighted. A short time later, perhaps 30 seconds later, it
  wiggles again, and continues onward in 30 second intervals
  indefinitely until the user gives attention to the application
  requesting it.

  Option C would circumvent a potential "annoyance" factor of option A,
  and it would work around the fact that option B) would require another
  thing to change in the settings menu. All in all, there *really*
  should be a way for a user to more easily see that an application
  needs attention. A simple one second wiggle is not enough. A
  background highlight is not enough as it does not move to be noticed.
  You only notice a background highlight if you specifically look at the
  icon, whereas a motion-based notification (wiggle, etc) actually
  'grabs' your attention to be noticed.

  Thank you for your time, consideration, and hard work. If I can be of
  any further assistance please let me know. Thank you again!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed May 14 15:28:24 2014
  InstallationDate: Installed on 2014-04-04 (40 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1319542/+subscriptions

[Touch-packages] [Bug 1234947] Re: contacts not honoring language setting (ie, Favourites with US English)

Dialer app and Address book app was already released with the correct
string.

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

** Changed in: messaging-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: dialer-app
   Status: New => Fix Released

** Branch linked: lp:~renatofilho/messaging-app/show-all-contacts-when-
search-starts

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

Title:
  contacts not honoring language setting (ie, Favourites with US
  English)

Status in Address Book App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  Fix Released
Status in Messaging App:
  New
Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  LANG=en_US.UTF-8
  LANGUAGE=en_US:en
  Settings says US English.

  Contacts in the dialer and the contacts app says 'Favourites' instead
  of 'Favorites'.

  $ adb shell system-image-cli -i
  current build number: 78
  device name: mako
  channel: stable
  last update: 2013-10-03 13:05:32
  version version: 78
  version ubuntu: 20131003
  version device: 20131002.1

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

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

[Touch-packages] [Bug 1234947] Re: contacts not honoring language setting (ie, Favourites with US English)

I messaging app the string was not marked to translation in the previous
release

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

Title:
  contacts not honoring language setting (ie, Favourites with US
  English)

Status in Address Book App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  Fix Released
Status in Messaging App:
  New
Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  LANG=en_US.UTF-8
  LANGUAGE=en_US:en
  Settings says US English.

  Contacts in the dialer and the contacts app says 'Favourites' instead
  of 'Favorites'.

  $ adb shell system-image-cli -i
  current build number: 78
  device name: mako
  channel: stable
  last update: 2013-10-03 13:05:32
  version version: 78
  version ubuntu: 20131003
  version device: 20131002.1

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

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

[Touch-packages] [Bug 1358625] Re: Mir FTBFS in release mode: scroll.cpp: variable ‘rc’ set but not used

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  Mir FTBFS in release mode: scroll.cpp: variable ‘rc’ set but not used

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Mir fails to build in release mode:

  cmake .. -DCMAKE_BUILD_TYPE=RELEASE
  make

  examples/scroll.cpp: In function ‘void 
create_and_run_scroll_surface(MirConnection*)’:
  examples/scroll.cpp:56:26: error: variable ‘rc’ set but not used 
[-Werror=unused-but-set-variable]
   int major, minor, n, rc;
    ^

  So I'm wondering; is it a bad thing that we apparently never use
  release mode?

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

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

[Touch-packages] [Bug 1354446] Re: [regression] Intermittent failure of TestTouchspotVisualizations.* tests

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  [regression] Intermittent failure of TestTouchspotVisualizations.*
  tests

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  As seen in https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-
  branch-utopic-amd64-autolanding/343/console

  Steps to reproduce: valgrind bin/mir_acceptance_tests
  --gtest_filter=TestTouchspotVisualizations.* --gtest_repeat=1000

  Expected result: Tests pass

  Actual results: One of the tests fails with:

  unknown file: Failure
  C++ exception with description "Invalid argument" thrown in TearDown().
  terminate called without an active exception

  I have seen both TestTouchspotVisualizations tests fail with this
  error.

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

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

[Touch-packages] [Bug 1353465] Re: Intermittent acceptance test failures in NestedServer.*

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  Intermittent acceptance test failures in NestedServer.*

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce: bin/mir_acceptance_tests
  --gtest_filter=NestedServer.* --gtest_repeat=1000
  --gtest_break_on_failure

  Expected result: Success

  Actual result:

  At some point the tests fail with

  [==] Running 4 tests from 1 test case.
  [--] Global test environment set-up.
  [--] 4 tests from NestedServer
  [ RUN  ] NestedServer.nested_platform_connects_and_disconnects
  [   OK ] NestedServer.nested_platform_connects_and_disconnects (19 ms)
  [ RUN  ] NestedServer.sees_expected_outputs
  [   OK ] NestedServer.sees_expected_outputs (21 ms)
  [ RUN  ] NestedServer.on_exit_display_objects_should_be_destroyed
  [   OK ] NestedServer.on_exit_display_objects_should_be_destroyed (20 ms)
  [ RUN  ] NestedServer.receives_lifecycle_events_from_host
  unknown file: Failure

  Unexpected mock function call - returning directly.
  Function call: lifecycle_event_occurred(2)
  Google Mock tried the following 3 expectations, but none matched:

  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:389: tried 
expectation #0: 
EXPECT_CALL(*(nested_config.the_mock_host_lifecycle_event_listener()), 
lifecycle_event_occurred(mir_lifecycle_state_resumed))...
Expected arg #0: is equal to 1
 Actual: 2
   Expected: to be called once
 Actual: called once - saturated and active
  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:391: tried 
expectation #1: 
EXPECT_CALL(*(nested_config.the_mock_host_lifecycle_event_listener()), 
lifecycle_event_occurred(mir_lifecycle_state_will_suspend))...
Expected arg #0: is equal to 0
 Actual: 2
   Expected: to be called once
 Actual: never called - unsatisfied and active
  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:393: tried 
expectation #2: 
EXPECT_CALL(*(nested_config.the_mock_host_lifecycle_event_listener()), 
lifecycle_event_occurred(mir_lifecycle_connection_lost))...
   Expected: all pre-requisites are satisfied
 Actual: the following immediate pre-requisites are not satisfied:
  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:391: 
pre-requisite #0
 (end of pre-requisites)
   Expected: to be called at most once
 Actual: never called - satisfied and active

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

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

[Touch-packages] [Bug 1358210] Re: [regression] mir_demo_server_shell segfaults immediately in generate_frame_corner_texture() [amd64], or displays corrupt titlebars [armhf]

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  [regression] mir_demo_server_shell segfaults immediately in
  generate_frame_corner_texture() [amd64], or displays corrupt titlebars
  [armhf]

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Invalid
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  [regression] mir_demo_server_shell segfaults immediately in
  generate_frame_corner_texture() from DemoRenderer::DemoRenderer()

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f6f184fa404 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  (gdb) bt
  #0  0x7f6f184fa404 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #1  0x7f6f184ff898 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #2  0x7f6f182f9f76 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #3  0x7f6f1840c0e2 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #4  0x7f6f182e9e38 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #5  0x0045b2e0 in (anonymous namespace)::generate_frame_corner_texture
  (corner_radius=0, color=..., highlight=255 '\377')
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_renderer.cpp:133
  #6  0x0045b40e in mir::examples::DemoRenderer::DemoRenderer (
  this=0x7f6efc000950, program_factory=..., display_area=..., 
  dest_alpha=mir::compositor::DestinationAlpha::opaque, titlebar_height=30, 
  shadow_radius=80)
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_renderer.cpp:157
  #7  0x00459d49 in mir::examples::DemoCompositor::DemoCompositor (
  this=0x7f6efc000920, display_buffer=..., scene=
  std::shared_ptr (count 8, weak 1) 0x1c59a50, factory=..., report=
  std::shared_ptr (count 4, weak 1) 0x19235d0)
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_compositor.cpp:52
  #8  0x00450fee in 
mir::examples::DisplayBufferCompositorFactory::create_compositor_for 
(this=0x1c5a400, display_buffer=...)
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_shell.cpp:69
  #9  0x7f6f1ea3e9f6 in mir::compositor::CompositingFunctor::operator() (
  this=0x1d638e0)
  at 
/home/dan/bzr/mir/dev/src/server/compositor/multi_threaded_compositor.cpp:113
  #10 0x7f6f1ea42881 in std::__invoke (
  __f=...) at /usr/include/c++/4.9/functional:202
  #11 0x7f6f1ea42856 in 
std::reference_wrapper::operator()<>() 
const (this=0x191c688)
  at /usr/include/c++/4.9/functional:435
  #12 0x7f6f1ea427a8 in 
std::_Bind_simple 
()>::_M_invoke<>(std::_Index_tuple<>) (this=0x191c688)
  at /usr/include/c++/4.9/functional:1700
  #13 0x7f6f1ea42682 in 
std::_Bind_simple 
()>::operator()() (this=0x191c688)
  at /usr/include/c++/4.9/functional:1688
  #14 0x7f6f1ea4258c in 
std::thread::_Impl
 ()> >::_M_run() (this=0x191c670)
  at /usr/include/c++/4.9/thread:115
  #15 0x7f6f1d5e7c60 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #16 0x7f6f1be19165 in start_thread (arg=0x7f6f12836700)
  at pthread_create.c:309
  #17 0x7f6f1cd454dd in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

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

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

[Touch-packages] [Bug 1358698] Re: [regression] Test failure holding up all merge proposals: "File already exists in database: mir_protobuf_wire.proto"

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  [regression] Test failure holding up all merge proposals: "File
  already exists in database: mir_protobuf_wire.proto"

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Invalid
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  We;ve seen a failure on two CI branches and briefly locally (by Kevin
  DuBois).

  > [libprotobuf ERROR google/protobuf/descriptor_database.cc:57] File already 
exists in database: mir_protobuf_wire.proto
  > [libprotobuf FATAL google/protobuf/descriptor.cc:954] CHECK failed: 
generated_database_->Add(encoded_file_descriptor, size):
  > terminate called after throwing an instance of 
'google::protobuf::FatalException'
  > what(): CHECK failed: generated_database_->Add(encoded_file_descriptor, 
size):
  > Aborted (core dumped) 

  
https://code.launchpad.net/~raof/mir/more-tiny-improvements/+merge/231304/comments/562598
  
https://code.launchpad.net/~alan-griffiths/mir/integration-and-unit-tests-link-against-internals/+merge/230810/comments/562173

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

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

[Touch-packages] [Bug 1359406] Re: mir should not composite/display buffers when an android driver calls ANativeWindow::cancelBuffer

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  mir should not composite/display buffers when an android driver calls
  ANativeWindow::cancelBuffer

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  mir should not composite/display buffers submitted via the android
  platform ANativeWindow::cancelBuffer.

  Some android drivers (like the mali driver in nexus10) will  call
  ANativeWindow::cancelBuffer in the client side at the beginning so a
  blank frame gets posted.

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

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

[Touch-packages] [Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  [regression] Clients are crashing (SIGSEGV) on mir_connect() failure

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  On image 195 on mako,

  phablet@ubuntu-phablet:~$ mirping
  Segmentation fault (core dumped)
  phablet@ubuntu-phablet:~$ mirscreencast -n1
  Segmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1353867] Re: [regression] Mir clients get caught in an infinite exception loop when the server goes away ("Caught exception at Mir/EGL driver boundary")

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  [regression] Mir clients get caught in an infinite exception loop when
  the server goes away ("Caught exception at Mir/EGL driver boundary")

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Nexus4: Mir client gets caught in an infinite exception loop if the
  server crashes ("Caught exception at Mir/EGL driver boundary")

  Test case:
     1. mir_demo_server_shell
     2. mir_demo_client_egltriangle
     3. Press the power button to sleep
     4. Press the power button again to wake up

  Expected: Rendering continues on screen after wakeup
  Observed:

  Caught exception at Mir/EGL driver boundary: 
/home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in 
function virtual void mir::client::rpc::StreamSocketTransport::send_data(const 
std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorE
  std::exception::what: Failed to send message to server: Bad file descriptor
  9, "Bad file descriptor"
  Caught exception at Mir/EGL driver boundary: 
/home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in 
function virtual void mir::client::rpc::StreamSocketTransport::send_data(const 
std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorE
  std::exception::what: Failed to send message to server: Bad file descriptor
  9, "Bad file descriptor"
  Caught exception at Mir/EGL driver boundary: 
/home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in 
function virtual void mir::client::rpc::StreamSocketTransport::send_data(const 
std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorE
  std::exception::what: Failed to send message to server: Bad file descriptor
  9, "Bad file descriptor"
  .

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

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

[Touch-packages] [Bug 1359264] Re: Surfaces receive input even while the screen is off

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  Surfaces receive input even while the screen is off

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  mir should not deliver input events to occluded surfaces.

  On a phone platform like n4, this can result in the UI actions even
  when the screen is off.

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

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

[Touch-packages] [Bug 1363214] [NEW] require 'Enter' key when entering PIN

2014-08-29 Thread Jamie Strandboge

*** This bug is a security vulnerability ***

Public security bug reported:

If I set a PIN on the device, I am prompted to enter it on screen unlock
(great!). Right now, the lockscreen checks the PIN as you type so that
you don't have press Enter. I guess this was done for usability, but it
is a security issue because an attacker can easily determine the PIN
length, which makes it easier to for an attacker to guess the PIN. Eg,
if I have a 2 digit PIN set, then an attacker need only type '111' and
know that the PIN is only two characters. Now, a PIN isn't strong to
begin with and an automated attack could rather quickly brute force
PINs, but we shouldn't make it easier for someone manually trying to
guess the PIN.

The passphrase lockscreen  promptcorrectly requires you to press Enter.

I suggest moving the 'X' up t the left of '0' and an Enter symbol to the
rigth of '0'.

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


** Tags: rtm14

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

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

Title:
  require 'Enter' key when entering PIN

Status in “unity8” package in Ubuntu:
  New

Bug description:
  If I set a PIN on the device, I am prompted to enter it on screen
  unlock (great!). Right now, the lockscreen checks the PIN as you type
  so that you don't have press Enter. I guess this was done for
  usability, but it is a security issue because an attacker can easily
  determine the PIN length, which makes it easier to for an attacker to
  guess the PIN. Eg, if I have a 2 digit PIN set, then an attacker need
  only type '111' and know that the PIN is only two characters. Now, a
  PIN isn't strong to begin with and an automated attack could rather
  quickly brute force PINs, but we shouldn't make it easier for someone
  manually trying to guess the PIN.

  The passphrase lockscreen  promptcorrectly requires you to press
  Enter.

  I suggest moving the 'X' up t the left of '0' and an Enter symbol to
  the rigth of '0'.

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

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

[Touch-packages] [Bug 1331958] Re: mir_demo_client_basic confusingly asserts instead of reporting that there is no server to connect to: `mir_connection_is_valid(mcd.connection)' failed.

** Changed in: mir
Milestone: 0.7.0 => 0.8.0

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

Title:
  mir_demo_client_basic confusingly asserts instead of reporting that
  there is no server to connect to:
  `mir_connection_is_valid(mcd.connection)' failed.

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

Bug description:
  
  Terminal:
$ mir_demo_client__basic

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mir-demos 0.3.0+14.10.20140618.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic i686
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  AssertionMessage: mir_demo_client_basic: 
/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c:109: demo_client: 
Assertion `mir_connection_is_valid(mcd.connection)' failed.
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Thu Jun 19 09:49:55 2014
  ExecutablePath: /usr/bin/mir_demo_client_basic
  InstallationDate: Installed on 2014-06-13 (5 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140613)
  ProcCmdline: mir_demo_client_basic
  Signal: 6
  SourcePackage: mir
  StacktraceTop:
   __assert_fail_base (fmt=0xb7601b94 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x80492dc 
"mir_connection_is_valid(mcd.connection)", file=file@entry=0x80492a0 
"/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c", 
line=line@entry=109, function=function@entry=0x804aa90 "demo_client") at 
assert.c:92
   __GI___assert_fail (assertion=0x80492dc 
"mir_connection_is_valid(mcd.connection)", file=0x80492a0 
"/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c", line=109, 
function=0x804aa90 "demo_client") at assert.c:101
   demo_client ()
   main ()
  Title: mir_demo_client_basic assert failure: mir_demo_client_basic: 
/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c:109: demo_client: 
Assertion `mir_connection_is_valid(mcd.connection)' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1363207] [NEW] mallit server running 100% cpu

Public bug reported:

Image#213 on N4
fresh flash, haven't run anything, just after welcome wizard completedphone 
got hot & dash was black/missing.
no crash files. Ran top and see mallit pegging 100%
camako also seeing uper hot phone when he was testing a mir silo (which is why 
we tested virgin image), he also saw 100% cpu by mallit-server

** Affects: maliit-framework (Ubuntu)
 Importance: Critical
 Status: New

** Changed in: maliit-framework (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  mallit server running 100% cpu

Status in “maliit-framework” package in Ubuntu:
  New

Bug description:
  Image#213 on N4
  fresh flash, haven't run anything, just after welcome wizard 
completedphone got hot & dash was black/missing.
  no crash files. Ran top and see mallit pegging 100%
  camako also seeing uper hot phone when he was testing a mir silo (which is 
why we tested virgin image), he also saw 100% cpu by mallit-server

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

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

[Touch-packages] [Bug 1359406] Re: mir should not composite/display buffers when an android driver calls ANativeWindow::cancelBuffer

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  mir should not composite/display buffers when an android driver calls
  ANativeWindow::cancelBuffer

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  mir should not composite/display buffers submitted via the android
  platform ANativeWindow::cancelBuffer.

  Some android drivers (like the mali driver in nexus10) will  call
  ANativeWindow::cancelBuffer in the client side at the beginning so a
  blank frame gets posted.

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

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

[Touch-packages] [Bug 1361610] Re: libPCRE3 8.31 regex matching is not working

2014-08-29 Thread Filip Sohajek

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

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

Title:
  libPCRE3 8.31 regex matching is not working

Status in “pcre3” package in Ubuntu:
  Confirmed
Status in “poco” package in Ubuntu:
  Invalid

Bug description:
  It looks like that libPCRE3 8.31 included in Ubuntu 13.10 does not
  handle regex matching alright. This also affects the libPocoFoundation
  RegularExpression classes.

  I attached a proof-of-concept which tests a good and bad heystack
  string to a regex pattern with Poco, Boost and PCRE. I tested it on
  two different machines with the following output:

  Ubuntu 13.10 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 
i686 i686 i686 GNU/Linux
  Poco 0x01030600 on Linux 3.11.0-13-generic @ i686
  Poco  match 1234567890 to pattern ^[0-9]{10} matches? no --> NOT CORRECT
  Poco  match 123456789 to pattern ^[0-9]{10} matches? no
  Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
  Boost match 123456789 to pattern ^[0-9]{10} matches? no
  PCRE 8.31 2012-07-06
  PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
  PRCE  match 123456789 to pattern ^[0-9]{10} matches? yes --> NOT CORRECT

  Ubuntu 12.04.3 LTS  3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 
15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
  Poco 0x01030600 on Linux 3.8.0-29-generic @ i686
  Poco  match 1234567890 to pattern ^[0-9]{10} matches? yes --> OK
  Poco  match 123456789 to pattern ^[0-9]{10} matches? no
  Boost match 1234567890 to pattern ^[0-9]{10} matches? yes
  Boost match 123456789 to pattern ^[0-9]{10} matches? no
  PCRE 8.12 2011-01-15
  PCRE  match 1234567890 to pattern ^[0-9]{10} matches? yes
  PRCE  match 123456789 to pattern ^[0-9]{10} matches? no --> OK

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

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

[Touch-packages] [Bug 1353465] Re: Intermittent acceptance test failures in NestedServer.*

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  Intermittent acceptance test failures in NestedServer.*

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce: bin/mir_acceptance_tests
  --gtest_filter=NestedServer.* --gtest_repeat=1000
  --gtest_break_on_failure

  Expected result: Success

  Actual result:

  At some point the tests fail with

  [==] Running 4 tests from 1 test case.
  [--] Global test environment set-up.
  [--] 4 tests from NestedServer
  [ RUN  ] NestedServer.nested_platform_connects_and_disconnects
  [   OK ] NestedServer.nested_platform_connects_and_disconnects (19 ms)
  [ RUN  ] NestedServer.sees_expected_outputs
  [   OK ] NestedServer.sees_expected_outputs (21 ms)
  [ RUN  ] NestedServer.on_exit_display_objects_should_be_destroyed
  [   OK ] NestedServer.on_exit_display_objects_should_be_destroyed (20 ms)
  [ RUN  ] NestedServer.receives_lifecycle_events_from_host
  unknown file: Failure

  Unexpected mock function call - returning directly.
  Function call: lifecycle_event_occurred(2)
  Google Mock tried the following 3 expectations, but none matched:

  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:389: tried 
expectation #0: 
EXPECT_CALL(*(nested_config.the_mock_host_lifecycle_event_listener()), 
lifecycle_event_occurred(mir_lifecycle_state_resumed))...
Expected arg #0: is equal to 1
 Actual: 2
   Expected: to be called once
 Actual: called once - saturated and active
  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:391: tried 
expectation #1: 
EXPECT_CALL(*(nested_config.the_mock_host_lifecycle_event_listener()), 
lifecycle_event_occurred(mir_lifecycle_state_will_suspend))...
Expected arg #0: is equal to 0
 Actual: 2
   Expected: to be called once
 Actual: never called - unsatisfied and active
  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:393: tried 
expectation #2: 
EXPECT_CALL(*(nested_config.the_mock_host_lifecycle_event_listener()), 
lifecycle_event_occurred(mir_lifecycle_connection_lost))...
   Expected: all pre-requisites are satisfied
 Actual: the following immediate pre-requisites are not satisfied:
  /storage/work/mir/tests/acceptance-tests/test_nested_mir.cpp:391: 
pre-requisite #0
 (end of pre-requisites)
   Expected: to be called at most once
 Actual: never called - satisfied and active

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

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

[Touch-packages] [Bug 1353867] Re: [regression] Mir clients get caught in an infinite exception loop when the server goes away ("Caught exception at Mir/EGL driver boundary")

** Changed in: mir/0.6
   Status: Triaged => Won't Fix

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  [regression] Mir clients get caught in an infinite exception loop when
  the server goes away ("Caught exception at Mir/EGL driver boundary")

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Nexus4: Mir client gets caught in an infinite exception loop if the
  server crashes ("Caught exception at Mir/EGL driver boundary")

  Test case:
     1. mir_demo_server_shell
     2. mir_demo_client_egltriangle
     3. Press the power button to sleep
     4. Press the power button again to wake up

  Expected: Rendering continues on screen after wakeup
  Observed:

  Caught exception at Mir/EGL driver boundary: 
/home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in 
function virtual void mir::client::rpc::StreamSocketTransport::send_data(const 
std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorE
  std::exception::what: Failed to send message to server: Bad file descriptor
  9, "Bad file descriptor"
  Caught exception at Mir/EGL driver boundary: 
/home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in 
function virtual void mir::client::rpc::StreamSocketTransport::send_data(const 
std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorE
  std::exception::what: Failed to send message to server: Bad file descriptor
  9, "Bad file descriptor"
  Caught exception at Mir/EGL driver boundary: 
/home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in 
function virtual void mir::client::rpc::StreamSocketTransport::send_data(const 
std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorE
  std::exception::what: Failed to send message to server: Bad file descriptor
  9, "Bad file descriptor"
  .

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

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

[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly

** Tags added: touch-2014-9-11

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

Title:
  unity8 freezes randomly

Status in “unity8” package in Ubuntu:
  New

Bug description:
  krillin #205

  [Sorry for the poor description]

  On krillin UI freeze randomly. For example on the screenshot it
  occurred while dragging the greeter to unlock the phone. I was playing
  music, woke up the phone with the power button to turn the display on
  and did a right edge swipe to remove the greeter.

  This has been reported by several people in the past days, but I
  didn't find a pattern to reproduce this bug reliably.

  There is no crash in /var/crash and no apport activity.
  If I press the power button to turn the screen off/on again, the greeter is 
completely displayed (ie. doesn't cover half of the screen like the screenshot) 
but the UI is not responsive to gestures or input events. A long press on the 
power button shows the shutdown dialog but none of the button can be pressed.

  top doesn't show any specific process going crazy

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140822-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: armhf
  Date: Sat Aug 23 14:18:00 2014
  InstallationDate: Installed on 2014-08-23 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140823-020205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1354446] Re: [regression] Intermittent failure of TestTouchspotVisualizations.* tests

** Changed in: mir/0.6
   Status: Triaged => Won't Fix

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  [regression] Intermittent failure of TestTouchspotVisualizations.*
  tests

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  As seen in https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-
  branch-utopic-amd64-autolanding/343/console

  Steps to reproduce: valgrind bin/mir_acceptance_tests
  --gtest_filter=TestTouchspotVisualizations.* --gtest_repeat=1000

  Expected result: Tests pass

  Actual results: One of the tests fails with:

  unknown file: Failure
  C++ exception with description "Invalid argument" thrown in TearDown().
  terminate called without an active exception

  I have seen both TestTouchspotVisualizations tests fail with this
  error.

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

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

[Touch-packages] [Bug 1358210] Re: [regression] mir_demo_server_shell segfaults immediately in generate_frame_corner_texture() [amd64], or displays corrupt titlebars [armhf]

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  [regression] mir_demo_server_shell segfaults immediately in
  generate_frame_corner_texture() [amd64], or displays corrupt titlebars
  [armhf]

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Invalid
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  [regression] mir_demo_server_shell segfaults immediately in
  generate_frame_corner_texture() from DemoRenderer::DemoRenderer()

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f6f184fa404 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  (gdb) bt
  #0  0x7f6f184fa404 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #1  0x7f6f184ff898 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #2  0x7f6f182f9f76 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #3  0x7f6f1840c0e2 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #4  0x7f6f182e9e38 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  #5  0x0045b2e0 in (anonymous namespace)::generate_frame_corner_texture
  (corner_radius=0, color=..., highlight=255 '\377')
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_renderer.cpp:133
  #6  0x0045b40e in mir::examples::DemoRenderer::DemoRenderer (
  this=0x7f6efc000950, program_factory=..., display_area=..., 
  dest_alpha=mir::compositor::DestinationAlpha::opaque, titlebar_height=30, 
  shadow_radius=80)
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_renderer.cpp:157
  #7  0x00459d49 in mir::examples::DemoCompositor::DemoCompositor (
  this=0x7f6efc000920, display_buffer=..., scene=
  std::shared_ptr (count 8, weak 1) 0x1c59a50, factory=..., report=
  std::shared_ptr (count 4, weak 1) 0x19235d0)
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_compositor.cpp:52
  #8  0x00450fee in 
mir::examples::DisplayBufferCompositorFactory::create_compositor_for 
(this=0x1c5a400, display_buffer=...)
  at /home/dan/bzr/mir/dev/examples/demo-shell/demo_shell.cpp:69
  #9  0x7f6f1ea3e9f6 in mir::compositor::CompositingFunctor::operator() (
  this=0x1d638e0)
  at 
/home/dan/bzr/mir/dev/src/server/compositor/multi_threaded_compositor.cpp:113
  #10 0x7f6f1ea42881 in std::__invoke (
  __f=...) at /usr/include/c++/4.9/functional:202
  #11 0x7f6f1ea42856 in 
std::reference_wrapper::operator()<>() 
const (this=0x191c688)
  at /usr/include/c++/4.9/functional:435
  #12 0x7f6f1ea427a8 in 
std::_Bind_simple 
()>::_M_invoke<>(std::_Index_tuple<>) (this=0x191c688)
  at /usr/include/c++/4.9/functional:1700
  #13 0x7f6f1ea42682 in 
std::_Bind_simple 
()>::operator()() (this=0x191c688)
  at /usr/include/c++/4.9/functional:1688
  #14 0x7f6f1ea4258c in 
std::thread::_Impl
 ()> >::_M_run() (this=0x191c670)
  at /usr/include/c++/4.9/thread:115
  #15 0x7f6f1d5e7c60 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #16 0x7f6f1be19165 in start_thread (arg=0x7f6f12836700)
  at pthread_create.c:309
  #17 0x7f6f1cd454dd in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

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

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

[Touch-packages] [Bug 1358625] Re: Mir FTBFS in release mode: scroll.cpp: variable ‘rc’ set but not used

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  Mir FTBFS in release mode: scroll.cpp: variable ‘rc’ set but not used

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Mir fails to build in release mode:

  cmake .. -DCMAKE_BUILD_TYPE=RELEASE
  make

  examples/scroll.cpp: In function ‘void 
create_and_run_scroll_surface(MirConnection*)’:
  examples/scroll.cpp:56:26: error: variable ‘rc’ set but not used 
[-Werror=unused-but-set-variable]
   int major, minor, n, rc;
    ^

  So I'm wondering; is it a bad thing that we apparently never use
  release mode?

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

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

[Touch-packages] [Bug 1359264] Re: Surfaces receive input even while the screen is off

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

** Changed in: mir/0.6
   Status: Triaged => Won't Fix

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

Title:
  Surfaces receive input even while the screen is off

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  mir should not deliver input events to occluded surfaces.

  On a phone platform like n4, this can result in the UI actions even
  when the screen is off.

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

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

[Touch-packages] [Bug 1358191] Re: [regression] Clients are crashing (SIGSEGV) on mir_connect() failure

** Changed in: mir/0.6
   Status: Triaged => Won't Fix

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

** Changed in: mir/0.7
   Status: Triaged => Fix Committed

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

Title:
  [regression] Clients are crashing (SIGSEGV) on mir_connect() failure

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Won't Fix
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  On image 195 on mako,

  phablet@ubuntu-phablet:~$ mirping
  Segmentation fault (core dumped)
  phablet@ubuntu-phablet:~$ mirscreencast -n1
  Segmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1358698] Re: [regression] Test failure holding up all merge proposals: "File already exists in database: mir_protobuf_wire.proto"

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  [regression] Test failure holding up all merge proposals: "File
  already exists in database: mir_protobuf_wire.proto"

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Invalid
Status in Mir 0.7 series:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  We;ve seen a failure on two CI branches and briefly locally (by Kevin
  DuBois).

  > [libprotobuf ERROR google/protobuf/descriptor_database.cc:57] File already 
exists in database: mir_protobuf_wire.proto
  > [libprotobuf FATAL google/protobuf/descriptor.cc:954] CHECK failed: 
generated_database_->Add(encoded_file_descriptor, size):
  > terminate called after throwing an instance of 
'google::protobuf::FatalException'
  > what(): CHECK failed: generated_database_->Add(encoded_file_descriptor, 
size):
  > Aborted (core dumped) 

  
https://code.launchpad.net/~raof/mir/more-tiny-improvements/+merge/231304/comments/562598
  
https://code.launchpad.net/~alan-griffiths/mir/integration-and-unit-tests-link-against-internals/+merge/230810/comments/562173

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

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

[Touch-packages] [Bug 1234947] Re: contacts not honoring language setting (ie, Favourites with US English)

** Also affects: address-book-app
   Importance: Undecided
   Status: New

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

** Changed in: address-book-app (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: address-book-app
   Status: New => Fix Released

** Changed in: dialer-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  contacts not honoring language setting (ie, Favourites with US
  English)

Status in Address Book App:
  Fix Released
Status in Dialer app for Ubuntu Touch:
  New
Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  LANG=en_US.UTF-8
  LANGUAGE=en_US:en
  Settings says US English.

  Contacts in the dialer and the contacts app says 'Favourites' instead
  of 'Favorites'.

  $ adb shell system-image-cli -i
  current build number: 78
  device name: mako
  channel: stable
  last update: 2013-10-03 13:05:32
  version version: 78
  version ubuntu: 20131003
  version device: 20131002.1

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

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

[Touch-packages] [Bug 1331958] Re: mir_demo_client_basic confusingly asserts instead of reporting that there is no server to connect to: `mir_connection_is_valid(mcd.connection)' failed.

** Changed in: mir
Milestone: 0.8.0 => 0.7.0

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

Title:
  mir_demo_client_basic confusingly asserts instead of reporting that
  there is no server to connect to:
  `mir_connection_is_valid(mcd.connection)' failed.

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

Bug description:
  
  Terminal:
$ mir_demo_client__basic

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mir-demos 0.3.0+14.10.20140618.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic i686
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  AssertionMessage: mir_demo_client_basic: 
/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c:109: demo_client: 
Assertion `mir_connection_is_valid(mcd.connection)' failed.
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Thu Jun 19 09:49:55 2014
  ExecutablePath: /usr/bin/mir_demo_client_basic
  InstallationDate: Installed on 2014-06-13 (5 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140613)
  ProcCmdline: mir_demo_client_basic
  Signal: 6
  SourcePackage: mir
  StacktraceTop:
   __assert_fail_base (fmt=0xb7601b94 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x80492dc 
"mir_connection_is_valid(mcd.connection)", file=file@entry=0x80492a0 
"/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c", 
line=line@entry=109, function=function@entry=0x804aa90 "demo_client") at 
assert.c:92
   __GI___assert_fail (assertion=0x80492dc 
"mir_connection_is_valid(mcd.connection)", file=0x80492a0 
"/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c", line=109, 
function=0x804aa90 "demo_client") at assert.c:101
   demo_client ()
   main ()
  Title: mir_demo_client_basic assert failure: mir_demo_client_basic: 
/build/buildd/mir-0.3.0+14.10.20140618.1/examples/basic.c:109: demo_client: 
Assertion `mir_connection_is_valid(mcd.connection)' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1331078] Re: address-book-app consumes 40% sometimes when backgrounded

** Also affects: address-book-app
   Importance: Undecided
   Status: New

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

** Changed in: dialer-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: address-book-app (Ubuntu)
   Status: New => Fix Released

** Changed in: address-book-app
   Status: New => Fix Released

** No longer affects: dialer-app

** Changed in: address-book-app
   Status: Fix Released => 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/1331078

Title:
  address-book-app consumes 40% sometimes when backgrounded

Status in Address Book App:
  In Progress
Status in “address-book-app” package in Ubuntu:
  Fix Released

Bug description:
  Reproduced this a couple of times on mako #85.
  Reboot, open a few apps including phone, messaging and addressbook.
  lock phone.

  adb shell into phone, run top.
  Note that address-book-app is eating ~40% cpu with screen off.
  Phone got a bit hot after a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: address-book-app 0.2+14.10.20140616-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: armhf
  Date: Tue Jun 17 17:36:53 2014
  InstallationDate: Installed on 2014-06-17 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140617)
  SourcePackage: address-book-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1295623] Re: Sometimes input breaks and only edges are responsive

** Tags added: touch-2014-9-11

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

Title:
  Sometimes input breaks and only edges are responsive

Status in The Unity 8 shell:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  I had the music app (paused) open over night on my mako, waking up the
  device I found the application page showing me the one open app. The
  shell page itself is completely unresponsive, all side edge swipes
  seem to work fine though. I can switch to the music app when swiping
  from the right, bring up the launcher from the left and use the
  indicators from the top.

  When I am in the music app I can bring up the HUD from the bottom
  (trying to close the app, since the closing via the unresponsive shell
  does not work) but the HUD is completely unresponsive. Trying to close
  the HUD again via swiping down I see the indicators expand behind it
  and I am able to get input into the expanded indicators behind the
  HUD, but not the HUD itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140319.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Fri Mar 21 11:57:53 2014
  InstallationDate: Installed on 2014-03-20 (1 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1353461] Re: File descriptor leak in frontend - PromptSessionClientAPI acceptance test hang consistently after 67 iterations