[Dx-packages] [Bug 1153250] Re: scrollbar overlay, cant scroll all the way down in softwarecenter for example

2015-03-30 Thread Launchpad Bug Tracker
[Expired for overlay-scrollbar (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: overlay-scrollbar (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  scrollbar overlay, cant scroll all the way down in softwarecenter for
  example

Status in overlay-scrollbar package in Ubuntu:
  Expired

Bug description:
  when using the mouse...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1153250/+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 1413206] Re: ctrl alt delete causes logout

2015-03-30 Thread Launchpad Bug Tracker
[Expired for Unity because there has been no activity for 60 days.]

** Changed in: unity
   Status: Incomplete => Expired

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

Title:
  ctrl alt delete causes logout

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  When I press ctrl alt delete on Ubuntu 14.10, unity shows the log out menu, 
where I can either lock or log out.
  However, even if I do nothing or close this menu, the system still logs out.
  So instead of only showing the menu, it seems to actually terminate the 
session.
  I'm not sure how to localize the package that is causing the problem.
  BTW: If I use the system menu to show this screen everything works as 
intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413206/+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 1413206] Re: ctrl alt delete causes logout

2015-03-30 Thread Launchpad Bug Tracker
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ctrl alt delete causes logout

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  When I press ctrl alt delete on Ubuntu 14.10, unity shows the log out menu, 
where I can either lock or log out.
  However, even if I do nothing or close this menu, the system still logs out.
  So instead of only showing the menu, it seems to actually terminate the 
session.
  I'm not sure how to localize the package that is causing the problem.
  BTW: If I use the system menu to show this screen everything works as 
intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413206/+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 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled

2015-03-30 Thread Nazar Mokrynskyi
Just ping to fix this annoying bug finally, should not be difficult.

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

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in rfkill package in Ubuntu:
  Incomplete
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1159249] Re: HUD does not show up over fullscreen window

2015-03-30 Thread Nazar Mokrynskyi
@azzar1, Just get Unity update, fix is not present, will it be available
in next release?

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

Title:
  HUD does not show up over fullscreen window

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

Bug description:
  [Impact]

  The HUD was not being rendered above fullscreen windows although it
  would grab the keyboard.

  [TEST CASE]

  1. Open some site in firefox

  2. Go to fullscreen mode (F11)

  3. Press "Alt" once.

  4  The HUD should appear and you should be able to interact with it.

  [REGRESSION POTENTIAL]

  No known regression potential.

  [OTHER INFO]

  The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid
  Vervet" dev release where it has been in production use for some time
  without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1159249/+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 1308265] Re: First password letter not registered in lockscreen if screen off

2015-03-30 Thread Stephen M. Webb
** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  First password letter not registered in lockscreen if screen off

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

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308265/+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 1029114] Re: With autohide and the HUD enabled the launcher can appear at incorrect times

2015-03-30 Thread Stephen M. Webb
** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  With autohide and the HUD enabled the launcher can appear at incorrect
  times

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

Bug description:
  Hi

  What Happened:
  1) Turn on launcher auto hide
  2) Display the HUD (tap Alt)
  3) Move the mouse to the left side of the screen (as if you are showing the 
launcher)
  4) Note the launcher is not displayed
  5) Now hide the HUD (either tap Alt or select the X in the top left corner)
  6) Note that the launcher is now displayed, after the HUD closes.

  What I expected to happen:
  - I expected that the launcher is not displayed at step 6.

  I expected for the launcher to not be displayed at step 6 because the
  user could have the HUD displayed for a long period of time then
  decide that they don't need the HUD. The launcher is then suddenly
  revealed to them as they moved their cursor to the left side of the
  screen a few minutes a ago. This could then confuse the user to why
  the launcher has appeared when all they did was close the HUD.

  Hope this can be fixed soon.

  Andy

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview]
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell]
  CrashDB: unity
  Date: Wed Jul 25 21:19:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2015-03-30 Thread Stephen M. Webb
** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  compiz crashed with SIGSEGV in XGetSelectionOwner()

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

