date:20140217

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1275379

Title:
  unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in “nux” package in Ubuntu:
  Confirmed

Bug description:
  This occured on VirtualBox.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nux-tools 4.0.3+13.10.20131011-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Feb  2 10:51:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/nux/unity_support_test
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2014-02-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/nux/unity_support_test
  ProcEnviron:
   LANGUAGE=ja
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic 
root=UUID=3059f971-387f-40ef-aa3c-259dd346cbb1 ro quiet splash vt.handoff=7
  Renderer: Software
  SegvAnalysis:
   Segfault happened at: 0x7f6342c2a414 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7f6342c2a414) ok
   source "0x10(%rdi)" (0x20d8) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nux
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so
   start_thread (arg=0x7f63404de700) at pthread_create.c:312
  Title: unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Sun Feb  2 10:51:12 2014
  xserver.configfile: default
  xserver.errors:
   AIGLX error: vboxvideo does not export required DRI extension
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu3
  xserver.video_driver: vboxvideo

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

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

[Dx-packages] [Bug 1271710] Re: doesn't list compiz/unity keybindings

** Branch linked: lp:ubuntu/trusty-proposed/compiz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1271710

Title:
  doesn't list compiz/unity keybindings

Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Invalid

Bug description:
  The unity-control-center keybinding dialog doesn't list things like
  the HUD control (seems like other sections are missing as well). Could
  it be that it's not looking in the right directory for those? (or do
  we need to migrate things shipping a custom .xml to install those in a
  new location?)

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

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

[Dx-packages] [Bug 1234624] Re: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key

** Branch linked: lp:ubuntu/trusty-proposed/compiz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1234624

Title:
  Spread - In the spread view, clicking on an empty space should perform
  the same action as pressing the ESC key

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  In the spread view, clicking on an empty space (e.g. anywhere that is
  not a window or the launcher) should perform the same action as
  pressing the ESC key and should exit the spread.

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

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

[Dx-packages] [Bug 1204664] Re: control+super+d works just the first time running Ubuntu Unity.

** Branch linked: lp:ubuntu/trusty-proposed/compiz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1204664

Title:
  control+super+d works just the first time running Ubuntu Unity.

Status in Compiz:
  Fix Committed
Status in Unity:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Raring:
  New

Bug description:
  Control+Super+D works just the first time cauisng 9/10 failures in AP.

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

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

[Dx-packages] [Bug 1233176] Re: Alarm notifications do not appear when an alarm is triggered

2014-02-17 Thread Péter Trombitás

what is going on with this? As I understand this bug actually means that
the user cannot set a very primitive alarm clock to wake them up in the
morning. I think this is almost as important as being able to receive
calls. When can we expect it to work?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1233176

Title:
  Alarm notifications do not appear when an alarm is triggered

Status in The Date and Time Indicator:
  In Progress
Status in Clock application for Ubuntu devices:
  Triaged
Status in URL Dispatcher:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Confirmed
Status in “url-dispatcher” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” source package in Saucy:
  Confirmed

Bug description:
  There is no indication when an alarm goes off. This should be done by
  the platform which opens the clock app when an alarm is triggered.

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

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

[Dx-packages] [Bug 1171314] Re: Window stacking order messed up for dialogs/overlays

** Branch linked: lp:ubuntu/trusty-proposed/compiz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1171314

Title:
  Window stacking order messed up for dialogs/overlays

Status in Compiz:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  I am seeing this bug where right click dialogs, menus, notifications
  etc are popping up behind other windows.  See the screenshot as an
  example.

  It mostly doesn't happen until I start Amarok, which is a QT app, but
  that doesn't always make it happen either.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/1'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.88  Wed Mar 27 14:26:46 
PDT 2013
   GCC version:  gcc version 4.7.3 (Ubuntu/Linaro 4.7.2-23ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,move,regex,animation,kdecompat,gnomecompat,mousepoll,put,mblur,wall,resize,vpswitch,workarounds,resizeinfo,place,imgpng,unitymtgrabhandles,snap,notification,session,expo,ezoom,staticswitcher,fade,scale,showdesktop,unityshell,opacify]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 22 15:52:33 2013
  DistUpgraded: 2013-04-04 18:29:02,697 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C77 [nForce 750a SLI] [10de:084d] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. M3N72-D mGPU [1043:82e8]
   NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 
[VGA controller])
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-18-generic 
root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to raring on 2013-04-04 (17 days ago)
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202
  dmi.board.name: M3N72-D
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.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.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Mon Apr 22 08:56:13 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.13.3-0ubuntu6

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

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

[Dx-packages] [Bug 992697] Re: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken

** Branch linked: lp:ubuntu/trusty-proposed/compiz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/992697

Title:
  Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window
  placement shortcuts are broken

Status in Autopilot:
  Fix Released
Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.10 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in “autopilot” package in Ubuntu:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  The "Ctrl + Alt + numpad 4" and "Ctrl + Alt + numpad 6" keyboard
  shortcuts are not working in 13.04.

  See bug #878820 for the full specification of the numpad window
  placement shortcuts. Quoting from this bug:

  "Ctrl-Alt-Numpad 4 - Place window on the left side of the screen in
  *semi-maximised* state (it is important that the window is actually
  semi-maximised, not just the same size and position as a semi-
  maximised window) Pressing a second time does nothing.

  Ctrl-Alt-Numpad 6 - Place window on the right side of the screen (it
  is important that the window is actually semi-maximised, not just the
  same size and position as a semi-maximised window). Pressing a second
  time does nothing."

  HOWTO:

  The solution we want here are additional shortcuts to semi-maximize
  windows vertically and move them to left/right half of the screen...

  The best way to achieve that:

  1. Remove the changing of the standard shortcuts by 
debian/patches/ubuntu-config.patch, so the original ones will work again.
  2. Add 2 quasi-duplicated shortcuts with the functions to semi-maximize 
windows vertically and move them to left/right half of the screen to Grid and 
make those functions use "Ctrl + Super + Cursor Left or Right" on Ubuntu.

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

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

[Dx-packages] [Bug 898870] Re: Grid placed window overlaps the adjacent viewport

** Branch linked: lp:ubuntu/trusty-proposed/compiz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/898870

Title:
  Grid placed window overlaps the adjacent viewport

Status in Compiz:
  Fix Released
Status in Compiz Grid Plugin:
  Triaged
Status in Compiz Main Plugins:
  Triaged
Status in Unity:
  Triaged
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz-plugins-main” package in Ubuntu:
  Triaged

Bug description:
  When using the grid plugin's "Put Right" method, the right edge of the
  window extends beyond the border between workspaces. When using Unity
  with "Hide Launcher" set to "Dodge Windows", the launcher hides when
  switching to the workspace to the right.

  The horizontal virtual desktop size must be 2 or more for the
  unexpected behavior to occur.

  "Put Left" works as expected.

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

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

[Dx-packages] [Bug 1281053] [NEW] Unity application panel does not appear with mirrored screens on Intel graphics

2014-02-17 Thread Amos Brocco

Public bug reported:


My setup


I'm using Ubuntu 13.10 on a HP TM2 with hybrid graphics (vga-
switcheroo):

- integrated card: 00:02.0 VGA compatible controller: Intel Corporation Core 
Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) 
- discrete card: 01:00.0 VGA compatible controller: Advanced Micro Devices, 
Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] (prog-if 00 [VGA 
controller])

Problem
===

I need to work using a mirrored screen setup, with an external screen
connected to VGA (resolution: 1024x768).

When using the integrated intel card the application/search panel does
not appear when I click on the launcher icon or press the keyboard
shortcut: there is just a slight shadow on the top left corner (see
attached screenshot). However, if I switch to the discrete card
(AMD/ATI) I have no problems at all (panel shows up in mirrored mode).

In non-mirrored mode the panel shows up using both cards and works
correctly on both screens.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 17 11:22:54 2014
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1486]
 Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU 
(Mobility Radeon HD 5450) [103c:1486]
InstallationDate: Installed on 2014-02-12 (4 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=6dc4e5fd-db39-4985-8a85-8db30961e8c5 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2011
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.20
dmi.chassis.asset.tag: CNU03739VM
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr058A21242A1120100:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.version: 058A21242A1120100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Mon Feb 17 11:20:41 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.5-1ubuntu2~saucy1
xserver.video_driver: radeon

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


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

** Attachment added: "Application panel not showing up"
   
https://bugs.launchpad.net/bugs/1281053/+attachment/3983776/+files/Schermata%20del%202014-02-17%2011%3A19%3A30.png

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281053

Title:
  Unity application panel does not appear with mirrored screens on Intel
  graphics

Status in “unity” package in Ubuntu:
  New

Bug description:
  
  My setup
  

  I'm using Ubuntu 13.10 on a HP TM2 with hybrid graphics (vga-
  switcheroo):

  - integrated card: 00:02.0 VGA compatible controller: Intel Corporation Core 
Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) 
  - discrete card: 01:00.0 VGA compatible cont

[Dx-packages] [Bug 1281058] [NEW] The system shutdowns when multiple accounts are open

2014-02-17 Thread Ara Pulido

Public bug reported:

Steps to reproduce:

1) Create a second account in the system
2) While the first account is open, open a session with the second one
3) Try to shutdown the system

Expected results:
The system logs out instead of shutting down (ideally with a warning on why it 
did that)

Actual results:
The system shutdowns and unsaved data on session1 is lost

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Feb 17 11:49:48 2014
InstallationDate: Installed on 2013-06-17 (244 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago)

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


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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281058

Title:
  The system shutdowns when multiple accounts are open

Status in “unity” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Feb 17 11:49:48 2014
  InstallationDate: Installed on 2013-06-17 (244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago)

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

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

[Dx-packages] [Bug 1278290] Re: package python-appindicator 12.10.0-0ubuntu1 failed to install/upgrade: ErrorMessage: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'éta

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libappindicator in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1278290

Title:
  package python-appindicator 12.10.0-0ubuntu1 failed to
  install/upgrade: ErrorMessage: le sous-processus nouveau script pre-
  removal a retourné une erreur de sortie d'état 1

Status in “libappindicator” package in Ubuntu:
  Confirmed

Bug description:
  upgrade 12.10 to 13.10

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: python-appindicator 12.10.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-45.68-generic 3.5.7.26
  Uname: Linux 3.5.0-45-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 10 07:30:04 2014
  DuplicateSignature: 
package:python-appindicator:12.10.0-0ubuntu1:ErrorMessage: le sous-processus 
nouveau script pre-removal a retourné une erreur de sortie d'état 1
  ErrorMessage: ErrorMessage: le sous-processus nouveau script pre-removal a 
retourné une erreur de sortie d'état 1
  MarkForUpload: True
  SourcePackage: libappindicator
  Title: package python-appindicator 12.10.0-0ubuntu1 failed to 
