[Dx-packages] [Bug 1017595] Re: In the calendar, today's date needs more contrast to distinguish itself from the other days

[Alex]

Confirms bug on Ubuntu 14.04 Trusty

-- 
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, dx-packages
https://bugs.launchpad.net/bugs/1017595

Title:
  In the calendar, today's date needs more contrast to distinguish
  itself from the other days

Status in Ayatana Design:
  Fix Committed
Status in Indicator Display Objects:
  Triaged
Status in The Date and Time Indicator:
  Triaged
Status in Themes for Ubuntu:
  New
Status in “ido” package in Ubuntu:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Triaged
Status in “ubuntu-themes” package in Ubuntu:
  Confirmed

Bug description:
  In usability testing, participants have commented on the fact that
  they cannot see today's date at a glance because there is not enough
  contrast between today's date that is highlighted and the rest of the
  calendar.

  Screenshot from duplicate bug 1280874:
  https://launchpadlibrarian.net/166456917/Selection_452.png

  https://wiki.ubuntu.com/TimeAndDate#menu-calendar: If a date item
  is the currently highlighted menu item, it should have the normal text
  and background highlight colors for a menu item. If a date has at
  least one event, its text should be bold. And today’s date should have
  a thin border around it in the unhighlighted text color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1017595/+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 968533] Re: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU

[Pellaeon Lin]

I still experience this in 14.04, not only alt-tab triggers this, simply
switching workspaces also does.

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

Title:
  Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to
  80% CPU and hud-service to 20-80% CPU

Status in Unity:
  Confirmed
Status in “indicator-appmenu” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I've been seeing UI hangs after switching tabs in Firefox, and
  switching from other applications to Firefox.

  It can take 3-8 seconds to change *tab*.  During this time the CPU is
  maxed out;  typical output from 'top' during this period shows 'hud-
  service' and 'unity-panel-service' combined using about the same CPU
  as Firefox itself:

   100 10.4  26:07.73 firefox
53  0.6   6:14.86 hud-service
38  1.5   6:42.14 unity-panel-service

  I suspect that the change is causing a (an inefficient) re-index
  related to updated menu structures.  (Eg. something like the history
  menu, although I can't see what it is as don't currently have a menu
  bar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/968533/+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 1300098] Re: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

[Apport retracing service]

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

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 #1194465, 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/1300098/+attachment/4055165/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1300098/+attachment/4055166/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1300098/+attachment/4055167/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1300098/+attachment/4055168/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1300098/+attachment/4055169/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1300098/+attachment/4055170/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1300098/+attachment/4055171/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1194465
   scope-runner-dbus.py crashed with SIGSEGV in 
auth_session_remote_object_destroyed_cb()

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

Title:
  scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

Status in “libunity” package in Ubuntu:
  New

Bug description:
  The bug report message just popped up directly after i upgraded my
  system with the update manager.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-scopes-runner 7.1.4+14.04.20140210-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 10:46:27 2014
  Dependencies:
   
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
  InstallationDate: Installed on 2014-03-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s 
files/gdrive.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7ff59fb339ae:cmp%rbp,(%rax)
   PC (0x7ff59fb339ae) ok
   source %rbp ok
   destination (%rax) (0x90001) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
  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/1300098/+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 1300099] [NEW] Color of choosen text in DASH should be in theme-matching color

[Tommy_CZ]

Public bug reported:

Hi, I think the color of choosen text in search place in DASH should be
something more matching the theme of Ubuntu, than to be justGREY.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.3-0ubuntu1
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,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Mar 31 10:25:10 2014
DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:365e]
InstallationDate: Installed on 2014-02-10 (48 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
MachineType: LENOVO 10104
ProcEnviron:
 LANGUAGE=cs
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-03-18 (13 days ago)
dmi.bios.date: 03/21/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: ELKT31AUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: 3193 STD
dmi.chassis.type: 13
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
dmi.product.name: 10104
dmi.product.version: Lenovo C440
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Mar 31 10:24:17 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8192 
 vendor LEN
xserver.version: 2:1.15.0-1ubuntu7

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


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

** Summary changed:

- Colour of choosen text in DASH should be in theme-matching color
+ Color of choosen text in DASH should be in theme-matching color

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

Title:
  Color of choosen text in DASH should be in theme-matching color

Status in “unity” package in Ubuntu:
  New

Bug description:
  Hi, I think the color of choosen text in search place in DASH should
  be something more matching the theme of Ubuntu, than to be
  justGREY.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar 31 10:25:10 2014
  DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:365e]
  InstallationDate: Installed on 2014-02-10 (48 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS 

[Dx-packages] [Bug 1291088] Re: Doesn't unlock when coming back from the greeter

[Sebastien Bacher]

Do you have a locally hacked gnome-screensaver version again? ;-) (you
tried with a guest session right?) Could you try with the archive
version?

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

Title:
  Doesn't unlock when coming back from the greeter

Status in GNOME Screensaver:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Using the new unity-lock-screen from the current candidate version:
  - run unity on a system with multiple users
  - click on another user in indicator-session

  - the greeter is displayed with that user selected, so you can type
  the password to log in

  - select back your user and enter the password to unlock the session

  - what happens: the session is unlocked then locked again just after that
  - what should happen: the session should stay unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1291088/+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 1291088] Re: Doesn't unlock when coming back from the greeter

[Michał Sawicz]

I still get it to lock after unlocking after a suspend :/

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

Title:
  Doesn't unlock when coming back from the greeter

Status in GNOME Screensaver:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Using the new unity-lock-screen from the current candidate version:
  - run unity on a system with multiple users
  - click on another user in indicator-session

  - the greeter is displayed with that user selected, so you can type
  the password to log in

  - select back your user and enter the password to unlock the session

  - what happens: the session is unlocked then locked again just after that
  - what should happen: the session should stay unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1291088/+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 1291088] Re: Doesn't unlock when coming back from the greeter

