[Dx-packages] [Bug 386057] Re: Consistent Volume "Safe to remove" notifications

2016-01-04 Thread Bug Watch Updater
** Changed in: gvfs
   Status: New => Invalid

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

Title:
  Consistent Volume "Safe to remove" notifications

Status in gvfs:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in notify-osd package in Ubuntu:
  Invalid

Bug description:
  At present when a hard drive partition/USB pendrive/external drive is
  unmounted , safe removal notification is displayed inconsistently.
  Before the safe removal notification there is a notification that the
  "writing data to drive is still going on and to wait". But sometimes
  this wait notification is skipped since the small write operation was
  over very quickly. So this leads to the user being presented with ONLY
  the safe removal notification , thus the user is not notified about
  delay due to the write operation.

  But when there is no pending write operation, to delay the unmount,
  the user is not presented with any notification about safe-removal.

  This causes confusion in the regular non-technical user/new users to
  Ubuntu , who usually keep waiting for the safe removal notifications
  to remove the drive or leads them to double-check the mount status of
  the drive before removing the drive

  This confusion can be avoided by presenting the "Safe to remove"
  notification AT EVERY unmount. And this could be done elegantly using
  the notify-osd notifications for every volume unmount regardless of
  the delays. The "Wait" notification can also be done using the notify-
  osd. Since both these notifications don't require user interactions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/386057/+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 390508] Re: notifyOSD ignores the expire timeout parameter

2016-01-04 Thread Matthew Paul Thomas
"unknown", as I said two years ago, we did not "remove support": Notify
OSD never implemented the parameter in the first place. And it is also
incorrect -- and, as I suspect you know, extremely silly -- to say that
the design takes away your freedom: you have the freedom to use mate-
notification-daemon instead, to apply Ankur's patch, or to write your
own. You don't have any of those freedoms with the notification systems
on Windows, OS X, or iOS, none of which let app developers customize
notification durations either.

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

Title:
  notifyOSD ignores the expire timeout parameter

Status in Ayatana Design:
  New
Status in One Hundred Papercuts:
  Invalid
Status in Message Web:
  New
Status in notify-osd package in Ubuntu:
  Won't Fix
Status in notify-osd package in Arch Linux:
  New

Bug description:
  Binary package hint: libnotify-bin

  adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
  Description:  Ubuntu 9.04
  Release:  9.04
  adyroman@panther:~/libnotify-0.4.5/tools$ 

  adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
  libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
   *** 0.4.5-0ubuntu1 0
  500 http://ro.archive.ubuntu.com jaunty/universe Packages
  100 /var/lib/dpkg/status
  adyroman@panther:~/libnotify-0.4.5/tools$ 

  adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep 
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
  adyroman@panther:~/libnotify-0.4.5/tools$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+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 1317860] Re: the phone should switch itself off before completely draining battery

2016-01-04 Thread Charles Kerr
** Branch unlinked: lp:~charlesk/indicator-power/lp-1296431-low-power-
notifications

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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 1509294] Re: X freezes when notfiy OSD appears while in full-screen openGL game

2016-01-04 Thread Alberto Salvia Novella
** Changed in: notify-osd (Ubuntu)
   Status: Confirmed => Triaged

** Summary changed:

- X freezes when notfiy OSD appears while in full-screen openGL game
+ X freezes when notify OSD appears while in full-screen openGL game

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

Title:
  X freezes when notify OSD appears while in full-screen openGL game

Status in notify-osd package in Ubuntu:
  Triaged

Bug description:
  when I want to change volume while I'm running a full-screen app the
  whole GUI freezes and I have to manually open a terminal to restart
  X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: notify-osd 0.9.35+15.10.20151014-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 23 12:15:29 2015
  DesktopSession: 'ubuntu'
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2014-11-08 (348 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Notebook W65_67SF
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c1033a27-1470-4958-aa0f-9c93f0858e3f ro quiet splash
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu4
   libgl1-mesa-glx  11.0.2-1ubuntu4
   libdrm2  2.4.64-1
   xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
   xserver-xorg-video-ati   1:7.5.0+git20150819-0ubuntu1
  SourcePackage: notify-osd
  UpgradeStatus: Upgraded to wily on 2015-10-19 (3 days ago)
  dmi.bios.date: 08/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.04:bd08/25/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1509294/+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 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves

2016-01-04 Thread atimonin
As I can see nobody can help here

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

Title:
  12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse
  Moves

Status in gnome-power:
  New
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
   A fully updated (Jan 11, 2013) Ubuntu 12.10 allows the bluetooth
  mouse to "connect" but fails to move the cursor.  The bluetooth
  battery indicator is created and works.

   If bluetooth  is turned on just before mouse connection is attempted (before 
the battery  indicator shows the mouse battery), sometimes there is mouse 
cursor  movement for a fraction of a second.  One time, a mouse onnection 
succeeded,  and at that time, the battery indicator for the mouse no longer 
reported the current battery state (switching batteries of different charges no 
longer accurately indicated the battery charge).  
  hcidump reports the mouse moves, but the cursor does nothing, nor do clicks.

** The mouse does work if the battery indicator is killed soon after
  boot before bluetooth is turned on.**

Taking a wild guess, the bluetooth battery indicator handler is not
  re-queueing the mouse moves it sees while looking for the battery
  info. Additionally, the mouse handler, when it rarely gets a position
  before the battery handler is not re-queuing the battery messages.

   Equipment:
   HP V3000, with Nvidia 6150 running driver version 304.51, root on 8G usb.
   Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface
  [Broadcom BCM2045], Generic Bluetooth mouse
   Broadcom 4311 wireless running the b43 driver with the firmware supplied
  from package firmware-b43-installer.
   xorg.conf file was originally absent, but copying one from my 12.04
  installation made no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: indicator-power 12.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  Date: Sat Jan 12 12:03:51 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1098959/+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 1317860] Re: the phone should switch itself off before completely draining battery

2016-01-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: ww02-2016 => ww08-2016

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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.

2016-01-04 Thread Pat McGowan
The images show that in neither case is the Bluetooth indicator shown in
the top panel

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

-- 
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.

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  New

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/canonical-devices-system-image/+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 1317860] Re: the phone should switch itself off before completely draining battery

2016-01-04 Thread Charles Kerr
It looks like upower should be handling this; it has triggers for
hibernation / power off at configured battery percentage.

I'll see if I can figure out why that's not kicking in.

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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.

2016-01-04 Thread Pat McGowan
Cannot reproduce on any other devices, could be specific to the N7 or
the current state of the specific device.

-- 
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.

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  New

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/canonical-devices-system-image/+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 1530807] Re: Bluetooth cannot be activated.

2016-01-04 Thread Charles Kerr
** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

-- 
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.

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  New

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/canonical-devices-system-image/+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 1530807] Re: Bluetooth cannot be activated.

2016-01-04 Thread Randall Ross
I am (I think) able to observe the slider behaviour referenced in the
bug on my N7, running r329. My device initially discoverable, even when
the slider reverts to "off" by itself. Shortly after (maybe a few
minutes later), the N7 is no longer discoverable and turning the slider
back to "on" has no effect. And, if I wait a few more minutes, I can
once again make the device discoverable with the slider. 

Checkbox output attached.

** Attachment added: "submission_2016-01-04T20:53:00.945947.xlsx"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530807/+attachment/4543962/+files/submission_2016-01-04T20%3A53%3A00.945947.xlsx

-- 
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.

Status in Canonical System Image:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  New

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/canonical-devices-system-image/+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