[Touch-packages] [Bug 1397751] Re: empty desktop

2014-12-01 Thread Christopher M. Penalver
** Tags added: bios-outdated-0603

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

Title:
  empty desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  user is new to ubuntu (windows user)

  using Geforce 220 (driver problem)
  observation: ubuntu is usable but unstable. 

  some things will disappear, except for wallper and mouse pointer, hdd
  light becomes stuck.

  only way to go is push reset button

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .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_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec  1 07:29:12 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0715]
  InstallationDate: Installed on 2014-11-25 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=2c0148c9-0e22-4bd2-87de-5f13f5c8f003 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0407
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0407:bd08/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141122.ec65f8d7-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141120.0f15b8b4-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
  xserver.bootTime: Mon Dec  1 07:14:49 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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


[Touch-packages] [Bug 1397753] Re: everything keeps closing cannot be opened unless i restart

2014-12-01 Thread Christopher M. Penalver
Mpendulo, thank you for reporting this and helping make Ubuntu better.

Does this issue when:
1) you are not connected to the internet at all?
2) If you are only connected to the internet via WiFi only?

This is asked as per your 
https://launchpadlibrarian.net/191564648/CurrentDmesg.txt :
[  245.020031] atl1c :09:00.0: vpd r/w failed.  This is likely a firmware 
bug on this device.  Contact the card vendor for a firmware update.

** Package changed: xorg (Ubuntu) = linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided = Low

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

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

Title:
  everything keeps closing cannot be opened unless i restart

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the system keeps closing programms like fire fox and downloaded videos
  even most applications

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec  1 01:39:54 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:049b]
 Subsystem: Acer Incorporated [ALI] Device [1025:049b]
  InstallationDate: Installed on 2014-11-27 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: eMachines eME528
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=e3756dd5-74d6-4441-af68-28ad3e2a9a3a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2011
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3408
  dmi.board.name: HM55-MV
  dmi.board.vendor: eMachines
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: eMachines
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3408:bd02/14/2011:svneMachines:pneME528:pvrNotApplicable:rvneMachines:rnHM55-MV:rvrNotApplicable:cvneMachines:ct10:cvrN/A:
  dmi.product.name: eME528
  dmi.product.version: Not Applicable
  dmi.sys.vendor: eMachines
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  1 01:26:07 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12369 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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


[Touch-packages] [Bug 1397751] Re: [xorg-edgers] empty desktop

2014-12-01 Thread Christopher M. Penalver
ralleon, thank you for reporting this and helping make Ubuntu better. As per 
http://www.asus.com/Motherboards/P5KPLAM/HelpDesk_Download/ an update to your 
BIOS is available (0603). If you update to this following 
https://help.ubuntu.com/community/BIOSUpdate does it change anything?  If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, then please mark this report Status New.

Thank you for your understanding.

** Summary changed:

- empty desktop
+ [xorg-edgers] empty desktop

** Changed in: xorg (Ubuntu)
   Importance: Undecided = Low

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

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

Title:
  [xorg-edgers] empty desktop

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  user is new to ubuntu (windows user)

  using Geforce 220 (driver problem)
  observation: ubuntu is usable but unstable. 

  some things will disappear, except for wallper and mouse pointer, hdd
  light becomes stuck.

  only way to go is push reset button

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .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_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec  1 07:29:12 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0715]
  InstallationDate: Installed on 2014-11-25 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=2c0148c9-0e22-4bd2-87de-5f13f5c8f003 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0407
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0407:bd08/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141122.ec65f8d7-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141120.0f15b8b4-0ubuntu0sarvatt~trusty
  

[Touch-packages] [Bug 1377939] Re: [location] + [Scope] using location cause a dialog An unconfined application wants to access your current location

2014-12-01 Thread Thomas Voß
The fix for this bug has been released some time ago. Wonder why it was
bumped to high for the UX?

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

Title:
  [location] + [Scope] using location cause a dialog An unconfined
  application wants to access your current location

Status in Ubuntu UX bugs:
  Triaged
Status in Unity Online Music Scope:
  Invalid
Status in location-service package in Ubuntu:
  Invalid
Status in trust-store package in Ubuntu:
  Fix Released
Status in trust-store package in Ubuntu RTM:
  Fix Released

Bug description:
  Swiping to the flickr scope yields a confusing dialog.

  Build: 20141006
  Clean install (--wipe)

  What you expected to happen
  If flickr/a scope wants to access my location, I expected to be asked that

  What happened instead
  I was asked if an unconfined app could use my location.
  unconfined
  An unconfined applications wants to access your current location
  [deny] [allow]

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

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


[Touch-packages] [Bug 1397734] Re: euuuuh

2014-12-01 Thread Christopher M. Penalver
franki1999, thank you for taking the time to report this and helping to
make Ubuntu better. Unfortunately, we cannot work on this bug because
your description didn't include enough information. You may find it
helpful to read How to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would
then provide a more complete description of the problem.

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

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem,
2. The behavior you expected, and
3. The behavior you actually encountered (in as much detail as possible).

Thank you for your understanding.

** Tags added: latest-bios-2.09

** Changed in: xorg (Ubuntu)
   Importance: Undecided = Low

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

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

Title:
  eh

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Donnow

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov 30 22:37:06 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400] [1002:9830] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:076b]
  MachineType: Acer Aspire E1-522
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=b821166e-f395-4dbf-9fa7-a139d9618fb5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire E1-522
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/19/2013:svnAcer:pnAspireE1-522:pvrV2.09:rvnAcer:rnAspireE1-522:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.name: Aspire E1-522
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Nov 30 11:51:32 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1397885] [NEW] [Atheros AR9462] Bluetooth looks activated but cannot be used

2014-12-01 Thread Pierre Equoy
Public bug reported:

Ubuntu 14.10

System Information
Manufacturer: Acer
Product Name: Aspire VN7-591G
Version: V1.08
SKU Number: Aspire VN7-591G_091B_1.08
Family: Sharkbay System

lspci
07:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
(rev 01)


lsusb -v
Bus 003 Device 006: ID 04ca:300d Lite-On Technology Corp. 


Steps to reproduce:
1. Activate a Bluetooth device (for instance a mouse or a nearby device)
2. On the laptop, press the Bluetooth icon, then Set Up new Device…

Expected result:
2. A list of available bluetooth devices is shown

Actual result:
2. Nothing shows up and the spinning icon keeps spinning with Searching for 
devices...

It looks like the bluetooth device does not work at all.