[Giovanni Mellini]

The fix don't work for me too, I have a single account system with
default configuration

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

Title:
  Doesn't unlock when coming back from the greeter

Status in GNOME Screensaver:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Using the new unity-lock-screen from the current candidate version:
  - run unity on a system with multiple users
  - click on another user in indicator-session

  - the greeter is displayed with that user selected, so you can type
  the password to log in

  - select back your user and enter the password to unlock the session

  - what happens: the session is unlocked then locked again just after that
  - what should happen: the session should stay unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1291088/+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 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

[Alberto Salvia Novella]

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided = High

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

Title:
  compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ...
  from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()

Status in Unity:
  Confirmed
Status in “glib2.0” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Unity crashed when i was trying the Preview.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity 6.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic i686
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri Sep  7 18:49:48 2012
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb0d448c2 g_mount_spec_to_dbus_with_path+50:
mov0x4(%eax),%ebp
   PC (0xb0d448c2) ok
   source 0x4(%eax) (0x0005) not located in a known VMA region (needed 
readable region)!
   destination %ebp ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   g_mount_spec_to_dbus_with_path () from 
/usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so
  Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
  UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1047517/+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 1300189] [NEW] usage of webapps makes unity unresponsive properly to touches on touchscreen

[Tommy_CZ]

Public bug reported:

Hi, If I use touchscreen, I can move, resize windows, open DASH etc. If
I open webapp (like youtube, facebook etc. in unity browser), unity
unresponsive to touches, I cannot resize windows, switch between them by
tap on them, I cannot open DASH by click. I have to use mouse then.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.13.3-0ubuntu1
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,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Mar 31 11:31:08 2014
DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:365e]
InstallationDate: Installed on 2014-02-10 (48 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
MachineType: LENOVO 10104
ProcEnviron:
 LANGUAGE=cs
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-03-18 (13 days ago)
dmi.bios.date: 03/21/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: ELKT31AUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: 3193 STD
dmi.chassis.type: 13
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
dmi.product.name: 10104
dmi.product.version: Lenovo C440
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Mar 31 10:24:17 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8192 
 vendor LEN
xserver.version: 2:1.15.0-1ubuntu7

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


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

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

Title:
  usage of webapps makes unity unresponsive properly to touches on
  touchscreen

Status in “unity” package in Ubuntu:
  New

Bug description:
  Hi, If I use touchscreen, I can move, resize windows, open DASH etc.
  If I open webapp (like youtube, facebook etc. in unity browser), unity
  unresponsive to touches, I cannot resize windows, switch between them
  by tap on them, I cannot open DASH by click. I have to use mouse then.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar 31 11:31:08 2014
  DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 

[Dx-packages] [Bug 1298431] [NEW] window switcher randomly switches windows

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

on ubuntu 14.04 trusty, when more than one window are open in one
workspace, sometimes another window is brought on top. you can see the
window switching animation like you would see when alt-tabbing.

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


** Tags: bot-comment
-- 
window switcher randomly switches windows
https://bugs.launchpad.net/bugs/1298431
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

-- 
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 1298431] Re: window switcher randomly switches windows

[Brian Murray]

** Package changed: ubuntu = unity (Ubuntu)

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

Title:
  window switcher randomly switches windows

Status in “unity” package in Ubuntu:
  New

Bug description:
  on ubuntu 14.04 trusty, when more than one window are open in one
  workspace, sometimes another window is brought on top. you can see the
  window switching animation like you would see when alt-tabbing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298431/+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 723167] Re: Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance theme.

[Treviño]

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

** Changed in: unity
Milestone: None = 7.2.0

** Changed in: unity
   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/723167

Title:
  Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance
  theme.

Status in Ayatana Design:
  Invalid
Status in Cairo Graphics Library:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Since the switch to a theme-aware panel, the Unity panel uses very
  fuzzy fonts. The actual submenus in the global menu bar, as well as
  the indicators look fine, but the top-level menu entries, time, name
  in me-menu, and the window title look fuzzy. Presumably this is
  because it doesn't use the configured Pango font anti-aliasing as the
  rest of GTK, as these are rendered by nux?

  This is Unity 3.4.4 on current Natty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/723167/+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 1299774] [NEW] Typing is slow in Unity DASH

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi, when I wrote for example ubuntu-bug unity-webapps and then want to
go back, it is slow. I push left arrow then for few seconds, remove
finger and it still moves for about a second! ;) Not a critical bug
but... you know.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop 1.322
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 30 16:07:28 2014
InstallationDate: Installed on 2014-03-29 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
ProcEnviron:
 LANGUAGE=cs
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty
-- 
Typing is slow in Unity DASH
https://bugs.launchpad.net/bugs/1299774
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

-- 
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 1299774] Re: Typing is slow in Unity DASH

[Brian Murray]

** Package changed: ubuntu-meta (Ubuntu) = unity (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
https://bugs.launchpad.net/bugs/1299774

Title:
  Typing is slow in Unity DASH

Status in “unity” package in Ubuntu:
  New

Bug description:
  Hi, when I wrote for example ubuntu-bug unity-webapps and then want to
  go back, it is slow. I push left arrow then for few seconds, remove
  finger and it still moves for about a second! ;) Not a critical bug
  but... you know.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop 1.322
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 30 16:07:28 2014
  InstallationDate: Installed on 2014-03-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1299774/+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 1291088] Re: Doesn't unlock when coming back from the greeter

[Andrea Azzarone]

Seb, yeah pretty sure it's a normal gnome-screensaver. Maybe just with
different settings?

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

Title:
  Doesn't unlock when coming back from the greeter

