[Dx-packages] [Bug 1888934] [NEW] Indicator is shown twice

2020-07-25 Thread teo1978
Public bug reported:

See the screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sat Jul 25 12:03:34 2020
InstallationDate: Installed on 2013-10-11 (2478 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: indicator-bluetooth
UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago)

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


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

** Attachment added: "Screenshot from 2020-07-25 12-02-17.png"
   
https://bugs.launchpad.net/bugs/1888934/+attachment/5395678/+files/Screenshot%20from%202020-07-25%2012-02-17.png

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

Title:
  Indicator is shown twice

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  See the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sat Jul 25 12:03:34 2020
  InstallationDate: Installed on 2013-10-11 (2478 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1888934/+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 1538760] Re: battery icon gone

2016-05-02 Thread teo1978
> 1. Is there anything for indicator-power in /var/crash?

In /var/crash/ there are three files:

  _usr_lib_gnome-user-share_gnome-user-share.1000.crash
  _usr_lib_gnome-user-share_gnome-user-share.1000.upload
  _usr_lib_gnome-user-share_gnome-user-share.1000.uploaded

In the .crash there is a line that reads:
   indicator-power 12.10.6+15.10.20151005.1-0ubuntu1

but above and below it is nothing more that what seems to be a list of
package names.


> 2. What happens if you run "$ start indicator-power" ?

Now I already rebooted and the indicator is there, so it would be of no
use to test, I'll have to wait until the next time it happens.


** Changed in: indicator-power (Ubuntu)
   Status: Incomplete => 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/1538760

Title:
  battery icon gone

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Usually the power/battery indicator works as expected.
  However, now I turned on my laptop while not connected to AC power, and there 
is no battery icon at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 27 22:10:15 2016
  InstallationDate: Installed on 2013-10-11 (838 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+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 1538760] Re: battery icon gone

2016-04-29 Thread teo1978
Still seeing this bug.

Note that this could be pretty serious if the indicator doesn't show up
when the battery gets low (which seems unlikely to happen)

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

Title:
  battery icon gone

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Usually the power/battery indicator works as expected.
  However, now I turned on my laptop while not connected to AC power, and there 
is no battery icon at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 27 22:10:15 2016
  InstallationDate: Installed on 2013-10-11 (838 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+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 1420499] Re: [REGRESSION] navigating to submenus has become painfully difficult. Clicking doesn't help; requires extreme precision

2015-09-28 Thread teo1978
By the way, you talk about "moving horizontally". Does the submenu
remain open also if clicking on the item and moving diagonally or
vertically?? If not, then it is not fixed at all.

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

Title:
  [REGRESSION] navigating to submenus has become painfully difficult.
  Clicking doesn't help; requires extreme precision

Status in Unity:
  Invalid
Status in gtk package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  case A:
  I want to access an item of a submenu of a menu of an application. That is, 
menu Foo->bar->something

  Case B:
  by right-clicking on something, I want to access an item of a submenu of the 
context menu, for example in Nautilus: right-click on a file -> open with -> 
someApplication

  So, I unfold the first level menu (of an application) or the context
  menu (by right-clicking), I move the mouse cursor onto the menu item
  so that the final submenu unfolds, and I CLICK on the submenu parent
  item (e.g. I click on "open with" from the context menu).

  EXPECTED (and how it used to work):
  By clicking on the item that unfolds the submenu (e.g. "open with"), as 
opposed to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor out of the submenu's parent item before you reach 
the area in the desired submenu.

  OBSERVED (since recently):
  Clicking as you navigate through the hierarchy doesn't change the behavior. 
Whether you click or not, in order to reach the final submenu and the desired 
item within it, you have to carefully move the cursor in an almost perfectly 
horizontal direction to the right, without going the slightest bit out the area 
of the submenu's parent item. Otherwise, the submenu will disappear before you 
reach it.

  For example, if the final item in the submenu you want to reach is the
  third, it is very likely that, after hovering (and clicking) on the
  menu item that opens the final submenu, you will move in diagonal
  downwards-rightwards, and in this trajectory you'll exit the area of
  the menu item that unfolded the submenu, making the submenu disappear
  before you reach it.

  Usually, this happened only if you only moved the mouse through the
  menu items and submenus without clicking. But when you clicked on an
  item that would unfold a submenu, that submenu would remain more
  "sticky", allowing for more freedom of movement, and remaining open
  even if moving out of it (until you clicked somewhere else, and
  perhaps also when you moved far enough from it).

  So, if you were super-precise and/or slow enough in your movements, you could 
reach the desired item in the sub-sub-menu by simply moving the mouse without 
clicking, but if you wanted to reach it quickly and carelessly, you could just 
click on each item of the hierarchy you were traversing.
  Which is what I used to do, because I like to navigate through menus quicky 