install/upgrade: ErrorMessage: le sous-processus nouveau script pre-removal a 
retourné une erreur de sortie d'état 1
  UpgradeStatus: Upgraded to saucy on 2014-02-10 (0 days ago)

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

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

[Dx-packages] [Bug 1281058] Re: The system shutdowns when multiple accounts are open

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281058

Title:
  The system shutdowns when multiple accounts are open

Status in “systemd” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Feb 17 11:49:48 2014
  InstallationDate: Installed on 2013-06-17 (244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago)

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

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

[Dx-packages] [Bug 1270800] Re: Losing text fields focus when changing keyboard's layout

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

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1270800

Title:
  Losing text fields focus when changing keyboard's layout

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Hello.
  There is a moment with changing keyboard's layout in 13.10 (and it was in 
12.10, but the focus was returning immediately so I could type in new language 
in the moment). I change it using Alt+Shift. While I'm pressing on theese 
buttons, the focus is left from any textfield (single lines, many lines). It 
causes some problems.
  The first is that focus doesn't return immediately, so sometimes if I type 
very fast, the first letters I typed after the changing will not be shown. The 
second is that some programs select all text in the box when the focus returned 
(for example Flash), so I need to put the caret in the right position. The 
third is sending useless in this situation onfocus events.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,regex,move,grid,snap,mousepoll,animation,imgpng,vpswitch,resize,place,compiztoolbox,unitymtgrabhandles,gnomecompat,firepaint,wall,expo,fade,workarounds,session,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg:
   [   43.768071] input: Logitech Unifying Device. Wireless PID:101a as 
/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0005/input/input14
   [   43.768389] logitech-djdevice 0003:046D:C52B.0006: input,hidraw3: USB HID 
v1.11 Mouse [Logitech Unifying Device. Wireless PID:101a] on 
usb-:00:14.0-3:1
  Date: Mon Jan 20 17:22:44 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.11.0-15-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:056a]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 7670M [1028:056a]
  InstallationDate: Installed on 2014-01-19 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Inspiron 5520
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=4804716b-af02-4e50-a9ad-429ab057c291 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0XWH1P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/18/2012:svnDellInc.:pnInspiron5520:pvrA06:rvnDellInc.:rn0XWH1P:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Jan 20 16:36:02 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8428 
   vendor AUO
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

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

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

[Dx-packages] [Bug 1274181] Re: notification-daemon crashed with signal 5 in g_source_remove()

2014-02-17 Thread Bucky Ball

Just filed bug report here. Happens to me when open the laptop lid from
suspend. Testing Ubuntu 14.04 LTS, xfce4 DE. Happens all the time.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notification-daemon in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1274181

Title:
  notification-daemon crashed with signal 5 in g_source_remove()

Status in “notification-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Just rebooted and logged into Gnome Flashback with Compiz and
  immediately got this error notification.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: notification-daemon 0.7.6-1
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Jan 29 11:37:58 2014
  ExecutablePath: /usr/lib/notification-daemon/notification-daemon
  InstallationDate: Installed on 2014-01-08 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
  ProcCmdline: /usr/lib/notification-daemon/notification-daemon
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: notification-daemon
  StacktraceTop:
   g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: notification-daemon crashed with signal 5 in g_source_remove()
  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/ubuntu/+source/notification-daemon/+bug/1274181/+subscriptions

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

[Dx-packages] [Bug 1281058] Re: The system shutdowns when multiple accounts are open

2014-02-17 Thread Thaddäus Tintenfisch

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281058

Title:
  The system shutdowns when multiple accounts are open

Status in “systemd” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Feb 17 11:49:48 2014
  InstallationDate: Installed on 2013-06-17 (244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago)

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

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

[Dx-packages] [Bug 1280077] Re: Text in the top panel is escaped while it's not needed

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1279904] Re: Launcher drag icon background flickers for a second after start dragging

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1277265] Re: Clicking a menu entry doesn't always show the drop down menu the first time

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1279499] Re: Input interactions in the Switcher has random behavior

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1274554] Re: Panel should show a dropdown menu if the menu entries doesn't fit in the available horizontal space

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1267888] Re: Using mouse scrollwheel on unfocused/inactive Launcher icons should not focus that app

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1267210] Re: Dash/Hud stealing focus from fullscreen windows

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1267902] Re: The unity-autopilot package should depend on mesa-utils

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1271710] Re: doesn't list compiz/unity keybindings

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1253740] Re: Active blur for Quicklists/Tooltips no longer working after committing performance updates to Unity

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1255241] Re: [regression] Clicking the Hud icon does not close the Hud

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1252760] Re: Alt-Tab arrow keys doesn't work when the switcher is opened when the dash is opened

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1274985] Re: Hud icon states are incorrect when displaying Hud on a monitor with no Launcher

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1263775] Re: Icon won't wiggle at defined intervals if it's been urgent before

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1227131] Re: Add suport for 3D points TypeID

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1244704] Re: Some test_hud tests fail on trusty desktop

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1206582] Re: [regression] pressing and holding the alt key in a GTK app does not show the menu bar

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1251275] Re: UnityScreen::nuxPrologue / UnityScreen::nuxEpilogue are unnecessary expensive

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1179210] Re: unity_low_gfx_mode + auto hide launcher causes visual artifacts

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1251777] Re: [regression] Semi-maximizing and then restoring the window does not return it to it's original place using Ctrl-Super-Left/Right

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1098419] Re: Panel should be right-clickable when window is maximised with global menu enabled

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1113008] Re: F10 or Alt+ opens the window menus within the window

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1175669] Re: fcitx often fails to work in dash with Unity

This bug was fixed in the package nux - 4.0.5+14.04.20140214-0ubuntu1

---
nux (4.0.5+14.04.20140214-0ubuntu1) trusty; urgency=low

  [ Brandon Schaefer ]
  * Add XIM preedit support
  * Bump version to 4.0.5
  * We need to check if the XIC client is synced up with the xevents
coming in. If someone changes the focus window and our XIC hasn't
been updated, we need to make sure we stay synced. Otherwise XIM
fails to work. (LP: #1175669)

  [ CI bot ]
  * Flush trunk to Ubuntu

  [ Chris Townsend ]
  * Need to add version 1.10 of lcov to the supported versions so the
Debian package build can succeed.

  [ Eleni Maria Stea ]
  * added virtual destructors where missing (fixing static analysis
errors).
  * small fixes based on clang errors and warnings.
  * fixed syntax error in macro.
  * minor fixes (static analyzer errors and warnings).

  [ Albert Astals ]
  * Kill declared but not implemented functions.

nux (4.0.4-0ubuntu1) UNRELEASED; urgency=low

  [ Sam Spilsbury ]
  * Bump version to 4.0.4.
 -- Ubuntu daily releaseFri, 14 Feb 2014 
23:11:31 +

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1175669

Title:
  fcitx often fails to work in dash with Unity

Status in Nux:
  Fix Committed
Status in Unity:
  Invalid
Status in “nux” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in “nux” source package in Saucy:
  New

Bug description:
  The input method "fcitx' is supposed to work with Unity dash in raring,but it 
is not working well.
  This happens *only* when I set the launcher to hide as default.
  When I press Super to open the dash and begin to type characters into dash or 
HUD display (by pressing left alt),sometimes I can activate the input method.In 
more cases,there aren't any response when pressing "ctrl+space".Sometimes I 
can't type anything into dash.

  I've asked a developer of fcitx ("csslayer") but he said he knew
  nothing about it.He said it could be a bug of unity and suggested me
  to report the bug here.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu May  2 23:51:07 2013
  InstallationDate: Installed on 2012-05-01 (365 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-04-03 (28 days ago)

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

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

[Dx-packages] [Bug 1170508] Re: Alt-Tab, shutdown dialog and shortcut overlay should not be transparent in Low GFX Mode

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1173219] Re: error building with GTK 3.9: gtk_widget_get_state is deprecated

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1080947] Re: damageScreen() in UnityScreen::nuxDamageCompiz() severely hurts Unity performance

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 961890] Re: Keyboard shortcuts - dash home does not minimize with ctrl-super-D

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 834777] Re: static blur does not show what was on the desktop before the dash opened

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 830709] Re: Keyboard shortcut - Unity should also use Super-L to lock screen by default

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 691817] Re: Framing around window decorations on windows and panel should be identical.

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 827537] Re: Decorations needs to support anti aliased rounded corners

This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1

---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low

  [ Sebastien Bacher ]
  * use unity-control-center by default.
  * lists keybinding in unity-control-center. (LP: #1271710)

  [ Brandon Schaefer ]
  * Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
  * Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
  * Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
  * Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
  * Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
  * Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
  * Add Pt to Px function to em converter.
  * Move EMConverter over to unity settings.
  * Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
  * Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.

  [ Marco Trevisan (Treviño) ]
  * Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
  * Convert compiz regions / rects to nux::Geometry's and back easily.
  * UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
  * Unity: always prefer passing [this] to lambdas than [&].
  * Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
  * DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
  * BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
  * SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic

[Dx-packages] [Bug 1281081] Re: unity-scope-loader crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281081

Title:
  unity-scope-loader crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in “libunity” package in Ubuntu:
  New

Bug description:
  Trying Unity8

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 13:13:50 2014
  ExecutablePath: /usr/bin/unity-scope-loader
  InstallationDate: Installed on 2014-02-14 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
  ProcCmdline: /usr/bin/unity-scope-loader music/mediascanner.scope 
video/mediascanner.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  Signal: 6
  SourcePackage: libunity
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   unity_scope_module_load_scopes () from 
/usr/lib/x86_64-linux-gnu/unity/unity-scope-mediascanner.so
  Title: unity-scope-loader crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  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/ubuntu/+source/libunity/+bug/1281081/+subscriptions

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

[Dx-packages] [Bug 1281053] Re: Unity application panel does not appear with mirrored screens on Intel graphics

2014-02-17 Thread Amos Brocco

I found out that if this problem only happens if, prior to setting
screens in mirrored mode,  the panel is moved on the external screen,
i.e

1. Connect external screen
2. In the display configuration tool enable screen and move unity panel to 
external screen
3. Select mirrored screen
4. Bug: application panel does not appear when icon is clicked

but

1. Connect external screen
2. In the display configuration tool ensure that the panel is on the laptop 
screen
3. Select mirrored screen
4. Ok, application panel appears

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281053

Title:
  Unity application panel does not appear with mirrored screens on Intel
  graphics

Status in “unity” package in Ubuntu:
  New

Bug description:
  
  My setup
  

  I'm using Ubuntu 13.10 on a HP TM2 with hybrid graphics (vga-
  switcheroo):

  - integrated card: 00:02.0 VGA compatible controller: Intel Corporation Core 
Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) 
  - discrete card: 01:00.0 VGA compatible controller: Advanced Micro Devices, 
Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] (prog-if 00 [VGA 
controller])

  Problem
  ===

  I need to work using a mirrored screen setup, with an external screen
  connected to VGA (resolution: 1024x768).

  When using the integrated intel card the application/search panel does
  not appear when I click on the launcher icon or press the keyboard
  shortcut: there is just a slight shadow on the top left corner (see
  attached screenshot). However, if I switch to the discrete card
  (AMD/ATI) I have no problems at all (panel shows up in mirrored mode).

  In non-mirrored mode the panel shows up using both cards and works
  correctly on both screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 17 11:22:54 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1486]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU 