Status in GNOME Screensaver:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Using the new unity-lock-screen from the current candidate version:
  - run unity on a system with multiple users
  - click on another user in indicator-session

  - the greeter is displayed with that user selected, so you can type
  the password to log in

  - select back your user and enter the password to unlock the session

  - what happens: the session is unlocked then locked again just after that
  - what should happen: the session should stay unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1291088/+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 1291243] Re: compiz crashed with SIGSEGV in TfpTexture::releaseTexImage()

[Stephen M. Webb]

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

Title:
  compiz crashed with SIGSEGV in TfpTexture::releaseTexImage()

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Spread wasn't working anymore, so I performed compiz --replace, then
  shut the terminal again, then this error came up.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 12 09:50:25 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2011-10-08 (885 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111007.1)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f20ec8d596e 
_ZN10TfpTexture15releaseTexImageEv+30:mov(%rdi),%rax
   PC (0x7f20ec8d596e) ok
   source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   TfpTexture::releaseTexImage() () from /usr/lib/compiz/libopengl.so
   TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so
   TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so
   GLTexture::List::clear() () from /usr/lib/compiz/libopengl.so
   unity::PluginAdapter::InitiateScale(std::string const, int) () from 
/usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in TfpTexture::releaseTexImage()
  UpgradeStatus: Upgraded to trusty on 2014-03-09 (2 days ago)
  UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare saned 
scanner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291243/+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 1275524] Re: notify-osd crashed with signal 5 in _XReply()

[Cavsfan]

I just got this error again today. I woke it from suspend and it got
this error.

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

Title:
  notify-osd crashed with signal 5 in _XReply()

Status in “notify-osd” package in Ubuntu:
  Confirmed

Bug description:
  This occurred while I was away from the pc no other info.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.04.20140117.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Feb  2 11:24:12 2014
  DesktopSession: 'ubuntu'
  ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd
  GtkTheme: 'Ambiance'
  IconTheme: 'buuf3.10'
  InstallationDate: Installed on 2014-01-08 (24 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
  ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.0~git20140131.1d53603f-0ubuntu0sarvatt
   libdrm2  2.4.52+git20140121.46d451c9-0ubuntu0sarvatt
   xserver-xorg-video-intel 2:2.99.907+git20140131.f934ee78-0ubuntu0sarvatt
   xserver-xorg-video-ati   1:7.3.0-1ubuntu1
  Signal: 5
  SourcePackage: notify-osd
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: notify-osd crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G31M3-L V2(MS-7529)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7529
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1275524/+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 1300330] Re: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::~trackable_callback_list()

[Apport retracing service]

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

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 #927099, 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/1300330/+attachment/4055968/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1300330/+attachment/4055970/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1300330/+attachment/4055972/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1300330/+attachment/4055973/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1300330/+attachment/4055974/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1300330/+attachment/4055975/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1300330/+attachment/4055976/+files/ThreadStacktrace.txt

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

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

Title:
  compiz crashed with SIGSEGV in
  sigc::internal::trackable_callback_list::~trackable_callback_list()

Status in “unity” package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 18:07:53 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-28 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f8ade221ac8 
_ZN4sigc8internal23trackable_callback_listD2Ev+24:mov0x18(%rbx),%rax
   PC (0x7f8ade221ac8) ok
   source 0x18(%rbx) (0x0018) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   sigc::internal::trackable_callback_list::~trackable_callback_list() () from 
/usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
   sigc::trackable::notify_callbacks() () from 
/usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
   sigc::slot_base::~slot_base() () from 
/usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
   sigc::internal::signal_impl::sweep() () from 
/usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
   sigc::internal::signal_impl::notify(void*) () from 
/usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0
  Title: compiz crashed with SIGSEGV in 
sigc::internal::trackable_callback_list::~trackable_callback_list()
  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/1300330/+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 1299706] Re: distortions in Unity after lock screen

[Jamie Strandboge]

** Information type changed from Private Security 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/1299706

Title:
  distortions in Unity after lock screen

Status in “unity” package in Ubuntu:
  New

Bug description:
  Hi, I locked my Ubuntu, then I unlocked it, opened DASH, then it lock again 
without my will as I describe in bug report #1299705 .
  The problem is, Unity is not rendered good in MacbookAir with sandy bridge, 
because if I do this:
  Lock screen - unlock - open DASH - then it locks without my will . 
in MacbookAir it do NOT show me it is locked, all I can see it something that 
left from DASH with black background, without left panel but WITH top panel.

  I think this can be a security issue because in this point I cannot
  know I am on lockscreen or not and so typing password can be
  dangerous.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  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]
  CurrentDesktop: Unity
  Date: Sun Mar 30 10:36:01 2014
  InstallationDate: Installed on 2014-03-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317)
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1299706/+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 1281825] Re: New decorations add a shadow to apps that don't even have a decoration

[Brandon Schaefer]

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

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

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

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

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

Title:
  New decorations add a shadow to apps that don't even have a decoration

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Weird shadow is rendered on apps that don't use a traditional window
  decoration. I've attached a screenshot of synapse as an example.

  I think this was introduced by the new CSD implementation in Unity for
  Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1281825/+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 1300350] [NEW] middle mouse button on window title bar does not push the window to the background

[Chris]

Public bug reported:

It seems that unlike any previous Ubuntu version the following feature will not 
work on Trusty Tahr:
When you use the middle mouse button (usually the scroll wheel) on a window's 
title bar it used to be put in the background, revealing the windows  that 
where right below it. This seems to be gone. Right now the middle click has no 
useful function on my install. I can only guess this might be connected locally 
integrated menus which have been introduced this cycle, so I'm opening this 
against Unity - hope thats correct. In any case I'm not using locally 
integrated menus but the default global menus.