and without having to train myself to move my hand with surgical precision.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Feb 10 21:32:41 2015
  InstallationDate: Installed on 2013-10-11 (487 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (262 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1420499/+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 1029371] Re: drag of files randomly silently fails

2015-09-26 Thread teo1978
I have also  noticed that this does not only happen when dragging and
dropping among and within Nautilus windows and/or the Desktop, but also
when dragging a file to an application capable of handling it, such as
dropping a file into Filezilla (on the server-side panel, i.e. the right
one) for upload. In that case, also, at random times the operation is
silently ignored.

I would say it does appear to be more likely to happen when the
drag-n-drop is done quickly, but it's difficult to say, because most of
the times I do it quickly, unless I am re-doing it just after a failure.

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

Title:
  drag of files  randomly silently fails

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

Bug description:
  I'm not sure whether this is Nautilus or Unity at fault. This happens
  with both a Nautilus window and the Desktop:

  1. In a Nautilus window: click on a file icon, drag it and drop it
  over a folder. Or hold the Ctrl key and click and drag and drop the
  file immediately in almost the same place where it was.

  In the first case (dragging over a folder) the file should be moved;
  in the second case the file should be copied. In both cases, if you do
  it quickly enough, the action is completely ignored and nothing
  happens.

  It seems to be related to the fact that the Launcher (or whatever it
  is called) shows up on the left of the screen when you start dragging.
  If its show-up animation is not complete when you drop the item, the
  drag operation is ignored.

  2. On the desktop, the same happens. Or if you simply move an icon (in
  which case the expected behavior would be for the icon to snap to the
  nearest position in the grid and stay there) you can also observe that
  the action is ignored and the icon goes back to its original position.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Jul 26 12:44:14 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-05-17 (69 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1029371/+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 1420499] Re: [REGRESSION] navigating to submenus has become painfully difficult. Clicking doesn't help; requires extreme precision

2015-09-25 Thread teo1978
(and previous non-dead LTS versions)

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

Title:
  [REGRESSION] navigating to submenus has become painfully difficult.
  Clicking doesn't help; requires extreme precision

Status in Unity:
  Invalid
Status in gtk package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  case A:
  I want to access an item of a submenu of a menu of an application. That is, 
menu Foo->bar->something

  Case B:
  by right-clicking on something, I want to access an item of a submenu of the 
context menu, for example in Nautilus: right-click on a file -> open with -> 
someApplication

  So, I unfold the first level menu (of an application) or the context
  menu (by right-clicking), I move the mouse cursor onto the menu item
  so that the final submenu unfolds, and I CLICK on the submenu parent
  item (e.g. I click on "open with" from the context menu).

  EXPECTED (and how it used to work):
  By clicking on the item that unfolds the submenu (e.g. "open with"), as 
opposed to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor out of the submenu's parent item before you reach 
the area in the desired submenu.

  OBSERVED (since recently):
  Clicking as you navigate through the hierarchy doesn't change the behavior. 
Whether you click or not, in order to reach the final submenu and the desired 
item within it, you have to carefully move the cursor in an almost perfectly 
horizontal direction to the right, without going the slightest bit out the area 
of the submenu's parent item. Otherwise, the submenu will disappear before you 
reach it.

  For example, if the final item in the submenu you want to reach is the
  third, it is very likely that, after hovering (and clicking) on the
  menu item that opens the final submenu, you will move in diagonal
  downwards-rightwards, and in this trajectory you'll exit the area of
  the menu item that unfolded the submenu, making the submenu disappear
  before you reach it.

  Usually, this happened only if you only moved the mouse through the
  menu items and submenus without clicking. But when you clicked on an
  item that would unfold a submenu, that submenu would remain more
  "sticky", allowing for more freedom of movement, and remaining open
  even if moving out of it (until you clicked somewhere else, and
  perhaps also when you moved far enough from it).

  So, if you were super-precise and/or slow enough in your movements, you could 
reach the desired item in the sub-sub-menu by simply moving the mouse without 
clicking, but if you wanted to reach it quickly and carelessly, you could just 
click on each item of the hierarchy you were traversing.
  Which is what I used to do, because I like to navigate through menus quicky 
and without having to train myself to move my hand with surgical precision.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Feb 10 21:32:41 2015
  InstallationDate: Installed on 2013-10-11 (487 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (262 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1420499/+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 1420499] Re: [REGRESSION] navigating to submenus has become painfully difficult. Clicking doesn't help; requires extreme precision

2015-09-24 Thread teo1978
#552920 looks like a different (though related) issue. That was filed in
2010 and there's no mention of clicks changing the behavior, or of any
recent regression.

Whatever the "tolerance" for diagonal movement is and was, a click on a
submenu item used to make its sub-submenu "sticky" (or more "sticky"
than without a click). That broke at some point with some update in
14.04 (not a major release upgrade) around the time I reported the bug
(probably a bit earlier). That is, clicking stopped making any
difference.

It's good that #552920 has been finally fixed (especially considering
the solution had already been invented in the mid eighties as pointed
out in a comment), but the click-makes-the-submenu-really-sticky
behavior that got lost a few months ago should be reintroduced too.

I at least used to observe the desired behavior (and now observe its
lack since I reported this bug) in right-click menus in Nautilus and the
Desktop, that I can tell with absolute certainty. Is that GTK, Gnome,
Nautilus or Unity? (or what?)

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

Title:
  [REGRESSION] navigating to submenus has become painfully difficult.
  Clicking doesn't help; requires extreme precision

Status in Unity:
  Invalid
Status in gtk package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  case A:
  I want to access an item of a submenu of a menu of an application. That is, 
menu Foo->bar->something

  Case B:
  by right-clicking on something, I want to access an item of a submenu of the 
context menu, for example in Nautilus: right-click on a file -> open with -> 
someApplication

  So, I unfold the first level menu (of an application) or the context
  menu (by right-clicking), I move the mouse cursor onto the menu item
  so that the final submenu unfolds, and I CLICK on the submenu parent
  item (e.g. I click on "open with" from the context menu).

  EXPECTED (and how it used to work):
  By clicking on the item that unfolds the submenu (e.g. "open with"), as 
opposed to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor out of the submenu's parent item before you reach 
the area in the desired submenu.

  OBSERVED (since recently):
  Clicking as you navigate through the hierarchy doesn't change the behavior. 
Whether you click or not, in order to reach the final submenu and the desired 
item within it, you have to carefully move the cursor in an almost perfectly 
horizontal direction to the right, without going the slightest bit out the area 
of the submenu's parent item. Otherwise, the submenu will disappear before you 
reach it.

  For example, if the final item in the submenu you want to reach is the
  third, it is very likely that, after hovering (and clicking) on the
  menu item that opens the final submenu, you will move in diagonal
  downwards-rightwards, and in this trajectory you'll exit the area of
  the menu item that unfolded the submenu, making the submenu disappear
  before you reach it.

  Usually, this happened only if you only moved the mouse through the
  menu items and submenus without clicking. But when you clicked on an
  item that would unfold a submenu, that submenu would remain more
  "sticky", allowing for more freedom of movement, and remaining open
  even if moving out of it (until you clicked somewhere else, and
  perhaps also when you moved far enough from it).

  So, if you were super-precise and/or slow enough in your movements, you could 
reach the desired item in the sub-sub-menu by simply moving the mouse without 
clicking, but if you wanted to reach it quickly and carelessly, you could just 
click on each item of the hierarchy you were traversing.
  Which is what I used to do, because I like to navigate through menus quicky 
and without having to train myself to move my hand with surgical precision.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Feb 10 21:32:41 2015
  InstallationDate: Installed on 2013-10-11 (487 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (262 days ago)

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

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

[Dx-packages] [Bug 1420499] Re: [REGRESSION] navigating to submenus has become painfully difficult. Clicking doesn't help; requires extreme precision

2015-09-23 Thread teo1978
I am on 15.04 now and I still observe the issue.

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

Title:
  [REGRESSION] navigating to submenus has become painfully difficult.
  Clicking doesn't help; requires extreme precision

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  case A:
  I want to access an item of a submenu of a menu of an application. That is, 
menu Foo->bar->something

  Case B:
  by right-clicking on something, I want to access an item of a submenu of the 
context menu, for example in Nautilus: right-click on a file -> open with -> 
someApplication

  So, I unfold the first level menu (of an application) or the context
  menu (by right-clicking), I move the mouse cursor onto the menu item
  so that the final submenu unfolds, and I CLICK on the submenu parent
  item (e.g. I click on "open with" from the context menu).

  EXPECTED (and how it used to work):
  By clicking on the item that unfolds the submenu (e.g. "open with"), as 
opposed to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor out of the submenu's parent item before you reach 
the area in the desired submenu.

  OBSERVED (since recently):
  Clicking as you navigate through the hierarchy doesn't change the behavior. 
Whether you click or not, in order to reach the final submenu and the desired 
item within it, you have to carefully move the cursor in an almost perfectly 
horizontal direction to the right, without going the slightest bit out the area 
of the submenu's parent item. Otherwise, the submenu will disappear before you 
reach it.

  For example, if the final item in the submenu you want to reach is the
  third, it is very likely that, after hovering (and clicking) on the
  menu item that opens the final submenu, you will move in diagonal
  downwards-rightwards, and in this trajectory you'll exit the area of
  the menu item that unfolded the submenu, making the submenu disappear
  before you reach it.

  Usually, this happened only if you only moved the mouse through the
  menu items and submenus without clicking. But when you clicked on an
  item that would unfold a submenu, that submenu would remain more
  "sticky", allowing for more freedom of movement, and remaining open
  even if moving out of it (until you clicked somewhere else, and
  perhaps also when you moved far enough from it).

  So, if you were super-precise and/or slow enough in your movements, you could 
reach the desired item in the sub-sub-menu by simply moving the mouse without 
clicking, but if you wanted to reach it quickly and carelessly, you could just 
click on each item of the hierarchy you were traversing.
  Which is what I used to do, because I like to navigate through menus quicky 
and without having to train myself to move my hand with surgical precision.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Feb 10 21:32:41 2015
  InstallationDate: Installed on 2013-10-11 (487 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (262 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1420499/+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 1415637] Re: Finding an application to launch from Dash is ridiculously slow

2015-09-19 Thread teo1978
Thanks for the tips.

However this is still an issue:

1) "Security and Privacy" is a not a sensible place for the setting to
include online search results.  What does it have to do with privacy or
security?

2) Even if that is enabled, applications should have a higher priority.
It's unacceptable that finding an application to launch becomes slower
because Dash is wasting time doing internet searches before or while
searching for applications.

3) it should seriously be considered to disable it by default. It's
totally useless. For searching the web we have browsers.

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

Title:
  Finding an application to launch from Dash is ridiculously slow

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Launching an application that you don't have locked on the launcher
  is extremely painful. And we don't want to fill up the launcher with
  dozens of icons, right? because it would become essentially useless.

  Steps to reproduce:
  - click on the Dash icon on the top left of the screen
  - start typing the name of the application to launch

  Expected:
  the list of applications that match the name should appear INSTANTLY, and 
keep updating INSTANTLY as you keep typing.

  Observed:
  it takes an insanely long time to first show a bunch of results of files in 
your computer, and then PURE GARBAGE such as suggested searches on Wikipedia.

  When I type "Tortoise" in order to run TortoiseHg (which is installed
  on my system), I always see the f***ing  link to the Wikipedia page
  for "tortoise" (the animal) appear way before the icon of the
  application appears.

  
  There are several issues here
  1) The "More suggestion" part, with suggested results from searches on the 
Internet, is COMPLETELY USELESS and should be removed. We already have browsers 
and Google for that.
  2) Searching for files on the computer is obviously orders of magnitude 
slower than searching for an application, and hence it's totally INSANE to have 
both in the same search box. Running an application and searching for a file 
should be separate options
  3) The list of applications should be cached, and/or stored more efficiently, 
because it's absolutely ridiculous that finding an application by its name 
(among no more than few dozens that one may have installed in total) takes 
several seconds on a fast computer, when the same search could be performed in 
an instant on a 10-year-old PC.
  4) Searching for an application should be given the highest priority. It's 