Bug description:
  Running updated & current Vivid, on systemd and using Intel Haswell
  video.  Crash happened using Unity Tweak Tool after clicking Window
  Manager->General->Hardware Acceleration->Texture (dropdown).

  Screen. mouse and keyboard froze for several seconds, screen flashed
  off and on,  mouse and keyboard were functional.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 14 16:01:38 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-03-14 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f04575688dc :mov
0x968(%rdi),%rax
   PC (0x7f04575688dc) ok
   source "0x968(%rdi)" (0x3f803f4ce1ff) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   unity::XdndStartStopNotifierImp::OnTimeout() () from 
/usr/lib/compiz/libunityshell.so
   unity::glib::Source::SourceCallback(void*) () from 
/usr/lib/libunity-core-6.0.so.9
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in XGetSelectionOwner()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1432231/+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 1301394] Re: Launcher damange the left-monitor area also if it's hidden

2015-03-30 Thread Stephen M. Webb
** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  Launcher damange the left-monitor area also if it's hidden

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

Bug description:
  When in auto-hide mode the launcher damages the area that it would
  fill when shown, also when hidden.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301394/+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 926979] Re: compiz crashed with SIGSEGV in nux::Property::operator=(bool const&) from unity::dash::DashView::AnalyseLensURI(std::string const&) from unity::dash::DashView::OnA

2015-03-30 Thread Stephen M. Webb
** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  compiz crashed with SIGSEGV in nux::Property::operator=(bool
  const&) from unity::dash::DashView::AnalyseLensURI(std::string const&)
  from unity::dash::DashView::OnActivateRequest(_GVariant*)

Status in Unity:
  Fix Committed
Status in Unity 5.0 series:
  Triaged
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.0 series:
  Invalid
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Clicked dash, Internet applications.

  Opened a new bug as the others appear to suggest a fix is released for
  those bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Sun Feb  5 14:51:39 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7eff5ff51d10 <_ZN3nux8PropertyIbEaSERKb+32>: mov
0x18(%rdi),%rdi
   PC (0x7eff5ff51d10) ok
   source "0x18(%rdi)" (0x03f0) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   nux::Property::operator=(bool const&) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::AnalyseLensURI(std::string const&) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::OnActivateRequest(_GVariant*) () from 
/usr/lib/compiz/libunityshell.so
   unity::UBusManager::OnCallback(_GVariant*, void*) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in nux::Property::operator=()
  UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo 
usrp video

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/926979/+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 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

2015-03-30 Thread Stephen M. Webb
** Changed in: unity
   Status: In Progress => Fix Committed

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

Title:
  AP test failure:
  unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

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

Bug description:
  The following two AP tests consistently ERROR during regular Unity
  testing.

  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
  --
  Empty attachments:
/var/log/syslog

  unity-log: {{{WARN  2015-03-24 13:43:02 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
128, in test_scaled_window_closes_on_middle_click
  self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 113, in match
  wait_fun(self.matcher, self.timeout)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 129, in _callable_wait_for
  new_value = refresh_fn()
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
67, in 
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.screen.scaled_windows]
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 520, in __getattr__
  self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 474, in refresh_state
  _, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 564, in get_new_state
  raise StateNotFoundError(self.__class__.__name__, id=self.id)
  StateNotFoundError: Object not found with name 'Window' and properties {'id': 
148832}.
  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
  --
  Empty attachments:
/var/log/syslog

  unity-log: {{{WARN  2015-03-24 14:00:34 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
148, in test_scaled_window_closes_on_close_button_click
  self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 113, in match
  wait_fun(self.matcher, self.timeout)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 129, in _callable_wait_for
  new_value = refresh_fn()
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
67, in 
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.screen.scaled_windows]
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 520, in __getattr__
  self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 474, in refresh_state
  _, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 564, in get_new_state
  raise StateNotFoundError(self.__class__.__name__, id=self.id)
  StateNotFoundError: Object not found with name 'Window' and properties {'id': 
224517}.
  ==

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

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

[Dx-packages] [Bug 926979] Re: compiz crashed with SIGSEGV in nux::Property::operator=(bool const&) from unity::dash::DashView::AnalyseLensURI(std::string const&) from unity::dash::DashView::OnA

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  compiz crashed with SIGSEGV in nux::Property::operator=(bool
  const&) from unity::dash::DashView::AnalyseLensURI(std::string const&)
  from unity::dash::DashView::OnActivateRequest(_GVariant*)

Status in Unity:
  In Progress
Status in Unity 5.0 series:
  Triaged
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.0 series:
  Invalid
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Clicked dash, Internet applications.

  Opened a new bug as the others appear to suggest a fix is released for
  those bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unity 5.0.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Sun Feb  5 14:51:39 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcCmdline: compiz
  SegvAnalysis:
   Segfault happened at: 0x7eff5ff51d10 <_ZN3nux8PropertyIbEaSERKb+32>: mov
0x18(%rdi),%rdi
   PC (0x7eff5ff51d10) ok
   source "0x18(%rdi)" (0x03f0) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   nux::Property::operator=(bool const&) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::AnalyseLensURI(std::string const&) () from 
/usr/lib/compiz/libunityshell.so
   unity::dash::DashView::OnActivateRequest(_GVariant*) () from 
/usr/lib/compiz/libunityshell.so
   unity::UBusManager::OnCallback(_GVariant*, void*) () from 
/usr/lib/compiz/libunityshell.so
   ?? () from /usr/lib/compiz/libunityshell.so
  Title: compiz crashed with SIGSEGV in nux::Property::operator=()
  UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo 
usrp video

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/926979/+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 1301394] Re: Launcher damange the left-monitor area also if it's hidden

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  Launcher damange the left-monitor area also if it's hidden

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When in auto-hide mode the launcher damages the area that it would
  fill when shown, also when hidden.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301394/+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 1029114] Re: With autohide and the HUD enabled the launcher can appear at incorrect times

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  With autohide and the HUD enabled the launcher can appear at incorrect
  times

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

Bug description:
  Hi

  What Happened:
  1) Turn on launcher auto hide
  2) Display the HUD (tap Alt)
  3) Move the mouse to the left side of the screen (as if you are showing the 
launcher)
  4) Note the launcher is not displayed
  5) Now hide the HUD (either tap Alt or select the X in the top left corner)
  6) Note that the launcher is now displayed, after the HUD closes.

  What I expected to happen:
  - I expected that the launcher is not displayed at step 6.

  I expected for the launcher to not be displayed at step 6 because the
  user could have the HUD displayed for a long period of time then
  decide that they don't need the HUD. The launcher is then suddenly
  revealed to them as they moved their cursor to the left side of the
  screen a few minutes a ago. This could then confuse the user to why
  the launcher has appeared when all they did was close the HUD.

  Hope this can be fixed soon.

  Andy

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview]
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell]
  CrashDB: unity
  Date: Wed Jul 25 21:19:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1029114/+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 932486] Re: showing quicklist from launcher keynav mode focuses last application

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  showing quicklist from launcher keynav mode focuses last application

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

Bug description:
  To reproduce:

  0) Have at least one application window open
  1) Enter launcher keynav mode with Alt+F1

   * Note that when entering keynav mode, the application loses focus.
  THe triangle to the right of it's launcher icon is no longer drawn,
  and the window title is not displayed in the panel.

  2) Select a launcher icon with the Up or Down keys.
  3) Show the quicklist by pressing Right.

   * Note that the application becomes active again - it's window title
  is drawn to the panel, and the triangle to the right of the launcher
  icon is drawn again.

  4) Collapse the quicklist by pressing Left.

   * The app loses focus again.

  
  This seems like inconsistent behavior to me... either the app should never 