(Mobility Radeon HD 5450) [103c:1486]
  InstallationDate: Installed on 2014-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=6dc4e5fd-db39-4985-8a85-8db30961e8c5 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.20
  dmi.chassis.asset.tag: CNU03739VM
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr058A21242A1120100:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 058A21242A1120100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Feb 17 11:20:41 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2~saucy1
  xs

[Dx-packages] [Bug 1276225] Re: Heavy CPU usage when sublimetext is opened

2014-02-17 Thread Treviño

Unfortunately the loop persists... http://pastebin.ubuntu.com/6948712/

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1276225

Title:
  Heavy CPU usage when sublimetext is opened

Status in Unity HUD:
  Confirmed
Status in “hud” package in Ubuntu:
  Fix Released

Bug description:
  It looks to be triggered by sublimetext:
  http://www.sublimetext.com/2

  The suspended stack:
  http://pastebin.ubuntu.com/6873661/

  This is the HUD log file:
  http://paste.ubuntu.com/6873710/

  This is the list of apps running:
  http://paste.ubuntu.com/6873719/

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

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

[Dx-packages] [Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher

as a result of this change, mouse wheel on other launcher icons does
nothing useful at all and mouse wheel on the focussed app icon switches
windows in a different way, it certainly isn't reverse-able like it was,
it is deterministic, but I am struggling to describe the rule, if you
rock one click back and forth on the mouse wheel it flips between one
window and each of the others in turn. Prior to the update it flipped
back and forth between two windows - which preserves the nature of the
mouse wheel, if you use it to flip between windows and go past the
window you wanted, a reverse click now takes you to a different window.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1081843

Title:
  [FFe] Launcher, Window Management - More Effective window switching
  for apps with multiple windows using the Launcher

Status in Ayatana Design:
  Fix Released
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  It would be very useful if you could simply hover over an icon of an
  open app and scroll with the mouse wheel to switch and highlight
  between the windows of that app, if it has more.

  -
  Desired resolution:

  Try implementing the following as an experiment.  Before the change
  described below lands in Ubuntu *it must first be user tested, and
  reviewed by the design team*

  If the pointer is positioned over the Launcher icon of an application
  that is in focus which has multiple windows open in the following
  order A,B,C,D,E:

  - Scrolling the mouse wheel 'one click towards the user' should display the 
next window (B) of the application in the Z stack. e.g.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: B,A,C,D,E

  - Scrolling the mouse wheel 'one click away from the user' should display the 
bottom window (E) in the application in the Z stack
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: E,A,B,C,D

  - Scrolling the mouse wheel 'two clicks towards the user' should first 
briefly display the next window of the application in the Z stack (window B) 
after the first mousewheel click, and then on the second mousewheel click 
return window B to it's previous position in the z-stack and display window C.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: C,A,B,D,E

  - Scrolling the mouse wheel 'two clicks away from the user' should first 
briefly display the bottom window of the application in the Z stack (window E) 
after the first mousewheel click, and then on the second mousewheel click 
return window E to it's previous position in the z-stack and display the next 
most bottom window, window D.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: D,A,B,C,E

  - Scrolling the mouse wheel 'three clicks towards the user' should first 
briefly display the next window of the application in the Z stack (window B) 
after the first mousewheel click, and then return window B to it's previous 
position in the z-stack and briefly display the next window of the application 
in the Z stack (window C) after the second mousewheel click, and then on the 
third mousewheel click return window C to it's previous position in the z-stack 
and display window D.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: D,A,B,C,E

  - etc, etc... for more windows and more mouse wheel clicks in either
  direction.

  If the application *is not* in focus when the user moves their pointer
  over the Launcher app icon, the first mouse wheel click towards or
  away from the user should focus the application, and bring the top
  most window in the application's z stack to the front of the global z
  stack.  Subsequent clicks of the mouse wheel the operate exactly as
  described above.

  If the application is not running, or has only one open window mouse
  wheel clicking towards or away from the user when the pointer is over
  the application's launcher icon should do nothing.

  Because this behaviour will conflict with the current use of the mouse
  wheel to scroll the launcher, the mouse wheel launcher scroll should
  be changed to only work when the ALT key is held down.  e.g. to scroll
  the launcher with the mouse wheel the user will have to press ALT +
  MOUSEWHEEL UP or press ALT + MOUSEWHEEL DOWN

  
  -
  Additional test case defining the interaction with minimised windows:

  hyia, minimised windows should be at the back of the stack.  So if App
  1 has have windows A, B, and C (stacking order) and you minimise
  window A, and then focus App 2, when you move your pointer over the
  launcher icon of App 2 and scroll the mousewheel one click, window B
  should appear.  Moving the mouse wheel one more click should then

[Dx-packages] [Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher

2014-02-17 Thread Tin Tvrtkovic

I found using the scroll wheel to bring unfocused application into focus
was very convenient, so it's a little disappointing it's getting
removed.

Also, I agree scrolling through open windows of an application should
behave in a ring-like manner; every scroll should be reversible.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1081843

Title:
  [FFe] Launcher, Window Management - More Effective window switching
  for apps with multiple windows using the Launcher

Status in Ayatana Design:
  Fix Released
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  It would be very useful if you could simply hover over an icon of an
  open app and scroll with the mouse wheel to switch and highlight
  between the windows of that app, if it has more.

  -
  Desired resolution:

  Try implementing the following as an experiment.  Before the change
  described below lands in Ubuntu *it must first be user tested, and
  reviewed by the design team*

  If the pointer is positioned over the Launcher icon of an application
  that is in focus which has multiple windows open in the following
  order A,B,C,D,E:

  - Scrolling the mouse wheel 'one click towards the user' should display the 
next window (B) of the application in the Z stack. e.g.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: B,A,C,D,E

  - Scrolling the mouse wheel 'one click away from the user' should display the 
bottom window (E) in the application in the Z stack
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: E,A,B,C,D

  - Scrolling the mouse wheel 'two clicks towards the user' should first 
briefly display the next window of the application in the Z stack (window B) 
after the first mousewheel click, and then on the second mousewheel click 
return window B to it's previous position in the z-stack and display window C.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: C,A,B,D,E

  - Scrolling the mouse wheel 'two clicks away from the user' should first 
briefly display the bottom window of the application in the Z stack (window E) 
after the first mousewheel click, and then on the second mousewheel click 
return window E to it's previous position in the z-stack and display the next 
most bottom window, window D.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: D,A,B,C,E

  - Scrolling the mouse wheel 'three clicks towards the user' should first 
briefly display the next window of the application in the Z stack (window B) 
after the first mousewheel click, and then return window B to it's previous 
position in the z-stack and briefly display the next window of the application 
in the Z stack (window C) after the second mousewheel click, and then on the 
third mousewheel click return window C to it's previous position in the z-stack 
and display window D.
  Starting Z stack order:   A,B,C,D,E
  Output Z stack order: D,A,B,C,E

  - etc, etc... for more windows and more mouse wheel clicks in either
  direction.

  If the application *is not* in focus when the user moves their pointer
  over the Launcher app icon, the first mouse wheel click towards or
  away from the user should focus the application, and bring the top
  most window in the application's z stack to the front of the global z
  stack.  Subsequent clicks of the mouse wheel the operate exactly as
  described above.

  If the application is not running, or has only one open window mouse
  wheel clicking towards or away from the user when the pointer is over
  the application's launcher icon should do nothing.

  Because this behaviour will conflict with the current use of the mouse
  wheel to scroll the launcher, the mouse wheel launcher scroll should
  be changed to only work when the ALT key is held down.  e.g. to scroll
  the launcher with the mouse wheel the user will have to press ALT +
  MOUSEWHEEL UP or press ALT + MOUSEWHEEL DOWN

  
  -
  Additional test case defining the interaction with minimised windows:

  hyia, minimised windows should be at the back of the stack.  So if App
  1 has have windows A, B, and C (stacking order) and you minimise
  window A, and then focus App 2, when you move your pointer over the
  launcher icon of App 2 and scroll the mousewheel one click, window B
  should appear.  Moving the mouse wheel one more click should then show
  window C.   Moving the mouse wheel one more click should then show
  window A.  Moving the mouse wheel one more click should then show
  window B.  Moving the pointer so that it is no longer over the
  launcher icon of app A at this point should focus window B.  Window A
  should remain minimised.

To manage notifications about this bug go to

[Dx-packages] [Bug 1156566] Re: "Restart" is missing from the system menu

2014-02-17 Thread Treviño

What always blocked me to do this in unity (as I never found the time to
fix things in gnome upstream), is the missing support for a "Reboot"
method call in gnome session dbus api that would generate a
org.gnome.SessionManager.EndSessionDialog.Open signal with an ID for
such kinds of dialogs... :/

As currently it just return the same ID that we have for shutdown...
This thing would make has harder (for example) to select the default
action for easier key-activation.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1156566

Title:
  "Restart" is missing from the system menu

Status in The Session Menu:
  Triaged
Status in “indicator-session” package in Ubuntu:
  Triaged

Bug description:
  Problem occurs in: indicator-session 12.10.5daily13.03.08-0ubuntu1, Ubuntu R
  Does not occur in: Ubuntu 12.10

  1. Open the system menu.

  What you see: "Log Out...", "Suspend", and "Shut Down..." items.

  What you should see: A "Restart..." item between "Suspend" and "Shut Down...".
  

  This is a regression of bug 815077. In 2011 we thought it might be a
  good idea to demote "Restart" to an extra button in the "Shut Down"
  dialog, but we were wrong. So we moved it back to a top-level item in
  the system menu.

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

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

[Dx-packages] [Bug 1280874] Re: current date not highlighted/wrong date highlighted

2014-02-17 Thread John Kim

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Incomplete

** Tags added: saucy

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280874

Title:
  current date not highlighted/wrong date highlighted

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.

  indicator-datetime provides *no highlighting at all* for the current
  date. Worse, it provides faint highlighting for a different date (the
  date I logged in?). See attached screenshot.

  This is related to to several other bugs (below), but the other issues
  are apx 2 years old and appear to be inactive.

  Implications and related UI issues:
  - It is too easy for a user to interpret the faint highlighting as today's 
date.
  - If another day has previously been clicked (even days earlier), it remains 
highlighted. Users will likely expect that the highlighting corresponds to 
today's date, not that of a click days earlier.
  - The lack of a "go to today" button makes it very difficult to focus the 
date for common use cases (What's today's date? What am I doing today? 
Tomorrow?)

  Related:
  https://bugs.launchpad.net/bugs/793450
  https://bugs.launchpad.net/bugs/1017595
  https://bugs.launchpad.net/bugs/740817
  https://bugs.launchpad.net/bugs/1240251
  https://wiki.ubuntu.com/TimeAndDate#menu-calendar

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

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

[Dx-packages] [Bug 1280874] Re: current date not highlighted/wrong date highlighted

2014-02-17 Thread John Kim

Also, please execute the following command, as it will automatically gather 
debugging information, in a terminal:
apport-collect BUGNUMBER
When reporting bugs in the future please use apport by using 'ubuntu-bug' and 
the name of the package affected. You can learn more about this functionality 
at https://wiki.ubuntu.com/ReportingBugs.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280874

Title:
  current date not highlighted/wrong date highlighted

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.

  indicator-datetime provides *no highlighting at all* for the current
  date. Worse, it provides faint highlighting for a different date (the
  date I logged in?). See attached screenshot.

  This is related to to several other bugs (below), but the other issues
  are apx 2 years old and appear to be inactive.

  Implications and related UI issues:
  - It is too easy for a user to interpret the faint highlighting as today's 
date.
  - If another day has previously been clicked (even days earlier), it remains 
highlighted. Users will likely expect that the highlighting corresponds to 
today's date, not that of a click days earlier.
  - The lack of a "go to today" button makes it very difficult to focus the 
date for common use cases (What's today's date? What am I doing today? 
Tomorrow?)

  Related:
  https://bugs.launchpad.net/bugs/793450
  https://bugs.launchpad.net/bugs/1017595
  https://bugs.launchpad.net/bugs/740817
  https://bugs.launchpad.net/bugs/1240251
  https://wiki.ubuntu.com/TimeAndDate#menu-calendar

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

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

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

this is causing an 1172 problem for me
https://xkcd.com/1172/
what was the harm in having clickless app switching from the launcher exactly?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1263786

Title:
  Nonsense behavior of scrollwheel over Launcher

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - move the mouse cursor over the launcher
  - move it over the icon of an application that has one and only one window 
open that is not on front
  - move the scrollwheel of the mouse in any direction

  Expected behavior: NOTHING.

  Ovserved behavior: the window, corresponding to the icon over which
  the mouse cursor is, is brought to front; and this cannot be reversed
  easily.

  
  Trying it with an icon of an application that has two or more windows open 
reveals "why" this happens:
  - move the mouse cursor over the Launcher over an icon of an application that 
has two or more windows open
  - move the scrollwheel
  This will switch between windows of that application, so scrolling up or down 
will bring one or another window (of that same application) to front.
  This is already annoying, like many other abuses of the scrollwheel that 
unfortunately have become widespread (such as: moving the scrollwheel while 
keeping the cursor over a tab will switch among tabs in applications that use 
tabs).
  But even if we accept the annoying 
use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors 
would make sense in this case:
  Option A:
- similar to current behavior (switch between windows of an application) 
but ONLY IF there are more than one window of that application open AND one of 
those window is already focused.
  Or option B:
   - whenever the scrollwheel is on the launcher, scrolling would switch among 
ALL existing windows

  Both option A and B would be consistent with the widespread
  scrollwheel abuse, but would at least make sense, and an unintentional
  movement of the scrollwheel causing an undesired window switching
  could always be reverted by a countermovement of the scrollwheel in
  the opposite direction.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Dec 23 22:45:54 2013
  InstallationDate: Installed on 2013-10-11 (73 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1233029] Re: unity should Depends on unity-scope-home

This bug was fixed in the package unity - 7.1.2+14.04.20140217-0ubuntu1

---
unity (7.1.2+14.04.20140217-0ubuntu1) trusty; urgency=low

  [ Luke Yelavich ]
  * QuickListMenuItem: Add GetPlainTextLabel method to better present
quicklist menu items to screen reader users. When Orca users
navigate quicklists, they hear something like item name, due
to the markup for the item being used as the accessible label. Use
the ACCESSIBLE_DESC property of dbusmenu menu items to provide a
plain text form of the label. (LP: #1266656)

  [ Sebastien Bacher ]
  * Restore archive change dropped by error, let g-s-d run in Unity
sessions

  [ Niklas Steger ]
  * Add missing unity-scope-home dependency. (LP: #1233029)

  [ Chris Townsend ]
  * Fix some more AP tests: Redo the Hud query method to account for the
fact that the Hud button we want may not be the first entry. Fix a
show desktop test so we get the correct show desktop state after the
test exits. Fix a Spread test to get the mouse to move to the
Launcher icon that we want. .
 -- Ubuntu daily releaseMon, 17 Feb 2014 
14:02:37 +

** Changed in: unity (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1233029

Title:
  unity should Depends on unity-scope-home

Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-scope-home” package in Ubuntu:
  Invalid
Status in “unity” source package in Saucy:
  Fix Committed
Status in “unity-scope-home” source package in Saucy:
  Invalid
Status in “unity” source package in Trusty:
  Fix Released
Status in “unity-scope-home” source package in Trusty:
  Invalid

Bug description:
  On my upgrade from 13.04 to 13.10 then my Dash showed only
  applications. This regression meant all other scopes (though appearing
  to be selected) did not produce any results.

  It turns out that installing the unity-scope-home package fixed the
  regression. In order to prevent more confused users, we should somehow
  ensure this package is installed when upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-scope-home 6.8.2+13.10.20130927-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: 346c69198d9a34d2dea85736f0dd6571
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Sun Sep 29 18:01:53 2013
  InstallationDate: Installed on 2012-07-14 (442 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-scope-home
  UpgradeStatus: Upgraded to saucy on 2013-09-24 (4 days ago)

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

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

[Dx-packages] [Bug 1266656] Re: Unity Launcher sub menus contain code launcher description to Orca

This bug was fixed in the package unity - 7.1.2+14.04.20140217-0ubuntu1

---
unity (7.1.2+14.04.20140217-0ubuntu1) trusty; urgency=low

  [ Luke Yelavich ]
  * QuickListMenuItem: Add GetPlainTextLabel method to better present
quicklist menu items to screen reader users. When Orca users
navigate quicklists, they hear something like item name, due
to the markup for the item being used as the accessible label. Use
the ACCESSIBLE_DESC property of dbusmenu menu items to provide a
plain text form of the label. (LP: #1266656)

  [ Sebastien Bacher ]
  * Restore archive change dropped by error, let g-s-d run in Unity
sessions

  [ Niklas Steger ]
  * Add missing unity-scope-home dependency. (LP: #1233029)

  [ Chris Townsend ]
  * Fix some more AP tests: Redo the Hud query method to account for the
fact that the Hud button we want may not be the first entry. Fix a
show desktop test so we get the correct show desktop state after the
test exits. Fix a Spread test to get the mouse to move to the
Launcher icon that we want. .
 -- Ubuntu daily releaseMon, 17 Feb 2014 
14:02:37 +

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1266656

Title:
  Unity Launcher sub menus contain code launcher description to
  Orca

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When in the Unity Launcher, right clicking or for Orca users right
  arrowing presents a context menu. The item is described as Firefox,
  Files, Thunderbird etc but Orca reads out the descriptoin enclosed in
  code ' Firefox. The expected result should be without the code,
  I do not know if this is also presented visually but Orca does read
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20131106.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  ApportVersion: 2.12.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Jan  7 17:29:32 2014
  InstallationDate: Installed on 2013-11-14 (53 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131113)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1280341] Re: indicator-datetime-service crashed with SIGSEGV in strlen()

2014-02-17 Thread Daniel F.

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280341

Title:
  indicator-datetime-service crashed with SIGSEGV in strlen()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  1) Release: 14.04 (Trusty Tahr, Development Branch)
  2) indicator-datetime:
Installed: 13.10.0+14.04.20140205-0ubuntu1
Candidate: 13.10.0+14.04.20140205-0ubuntu1
Version table:
   *** 13.10.0+14.04.20140205-0ubuntu1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  3) Datetime indicator works
  4) Datetime Indicator crashs on Startup

  Some additional reports from syslog:

  Feb 14 16:22:11 sandbox whoopsie[1289]: Parsing 
/var/crash/_usr_lib_x86_64-linux-gnu_indicator-datetime_indicator-datetime-service.1000.crash.
  Feb 14 16:22:11 sandbox whoopsie[1289]: Uploading 
/var/crash/_usr_lib_x86_64-linux-gnu_indicator-datetime_indicator-datetime-service.1000.crash.
  Feb 14 16:22:12 sandbox kernel: [   37.403036] indicator-datet[4528]: 
segfault at 0 ip 7fd7d60ef47a sp 7e1bdd88 error 4 in 
libc-2.18.so[7fd7d6066000+1bc000]
  Feb 14 16:22:12 sandbox whoopsie[1289]: Sent; server replied with: No error
  Feb 14 16:22:12 sandbox whoopsie[1289]: Response code: 200
  Feb 14 16:22:42 sandbox kernel: [   67.415683] indicator-datet[4884]: 
segfault at 0 ip 7fb3fe0fb47a sp 7fff2efff588 error 4 in 
libc-2.18.so[7fb3fe072000+1bc000]
  Feb 14 16:22:44 sandbox kernel: [   69.752004] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:00:0c:f6:f1:c4:d8:08:00 SRC=192.168.0.1 DST=224.0.0.1 
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=33877 PROTO=2
  Feb 14 16:23:13 sandbox kernel: [   98.418746] indicator-datet[4971]: 
segfault at 0 ip 7f9bd898847a sp 7fff31b5f1e8 error 4 in 
libc-2.18.so[7f9bd88ff000+1bc000]
  Feb 14 16:23:44 sandbox kernel: [  129.364079] indicator-datet[5006]: 
segfault at 0 ip 7f38351d447a sp 7fffafb6e498 error 4 in 
libc-2.18.so[7f383514b000+1bc000]
  Feb 14 16:24:14 sandbox kernel: [  159.486863] indicator-datet[5038]: 
segfault at 0 ip 7f770347147a sp 7fff6d467888 error 4 in 
libc-2.18.so[7f77033e8000+1bc000]
  Feb 14 16:24:45 sandbox kernel: [  190.548866] indicator-datet[5077]: 
segfault at 0 ip 7f1f195d447a sp 7fff16aef588 error 4 in 
libc-2.18.so[7f1f1954b000+1bc000]
  Feb 14 16:24:49 sandbox kernel: [  194.852228] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:00:0c:f6:f1:c4:d8:08:00 SRC=192.168.0.1 DST=224.0.0.1 
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=33878 PROTO=2
  Feb 14 16:25:16 sandbox kernel: [  221.429753] indicator-datet[5150]: 
segfault at 0 ip 7ff5402e347a sp 7fff86272718 error 4 in 
libc-2.18.so[7ff54025a000+1bc000]

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140205-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Feb 14 16:21:55 2014
  EcryptfsInUse: Yes
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2013-12-30 (45 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x7fcc7470147a :movdqu (%rax),%xmm12
   PC (0x7fcc7470147a) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   
unity::indicator::datetime::PlannerEds::Impl::my_get_appointments_foreach(_ECalComponent*,
 long, long, void*) ()
   ?? () from /usr/lib/libecal-1.2.so.16
   ?? () from /usr/lib/libecal-1.2.so.16
   ?? () from /usr/lib/libecal-1.2.so.16
  Title: indicator-datetime-service crashed with SIGSEGV in strlen()
  UpgradeStatus: Upgraded to trusty on 2014-01-06 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

2014-02-17 Thread Avi Greenbury

The harm is not in having clickless app switching, it's in having an
action triggered by a scroll-up that's not undone by a scroll-down;
there's no obvious way to undo this and if you don't know that it's
intentional it's a bit surprising when it happens.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1263786

Title:
  Nonsense behavior of scrollwheel over Launcher

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - move the mouse cursor over the launcher
  - move it over the icon of an application that has one and only one window 
open that is not on front
  - move the scrollwheel of the mouse in any direction

  Expected behavior: NOTHING.

  Ovserved behavior: the window, corresponding to the icon over which
  the mouse cursor is, is brought to front; and this cannot be reversed
  easily.

  
  Trying it with an icon of an application that has two or more windows open 
reveals "why" this happens:
  - move the mouse cursor over the Launcher over an icon of an application that 
has two or more windows open
  - move the scrollwheel
  This will switch between windows of that application, so scrolling up or down 
will bring one or another window (of that same application) to front.
  This is already annoying, like many other abuses of the scrollwheel that 
unfortunately have become widespread (such as: moving the scrollwheel while 
keeping the cursor over a tab will switch among tabs in applications that use 
tabs).
  But even if we accept the annoying 
use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors 
would make sense in this case:
  Option A:
- similar to current behavior (switch between windows of an application) 
but ONLY IF there are more than one window of that application open AND one of 
those window is already focused.
  Or option B:
   - whenever the scrollwheel is on the launcher, scrolling would switch among 
ALL existing windows

  Both option A and B would be consistent with the widespread
  scrollwheel abuse, but would at least make sense, and an unintentional
  movement of the scrollwheel causing an undesired window switching
  could always be reverted by a countermovement of the scrollwheel in
  the opposite direction.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Dec 23 22:45:54 2013
  InstallationDate: Installed on 2013-10-11 (73 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

2014-02-17 Thread matteo sisti sette

And when you know it's intentional it is annoying as well as surprising
:)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1263786

Title:
  Nonsense behavior of scrollwheel over Launcher

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - move the mouse cursor over the launcher
  - move it over the icon of an application that has one and only one window 
open that is not on front
  - move the scrollwheel of the mouse in any direction

  Expected behavior: NOTHING.

  Ovserved behavior: the window, corresponding to the icon over which
  the mouse cursor is, is brought to front; and this cannot be reversed
  easily.

  
  Trying it with an icon of an application that has two or more windows open 
reveals "why" this happens:
  - move the mouse cursor over the Launcher over an icon of an application that 
has two or more windows open
  - move the scrollwheel
  This will switch between windows of that application, so scrolling up or down 
will bring one or another window (of that same application) to front.
  This is already annoying, like many other abuses of the scrollwheel that 
unfortunately have become widespread (such as: moving the scrollwheel while 
keeping the cursor over a tab will switch among tabs in applications that use 
tabs).
  But even if we accept the annoying 
use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors 
would make sense in this case:
  Option A:
- similar to current behavior (switch between windows of an application) 
but ONLY IF there are more than one window of that application open AND one of 
those window is already focused.
  Or option B:
   - whenever the scrollwheel is on the launcher, scrolling would switch among 
ALL existing windows

  Both option A and B would be consistent with the widespread
  scrollwheel abuse, but would at least make sense, and an unintentional
  movement of the scrollwheel causing an undesired window switching
  could always be reverted by a countermovement of the scrollwheel in
  the opposite direction.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Dec 23 22:45:54 2013
  InstallationDate: Installed on 2013-10-11 (73 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1281189] [NEW] compiz crashed with SIGSEGV in generate()

2014-02-17 Thread Carterclan

Public bug reported:

Running in low graphics mode after latest update to compiz and unity.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 17 17:02:50 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-01-21 (26 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f0fb830bc24 <__memmove_sse2+244>: movzbl 
(%rdx),%ecx
 PC (0x7f0fb830bc24) ok
 source "(%rdx)" (0x44e4a3d3) not located in a known VMA region (needed 
readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, unsigned 
long, boost::function const&, boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
 TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
 TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: unity (Ubuntu)
 Importance: Medium
 Status: New


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

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281189

Title:
  compiz crashed with SIGSEGV in generate()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Running in low graphics mode after latest update to compiz and unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 17:02:50 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-01-21 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f0fb830bc24 <__memmove_sse2+244>:   movzbl 
(%rdx),%ecx
   PC (0x7f0fb830bc24) ok
   source "(%rdx)" (0x44e4a3d3) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281189/+subscriptions

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

[Dx-packages] [Bug 1281189] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1281189/+attachment/3984210/+files/StacktraceSource.txt

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281189

Title:
  compiz crashed with SIGSEGV in generate()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Running in low graphics mode after latest update to compiz and unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 17:02:50 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-01-21 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f0fb830bc24 <__memmove_sse2+244>:   movzbl 
(%rdx),%ecx
   PC (0x7f0fb830bc24) ok
   source "(%rdx)" (0x44e4a3d3) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281189/+subscriptions

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

[Dx-packages] [Bug 1281189]

StacktraceTop:
 generate (list=0x243, condition=0x0, i=0, this=0x64d77034) at 
../../../../src/glsl/lower_variable_index_to_cond_assign.cpp:226
 linear_sequence (list=0x243, end=0, begin=0, this=0x9b288fcc) at 
../../../../src/glsl/lower_variable_index_to_cond_assign.cpp:269
 (anonymous namespace)::switch_generator::generate (this=0x9b288fcc, 
begin=0, end=0, list=0x243) at 
../../../../src/glsl/lower_variable_index_to_cond_assign.cpp:326
 ?? ()

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281189

Title:
  compiz crashed with SIGSEGV in generate()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Running in low graphics mode after latest update to compiz and unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 17:02:50 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-01-21 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f0fb830bc24 <__memmove_sse2+244>:   movzbl 
(%rdx),%ecx
   PC (0x7f0fb830bc24) ok
   source "(%rdx)" (0x44e4a3d3) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281189/+subscriptions

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

[Dx-packages] [Bug 1281189] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1281189/+attachment/3984209/+files/Stacktrace.txt

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281189

Title:
  compiz crashed with SIGSEGV in generate()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Running in low graphics mode after latest update to compiz and unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 17:02:50 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-01-21 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f0fb830bc24 <__memmove_sse2+244>:   movzbl 
(%rdx),%ecx
   PC (0x7f0fb830bc24) ok
   source "(%rdx)" (0x44e4a3d3) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281189/+subscriptions

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

[Dx-packages] [Bug 1281191] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1199571
   compiz crashed with SIGSEGV in af_latin_hints_compute_edges()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281191

Title:
  compiz crashed with SIGSEGV in FT_Load_Glyph()

Status in “unity” package in Ubuntu:
  New

Bug description:
  I wasn't doing anything in particular. Simply using Unity

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 12:09:18 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-12-17 (61 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131217)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4a8018b7e0:mov%rdx,0x10(%rax)
   PC (0x7f4a8018b7e0) ok
   source "%rdx" ok
   destination "0x10(%rax)" (0x0010) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  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/ubuntu/+source/unity/+bug/1281191/+subscriptions

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

[Dx-packages] [Bug 1281189] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1281189/+attachment/3984211/+files/ThreadStacktrace.txt

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

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

** Summary changed:

- compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
+ compiz crashed with SIGSEGV in generate()

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281189

Title:
  compiz crashed with SIGSEGV in generate()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Running in low graphics mode after latest update to compiz and unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 17:02:50 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-01-21 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f0fb830bc24 <__memmove_sse2+244>:   movzbl 
(%rdx),%ecx
   PC (0x7f0fb830bc24) ok
   source "(%rdx)" (0x44e4a3d3) not located in a known VMA region 
(needed readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281189/+subscriptions

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

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

yeah, I know I am on the bring back spacebar heating side of this one.
bah. I liked it.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1263786

Title:
  Nonsense behavior of scrollwheel over Launcher

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - move the mouse cursor over the launcher
  - move it over the icon of an application that has one and only one window 
open that is not on front
  - move the scrollwheel of the mouse in any direction

  Expected behavior: NOTHING.

  Ovserved behavior: the window, corresponding to the icon over which
  the mouse cursor is, is brought to front; and this cannot be reversed
  easily.

  
  Trying it with an icon of an application that has two or more windows open 
reveals "why" this happens:
  - move the mouse cursor over the Launcher over an icon of an application that 
has two or more windows open
  - move the scrollwheel
  This will switch between windows of that application, so scrolling up or down 
will bring one or another window (of that same application) to front.
  This is already annoying, like many other abuses of the scrollwheel that 
unfortunately have become widespread (such as: moving the scrollwheel while 
keeping the cursor over a tab will switch among tabs in applications that use 
tabs).
  But even if we accept the annoying 
use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors 
would make sense in this case:
  Option A:
- similar to current behavior (switch between windows of an application) 
but ONLY IF there are more than one window of that application open AND one of 
those window is already focused.
  Or option B:
   - whenever the scrollwheel is on the launcher, scrolling would switch among 
ALL existing windows

  Both option A and B would be consistent with the widespread
  scrollwheel abuse, but would at least make sense, and an unintentional
  movement of the scrollwheel causing an undesired window switching
  could always be reverted by a countermovement of the scrollwheel in
  the opposite direction.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Dec 23 22:45:54 2013
  InstallationDate: Installed on 2013-10-11 (73 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

wow it does freaky stuff with the z-order now, this is barely
deterministic, it does different things for slow scrolling or pausing
between windows and fast scrolling. Probably worth a new bug with video
I think.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1263786

Title:
  Nonsense behavior of scrollwheel over Launcher

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - move the mouse cursor over the launcher
  - move it over the icon of an application that has one and only one window 
open that is not on front
  - move the scrollwheel of the mouse in any direction

  Expected behavior: NOTHING.

  Ovserved behavior: the window, corresponding to the icon over which
  the mouse cursor is, is brought to front; and this cannot be reversed
  easily.

  
  Trying it with an icon of an application that has two or more windows open 
reveals "why" this happens:
  - move the mouse cursor over the Launcher over an icon of an application that 
has two or more windows open
  - move the scrollwheel
  This will switch between windows of that application, so scrolling up or down 
will bring one or another window (of that same application) to front.
  This is already annoying, like many other abuses of the scrollwheel that 
unfortunately have become widespread (such as: moving the scrollwheel while 
keeping the cursor over a tab will switch among tabs in applications that use 
tabs).
  But even if we accept the annoying 
use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors 
would make sense in this case:
  Option A:
- similar to current behavior (switch between windows of an application) 
but ONLY IF there are more than one window of that application open AND one of 
those window is already focused.
  Or option B:
   - whenever the scrollwheel is on the launcher, scrolling would switch among 
ALL existing windows

  Both option A and B would be consistent with the widespread
  scrollwheel abuse, but would at least make sense, and an unintentional
  movement of the scrollwheel causing an undesired window switching
  could always be reverted by a countermovement of the scrollwheel in
  the opposite direction.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Dec 23 22:45:54 2013
  InstallationDate: Installed on 2013-10-11 (73 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 839728] Re: Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow

2014-02-17 Thread Treviño

** Changed in: unity
   Status: Triaged => In Progress

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

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

** Changed in: unity
Milestone: backlog => 7.2.0

** Changed in: unity (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/839728

Title:
  Launcher - dragging a item on top of a launcher tile that is a valid
  drop receptacle in the Launcher should cause that launcher tile to
  glow

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Launcher - dragging a item on top of a launcher tile that is a valid
  drop receptacle in the Launcher should cause that launcher tile to
  glow.  This glow only persists as long as the dragged item is directly
  over the launcher tile, as soon as the dragged item is moved off the
  launcher tile, the glow should stop.

  Use cases:

  - User drags a .png file over the Firefox icon in the Launcher.  As
  soon as the .png file is over the Firefox icon, the firefox icon
  starts to glow.  The user then moves the .png file off the Firefox
  launcher icon, and the Firefox launcher immediately stops glowing.

  - User drags a launcher tile from it's position in the launcher to the
  trash can.  As soon as the Launcher tile is above the trash can, the
  trash can starts to glow.  The user then moves the launcher tile off
  the trash can and the trash can stops glowing.

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

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

[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher

2014-02-17 Thread David Callé

If there is a wheel, there is a way ;-)
$ while :;do xev -id $(xwininfo -name "unity-launcher" | head -n 2 | cut -d' ' 
-f4) | grep -q '4096\|2048'; xdotool click 1;done

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1263786

Title:
  Nonsense behavior of scrollwheel over Launcher

Status in Unity:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - move the mouse cursor over the launcher
  - move it over the icon of an application that has one and only one window 
open that is not on front
  - move the scrollwheel of the mouse in any direction

  Expected behavior: NOTHING.

  Ovserved behavior: the window, corresponding to the icon over which
  the mouse cursor is, is brought to front; and this cannot be reversed
  easily.

  
  Trying it with an icon of an application that has two or more windows open 
reveals "why" this happens:
  - move the mouse cursor over the Launcher over an icon of an application that 
has two or more windows open
  - move the scrollwheel
  This will switch between windows of that application, so scrolling up or down 
will bring one or another window (of that same application) to front.
  This is already annoying, like many other abuses of the scrollwheel that 
unfortunately have become widespread (such as: moving the scrollwheel while 
keeping the cursor over a tab will switch among tabs in applications that use 
tabs).
  But even if we accept the annoying 
use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors 
would make sense in this case:
  Option A:
- similar to current behavior (switch between windows of an application) 
but ONLY IF there are more than one window of that application open AND one of 
those window is already focused.
  Or option B:
   - whenever the scrollwheel is on the launcher, scrolling would switch among 
ALL existing windows

  Both option A and B would be consistent with the widespread
  scrollwheel abuse, but would at least make sense, and an unintentional
  movement of the scrollwheel causing an undesired window switching
  could always be reverted by a countermovement of the scrollwheel in
  the opposite direction.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Dec 23 22:45:54 2013
  InstallationDate: Installed on 2013-10-11 (73 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 839728] Re: Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow

** Branch linked: lp:~3v1n0/unity/glowing-dnd-launcher-icon

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/839728

Title:
  Launcher - dragging a item on top of a launcher tile that is a valid
  drop receptacle in the Launcher should cause that launcher tile to
  glow

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Launcher - dragging a item on top of a launcher tile that is a valid
  drop receptacle in the Launcher should cause that launcher tile to
  glow.  This glow only persists as long as the dragged item is directly
  over the launcher tile, as soon as the dragged item is moved off the
  launcher tile, the glow should stop.

  Use cases:

  - User drags a .png file over the Firefox icon in the Launcher.  As
  soon as the .png file is over the Firefox icon, the firefox icon
  starts to glow.  The user then moves the .png file off the Firefox
  launcher icon, and the Firefox launcher immediately stops glowing.

  - User drags a launcher tile from it's position in the launcher to the
  trash can.  As soon as the Launcher tile is above the trash can, the
  trash can starts to glow.  The user then moves the launcher tile off
  the trash can and the trash can stops glowing.

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

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

[Dx-packages] [Bug 1281212] Re: zeitgeist-datahub crashed with SIGSEGV in g_slice_alloc()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to zeitgeist in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281212

Title:
  zeitgeist-datahub crashed with SIGSEGV in g_slice_alloc()

Status in “zeitgeist” package in Ubuntu:
  New

Bug description:
  xubuntu trusty, upgraded from 13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: zeitgeist-datahub 0.9.14-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  Date: Mon Feb 17 19:44:42 2014
  ExecutablePath: /usr/bin/zeitgeist-datahub
  InstallationDate: Installed on 2014-01-10 (37 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
  ProcCmdline: zeitgeist-datahub
  SegvAnalysis:
   Segfault happened at: 0xb6ea704e :mov
(%edi),%edx
   PC (0xb6ea704e) ok
   source "(%edi)" (0x0017f1eb) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: zeitgeist
  StacktraceTop:
   g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: zeitgeist-datahub crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to trusty on 2014-01-15 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1280874] ProcEnviron.txt

2014-02-17 Thread Reece

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1280874/+attachment/3984254/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280874

Title:
  current date not highlighted/wrong date highlighted

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.

  indicator-datetime provides *no highlighting at all* for the current
  date. Worse, it provides faint highlighting for a different date (the
  date I logged in?). See attached screenshot.

  This is related to to several other bugs (below), but the other issues
  are apx 2 years old and appear to be inactive.

  Implications and related UI issues:
  - It is too easy for a user to interpret the faint highlighting as today's 
date.
  - If another day has previously been clicked (even days earlier), it remains 
highlighted. Users will likely expect that the highlighting corresponds to 
today's date, not that of a click days earlier.
  - The lack of a "go to today" button makes it very difficult to focus the 
date for common use cases (What's today's date? What am I doing today? 
Tomorrow?)

  Related:
  https://bugs.launchpad.net/bugs/793450
  https://bugs.launchpad.net/bugs/1017595
  https://bugs.launchpad.net/bugs/740817
  https://bugs.launchpad.net/bugs/1240251
  https://wiki.ubuntu.com/TimeAndDate#menu-calendar
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2012-10-09 (495 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags: saucy third-party-packages
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-11-12 (97 days ago)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo vboxusers

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

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

[Dx-packages] [Bug 1280874] Re: current date not highlighted/wrong date highlighted

2014-02-17 Thread Reece

apport information

** Tags added: apport-collected third-party-packages

** Description changed:

  Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.
  
  indicator-datetime provides *no highlighting at all* for the current
  date. Worse, it provides faint highlighting for a different date (the
  date I logged in?). See attached screenshot.
  
  This is related to to several other bugs (below), but the other issues
  are apx 2 years old and appear to be inactive.
  
  Implications and related UI issues:
  - It is too easy for a user to interpret the faint highlighting as today's 
date.
  - If another day has previously been clicked (even days earlier), it remains 
highlighted. Users will likely expect that the highlighting corresponds to 
today's date, not that of a click days earlier.
  - The lack of a "go to today" button makes it very difficult to focus the 
date for common use cases (What's today's date? What am I doing today? 
Tomorrow?)
  
  Related:
  https://bugs.launchpad.net/bugs/793450
  https://bugs.launchpad.net/bugs/1017595
  https://bugs.launchpad.net/bugs/740817
  https://bugs.launchpad.net/bugs/1240251
  https://wiki.ubuntu.com/TimeAndDate#menu-calendar
+ --- 
+ ApportVersion: 2.12.5-0ubuntu2.2
+ Architecture: amd64
+ DistroRelease: Ubuntu 13.10
+ InstallationDate: Installed on 2012-10-09 (495 days ago)
+ InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
+ MarkForUpload: True
+ Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
+ Tags: saucy third-party-packages
+ Uname: Linux 3.11.0-15-generic x86_64
+ UpgradeStatus: Upgraded to saucy on 2013-11-12 (97 days ago)
+ UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo vboxusers

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1280874/+attachment/3984253/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280874

Title:
  current date not highlighted/wrong date highlighted

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.

  indicator-datetime provides *no highlighting at all* for the current
  date. Worse, it provides faint highlighting for a different date (the
  date I logged in?). See attached screenshot.

  This is related to to several other bugs (below), but the other issues
  are apx 2 years old and appear to be inactive.

  Implications and related UI issues:
  - It is too easy for a user to interpret the faint highlighting as today's 
date.
  - If another day has previously been clicked (even days earlier), it remains 
highlighted. Users will likely expect that the highlighting corresponds to 
today's date, not that of a click days earlier.
  - The lack of a "go to today" button makes it very difficult to focus the 
date for common use cases (What's today's date? What am I doing today? 
Tomorrow?)

  Related:
  https://bugs.launchpad.net/bugs/793450
  https://bugs.launchpad.net/bugs/1017595
  https://bugs.launchpad.net/bugs/740817
  https://bugs.launchpad.net/bugs/1240251
  https://wiki.ubuntu.com/TimeAndDate#menu-calendar
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2012-10-09 (495 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags: saucy third-party-packages
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-11-12 (97 days ago)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo vboxusers

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

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

[Dx-packages] [Bug 1280874] Re: current date not highlighted/wrong date highlighted

2014-02-17 Thread Reece

apport bug data sent

This is reproducible. Steps:

1) Boot ubuntu.
2) Go to calendar (click indicator-datetime). Select a day in the previous or 
next month (any day works, but this makes a good example).
3) Click indicator again. The clicked date remains highlighted.

The confusion occurs when there is a long duration between 2 and 3: I
forget I've clicked and the highlighted day is NOT today. Personally, I
don't see any reason to preserve the selected day between drop down
events.


(As an aside, Launchpad has a big button that says "Report a bug". It might be 
worth recommending ubuntu-bug in that workflow if that's the preferred method 
for bug reporting.  Thanks for your help and I'll use ubuntu-bug next time.)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280874

Title:
  current date not highlighted/wrong date highlighted

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10, x86_64, indicator-datetime 13.10.0+13.10.20131023.

  indicator-datetime provides *no highlighting at all* for the current
  date. Worse, it provides faint highlighting for a different date (the
  date I logged in?). See attached screenshot.

  This is related to to several other bugs (below), but the other issues
  are apx 2 years old and appear to be inactive.

  Implications and related UI issues:
  - It is too easy for a user to interpret the faint highlighting as today's 
date.
  - If another day has previously been clicked (even days earlier), it remains 
highlighted. Users will likely expect that the highlighting corresponds to 
today's date, not that of a click days earlier.
  - The lack of a "go to today" button makes it very difficult to focus the 
date for common use cases (What's today's date? What am I doing today? 
Tomorrow?)

  Related:
  https://bugs.launchpad.net/bugs/793450
  https://bugs.launchpad.net/bugs/1017595
  https://bugs.launchpad.net/bugs/740817
  https://bugs.launchpad.net/bugs/1240251
  https://wiki.ubuntu.com/TimeAndDate#menu-calendar
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2012-10-09 (495 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags: saucy third-party-packages
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-11-12 (97 days ago)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo vboxusers

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

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

[Dx-packages] [Bug 1279811] Re: Clock keeps marked calendar day

2014-02-17 Thread Fido

This happens to me every time a day passes, for instance: if I turn my computer 
on today then tomorrow the selected day will be todays, and so forth.
As an example the attached screenshot is from today.

To reproduce (the short way...): 
1) disable NTP
2) set the hour to 11:59PM 
3) wait a minute

** Attachment added: "Screenshot from 2014-02-17 15:36:50.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1279811/+attachment/3984329/+files/Screenshot%20from%202014-02-17%2015%3A36%3A50.png

** Package changed: unity (Ubuntu) => indicator-datetime (Ubuntu)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1279811

Title:
  Clock keeps marked calendar day

Status in “indicator-datetime” package in Ubuntu:
  Incomplete

Bug description:
  I do not know the reason for keeping a day marked in the calendar
  (unity-panel-service) as it is confusing. I must have selected the
  yesterday's day and now I see it selected in the calendar. Sometimes I
  see even an older day. It should flush it. See the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Feb 13 15:42:43 2014
  InstallationDate: Installed on 2013-10-19 (117 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 971462] Re: When HUD is enabled, AltGr/Compose still causes focus stealing from the widget

2014-02-17 Thread Peter

I found a workaround that solved it for me.

It seams the reason for this is somehow related to equal key bindings in compiz
plugins for unity and gnome compatibility.
Disabling the key bindings in gnome compatibility plugin solved this for me.

--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/971462

Title:
When HUD is enabled, AltGr/Compose still causes focus stealing from
the widget

Status in Compiz:
Confirmed
Status in Unity:
Confirmed
Status in “unity” package in Ubuntu:
Confirmed

Bug description:
STR:

1. Make sure that HUD is enabled
2. Make sure you are using a keyboard layout that uses a Compose key (e.g.
English (UK))
3. Open http://people.canonical.com/~roman.yepishev/blur.html in firefox or
chromium
4. Put the cursor in the field and press AltGr/Compose key
5. Observe that "Blurred" is appended on the page

Expected results:
Compose sends nothing (as it happens when HUD is disabled)

Actual results:
Widget loses focus for a fraction of the second.

Impact:
This is most noticeable in the web pages that make use of 'blur' event
handler, such as PicasaWeb, where the image title is updated once the focus
leaves the field, thus making it impossible to properly change the title of the
picture.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-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: Mon Apr 2 11:28:58 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64
(20120225)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1262374] Re: please do not build-depend on valgrind on ppc64el

** Branch linked: lp:ubuntu/trusty-proposed/libdbusmenu

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libdbusmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1262374

Title:
  please do not build-depend on valgrind on ppc64el

Status in “libdbusmenu” package in Ubuntu:
  New

Bug description:
  same thing as on arm64. please do not build-depend on valgrind on
  ppc64el, not yet ported.

  patch at
  
http://launchpadlibrarian.net/160145511/libdbusmenu_12.10.3%2B14.04.20131125-0ubuntu1_12.10.3%2B14.04.20131125-0ubuntu2.diff.gz

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

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

[Dx-packages] [Bug 907635] Re: lidbusmenu-GTK crash with Geany IDE using Python

** Branch linked: lp:ubuntu/trusty-proposed/libdbusmenu

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libdbusmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/907635

Title:
  lidbusmenu-GTK crash with Geany IDE using Python

Status in DBus Menu:
  Fix Committed
Status in “libdbusmenu” package in Ubuntu:
  Expired

Bug description:
  When I list debug msgs from the Geany Menu, i get:
  22:59:03: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:00:42: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:09:48: Geany INFO  : *DOC* : Python (UTF-8)
  23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:55: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed

  I have seen the same or similar postings all on Ubuntu or a derivative. Some 
have implied that it was a known bug with Ubuntu 11.10. Any help would be 
greatly appreciated.
  Geany 0.20, libdbusmenu-gtk4, libdbusmenu-gtk3-4, libdbusmenu-gtk-dev, 
libdbusmenu-gtk3-dev, Ubuntu 11.10
  Someone else on the web was having the same problems using Lotus Notes, same 
error msg.

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

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

[Dx-packages] [Bug 976100] Re: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic

2014-02-17 Thread Ryan Tandy

With the merge of lp:~robert-ancell/indicator-datetime/no-panel,
released in 13.10.0+14.04.20140217-0ubuntu1, the behaviour is correct in
Trusty now, so marking fixed.

** Branch unlinked: lp:~rtandy/indicator-datetime/lp976100

** Changed in: indicator-datetime
   Status: In Progress => Fix Released

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: indicator-datetime
 Assignee: Ryan Tandy (rtandy) => (unassigned)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/976100

Title:
  Time and Date Settings don't load in Ubuntu Precise and newer with
  Gnome Classic

Status in The Date and Time Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” source package in Precise:
  Won't Fix

Bug description:
  STEPS TO REPRODUCE:

  1) Install "gnome-panel" to have Ubuntu Classic

  2) Login to Ubuntu Gnome Classic with Effects

  3) Click on the Time Indicator

  4) Select "Time and Date Settings"

  5) System Settings is opened. We have to find "date and time"
  manually.

  
  DESIRED OUTPUT:

  4) Select "Time and Date Settings"

  5) System Settings->  "Date and Time" should be opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-datetime 0.3.94-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 10:49:05 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120325)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1262374] Re: please do not build-depend on valgrind on ppc64el