I'd really hope to see this function return as it is an efficient and
easy windows management feature.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Mar 31 19:12:00 2014
InstallationDate: Installed on 2014-02-15 (44 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140214)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  middle mouse button on window title bar does not push the window to
  the background

Status in “unity” package in Ubuntu:
  New

Bug description:
  It seems that unlike any previous Ubuntu version the following feature will 
not work on Trusty Tahr:
  When you use the middle mouse button (usually the scroll wheel) on a window's 
title bar it used to be put in the background, revealing the windows  that 
where right below it. This seems to be gone. Right now the middle click has no 
useful function on my install. I can only guess this might be connected locally 
integrated menus which have been introduced this cycle, so I'm opening this 
against Unity - hope thats correct. In any case I'm not using locally 
integrated menus but the default global menus.

  I'd really hope to see this function return as it is an efficient and
  easy windows management feature.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Mar 31 19:12:00 2014
  InstallationDate: Installed on 2014-02-15 (44 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140214)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300350/+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 1300352] Re: notification-daemon crashed with signal 5 in g_source_remove()

[Apport retracing service]

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

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 #1282186, 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/1300352/+attachment/4056017/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1300352/+attachment/4056019/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1300352/+attachment/4056020/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1300352/+attachment/4056021/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1300352/+attachment/4056022/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1300352/+attachment/4056023/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1300352/+attachment/4056024/+files/ThreadStacktrace.txt

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

** 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 notification-daemon in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1300352

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

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

Bug description:
  Received this error after updating from ubuntu updates.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: notification-daemon 0.7.6-1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Mar 31 13:06:40 2014
  ExecutablePath: /usr/lib/notification-daemon/notification-daemon
  InstallationDate: Installed on 2014-03-17 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140316)
  ProcCmdline: /usr/lib/notification-daemon/notification-daemon
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: notification-daemon
  StacktraceTop:
   g_source_remove () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_cclosure_marshal_VOID__VOID () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-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/1300352/+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 723167] Re: Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance theme.

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity/fuzzy-deco-text-fix

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

Title:
  Fuzzy fonts caused by Cairo antialiasing artifacts with Radiance
  theme.

Status in Ayatana Design:
  Invalid
Status in Cairo Graphics Library:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Since the switch to a theme-aware panel, the Unity panel uses very
  fuzzy fonts. The actual submenus in the global menu bar, as well as
  the indicators look fine, but the top-level menu entries, time, name
  in me-menu, and the window title look fuzzy. Presumably this is
  because it doesn't use the configured Pango font anti-aliasing as the
  rest of GTK, as these are rendered by nux?

  This is Unity 3.4.4 on current Natty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/723167/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

[Christian S.]

OK you are right. I opened a ticket for those the fix in comment #6 does not 
work and the issue appears when a external monitor is connected when login 
(e.g. as described in #77 and 76):
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1300393

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

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  Confirmed
Status in Release Notes for Ubuntu:
  Invalid
Status in “mesa” package in Ubuntu:
  Fix Released
Status in “nux” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  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 Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  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-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1222602/+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 1291737] Re: New lockscreen doesn't indicate when capslock is on

[Brandon Schaefer]

** Changed in: unity
 Assignee: (unassigned) = Brandon Schaefer (brandontschaefer)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Brandon Schaefer (brandontschaefer)

** Changed in: unity (Ubuntu)
   Importance: Medium = High

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

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

** Changed in: unity
   Importance: Medium = High

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

Title:
  New lockscreen doesn't indicate when capslock is on

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  The Unity greeter shows a warning sign in the password field when capslock is 
on. The old lockscreen does the same.
  The new lockscreen should also indicate when capslock is on.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Mar 13 03:24:59 2014
  InstallationDate: Installed on 2014-02-24 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1291737/+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 1296866] Re: Allow unity-panel.menuitem to paint window title text for maximized window in new Unity Decorator(Trusty)

[Treviño]

** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New = In Progress

** Changed in: unity
   Importance: Undecided = Medium

** 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: None = 7.2.0

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

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

** Changed in: ubuntu-themes
   Importance: Undecided = Medium

** Changed in: ubuntu-themes
 Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0)

** Changed in: ubuntu-themes
   Status: New = In Progress

** Branch linked: lp:~3v1n0/ubuntu-themes/unity-panel-colors

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

Title:
  Allow unity-panel.menuitem to paint window title text for maximized
  window in new Unity Decorator(Trusty)

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Some themes (Greybird, Elementary) use dark-panel  light window
  title-bar (When it is not maximized). As new Unity window decorator
  uses same title-bar foreground color for both normal  maximized
  windows, window title on unity-panel is not properly visible as it
  becomes dark-text on dark-panel. I have attached a screenshot.

  This forces theme developer to use use same background color for both
  unity-panel  un-maximized windows, which breaks theme design. The
  idea is that theme-developers like to think unity-panel as a panel 
  not just a title-bar for maximized window.

  According to https://wiki.ubuntu.com/Unity/Theming, color set in
  UnityDecoration.top is used for both unmaximized  maximized window.

  UnityDecoration.top {
   color: @dark_fg_color
  }

  And when this is set, the color set in .unity-panel.menuitem is
  ignored for window title text in panel (it still paints some other
  text in panel like indicator-datetime)

  .unity-panel .menuitem {
  border-width: 0 1px;
  color: @panel_fg_color; # this does not affect window title text 
anymore. 
  }

  This color (OR unity.panel foreground color in UnityPanelWidget)
  should be used to paint the window tile text for maximized window, as
  it used to be in old compiz-decorator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1296866/+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 1295821] Re: indicator-power-service crashed with SIGSEGV in g_object_unref()

[Launchpad Bug Tracker]

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

** Changed in: indicator-power (Ubuntu)
   Status: New = Confirmed

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

Title:
  indicator-power-service crashed with SIGSEGV in g_object_unref()