lose focus when we enter keynav mode, or should not be activated when we show a 
quicklist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/932486/+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 1308265] Re: First password letter not registered in lockscreen if screen off

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  First password letter not registered in lockscreen if screen off

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

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  compiz crashed with SIGSEGV in XGetSelectionOwner()

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Running updated & current Vivid, on systemd and using Intel Haswell
  video.  Crash happened using Unity Tweak Tool after clicking Window
  Manager->General->Hardware Acceleration->Texture (dropdown).

  Screen. mouse and keyboard froze for several seconds, screen flashed
  off and on,  mouse and keyboard were functional.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 14 16:01:38 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-03-14 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f04575688dc :mov
0x968(%rdi),%rax
   PC (0x7f04575688dc) ok
   source "0x968(%rdi)" (0x3f803f4ce1ff) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   unity::XdndStartStopNotifierImp::OnTimeout() () from 
/usr/lib/compiz/libunityshell.so
   unity::glib::Source::SourceCallback(void*) () from 
/usr/lib/libunity-core-6.0.so.9
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in XGetSelectionOwner()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1432231/+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 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

Title:
  AP test failure:
  unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  The following two AP tests consistently ERROR during regular Unity
  testing.

  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
  --
  Empty attachments:
/var/log/syslog

  unity-log: {{{WARN  2015-03-24 13:43:02 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
128, in test_scaled_window_closes_on_middle_click
  self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 113, in match
  wait_fun(self.matcher, self.timeout)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 129, in _callable_wait_for
  new_value = refresh_fn()
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
67, in 
  refresh_fn = lambda: xid in [w.xid for w in 
self.unity.screen.scaled_windows]
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 520, in __getattr__
  self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 474, in refresh_state
  _, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py", 
line 564, in get_new_state
  raise StateNotFoundError(self.__class__.__name__, id=self.id)
  StateNotFoundError: Object not found with name 'Window' and properties {'id': 
148832}.
  ==
  ERROR: 
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
  --
  Empty attachments:
/var/log/syslog

  unity-log: {{{WARN  2015-03-24 14:00:34 nux.inputmethod.ibus
  InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}

  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
148, in test_scaled_window_closes_on_close_button_click
  self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line 
68, in assertWindowIsScaledEquals
  self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in 
assertThat
  mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in 
_matchHelper
  mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py", 
line 113, in match
  wait_fun(self.matcher, s

[Dx-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.2+15.04.20150330-0ubuntu1

---
unity (7.3.2+15.04.20150330-0ubuntu1) vivid; urgency=medium

  [ Andrea Azzarone ]
  * Do not restore focus if a quicklist is opened during launcher key
navigation. (LP: #932486)
  * Forward first key event that happens on top of the blank window to
the lockscreen. (LP: #1308265)
  * Hide launcher to avoid damaging window when not needed. Also make
sure that pressure effect works fine (previous fix has been reverted
because of this!). (LP: #1301394)
  * Make sure scope_views_[filter.id] exists before using operator[] on
it. (LP: #926979)
  * Make sure that signals are auto-desconnected when
XdndStartStopNotifierImp is destroyed. (LP: #1432231)
  * Release pointer barrier if launcher is in lock_hide state. (LP:
#1029114)

  [ Sebastien Bacher ]
  * use the new nautilus .desktop name (LP: #1436297)

  [ Stephen M. Webb ]
  * AP tests: accounted for arbitrarily-raised exceptions in checking
scaled windows (LP: #1436095)
 -- CI Train BotMon, 30 Mar 2015 15:48:47 +

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

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

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1421712] Re: Ubuntu Phone: No keyboard in webapp after a lock screen

2015-03-30 Thread Zsombor Egri
Alex, I'll hand this over to you, you can forward to whomever will fix.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

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

Title:
  Ubuntu Phone: No keyboard in webapp after a lock screen

Status in libunity-webapps package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  Hi!

  Steps:
  1. Open a webapp by first time: By example Facebook.
  2. Click on username for login > Keyboard appears.
  3. Block the mobile
  4. Unblock the mobile.
  5. Click on username > Bug: No keyboard. You have to kill the app.

  Please, see this video:
  https://copy.com/svmAU1RFZICrl4Lr

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1421712/+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 1438370] [NEW] indicator-datetime wrong day highlighted when you change month/year

2015-03-30 Thread Mike Pap
Public bug reported:

indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1, Ubuntu 14.04.2
LTS.

If you change the month or year while the datetime indicator is open,
the highlighted date doesn't move with the current month, but instead
keeps still on the same number as it was before, regardless of the month
and/or year selected, giving the user a false indication of the current
date. The highlighted date should always be on the current date, unless
the user selects a specific date to add an event or to open evolution by
double-clicking.

What you expected to happen:
1. Click on date-time indicator. (Current month and year is shown with the 
current date highlighted.)
2. Change the month or year with the arrows.
3. If current date is not visible do not highlight any date. 
4. If the current date is visible (on previous or next month) highlight the 
current date on the current month.

What happened instead:
1. Click on date-time indicator. (Current month and year is shown with the 
current date highlighted.)
2. Change the month or year with the arrows.
3. The highlight remains on the same number as the current date on every month 
and/or year.

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

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

Title:
  indicator-datetime wrong day highlighted when you change month/year

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1, Ubuntu 14.04.2
  LTS.

  If you change the month or year while the datetime indicator is open,
  the highlighted date doesn't move with the current month, but instead
  keeps still on the same number as it was before, regardless of the
  month and/or year selected, giving the user a false indication of the
  current date. The highlighted date should always be on the current
  date, unless the user selects a specific date to add an event or to
  open evolution by double-clicking.

  What you expected to happen:
  1. Click on date-time indicator. (Current month and year is shown with the 
current date highlighted.)
  2. Change the month or year with the arrows.
  3. If current date is not visible do not highlight any date. 
  4. If the current date is visible (on previous or next month) highlight the 
current date on the current month.

  What happened instead:
  1. Click on date-time indicator. (Current month and year is shown with the 
current date highlighted.)
  2. Change the month or year with the arrows.
  3. The highlight remains on the same number as the current date on every 
month and/or year.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1438370/+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 1436538] Re: brigtness slider should not allow total darkness

2015-03-30 Thread Pat McGowan
** Changed in: indicator-power (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: indicator-power (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Changed in: indicator-power (Ubuntu)
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

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

Title:
  brigtness slider should not allow total darkness

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+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 1390625] Re: mouse cursor gets corrupted

2015-03-30 Thread Joseph N
I have this problem in Xubuntu 14.10 sometimes when dragging files in
Thunar. I found an interesting work-around that works for me. When
Parole media player is open with a video file (can be paused) if I drag
the corrupted cursor into the video area it fixes the cursor. The
resolution change fix also works but takes longer.

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

Title:
  mouse cursor gets corrupted

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag&dropping a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag&drop, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1390625/+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 1419001] Re: Reminders trigger at the time of the event and not before by default

2015-03-30 Thread Charles Kerr
** Changed in: indicator-datetime (Ubuntu)
   Status: New => Triaged

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

Title:
  Reminders trigger at the time of the event and not before by default

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Calendar application for Ubuntu devices:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Triaged
Status in qtorganizer5-eds package in Ubuntu:
  Invalid

Bug description:
  Sync of google calendar. The Google calendar setting is set by default
  to notify 10 min prior to all meetings.

  Is it possible to get this default notification time from google with the 
sync?
  or can we add a setting for a default notification time in the calendar app?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+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 1431384] Re: Need a mechanism for specifying an ical event's icon

2015-03-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~charlesk/indicator-datetime/lp-1431384-add-tag-
for-menuitem-icon

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

Title:
  Need a mechanism for specifying an ical event's icon

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This issue was raised in discussion with mzanetti, who would like
  reminders (created with reminder-app) to be shown in the drop-down
  menu with that app's icon.

  datetime currently is implemented with "everything is either a clock-
  app alarm or a calendar-app event", which is not an approach that will
  scale to 3rd party apps. I suggest we add something like an x-unity-
  alarm-icon tag to the ical components to let clients specify their own
  icon as a string that gets passed to unity8.

  See related bug https://bugs.launchpad.net/ubuntu/+source/indicator-
  datetime/+bug/1426519 for letting the clients, rather than datetime,
  specify the behavior when the menuitems are clicked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1431384/+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 1436538] Re: brigtness slider should not allow total darkness

2015-03-30 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
Milestone: None => ww13-ota

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

Title:
  brigtness slider should not allow total darkness

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+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 1203718] Re: hud-service is consuming too much recources

2015-03-30 Thread tom
Same is happening to me. Computer was not performing in a way a 64 bit
i7 should. Every operation was taking one second or more. After running
top in a terminal it showed me that hud-service was using up 95% of CPU
an 30% of memmory.  I am using ubuntu 14.04 and two additional displays
(one hdmi and one vga) attached to my labtop. After killing hud-service
everything seems to work smoothly.

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

Title:
  hud-service is consuming too much recources

Status in Unity HUD:
  New
Status in hud package in Ubuntu:
  Confirmed

Bug description:
  For a couple of days now (I assume since recent Unity updates), my Laptop is 
performing more an more poor throughout the day. First 2-3 hours Unity is 
running smoothly (Dash, HUD, etc.) Afterwards, opening Dash or HUD and even 
switching workspaces and starting applications becomes very slow. Sometimes I 
have to restart lightdm from a tty-console or reboot.
  Running "top" in a terminal shows that a process called "hud-service" is 
consuming up to 60% of CPU and RAM resources.

  My hardware should be perfectly able to cope with 13.04 (Dell Latitude
  E5420, quad-core, 8GB RAM) and was until about two weeks before.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Jul 22 13:49:15 2013
  InstallationDate: Installed on 2013-04-25 (87 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   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/hud/+bug/1203718/+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 1290876] Re: indicator-session-service crashed with SIGSEGV in get_user_label()

2015-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package indicator-session -
12.10.5+15.04.20150327-0ubuntu1

---
indicator-session (12.10.5+15.04.20150327-0ubuntu1) vivid; urgency=medium

  [ Charles Kerr ]
  * Fix a crash in get_user_label() by testing a string pointer for NULL
before dereferencing it. (LP: #1290876)
 -- CI Train BotFri, 27 Mar 2015 15:00:16 +

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

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

Title:
  indicator-session-service crashed with SIGSEGV in get_user_label()

Status in indicator-session package in Ubuntu:
  Fix Released

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140214-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Mar 11 14:48:23 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-03-05 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140304)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  SegvAnalysis:
   Segfault happened at: 0x8056643 <_start+945>:movzbl (%edi),%eax
   PC (0x08056643) ok
   source "(%edi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x08056643 in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  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/indicator-session/+bug/1290876/+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 1290876] Re: indicator-session-service crashed with SIGSEGV in get_user_label()

2015-03-30 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/indicator-session

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

Title:
  indicator-session-service crashed with SIGSEGV in get_user_label()

Status in indicator-session package in Ubuntu:
  In Progress

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140214-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Mar 11 14:48:23 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-03-05 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140304)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-session/indicator-session-service
  SegvAnalysis:
   Segfault happened at: 0x8056643 <_start+945>:movzbl (%edi),%eax
   PC (0x08056643) ok
   source "(%edi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  Stacktrace:
   #0  0x08056643 in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: indicator-session-service crashed with SIGSEGV in _start()
  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/indicator-session/+bug/1290876/+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 1427866] Re: Eclipse crashes in g_str_hash when using menu proxy and "New Window"

2015-03-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Eclipse crashes in g_str_hash when using menu proxy and "New Window"

Status in unity-gtk-module package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.2 LTS
  unity-gtk2-module:
Installed: 0.0.0+14.04.20141212-0ubuntu1

  1. Download Eclipse 4.4.2 available here:
  
https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/luna/SR2/eclipse-java-luna-SR2-linux-gtk-x86_64.tar.gz
  2.  Start Eclipse. Close the Welcome screen.
  3.  Mouse over to "Window" menu on top bar, click, move mouse down to "New 
Window", click to open a new, empty window.
  4.  Mouse over to "Window" menu on top bar, click. Crash occurs.

  If Eclipse is started with UBUNTU_MENUPROXY=0, it doesn't crash.

  #  SIGSEGV (0xb) at pc=0x7fa88c654fe0, pid=3787, tid=140362505688832
  #
  # JRE version: OpenJDK Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
  # Java VM: OpenJDK 64-Bit Server VM (24.75-b04 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea 2.5.4
  # Distribution: Ubuntu 14.04 LTS, package 7u75-2.5.4-1~trusty1
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x38fe0]  g_str_hash+0x0

  ...

  Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
  j  org.eclipse.swt.internal.gtk.OS._gtk_widget_show(J)V+0
  j  org.eclipse.swt.internal.gtk.OS.gtk_widget_show(J)V+8
  j  org.eclipse.swt.widgets.MenuItem.createHandle(I)V+248
  j  org.eclipse.swt.widgets.Widget.createWidget(I)V+2
  j  
org.eclipse.swt.widgets.MenuItem.(Lorg/eclipse/swt/widgets/Menu;II)V+38
  j  
org.eclipse.ui.internal.SwitchToWindowMenu.fill(Lorg/eclipse/swt/widgets/Menu;I)V+97
  j  
org.eclipse.jface.action.MenuManager.doItemFill(Lorg/eclipse/jface/action/IContributionItem;I)V+6
  j  org.eclipse.jface.action.MenuManager.update(ZZ)V+371
  j  org.eclipse.jface.action.MenuManager.handleAboutToShow()V+33

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1427866/+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 1436538] Re: brigtness slider should not allow total darkness

2015-03-30 Thread John McAleely
@pat, please can you triage this onto a milestone, so I know where to
land it. Thanks.

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

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

Title:
  brigtness slider should not allow total darkness

Status in the base for Ubuntu mobile products:
  New
Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+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 1434637] Re: Default alarm behavior can cause unnecessary battery drain

2015-03-30 Thread Matthew Paul Thomas
Specification updated.

** Description changed:

  As discussed in private bug #1430666, the default alarm ring duration of
  30 minutes is really long compared to other phones. This got called out
  because it will cause unnecessary screen-on battery drain.
  
  IMO 30 minutes should not be the default option -- if a user doesn't
  dismiss after 10 minutes, adding another 20 feels like overkill.
  
  In addition, datetime (rightly) turns the screen on when an alarm
  triggers. It's kept on for the duration of the alarm, even if it rings
  for a half hour. That's a pretty long screen-on time to pay when the
  user's inactive.
  
- So, two questions.
- 
- 1. Can we change the default alarm duration from 30 minutes to something
- shorter, e.g. 10 minutes? The 30 minute default is specified in
- 
.
+ 1. : "‘Stop ringing after’ controls how long the
+ timer rings. It is set by default to 10 minutes and can be changed with
+ the expansion component"
  
  2. Datetime should release its "screen on" hold after the first few
  minutes, so that even long-ringing alarms don't drain more battery than
  necessary.

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Default alarm behavior can cause unnecessary battery drain

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  As discussed in private bug #1430666, the default alarm ring duration
  of 30 minutes is really long compared to other phones. This got called
  out because it will cause unnecessary screen-on battery drain.

  IMO 30 minutes should not be the default option -- if a user doesn't
  dismiss after 10 minutes, adding another 20 feels like overkill.

  In addition, datetime (rightly) turns the screen on when an alarm
  triggers. It's kept on for the duration of the alarm, even if it rings
  for a half hour. That's a pretty long screen-on time to pay when the
  user's inactive.

  1. : "‘Stop ringing after’ controls how long the
  timer rings. It is set by default to 10 minutes and can be changed
  with the expansion component"

  2. Datetime should release its "screen on" hold after the first few
  minutes, so that even long-ringing alarms don't drain more battery
  than necessary.

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