ridiculous that it gets slowed down because files (and stupid internet 
searches) are done before, or maybe at the same time.

  This is a huge step backwards in usability (which happened quite a
  long ago, I know), and the most irritating thing is that this was by
  design.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Jan 28 21:20:34 2015
  InstallationDate: Installed on 2013-10-11 (474 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (249 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1415637/+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 1296253] Re: At random times, Launcher does not respond to clicks too close to the left border of the screen

2015-09-18 Thread teo1978
It's been a very long time since the last time I observed it, so I guess
it's fixed.

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

Title:
  At random times, Launcher does not respond to clicks too close to the
  left border of the screen

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I have Launcher set up to not automatically hide (because it's buggy
  and it would stop showing up too often).

  Usually, you can click on a launcher icon even on the leftmost column of 
pixels and it will respond to clicks.
  Sometimes however, randomly, if you click on the very leftmost region, i.e. 
just next to the left border of the screen, it will not respond to click; you 
then have to click a little bit more to the right, inside the rounded rectangle 
that surrounds the icon, for it to work.
  Then, after doing some random things with the mouse (switching focus between 
different windows, closing some), it behaves normally again

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Mar 23 12:19:12 2014
  InstallationDate: Installed on 2013-10-11 (162 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1296253/+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 1493106] [NEW] Dash randomly becomes transparent to mouse events

2015-09-07 Thread teo1978
Public bug reported:

Don't tell me "can't reproduce". Almost surely you can't. This has just
happened to me randomly, it will probably disappear at the next reboot
and it will probably be ages until the next time it randomly happens
again. However this is HUGE.

Dash has suddenly become transparent to mouse interaction. For example
- I click on the Dash icon on Launcher
- (optuonal) I type the name of some application
- I click on the icon of some application that I want to launch

Instead, I am clicking on whatever is behind it.

This is a CRITICAL SECURITY ISSUE, as you may accidentally click on a
button to confirm some destructive action (or to send an email before
you finish writing it), if it happens to be behind the icon you are
trying to click.

You can LITERALLY (and I'm not abusing the word "literally") format your
hard drive because of this bug.

Besides, obviously, rendering Dash unusable and making you unable to
launch any application.

When the issue appears, it won't go away. I tried ctrl+super+D twice,
clicking on random other launcher icons, and the like.

The only workaround I can think of is reboot.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.2+15.04.20150420-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Sep  7 18:01:27 2015
InstallationDate: Installed on 2013-10-11 (695 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to vivid on 2015-08-15 (22 days ago)

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


** Tags: amd64 apport-bug vivid

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

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

Title:
  Dash randomly becomes transparent to mouse events

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Don't tell me "can't reproduce". Almost surely you can't. This has
  just happened to me randomly, it will probably disappear at the next
  reboot and it will probably be ages until the next time it randomly
  happens again. However this is HUGE.

  Dash has suddenly become transparent to mouse interaction. For example
  - I click on the Dash icon on Launcher
  - (optuonal) I type the name of some application
  - I click on the icon of some application that I want to launch

  Instead, I am clicking on whatever is behind it.

  This is a CRITICAL SECURITY ISSUE, as you may accidentally click on a
  button to confirm some destructive action (or to send an email before
  you finish writing it), if it happens to be behind the icon you are
  trying to click.

  You can LITERALLY (and I'm not abusing the word "literally") format
  your hard drive because of this bug.

  Besides, obviously, rendering Dash unusable and making you unable to
  launch any application.

  When the issue appears, it won't go away. I tried ctrl+super+D twice,
  clicking on random other launcher icons, and the like.

  The only workaround I can think of is reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Sep  7 18:01:27 2015
  InstallationDate: Installed on 2013-10-11 (695 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1493106/+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 1493106] Re: Dash randomly becomes transparent to mouse events

2015-09-07 Thread teo1978
This is too critical to wait for some random other user to stumble upon
it, therefore I change the status to "confirmed" given the exceptional
severity of the issue

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

Title:
  Dash randomly becomes transparent to mouse events

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Don't tell me "can't reproduce". Almost surely you can't. This has
  just happened to me randomly, it will probably disappear at the next
  reboot and it will probably be ages until the next time it randomly
  happens again. However this is HUGE.

  Dash has suddenly become transparent to mouse interaction. For example
  - I click on the Dash icon on Launcher
  - (optuonal) I type the name of some application
  - I click on the icon of some application that I want to launch

  Instead, I am clicking on whatever is behind it.

  This is a CRITICAL SECURITY ISSUE, as you may accidentally click on a
  button to confirm some destructive action (or to send an email before
  you finish writing it), if it happens to be behind the icon you are
  trying to click.

  You can LITERALLY (and I'm not abusing the word "literally") format
  your hard drive because of this bug.

  Besides, obviously, rendering Dash unusable and making you unable to
  launch any application.

  When the issue appears, it won't go away. I tried ctrl+super+D twice,
  clicking on random other launcher icons, and the like.

  The only workaround I can think of is reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Sep  7 18:01:27 2015
  InstallationDate: Installed on 2013-10-11 (695 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1493106/+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 1029371] Re: dragdrop of files randomly silently fails

2015-08-28 Thread teo1978
By the way, I'd like to know whether you tried yourself and couldn't
observe the issue, or didn't even try. Would you mind telling me? It's
just a curiosity I have about how bugs are handled.

** Changed in: unity
   Status: Incomplete = Confirmed

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

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

Title:
  dragdrop of files  randomly silently fails

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

Bug description:
  I'm not sure whether this is Nautilus or Unity at fault. This happens
  with both a Nautilus window and the Desktop:

  1. In a Nautilus window: click on a file icon, drag it and drop it
  over a folder. Or hold the Ctrl key and click and drag and drop the
  file immediately in almost the same place where it was.

  In the first case (dragging over a folder) the file should be moved;
  in the second case the file should be copied. In both cases, if you do
  it quickly enough, the action is completely ignored and nothing
  happens.

  It seems to be related to the fact that the Launcher (or whatever it
  is called) shows up on the left of the screen when you start dragging.
  If its show-up animation is not complete when you drop the item, the
  dragdrop operation is ignored.

  2. On the desktop, the same happens. Or if you simply move an icon (in
  which case the expected behavior would be for the icon to snap to the
  nearest position in the grid and stay there) you can also observe that
  the action is ignored and the icon goes back to its original position.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Jul 26 12:44:14 2012
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-05-17 (69 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1029371/+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 1475719] Re: Copying text to clipboard randomly fails half of the times

2015-08-26 Thread teo1978
No, I'm not.

I remember that issue. That was systematic and also I thought that was
fixed (but I almost never close a window before I paste, because since
that issue I got used to keeping the source window open and also I
rarely would need to close it anyway)

** Changed in: unity
   Status: Incomplete = New

** Changed in: unity (Ubuntu)
   Status: Incomplete = 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/1475719

Title:
  Copying text to clipboard randomly fails half of the times

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Around 50% of the times (very rough estimation) that I copy something,
  regardless of whether it is via Ctrl+C or by right-click+copy (from
  whatever application), it randomly fails to copy, so when I paste, I
  paste whatever was the last-but-one thing that I had copied before.

  As a workaround, I hysterically hit Ctrl+C like a dozen times almost
  every time I want to copy something.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jul 17 17:48:06 2015
  InstallationDate: Installed on 2013-10-11 (643 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (418 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1475719/+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 1485333] [NEW] [REGRESSION] cannot switch to a given window after showing desktop

2015-08-16 Thread teo1978
Public bug reported:

This is a regression which has appeared either in 14.10 or 15.04, as it
didn't exist in 14.04.

This is 100% systematically reproducible for me.

1. have a few windows of the same program open, for example, three terminal 
windows
2. make sure all of them are visible and one is focused
3. hit Ctrl+Super+D so that all windows are hidden and the desktop is shown
4. click on the terminal icon (or the icon of whatever example program we are 
testing the issue against) on the Launcher
= one of the windows becomes visible, foreground and focused, as expected. But 
suppose you want to switch to one of the other ones
5. click on the launcher icon again
6. pick any window other than the one that was focused in the previous step

Expected result: that window should be brought to front and given focus

Observed result:
the window does the animation as if it was going to be brought to front, but 
then vanishes, and is not visible at all
the previous window is still on the foreground but no longer focused.
No visible window is focused at all.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.2+15.04.20150420-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sun Aug 16 17:04:37 2015
InstallationDate: Installed on 2013-10-11 (673 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  [REGRESSION] cannot switch to a given window after showing desktop

Status in unity package in Ubuntu:
  New

Bug description:
  This is a regression which has appeared either in 14.10 or 15.04, as
  it didn't exist in 14.04.

  This is 100% systematically reproducible for me.

  1. have a few windows of the same program open, for example, three terminal 
windows
  2. make sure all of them are visible and one is focused
  3. hit Ctrl+Super+D so that all windows are hidden and the desktop is shown
  4. click on the terminal icon (or the icon of whatever example program we are 
testing the issue against) on the Launcher
  = one of the windows becomes visible, foreground and focused, as expected. 
But suppose you want to switch to one of the other ones
  5. click on the launcher icon again
  6. pick any window other than the one that was focused in the previous step

  Expected result: that window should be brought to front and given
  focus

  Observed result:
  the window does the animation as if it was going to be brought to front, but 
then vanishes, and is not visible at all
  the previous window is still on the foreground but no longer focused.
  No visible window is focused at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Aug 16 17:04:37 2015
  InstallationDate: Installed on 2013-10-11 (673 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1485333/+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 1485333] Re: [REGRESSION] cannot switch to a given window after showing desktop

2015-08-16 Thread teo1978
This might actually be an evolution of #1485330 becoming worse.

Here's a 100% reproducible set of steps which will exhibit the symptoms
described above AND those in #1485330:

- have exactly 3 (three) windows of the same program, e.g. three terminal 
windows
- follow the steps 1-6 described above. Be A the window that first got 
focused at step 4. Be B the window that you picked at step 6
- repeat steps 5-6 and pick the same window B again.

= this time the window B will become foreground and focused, but with
no title bar and no borders

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

Title:
  [REGRESSION] cannot switch to a given window after showing desktop

Status in unity package in Ubuntu:
  New

Bug description:
  This is a regression which has appeared either in 14.10 or 15.04, as
  it didn't exist in 14.04.

  This is 100% systematically reproducible for me.

  1. have a few windows of the same program open, for example, three terminal 
windows
  2. make sure all of them are visible and one is focused
  3. hit Ctrl+Super+D so that all windows are hidden and the desktop is shown
  4. click on the terminal icon (or the icon of whatever example program we are 
testing the issue against) on the Launcher
  = one of the windows becomes visible, foreground and focused, as expected. 
But suppose you want to switch to one of the other ones
  5. click on the launcher icon again
  6. pick any window other than the one that was focused in the previous step

  Expected result: that window should be brought to front and given
  focus

  Observed result:
  the window does the animation as if it was going to be brought to front, but 
then vanishes, and is not visible at all
  the previous window is still on the foreground but no longer focused.
  No visible window is focused at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Aug 16 17:04:37 2015
  InstallationDate: Installed on 2013-10-11 (673 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1485333/+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 1485333] Re: [REGRESSION] cannot switch to a given window after showing desktop

2015-08-16 Thread teo1978
And another wicked 100% reproducible scenario:

- have exactly 3 terminal windows (Terminal is still just an example)
- follow the steps 1-6 in the original report
- be A the window that gets focused at step 4 and be B the window that you 
tried to pick at step 6
- repeat steps 5-6 but this time pick window C

= window B now becomes visible but not focused (note that C should have
become visible and focused)

- repeat steps 5-6 but this time pick window A

= now window C becomes visible, and window A (which was already visible
from before) is focused, as expected. All windows have the borders and
title bars as expected now.

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

Title:
  [REGRESSION] cannot switch to a given window after showing desktop

Status in unity package in Ubuntu:
  New

Bug description:
  This is a regression which has appeared either in 14.10 or 15.04, as
  it didn't exist in 14.04.

  This is 100% systematically reproducible for me.

  1. have a few windows of the same program open, for example, three terminal 
windows
  2. make sure all of them are visible and one is focused
  3. hit Ctrl+Super+D so that all windows are hidden and the desktop is shown
  4. click on the terminal icon (or the icon of whatever example program we are 
testing the issue against) on the Launcher
  = one of the windows becomes visible, foreground and focused, as expected. 
But suppose you want to switch to one of the other ones
  5. click on the launcher icon again
  6. pick any window other than the one that was focused in the previous step

  Expected result: that window should be brought to front and given
  focus

  Observed result:
  the window does the animation as if it was going to be brought to front, but 
then vanishes, and is not visible at all
  the previous window is still on the foreground but no longer focused.
  No visible window is focused at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Aug 16 17:04:37 2015
  InstallationDate: Installed on 2013-10-11 (673 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1485333/+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 1483388] Re: System randomly won't complete boot

2015-08-13 Thread teo1978
** Summary changed:

- Boot gets stuck at purple Ubuntu  screen forever if running from battery
+ System randomly won't complete boot

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

Title:
  System randomly won't complete boot

Status in unity package in Ubuntu:
  New

Bug description:
  I am not sure at all what package this bug is; I report it against
  Unity because I get to see the purple screen...

  Steps to reproduce:
  - turn on the laptop while not connected to AC power, but with more than 
enough battery charge (tested with battery completely charged)

  Expected result:
  should boot fine

  Observed result:
  When the purple Ubuntu loading screen appears and the four dots below the 
word Ubuntu are all filled in red, the system gets stuck at that screen for 
fucking ever.
  No matter how many times I retry, it will always remain stuck there.
  If I connect the charger and reboot, then it works fine.

  This REGRESSION has appeared after some recent automatic updates. This
  didn't use to happen before. I had booted with  battery power
  thousands of time, though it's not something that I do very often so i
  can't tell exactly when the regression appeared.

  
  Before the purple screen appears, for a fraction of a second I've been able 
to see a black screen full of messages, probably error messages, while normally 
(when boot works fine) there would only be one usb-related error message.

  Please let me know from which log I can retrieve those error messages
  so that I can post them here.

  Don't tell me to update the bios, because this used to work on the
  very same machine, so the issue is obviously in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:15:32 2015
  InstallationDate: Installed on 2013-10-11 (668 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388/+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 1483388] Re: System randomly won't complete boot

2015-08-13 Thread teo1978
** Attachment added: IMG_20150813_210905185.jpg
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388/+attachment/371/+files/IMG_20150813_210905185.jpg

** Description changed:

- I am not sure at all what package this bug is; I report it against Unity
- because I get to see the purple screen...
+ Since the incomplete/broken fix for #1431753 was released, and hence
+ NVidia drivers version 340 were installed AND enabled on my machine
+ (where previously I had 331 installed and disabled) this has started
+ happening:
  
- Steps to reproduce:
- - turn on the laptop while not connected to AC power, but with more than 
enough battery charge (tested with battery completely charged)
+ About 50-75% of the times (very rough estimation), when I boot, the boot
+ gets stuck at the purple screen with the Ubuntu word with four red
+ dots below.
  
- Expected result:
- should boot fine
+ Systematically, when this happens, that screen is preceded by a black screen 
with a lot of errors, of which I attach a picture (yes, I know, it's 
unreadable, but it's all I can do).
+ If anybody tells me in which log files those errors can be found, I will be 
happy to attach them.
  
- Observed result:
- When the purple Ubuntu loading screen appears and the four dots below the 
word Ubuntu are all filled in red, the system gets stuck at that screen for 
fucking ever.
- No matter how many times I retry, it will always remain stuck there.
- If I connect the charger and reboot, then it works fine.
+ Normally, that is, when the issue does not happen and the boot is
+ succesful, the black screen preceding the purple screen would only
+ contain one line with an unrelated error that has to do with USB.
  
- This REGRESSION has appeared after some recent automatic updates. This
- didn't use to happen before. I had booted with  battery power thousands
- of time, though it's not something that I do very often so i can't tell
- exactly when the regression appeared.
- 
- 
- Before the purple screen appears, for a fraction of a second I've been able 
to see a black screen full of messages, probably error messages, while normally 
(when boot works fine) there would only be one usb-related error message.
- 
- Please let me know from which log I can retrieve those error messages so
- that I can post them here.
- 
- Don't tell me to update the bios, because this used to work on the very
- same machine, so the issue is obviously in Ubuntu.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:15:32 2015
  InstallationDate: Installed on 2013-10-11 (668 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)

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

Title:
  System randomly won't complete boot

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Since the incomplete/broken fix for #1431753 was released, and hence
  NVidia drivers version 340 were installed AND enabled on my machine
  (where previously I had 331 installed and disabled) this has started
  happening:

  About 50-75% of the times (very rough estimation), when I boot, the
  boot gets stuck at the purple screen with the Ubuntu word with four
  red dots below.

  Systematically, when this happens, that screen is preceded by a black screen 
with a lot of errors, of which I attach a picture (yes, I know, it's 
unreadable, but it's all I can do).
  If anybody tells me in which log files those errors can be found, I will be 
happy to attach them.

  Normally, that is, when the issue does not happen and the boot is
  succesful, the black screen preceding the purple screen would only
  contain one line with an unrelated error that has to do with USB.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:15:32 2015
  InstallationDate: Installed on 2013-10-11 (668 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)


[Dx-packages] [Bug 1483388] Re: System randomly won't complete boot

2015-08-13 Thread teo1978
Inability to boot after the update of NVidia drivers to 340 has been
confirmed by user Anna at https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340-updates/+bug/1431753/comments/104

** Package changed: unity (Ubuntu) = nvidia-graphics-drivers-340
(Ubuntu)

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New = Confirmed

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

Title:
  System randomly won't complete boot

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Since the incomplete/broken fix for #1431753 was released, and hence
  NVidia drivers version 340 were installed AND enabled on my machine
  (where previously I had 331 installed and disabled) this has started
  happening:

  About 50-75% of the times (very rough estimation), when I boot, the
  boot gets stuck at the purple screen with the Ubuntu word with four
  red dots below.

  Systematically, when this happens, that screen is preceded by a black screen 
with a lot of errors, of which I attach a picture (yes, I know, it's 
unreadable, but it's all I can do).
  If anybody tells me in which log files those errors can be found, I will be 
happy to attach them.

  Normally, that is, when the issue does not happen and the boot is
  succesful, the black screen preceding the purple screen would only
  contain one line with an unrelated error that has to do with USB.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:15:32 2015
  InstallationDate: Installed on 2013-10-11 (668 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1483388/+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 1483388] [NEW] Boot gets stuck at purple Ubuntu .... screen forever if running from battery

2015-08-10 Thread teo1978
Public bug reported:

I am not sure at all what package this bug is; I report it against Unity
because I get to see the purple screen...

Steps to reproduce:
- turn on the laptop while not connected to AC power, but with more than enough 
battery charge (tested with battery completely charged)

Expected result:
should boot fine

Observed result:
When the purple Ubuntu loading screen appears and the four dots below the word 
Ubuntu are all filled in red, the system gets stuck at that screen for 
fucking ever.
No matter how many times I retry, it will always remain stuck there.
If I connect the charger and reboot, then it works fine.

This REGRESSION has appeared after some recent automatic updates. This
didn't use to happen before. I had booted with  battery power thousands
of time, though it's not something that I do very often so i can't tell
exactly when the regression appeared.


Before the purple screen appears, for a fraction of a second I've been able to 
see a black screen full of messages, probably error messages, while normally 
(when boot works fine) there would only be one usb-related error message.

Please let me know from which log I can retrieve those error messages so
that I can post them here.

Don't tell me to update the bios, because this used to work on the very
same machine, so the issue is obviously in Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.5+14.04.20150603-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Mon Aug 10 21:15:32 2015
InstallationDate: Installed on 2013-10-11 (668 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)

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

Title:
  Boot gets stuck at purple Ubuntu  screen forever if running from
  battery

Status in unity package in Ubuntu:
  New

Bug description:
  I am not sure at all what package this bug is; I report it against
  Unity because I get to see the purple screen...

  Steps to reproduce:
  - turn on the laptop while not connected to AC power, but with more than 
enough battery charge (tested with battery completely charged)

  Expected result:
  should boot fine

  Observed result:
  When the purple Ubuntu loading screen appears and the four dots below the 
word Ubuntu are all filled in red, the system gets stuck at that screen for 
fucking ever.
  No matter how many times I retry, it will always remain stuck there.
  If I connect the charger and reboot, then it works fine.

  This REGRESSION has appeared after some recent automatic updates. This
  didn't use to happen before. I had booted with  battery power
  thousands of time, though it's not something that I do very often so i
  can't tell exactly when the regression appeared.

  
  Before the purple screen appears, for a fraction of a second I've been able 
to see a black screen full of messages, probably error messages, while normally 
(when boot works fine) there would only be one usb-related error message.

  Please let me know from which log I can retrieve those error messages
  so that I can post them here.

  Don't tell me to update the bios, because this used to work on the
  very same machine, so the issue is obviously in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Aug 10 21:15:32 2015
  InstallationDate: Installed on 2013-10-11 (668 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (443 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1483388/+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 1475719] [NEW] Copying text to clipboard randomly fails half of the times

2015-07-17 Thread teo1978
Public bug reported:

Around 50% of the times (very rough estimation) that I copy something,
regardless of whether it is via Ctrl+C or by right-click+copy (from
whatever application), it randomly fails to copy, so when I paste, I
paste whatever was the last-but-one thing that I had copied before.

As a workaround, I hysterically hit Ctrl+C like a dozen times almost
every time I want to copy something.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.5+14.04.20150603-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Jul 17 17:48:06 2015
InstallationDate: Installed on 2013-10-11 (643 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (418 days ago)

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

Title:
  Copying text to clipboard randomly fails half of the times

Status in unity package in Ubuntu:
  New

Bug description:
  Around 50% of the times (very rough estimation) that I copy something,
  regardless of whether it is via Ctrl+C or by right-click+copy (from
  whatever application), it randomly fails to copy, so when I paste, I
  paste whatever was the last-but-one thing that I had copied before.

  As a workaround, I hysterically hit Ctrl+C like a dozen times almost
  every time I want to copy something.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150603-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jul 17 17:48:06 2015
  InstallationDate: Installed on 2013-10-11 (643 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (418 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1475719/+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 1354180] Re: Regression: Ctrl+Alt+T shortcut, volume printScreen keys randomly stop working

2015-05-10 Thread teo1978
** Summary changed:

- Regression: Ctrl+Alt+T doesn't open a terminal
+ Regression: Ctrl+Alt+T shortcut, volume  printScreen keys randomly stop 
working

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

Title:
  Regression: Ctrl+Alt+T shortcut, volume  printScreen keys randomly
  stop working

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

Bug description:
  Not sure Unity is the package.

  Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal
  window (whether or not one was already open).

  It doesn't work any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Aug  7 23:12:06 2014
  InstallationDate: Installed on 2013-10-11 (300 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1354180/+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 1420499] [NEW] [REGRESSION] navigating to submenus has become painfully difficult. Clicking doesn't help; requires extreme precision

2015-02-10 Thread teo1978
Public bug reported:

Steps to reproduce:

case A:
I want to access an item of a submenu of a menu of an application. That is, 
menu Foo-bar-something

Case B:
by right-clicking on something, I want to access an item of a submenu of the 
context menu, for example in Nautilus: right-click on a file - open with - 
someApplication

So, I unfold the first level menu (of an application) or the context
menu (by right-clicking), I move the mouse cursor onto the menu item so
that the final submenu unfolds, and I CLICK on the submenu parent item
(e.g. I click on open with from the context menu).

EXPECTED (and how it used to work):
By clicking on the item that unfolds the submenu (e.g. open with), as opposed 
to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor out of the submenu's parent item before you reach 
the area in the desired submenu.

OBSERVED (since recently):
Clicking as you navigate through the hierarchy doesn't change the behavior. 
Whether you click or not, in order to reach the final submenu and the desired 
item within it, you have to carefully move the cursor in an almost perfectly 
horizontal direction to the right, without going the slightest bit out the area 
of the submenu's parent item. Otherwise, the submenu will disappear before you 
reach it.

For example, if the final item in the submenu you want to reach is the
third, it is very likely that, after hovering (and clicking) on the menu
item that opens the final submenu, you will move in diagonal downwards-
rightwards, and in this trajectory you'll exit the area of the menu item
that unfolded the submenu, making the submenu disappear before you reach
it.

Usually, this happened only if you only moved the mouse through the menu
items and submenus without clicking. But when you clicked on an item
that would unfold a submenu, that submenu would remain more sticky,
allowing for more freedom of movement, and remaining open even if moving
out of it (until you clicked somewhere else, and perhaps also when you
moved far enough from it).

So, if you were super-precise and/or slow enough in your movements, you could 
reach the desired item in the sub-sub-menu by simply moving the mouse without 
clicking, but if you wanted to reach it quickly and carelessly, you could just 
click on each item of the hierarchy you were traversing.
Which is what I used to do, because I like to navigate through menus quicky and 
without having to train myself to move my hand with surgical precision.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Feb 10 21:32:41 2015
InstallationDate: Installed on 2013-10-11 (487 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (262 days ago)

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


** Tags: amd64 apport-bug trusty

** Description changed:

  Steps to reproduce:
  
  case A:
  I want to access an item of a submenu of a menu of an application. That is, 
menu Foo-bar-something
  
  Case B:
  by right-clicking on something, I want to access an item of a submenu of the 
context menu, for example in Nautilus: right-click on a file - open with - 
someApplication
  
  So, I unfold the first level menu (of an application) or the context
  menu (by right-clicking), I move the mouse cursor onto the menu item so
- that the final submenu unfolds, and I CLICK on the submenu title (e.g. I
- click on open with from the context menu).
+ that the final submenu unfolds, and I CLICK on the submenu parent item
+ (e.g. I click on open with from the context menu).
  
  EXPECTED (and how it used to work):
- By clicking on the item that unfolds the submenu (e.g. open with), as 
opposed to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor a little bit out of the menu item before you reach 
the area in the desired submenu. 
+ By clicking on the item that unfolds the submenu (e.g. open with), as 
opposed to simply hovering over it, the submenu should remain open, even if you 
accidentally move the cursor a little bit out of the menu item before you reach 
the area in the desired submenu.
  
  OBSERVED (since some time ago):
  Clicking on the menu item that has a submenu associated doesn't change its 
behavior the slightest bit. Whether or not you click on it, in order to reach 
the submenu, you have to carefully move the cursor in an almost perfectly 
horizontal direction to the right, without going out the area of the item that 
has the submenu. Otherwise, the submenu will disappear.
  
  For example, if the final 

[Dx-packages] [Bug 1415637] [NEW] Finding an application to launch from Dash is ridiculously slow

2015-01-28 Thread teo1978
Public bug reported:

Launching an application that you don't have locked on the launcher  is
extremely painful. And we don't want to fill up the launcher with dozens
of icons, right? because it would become essentially useless.

Steps to reproduce:
- click on the Dash icon on the top left of the screen
- start typing the name of the application to launch

Expected:
the list of applications that match the name should appear INSTANTLY, and keep 
updating INSTANTLY as you keep typing.

Observed:
it takes an insanely long time to first show a bunch of results of files in 
your computer, and then PURE GARBAGE such as suggested searches on Wikipedia.

When I type Tortoise in order to run TortoiseHg (which is installed on
my system), I always see the f***ing  link to the Wikipedia page for
tortoise (the animal) appear way before the icon of the application
appears.


There are several issues here
1) The More suggestion part, with suggested results from searches on the 
Internet, is COMPLETELY USELESS and should be removed. We already have browsers 
and Google for that.
2) Searching for files on the computer is obviously orders of magnitude slower 
than searching for an application, and hence it's totally INSANE to have both 
in the same search box. Running an application and searching for a file should 
be separate options
3) The list of applications should be cached, and/or stored more efficiently, 
because it's absolutely ridiculous that finding an application by its name 
(among no more than few dozens that one may have installed in total) takes 
several seconds on a fast computer, when the same search could be performed in 
an instant on a 10-year-old PC.
4) Searching for an application should be given the highest priority. It's 
ridiculous that it gets slowed down because files (and stupid internet 
searches) are done before, or maybe at the same time.

This is a huge step backwards in usability (which happened quite a long
ago, I know), and the most irritating thing is that this was by design.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Jan 28 21:20:34 2015
InstallationDate: Installed on 2013-10-11 (474 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (249 days ago)

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


** Tags: amd64 apport-bug trusty

** Description changed:

  Launching an application that you don't have locked on the launcher  is
  extremely painful. And we don't want to fill up the launcher with dozens
  of icons, right? because it would become essentially useless.
  
  Steps to reproduce:
  - click on the Dash icon on the top left of the screen
  - start typing the name of the application to launch
  
  Expected:
  the list of applications that match the name should appear INSTANTLY, and 
keep updating INSTANTLY as you keep typing.
  
  Observed:
- it takes an unhumanly long time to first show find a bunch of results of 
files in your computer, and then PURE GARBAGE such as suggested search on 
Wikipedia. 
+ it takes an insanely long time to first show find a bunch of results of files 
in your computer, and then PURE GARBAGE such as suggested search on Wikipedia.
  
  There are several issues here
  1) The More suggestion part, with suggested results from searches on the 
Internet, is COMPLETELY USELESS and should be removed. We already have browsers 
and Google for that.
  2) Searching for files on the computer is obviously orders of magnitude 
slower than searching for an application, and hence it's totally INSANE to have 
both in the same search box. Running an application and searching for a file 
should be separate options
  3) The list of applications should be cached, and/or stored more efficiently, 
because it's absolutely ridiculous that finding an application by its name 
(among no more than few dozens that one may have installed in total) takes 
several seconds on a fast computer, when the same search could be performed in 
an instant on a 10-year-old PC.
  4) Searching for an application should be given the highest priority. It's 
ridiculous that it gets slowed down because files (and stupid internet 
searches) are done before, or maybe at the same time.
  
- 
- This is a huge step backwards in usability (which happened quite a long ago, 
I know), and the most irritating thing is that this was by design.
+ This is a huge step backwards in usability (which happened quite a long
+ ago, I know), and the most irritating thing is that this was by design.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 

[Dx-packages] [Bug 1159404] Re: System completely inaccessible after suspend/resume if the only enabled screen is no longer available

2015-01-12 Thread teo1978
Yes I can still reproduce the issue, but it happens when HIBERNATING,
not suspending (not sure whether it has changed or whether I erroneously
wrote suspend when reporting it).

The issue is even much worse than I thought: if you happen to have the
external screen available and you do re-plug it after resuming from
hibernation, the output to the external screen will appear but the
system will be frozen and won't respond to mouse or keyboard input. You
have to switch it off via hardware.

** Description changed:

  Steps to reproduce:
  - connect an external monitor to a laptop
- - enable only the external monitor and disable the laptop's builtin monitor, 
as in: disper -S
- - suspend
+ - enable only the external monitor and disable the laptop's builtin monitor
+ - hibernate
  - disconnect the external monitor and take your laptop to another place
- - resume from suspend, ready to resume working happily with all your unsaved 
data
+ - resume from hibernation, ready to resume working happily with all your 
unsaved data
  
  Expected behavior:
  - on resume, the system should detect that the only screen that was enabled 
is no longer available, and that the only available screen is the builtin one, 
so it should enable it.
  
  Observed behavior:
- - the builtin screen is still disabled, so you have no usable screen. 
Everything is probably there and working, but you can't see anything, so you 
can't even switch screen back to enable the builtin screen
+ - the builtin screen is still disabled, so you have no usable screen. 
+ - if you do have the external screen available and re-connect it, then the 
screen will show up on the external monitor, but the system is frozen, 
unresponsive to keyboard and mouse input (and doesn't even react to connecting 
usb devices, I can tell because if I connect an external keyboard its leds 
won't turn on). The only way out is a hadrware power off.
  
- As a workaround I've tried Ctrl+Alt+F1 to access a virtual terninal, and
- it works, but I don't know of any command that can be executed from the
- virtual terminal that would force xorg to switch screen. disper -s
- doesn't work if run from the virtual terminal.
+ This is critical, as it causes data loss.
  
- So the only option you have is to kill Xorg or reboot, loosing in both
- cases all unsaved data.
  
- Unless you can manage your system blindly, and manage to switch screen
- without seing what you're doing.
+ Last reproduced on 14.04.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Mar 24 13:22:59 2013
  InstallationDate: Installed on 2010-06-23 (1005 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (70 days ago)

** Summary changed:

- System completely inaccessible after suspend/resume if the only enabled 
screen is no longer available
+ System completely inaccessible after hibernate/resume if the only enabled 
screen is no longer available

** Changed in: unity
   Status: Incomplete = New

** Changed in: unity (Ubuntu)
   Status: Incomplete = 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/1159404

Title:
  System completely inaccessible after hibernate/resume if the only
  enabled screen is no longer available

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - connect an external monitor to a laptop
  - enable only the external monitor and disable the laptop's builtin monitor
  - hibernate
  - disconnect the external monitor and take your laptop to another place
  - resume from hibernation, ready to resume working happily with all your 
unsaved data

  Expected behavior:
  - on resume, the system should detect that the only screen that was enabled 
is no longer available, and that the only available screen is the builtin one, 
so it should enable it.

  Observed behavior:
  - the builtin screen is still disabled, so you have no usable screen. 
  - if you do have the external screen available and re-connect it, then the 
screen will show up on the external monitor, but the system is frozen, 
unresponsive to 

[Dx-packages] [Bug 1159404] Re: System completely inaccessible after hibernate/resume if the only enabled screen is no longer available

2015-01-12 Thread teo1978
I think this could be considered confirmed, as I have already observed
it on two different machines.

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

Title:
  System completely inaccessible after hibernate/resume if the only
  enabled screen is no longer available

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - connect an external monitor to a laptop
  - enable only the external monitor and disable the laptop's builtin monitor
  - hibernate
  - disconnect the external monitor and take your laptop to another place
  - resume from hibernation, ready to resume working happily with all your 
unsaved data

  Expected behavior:
  - on resume, the system should detect that the only screen that was enabled 
is no longer available, and that the only available screen is the builtin one, 
so it should enable it.

  Observed behavior:
  - the builtin screen is still disabled, so you have no usable screen. 
  - if you do have the external screen available and re-connect it, then the 
screen will show up on the external monitor, but the system is frozen, 
unresponsive to keyboard and mouse input (and doesn't even react to connecting 
usb devices, I can tell because if I connect an external keyboard its leds 
won't turn on). The only way out is a hadrware power off.

  This is critical, as it causes data loss.

  
  Last reproduced on 14.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Mar 24 13:22:59 2013
  InstallationDate: Installed on 2010-06-23 (1005 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (70 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1159404/+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 1354180] Re: Regression: Ctrl+Alt+T doesn't open a terminal

2015-01-12 Thread teo1978
This had incorrectly remained in the Incomplete status though #7
replied to the request for additional information. Setting to
Confirmed as we have been two users observing this.

** Changed in: unity
   Status: Incomplete = Confirmed

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

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

Title:
  Regression: Ctrl+Alt+T doesn't open a terminal

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

Bug description:
  Not sure Unity is the package.

  Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal
  window (whether or not one was already open).

  It doesn't work any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Aug  7 23:12:06 2014
  InstallationDate: Installed on 2013-10-11 (300 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1354180/+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 1134357] Re: At random times whole system hangs; on occasions Ctrl+Alt+F1 followed by Ctrl+Alt+F7 fixes it, other times have to do hardware power off

2015-01-12 Thread teo1978
I guess it isn't. Long time since the last time I observed it.

Btw, I hadn't realized but this was probably a duplicate of #1165767

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

Title:
  At random times whole system hangs; on occasions Ctrl+Alt+F1 followed
  by Ctrl+Alt+F7 fixes it, other times have to do hardware power off

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I clicked on the Thunderbird launcher icon in the launcher, and the whole 
system hanged and stopped responding.
  The cursor still kept moving with the movements of the mouse (it got stuck 
every once in a while), though the cursor arrow graphics got corrupted, but I 
couldn't click on anything.
  Keyboard didn't work too: I tried alt+tab and even ctrl+alt+F1 to access a 
virtual terminal, but keyboard input didn't produce any effect.
  CPU consumption was high, or at least the cooler fan was running fast.

  I had no choice but to force a power down.

  
  After that, after a new fresh boot, I clicked the Thunderbird launcher icon 
again and the same happened again There's probably some bug in Thunderbird 
triggering this, but if a single program can hang the whole system in an 
unrecoverable way something's wrong in either Unity, Xorg or Linux.

  This second time, I was able to switch to a virtual terminal with 
Ctlr+Alt+F1. Then I went back to normal screen with Ctrl+Alt+F7 and it fixed 
the issue!! (without doing anything from the terminal).
  After this, everything behaved as if the Tab key of the keyboard was 
continuously pressed (which it wasn't, ovbviously) and this got fixed by 
actually pressing and releasing it. (I guess when the system was not 
responding, the key press was received and the key released was not processed; 
this must never ever happen no matter how hanged the cpu is).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed Feb 27 14:24:00 2013
  InstallationDate: Installed on 2010-06-23 (980 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1134357/+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 1165767] Re: Clicking on a launcher icon freezes the system completely - need hardware reboot

2015-01-12 Thread teo1978
This was never reproducible at will, but actually it's been a very long
time since the last time it happened to me.

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

Title:
  Clicking on a launcher icon freezes the system completely - need
  hardware reboot

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Every once in a while (almost once a day!) at the very moment I click on 
some launcher icon (on the left of the screen), the whole system freezes and 
stops responding to both mouse and keyboard. The mouse cursor still moves but 
it doesn't respond to clicks.
  CPU use goes relatively high, but not even close to 100%. And no disk 
activity at all.

  The system doesn't even respond to Ctrl+Alt+F1 (switch to virtual
  terminal).

  This has happened to me clicking on launcher icons of the Terminal in
  some occasions, and of Thunderbird on other occasions, so it doesn't
  seem to be related to any application  in particular.

  THIS IS HUGE, this happens to me almost every day (sometimes more than
  once a day)

  This is similar to other issues I've reported recently but this is not 
exactly the same (actually I thought I _had_ reported this very one but I can't 
find it):
  - CPU consumption does NOT reach 100%, though it does go relatively high. I 
can tell because of the fan: when cpu is 100% it spins much faster; while in 
other issues I've reported cpu went to 100% (it was compiz)
  - the system becomes COMPLETELY unresponsive, not just _almost_ unresponsive, 
meaning that you don't have even the smallest chance to have a keystroke or 
click captured (well, or the chance is so much smaller that it basically never 
happens); and everything is completely frozen, it won't move the smallest bit 
after a while: for example the launcher won't ever hide - while in other issues 
I reported you would see things happening at intervals and very jerkily.
  - this alway at the precise instant I click on a launcher icon, while in 
other issues I've reported it happens randomly at any time, e.g. while typing.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Apr  7 15:53:17 2013
  InstallationDate: Installed on 2010-06-23 (1019 days ago)
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (84 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1165767/+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 1085637] Re: Auto-hide Unity launcher is transparent to clicks when revealed (you actually click into the window behind it)

2015-01-12 Thread teo1978
I can't confirm, sorry, since I don't use autohide anymore plus this was
never systematically reproducible in the first place.

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

Title:
  Auto-hide Unity launcher is transparent to clicks when revealed (you
  actually click into the window behind it)

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  This has happened only once to me. I guess it's random.

  I had Thunderbird open and maximixed. I moved the cursor to the left
  of the screen; the dock or panel with application icons appeared. I
  clicked on some icons, but the clicks somehow went through and
  reached Thunderbird behind it, having no effect on the dock.

  I switched focus forth and back to different windows and tried again
  and the issue persisted. Then I unmaximized and remaximized
  thunderbird and the issue disappeared (not sure whether I had to do it
  twice, though).

  When I had open Thunderbird, the system was a bit slow due to high RAM
  usage and paging (but when I observed the issue it wasn't any more),
  so it may be a timing issue where the order in which some things are
  done is not guaranteed but is usually right (which doesn't make it
  less of a bug).

  Note this is not a minor issue (though one that apparently manifests
  itself with a very small probability). Guaranteeing 100% you-click-on-
  what-you-see is absolutely critical.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.18.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Dec  2 15:18:16 2012
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-05-17 (198 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1085637/+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 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working

2014-12-18 Thread teo1978
Can't tell, sorry.
I only use Unity, and as i mentioned this only occurs sporadically, very 
rarely, and with no way to reproduce at will that i know of. (I did see it 
again not long ago, btw)
So even if i tried a given shell for the sake of it, i couldn't but wait for 
ages for it to happen or not.

It's true that there's no technical evidence that this may belong to Unity. 
There is equelly no evidence at all that this may nelong to kernel, either. I 
originañly reported this agaonst linux because i have no clue what package is 
responsible, and there doesn't seem to exist a generic ubuntu package to 
report bugs (not with apport at least)

If there's some package responsible for keyboard layout settings that
would be a better bet in my opinion

I used to report bugs to linux when i didn't know the package in the
hope that people with more knowledge would retriage them. Until i found
out there's this stupid policy for all linux bugs of not even looking at
it if the OP doesn't have the latest bios

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

Title:
  [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have
  stopped working

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  All of a sudden, the volume keys from the keyboard have stopped
  working.

  The volume control on the top right corner of the screen does work if
  used with the mouse.

  I have both an external usb keyboard with dedicated volume + and -
  keys, and the builtin laptop keyboard where the volume +/-keys are the
  combination of the Fn key plus the up/down arrows.

  All these used to work up to a few minutes ago. Now none of them works.
  I think they stopped working with the last reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2303 F pulseaudio
   /dev/snd/pcmC0D0p:   teo2303 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:13:35 2014
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (298 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1353129/+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 1261217] Re: screen gets full of small horizontal black segments at random times

2014-12-12 Thread teo1978
I've since upgraded to 13.10 and then 14.04 and I do still see it from
time to time, though it's not frequent (it never was).

** Changed in: unity
   Status: Incomplete = New

** Changed in: unity (Ubuntu)
   Status: Incomplete = 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/1261217

Title:
  screen gets full of small horizontal black segments at random times

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Since the last reboot, from time to time, randomly, the screen gets
  filled of short vertical black lines (segments), for a fraction of a
  second or few seconds, then gets back to normal.

  Now a few minutes have passed and apparently it has stopped doing it.

  Prior to this last reboot some updates had been installed (that's why
  I had to reboot), and I had never ever seen this happen before, so
  this may be a regression in some recent update.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Dec 15 21:37:06 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.2, 3.8.0-32-generic, x86_64: installed
   vboxhost, 4.3.2, 3.8.0-33-generic, x86_64: installed
   vboxhost, 4.3.2, 3.8.0-34-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] 
[10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (65 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sun Dec 15 21:10:19 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6.2
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1261217/+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 1016613] Re: application launcher icons are mixed with icons of minimized windows

2014-12-03 Thread teo1978
@andyrock would you mind elaborating on the reasons that lead the design
team to the decision to not fix it?

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

Title:
  application launcher icons are mixed with icons of minimized windows

Status in Ayatana Design:
  Invalid
Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I now, it's the way it is designed, but it is wrong.

  And the fact that Mac OS does it this way too doesn't make it less
  wrong. Apple can afford, or sometimes even _needs_, to do things the
  wrong way, because Apple users love Apple products just because they
  are Apple, and they want them to distinguish from the rest. They don't
  care if occasionally they are actually less usable. So if the
  prevailing way of doing something, adopted by all competitors, happens
  to be already the best one, Apple needs to distinguish itself by doing
  it a different way, even if it's worse.

  An icon to launch an application and the icon of an already opened
  window are two completely different things, and it is demential to
  have them mixed together. When you need to switch between open
  windows, or to drag something into an existing but minimized window,
  you don't want to have to look through a lot of icons, including those
  of applications that are not open, and pay attention at which ones
  have a small arrow next to it. Icons of open windows should be grouped
  together and separated from icons of application launchers.

  Also, there are cases where one thing is calling an already opened
  instance of a program and another thing is to launch a new instance of
  it (including programs that don't have a notion of open a new
  window) and you need to be able to do any of the two things.

  And Gnome worked just that way, but then Ubuntu 11.10 came and
  replaced Gnome with Unity and something that was designed correctly
  was replaced with something that is simply and plainly worse. I'm
  talking about this particular aspect, i.e. the way application icons
  are managed. I'm not saying Gnome is generally better than Unity. But
  this is one feature that has been a huge step back in usability.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  295.40  Thu Apr  5 21:28:09 PDT 
2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu10
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Fri Jun 22 17:15:50 2012
  DistUpgraded: 2012-05-17 16:45:23,028 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 9500M GS] [10de:0405] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15d2]
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   pkg:sl-modem-daemon - Software modem (Proprietary, Disabled, Not in use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-05-17 (36 days ago)
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.libdrm2: 

[Dx-packages] [Bug 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad

2014-11-30 Thread teo1978
I thought this had been fixed because i stopped observing it, but now
it's happening again.

So, either this was fixed and then broken again (unlikely), or more
likely this is intermittent, perhaps triggered by some particular event.

This should have very high priority, as it renders any laptop completely
unusable unless you have an external mouse.

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

Title:
  [REGRESSION] touchpad behavior broken: left button press delayed if
  finger is on touchpad

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

Bug description:
  This is a REGRESSION. This used to work fine. I don't know when
  exactly it broke.

  Steps to reproduce: Test 1 and Test 2 should both behave the same as
  test 2, but test 1 gives nonsense and dangerous results.

  --Test 1--
  - place finger 1  on the touchpad
  - move the finger around while keeping it in contact with the touchpad = the 
mouse cursor moves around as expected
  - with another finger 2, press the left button and hold it, while finger 1 is 
still on the touchpad, at point A
  - (*) move finger 1 around on the touchpad to some other point B, then stop 
moving it
  - move finger 1 around again, to point C
  - only then, release the left button

  -- Test 2 --
  - place finger 1 on the touchpad
  - move the finger around as in test 1
  - take finger 1 away from the touchpad, leaving the cursor at point A
  - with another finger 2, press the left button and hold it
  - place finger 1 on the touchpad again and move it around, then stop at  
point B.
  - Move finger 1 a bit more, to point C
  - release the left button

  Expected result:
  OBVIOUSLY, in both cases, the behavior should be the same. A left button 
press should be registered at point A, then a drag movement to B and then C, 
and then a button release. If, for example, at point A you hit something 
draggable, the result is that you drag it and drop to point C

  Observed result:
  Test 2 behaves as expected
  However, in test 1, nothing happens when you actually press the button. 
Instead, a button press is registered when finger 1 pauses at point B. That is, 
everything behaves as if you had pressed the mouse button at a completely 
different place and time than you did. The result is dragging from point B to 
point C.

  The consequences can be disastrous. This can lead to data loss,
  because a click may be registered on a button that delete things, or
  the drag-and-move operation that is executed (completely unrelated to
  the real action of the user) may be that of moving an object to a
  place where you're not supposed to move it (e.g. moving a file to the
  trash or whatever).

  This can literally  result in formatting your hard drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Oct 12 17:17:03 2014
  InstallationDate: Installed on 2013-10-11 (365 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1380320/+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 1370190] [NEW] .desktop files in .local/share/applications not processed correctly

2014-09-16 Thread teo1978
Public bug reported:

I had this file:  ~/.local/share/applications/jetbrains-android-
studio.desktop

whose content is:
-
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Android Studio (Preview) 0.4.6
Icon=jetbrains-android-studio.png
Path=/home/teo/
#Exec=/usr/lib/jvm/java-7-oracle/bin/java -Xms128m -Xmx750m 
-XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -ea 
-Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true 
-Didea.project.structure.max.errors.to.show=0 -XX:+UseCodeCacheFlushing 
-XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 
-XX:+HeapDumpOnOutOfMemoryError -Dawt.useSystemAAFontSettings=lcd 
-Djb.vmOptionsFile=Documents/programmi/android-studio/bin/studio64.vmoptions 
-Xbootclasspath/a:Documents/programmi/android-studio/bin/../lib/boot.jar 
-Didea.paths.selector=AndroidStudioPreview -Didea.platform.prefix=AndroidStudio 
-Djb.restart.code=88 com.intellij.idea.Main
Exec=/home/teo/Documents/programmi/android-studio/bin/studio.sh
StartupNotify=false
#StartupWMClass=jetbrains-android-studio
OnlyShowIn=Unity;
X-UnityGenerated=true
-

I wanted to use this as a model for creating a desktop file for a
completely unrelated application. So this is what I did:

I copied the file verbatim to
~/.local/share/applications/telegram.desktop

and then edited it. Its content now is:

-
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Telegram Desktop
Path=/home/teo/
Exec=/home/teo/Documents/programmi/Telegram/Telegram
StartupNotify=true
OnlyShowIn=Unity;
X-UnityGenerated=true
-

You can see that there's absolutely nothing in the first file that
matches the string telegram, and also you can see that the second file
(the one called telegram.desktop) has Telegram Desktop as its
application name, NOT Android Studio, and doesn't contain anything
related to Android Studio.


So, the expected behavior is that if I type Telegram in the Dash, an item 
should be displayed under Applications, with the name Telegram Desktop, and 
with either the default icon embedded in the executable, if any, or some 
default icon.

Instead, I get this: see screenshot.

It looks like the list of applications got somehow cached when I
created the new file, but it didn't get updated when I modified the
file.

If I click on the wrongly-named Android Studio (etc) application, it
does load the correct one, which is Telegram.

Perhaps this will be fixed at the next reboot, but it shouldn't take a
reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Sep 16 19:44:17 2014
InstallationDate: Installed on 2013-10-11 (340 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (115 days ago)

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


** Tags: amd64 apport-bug trusty

** Attachment added: Screenshot from 2014-09-16 20:03:43.png
   
https://bugs.launchpad.net/bugs/1370190/+attachment/4205676/+files/Screenshot%20from%202014-09-16%2020%3A03%3A43.png

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

Title:
  .desktop files in .local/share/applications not processed correctly

Status in “unity” package in Ubuntu:
  New

Bug description:
  I had this file:  ~/.local/share/applications/jetbrains-android-
  studio.desktop

  whose content is:
  -
  [Desktop Entry]
  Encoding=UTF-8
  Version=1.0
  Type=Application
  Name=Android Studio (Preview) 0.4.6
  Icon=jetbrains-android-studio.png
  Path=/home/teo/
  #Exec=/usr/lib/jvm/java-7-oracle/bin/java -Xms128m -Xmx750m 
-XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -ea 
-Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true 
-Didea.project.structure.max.errors.to.show=0 -XX:+UseCodeCacheFlushing 
-XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 
-XX:+HeapDumpOnOutOfMemoryError -Dawt.useSystemAAFontSettings=lcd 
-Djb.vmOptionsFile=Documents/programmi/android-studio/bin/studio64.vmoptions 
-Xbootclasspath/a:Documents/programmi/android-studio/bin/../lib/boot.jar 
-Didea.paths.selector=AndroidStudioPreview -Didea.platform.prefix=AndroidStudio 
-Djb.restart.code=88 com.intellij.idea.Main
  Exec=/home/teo/Documents/programmi/android-studio/bin/studio.sh
  StartupNotify=false
  #StartupWMClass=jetbrains-android-studio
  OnlyShowIn=Unity;
  X-UnityGenerated=true
  -

  I wanted to use this as a model for creating a desktop file for a
  completely unrelated application. So this is what I did:

  I copied the file verbatim to
  

[Dx-packages] [Bug 1351113] Re: password input box after suspend/resume was not focused but looked like it was; keyboard input was being intercepted by another window

2014-08-08 Thread teo1978
After restarting (several times) I've never observed the issue again, so
I guess it was fixed by the update mentioned above.

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

Title:
  password input box after suspend/resume was not focused but looked
  like it was; keyboard input was being intercepted by another window

Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  This is a HUGE SECURITY ISSUE.

  I suspended, then I resumed.

  Upon resume, I was presented the usual screen where you have to insert
  the password to unlock the screen.

  The password input box had a blinking cursor, as expected.
  I tried to type the password but it appeared to be not responding to 
keystrokes (from an external usb keyboard), meaning the usual dots would not 
appear at every keystroke.

  I thought the external usb keyboard was not working (due to another
  known bug) so I plugged it to another port, with no luck.

  So I tried to use the builtin keyboard of the laptop, but it wouldn't
  (apparently) respond to keystrokes either.

  So I clicked with the mouse on the language selection indicator in the
  upper right corner of the screen, and selected the (unique and already
  selected) language: spanish. A posteriori I think this was irrelevant.
  What I guess was relevant is that I gave focus to anything other than
  the password input box and then clicked on the password input box
  again.

  So now it worked and I could type my password and unlock the screen.

  AND HERE'S THE TERRIFYING THING: after inserting the password and
  unlocking the screen, Google Chrome was the active window (because it
  had been prior to suspending), and in the active tab there was
  facebook open. In the status-update textarea there were all the keys
  that I had been hitting when trying to input the password.

  Do you realize the enormous security hazard here? If I had typed the
  whole password quickly without looking at the screen and hit Enter
  before realizing the keystrokes were not being intercepted by the
  password input box, I could have posted my password on facebook
  without seeing it. Perhaps even twice. Fortunately, I saw the
  keystrokes were not being registered from the very beginning, and
  reacted by repeating the first few characters several times, and then
  hitting random keys, so I only typed a nonsense sequence of characters
  that doesn't even remotely resemble my password and I never got to hit
  the Enter key anyway.

  
  So, to sum up the issue:
  - after resume, the password input box wasn't focused and it should have been
  - worse: it completely looked like it was focused, with a blinking cursor 
inside, so everything looked like keyboard was not working at all
  - worst of all: keystrokes were actually being intercepted by an active 
application (which was not visible because the screen was locked). NOTHING that 
is behind the locked screen should be able to intercept keystrokes or mouse 
interaction, under any circumstance. If you are not seing something, that 
something must be non-existent to keyboard and mouse interaction.

  
  This is far from systematically reproducible. This is the first time I have 
observed this, ever, and have no idea what triggered this. I suspend and resume 
very often on a daily basis so this must be something pretty rare. Yet it is 
hugely dangerous.
  My very real-life case could have led to posting my password on facebook.
  Imagine if the active window was a terminal and if you happen to have a funny 
password such as sudo rm -f /*

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Aug  1 02:40:29 2014
  InstallationDate: Installed on 2013-10-11 (293 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1351113/+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 1354171] [NEW] Volume slider UI broken: can stick to cursor after button release

2014-08-07 Thread teo1978
Public bug reported:

Steps to reproduce:
- click on the volume indicator (top right of the screen) to make the volume 
slider appear
- click and drag the volume slider cursor and do not release the mouse button 
(yet)
- drag the volume all the way to the left and keep dragging a little further, 
off the limit of the slider and beyond the little volume icon on the left BUT 
remaining within the dark-grey rectangle that delimits the widget
- release the mouse button
- move the mouse away
- move the mouse over the slider again but without pressing the button

Expected behavior: the same as if you had released the button while the
cursor was within the slider, or outside the widget completely: when you
release the button, the volume slider cursor should be released and
never move again until you click on the slider again.

Observed:
- when you move the mouse cursor over the slider area, the slider's cursor 
sticks to the mouse cursor, as if you were dragging it again. It's being 
dragged while the mouse cursor is not even pressed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ActionStates: ({'desktop-settings': (true, signature '', @av []), 'mic-volume': 
(true, '', [0.421722412109375]), 'mute': (true, '', [false]), 
'phone-settings': (true, '', []), 'volume': (true, 'i', [0.745086669921875]), 
'root': (true, '', [{'title': 'Sound', 'accessible-desc': 'Volume (74%)', 
'icon': ('themed', ['audio-volume-high-panel', 'audio-volume-high', 
'audio-volume', 'audio']), 'visible': true}]), 'scroll': (true, 'i', [])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Aug  7 23:10:46 2014
InstallationDate: Installed on 2013-10-11 (300 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

** Affects: indicator-sound (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 indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1354171

Title:
  Volume slider UI broken: can stick to cursor after button release

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

Bug description:
  Steps to reproduce:
  - click on the volume indicator (top right of the screen) to make the volume 
slider appear
  - click and drag the volume slider cursor and do not release the mouse button 
(yet)
  - drag the volume all the way to the left and keep dragging a little further, 
off the limit of the slider and beyond the little volume icon on the left BUT 
remaining within the dark-grey rectangle that delimits the widget
  - release the mouse button
  - move the mouse away
  - move the mouse over the slider again but without pressing the button

  Expected behavior: the same as if you had released the button while
  the cursor was within the slider, or outside the widget completely:
  when you release the button, the volume slider cursor should be
  released and never move again until you click on the slider again.

  Observed:
  - when you move the mouse cursor over the slider area, the slider's cursor 
sticks to the mouse cursor, as if you were dragging it again. It's being 
dragged while the mouse cursor is not even pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ActionStates: ({'desktop-settings': (true, signature '', @av []), 
'mic-volume': (true, '', [0.421722412109375]), 'mute': (true, '', [false]), 
'phone-settings': (true, '', []), 'volume': (true, 'i', [0.745086669921875]), 
'root': (true, '', [{'title': 'Sound', 'accessible-desc': 'Volume (74%)', 
'icon': ('themed', ['audio-volume-high-panel', 'audio-volume-high', 
'audio-volume', 'audio']), 'visible': true}]), 'scroll': (true, 'i', [])},)
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 23:10:46 2014
  InstallationDate: Installed on 2013-10-11 (300 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: indicator-sound
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1354171/+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 1354178] [NEW] volume slider UI broken: strange slow movements after moving the mouse off and on

2014-08-07 Thread teo1978
Public bug reported:

Steps to reproduce (it's a bit difficult):

- start with the volume at a value somewhere near the middle; just to ease 
testing.
- click on the sound indicator
- press the button over the volume slider handle as if to start dragging it and 
keep the mouse button pressed
- don't move the mouse horizontally, only vertically. If you move the mouse 
horizontally (perhaps beyond a small tolerance of a few pixels) you won't 
reproduce the issue 
- drag downwards, untill outside the volume widget. Do not release the mouse 
button yet
- now move horizontally (still keeping the mouse button pressed), for example 
to the left. Now the volume slider doesn't move, which is expected (well 
actually it should keep following mouse movements, but this is a minor issue 
and it can be considered ok, in a kind of incomplete imitation of the 
drag-too-far-cancels-interaction way certain UI elements work)
- move the mouse cursor vertically upwards, so as to go back into the slider 
area.

Expected: the slider handle should now jump to the position of the mouse
cursor and follow mouse movements, as it did at the beginning

Observed: the slider handle jumps to some apparently random position
which is somewhere midway between where it was and the mouse cursor. As
you move the mouse cursor to the left or to the right, the slider handle
moves too in the same direction, but much slower, that is, the slider
handle movements reproduce mouse cursor movements on a much smaller
scale (linearly). Normally, when you hold the mouse cursor still, the
slider handle stays still too (there is a 1-1 correspondence between
mouse horizontal position and slider handle position, though at a
non-1:1 scale). However, if you move the mouse cursor off-end on one
side or the other, then (and only in that case) the slider handle will
keep moving slowly towards the mouse cursor.

All together it's complete nonsense.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ActionStates: ({'desktop-settings': (true, signature '', @av []), 'mic-volume': 
(true, '', [0.421722412109375]), 'mute': (true, '', [false]), 
'phone-settings': (true, '', []), 'volume': (true, 'i', [0.745086669921875]), 
'root': (true, '', [{'title': 'Sound', 'accessible-desc': 'Volume (74%)', 
'icon': ('themed', ['audio-volume-high-panel', 'audio-volume-high', 
'audio-volume', 'audio']), 'visible': true}]), 'scroll': (true, 'i', [])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Aug  7 23:11:49 2014
InstallationDate: Installed on 2013-10-11 (300 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

** Affects: indicator-sound (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 indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1354178

Title:
  volume slider UI broken: strange slow movements after moving the mouse
  off and on

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

Bug description:
  Steps to reproduce (it's a bit difficult):

  - start with the volume at a value somewhere near the middle; just to ease 
testing.
  - click on the sound indicator
  - press the button over the volume slider handle as if to start dragging it 
and keep the mouse button pressed
  - don't move the mouse horizontally, only vertically. If you move the mouse 
horizontally (perhaps beyond a small tolerance of a few pixels) you won't 
reproduce the issue 
  - drag downwards, untill outside the volume widget. Do not release the mouse 
button yet
  - now move horizontally (still keeping the mouse button pressed), for example 
to the left. Now the volume slider doesn't move, which is expected (well 
actually it should keep following mouse movements, but this is a minor issue 
and it can be considered ok, in a kind of incomplete imitation of the 
drag-too-far-cancels-interaction way certain UI elements work)
  - move the mouse cursor vertically upwards, so as to go back into the slider 
area.

  Expected: the slider handle should now jump to the position of the
  mouse cursor and follow mouse movements, as it did at the beginning

  Observed: the slider handle jumps to some apparently random position
  which is somewhere midway between where it was and the mouse cursor.
  As you move the mouse cursor to the left or to the right, the slider
  handle moves too in the same direction, but much slower, that is,
  the slider handle movements reproduce mouse cursor movements on a much
  smaller scale (linearly). Normally, when you hold the mouse cursor
  still, the 

[Dx-packages] [Bug 1354180] [NEW] Regression: Ctrl+Alt+T doesn't open a terminal

2014-08-07 Thread teo1978
Public bug reported:

Not sure Unity is the package.

Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal
window (whether or not one was already open).

It doesn't work any more.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu Aug  7 23:12:06 2014
InstallationDate: Installed on 2013-10-11 (300 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

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

Title:
  Regression: Ctrl+Alt+T doesn't open a terminal

Status in “unity” package in Ubuntu:
  New

Bug description:
  Not sure Unity is the package.

  Ctrl+Alt+T used to be the keyboard shortcut for opening a new terminal
  window (whether or not one was already open).

  It doesn't work any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Aug  7 23:12:06 2014
  InstallationDate: Installed on 2013-10-11 (300 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (75 days ago)

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