Status in “indicator-power” package in Ubuntu:
  Confirmed

Bug description:
  None

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140314-0ubuntu1
  Uname: Linux 3.14.0-031400rc6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 14 16:55:35 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
  InstallationDate: Installed on 2014-03-05 (15 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
  SegvAnalysis:
   Segfault happened at: 0x7f1532489c1c g_object_unref+12:mov
(%rdi),%rax
   PC (0x7f1532489c1c) ok
   source (%rdi) (0x0021) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-power
  StacktraceTop:
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_bus_unwatch_name () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
  Title: indicator-power-service crashed with SIGSEGV in g_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1295821/+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 1296866] Re: Allow unity-panel.menuitem to paint window title text for maximized window in new Unity Decorator(Trusty)

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity/panel-style-context-fix

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

Title:
  Allow unity-panel.menuitem to paint window title text for maximized
  window in new Unity Decorator(Trusty)

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Some themes (Greybird, Elementary) use dark-panel  light window
  title-bar (When it is not maximized). As new Unity window decorator
  uses same title-bar foreground color for both normal  maximized
  windows, window title on unity-panel is not properly visible as it
  becomes dark-text on dark-panel. I have attached a screenshot.

  This forces theme developer to use use same background color for both
  unity-panel  un-maximized windows, which breaks theme design. The
  idea is that theme-developers like to think unity-panel as a panel 
  not just a title-bar for maximized window.

  According to https://wiki.ubuntu.com/Unity/Theming, color set in
  UnityDecoration.top is used for both unmaximized  maximized window.

  UnityDecoration.top {
   color: @dark_fg_color
  }

  And when this is set, the color set in .unity-panel.menuitem is
  ignored for window title text in panel (it still paints some other
  text in panel like indicator-datetime)

  .unity-panel .menuitem {
  border-width: 0 1px;
  color: @panel_fg_color; # this does not affect window title text 
anymore. 
  }

  This color (OR unity.panel foreground color in UnityPanelWidget)
  should be used to paint the window tile text for maximized window, as
  it used to be in old compiz-decorator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1296866/+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 1269409] Re: Reenable closing apps from HUD

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/camera-app

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

Title:
  Reenable closing apps from HUD

Status in Camera App:
  In Progress
Status in Unity HUD:
  Fix Released
Status in Ubuntu UI Toolkit:
  Fix Released
Status in unity-action-api:
  Fix Released
Status in The Unity 8 shell:
  Won't Fix
Status in “camera-app” package in Ubuntu:
  New
Status in “hud” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
   Readd the closing functionality to HUD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1269409/+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 1269409] Re: Reenable closing apps from HUD

[Launchpad Bug Tracker]

This bug was fixed in the package camera-app -
2.9.1+14.04.20140331-0ubuntu1

---
camera-app (2.9.1+14.04.20140331-0ubuntu1) trusty; urgency=low

  [ Bill Filler ]
  * updated framework version
  * change check for desktopMode to use platform name rather than env
var

  [ Pete Woods ]
  * Handle the HUD quit signal This change is only necessary for apps
that don't use the UITK MainView (LP: #1269409)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Mon, 31 Mar 2014 
16:39:21 +

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

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

Title:
  Reenable closing apps from HUD

Status in Camera App:
  In Progress
Status in Unity HUD:
  Fix Released
Status in Ubuntu UI Toolkit:
  Fix Released
Status in unity-action-api:
  Fix Released
Status in The Unity 8 shell:
  Won't Fix
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “hud” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
   Readd the closing functionality to HUD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1269409/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage

[Colin King]

** Changed in: ubuntu-power-consumption
   Status: New = 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, dx-packages
https://bugs.launchpad.net/bugs/1199877

Title:
  unity-panel-service memory leak and 100% CPU usage

Status in The Application Menu:
  Fix Released
Status in Application Menu Indicator 13.10 series:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in Unity:
  Invalid
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “indicator-appmenu” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+3.0” source package in Saucy:
  Fix Released
Status in “indicator-appmenu” source package in Saucy:
  Fix Released

Bug description:
  Impact: high CPU/memory usage from unity-panel-service

  Test case:

  Open a large image in the GIMP and activate a lot of items from the
  global menu. Using shortcuts is enough and faster to reproduce this
  bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity-
  panel-service increases steadily and it uses a lot of CPU shortly
  after activating the menu items in a short time.

  Regression potential: check that the menus are stable/working as they
  should

  -
  Just going about my business on Ubuntu Raring amd64 on an x230 and I heard 
the fan kick into action.  top showed me that unity-panel-service was consuming 
all the free cycles on one of my CPUs.  I killed it before my machine 
overheated, so I didn't attach a debugger to see why it was totally pegging out 
a  CPU.

  I'm not sure if this adds any context, but I was using a LibreOffice
  spreadsheet and I could not insert a table because the menu had lost
  it's mind, and then I observed the overly loaded CPU a very short
  while after that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1234289] Re: accounts-daemon is progressively causing more wakeups over time

[Colin King]

** Changed in: ubuntu-power-consumption
   Status: New = Fix Released

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

Title:
  accounts-daemon is progressively causing more wakeups over time

Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in “accountsservice” package in Ubuntu:
  Fix Released

Bug description:
  Over the past few months accounts-daemon has been increasing the
  number of wakeup events it generates, see:

  http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task
  /accounts-daemon/details/

  In April 2013 it was averaging about 13.5 wakeups per minute, now it
  has increased to 17.5.  This isn't much overall, but it does seem like
  the trend is upwards and every wakeup takes the CPU out of deep sleep
  and hence consumes a little more power.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1234289/+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 1292041] Re: Lockscreen doesn't turn off the screen

[Pausanias]

Is there a workaround?