Apparently, there have been previous bugs reported and corrected [1],
but the situation still occurs with this module on my laptop...

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu20
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec  1 16:35:17 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-15 (15 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: Acer Aspire VN7-591G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-591G
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: V1.08
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-591G:pvrV1.08:rvnAcer:rnAspireVN7-591G:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08:
dmi.product.name: Aspire VN7-591G
dmi.product.version: V1.08
dmi.sys.vendor: Acer
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 5C:93:A2:EB:FF:43  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:2751 acl:0 sco:0 events:351 errors:0
TX bytes:3779 acl:0 sco:0 commands:306 errors:0
syslog:
 Dec  1 16:21:16 Miles bluetoothd[631]: Discovery session 0x7fa5da51da30 with 
:1.228 activated
 Dec  1 16:27:43 Miles bluetoothd[631]: Discovery session 0x7fa5da530a50 with 
:1.230 activated

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


** Tags: amd64 apport-bug bluetooth bluez utopic

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

Title:
  [Atheros AR9462] Bluetooth looks activated but cannot be used

Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10

  System Information
Manufacturer: Acer
Product Name: Aspire VN7-591G
Version: V1.08
SKU Number: Aspire VN7-591G_091B_1.08
Family: Sharkbay System

  lspci
  07:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
(rev 01)

  
  lsusb -v
  Bus 003 Device 006: ID 04ca:300d Lite-On Technology Corp. 

  
  Steps to reproduce:
  1. Activate a Bluetooth device (for instance a mouse or a nearby device)
  2. On the laptop, press the Bluetooth icon, then Set Up new Device…

  Expected result:
  2. A list of available bluetooth devices is shown

  Actual result:
  2. Nothing shows up and the spinning icon keeps spinning with Searching for 
devices...

  It looks like the bluetooth device does not work at all.

  Apparently, there have been previous bugs reported and corrected [1],
  but the situation still occurs with this module on my laptop...

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 16:35:17 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-15 (15 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire VN7-591G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  

[Touch-packages] [Bug 1397887] [NEW] Apport asks to install 'bluez-hcidump' but this package does not exist

2014-12-01 Thread Pierre Equoy
Public bug reported:

I wanted to file a bug regarding bluetooth, so I run 'ubuntu-bug bluez'.

Apport is launched and proposes the following:


Your bug report will be processed in few seconds.
If you can reproduce it, please follow the next steps:
- Install the package 'bluez-hcidump'
- Open a new terminal
- Run the command sudo hcidump -XYt  $HOME/hci.log
- Reproduce the actions until the error happens
- On the terminal, press Ctrl+C to stop hcidump.
- Attach the file hci.log to the bug report.


So I try to install the 'bluez-hcidump' package, but...


% sudo apt-get install bluez-hcidump 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package bluez-hcidump is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'bluez-hcidump' has no installation candidate


ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu20
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec  1 16:50:04 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-15 (15 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: Acer Aspire VN7-591G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-591G
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: V1.08
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-591G:pvrV1.08:rvnAcer:rnAspireVN7-591G:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08:
dmi.product.name: Aspire VN7-591G
dmi.product.version: V1.08
dmi.sys.vendor: Acer
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 5C:93:A2:EB:FF:43  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:5529 acl:0 sco:0 events:856 errors:0
TX bytes:6892 acl:0 sco:0 commands:727 errors:0
syslog:
 Dec  1 16:21:16 Miles bluetoothd[631]: Discovery session 0x7fa5da51da30 with 
:1.228 activated
 Dec  1 16:27:43 Miles bluetoothd[631]: Discovery session 0x7fa5da530a50 with 
:1.230 activated

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


** Tags: amd64 apport-bug utopic

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

Title:
  Apport asks to install 'bluez-hcidump' but this package does not exist

Status in bluez package in Ubuntu:
  New

Bug description:
  I wanted to file a bug regarding bluetooth, so I run 'ubuntu-bug
  bluez'.

  Apport is launched and proposes the following:

  
  Your bug report will be processed in few seconds.
  If you can reproduce it, please follow the next steps:
  - Install the package 'bluez-hcidump'
  - Open a new terminal
  - Run the command sudo hcidump -XYt  $HOME/hci.log
  - Reproduce the actions until the error happens
  - On the terminal, press Ctrl+C to stop hcidump.
  - Attach the file hci.log to the bug report.
  

  So I try to install the 'bluez-hcidump' package, but...

  
  % sudo apt-get install bluez-hcidump 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package bluez-hcidump is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'bluez-hcidump' has no installation candidate
  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 16:50:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-15 (15 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire VN7-591G
  

Re: [Touch-packages] [Bug 1396919] Re: unity8 display blank in emulator when virtualization disabled

2014-12-01 Thread Michał Sawicz
 With visualization disabled, it run so slow and we should dis-courage
 user to try it even if we can make it work.

I agree.

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

Title:
  unity8 display blank in emulator when virtualization disabled

Status in goget-ubuntu-touch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Emulator screen remains blank when virtualization is disabled.

  Step to reproduce:

  1. disable virtualization support in your BIOS
  2. install utopic.
  3. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa
  4. sudo apt-get install ubuntu-sdk
  5. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and 
chroot:click-ubuntu-sdk-14.10-i386
  6. create device instance i386 / rtm-14.09 and launch it.

  Expected result:
  See ubuntu phone UI there.

  Current result:
  Emulator screen is black.

  Extra Note:
  1. On the pc, in the first run of the instance, I can see phone interface on 
first boot after I kill -9 unity8 unity8-dash.
  But this work around failed as I stop the instance and run again. I even 
create the same instance with the other name
     and try this work around, still can't see anything on the screen.
  2. I can run test_glesv2 and see the result on the screen of the display 
correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1396919/+subscriptions

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


[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)

2014-12-01 Thread linuxball
The bug hits me from time to time, too. Right now it shows up, again:

W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
updates/main/i18n/Translation-en  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old
ones used instead.

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

Title:
  apt-get update fails, hash sum mismatches (trusty)

Status in apt package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  1. Release: 
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2.  not a package. The whole distro is broken.

  3. I always expect apt-get update to work, at least with Ubuntu's own
  repositories.

  4. apt-get update failed, and later apt-get dist upgrade

  
  It started with this when doing a normal apt-get update

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/main/source/Sources  Hash Sum mismatch

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/main/binary-amd64/Packages  Hash Sum mismatch

  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty-
  updates/universe/binary-i386/Packages  Hash Sum mismatch

  E: Some index files failed to download. They have been ignored, or old
  ones used instead.

  
  When doing a dist-upgrade, I then got this:
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025.
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: error processing package 
linux-image-extra-3.13.0-36-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however:
Package linux-image-extra-3.13.0-36-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ...
  Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic 
/boot/vmlinuz-3.13.0-36-generic
  Setting up linux-headers-generic (3.13.0.36.43) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: dependency problems prevent configuration of 
linux-generic:
   linux-generic depends on linux-image-generic (= 3.13.0.36.43); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured

  
  And later this at the end:
  Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.5
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Wed Sep 24 21:57:55 2014
  InstallationDate: Installed on 2013-05-09 (503 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago)
  VarLogDistupgradeTermlog:

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

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


[Touch-packages] [Bug 1381050] Re: Import Key File fails when the path of the file has special characters

2014-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.96.1

---
software-properties (0.96.1) vivid; urgency=low

  * fix autopkgtest failure
 -- Michael Vogt michael.v...@ubuntu.com   Mon, 01 Dec 2014 08:04:47 +0100

** Changed in: software-properties (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Import Key File fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  The Import Key File... button in the Authentication tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the /home/$USER/Downloads folder is 
named /home/$USER/Transferências here.
  Adding a key from that folder fails, but adding a key from /home/$USER (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_(Error importing selected file),
_(The selected file may not be a GPG key file 
  or it might be corrupt.))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error(Authentication canceled, changes have not 
been saved)

  self.backend.AddKey(chooser.get_filename()) throws a 
org.freedesktop.DBus.Python.UnicodeEncodeError exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1306494] Re: Not all keys in System Settings Software Updates Authentication can be localized

2014-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.96.1

---
software-properties (0.96.1) vivid; urgency=low

  * fix autopkgtest failure
 -- Michael Vogt michael.v...@ubuntu.com   Mon, 01 Dec 2014 08:04:47 +0100

** Changed in: software-properties (Ubuntu)
   Status: New = Fix Released

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

Title:
  Not all keys in System Settings  Software  Updates 
  Authentication can be localized

Status in Ubuntu Kylin:
  In Progress
Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Please see the screenshot, not all keys are localized.

  系统测试版本:UK14.04-Daily-0410-i386
  系统设置-软件和更新 页面 存在汉化不全问题。

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

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


[Touch-packages] [Bug 1397911] [NEW] mountnfs source /lib/init/mount-functions.sh which has been removed from the package

2014-12-01 Thread Václav Šmilauer
Public bug reported:

In up-to-date 14.04 LTS, I see that the script /etc/network/if-
up.d/mountnfs sources /lib/init/mount-functions.sh (line 14). This file
is not present the current initscripts version (2.88dsf-41ubuntu6)
though debian's 2.88dsf-13.1+squeeze1
(https://packages.debian.org/squeeze/amd64/initscripts/filelist) lists
this file.

This bug is similar to #432029 which has been closed already 2.5 years
ago, so I am opening a separate report.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: initscripts 2.88dsf-41ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-40.69-lowlatency 3.13.11.10
Uname: Linux 3.13.0-40-lowlatency x86_64
NonfreeKernelModules: mic
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
Date: Mon Dec  1 10:29:55 2014
SourcePackage: sysvinit
UpgradeStatus: Upgraded to trusty on 2012-03-12 (993 days ago)
mtime.conffile..etc.default.rcS: 2013-09-27T18:03:30.036417

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


** Tags: amd64 apport-bug trusty

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

Title:
  mountnfs source /lib/init/mount-functions.sh which has been removed
  from the package

Status in sysvinit package in Ubuntu:
  New

Bug description:
  In up-to-date 14.04 LTS, I see that the script /etc/network/if-
  up.d/mountnfs sources /lib/init/mount-functions.sh (line 14). This
  file is not present the current initscripts version (2.88dsf-
  41ubuntu6) though debian's 2.88dsf-13.1+squeeze1
  (https://packages.debian.org/squeeze/amd64/initscripts/filelist) lists
  this file.

  This bug is similar to #432029 which has been closed already 2.5 years
  ago, so I am opening a separate report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-40.69-lowlatency 3.13.11.10
  Uname: Linux 3.13.0-40-lowlatency x86_64
  NonfreeKernelModules: mic
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Mon Dec  1 10:29:55 2014
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2012-03-12 (993 days ago)
  mtime.conffile..etc.default.rcS: 2013-09-27T18:03:30.036417

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

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


[Touch-packages] [Bug 1397912] [NEW] [webapp-container] apparmor denies access to QML cache

2014-12-01 Thread David Barth
Public bug reported:

While using the Twitter webapp, Alan noticed the following messages in
syslog:

[Mon Dec  1 07:07:54 2014] type=1400 audit(1417426476.230:153): 
apparmor=DENIED operation=open 
profile=com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.21 
name=/home/phablet/.cache/QML/Apps/ pid=22634 comm=webapp-containe 
requested_mask=r denied_mask=r fsuid=32011 ouid=32011
[Mon Dec  1 07:07:56 2014] type=1400 audit(1417426477.740:154): 
apparmor=DENIED operation=open 
profile=com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.21//oxide_helper
 name=/sys/devices/system/cpu/ pid=22719 comm=oxide-renderer 
requested_mask=r denied_mask=r fsuid=32011 ouid=0

The webapp was still functional, but probably not taking advantage of
the new QML cache.

** Affects: webbrowser-app
 Importance: Medium
 Status: Triaged

** Affects: apparmor-easyprof-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New

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

** Changed in: webbrowser-app
   Status: New = Triaged

** Changed in: webbrowser-app
   Importance: Undecided = Medium

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

Title:
  [webapp-container] apparmor denies access to QML cache

Status in Web Browser App:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  While using the Twitter webapp, Alan noticed the following messages in
  syslog:

  [Mon Dec  1 07:07:54 2014] type=1400 audit(1417426476.230:153): 
apparmor=DENIED operation=open 
profile=com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.21 
name=/home/phablet/.cache/QML/Apps/ pid=22634 comm=webapp-containe 
requested_mask=r denied_mask=r fsuid=32011 ouid=32011
  [Mon Dec  1 07:07:56 2014] type=1400 audit(1417426477.740:154): 
apparmor=DENIED operation=open 
profile=com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.21//oxide_helper
 name=/sys/devices/system/cpu/ pid=22719 comm=oxide-renderer 
requested_mask=r denied_mask=r fsuid=32011 ouid=0

  The webapp was still functional, but probably not taking advantage of
  the new QML cache.

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

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


[Touch-packages] [Bug 1391798] Re: Left-edge / home does not close temporary scopes

2014-12-01 Thread Michał Sawicz
** Also affects: unity8 (Ubuntu RTM)
   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/1391798

Title:
  Left-edge / home does not close temporary scopes

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

Bug description:
  Steps to reproduce:
  * go to Ubuntu Store
  * press the Ubuntu button on the launcher

  Expected:
  * you're taken back to the leftmost scope

  Current:
  * nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.01+15.04.20141107.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 12 10:34:23 2014
  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/1391798/+subscriptions

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


[Touch-packages] [Bug 1397918] [NEW] krillin #169 + cgroups fix, scopes hang / crash / unusable

2014-12-01 Thread Alan Pope
Public bug reported:

On a couple of occasions over the weekend my phone has become unusable.
I can unlock it, swipe the launcher out, pull down indicators, launch
applications (from the launcher) and switch applications from the side.
I cannot use any scops. They don't respond to touch at all. I'm stuck on
the Today scope.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: libunity-scopes3 0.6.7+15.04.20141107.1~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Mon Dec  1 09:55:21 2014
InstallationDate: Installed on 2014-11-24 (6 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141124-203231)
SourcePackage: unity-scopes-api
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug armhf third-party-packages utopic

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

Title:
  krillin #169 + cgroups fix, scopes hang / crash / unusable

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  On a couple of occasions over the weekend my phone has become
  unusable. I can unlock it, swipe the launcher out, pull down
  indicators, launch applications (from the launcher) and switch
  applications from the side. I cannot use any scops. They don't respond
  to touch at all. I'm stuck on the Today scope.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: libunity-scopes3 0.6.7+15.04.20141107.1~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Dec  1 09:55:21 2014
  InstallationDate: Installed on 2014-11-24 (6 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141124-203231)
  SourcePackage: unity-scopes-api
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: Opinion = In Progress

** Changed in: unity8 (Ubuntu RTM)
   Status: Opinion = New

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Albert Astals Cid (aacid) = (unassigned)

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in network-manager package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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


[Touch-packages] [Bug 1397918] Re: krillin #169 + cgroups fix, scopes hang / crash / unusable

2014-12-01 Thread Oliver Grawert
** Changed in: unity-scopes-api (Ubuntu)
   Status: New = Confirmed

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

Title:
  krillin #169 + cgroups fix, scopes hang / crash / unusable

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  On a couple of occasions over the weekend my phone has become
  unusable. I can unlock it, swipe the launcher out, pull down
  indicators, launch applications (from the launcher) and switch
  applications from the side. I cannot use any scops. They don't respond
  to touch at all. I'm stuck on the Today scope.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: libunity-scopes3 0.6.7+15.04.20141107.1~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Dec  1 09:55:21 2014
  InstallationDate: Installed on 2014-11-24 (6 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141124-203231)
  SourcePackage: unity-scopes-api
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1384393] Re: Photos in scope not visible until all loaded

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Status: In Progress = New

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Albert Astals Cid (aacid) = (unassigned)

** Changed in: unity8 (Ubuntu RTM)
   Status: New = Triaged

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  Photos in scope not visible until all loaded

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Savilerow project:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  I think this is a generic unity8 issue that is exposed in the My
  Photos scope. This scope displays photos from the photo roll through
  mediascanner.

  Problem:
  When there are many photos, the scope does not display thumbnails for quite a 
while. (It may even be that no photo thumbnails display until all are loaded 
into memory.) This is an awkward user experience because the scope looks like 
nothing is happening for significant periods of time. 

  Expectation:
  Photo thumbnails would display as they arrive. (Perhaps there would be some 
kind of window around what is currently visible in the scope so that as soon as 
photos in the current scroll area, before it by some amount, and after it by 
some amount are in memory, they could display and the user could scroll 
somewhat, with the window moving appropriately.)

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

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


[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Status: New = Triaged

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

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

** Branch linked: lp:~aacid/unity8/asyncCroppedImageSizer

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

Title:
  Dash pauses/stutters during scope switching left/right

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  Dash pauses/stutters during scope switching left/right.

  Watching the log:   tail -f ~/.cache/upstart/unity8-dash.log

  I can see error messages flood out whenever the dash pauses/stutters
  during left/right swipes:

  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height
  
file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: 
QML Label: Binding loop detected for property height

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

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


[Touch-packages] [Bug 1391798] Re: Left-edge / home does not close temporary scopes

2014-12-01 Thread Michał Sawicz
** Also affects: canonical-devices-system-image
   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/1391798

Title:
  Left-edge / home does not close temporary scopes

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce:
  * go to Ubuntu Store
  * press the Ubuntu button on the launcher

  Expected:
  * you're taken back to the leftmost scope

  Current:
  * nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.01+15.04.20141107.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 12 10:34:23 2014
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned

2014-12-01 Thread Iain Lane
** Also affects: ureadahead (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

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

Title:
  package ureadahead 0.100.0-16 failed to install/upgrade: triggers
  looping, abandoned

Status in ureadahead package in Ubuntu:
  Fix Released
Status in ureadahead source package in Trusty:
  New
Status in ureadahead source package in Utopic:
  New

Bug description:
  Happend on today's sudo apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: ureadahead 0.100.0-16
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  Date: Fri Nov 21 09:17:23 2014
  DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-11-03 (17 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103)
  SourcePackage: ureadahead
  Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10

2014-12-01 Thread Roman Shipovskij
Bug still present in java programs on 14.04.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04,
  14.04.1, 14.10

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in indicator-keyboard package in Ubuntu:
  Triaged
Status in openjdk-7 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in Fedora:
  Unknown
Status in gnome-shell package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters-keyboard-hotkeys-windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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


[Touch-packages] [Bug 1372952] Re: Can pull in greeter above the lockscreen

2014-12-01 Thread Michał Sawicz
** Also affects: unity8 (Ubuntu RTM)
   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/1372952

Title:
  Can pull in greeter above the lockscreen

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

Bug description:
  * Enable the lockscreen on your phone
  * with the locked greeter, swipe the greeter from right to left to get to the 
lockscreen
  * on the lockscreen, pull in the greeter from the left

  actual outcome:
   greeter is pulled in, animates back outside the screen when released

  expected outcome:
   should not be able to pull in the greeter on top of the lock screen

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

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


[Touch-packages] [Bug 1355284] Re: Switching swipe directions should reverse app spread

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Status: Triaged = New

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Michał Sawicz (saviq) = (unassigned)

** Also affects: canonical-devices-system-image
   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/1355284

Title:
  Switching swipe directions should reverse app spread

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  The new app spread is gorgeous, thank you! In general we try to ensure
  reversibility of transitions - if a user starts a gesture and changes
  their mind they should be able to reverse the gesture and exit the
  transition as long as they have not lifted their finger.

  In this case, a user swiping from the right who intends to toggle
  windows but overshoots (thereby entering the spread) should be able to
  change direction, move their finger back towards the right edge,
  returning to the toggle and then to the original app if they move
  their finger all the way off the right edge.

  ---
  Desired solution

  User should be in control through the whole the gesture. We want to have
  reversibility also after second commit point the same way we have for the 
first commit point in current implementation. 

  This has now been captured also in the right edge documentation:
  https://docs.google.com/a/canonical.com/document/d/1FC_-
  5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit#

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

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


[Touch-packages] [Bug 1368677] Re: [Apps switcher] Move commit points toward right to make spread more accessible

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Status: Triaged = New

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Michał Sawicz (saviq) = (unassigned)

** Also affects: canonical-devices-system-image
   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/1368677

Title:
  [Apps switcher] Move commit points toward right to make spread more
  accessible

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  In our user testing users often failed to access the spread via long
  right edge swipe. We want to make spread a bit more accessible by
  moving second phase commit point few grid units to right. Not to
  affect the overall functionality and experience the right thing to do
  is to make first phase reveal phase shorter which then automatically
  moves both first phase and second phase commit point same amount
  towards right.

  See the spec for detailed descriptions of different gesture phases:
  https://docs.google.com/a/canonical.com/document/d/1FC_-
  5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit#

  Desired solution:
  Shorten the first phase reveal by 4 gu

  Since the 4gu value is just an estimate and might need refining the
  result should be approved with design team before committing.

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

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


[Touch-packages] [Bug 1368287] Re: [App switcher] Different drag behaviour between items that can and cannot be closed

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Status: In Progress = New

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Andrea Cimitan (cimi) = (unassigned)

** Also affects: canonical-devices-system-image
   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/1368287

Title:
  [App switcher] Different drag behaviour between items that can and
  cannot be closed

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Drag to close is a great feature in application spread. In user
  testing it had a great success rate and users understood it and knew
  how to use it. The problem is the Dash item that's part of the spread
  but is the only item which cannot be closed. Currently the Dash item
  drag movement is similar to the movement of the items that actually
  can be closed.

  We want to make Dash drag different from others by restricting the
  movement while still responding to user's drag.

  
  Desired solution

  Use restriction algorithm for dash item so that it moves along the
  drag but soon starts restricting the movement indicating that it's an
  item that cannot be closed.

  Here is quite nice elastic function that can be used:
  function elastic( currentPosition, limit ) {
  return limit * ( 1 - Math.pow( ( limit - 1 ) / limit, currentPosition ) )
  }

  Where:
  limit is the highest value that ever can be returned by the function
  current position is the value to be limited

  It's a bit hard to describe the parameters, therefore I created a prototype 
that should explain the usage. 
  Find it from: lp:~willow-team/willow/elasticRestriction

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

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


[Touch-packages] [Bug 1395075] Re: [Security] Can easily bypass pincode

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  [Security] Can easily bypass pincode

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Confirmed

Bug description:
  rtm image 166

  1. reboot the phone
  2. As soon as the greeter is show, try to swipe it away.

  What happens:
  In some attempts we don't see the pincode screen rather 'Scopes' is seen with 
a spinner and there you are unlocked.

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

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


[Touch-packages] [Bug 1368668] Re: [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
 Assignee: Michał Sawicz (saviq) = (unassigned)

** Changed in: unity8 (Ubuntu RTM)
   Status: Triaged = New

** Also affects: canonical-devices-system-image
   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/1368668

Title:
  [Apps switcher] Visual feedback of user's finger movement needed
  throughout the gesture

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Right edge compound gesture has two phases. During the second phase
  all the recent applications stack together in to the apps spread.
  There is a second phase commit threshold value after which this
  stacking happens. Currently when this commit threshold has been
  exceeded user loses control over the gesture. There is no way to go
  back and the UI doesn't react to further finger movement to left. We
  want user to be in control also after the second commit line.

  RIght edge gesture progress is explained and broken into pieces in this spec:
  
https://docs.google.com/a/canonical.com/document/d/1FC_-5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit#

  There is already a bug about reversibility (movement back to right)
  after second commit line (#1355284). So this bug is to fix the non-
  responsiveness after second phase commit line when user moves finger
  towards left edge.

  Steps to repro:
  1. Start right edge swipe
  2. keep finger pressed and drag to left until you reach the point when apps 
spread is formed
  3. keep still finger pressed and move finger towards left

  Current behaviour:
  No visual feedback

  Expected behaviour: 
  Applications should start moving to left and stack the way they do when 
they're dragged to left in normal spread use case

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

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


[Touch-packages] [Bug 1397887] Re: Apport asks to install 'bluez-hcidump' but this package does not exist

2014-12-01 Thread Christopher M. Penalver
Pierre Equoy, thank you for reporting this and helping make Ubuntu
better. As per https://launchpad.net/ubuntu/+source/bluez-hcidump the
package is not available in Utopic+. Hence, it would appear apport would
want to be adjusted for these releases to not include this request,
and/or provide some other suggestion.

** Package changed: bluez (Ubuntu) = apport (Ubuntu)

** Changed in: apport (Ubuntu)
   Importance: Undecided = Low

** Changed in: apport (Ubuntu)
   Status: New = Triaged

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

Title:
  Apport asks to install 'bluez-hcidump' but this package does not exist

Status in apport package in Ubuntu:
  Triaged

Bug description:
  I wanted to file a bug regarding bluetooth, so I run 'ubuntu-bug
  bluez'.

  Apport is launched and proposes the following:

  
  Your bug report will be processed in few seconds.
  If you can reproduce it, please follow the next steps:
  - Install the package 'bluez-hcidump'
  - Open a new terminal
  - Run the command sudo hcidump -XYt  $HOME/hci.log
  - Reproduce the actions until the error happens
  - On the terminal, press Ctrl+C to stop hcidump.
  - Attach the file hci.log to the bug report.
  

  So I try to install the 'bluez-hcidump' package, but...

  
  % sudo apt-get install bluez-hcidump 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package bluez-hcidump is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'bluez-hcidump' has no installation candidate
  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 16:50:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-15 (15 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire VN7-591G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-591G
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-591G:pvrV1.08:rvnAcer:rnAspireVN7-591G:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08:
  dmi.product.name: Aspire VN7-591G
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 5C:93:A2:EB:FF:43  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:5529 acl:0 sco:0 events:856 errors:0
TX bytes:6892 acl:0 sco:0 commands:727 errors:0
  syslog:
   Dec  1 16:21:16 Miles bluetoothd[631]: Discovery session 0x7fa5da51da30 with 
:1.228 activated
   Dec  1 16:27:43 Miles bluetoothd[631]: Discovery session 0x7fa5da530a50 with 
:1.230 activated

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

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


[Touch-packages] [Bug 1397918] Re: krillin #169 + cgroups fix, scopes hang / crash / unusable

2014-12-01 Thread Oliver Grawert
i have seen this without the cgmanager change on 169 too

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

Title:
  krillin #169 + cgroups fix, scopes hang / crash / unusable

Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  On a couple of occasions over the weekend my phone has become
  unusable. I can unlock it, swipe the launcher out, pull down
  indicators, launch applications (from the launcher) and switch
  applications from the side. I cannot use any scops. They don't respond
  to touch at all. I'm stuck on the Today scope.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: libunity-scopes3 0.6.7+15.04.20141107.1~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Dec  1 09:55:21 2014
  InstallationDate: Installed on 2014-11-24 (6 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141124-203231)
  SourcePackage: unity-scopes-api
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1394893] Re: package ureadahead 0.100.0-16 failed to install/upgrade: triggers looping, abandoned

2014-12-01 Thread Iain Lane
This can happen in dist-upgrades, depending on the configure/trigger
order that's used. I think we should SRU this fix to 14.04/14.10. But
double check that dpkg in those versions supports the interest-noawait
variants first.

Assign back to me if nobody takes this before 2014-12-05.

** Changed in: ureadahead (Ubuntu Trusty)
 Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)

** Changed in: ureadahead (Ubuntu Utopic)
 Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)

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

Title:
  package ureadahead 0.100.0-16 failed to install/upgrade: triggers
  looping, abandoned

Status in ureadahead package in Ubuntu:
  Fix Released
Status in ureadahead source package in Trusty:
  New
Status in ureadahead source package in Utopic:
  New

Bug description:
  Happend on today's sudo apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: ureadahead 0.100.0-16
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  Date: Fri Nov 21 09:17:23 2014
  DuplicateSignature: package:ureadahead:0.100.0-16:triggers looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-11-03 (17 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141103)
  SourcePackage: ureadahead
  Title: package ureadahead 0.100.0-16 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1393523] Re: Dragging windows in Expo mode occasionally results in weird behavior

2014-12-01 Thread Bruno Nova
This bug occurred again now, but this time Super+S didn't close Expo mode.
The window drag action got stuck in Expo mode, and every time I pressed the 
Super key, the window moved to to cursor position.
I had to run sudo restart lightdm from a virtual console to restart the 
session.

This should be of high importance! Could a developer check (triage) this
bug?

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

Title:
  Dragging windows in Expo mode occasionally results in weird behavior

Status in compiz package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  There are some times where dragging windows in Expo mode doesn't work or 
results in weird behaviors.
  Sometimes, when dragging a window, the drag fails midway and then clicking 
anywhere on the screen does nothing (even when clicking in the Expo button, 
needing to press Super+S to exit Expo mode).

  I have also noticed that, when moving the cursor around in Expo mode, the 
close/minimize/maximize buttons of the windows would sometimes highlight and 
the locally integrated menus would be displayed.
  This seems to occur in the current workspace (the one where I was before 
entering Expo mode) when I move the cursor over where the buttons or menu are 
when out of the Expo mode.

  To reproduce that:
  * Open a window (terminal, nautilus, or anything else)
  * Move the window to the center (to make the next step easier)
  * Move the mouse cursor to a few pixels to the left of the close button of 
the window
  * Open Expo mode by pressing Super+S
  * Now start moving the cursor slowly to the right and see if the buttons (and 
menu) of the window are highlighted
  * When one of the buttons is highlighted, click. The action of that button 
will be performed (and it shouldn't) and Expo mode will exit to that workspace

  This may be the cause of the problem.

  I have also reproduced this in the guest session and in a 14.04.1
  virtual machine (not updated).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:56:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (35 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1377939] Re: [location] + [Scope] using location cause a dialog An unconfined application wants to access your current location

2014-12-01 Thread Olga Kemmet
The importance and status were changed so that the corresponding designer can 
review the bug/implementation. 
Otherwise the bug will always remain as new for ubuntu-ux. This way we can 
make sure not to loose track of it or comment here if there are any other 
outstanding issues.

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

Title:
  [location] + [Scope] using location cause a dialog An unconfined
  application wants to access your current location

Status in Ubuntu UX bugs:
  Triaged
Status in Unity Online Music Scope:
  Invalid
Status in location-service package in Ubuntu:
  Invalid
Status in trust-store package in Ubuntu:
  Fix Released
Status in trust-store package in Ubuntu RTM:
  Fix Released

Bug description:
  Swiping to the flickr scope yields a confusing dialog.

  Build: 20141006
  Clean install (--wipe)

  What you expected to happen
  If flickr/a scope wants to access my location, I expected to be asked that

  What happened instead
  I was asked if an unconfined app could use my location.
  unconfined
  An unconfined applications wants to access your current location
  [deny] [allow]

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

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


[Touch-packages] [Bug 1339413] Re: [Launcher] Emblems for apps that are not pinned to launcher don't show up

2014-12-01 Thread Vesa Rautiainen
** Changed in: ubuntu-ux
   Status: Fix Committed = Fix Released

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

Title:
  [Launcher] Emblems for apps that are not pinned to launcher don't show
  up

Status in Ubuntu UX bugs:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When a push notification comes for an app that isn't running and is
  not pinned, the count emblem can't be displayed.

  Solution desired from the push notification team would be to add
  ephemeral entries to the launcher, that only live as long as the
  count emblem is non-zero.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul  9 02:07:46 2014
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  ---
  Desired resolution:

  - emblems should be displayed and updated for apps that are not
  running and not pinned to the launcher.

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

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


[Touch-packages] [Bug 1302761] Re: Wrong icon when dragging items in the launcher

2014-12-01 Thread Vesa Rautiainen
** Changed in: ubuntu-ux
   Status: Fix Committed = Fix Released

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

Title:
  Wrong icon when dragging items in the launcher

Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps:
  - long-press and drag'n'drop an icon in the launcher
  - long-press and start dragging another icon in the launcher

  Expected:
  - correct items are dragged in both cases

  Current:
  - the item dragged has the first item's icon

  
  
  Desired resolution:

  
  Often when trying to organise items in launcher the dragged item behaves 
strangely. Actually not even dragging is needed, it is enough just to long 
press an item.

  This doesn't happen every time but still often enough to be easily
  reproduced.

  Steps to reproduce:
  Long press some launcher item

  Expected outcome:
  User can move the item around and the icon is the same as what it was 
initially

  Actual outcome:
  Icon changes to some other icon (I wasn't able to figure out logic to which 
it changes, it can even be an icon that's not pinned or isn't currently in 
recent apps list)

  When released icon changes back to its original one.

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

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


[Touch-packages] [Bug 1370075] Re: [Scopes][App switcher] Non-favourite feeds should appear in the apps stack

2014-12-01 Thread Vesa Rautiainen
** Changed in: ubuntu-ux
   Importance: High = Medium

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

Title:
  [Scopes][App switcher] Non-favourite feeds should appear in the apps
  stack

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  Currently app switcher (accessed via long right edge swipe) shows the
  Dash and all recent applications.

  The Dash contains favourite feeds. The current design proposal is that
  an individually opened feed (feed = scope) opens as a separate
  application in its own instance if it's not one of the favourite
  feeds.

  Within the feed there can be a navigation similarly as apps have but
  there is no header back navigation back to dash. Even if it was
  launched from there. So these non-favourite feeds are self contained
  items behaving like any app.

  Because of their app-like nature we want to add non-favourite feeds to
  the spread view and treat them there as any applications. They follow
  same recency order positioning, they can be closed and navigated to.

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

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


[Touch-packages] [Bug 1357333] Re: [Launcher] shouldn't hide on long left edge swipes in some circumstances

2014-12-01 Thread Vesa Rautiainen
** Changed in: ubuntu-ux
   Status: Fix Committed = Fix Released

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

Title:
  [Launcher] shouldn't hide on long left edge swipes in some
  circumstances

Status in Ubuntu UX bugs:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  There are some cases when the Launcher shouldn't hide on long left
  edge swipes. One example is when the dash is already focused.

  
  Desired solution

  When there is no visible navigation change happening due to the long
  left edge swipe the Launcher should not hide. For example if apps
  scope is the current screen when the long left edge swipe is performed

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

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


[Touch-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-12-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Also affects nvidia-graphics-drivers-319

The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

neuffer@charion:~$ xset -q -d :0.0
Keyboard Control:
  auto repeat:  onkey click percent:  0LED mask:  
  XKB indicators:
00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep:   off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock:  off
12: Group 2: off13: Mouse Keys:  off
  auto repeat delay:  500repeat rate:  20
  auto repeating keys:  00ffdbbf
fadfffefffed
9fff
fff7
  bell percent:  50bell pitch:  400bell duration:  100
Pointer Control:
  acceleration:  2/1threshold:  4
Screen Saver:
  prefer blanking:  yesallow exposures:  yes
  timeout:  0cycle:  0
Colors:
  default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
Font Path:
  
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
  Standby: 0Suspend: 0Off: 0
  DPMS is Enabled
  Monitor is On

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 12:06:30 2014
InstallationDate: Installed on 2014-01-07 (3 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dell
 Importance: Undecided
 Status: Confirmed

** Affects: hwe-next
 Importance: Undecided
 Status: Confirmed

** Affects: nouveau
 Importance: Low
 Status: Confirmed

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

** Affects: xorg-server
 Importance: Low
 Status: Confirmed


** Tags: amd64 apport-bug precise trusty utopic
-- 
[Dell M4800] DPMS support broken, fails to wake up the monitor after putting it 
to sleep
https://bugs.launchpad.net/bugs/1268151
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-12-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Also affects nvidia-graphics-drivers-319

The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

neuffer@charion:~$ xset -q -d :0.0
Keyboard Control:
  auto repeat:  onkey click percent:  0LED mask:  
  XKB indicators:
00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep:   off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock:  off
12: Group 2: off13: Mouse Keys:  off
  auto repeat delay:  500repeat rate:  20
  auto repeating keys:  00ffdbbf
fadfffefffed
9fff
fff7
  bell percent:  50bell pitch:  400bell duration:  100
Pointer Control:
  acceleration:  2/1threshold:  4
Screen Saver:
  prefer blanking:  yesallow exposures:  yes
  timeout:  0cycle:  0
Colors:
  default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
Font Path:
  
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
  Standby: 0Suspend: 0Off: 0
  DPMS is Enabled
  Monitor is On

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 12:06:30 2014
InstallationDate: Installed on 2014-01-07 (3 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dell
 Importance: Undecided
 Status: Confirmed

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

** Affects: nouveau
 Importance: Low
 Status: Confirmed

** Affects: xorg-server
 Importance: Low
 Status: Confirmed


** Tags: amd64 apport-bug precise trusty utopic
-- 
[Dell M4800] DPMS support broken, fails to wake up the monitor after putting it 
to sleep
https://bugs.launchpad.net/bugs/1268151
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-12-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Also affects nvidia-graphics-drivers-319

The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

neuffer@charion:~$ xset -q -d :0.0
Keyboard Control:
  auto repeat:  onkey click percent:  0LED mask:  
  XKB indicators:
00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep:   off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock:  off
12: Group 2: off13: Mouse Keys:  off
  auto repeat delay:  500repeat rate:  20
  auto repeating keys:  00ffdbbf
fadfffefffed
9fff
fff7
  bell percent:  50bell pitch:  400bell duration:  100
Pointer Control:
  acceleration:  2/1threshold:  4
Screen Saver:
  prefer blanking:  yesallow exposures:  yes
  timeout:  0cycle:  0
Colors:
  default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
Font Path:
  
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
  Standby: 0Suspend: 0Off: 0
  DPMS is Enabled
  Monitor is On

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 12:06:30 2014
InstallationDate: Installed on 2014-01-07 (3 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: nouveau
 Importance: Low
 Status: Confirmed

** Affects: xorg-server
 Importance: Low
 Status: Confirmed


** Tags: amd64 apport-bug precise trusty utopic
-- 
[Dell M4800] DPMS support broken, fails to wake up the monitor after putting it 
to sleep
https://bugs.launchpad.net/bugs/1268151
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1396526] Re: /usr/bin/unity8-dash:11:std::basic_string:unity::scopes::Category::title:title:scopes_ng::Categories::data:QSortFilterProxyModel::data

2014-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scopes-shell -
0.5.4+15.04.20141128-0ubuntu1

---
unity-scopes-shell (0.5.4+15.04.20141128-0ubuntu1) vivid; urgency=low

  [ Pete Woods ]
  * Write the scope settings using UTF-8 to match up with the scope
regsitry (LP: #1381010)
  * Move QNetworkAccessManager onto correct thread
  * Fix crash exposed by today scope (LP: #1396526)

  [ Pawel Stolowski ]
  * Fix version check for unity api to match version required by
src/Unity/CMakeLists.txt.
  * Read /custom/partner-id value (if present) and pass it with user-
agent hint. (LP: #1389273)

  [ Albert Astals ]
  * Don't call Result::contains and then Result::value
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 28 Nov 2014 
08:52:43 +

** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  
/usr/bin/unity8-dash:11:std::basic_string:unity::scopes::Category::title:title:scopes_ng::Categories::data:QSortFilterProxyModel::data

Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.01.1+15.04.2014~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/1d146aed1a307e6e69dc8cb8f3d7ee012df94e2c
  contains more details.

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

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


[Touch-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-12-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Also affects nvidia-graphics-drivers-319

The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

neuffer@charion:~$ xset -q -d :0.0
Keyboard Control:
  auto repeat:  onkey click percent:  0LED mask:  
  XKB indicators:
00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep:   off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock:  off
12: Group 2: off13: Mouse Keys:  off
  auto repeat delay:  500repeat rate:  20
  auto repeating keys:  00ffdbbf
fadfffefffed
9fff
fff7
  bell percent:  50bell pitch:  400bell duration:  100
Pointer Control:
  acceleration:  2/1threshold:  4
Screen Saver:
  prefer blanking:  yesallow exposures:  yes
  timeout:  0cycle:  0
Colors:
  default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
Font Path:
  
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
  Standby: 0Suspend: 0Off: 0
  DPMS is Enabled
  Monitor is On

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 12:06:30 2014
InstallationDate: Installed on 2014-01-07 (3 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: xorg-server
 Importance: Low
 Status: Confirmed


** Tags: amd64 apport-bug precise trusty utopic
-- 
[Dell M4800] DPMS support broken, fails to wake up the monitor after putting it 
to sleep
https://bugs.launchpad.net/bugs/1268151
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1346734] Re: Unprivileged LXC containers don't work under systemd

2014-12-01 Thread Martin Pitt
Finally!
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntuid=1e76bb017a447d92b224f0476d5d5551bbd16850

** Changed in: systemd (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Unprivileged LXC containers don't work under systemd

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  With systemd 208, unprivileged containers stop working when running
  under systemd (working fine under upstart with cgmanager). Quoting
  Stephane Graber:

  In this setup, things don't work nearly as well. On login I'm only
  placed into the name=systemd cgroup and not in any of the others, which
  means that unprivileged LXC isn't usable.

  Martin suggested setting JoinControllers in /etc/systemd/system.conf but
  upon closer inspection, this isn't at all what we want. This setting is
  used to tell systemd what controllers to co-mount, by default this is
  set to cpu,cpuset (which caused the earlier cgmanager breakage).

  Even though this option isn't helpful for what we want (i.e. setting the
  list of cgroup controllers the first PID of a user session should be
  added to), we should nonetheless set it to an empty string which should
  instruct systemd not to co-mount any controller, therefore giving us a
  more reliable behavior (identical to what we have in the upstart world
  and unlikely to confuse lxc and other stuff doing direct cgroup access).

  Additionally, we need to find an equivalent to our good old
  Controllers logind.conf option, or re-introduce it or just patch
  logind so that it will always join all the controllers (similar to what
  the shim does).

  
  == Actions ==
   * Update systemd.conf to set JoinControllers to an empty value.
   * Make it so new user sessions are joined to all the available
 controllers by doing one of the following:
 - Find the magic undocumented config variable
 - Re-introduce the Controllers option in logind.conf
 - Patch logind to have it always join all available controllers

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

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


[Touch-packages] [Bug 1389273] Re: Track app sales per partner

2014-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scopes-shell -
0.5.4+15.04.20141128-0ubuntu1

---
unity-scopes-shell (0.5.4+15.04.20141128-0ubuntu1) vivid; urgency=low

  [ Pete Woods ]
  * Write the scope settings using UTF-8 to match up with the scope
regsitry (LP: #1381010)
  * Move QNetworkAccessManager onto correct thread
  * Fix crash exposed by today scope (LP: #1396526)

  [ Pawel Stolowski ]
  * Fix version check for unity api to match version required by
src/Unity/CMakeLists.txt.
  * Read /custom/partner-id value (if present) and pass it with user-
agent hint. (LP: #1389273)

  [ Albert Astals ]
  * Don't call Result::contains and then Result::value
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 28 Nov 2014 
08:52:43 +

** Changed in: unity-scopes-shell (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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1389273

Title:
  Track app sales per partner

Status in Pay UI:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu RTM:
  Triaged

Bug description:
  We need to track what app sales come from which partner, by sending
  the partner string when performing a purchase.

  For documentation on what the server expects, see:
  https://wiki.ubuntu.com/AppStore/Interfaces/Purchases#purchases

  The code for each partner needs to be specified in the OEM image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pay-ui/+bug/1389273/+subscriptions

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


[Touch-packages] [Bug 1330959] Re: Art in cards with backgrounds are Ubuntu-shaped

2014-12-01 Thread Michał Sawicz
I'm not sure we'll be able to fix this by r1, the related bug #1157712
in UITK was just closed 'Won't Fix', and any workaround we employ will
negatively impact performance of items in the dash suffering from this.

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

Title:
  Art in cards with backgrounds are Ubuntu-shaped

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  When a card has its background enabled, the art should not have its
  bottom edge shaped.

  Until the new shape item comes, we should probably use the
  UbuntuShapeForItem component.

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

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


[Touch-packages] [Bug 1381010] Re: Cannot get Chinese string in the scope setting

2014-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-scopes-shell -
0.5.4+15.04.20141128-0ubuntu1

---
unity-scopes-shell (0.5.4+15.04.20141128-0ubuntu1) vivid; urgency=low

  [ Pete Woods ]
  * Write the scope settings using UTF-8 to match up with the scope
regsitry (LP: #1381010)
  * Move QNetworkAccessManager onto correct thread
  * Fix crash exposed by today scope (LP: #1396526)

  [ Pawel Stolowski ]
  * Fix version check for unity api to match version required by
src/Unity/CMakeLists.txt.
  * Read /custom/partner-id value (if present) and pass it with user-
agent hint. (LP: #1389273)

  [ Albert Astals ]
  * Don't call Result::contains and then Result::value
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 28 Nov 2014 
08:52:43 +

** Changed in: unity-scopes-shell (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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1381010

Title:
  Cannot get Chinese string in the scope setting

Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  I am trying to set some Chinese Strings in the scope. however, I
  cannot get it but the default one. If I input an English string there
  in the setting, I can always get it correctly.

  My test code is at: bzr branch lp:~liu-xiao-
  guo/debiantrial/settingscope

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

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


[Touch-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-12-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Also affects nvidia-graphics-drivers-319

The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.

HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display

Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
Only a restart of the Xserver will bring back the display at that point.

A cycle of
xset dpms force off; sleep 30; xset dpms force on
will leave the display dark.

At the moment I help myself by not allowing DPMS to switch off the display:
neuffer@charion:~$ xset dpms 0 0 0

neuffer@charion:~$ xset -q -d :0.0
Keyboard Control:
  auto repeat:  onkey click percent:  0LED mask:  
  XKB indicators:
00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep:   off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock:  off
12: Group 2: off13: Mouse Keys:  off
  auto repeat delay:  500repeat rate:  20
  auto repeating keys:  00ffdbbf
fadfffefffed
9fff
fff7
  bell percent:  50bell pitch:  400bell duration:  100
Pointer Control:
  acceleration:  2/1threshold:  4
Screen Saver:
  prefer blanking:  yesallow exposures:  yes
  timeout:  0cycle:  0
Colors:
  default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
Font Path:
  
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
DPMS (Energy Star):
  Standby: 0Suspend: 0Off: 0
  DPMS is Enabled
  Monitor is On

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.20-0ubuntu9
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Sat Jan 11 12:06:30 2014
InstallationDate: Installed on 2014-01-07 (3 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise trusty utopic
-- 
[Dell M4800] DPMS support broken, fails to wake up the monitor after putting it 
to sleep
https://bugs.launchpad.net/bugs/1268151
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1350891] Re: [Dash] [design] Suru Background should scroll

2014-12-01 Thread Michał Sawicz
This is awaiting assets.

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  [Dash] [design] Suru Background should scroll

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu RTM:
  Incomplete

Bug description:
  On the dash, the Suru paper folds stays fixed at the bottom, while it
  should rather scroll away.

  We should also 'tile' the background, so the paper fold is displayed
  again after scrolling a certain amount of vertical space.

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

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


[Touch-packages] [Bug 622965] Re: New windows always use active window's keyboard layout

2014-12-01 Thread Andrea Azzarone
I can no longer reproduce it on my system. Can anyone confirm it?

** Changed in: compiz
   Status: Confirmed = Incomplete

** Changed in: unity
   Status: Confirmed = Incomplete

** Changed in: compiz (Ubuntu)
   Status: Triaged = Incomplete

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

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

Title:
  New windows always use active window's keyboard layout

Status in Compiz:
  Incomplete
Status in GNOME Control Center:
  Unknown
Status in Unity:
  Incomplete
Status in compiz package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  If Compiz used (e.g. Ubuntu with Unity), Gnome keyboard settings
  Allow different layouts for individual windows  New windows use
  the default layout doesn't work properly. New windows always use last
  active window's layout ignoring default keyboard layout.

  This bug affects all Ubuntu versions using Compiz as window manager
  (including Ubuntu 12.04 LTS and Ubuntu 12.10-beta1).

  Steps to reproduce this bug.

  Required settings:

  1. Ubuntu with Compiz as window manager (e.g. Ubuntu with Unity, which
  is based on Compiz).

  2. Two or more input languages in the Keyboard Layout Settings (e.g.
  1st - English (US), 2nd - Russian).

  3. Keyboard Layout Settings:
  a) Allow different layouts for individual windows;
  b) New windows use the default layout.
  [Default layout is the first one in the layouts list, I think]

  *** Scenario 1

  1. Open Text Editor (gedit).
  2. Switch input language to Russian.
  3. Type some text in the gedit window in russian.
  4. Start Terminal (gnome-terminal).
  5. Type some text in the Terminal window (without keyboard layout switching).

  Expected behavior:
  Typed symbols in the terminal are English (because English was set as default 
input language in Keyboard Settings, and new windows should use the default 
layout).

  What actually happens:
  Typed symbols in the terminal are Russian (same input language as in the 
previous active window).

  *** Scenario 2

  1. Open Text Editor (gedit).
  2. Switch input language to Russian.
  3. Type some text in the gedit window in russian.
  4. Leave your computer with no activity for 10 minutes (wait for screen 
locking).
  5. Try to enter password in the logon screen (without keyboard layout 
switching).

  Expected behavior:
  Password is entered in English (because English was set as default input 
language in Keyboard Settings, and new windows should use the default layout).

  What actually happens:
  Password is entered in Russian (same input language as in the previous active 
window).

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

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


[Touch-packages] [Bug 1389273] Re: Track app sales per partner

2014-12-01 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/unity-scopes-shell

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

Title:
  Track app sales per partner

Status in Pay UI:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu RTM:
  Triaged

Bug description:
  We need to track what app sales come from which partner, by sending
  the partner string when performing a purchase.

  For documentation on what the server expects, see:
  https://wiki.ubuntu.com/AppStore/Interfaces/Purchases#purchases

  The code for each partner needs to be specified in the OEM image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pay-ui/+bug/1389273/+subscriptions

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


[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep

2014-12-01 Thread Christopher M. Penalver
Michael Neuffer, could you please boot into the kernel that comes with
Ubuntu by default (i.e. not 3.11.x) and execute the following in a
terminal as it will automatically gather and attach updated debug
information to this report:

apport-collect -p xorg 1268151

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** No longer affects: xserver-xorg-video-nouveau (Ubuntu)

** No longer affects: nvidia-graphics-drivers-331-updates (Ubuntu)

** No longer affects: nvidia-graphics-drivers-331 (Ubuntu)

** No longer affects: xorg (Ubuntu)

** Project changed: oem-priority = xorg (Ubuntu)

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

** No longer affects: xorg (Ubuntu)

** Project changed: hwe-next = xorg (Ubuntu)

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

** No longer affects: xorg (Ubuntu)

** Project changed: dell = xorg (Ubuntu)

** No longer affects: xorg (Ubuntu)

** Project changed: nouveau = xorg (Ubuntu)

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

** Changed in: xorg (Ubuntu)
 Remote watch: LibreOffice Bugzilla #85459 = None

** No longer affects: xorg (Ubuntu)

** Project changed: xorg-server = xorg (Ubuntu)

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

** Changed in: xorg (Ubuntu)
 Remote watch: freedesktop.org Bugzilla #85459 = None

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

** Description changed:

- Also affects nvidia-graphics-drivers-319
+ With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and 
either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the 
display shuts off, it will not wake up anymore, and the screen stays dark. A 
cycle of the following will leave the display dark:
+ xset dpms force off; sleep 30; xset dpms force on
  
- The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
- but with Nvidia instead of AMD/ATI drivers.
+ WORKAROUND: A restart of the Xserver will bring back the display.
  
- HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
- display
+ WORKAROUND: Don't allow DPMS to switch off the display:
+ xset dpms 0 0 0
  
- Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
- Only a restart of the Xserver will bring back the display at that point.
- 
- A cycle of
- xset dpms force off; sleep 30; xset dpms force on
- will leave the display dark.
- 
- At the moment I help myself by not allowing DPMS to switch off the display:
- neuffer@charion:~$ xset dpms 0 0 0
- 
- neuffer@charion:~$ xset -q -d :0.0
+ xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Dell M4800] DPMS support broken, fails to wake up the monitor after
  putting it to sleep

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and 

[Touch-packages] [Bug 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

2014-12-01 Thread Bruno Nova
Also affected in 14.04. This bug should be of high importance.
This bug was fixed in Debian in version 1.1~exp4, but the version in sid is 
1.0.9.3, so I think we will have to wait bit yet.

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg.

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 
ftpmas...@ubuntu.com
  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 
ftpmas...@ubuntu.com

  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: Ubuntu Archive Automatic Signing Key 
ftpmas...@ubuntu.com not changed
  gpg: key FBB75451: Ubuntu CD Image Automatic Signing Key 
cdim...@ubuntu.com not changed
  gpg: key C0B21F32: Ubuntu Archive Automatic Signing Key (2012) 
ftpmas...@ubuntu.com not changed
  gpg: key EFE21092: Ubuntu CD Image Automatic Signing Key (2012) 
cdim...@ubuntu.com not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the resource limit message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

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

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


[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated

2014-12-01 Thread Michał Sawicz
Alberto, can you please confirm if the above is good enough for you for
now? And if not, please describe what other use case this lacks support
for?

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

Title:
  Splash screen is shown as soon as QGuiApplication is instantiated

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu RTM:
  Confirmed

Bug description:
  On the phone, a splash screen is shown as soon as QGuiApplication is 
instantiated; however, a QWindow might be created much later, or not be created 
at all.
  We have for example a D-Bus service (ubuntu-system-settings-online-accounts) 
which is a QGuiApplication, but creates QWindows only as client requests 
arrive. In the common case, this works fine because the service is generally 
started when a window needs to be displayed, but we are now preparing for 
implementing trust session support, and that would require either this bug to 
be fixed, or a deeper refactoring of our code.

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

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


[Touch-packages] [Bug 1368670] Re: [Dash] Simplify 'Manage Dash' area

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Importance: Critical = High

** Changed in: unity8 (Ubuntu RTM)
   Status: In Progress = Triaged

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Albert Astals Cid (aacid) = (unassigned)

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

Title:
  [Dash] Simplify 'Manage Dash' area

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity-scope-mediascanner package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity-scope-mediascanner source package in Utopic:
  Confirmed
Status in unity-scopes-shell source package in Utopic:
  Confirmed
Status in unity8 source package in Utopic:
  Confirmed
Status in unity-scopes-shell package in Ubuntu RTM:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  UX Testing Report: Replace the current bottom edge screens with the
  simpler Complete list of Scopes design.

  New Manage Dash design can be found here:
  
https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure

  Additional UX Testing Report findings addressed by the redesign:

  Poor discoverability and comprehension of scopes - The use of
  labelings that do not include the word 'scope'/'scopes'

  Lack of visual distinctions between apps and scopes in the 'manage
  dash' screen

  Undefined relationship between apps and scopes

  Search function does not help the discovery of scopes

  No dedicated place for adding scopes on the dash

  Poor memorability in locating the' manage dash' screen again

  The impact of making a scope favourite is unclear

  Lack of indication of the nature of the scopes under 'all' tab on
  'manage dash'

  Navigation between manage dash and apps scope was difficult

  Expect to see categorises instead of content


  ---
  [EDIT]
  Please refer to the Dash  Feeds RTM usability fix for this bug:
  
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing

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

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


[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated

2014-12-01 Thread Michał Sawicz
I believe that as far as trust prompts go, we've resolved that they
should ultimately never talk to the default Mir socket, which is the
only case when they get a splash screen. The backends should open a
trust session, even if it's not going to create any UI in the end (that
is, if they require a Mir connection to function, as is the case for
Oxide). Until we have the headless-client hints implemented on surfaces,
you can open the trusted session with dash's PID or whatever else makes
sense.

Jury's still out on whether we want to disable splash screens for some
apps, but that is more of a UX question than a technical one.

Another approach we might consider is dropping the --desktop_file_hint
hack (I believe OA is one of the last instances of it) and think of a
different way to allow trusted helpers in. We could also say that only
UAL-backed apps get splash screens.

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

Title:
  Splash screen is shown as soon as QGuiApplication is instantiated

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu RTM:
  Confirmed

Bug description:
  On the phone, a splash screen is shown as soon as QGuiApplication is 
instantiated; however, a QWindow might be created much later, or not be created 
at all.
  We have for example a D-Bus service (ubuntu-system-settings-online-accounts) 
which is a QGuiApplication, but creates QWindows only as client requests 
arrive. In the common case, this works fine because the service is generally 
started when a window needs to be displayed, but we are now preparing for 
implementing trust session support, and that would require either this bug to 
be fixed, or a deeper refactoring of our code.

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

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


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

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
 Assignee: Nick Dedekind (nick-dedekind) = (unassigned)

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  SMS notification: time format not translatable

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu Translations:
  Triaged
Status in telephony-service package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

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

  The time format needs to be marked for translation.

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

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

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


[Touch-packages] [Bug 1378126] Re: Passcode screen misses keypresses

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  Passcode screen misses keypresses

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

Bug description:
  For some reason the passcode entry screen / lock screen feels very
  laggy when entering my passcode.

  It frequently misses my keypresses, so i end up typing insufficient
  characters. I don't know if the hit area for the numbers is too small
  and I'm mis-hitting or if there is a lag/delay. I'm not typing
  stupendously fast, but pretty quick. Any slower and it feels very
  deliberate, like I'm typing a PIN into an ATM.

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

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


[Touch-packages] [Bug 1368680] Re: [design] [Dash] pagination graphic should remain static when swiping between favourites.

2014-12-01 Thread Michał Sawicz
Can't see this happening by r1 unless we get a better design solution
for this.

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

** Changed in: unity8 (Ubuntu RTM)
 Assignee: Michał Sawicz (saviq) = (unassigned)

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

** Changed in: unity8 (Ubuntu)
 Assignee: Michał Sawicz (saviq) = (unassigned)

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

Title:
  [design] [Dash] pagination graphic should remain static when swiping
  between favourites.

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  Pagination graphic should remain fixed in place when swiping between 
favourites contained within the dash.
  'Dot' used to communicate which favourite is currently being viewed should be 
more visible (switch colour from Dark Grey to Orange colour used for 
highlights, etc):

  See here for more info on dash pagination (page 10):
  
https://docs.google.com/a/canonical.com/document/d/1LsjdqKDVcFN8Zxb_Oe-Zk1X_DiqviXr8D7-ELt2LEFI/edit?usp=sharing

  
  UX Testing Report finding  recommendation:

  No incentive to discover scopes beyond the apps scope.  Lack of
  strong visual cues to hint swiping from the apps scope to discover
  more scopes on the right.

  In the SURU divider pagination pattern (as currently used by the
  Dash), change the selected colour from orange to white.

  When the Scopes slide, the SURU divider portion of the screen should
  not slide (it should remain static).  The state of the 'dot'
  pagination pattern should of course change. Keeping the SURU divider
  static should make the change to the pagination pattern more
  noticeable.

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

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


[Touch-packages] [Bug 1378417] Re: Icon clipping in notification-renderer

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  Icon clipping in notification-renderer

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

Bug description:
  Discussed with MacSlow in #unity-touch earlier today.

  When indicator-power requests a low battery notification, the low
  battery icon gets clipped.

  Here's what it looks like:

  http://i.imgur.com/69hqWlL.jpg

  Here's what is sent to unity-notifications:

  method call sender=:1.104 - dest=:1.55 serial=18 
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; 
member=Notify
 string indicator-power-service
 uint32 0
 string battery-020
 string Battery Low
 string 10% charge remaining
 array [
string dismiss
string OK
string settings
string Battery settings
 ]
 array [
dict entry(
   string x-canonical-non-shaped-icon
   variant string true
)
dict entry(
   string x-canonical-snap-decisions
   variant string true
)
dict entry(
   string x-canonical-snap-decisions-timeout
   variant int32 2147483647
)
 ]
 int32 0

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

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


[Touch-packages] [Bug 1395075] Re: [Security] Can easily bypass pincode

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
   Status: Confirmed = Triaged

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

Title:
  [Security] Can easily bypass pincode

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  rtm image 166

  1. reboot the phone
  2. As soon as the greeter is show, try to swipe it away.

  What happens:
  In some attempts we don't see the pincode screen rather 'Scopes' is seen with 
a spinner and there you are unlocked.

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

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


[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu RTM)
 Assignee: Josh Arenson (josharenson) = (unassigned)

** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1

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

Title:
  It's too easy to trigger a volume notification when taking a
  screenshot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  On Mako, I'm unable to take a screenshot (Vol up + Vol down) without
  changing the volume, which would be fine if there wasn't a
  notification appearing on the screenshot.

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

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


[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package qtbase-opensource-src - 5.3.2+dfsg-
4ubuntu8

---
qtbase-opensource-src (5.3.2+dfsg-4ubuntu8) vivid; urgency=medium

  * Pick up one more DBus fix (LP: #1384776):
- debian/patches/Break-after-handling-the-read-write.patch

qtbase-opensource-src (5.3.2+dfsg-4ubuntu7) vivid; urgency=medium

  * Pick up upstream 5.3 branch DBus fixes (LP: #1384776)
- debian/patches/Always-lock-the-DBus-dispatcher-before-dbus_connecti.patch
- debian/patches/Partially-revert-Fix-a-deadlock-introduced-by-the-ra.patch
- debian/patches/QDBusConnection-Merge-the-dispatch-and-the-watch-and.patch
 -- Timo Jyrinki timo-jyri...@ubuntu.com   Thu, 27 Nov 2014 13:11:36 +

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in network-manager package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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


[Touch-packages] [Bug 1386709] Re: Queries to remote scopes don't include location data (even if the scope needs it)

2014-12-01 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Queries to remote scopes don't include location data (even if the
  scope needs it)

Status in the base for Ubuntu mobile products:
  New
Status in unity-scopes-api package in Ubuntu:
  Fix Released

Bug description:
  The query to weatherchannel is not including lat/long, even if the
  remote-scopes listing have the needs_location_data in true:
  https://pastebin.canonical.com/119512/

  The server try to guess user location using geo-ip, but it's not
  always as accurate as we need for a user service (it depends heavily
  on your IP being representative of where you really are, which may not
  be the case for hotel proxys, weird ISPs, etc).

  Plase, send user's latitude and longitude for the remote scopes that
  need this information.

  Thanks!

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

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


[Touch-packages] [Bug 1385360] Re: Change include guards to use #pragma once

2014-12-01 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Change include guards to use #pragma once

Status in unity-scopes-api package in Ubuntu:
  Fix Released

Bug description:
  We should do a pass over the code base and get rid of the old-style
  include guards, replacing them with #pragma once. That's a lot simpler
  and less error prone than having to remember to update the guard
  identifier every time copies a header to create a new one.

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

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


[Touch-packages] [Bug 1356409] Re: Confined scopes are using the wrong path for the writable directory

2014-12-01 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Confined scopes are using the wrong path for the writable directory

Status in API for Unity scopes integration:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-api source package in Utopic:
  Fix Released

Bug description:
  Confined scopes are trying to use the wrong path for their writable
  data directory:

  Jan 1 20:24:13 ubuntu-phablet kernel: [ 203.538083]
  (1)[4915:scoperunner]type=1400 audit(1388607853.401:143):
  apparmor=DENIED operation=mkdir
  profile=com.ubuntu.scopes.youtube_youtube_1.0.7
  name=/home/phablet/.local/share/unity-scopes/leaf-
  net/com.ubuntu.scopes.youtube_youtube/ pid=4915 comm=scoperunner
  requested_mask=c denied_mask=c fsuid=32011 ouid=32011

  The runtime is trying to create the path:

  $HOME/.local/share/unity-scopes/leaf-net/$APP_PKGNAME_$APP_APPNAME
  ==
  $HOME/.local/share/unity-scopes/leaf-net/com.ubuntu.scopes.youtube_youtube

  which is not quite correct for confined scopes. They should actually
  be using:

  $HOME/.local/share/unity-scopes/leaf-net/$APP_PKGNAME
  ==
  $HOME/.local/share/unity-scopes/leaf-net/com.ubuntu.scopes.youtube

  The scope ID is made of two components, the APP_PKGNAME and the
  APP_APPNAME. Therefore it should not be used to determine the writable
  path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scopes-api/+bug/1356409/+subscriptions

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


[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

2014-12-01 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: In Progress = Invalid

** Changed in: unity8 (Ubuntu RTM)
   Status: New = Invalid

** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) = (unassigned)

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

Title:
  Occasional hang in unity 8 dash on the phone

Status in network-manager package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu RTM:
  Invalid

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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


[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data

2014-12-01 Thread Michi Henning
** Changed in: unity-scopes-api (Ubuntu Vivid)
   Status: Fix Committed = Fix Released

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

Title:
  add directory allowing scopes and apps to share data

Status in the base for Ubuntu mobile products:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  In Progress
Status in click-reviewers-tools package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu source package in Utopic:
  In Progress
Status in unity-scopes-api source package in Utopic:
  New
Status in apparmor-easyprof-ubuntu source package in Vivid:
  In Progress
Status in click-reviewers-tools source package in Vivid:
  In Progress
Status in unity-scopes-api source package in Vivid:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
  Fix Released

Bug description:
  Summary says it all, just need to decide on the directory. I propose using 
this rule:
    # Allow scopes to share data with the app shipped in the same click
    owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
    owner @{HOME}/.local/share/@{APP_PKGNAME}/**  mrkl,

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

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


[Touch-packages] [Bug 1031736] Re: root password is typed to Dash as wrong place (focus issue)

2014-12-01 Thread Andrea Azzarone
Can you still reproduce the bug?

** Changed in: unity
   Status: Confirmed = Incomplete

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

** Changed in: unity-2d (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  root password is typed to Dash as wrong place (focus issue)

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete
Status in unity-2d package in Ubuntu:
  Incomplete

Bug description:
  Start Synaptic from Dash is asking the root password (it's natural
  behaviour) but the input box of Synaptic does not grab the focus it
  stays on Dash further. This way the root pasword is got typed into
  Dash. After re-opening Dash the root password is well visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity-2d 5.12.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
  Uname: Linux 3.2.0-27-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Wed Aug  1 13:34:53 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-2d
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 951929] Re: Unity launcher and Alt-Tab switcher missing entry for gnome-terminal

2014-12-01 Thread Andrea Azzarone
Can you still reproduce this bug?

** Changed in: unity
   Status: Confirmed = Incomplete

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

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

Title:
  Unity launcher and Alt-Tab switcher missing entry for gnome-terminal

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  edit: Updated title, its affecting more than gnome-terminal

  1) Description:   Ubuntu precise (development branch)
  Release:  12.04

  2) unity:
    Installed: 5.4.0-0ubuntu2

  3) Gnome-Terminal to show in list of programs to alt+tab to.

  4)  Alt+Tab consistently fails to show gnome-terminal for 'a while' (I
  hate to be vague, I can't figure out what suddenly triggers it to
  appear in the box).  See attached photograph of it occurring.

  I can make it happen at will:

  1) Cold boot into Ubuntu.
  2) Open gnome-terminal.
  3) Open Firefox.
  4) Press alt+tab.  alt+tab window only shows Desktop and Firefox.

  In attached screenshot, note that gnome-terminal has a highlighted
  background and arrow, indicating an instance of it running, as is
  Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sat Mar 10 14:50:09 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work

2014-12-01 Thread Andrea Azzarone
Super+space shortcut seems to work fine here now. Can you confirm?

** Changed in: unity
   Status: Triaged = Incomplete

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Triaged = Incomplete

** Changed in: unity (Ubuntu)
   Status: Triaged = Incomplete

** Changed in: hundredpapercuts
   Status: Triaged = Incomplete

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

Title:
  ibus' Super+Space shortcut (usually) doesn't work

Status in One Hundred Papercuts:
  Incomplete
Status in Unity:
  Incomplete
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  1. Add the ubuntu-desktop PPA on Ubuntu 13.10 Saucy
  sudo add-apt-repository ppa:ubuntu-desktop/ppa
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get install indicator-keyboard
  2. Log out and log back in.
  2. Open System SettingsRegion  Language
  3. Switch to the Text Entry tab.
  4. Click the + button to add at least two more keyboard layouts.
  5. Log out and log back in.
  6. Try to use the (new) default Super+Space keyboard shortcut to switch 
between keyboard layouts.

  What happens
  ---
  Usually, Super+Space is ignored. It worked for me once on login but every 
other time I tested it didn't work.
  It works fine in GNOME Shell but not in Unity.

  gsettings reset org.gnome.settings-daemon.plugins.media-keys 
switch-input-source
  seems to be enough to nudge Unity into respecting the Super+Space keyboard 
shortcut.

  My guess is that Unity is too aggressive in binding the Super key to
  itself.

  Workaround
  -
  Shift+Super+Space, the keyboard shortcut to switch backward between keyboard 
layouts works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jul 16 00:28:27 2013
  InstallationDate: Installed on 2013-06-14 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 962581] Re: compiz crashed with SIGSEGV in empty() from check_selection() [unity-rvgrid-accessible.cpp:171]

2014-12-01 Thread Andrea Azzarone
Should be fixed in most recent unity releases.

** Changed in: unity
   Status: Confirmed = Fix Released

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

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

Title:
  compiz crashed with SIGSEGV in empty() from check_selection() [unity-
  rvgrid-accessible.cpp:171]

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Confirmed
Status in Unity 6.0 series:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  on update today

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.6.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 22 14:41:58 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120201)
  ProcCmdline: compiz
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  Title: compiz crashed with SIGSEGV in g_main_context_dispatch()
  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/unity/+bug/962581/+subscriptions

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


[Touch-packages] [Bug 1397960] [NEW] Ship library in /lib, not /usr

2014-12-01 Thread Martin Pitt
Public bug reported:

In bug 1396270 we enabled AppArmor support in systemd. However, that
breaks on machines where /usr is on a separate partition, so we must
move libapparmor1 from /usr to the root partition.

** Affects: apparmor (Ubuntu)
 Importance: High
 Assignee: Martin Pitt (pitti)
 Status: Triaged

** Affects: apparmor (Ubuntu Vivid)
 Importance: High
 Assignee: Martin Pitt (pitti)
 Status: Triaged

** Affects: apparmor (Debian)
 Importance: Unknown
 Status: Unknown

** Also affects: apparmor (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Bug watch added: Debian Bug tracker #771667
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771667

** Also affects: apparmor (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771667
   Importance: Unknown
   Status: Unknown

** Changed in: apparmor (Ubuntu Vivid)
   Status: New = Triaged

** Changed in: apparmor (Ubuntu Vivid)
   Importance: Undecided = High

** Changed in: apparmor (Ubuntu Vivid)
 Assignee: (unassigned) = Martin Pitt (pitti)

** Changed in: apparmor (Ubuntu Vivid)
Milestone: None = ubuntu-14.12

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

Title:
  Ship library in /lib, not /usr

Status in apparmor package in Ubuntu:
  Triaged
Status in apparmor source package in Vivid:
  Triaged
Status in apparmor package in Debian:
  Unknown

Bug description:
  In bug 1396270 we enabled AppArmor support in systemd. However, that
  breaks on machines where /usr is on a separate partition, so we must
  move libapparmor1 from /usr to the root partition.

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

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


[Touch-packages] [Bug 934240] Re: Sometimes title bar doesn't integrate when maximising games.

2014-12-01 Thread Andrea Azzarone
Please reopen if you can still reproduce it on ubuntu 14.04+.

** Changed in: unity
   Status: New = Fix Released

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

Title:
  Sometimes title bar doesn't integrate when maximising games.

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When maximising windowed OpenGL games... usually the window title
  bar integrates with the top-bar as expected, but sometimes it does
  not.  After it fails once, this is repeatable.

  Tested in 12.04 Alpha1 + patches to 16/2/2012

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

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


[Touch-packages] [Bug 1310943] Re: Unable to load icon file:/// at size -1x22

2014-12-01 Thread Andrea Azzarone
Can you still see this warning?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Unable to load icon file:/// at size -1x22

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  This is merely a warning shown when the dash is first opened, but
  there's probably a bug here somewhere.

  unity.iconloader IconLoader.cpp:755 Unable to load icon file:/// at
  size -1x22: Can't open directory

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

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


[Touch-packages] [Bug 1372590] Re: Update header divider

2014-12-01 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Update header divider

Status in Ubuntu UX bugs:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Use color: 5% black instead of the current image.

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

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


[Touch-packages] [Bug 1076069] Re: show Lens name into panel

2014-12-01 Thread Andrea Azzarone
** Changed in: unity
   Status: Triaged = Incomplete

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

** Tags added: needs-design

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

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

Title:
  show Lens name into panel

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  in my opinion when Lens X is selected into Dash, its name X should be 
displayed into panel.
  As implemented at the time of this writing, the name (Home/Applications/..) 
should appear at the right of Dash buttons.
  This would allow a clear classification of the space where you're in.
  If my previous bug about auto-hiding Dash Clo/Min/Max buttons was 
implemented, Lens title should appear at top-left screen corner, and disappear 
on mouse pointer overlay in favour of Clo/Min/Max Dash Buttons.
  In this way panel in Dash overlay would behave the same as when working for 
standard apps.

  Thanks for your attention,
  alex

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

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


[Touch-packages] [Bug 1397963] [NEW] SIM PIN and passcode screens too similar

2014-12-01 Thread Michał Sawicz
Public bug reported:

The SIM PIN and lockscreen dialogs for passcode are too similar to one
another, I repeatedly end up putting my passcode as SIM PIN, this could
lead to locking your SIM card.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity8 8.01+15.04.20141125.2-0ubuntu1
Uname: Linux 3.18.0-031800rc4-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec  1 12:28:06 2014
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug vivid

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

Title:
  SIM PIN and passcode screens too similar

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

Bug description:
  The SIM PIN and lockscreen dialogs for passcode are too similar to one
  another, I repeatedly end up putting my passcode as SIM PIN, this
  could lead to locking your SIM card.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.01+15.04.20141125.2-0ubuntu1
  Uname: Linux 3.18.0-031800rc4-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 12:28:06 2014
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1007501] Re: Applications fail to open

2014-12-01 Thread Andrea Azzarone
** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Applications fail to open

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Dash is not responding to open applications

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dash 0.5.7-2ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Fri Jun  1 21:26:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 971805] Re: Unity isn't responsive(?)

2014-12-01 Thread Andrea Azzarone
** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Unity isn't responsive(?)

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I test Ubuntu 12.04 and installed the latest updates. Several problems
  appear, which could relate to each other:

  - the Dash doesn't blur its background, though it is set in ccsm
  - radiotray in the panel doesn't react on scrolling with the mousewheel 
anymore to change the volume
  - under attached devices in indicator-session no update appears when 
plugging in the webcam or scanner

  I don't know how to research this exactly ... Possibly it's related to
  Unity??

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

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


[Touch-packages] [Bug 1330410] Re: All keyboard types in Keyboard layout are not localized during installation

2014-12-01 Thread Jonathan Riddell
I removed using the translated names for keyboard layouts from the Qt
frontend as it was causing crashes.  The GTK frontend has never
translated them.

Patches to add this feature in would be welcome but it needs to be well
tested to make sure none of the crashes come back.

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

Title:
  All keyboard types in Keyboard layout are not localized during
  installation

Status in Ubuntu Kylin:
  Triaged
Status in console-setup package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  系统:UK 14.10 dailybuild 32 位 6-15
  机器型号:vritualbox 
  现象: 安装过程中键盘布局页面所有的键盘布局类型没有汉化

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

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


[Touch-packages] [Bug 1352251] Re: Splash screen is shown as soon as QGuiApplication is instantiated

2014-12-01 Thread Alberto Mardegan
Yes, this is not really blocking me; until the headless-client hints are
implemented I can just play safe and simply return an error on all UI
requests.

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

Title:
  Splash screen is shown as soon as QGuiApplication is instantiated

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Qt integration with the Mir display server:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu RTM:
  Confirmed

Bug description:
  On the phone, a splash screen is shown as soon as QGuiApplication is 
instantiated; however, a QWindow might be created much later, or not be created 
at all.
  We have for example a D-Bus service (ubuntu-system-settings-online-accounts) 
which is a QGuiApplication, but creates QWindows only as client requests 
arrive. In the common case, this works fine because the service is generally 
started when a window needs to be displayed, but we are now preparing for 
implementing trust session support, and that would require either this bug to 
be fixed, or a deeper refactoring of our code.

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

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


[Touch-packages] [Bug 856520] Re: Make the Alt-tab explode timer count from when the frame was dislayed, not when it happened

2014-12-01 Thread Andrea Azzarone
Alt-tab is faster in most recent unity versions. Please reopen it if you
can still reproduce the bug.

** Changed in: ayatana-design
   Status: New = Incomplete

** Changed in: unity
   Status: New = Invalid

** Changed in: ayatana-design
   Status: Incomplete = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Make the Alt-tab explode timer count from when the frame was dislayed,
  not when it happened

Status in Ayatana Design:
  Invalid
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  In the alt-tab switcher the latency of the Alt-tab switcher frame rate
  gets quite close to the Alt-tab expanding exploder time out.

  This means that if you wait until to see which icons is actually
  highlighted that icon could have exploded into a set of window
  previews by the time it the seen has seen it.

  Ideally the exploder timer should be tied to the point at which the
  frame was displayed.  This can be approximated by adding on the
  current inverse of the current framerate.  This would mean that the
  user always has a consistent and predictable reaction time ceiling,
  rather than having to keep alt-tabbing ahead just to stop the window
  display exploding on the off-chance that the current FPS is low.

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

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


[Touch-packages] [Bug 906472] Re: Emoticons not shown on global menu

2014-12-01 Thread Andrea Azzarone
Pretty sure it's not a unity bug. Please install and use gnome-classic
sessions and try to reproduce the bug.

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  Emoticons not shown on global menu

Status in Unity:
  Incomplete
Status in Unity GTK+ module:
  New
Status in empathy package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Incomplete
Status in unity-gtk-module package in Ubuntu:
  Confirmed

Bug description:
  Whilst focused on a conversation window, going to Conversation 
  Insert smiley in the global menu, will display a list of blank entires
  where there should be emoticons.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.2.0.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Mon Dec 19 18:39:11 2011
  ExecutablePath: /usr/lib/empathy/empathy-chat
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: empathy
  UpgradeStatus: Upgraded to oneiric on 2011-11-08 (41 days ago)

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

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


[Touch-packages] [Bug 926357] Re: Windows can be hidden on another workspace

2014-12-01 Thread Andrea Azzarone
** Changed in: compiz
   Status: New = Confirmed

** Changed in: unity
   Status: New = Confirmed

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

** Changed in: compiz
   Importance: Undecided = Medium

** Changed in: unity
   Importance: Undecided = Medium

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

Title:
  Windows can be hidden on another workspace

Status in Compiz:
  Confirmed
Status in One Hundred Papercuts:
  Invalid
Status in Unity:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  What happens:
  A window can be moved so that just a part of its lower edge is below the 
bottom boundary of the current workspace (workspace 1). If I later swicth to 
the workspace below (workspace 2), the window is registered as being on that 
workspace -- even though the lower edge of the window is hidden by the top 
panel of workspace 2. This means I can't activate the window by clicking its 
icon in the Dash; I will have to switch back to workspace 1 before I can 
interact with the window again. (see attached screenshot)

  This is a minor annoyance if you are familiar with workspaces. If you,
  however, accidentally switch workspace this can be really bad, since
  you do not know how to go back, and the application window will just
  appear to be gone even though it is still running. The only way for
  such a user to get back to the application is to restart it, losing
  potential work in the process.

  Expected behavior:
  Clicking the icon of a running applicaiton in the Dash should bring you to 
the workspace/viewport were it occupies the biggest part of the screen. This 
way, an application window cannot accidentally disappear.

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

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


[Touch-packages] [Bug 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset

2014-12-01 Thread Oliver Woodford
I tried the release you asked me to (12.04.0) and it exhibits the same
problem. The VGA output works fine when the monitor is plugged in at
boot up, but not if plugged in after booting.

By the way, I didn't state this before, but the VGA output worked fine
under Windows, even when plugged in after booting.

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

Title:
  [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45
  chipset

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege
  R600-10Q laptop (a model from 2009). I am now trying to display the
  desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's
  not working - the monitor says No Signal Detected!.

  What I've done:
  I have gone into Screen Display, where I can see the monitor is detected by 
the laptop.
  The monitor has a 1920 x 1080 native resolution, which I have tried to use, 
but I have also set it to lower resolutions, e.g. 1024 x 576.
  I have tried to use the monitor in dual screen, mirrored and single screen 
mode - none work.
  I have tried pressing Fn + F5 to get single screen output - the laptop screen 
goes blank, but still no output on the monitor.
  I have tried several monitors (of the same type, and also of a different 
make), so I don't think it's that.

  If I plug the vga cable in after boot up, then the monitor receives no
  signal.

  WORKAROUND: If, and only if, the monitor was plugged in to the PC's
  VGA output during boot up, then the display outputs to the monitor
  correctly.

  The laptop has the Intel® GS45 Express chipset for graphics acceleration. I 
installed mesa-utils and ran glxinfo in a terminal. Amongst the output was:
  OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset

  Also, in the About This Computer window I see:
  Graphics: Mobile Intel® GM45 Express Chipset

  I wonder if the problem is that my chipset is GS45 not GM45.

  The output of sudo lshw -C video is:
  *-display:0
  description: VGA compatible controller
  product: Mobile 4 Series Chipset Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  version: 07
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom
  configuration: driver=i915 latency=0
  resources: irq:44 memory:ff40-ff7f memory:e000-efff 
ioport:cff8(size=8)
  *-display:1 UNCLAIMED
  description: Display controller
  product: Mobile 4 Series Chipset Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2.1
  bus info: pci@:00:02.1
  version: 07
  width: 64 bits
  clock: 33MHz
  capabilities: pm bus_master cap_list
  configuration: latency=0
  resources: memory:ffc0-ffcf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Sep  2 10:00:57 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:000c]
     Subsystem: Toshiba America Info Systems Device [1179:000c]
  InstallationDate: Installed on 2014-08-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: TOSHIBA PORTEGE R600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R600
  dmi.product.version: PPR61E-00Q00CEN
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: 

[Touch-packages] [Bug 1397979] [NEW] UITK fails to build with Qt 5.4.0: launcher.cpp:70:5: error: 'setGlobalShareContext' is not a member of 'QOpenGLContextPrivate'

2014-12-01 Thread Timo Jyrinki
Public bug reported:

launcher.cpp:70:5: error: 'setGlobalShareContext' is not a member of
'QOpenGLContextPrivate' as seen in the build log:
https://launchpadlibrarian.net/191603952/buildlog_ubuntu-vivid-i386
.ubuntu-ui-
toolkit_1.1.1347%2B15.04.20141126-0ubuntu2~rc~test2_FAILEDTOBUILD.txt.gz
All archs: https://launchpad.net/~canonical-
qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4596263/+listing-
archive-extra

More information about Qt testing at
https://wiki.ubuntu.com/Touch/QtTesting

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt5.4

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

Title:
  UITK fails to build with Qt 5.4.0: launcher.cpp:70:5: error:
  'setGlobalShareContext' is not a member of 'QOpenGLContextPrivate'

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

Bug description:
  launcher.cpp:70:5: error: 'setGlobalShareContext' is not a member of
  'QOpenGLContextPrivate' as seen in the build log:
  https://launchpadlibrarian.net/191603952/buildlog_ubuntu-vivid-i386
  .ubuntu-ui-
  toolkit_1.1.1347%2B15.04.20141126-0ubuntu2~rc~test2_FAILEDTOBUILD.txt.gz
  All archs: https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4596263/+listing-
  archive-extra

  More information about Qt testing at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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


[Touch-packages] [Bug 1397960] Re: Ship library in /lib, not /usr

2014-12-01 Thread Jamie Strandboge
** Tags added: aa-systemd

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

Title:
  Ship library in /lib, not /usr

Status in apparmor package in Ubuntu:
  Triaged
Status in apparmor source package in Vivid:
  Triaged
Status in apparmor package in Debian:
  New

Bug description:
  In bug 1396270 we enabled AppArmor support in systemd. However, that
  breaks on machines where /usr is on a separate partition, so we must
  move libapparmor1 from /usr to the root partition.

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

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


[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

2014-12-01 Thread WHK
me@machine:~/Escritorio$ patch -p1  
0001-upowerd-Fix-cleanup-in-up_device_idevice_coldplug-fi.patch
[sudo] password for whk: 
can't find file to patch at input line 20
Perhaps you used the wrong -p or --strip option?

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 service_client_free+25:   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source (%esi) (0x302e) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

2014-12-01 Thread AndreK
please tell how tp properly install this upgraded package on 14.10.
(I doubt adding repositories for vivid is a good idea)

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t type to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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


[Touch-packages] [Bug 926357] Re: Windows can be hidden on another workspace

2014-12-01 Thread Andrea Azzarone
** Changed in: compiz (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: compiz
   Status: Confirmed = Invalid

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

Title:
  Windows can be hidden on another workspace

Status in Compiz:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in Unity:
  Confirmed
Status in compiz package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  What happens:
  A window can be moved so that just a part of its lower edge is below the 
bottom boundary of the current workspace (workspace 1). If I later swicth to 
the workspace below (workspace 2), the window is registered as being on that 
workspace -- even though the lower edge of the window is hidden by the top 
panel of workspace 2. This means I can't activate the window by clicking its 
icon in the Dash; I will have to switch back to workspace 1 before I can 
interact with the window again. (see attached screenshot)

  This is a minor annoyance if you are familiar with workspaces. If you,
  however, accidentally switch workspace this can be really bad, since
  you do not know how to go back, and the application window will just
  appear to be gone even though it is still running. The only way for
  such a user to get back to the application is to restart it, losing
  potential work in the process.

  Expected behavior:
  Clicking the icon of a running applicaiton in the Dash should bring you to 
the workspace/viewport were it occupies the biggest part of the screen. This 
way, an application window cannot accidentally disappear.

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

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


[Touch-packages] [Bug 1397983] [NEW] Slow Single Click Fails to Work

2014-12-01 Thread 2CV67
Public bug reported:

I already asked about this in Launchpad Question #256474, but with no
answer.

If I single-click on an Ubuntu Unity Launcher Tile, I expect that to
launch the application.

It only does so if I can click--release extremely rapidly (less than
one tenth of a second - who can measure?).

At my normal click--release timing, the action is interpreted as
click--hold, so the Tile just wobbles (preliminary to being moved
in/from the Launcher) and the application is NOT launched.

For personal reasons, I am not able to click--release any faster.
There must be many other people (older, handicapped, etc) in the same situation.

We need to be able to reset the threshold between click--release and 
click--hold to get satisfactory functionality with Unity.
In the same way everybody can already reset the timing for double-click to suit 
their equipment  physiology.

The same problem occurs with Window Menus in Unity (with Menus on
Windows) where a slowish single click fails to open the Menu  is
interpreted as a desire to move the Window.

For information, MS Windows 8.1 works perfectly for me, with the same
hardware...

Ubuntu 14.04.1

unity:   Installed: 7.2.2+14.04.20140714-0ubuntu1.1

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Dec  1 13:41:47 2014
InstallationDate: Installed on 2014-10-23 (38 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Slow Single Click Fails to Work

Status in unity package in Ubuntu:
  New

Bug description:
  I already asked about this in Launchpad Question #256474, but with no
  answer.

  If I single-click on an Ubuntu Unity Launcher Tile, I expect that to
  launch the application.

  It only does so if I can click--release extremely rapidly (less than
  one tenth of a second - who can measure?).

  At my normal click--release timing, the action is interpreted as
  click--hold, so the Tile just wobbles (preliminary to being moved
  in/from the Launcher) and the application is NOT launched.

  For personal reasons, I am not able to click--release any faster.
  There must be many other people (older, handicapped, etc) in the same 
situation.

  We need to be able to reset the threshold between click--release and 
click--hold to get satisfactory functionality with Unity.
  In the same way everybody can already reset the timing for double-click to 
suit their equipment  physiology.

  The same problem occurs with Window Menus in Unity (with Menus on
  Windows) where a slowish single click fails to open the Menu  is
  interpreted as a desire to move the Window.

  For information, MS Windows 8.1 works perfectly for me, with the same
  hardware...

  Ubuntu 14.04.1

  unity:   Installed: 7.2.2+14.04.20140714-0ubuntu1.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Dec  1 13:41:47 2014
  InstallationDate: Installed on 2014-10-23 (38 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1397960] Re: Ship library in /lib, not /usr

2014-12-01 Thread Bug Watch Updater
** Changed in: apparmor (Debian)
   Status: Unknown = New

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

Title:
  Ship library in /lib, not /usr

Status in apparmor package in Ubuntu:
  Triaged
Status in apparmor source package in Vivid:
  Triaged
Status in apparmor package in Debian:
  New

Bug description:
  In bug 1396270 we enabled AppArmor support in systemd. However, that
  breaks on machines where /usr is on a separate partition, so we must
  move libapparmor1 from /usr to the root partition.

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

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


[Touch-packages] [Bug 1372563] Re: Checkbox in ListItem missing haptic response

2014-12-01 Thread Christian Dywan
I'm told the design has changed, so that the CheckBox is *not* supposed
to activate at all unless you actually tap the CheckBox. Can this be
clarified? As this completely changes the solution to this bug.

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

Title:
  Checkbox in ListItem missing haptic response

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  utopic-proposed-krillin r40
  Ubuntu 14.10 r257

  1. Go to System Settings  Sound, a screen that contains both switches and 
checkboxes.
  2. Tap on a switch or checkbox.
  3. Tap on the label next to a switch or checkbox.

  What happens:
  2. Tapping on the switch or checkbox gives haptic feedback.
  3. Tapping on the label similarly toggles the control, but with no haptic 
feedback.

  What should happen: Tapping on the label behaves exactly the same as
  tapping on the control itself.

  One way of fixing this bug would be to add haptic feedback to the
  labels. Another would be to remove haptic feedback for taps altogether
  (bug 1267592).

  Code example:

  ListItem.Standard {
  control: CheckBox {
  objectName: callVibrate
  checked: true
  }
  text: i18n.tr(Vibrate when ringing)
  }

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

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


[Touch-packages] [Bug 1372563] Re: Checkbox in ListItem missing haptic response

2014-12-01 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/noImpliedControlClicking

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

Title:
  Checkbox in ListItem missing haptic response

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  utopic-proposed-krillin r40
  Ubuntu 14.10 r257

  1. Go to System Settings  Sound, a screen that contains both switches and 
checkboxes.
  2. Tap on a switch or checkbox.
  3. Tap on the label next to a switch or checkbox.

  What happens:
  2. Tapping on the switch or checkbox gives haptic feedback.
  3. Tapping on the label similarly toggles the control, but with no haptic 
feedback.

  What should happen: Tapping on the label behaves exactly the same as
  tapping on the control itself.

  One way of fixing this bug would be to add haptic feedback to the
  labels. Another would be to remove haptic feedback for taps altogether
  (bug 1267592).

  Code example:

  ListItem.Standard {
  control: CheckBox {
  objectName: callVibrate
  checked: true
  }
  text: i18n.tr(Vibrate when ringing)
  }

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

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


[Touch-packages] [Bug 927826] Re: When a folder bookmarked in Nautilus is deleted, it doesn't disappear in the Unity quicklist inmediatelly

2014-12-01 Thread Andrea Azzarone
** Changed in: nautilus (Ubuntu)
   Status: New = Invalid

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

** Changed in: nautilus (Ubuntu)
   Status: Invalid = Confirmed

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

Title:
  When a folder bookmarked in Nautilus is deleted, it doesn't disappear
  in the Unity quicklist inmediatelly

Status in Unity:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  When I delete a folder bookmarked in Nautilus, it still appears in the
  Unity quicklist inmediatelly, but disappears after a while. I don't
  know how long it takes to disappear ;).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
  Uname: Linux 3.2.0-12-generic-pae i686
  .tmp.unity.support.test.0:

  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  CasperVersion: 1.303
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,snap,vpswitch,wall,animation,expo,ezoom,fade,scale,unityshell,workarounds]
  CompositorRunning: compiz
  Date: Mon Feb  6 19:15:31 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2000]
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2000]
  LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120201.1)
  MachineType: Olidata Chile S.A. A1xIM0
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- debian-installer/language=es keyboard-configuration/layoutcode=latam
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.04
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A1xIM0
  dmi.board.vendor: Olidata Chile S.A.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Olidata Chile S.A.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.04:bd02/23/2010:svnOlidataChileS.A.:pnA1xIM0:pvrToBeFilledByO.E.M.:rvnOlidataChileS.A.:rnA1xIM0:rvrTobefilledbyO.E.M.:cvnOlidataChileS.A.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: A1xIM0
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata Chile S.A.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.3-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901-1ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Touch-packages] [Bug 928219] Re: When working with multiple workspaces, Launcher indicates that Texmaker has three instead of one opened windows

2014-12-01 Thread Andrea Azzarone
Can you still reproduce this bug?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  When working with multiple workspaces, Launcher indicates that
  Texmaker has three instead of one opened windows

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  How to reproduce:
  0. I am not exactly sure yet but generally
  1. launch texmaker on a workspace x
  2. work on workspace y
  3. wait for it to happen (it can take several minutes)

  How it looks like:
  see attached video (pay attention to the mouse pointer) - Texmaker has only 
one window opened, upon clicking its icon, the two additional arrows that are 
not supposed to be there disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,move,vpswitch,resize,imgpng,regex,wall,animation,expo,compiztoolbox,grid,winrules,place,gnomecompat,snap,workarounds,session,ezoom,staticswitcher,fade,scale,unityshell]
  Date: Tue Feb  7 13:40:18 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 934986] Re: update icon duplicates itself in the launch bar

2014-12-01 Thread Andrea Azzarone
Can you still reproduce this issues?

** Changed in: unity
   Status: New = Incomplete

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

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

Title:
  update icon duplicates itself in the launch bar

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I record the problem

  It's the first time i see this issue and yesterday i was in ubuntu
  11.10, but i'm format my pc today and i'm notice this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,animation,move,resize,vpswitch,workarounds,snap,mousepoll,grid,gnomecompat,place,imgpng,expo,wall,unitymtgrabhandles,ezoom,session,fade,scale,unityshell]
  Date: Sat Feb 18 12:54:43 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 937300] Re: Make maximised window button controls appear in line with left window margin, use space above launcher for launcher toggle switch

2014-12-01 Thread Andrea Azzarone
It's has already been largely discussed somewhere else (can't find where
now). Marking as invalid.

** Changed in: ayatana-design
   Status: New = Invalid

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  Make maximised window button controls appear in line with left window
  margin, use space above launcher for launcher toggle switch

Status in Ayatana Design:
  Invalid
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I apologise for the lengthy summary, this is the first bug I've ever opened 
here.
  And it is a bug IMHO, a design bug more precisely.

  When using maximised application windows, and with the launcher being
  set to permanently show, the button controls intentionally don't show
  in line with the left application window margin, but above the
  launcher. I've seen that especially novice users are confused by the
  window controls being placed strangely away from the window to which
  they're supposed to belong to (even more the bigger the launcher
  size).

  I understand that the devs want to have some coherence with the dash
  window controls being placed at the same spot (which now sport the
  same looks as the application window controls), but I think this only
  adds to confusion. Launcher and applications are just of a different
  kind.

  My proposal is to use the freed up space above the launcher for an
  auto-hide/permanent show launcher toggle switch. This could provide
  for a quick and intuitive way to pin or unpin the launcher to the
  desktop - most novice users wouldn't know that they can also find this
  functionality in the system settings, and it would even be handy for
  the more advanced when they need more screen width once in a time.

  Thank you.

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

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


[Touch-packages] [Bug 932688] Re: Unity 3D causes video apps to malfunction

2014-12-01 Thread Andrea Azzarone
Is this still an issue?

** Changed in: unity
   Status: New = Incomplete

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New = Incomplete

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

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

Title:
  Unity 3D causes video apps to malfunction

Status in Unity:
  Incomplete
Status in nvidia-graphics-drivers package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I am getting very weird behavior:
- starting XBMC results in XBMC maxing out one of my cores and the XBMC UI 
is unresponsive (updates once in several seconds, at best)
- if XBMC started normally, toggling fullscreen/window mode will make it 
exhibit the above behavior
- after toggling fullscreen/window the screen/window will sometime contain 
garbage
- TV-MAXE, uses VLC as backend, works normally while not in fullscreen. 
When I switch it to fullscreen I get a blank screen or a static video frame.
- totem works normally while not in fullscreen. When I switch it to 
fullscreen I get a blank screen or a static video frame (usually the video 
frame is in the top left corner, unresized, and the rest of the screen is 
blank).

  This has been happening from the start on Oneiric with unity and
  nvidia proprietary drivers from the stock versions up to unity 5.0.0
  and nvidia drivers 295.20.

  All these apps function properly under Gnome Shell and Unity 2D.
  I have run out of ideas on what I can do/try to be able to use Unity 3D and 
these apps together.

  I think there's a good chance this bug might be present in the current 
development version of unity in precise and would hate it if Precise would be 
released with this bug still present.
  --- 
  .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_64 Kernel Module  295.20  Mon Feb  6 21:07:30 
PST 2012
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,copytex,place,move,snap,commands,imgpng,regex,animation,vpswitch,mousepoll,wall,gnomecompat,workarounds,session,grid,resize,compiztoolbox,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  DistUpgraded: Log time: 2011-11-22 12:43:23.029973
  DistroCodename: oneiric
  DistroRelease: Ubuntu 11.10
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 295.20, 3.0.0-16-generic, x86_64: installed
   virtualbox, 4.1.2, 3.0.0-16-generic, x86_64: installed
  GraphicsCard:
   nVidia Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. Device [107d:209c]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: unity 5.0.0+bzr1879ubuntu0+622
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-16-generic 
root=UUID=bdd0f7f0-e92e-40fb-989d-7daec91beae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Tags:  oneiric running-unity oneiric running-unity oneiric running-unity 
ubuntu
  Uname: Linux 3.0.0-16-generic x86_64
  UnreportableReason: This is not a genuine Ubuntu package
  UpgradeStatus: Upgraded to oneiric on 2012-01-30 (15 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XorgConf:
   Section Device
Identifier  Default Device
Option  NoLogoTrue
   EndSection
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
  version.ia32-libs: ia32-libs 20090808ubuntu26
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  

[Touch-packages] [Bug 946527] Re: compiz crashed with SIGSEGV in operator nux::Property, int, float, int() (MouseOverTopScrollArea)

2014-12-01 Thread Andrea Azzarone
It's an old bug withoud duplicated. I think it's safe to close it.

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  compiz crashed with SIGSEGV in operator nux::Property, int, float,
  int() (MouseOverTopScrollArea)

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  couldn't click on dash icons

  run unity - reset from remote ssh session and received this error
  during reset procedure

  reset completed ok and icons on dash are now clickable

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 1.94-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Sun Mar  4 18:09:43 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301)
  ProcCmdline: compiz --replace
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb4798514 
_ZN5unity8launcher8Launcher22MouseOverTopScrollAreaEv+20: fildl  0x14(%eax)
   PC (0xb4798514) ok
   source 0x14(%eax) (0x0014) not located in a known VMA region (needed 
readable region)!
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   unity::launcher::Launcher::MouseOverTopScrollArea() () from 
/usr/lib/compiz/libunityshell.so
   unity::launcher::Launcher::OnScrollTimeout(void*) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in 
unity::launcher::Launcher::MouseOverTopScrollArea()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == 
NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed
   gnome-session[3092]: WARNING: Application 'compiz.desktop' killed by signal

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

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


  1   2   3   4   >