This bug was fixed in the package libdbusmenu -
12.10.3+14.04.20140217.1-0ubuntu1

---
libdbusmenu (12.10.3+14.04.20140217.1-0ubuntu1) trusty; urgency=low

  [ Ted Gould ]
  * Don't depend on valgrind on ppc64el. (LP: #1262374)
  * Flushing trunk with a release

  [ Matthew Brush ]
  * Check to ensure the property isn't set to NULL. (LP: #907635)
 -- Ubuntu daily releaseMon, 17 Feb 2014 
18:07:41 +

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libdbusmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1262374

Title:
  please do not build-depend on valgrind on ppc64el

Status in “libdbusmenu” package in Ubuntu:
  Fix Released

Bug description:
  same thing as on arm64. please do not build-depend on valgrind on
  ppc64el, not yet ported.

  patch at
  
http://launchpadlibrarian.net/160145511/libdbusmenu_12.10.3%2B14.04.20131125-0ubuntu1_12.10.3%2B14.04.20131125-0ubuntu2.diff.gz

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

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

[Dx-packages] [Bug 1281274] [NEW] tahr update 17 Feb display settings fail

2014-02-17 Thread jerrylamos

Public bug reported:

after today's update screen settings changed from laptop display off, external 
monitor 1440x900 
to both displays on at 1024x768.  Settings gets error msg GDBus error, could 
not find org.gnome.SettingsDaemon.

See screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Feb 17 15:09:04 2014
InstallationDate: Installed on 2014-01-28 (19 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: "screenshot showing error msb"
   
https://bugs.launchpad.net/bugs/1281274/+attachment/3984441/+files/Screenshot%20from%202014-02-17%2015%3A07%3A41.png

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281274

Title:
  tahr update 17 Feb display settings fail

Status in “unity” package in Ubuntu:
  New

Bug description:
  after today's update screen settings changed from laptop display off, 
external monitor 1440x900 
  to both displays on at 1024x768.  Settings gets error msg GDBus error, could 
not find org.gnome.SettingsDaemon.

  See screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Feb 17 15:09:04 2014
  InstallationDate: Installed on 2014-01-28 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128)
  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/1281274/+subscriptions

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

[Dx-packages] [Bug 907635] Re: lidbusmenu-GTK crash with Geany IDE using Python

This bug was fixed in the package libdbusmenu -
12.10.3+14.04.20140217.1-0ubuntu1

---
libdbusmenu (12.10.3+14.04.20140217.1-0ubuntu1) trusty; urgency=low

  [ Ted Gould ]
  * Don't depend on valgrind on ppc64el. (LP: #1262374)
  * Flushing trunk with a release

  [ Matthew Brush ]
  * Check to ensure the property isn't set to NULL. (LP: #907635)
 -- Ubuntu daily releaseMon, 17 Feb 2014 