Better question: is there any hope of GNOME developers *not* breaking
critical functionality from release to release? After 12 years with
Ubuntu, I can come up with a huge list of extremely frustrating and
sometimes downright dangerous regressions, almost all of them in GNOME,
and almost all of them affecting a feature that was working perfectly
well in a previous release.

/rant

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

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Invalid
Status in Unity Greeter:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't trun off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292041] Re: Lockscreen doesn't turn off the screen

[Pausanias]

** Also affects: unity-greeter
   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/1292041

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Invalid
Status in Unity Greeter:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't trun off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

[Nelson Elhage]

This also just affected me.

Possibly-relevant detail from my environment: If I explicitly lock the
screen and then also wait for a lock timeout, I somehow end up with two
lock screens -- I unlock the machine, I can interact with the desktop
for a few seconds, and then a second lock screen pops up. When I hit
this bug, I'd unlocked the first lock screen but not the second.

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

Title:
  lightdm screen lock has triggered but keyboard is still connected to
  the main session

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop which has screensaved naturally due to timeout (most
  likely) and it is sitting there showing the lock screen but keyboard
  is still connected to the session, I can alt-tab to applications and
  via IRC i was able to send myself messages (blind) so clearly the
  keyboard is really operational.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 13 20:56:10 2014
  EcryptfsInUse: Yes
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292217/+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 1300494] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()

[Apport retracing service]

*** 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/1300494/+attachment/4056726/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1300494/+attachment/4056728/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1300494/+attachment/4056730/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1300494/+attachment/4056731/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1300494/+attachment/4056732/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1300494/+attachment/4056733/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1300494/+attachment/4056734/+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/1300494

Title:
  compiz crashed with SIGSEGV in FT_Load_Glyph()

Status in “unity” package in Ubuntu:
  New

Bug description:
  Compiz crashed and restarted.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 10:04:14 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-03-21 (10 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7f60e822f860:mov%rdx,0x10(%rax)
   PC (0x7f60e822f860) 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: Upgraded to trusty on 2014-03-28 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300494/+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 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

[Seth Arnold]

Nelson, thanks; I believe the double-lock bug is tracked here:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451

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

Title:
  lightdm screen lock has triggered but keyboard is still connected to
  the main session

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop which has screensaved naturally due to timeout (most
  likely) and it is sitting there showing the lock screen but keyboard
  is still connected to the session, I can alt-tab to applications and
  via IRC i was able to send myself messages (blind) so clearly the
  keyboard is really operational.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 13 20:56:10 2014
  EcryptfsInUse: Yes
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292217/+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 1073114] Re: Online Smart Scopes Do Not Respect User Privacy

[mlaverdiere]

It seems that this bug is partially solved, at least for the upcoming
Unity 8 (so not for Ubuntu 14.04) where the Amazon scope activation will
become opt-in:  http://www.omgubuntu.co.uk/2014/03/ubuntu-make-amazon-
product-results-opt-unity

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

Title:
  Online Smart Scopes  Do Not Respect User Privacy

Status in “libunity” package in Ubuntu:
  Confirmed
Status in “unity-lens-shopping” package in Ubuntu:
  Confirmed
Status in “libunity” source package in Quantal:
  Confirmed
Status in “unity-lens-shopping” source package in Quantal:
  Confirmed
Status in “libunity” source package in Raring:
  Confirmed
Status in “unity-lens-shopping” source package in Raring:
  Confirmed

Bug description:
  See this from the Electronic Frontier Foundation (EFF), a well
  respected international non-profit digital rights advocacy and legal
  organization (as described on Wikipedia):
  https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads-
  and-data-leaks

  Obviously, despite some improvements that have came late in the 12.10
  development cycle, there are still serious privacy concerns with the
  unity shopping lens.  To be more precise, here are the main problems
  to be fixed according to EFF:

  - Disable Include online search results by default.

  - Explain in detail what Canonical does with search queries and IP
  addresses, how long it stores them, and in what circumstances it gives
  them to third parties.

  - Make the Search Results tab of the Privacy settings let users toggle
  on and off specific online search results, as some users might want
  Amazon products in their search results, but never anything from
  Facebook.

  Here is another related bug:

   #1055952 Direct data leaking to Amazon:
  https://bugs.launchpad.net/ubuntu/+source/unity-lens-
  shopping/+bug/1055952

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-lens-shopping 6.8.0-0ubuntu1
  Uname: Linux 3.5.6-030506-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Oct 30 06:35:38 2012
  InstallationDate: Installed on 2012-02-12 (260 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: unity-lens-shopping
  UpgradeStatus: Upgraded to quantal on 2012-09-28 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1073114/+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 1300514] [NEW] Account with UID 501 disappeared after update

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After today performing a system update from 13.10 [previously updated
cca 1mo ago], my account with UID has disappeared from lightdm.

/etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have all
been configured to treat users with minimum UID 500 as regular users.

The remark in users.conf mentioning AccountsService gave me a hint to
explore what this service is.  It's very nasty that this completely
opaque and unknown service determines whether an account will appear on
the list or not.

Digging around its process /usr/lib/accountsservice/accounts-daemon
(what a nasty place to put this binary) using strace, I noticed
/var/lib/AccountsService/users/myusername is being accessed. This may be
obvious to developers, but to someone troubleshooting, it's bad and
unexpected.

I fixed my issue by editing the aforementioned file and replacing
SystemAccount=true with SystemAccount=false, killing the accounts-
daemon and (to avoid restart) starting it in terminal. This would all be
worth just a rant instead of a bug report, were it not for the fact that
only today have I logged in correctly from the main screen, updated the
system, and after only a reboot -- without touching or knowing about
/var/lib/AccountsService/users directory -- my account has disappeared.
Either this directory was automagically touched, or SystemAccount=true
previously didn't affect lightdm.

