[Dx-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

2017-01-17 Thread Seth Arnold 
** Also affects: indicator-power (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  New

Bug description:
  [Impact]

   * It's very annoying to see the mouse battery instead of the system
  battery on indicator bar.

  [Test Case]

   * Using Logitech Wireless Mouse M325 or other wireless mouse can see
  this issue.

  [Regression Potential]

   * No regression as I know.

  [Other Info]
   
   * This is a SRU request for Ubuntu 16.04 (xenial).

  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1100546/+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 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

2017-01-17 Thread Shih-Yuan Lee 
** Description changed:

+ [Impact]
+ 
+  * It's very annoying to see the mouse battery instead of the system
+ battery on indicator bar.
+ 
+ [Test Case]
+ 
+  * Using Logitech Wireless Mouse M325 or other wireless mouse can see
+ this issue.
+ 
+ [Regression Potential]
+ 
+  * No regression as I know.
+ 
+ [Other Info]
+  
+  * This is a SRU request for Ubuntu 16.04 (xenial).
+ 
  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status over
  the laptop battery level in the top bar.
  
  I haven't done a good job of explaining it, so check out the screenshot
  - it will explain all :)
  
  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: xenial

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * It's very annoying to see the mouse battery instead of the system
  battery on indicator bar.

  [Test Case]

   * Using Logitech Wireless Mouse M325 or other wireless mouse can see
  this issue.

  [Regression Potential]

   * No regression as I know.

  [Other Info]
   
   * This is a SRU request for Ubuntu 16.04 (xenial).

  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1100546/+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 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

2017-01-17 Thread Launchpad Bug Tracker 
This bug was fixed in the package indicator-power -
12.10.6+17.04.20170116-0ubuntu1

---
indicator-power (12.10.6+17.04.20170116-0ubuntu1) zesty; urgency=medium

  [ Shih-Yuan Lee (FourDollars) ]
  * Make device with power supply has higher sorting priority. (LP: #1100546)

 -- charles.k...@canonical.com (charles.k...@canonical.com)  Mon, 16 Jan
2017 20:29:09 +

** Changed in: indicator-power (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power:
  Triaged
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1100546/+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 1530807] Re: Bluetooth cannot be activated on several devices

2017-01-17 Thread Charles Kerr 
Reopening for workitem found by dobey to see if
https://code.launchpad.net/~morphis/indicator-bluetooth/fix-
lp1530807/+merge/290022 should still be landed

** Changed in: indicator-bluetooth (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: Charles Kerr (charlesk) => Rodney Dawes (dobey)

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

Title:
  Bluetooth cannot be activated on several devices

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1530807/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

2017-01-17 Thread Treviño 
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  Fix Committed
Status in ido source package in Yakkety:
  Fix Committed

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1644323] Re: Installing unity8-session-snap adversely effects unity7

2017-01-17 Thread Launchpad Bug Tracker 
This bug was fixed in the package dbus - 1.10.6-1ubuntu3.3

---
dbus (1.10.6-1ubuntu3.3) xenial; urgency=medium

  * debian/dbus.user-session.upstart:
- Temporarily revert latest changes as those seem to cause issues in the
  unity8 session on touch (LP: #1654241).

 -- Łukasz 'sil2100' Zemczak   Thu, 12 Jan
2017 19:01:21 +0100

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

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1254106] Re: "browse files" on device does nothing

2017-01-17 Thread Rodney Dawes 
** Changed in: indicator-bluetooth (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  "browse files" on device does nothing

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  I click on the Bluetooth icon on the top-right corner of the screen next to 
the battery icon
  My mobile phone is listed in the drop down. I select it and I click on 
"Browse files"

  Expected: a Nautilus window should appear showing the browsable
  contents of the device. Maybe the device should prompt me whether to
  allow browsing before

  Observed: ABSOLUTELY NOTHING happens. The computer doesn't even try to
  connect to the phone. Nothing happens on the phone, nothing happens on
  the computer; no error message is shown anywhere, it's just as if I
  had done nothing.

  I've done an hcidump while trying this, and it's empty.

  
  This HAD WORKED BEFORE on the same machine and with  the same device.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Fri Nov 22 17:53:08 2013
  InstallationDate: Installed on 2013-10-11 (41 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  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
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:549 acl:0 sco:0 events:31 errors:0
TX bytes:1168 acl:0 sco:0 commands:31 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1254106/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory

2017-01-17 Thread Ubuntu-FR-1 
Disabling eveolution-data-server's access to google calendar stops the 
excessive memory usage.
Similar to #1633319

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

Title:
  indicator-datetime-service using high volumes of ram/memory

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I have noticed every time my computer boots into Ubuntu, it freezes up
  with the mouse lagging and then unfreezes. I notice the SSD making
  huge amounts of read/writes (which I imagine is into virtual
  memory/swap space). I have to leave the computer for 15 mins or so
  before coming back to it.

  I noticed `indicator-datetime-service` was using a lot of RAM in
  `System Monitor`. So I killed it, and it comes back again each time I
  kill the process. So I clicked 'Stop' with has seemed to have
  temporary fixed the problem. Obviously now the correct time is not
  displayed on the task bar.

  indicator-datetime:
    Installed: 15.10+16.10.20160820.1-0ubuntu1
    Candidate: 15.10+16.10.20160820.1-0ubuntu1
    Version table:
   *** 15.10+16.10.20160820.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:Ubuntu 16.10
  Release:16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory

2017-01-17 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  indicator-datetime-service using high volumes of ram/memory

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I have noticed every time my computer boots into Ubuntu, it freezes up
  with the mouse lagging and then unfreezes. I notice the SSD making
  huge amounts of read/writes (which I imagine is into virtual
  memory/swap space). I have to leave the computer for 15 mins or so
  before coming back to it.

  I noticed `indicator-datetime-service` was using a lot of RAM in
  `System Monitor`. So I killed it, and it comes back again each time I
  kill the process. So I clicked 'Stop' with has seemed to have
  temporary fixed the problem. Obviously now the correct time is not
  displayed on the task bar.

  indicator-datetime:
    Installed: 15.10+16.10.20160820.1-0ubuntu1
    Candidate: 15.10+16.10.20160820.1-0ubuntu1
    Version table:
   *** 15.10+16.10.20160820.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:Ubuntu 16.10
  Release:16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 774098] Re: Overlay scrollbars are inconsistent and hard to use

2017-01-17 Thread D H 
I have to totally agree on all points with Ingo Ruhnke on his first
post.  These overlay scroll bars are completely useless.  One of the
problems maybe the programmer's are using a an old 100dpi mouse or
something?  As I find it almost impossible to mouse over or click on an
overlay scroll bar.  A lot of people have modern mice with 1200dpi on up
to 4000dpi and beyond with monitors in the 3840 x 2160 range and beyond
and the tiny fraction of a second the pointer tracks over the new
"improved" scroll bar's few pixels is simply too little to make
efficient page control.

I have patched every version of Ubuntu I have used to fix the overlay
scroll bar issue since the "feature" was added. Its on almost every web
site with things to do when you update Ubuntu ...   To me when its that
prevalent that fixing that "feature" is on all these lists of "things to
do", it means that "feature" needs fixing.

This needs to be listed as a permanent bug until some sanity returns on
the scroll bar defaults.

In my last update to 14.04 I gained another "feature" on the scroll bar
bit to fix.  That in the swapping of the single page click of the left
mouse on the scroll bar's panel to go up and down by page which now does
random page movements.  The right mouse button now runs the regular page
up or page down.  Why this was changed I have no clue?  I have not been
able to find a patch that returns the mouse click scroll to the right
buttons yet?  Getting the scroll bar click arrows back would be nice
too, but isn't as big a problem as swapped buttons or un-overlay'ing the
scroll bar.

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

Title:
  Overlay scrollbars are inconsistent and hard to use

Status in overlay-scrollbar:
  Opinion
Status in overlay-scrollbar package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: overlay-scrollbar

  Foreword: Sorry, that's more a rant then a proper bug report, but I
  haven't really found a single good reason for overlay-scrollbar to
  exist, just a whole lot of reason why its really bad.

  The overlay scrollbar is one of those crazy wheel reinventions for no
  reason in the new Ubuntu, here a few basic reasons why it sucks:

  * it's inconsistent, when windows are maximuzed or close to the screen border 
it will pop up on the right, otherwise it will pop up on the left
  * it's inconsistent as it is hardly used by anything, even among Gtk+ 
applications only a tiny fractions make use of it and there is no chance that 
any of the non Gtk applications will ever make use of it
  * it's invisible and thus much harder to hit then a visible scrollbar
  * it's impossible to hit in a single straight line when approaching a window 
from the right, it will only pop up once inside the window, but when that 
happens it will pop up on the outside of the window, so you have to move your 
mouse close, stop, then move back to click it
  * selections have the same color as the scrollbar, thus when a widget has a 
selection that goes till the edge it will blend into the scrollbar, making it 
not only look weird, but in the worst case completely invisible when scrollbar 
and selecting merge into one
  * it's much smaller then a classic scrollbar, real scrollbars fill the whole 
height of the window, overlay only fills the tiny portion that is the visible 
part of a document, thus you have a much smaller area to click on for 
page-up/down events
  * it doesn't pop up under the mouse, but a few pixels to the right, this 
makes it incredible frustrating to use, as the regular pattern of "graphical 
reaction -> I am hovering over the item" becomes untrue
  * the thing you want least in your GUI is randomly blinking stuff, yet 
overlay does exactly that, whenever you move your mouse around the screen 
overlay scrollbars pops up and fades out
  * if you are off by a single pixel to the right it will disappear instantly, 
forcing you not only to travel that pixel back, but to travel all the way to 
the left to make it reappear and then back to the right to actually click it, 
making it not only hard to hit, but actually punishment, as you get reset to an 
earlier stage then where you failed
  * buttons that are clickable and dragable at the same time without clear 
visual indication that they are special
  * it's extremely tiny, yeah the point is to save "screen real estate", but 
seriously, a scrollbar is worth more then four pixels that look more like a 
graphic glitch then a user element
  * it violates Fitt's law on maximized windows

  To sum things up, the overlay scrollbar is baffling. It is not just a
  cosmetic change or a small tweak, but a drastic change in usability
  for the worst while providing no new features of its own. The way it
  punishes the user for slipping a few pixels off to the right makes it
  fell more like a

[Dx-packages] [Bug 1656283] Re: indicator-datetime should drop dependency on systemd-shim

2017-01-17 Thread Dimitri John Ledkov 
** Changed in: indicator-datetime (Ubuntu Trusty)
   Status: Triaged => Won't Fix

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

Title:
  indicator-datetime should drop dependency on systemd-shim

Status in indicator-datetime package in Ubuntu:
  Invalid
Status in indicator-datetime source package in Trusty:
  Won't Fix

Bug description:
  [Impact]

   * Unable to install deputy systemd for snapd
   
  indicator-datetime depend on both systemd-services and systemd-shim. However, 
systemd-services depend on systemd or systemd-shim. With upcoming systemd SRU 
timedated (part of systemd-services) will operate correctly with either 
systemd-shim or systemd installed, and therefore indicator-datetime dependency 
on systemd-shim is no longer required.

  [Test case]
* indicator-datetime should not depend on systemd-shim or conflict with 
bin:systemd in any other way

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