18:07:41 +

** Changed in: libdbusmenu (Ubuntu)
   Status: Expired => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libdbusmenu in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/907635

Title:
  lidbusmenu-GTK crash with Geany IDE using Python

Status in DBus Menu:
  Fix Committed
Status in “libdbusmenu” package in Ubuntu:
  Fix Released

Bug description:
  When I list debug msgs from the Geany Menu, i get:
  22:59:03: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:00:42: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:09:48: Geany INFO  : *DOC* : Python (UTF-8)
  23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed
  23:18:55: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion 
`GTK_IS_MENU_SHELL(menu)' failed

  I have seen the same or similar postings all on Ubuntu or a derivative. Some 
have implied that it was a known bug with Ubuntu 11.10. Any help would be 
greatly appreciated.
  Geany 0.20, libdbusmenu-gtk4, libdbusmenu-gtk3-4, libdbusmenu-gtk-dev, 
libdbusmenu-gtk3-dev, Ubuntu 11.10
  Someone else on the web was having the same problems using Lotus Notes, same 
error msg.

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

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

[Dx-packages] [Bug 1281272] Re: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1055166
   compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from 
dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() 
from ... from unity::UnityWindow::DrawWindowDecoration

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281272

Title:
  compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

Status in “unity” package in Ubuntu:
  New

Bug description:
  As normal the UK keyboard setting still doesn't work (reverting to US
  on reboot), I went to advanced recovery to check it was ok there (it
  was) and then resumed the boot at which point Compiz went wobbly.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140214.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 17 19:58:40 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-02-17 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140216)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3b893f4c24 <__memmove_sse2+244>:   movzbl 
(%rdx),%ecx
   PC (0x7f3b893f4c24) ok
   source "(%rdx)" (0x7f3ae830f073) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281272/+subscriptions

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

[Dx-packages] [Bug 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

** Tags added: bugpattern-needed

** Tags added: trusty

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1055166

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Mesa:
  Invalid
Status in Unity:
  Triaged
Status in Unity 6.0 series:
  Triaged
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Dx-packages] [Bug 1280341] Re: indicator-datetime-service crashed with SIGSEGV in strlen()

2014-02-17 Thread Daniel F.

This error occurs when you import empty calendar events (no name), e.g
by integrating an gmail calendar account

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1280341

Title:
  indicator-datetime-service crashed with SIGSEGV in strlen()

Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  1) Release: 14.04 (Trusty Tahr, Development Branch)
  2) indicator-datetime:
Installed: 13.10.0+14.04.20140205-0ubuntu1
Candidate: 13.10.0+14.04.20140205-0ubuntu1
Version table:
   *** 13.10.0+14.04.20140205-0ubuntu1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  3) Datetime indicator works
  4) Datetime Indicator crashs on Startup

  Some additional reports from syslog:

  Feb 14 16:22:11 sandbox whoopsie[1289]: Parsing 
/var/crash/_usr_lib_x86_64-linux-gnu_indicator-datetime_indicator-datetime-service.1000.crash.
  Feb 14 16:22:11 sandbox whoopsie[1289]: Uploading 
/var/crash/_usr_lib_x86_64-linux-gnu_indicator-datetime_indicator-datetime-service.1000.crash.
  Feb 14 16:22:12 sandbox kernel: [   37.403036] indicator-datet[4528]: 
segfault at 0 ip 7fd7d60ef47a sp 7e1bdd88 error 4 in 
libc-2.18.so[7fd7d6066000+1bc000]
  Feb 14 16:22:12 sandbox whoopsie[1289]: Sent; server replied with: No error
  Feb 14 16:22:12 sandbox whoopsie[1289]: Response code: 200
  Feb 14 16:22:42 sandbox kernel: [   67.415683] indicator-datet[4884]: 
segfault at 0 ip 7fb3fe0fb47a sp 7fff2efff588 error 4 in 
libc-2.18.so[7fb3fe072000+1bc000]
  Feb 14 16:22:44 sandbox kernel: [   69.752004] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:00:0c:f6:f1:c4:d8:08:00 SRC=192.168.0.1 DST=224.0.0.1 
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=33877 PROTO=2
  Feb 14 16:23:13 sandbox kernel: [   98.418746] indicator-datet[4971]: 
segfault at 0 ip 7f9bd898847a sp 7fff31b5f1e8 error 4 in 
libc-2.18.so[7f9bd88ff000+1bc000]
  Feb 14 16:23:44 sandbox kernel: [  129.364079] indicator-datet[5006]: 
segfault at 0 ip 7f38351d447a sp 7fffafb6e498 error 4 in 
libc-2.18.so[7f383514b000+1bc000]
  Feb 14 16:24:14 sandbox kernel: [  159.486863] indicator-datet[5038]: 
segfault at 0 ip 7f770347147a sp 7fff6d467888 error 4 in 
libc-2.18.so[7f77033e8000+1bc000]
  Feb 14 16:24:45 sandbox kernel: [  190.548866] indicator-datet[5077]: 
segfault at 0 ip 7f1f195d447a sp 7fff16aef588 error 4 in 
libc-2.18.so[7f1f1954b000+1bc000]
  Feb 14 16:24:49 sandbox kernel: [  194.852228] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:00:0c:f6:f1:c4:d8:08:00 SRC=192.168.0.1 DST=224.0.0.1 
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=33878 PROTO=2
  Feb 14 16:25:16 sandbox kernel: [  221.429753] indicator-datet[5150]: 
segfault at 0 ip 7ff5402e347a sp 7fff86272718 error 4 in 
libc-2.18.so[7ff54025a000+1bc000]

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140205-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Feb 14 16:21:55 2014
  EcryptfsInUse: Yes
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2013-12-30 (45 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  SegvAnalysis:
   Segfault happened at: 0x7fcc7470147a :movdqu (%rax),%xmm12
   PC (0x7fcc7470147a) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-datetime
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   
unity::indicator::datetime::PlannerEds::Impl::my_get_appointments_foreach(_ECalComponent*,
 long, long, void*) ()
   ?? () from /usr/lib/libecal-1.2.so.16
   ?? () from /usr/lib/libecal-1.2.so.16
   ?? () from /usr/lib/libecal-1.2.so.16
  Title: indicator-datetime-service crashed with SIGSEGV in strlen()
  UpgradeStatus: Upgraded to trusty on 2014-01-06 (38 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Dx-packages] [Bug 1281297] [NEW] Scale/Spread Search does not use applications name

2014-02-17 Thread Brandon Schaefer

Public bug reported:

To reproduce:

1) Open 2 gnome-terminal
2) Super+W (to go into scale mode)
3) type "terminal"

Expected:
  The 2 gnome-terminals to be left as valid matches.

Result:
  Empty search results on the gnome-terminals.

** Affects: unity
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Triaged

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

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

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

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

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

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

** Changed in: unity
   Importance: Undecided => Medium

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281297

Title:
  Scale/Spread Search does not use applications name

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  To reproduce:

  1) Open 2 gnome-terminal
  2) Super+W (to go into scale mode)
  3) type "terminal"

  Expected:
The 2 gnome-terminals to be left as valid matches.

  Result:
Empty search results on the gnome-terminals.

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

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

[Dx-packages] [Bug 1281321] [NEW] compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

Public bug reported:

This happened after an upgrade from fresh 13.10 to devel sources (I can
link my sources.list if necessary). I'm on a new Lenovo IdeaPad Y510P
with dual graphics. The upgrade got the open source NVIDIA drivers
working (the screen is at full resolution), but there are no window
decorations (I would take a screenshot, but...). In any case, I will see
if this is resolved on a reboot.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140217-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Feb 17 14:38:16 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-02-16 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f64e2a5ed50 <__memmove_ssse3_back+80>:movdqu 
(%rsi),%xmm0
 PC (0x7f64e2a5ed50) ok
 source "(%rsi)" (0x52175af4) not located in a known VMA region (needed 
readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, unsigned 
long, boost::function const&, boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
 TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
 TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace trusty

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281321

Title:
  compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

Status in “unity” package in Ubuntu:
  New

Bug description:
  This happened after an upgrade from fresh 13.10 to devel sources (I
  can link my sources.list if necessary). I'm on a new Lenovo IdeaPad
  Y510P with dual graphics. The upgrade got the open source NVIDIA
  drivers working (the screen is at full resolution), but there are no
  window decorations (I would take a screenshot, but...). In any case, I
  will see if this is resolved on a reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Feb 17 14:38:16 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-02-16 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f64e2a5ed50 <__memmove_ssse3_back+80>:  movdqu 
(%rsi),%xmm0
   PC (0x7f64e2a5ed50) ok
   source "(%rsi)" (0x52175af4) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281321/+subscriptions

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

[Dx-packages] [Bug 1281325] [NEW] System setting icons are duplicated in Dash

Public bug reported:

I will attach a screenshot when my desktop works properly again (see my
bugs for details). The System Settings icon and all its children
(Keyboard, Mouse and Touchpad, Security and Privacy, etc. [but not their
children: There is only one Language icon]) are duplicated in the Dash.

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281325

Title:
  System setting icons are duplicated in Dash

Status in “unity” package in Ubuntu:
  New

Bug description:
  I will attach a screenshot when my desktop works properly again (see
  my bugs for details). The System Settings icon and all its children
  (Keyboard, Mouse and Touchpad, Security and Privacy, etc. [but not
  their children: There is only one Language icon]) are duplicated in
  the Dash.

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

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

[Dx-packages] [Bug 1281321] Re: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1055166
   compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from 
dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() 
from ... from unity::UnityWindow::DrawWindowDecoration

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1281321

Title:
  compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()

Status in “unity” package in Ubuntu:
  New

Bug description:
  This happened after an upgrade from fresh 13.10 to devel sources (I
  can link my sources.list if necessary). I'm on a new Lenovo IdeaPad
  Y510P with dual graphics. The upgrade got the open source NVIDIA
  drivers working (the screen is at full resolution), but there are no
  window decorations (I would take a screenshot, but...). In any case, I
  will see if this is resolved on a reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Feb 17 14:38:16 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-02-16 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f64e2a5ed50 <__memmove_ssse3_back+80>:  movdqu 
(%rsi),%xmm0
   PC (0x7f64e2a5ed50) ok
   source "(%rsi)" (0x52175af4) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
   TfpTexture::bindPixmapToTexture(unsigned long, int, int, int, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  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/ubuntu/+source/unity/+bug/1281321/+subscriptions

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

[Dx-packages] [Bug 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from

I was able to solve this by installing the latest proprietary drivers
for my graphics cards.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1055166

Title:
  compiz crashed with SIGSEGV in memmove() from
  drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator()
  from compiz::opengl::bindTexImageGLX() from ... from
  unity::UnityWindow::DrawWindowDecoration

Status in Mesa:
  Invalid
Status in Unity:
  Triaged
Status in Unity 6.0 series:
  Triaged
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  See also bug 927168, which was resolved recently.

  Compiz crashed after installed something via Synaptic and just it
  installed that i want it crashed coz i want to see  the black
  installition screen

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sun Sep 23 21:36:37 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi)
   PC (0x7f031d57d73c) ok
   source "%xmm1" ok
   destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, 
unsigned long, boost::function const&, 
boost::function const&, boost::function const&, 
compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so
   TfpTexture::bindTexImage(unsigned long const&) () from 
/usr/lib/compiz/libopengl.so
  Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 
11
   gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly
   gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Dx-packages] [Bug 1281325] Re: System setting icons are duplicated in Dash