Please provide and expose a canonical and universal place to determine
minimum UID for the system to treat a user account as a human account.
Having three somewhat-documented files and none of them having effect
upon accountsservice is quite bad.

If this package is inappropriate for this bug report, please reassign.

[The reason why UID 1000 is no-good are OS X partitions -- on which I'd
like to be able to access my files without resorting to sudo voodoo. The
default UID on OS X happens to be 501.]

Package version: 0.6.34-0ubuntu6

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lightdm 1.8.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Apr  1 00:43:23 2014
InstallationDate: Installed on 2014-02-18 (41 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug saucy
-- 
Account with UID 501 disappeared after update
https://bugs.launchpad.net/bugs/1300514
You received this bug notification because you are a member of DX Packages, 
which is subscribed to accountsservice in Ubuntu.

-- 
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 1300514] Re: Account with UID 501 disappeared after update

[Robert Ancell]

Re-assigning to accountsservice as this is the service that lightdm
queries as to which users to show. Correct, we did change lightdm to
honour the SystemAccount flag which is what has caused this problem for
you.

** Package changed: lightdm (Ubuntu) = accountsservice (Ubuntu)

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

Title:
  Account with UID 501 disappeared after update

Status in “accountsservice” package in Ubuntu:
  New

Bug description:
  After today performing a system update from 13.10 [previously updated
  cca 1mo ago], my account with UID has disappeared from lightdm.

  /etc/login.defs, /etc/adduser.conf and /etc/lightdm/users.conf have
  all been configured to treat users with minimum UID 500 as regular
  users.

  The remark in users.conf mentioning AccountsService gave me a hint to
  explore what this service is.  It's very nasty that this completely
  opaque and unknown service determines whether an account will appear
  on the list or not.

  Digging around its process /usr/lib/accountsservice/accounts-daemon
  (what a nasty place to put this binary) using strace, I noticed
  /var/lib/AccountsService/users/myusername is being accessed. This may
  be obvious to developers, but to someone troubleshooting, it's bad and
  unexpected.

  I fixed my issue by editing the aforementioned file and replacing
  SystemAccount=true with SystemAccount=false, killing the accounts-
  daemon and (to avoid restart) starting it in terminal. This would all
  be worth just a rant instead of a bug report, were it not for the fact
  that only today have I logged in correctly from the main screen,
  updated the system, and after only a reboot -- without touching or
  knowing about /var/lib/AccountsService/users directory -- my account
  has disappeared. Either this directory was automagically touched, or
  SystemAccount=true previously didn't affect lightdm.

  Please provide and expose a canonical and universal place to determine
  minimum UID for the system to treat a user account as a human
  account. Having three somewhat-documented files and none of them
  having effect upon accountsservice is quite bad.

  If this package is inappropriate for this bug report, please reassign.

  [The reason why UID 1000 is no-good are OS X partitions -- on which
  I'd like to be able to access my files without resorting to sudo
  voodoo. The default UID on OS X happens to be 501.]

  Package version: 0.6.34-0ubuntu6

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.8.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Apr  1 00:43:23 2014
  InstallationDate: Installed on 2014-02-18 (41 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1300514/+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 1275524] Re: notify-osd crashed with signal 5 in _XReply()

[Apport retracing service]

** Tags added: bugpattern-needed

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

Title:
  notify-osd crashed with signal 5 in _XReply()

Status in “notify-osd” package in Ubuntu:
  Confirmed

Bug description:
  This occurred while I was away from the pc no other info.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.04.20140117.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Feb  2 11:24:12 2014
  DesktopSession: 'ubuntu'
  ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd
  GtkTheme: 'Ambiance'
  IconTheme: 'buuf3.10'
  InstallationDate: Installed on 2014-01-08 (24 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
  ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd
  ProcEnviron:
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.0~git20140131.1d53603f-0ubuntu0sarvatt
   libdrm2  2.4.52+git20140121.46d451c9-0ubuntu0sarvatt
   xserver-xorg-video-intel 2:2.99.907+git20140131.f934ee78-0ubuntu0sarvatt
   xserver-xorg-video-ati   1:7.3.0-1ubuntu1
  Signal: 5
  SourcePackage: notify-osd
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: notify-osd crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G31M3-L V2(MS-7529)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7529
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1275524/+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 1165420] Re: Unable to access indicators from HUD

[Theodore Dokos]

This was the only thing I ever used the HUD for, and it was the reason I
thought the HUD was fantastic. Removing this was an incredibly poor
decision.

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

Title:
  Unable to access indicators from HUD

Status in Ayatana Design:
  Confirmed
Status in Unity HUD:
  Confirmed
Status in “hud” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's 
Update Status option there, making status updates to Twitter easy and fast.
  I could also use HUD to change my status in Empathy from Available to Busy 
and vice-versa.

  In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when 
typing Update Status or Update
  Also writing Available Away or Busy no longer gives any results.

  Other indicators however are accessible and I can use HUD to Suspend
  my computer or to view Skype status or Ubuntu one indicator options.

  Repeating:
  1. Press alt key to start HUD
  2. Write Update status or Available

  What was expected:
  HUD should have shown options ether from Gwibber to Update Status or Empathy 
to change status to Available both available from the messaging indicator.

  What happened:
  HUD didn't find any results.

  Notes:
  I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm 
using proprietary fglrx drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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

Re: [Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager

[Turbo]

Hi,

I can confirm that comenting the line as he said, works as it should.

Just don't get it; if the solution is so easy, WHY this bug is alive
several years late.

Regards.

 Date: Sat, 29 Mar 2014 23:52:12 +
 From: 1201...@bugs.launchpad.net
 To: axe...@hotmail.com
 Subject: [Bug 1201180] Re: Pressing power button turns off the PC ignoring 
 the presence of another session manager
 
 In which case this bug is a duplicate of the long standing #1243399 and
 #268734
 
 -- 
 You received this bug notification because you are subscribed to a
 duplicate bug report (1124149).
 https://bugs.launchpad.net/bugs/1201180
 
 Title:
   Pressing power button turns off the PC ignoring the presence of
   another session manager
 
 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+subscriptions

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

Title:
  Pressing power button turns off the PC ignoring the presence of
  another session manager

Status in “acpid” package in Ubuntu:
  Triaged
Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling poweroff, but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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 1285614] Re: Mouse click offset

[Lucas Silveira Melo]

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Lucas Silveira Melo (lucas-silveiramelo)

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

Title:
  Mouse click offset

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

Bug description:
  In trusty, I have seen an old bug coming back: my mouse clicks suffer
  from an offset compared to what I see on screen.

  This is very similar to 
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/772612 but happening now 
in Trusty.
  This seems to happen after compiz somehow restarts spontaneously...

  I am conscious this is not a very usable bug report, but I have seen
  this happening 3 or 4 times in the last 2 days on my system, so I
  though it was worth reporting...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Feb 27 12:12:41 2014
  InstallationDate: Installed on 2013-02-16 (375 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1285614/+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 1300574] [NEW] Custom indicators not shown after restarting Unity

[hackel]

Public bug reported:

Tested on Unity 7.1.2+14.04.20140328.1-0ubuntu1

If Unity restarts, either by crashing or manually with restart unity-
panel-service or unity --replace, when Unity comes back, I can no
longer see my custom indicators.  I am still able to see the default
indicators (sync, messages, sound, datetime, and session), but not the
ones I have installed: sensors, cpufreq, multiload, weather, etc.  These
indicators are still running and appear in the process list, I just
can't see them in the panel.  I still see notifications from them.  If I
kill and restart any of these indicators, they run fine, but I still
cannot see them in the panel.  The only way I have found to get them
back is to completely log out and  back in.

I can't figure out what differentiates these custom indicators from
the default ones that would cause them not to appear.  With weather-
indicator, I even created an upstart job to control it.  If no one else
is able to reproduce this, please let me know how best to debug it
further.

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

Title:
  Custom indicators not shown after restarting Unity

Status in “unity” package in Ubuntu:
  New

Bug description:
  Tested on Unity 7.1.2+14.04.20140328.1-0ubuntu1

  If Unity restarts, either by crashing or manually with restart unity-
  panel-service or unity --replace, when Unity comes back, I can no
  longer see my custom indicators.  I am still able to see the default
  indicators (sync, messages, sound, datetime, and session), but not the
  ones I have installed: sensors, cpufreq, multiload, weather, etc.
  These indicators are still running and appear in the process list, I
  just can't see them in the panel.  I still see notifications from
  them.  If I kill and restart any of these indicators, they run fine,
  but I still cannot see them in the panel.  The only way I have found
  to get them back is to completely log out and  back in.

  I can't figure out what differentiates these custom indicators from
  the default ones that would cause them not to appear.  With weather-
  indicator, I even created an upstart job to control it.  If no one
  else is able to reproduce this, please let me know how best to debug
  it further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300574/+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 1073114] Re: Online Smart Scopes Do Not Respect User Privacy

[Benjamin Kerensa]

@mlaverdiere: I agree this announcement addresses any privacy concerns
users should have do we have a likely milestone to attach it to and is
it worth marking Fix Committed?

** Changed in: libunity (Ubuntu Quantal)
   Status: Confirmed = Won't Fix

** Changed in: libunity (Ubuntu Raring)
   Status: Confirmed = Won't Fix

** Changed in: unity-lens-shopping (Ubuntu Quantal)
   Status: Confirmed = Won't Fix

** Changed in: unity-lens-shopping (Ubuntu Raring)
   Status: Confirmed = Won't Fix

** Changed in: unity-lens-shopping (Ubuntu)
Milestone: None = later

** Changed in: libunity (Ubuntu)
Milestone: None = later

** Changed in: unity-lens-shopping (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: libunity (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  Online Smart Scopes  Do Not Respect User Privacy

Status in “libunity” package in Ubuntu:
  In Progress
Status in “unity-lens-shopping” package in Ubuntu:
  In Progress
Status in “libunity” source package in Quantal:
  Won't Fix
Status in “unity-lens-shopping” source package in Quantal:
  Won't Fix
Status in “libunity” source package in Raring:
  Won't Fix
Status in “unity-lens-shopping” source package in Raring:
  Won't Fix

Bug description:
  See this from the Electronic Frontier Foundation (EFF), a well
  respected international non-profit digital rights advocacy and legal
  organization (as described on Wikipedia):
  https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads-
  and-data-leaks

  Obviously, despite some improvements that have came late in the 12.10
  development cycle, there are still serious privacy concerns with the
  unity shopping lens.  To be more precise, here are the main problems
  to be fixed according to EFF:

  - Disable Include online search results by default.

  - Explain in detail what Canonical does with search queries and IP
  addresses, how long it stores them, and in what circumstances it gives
  them to third parties.

  - Make the Search Results tab of the Privacy settings let users toggle
  on and off specific online search results, as some users might want
  Amazon products in their search results, but never anything from
  Facebook.

  Here is another related bug:

   #1055952 Direct data leaking to Amazon:
  https://bugs.launchpad.net/ubuntu/+source/unity-lens-
  shopping/+bug/1055952

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-lens-shopping 6.8.0-0ubuntu1
  Uname: Linux 3.5.6-030506-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Oct 30 06:35:38 2012
  InstallationDate: Installed on 2012-02-12 (260 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: unity-lens-shopping
  UpgradeStatus: Upgraded to quantal on 2012-09-28 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1073114/+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