[Dx-packages] [Bug 1440825] Re: dnd_is_screensaver_inhibited no longer works

2015-10-13 Thread Sebastien Bacher
The code looks wrong indeed but I can't reproduce the issue (using totem
or libreoffice impress no notifications are showing over them), do you
step to trigger the bug as an user?

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

Title:
  dnd_is_screensaver_inhibited no longer works

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  Notifications are still shown even if the system inhibits
  screensaver(expecting dnd_is_screensaver_inhibited state).

  The code seems to expect "GetInhibitors" method is in
  "org.gnome.ScreenSaver", but the method is no longer there. The
  equivalent is "IsInhibited" method in org.gnome.SessionManager.

  
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
  ## unit32:8 = (Inhibit the session being marked as idle)
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
  method return sender=:1.24 -> dest=:1.284 reply_serial=2
 boolean true

  [src/dnd.c]
  100 static DBusGProxy*
  101 get_screensaver_proxy (void)
  102 {
  103 if (gsmgr == NULL)
  104 {
  105 DBusGConnection *connection = dbus_get_connection ();
  106 gsmgr = dbus_g_proxy_new_for_name (connection,
  107
"org.gnome.ScreenSaver",
  108
"/org/gnome/ScreenSaver",
  109
"org.gnome.ScreenSaver");
  110 }
  111 
  112 return gsmgr;
  113 }   
  114 
  115 gboolean
  116 dnd_is_screensaver_inhibited ()
  117 {
  118 GError  *error = NULL;
  119 gboolean inhibited = FALSE;
  120 char **list;
  121 
  122 if (! get_screensaver_proxy ())
  123 return FALSE;
  124 
  125 if (dbus_g_proxy_call_with_timeout (
  126 gsmgr, "GetInhibitors", 2000, ,
  127 G_TYPE_INVALID,
  128 G_TYPE_STRV, ,
  129 G_TYPE_INVALID))

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 01:49:02 2015
  DesktopSession: 'ubuntu'
  EcryptfsInUse: Yes
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2015-02-28 (37 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
  MachineType: FUJITSU FMVS54KR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu4
   libgl1-mesa-glx  10.5.2-0ubuntu1
   libdrm2  2.4.59-0ubuntu1
   xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
   xserver-xorg-video-ati   1:7.5.0-1ubuntu2
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.06
  dmi.board.name: FJNB24F
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
  dmi.product.name: FMVS54KR
  dmi.sys.vendor: FUJITSU
  glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+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 1505688] [NEW] Alerts like for calendar events should use a default sound different from alarms

2015-10-13 Thread Pat McGowan
Public bug reported:

Currently the new default alarm suond is used and it is not appropriate
for calendar events

Choose something like Marimbach

** Affects: indicator-datetime (Ubuntu)
 Importance: Critical
 Status: 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/1505688

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1505688/+subscriptions

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


Re: [Dx-packages] [Bug 1427566] Re: [Clock][UX] Add timers functionality

2015-10-13 Thread Robie Basak
On Tue, Oct 13, 2015 at 01:30:57PM -, Sam Bull wrote:
> I would like to be able to send a notification to the user after a set
> amount of time. Additionally, I would like the user to be able to
> respond to the notification with a couple of buttons (e.g. Yes/No or
> similar).

+1. I had thought along the same lines but didn't know where to file it.
Thank you for noting it.

This would also enable, for example, an offline reminders app.

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

Title:
  [Clock][UX] Add timers functionality

Status in Indicator Date and Time:
  New
Status in ubuntu-application-lifecycle:
  New
Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I'm greatly missing timers from the clock app. In Android I use them
  all the time for fixed time periods (laundry/bread/cooking/tea is
  ready, etc.), and it's rather inconvenient to have to create a
  gazillion alarms at a fixed time for these.

  I'm not sure why they got removed, but could we have them back please?
  Thanks for considering!

  Before we will implement this we need to fix:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200

  -- Additional feature request,
  I have a UX request when setting the timer. In addition to setting the time 
remaining until it expires (as you'd expect), I'd like to also switch to the 
ability to setting the clock time that I want it to expire. This would be very 
similar to setting an alarm of course, but the alarm setting UI is geared 
towards persistent alarms, not ephemeral ones.

  Example use case: there's a one-off thing I need to do at 2pm. I could
  set an alarm for 2pm by adding a new alarm, and then going in and
  deleting the alarm after it has rung but this is tedious.
  Alternatively I could calculate the time until 2pm myself and then
  quickly set a timer for that length of time. This way there is no
  alarm to delete after it has expired. I'd like to just go to the timer
  section and add a timer to ring at 2pm by toggling to an "ETA" display
  instead of "time remaining" and setting it from there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1505692] [NEW] Show connected Bluetooth profiles in settings application

2015-10-13 Thread Simon Fels
Public bug reported:

Right now the user doesn't have any way to find out on which Bluetooth
profiles he is connected. The only thing he knows from the settings app
or the bluetooth indicator is that he is connected in some way with a
remote bluetooth device.

Android for example allows you to select for what you want to use a
known and auto connectable bluetooth device. For example it lists:

 * phone audio
 * media audio
 * contact sharing

where each of those points is an alias for one or more profiles (phone
audio: HFP/HSP, media-audio: A2DP AVCTP .., contact-sharing: PBAP).

We should at minimum list the profiles the user is connected to at the
moment in the settings application on the device information page.

On a next level we could implement a allow/deny preference for a device
or something similar.

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

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

** Affects: ubuntu-system-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: after-bluez5 bluetooth

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

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Show connected Bluetooth profiles in settings application

Status in Ubuntu UX:
  New
Status in bluez package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Right now the user doesn't have any way to find out on which Bluetooth
  profiles he is connected. The only thing he knows from the settings
  app or the bluetooth indicator is that he is connected in some way
  with a remote bluetooth device.

  Android for example allows you to select for what you want to use a
  known and auto connectable bluetooth device. For example it lists:

   * phone audio
   * media audio
   * contact sharing

  where each of those points is an alias for one or more profiles (phone
  audio: HFP/HSP, media-audio: A2DP AVCTP .., contact-sharing: PBAP).

  We should at minimum list the profiles the user is connected to at the
  moment in the settings application on the device information page.

  On a next level we could implement a allow/deny preference for a
  device or something similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1505692/+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 1427566] Re: [Clock][UX] Add timers functionality

2015-10-13 Thread Sam Bull
A proposed lifecycle solution from bug #1502628:

I would like to be able to send a notification to the user after a set
amount of time. Additionally, I would like the user to be able to
respond to the notification with a couple of buttons (e.g. Yes/No or
similar).

This could also be used by the clock app for the timer functionality.

Currently, this is only possible with the push notification service.
But, as a developer, I do not want to implement the complex push
notification service or have to run a server for this simple use case,
and as a user, I do not want to depend on network connectivity for this
functionality.

This could be solved with some kind of interface to anacron that can
schedule a notification to appear at a specified time.

** Also affects: ubuntu-application-lifecycle
   Importance: Undecided
   Status: New

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

Title:
  [Clock][UX] Add timers functionality

Status in Indicator Date and Time:
  New
Status in ubuntu-application-lifecycle:
  New
Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I'm greatly missing timers from the clock app. In Android I use them
  all the time for fixed time periods (laundry/bread/cooking/tea is
  ready, etc.), and it's rather inconvenient to have to create a
  gazillion alarms at a fixed time for these.

  I'm not sure why they got removed, but could we have them back please?
  Thanks for considering!

  Before we will implement this we need to fix:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200

  -- Additional feature request,
  I have a UX request when setting the timer. In addition to setting the time 
remaining until it expires (as you'd expect), I'd like to also switch to the 
ability to setting the clock time that I want it to expire. This would be very 
similar to setting an alarm of course, but the alarm setting UI is geared 
towards persistent alarms, not ephemeral ones.

  Example use case: there's a one-off thing I need to do at 2pm. I could
  set an alarm for 2pm by adding a new alarm, and then going in and
  deleting the alarm after it has rung but this is tedious.
  Alternatively I could calculate the time until 2pm myself and then
  quickly set a timer for that length of time. This way there is no
  alarm to delete after it has expired. I'd like to just go to the timer
  section and add a timer to ring at 2pm by toggling to an "ETA" display
  instead of "time remaining" and setting it from there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 1505688] Re: Alerts like for calendar events should use a default sound different from alarms

2015-10-13 Thread Pat McGowan
Bumping priority given user complaints

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

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

** Changed in: canonical-devices-system-image
Milestone: None => ww40-2015

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505688/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

2015-10-13 Thread Andrea Azzarone
Can you please try on 15.04? Please notice that some time the leak is
not real, it's just the way the kernel manages the memory (but 18.7GB is
for nor not normal at all)

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1427566] Re: [Clock][UX] Add timers functionality

2015-10-13 Thread Sam Bull
Exactly my usecase. I'm making a nagging reminders app, that will nag
you more and more frequently till you complete a task.

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

Title:
  [Clock][UX] Add timers functionality

Status in Indicator Date and Time:
  New
Status in ubuntu-application-lifecycle:
  New
Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I'm greatly missing timers from the clock app. In Android I use them
  all the time for fixed time periods (laundry/bread/cooking/tea is
  ready, etc.), and it's rather inconvenient to have to create a
  gazillion alarms at a fixed time for these.

  I'm not sure why they got removed, but could we have them back please?
  Thanks for considering!

  Before we will implement this we need to fix:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200

  -- Additional feature request,
  I have a UX request when setting the timer. In addition to setting the time 
remaining until it expires (as you'd expect), I'd like to also switch to the 
ability to setting the clock time that I want it to expire. This would be very 
similar to setting an alarm of course, but the alarm setting UI is geared 
towards persistent alarms, not ephemeral ones.

  Example use case: there's a one-off thing I need to do at 2pm. I could
  set an alarm for 2pm by adding a new alarm, and then going in and
  deleting the alarm after it has rung but this is tedious.
  Alternatively I could calculate the time until 2pm myself and then
  quickly set a timer for that length of time. This way there is no
  alarm to delete after it has expired. I'd like to just go to the timer
  section and add a timer to ring at 2pm by toggling to an "ETA" display
  instead of "time remaining" and setting it from there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

2015-10-13 Thread Valentin Crone
I have the same bug since Ubuntu 12.04 LTS.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

2015-10-13 Thread Colin Law
@va_crone  you have not told us which version you are using now.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 270785] Re: When a notification appears, if the mouse is over it, then the notification never disappears.

2015-10-13 Thread Ransom stark
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect  and any other logs that are relevant for this
particular issue.

** Changed in: notification-daemon (Ubuntu)
   Status: New => Incomplete

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

Title:
  When a notification appears, if the mouse is over it, then the
  notification never disappears.

Status in notification-daemon package in Ubuntu:
  Incomplete

Bug description:
  When a notification appears on the screen, moving the cursor over it
  will keep that notification forever displayed. This is a nice feature,
  but IMO this should not happen when the cursor is accidentally already
  over the notification when it appears. A cursor movement should be
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/270785/+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 1440825] Re: dnd_is_screensaver_inhibited no longer works

2015-10-13 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/notify-osd/notify-osd-ubuntu-wily-
proposed

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

Title:
  dnd_is_screensaver_inhibited no longer works

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  Notifications are still shown even if the system inhibits
  screensaver(expecting dnd_is_screensaver_inhibited state).

  The code seems to expect "GetInhibitors" method is in
  "org.gnome.ScreenSaver", but the method is no longer there. The
  equivalent is "IsInhibited" method in org.gnome.SessionManager.

  
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
  ## unit32:8 = (Inhibit the session being marked as idle)
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
  method return sender=:1.24 -> dest=:1.284 reply_serial=2
 boolean true

  [src/dnd.c]
  100 static DBusGProxy*
  101 get_screensaver_proxy (void)
  102 {
  103 if (gsmgr == NULL)
  104 {
  105 DBusGConnection *connection = dbus_get_connection ();
  106 gsmgr = dbus_g_proxy_new_for_name (connection,
  107
"org.gnome.ScreenSaver",
  108
"/org/gnome/ScreenSaver",
  109
"org.gnome.ScreenSaver");
  110 }
  111 
  112 return gsmgr;
  113 }   
  114 
  115 gboolean
  116 dnd_is_screensaver_inhibited ()
  117 {
  118 GError  *error = NULL;
  119 gboolean inhibited = FALSE;
  120 char **list;
  121 
  122 if (! get_screensaver_proxy ())
  123 return FALSE;
  124 
  125 if (dbus_g_proxy_call_with_timeout (
  126 gsmgr, "GetInhibitors", 2000, ,
  127 G_TYPE_INVALID,
  128 G_TYPE_STRV, ,
  129 G_TYPE_INVALID))

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 01:49:02 2015
  DesktopSession: 'ubuntu'
  EcryptfsInUse: Yes
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2015-02-28 (37 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
  MachineType: FUJITSU FMVS54KR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu4
   libgl1-mesa-glx  10.5.2-0ubuntu1
   libdrm2  2.4.59-0ubuntu1
   xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
   xserver-xorg-video-ati   1:7.5.0-1ubuntu2
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.06
  dmi.board.name: FJNB24F
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
  dmi.product.name: FMVS54KR
  dmi.sys.vendor: FUJITSU
  glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+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 1505688] Re: Alerts like for calendar events should use a default sound different from alarms

2015-10-13 Thread Charles Kerr
** Branch linked: lp:~charlesk/indicator-datetime/15.04-lp-1505688
-different-default-sounds-for-alarms-and-events

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

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505688/+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 994884] Re: QueueDraw is very expensive

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  QueueDraw is very expensive

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  Performance fix - only way of testing is performing the benchmarking steps 
again to check if there is improvement.

  [Regression Potential]
  No obvious regression potential.

  Original description:

  I've been running a callgrind session trying to figure out how we
  could speed up opening the dash and it turned out that especially the
  first time the dash is opened, we spend more than 25% of time in
  QueueDraw - see the attached callgrind profile (best viewed with
  kcachegrind).

  Attaching also a simple unity patch that was used to collect the data
  + the command line was `valgrind --tool=callgrind --instr-atstart=no
  --collect-atstart=no compiz --replace ccp`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/994884/+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 987294] Re: [regression] Dash - Arrow keys not working in the search bar on second use

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  [regression] Dash - Arrow keys not working in the search bar on second
  use

Status in Nux:
  Fix Released
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  If the search bar's text is not an empty string, the arrow keys and
  the whole interaction with the search bar is in a weird state. To
  reproduce:

  1) Open dash and search for "gedit"
  2) Close the dash using the super key
  3) Open the dash again
  4) You should see the "gedit" search string selected, but pressing left/right 
arrow keys doesn't move the cursor, pressing enter doesn't activate the result, 
and using mouse to deselect the search string is showing weird inverted 
behaviour

  When in state 4) pressing the escape or backspace keys (or any key to
  replace the selection) fixes the weird state of the search bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/987294/+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 985495] Re: Popularity sorting not working correctly

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Popularity sorting not working correctly

Status in Unity:
  Fix Released
Status in unity-lens-applications:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released
Status in unity-lens-applications source package in Precise:
  Fix Released

Bug description:
  Test case:
  1. Start with a fresh system
  2. Open the dash, type in Sound (or locale equivalent) and run the Sound 
preferences 4-5 times
  3. Close the dash
  4. Open the dash, type in Sound
 -> The "Sound" application should be the first one appearing

  ===

  There are some cases where the popularity sorting is not working
  correctly - this seems to be connected to the way we do bins when
  applying the popularity sort.

  As an example - searching for "sound" always puts "Sound Recorder" as
  the first result, even though "Sound" is used more frequently, same
  goes for "office", the order changes once you go from "offic" ->
  "office" and we don't want that.

  (this is caused by "Sound recorder" having a relevancy of 100 and
  "Sound" just 99, therefore they get into different bins and popularity
  is not taken into account)

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

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  compiz crashed with SIGSEGV in child_setup()

Status in Nux:
  Invalid
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  When trying to open two firefox browser windows compiz crashed. I am
  using 64bit  12.04 Alpha 1 version.

  TEST CASE
  1. Open Firefox
  2. Reveal the launcher and right-click on the Firefox Icon
  3. Select "Open a New Window" in the quicklist
  4. Repeat step 2 and 3

  EXPECTED RESULT
  A Firefox window opens

  ACTUAL RESULT
  This crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: libnux-1.0-0 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
  Uname: Linux 3.2.0-3-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Dec  8 20:33:11 2011
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20111202.1)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2fcb3446ab:mov%r9b,(%rax)
   PC (0x7f2fcb3446ab) ok
   source "%r9b" ok
   destination "(%rax)" (0x7f2fcb3ba2c5) in non-writable VMA region: 
0x7f2fcb2bb000-0x7f2fcb3fd000 r-xp 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3102.0
  SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3102.0
  Signal: 11
  SourcePackage: nux
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_spawn_async_with_pipes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_spawn_async () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_spawn_async_with_pipes()
  UpgradeStatus: Upgraded to precise on 2011-12-05 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/901982/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

2015-10-13 Thread Valentin Crone
Ubuntu 14.04 LTS with Linux 3.13.0-65-generic

I have just tested the Ubuntu 15.10 but not for all day use. (The Next
Release I will use for all day use will be the 16.04 LTS if it's the
same or better than 14.04 LTS)

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 983321] Re: Conditional jump or move depends on uninitialised value(s) nux::GraphicsDisplay::ProcessXEvent(_XEvent, bool) (GraphicsDisplayX11.cpp:1702)

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Conditional jump or move depends on uninitialised value(s)
  nux::GraphicsDisplay::ProcessXEvent(_XEvent, bool)
  (GraphicsDisplayX11.cpp:1702)

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  Running valgrind to check if the given conditional jump error still appears. 

  [Regression Potential]
  No regression potential, trivial fix.

  Original description:

  ==24716== 6 errors in context 132 of 20919:
  ==24716== Conditional jump or move depends on uninitialised value(s)
  ==24716==at 0x12AF1E27: nux::GraphicsDisplay::ProcessXEvent(_XEvent, 
bool) (GraphicsDisplayX11.cpp:1702)
  ==24716==by 0x12AF25D7: nux::GraphicsDisplay::GetSystemEvent(nux::Event*) 
(GraphicsDisplayX11.cpp:1287)
  ==24716==by 0x16314377: nux::WindowThread::ExecutionLoop(unsigned int) 
(WindowThread.cpp:523)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/983321/+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 981309] Re: hash tables, strings, and variants leaked in LauncherEntry.serialize()

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  hash tables, strings, and variants leaked in LauncherEntry.serialize()

Status in libunity:
  Fix Released
Status in Unity:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in libunity source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  Test case:
  1. Run valgring profiling on nautilus (with at least --leak-check=yes)
  2. Confirm that the memory leaks, as noted in the original description, do 
not appear anymore

  ===

  
  Found while running valgrind on Nautilus. This looks like a Low importance 
leak to me since the size of the leak is small, but I only profiled for about 
30 seconds & don't know how quickly the bytes would accumulate over time.

  ==6455==
  ==6455== 444 (56 direct, 388 indirect) bytes in 1 blocks are definitely lost 
in loss record 19,250 of 20,624
  ==6455==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==6455==by 0x4C8296A: standard_malloc (gmem.c:85)
  ==6455==by 0x4C82E02: g_malloc (gmem.c:159)
  ==6455==by 0x4C9727D: g_slice_alloc (gslice.c:1003)
  ==6455==by 0x4C6BEB1: g_hash_table_new_full (ghash.c:689)
  ==6455==by 0x4A3C4C9: unity_collect_launcher_entry_properties (in 
/usr/lib/libunity.so.9.0.1)
  ==6455==by 0x400E29A: _dl_fixup (dl-runtime.c:119)
  ==6455==by 0x40146AF: _dl_runtime_resolve (dl-trampoline.S:37)
  ==6455==by 0xBE8B470F: ???
  ==6455==
  ==6455== 444 (56 direct, 388 indirect) bytes in 1 blocks are definitely lost 
in loss record 19,251 of 20,624
  ==6455==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==6455==by 0x4C8296A: standard_malloc (gmem.c:85)
  ==6455==by 0x4C82E02: g_malloc (gmem.c:159)
  ==6455==by 0x4C9727D: g_slice_alloc (gslice.c:1003)
  ==6455==by 0x4C6BEB1: g_hash_table_new_full (ghash.c:689)
  ==6455==by 0x4A3C4C9: unity_collect_launcher_entry_properties (in 
/usr/lib/libunity.so.9.0.1)

  ...etc...

  ==6455==
  ==6455== 444 (56 direct, 388 indirect) bytes in 1 blocks are definitely lost 
in loss record 19,250 of 20,624
  ==6455==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==6455==by 0x4C8296A: standard_malloc (gmem.c:85)
  ==6455==by 0x4C82E02: g_malloc (gmem.c:159)
  ==6455==by 0x4C9727D: g_slice_alloc (gslice.c:1003)
  ==6455==by 0x4C6BEB1: g_hash_table_new_full (ghash.c:689)
  ==6455==by 0x4A3C4C9: unity_collect_launcher_entry_properties (in 
/usr/lib/libunity.so.9.0.1)
  ==6455==by 0x400E29A: _dl_fixup (dl-runtime.c:119)
  ==6455==by 0x40146AF: _dl_runtime_resolve (dl-trampoline.S:37)
  ==6455==by 0xBE8B470F: ???
  ==6455==
  ==6455== 444 (56 direct, 388 indirect) bytes in 1 blocks are definitely lost 
in loss record 19,251 of 20,624
  ==6455==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==6455==by 0x4C8296A: standard_malloc (gmem.c:85)
  ==6455==by 0x4C82E02: g_malloc (gmem.c:159)
  ==6455==by 0x4C9727D: g_slice_alloc (gslice.c:1003)
  ==6455==by 0x4C6BEB1: g_hash_table_new_full (ghash.c:689)
  ==6455==by 0x4A3C4C9: unity_collect_launcher_entry_properties (in 
/usr/lib/libunity.so.9.0.1)
  ==6455== 1 bytes in 1 blocks are indirectly lost in loss record 140 of 20,624
  ==6455==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==6455==by 0x4C8296A: standard_malloc (gmem.c:85)
  ==6455==by 0x4C82E02: g_malloc (gmem.c:159)
  ==6455==by 0x4C98C43: g_memdup (gstrfuncs.c:384)
  ==6455==by 0x4C574D9: g_bytes_new (gbytes.c:95)
  ==6455==by 0x4CAC4EB: g_variant_new_from_trusted (gvariant.c:326)
  ==6455==by 0x4CAC59C: g_variant_new_boolean (gvariant.c:348)
  ==6455==by 0x4A3C527: unity_collect_launcher_entry_properties (in 
/usr/lib/libunity.so.9.0.1)
  ==6455==by 0x4A3C697: ??? (in /usr/lib/libunity.so.9.0.1)
  ==6455==by 0x400E29A: _dl_fixup (dl-runtime.c:119)
  ==6455==by 0x40146AF: _dl_runtime_resolve (dl-trampoline.S:37)
  ==6455==by 0xBE8B470F: ???
  ==6455==
  ==6455== 1 bytes in 1 blocks are indirectly lost in loss record 141 of 20,624
  ==6455==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==6455==by 0x4C8296A: standard_malloc (gmem.c:85)
  ==6455==by 0x4C82E02: g_malloc (gmem.c:159)
  ==6455==by 0x4C98C43: g_memdup (gstrfuncs.c:384)
  ==6455==by 0x4C574D9: g_bytes_new (gbytes.c:95)
  ==6455==by 0x4CAC4EB: g_variant_new_from_trusted (gvariant.c:326)
  ==6455==by 0x4CAC59C: g_variant_new_boolean (gvariant.c:348)
  ==6455==by 

[Dx-packages] [Bug 937588] Re: Coverity PW.PARAMETER_HIDDEN - CID 10653

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Coverity PW.PARAMETER_HIDDEN - CID 10653

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Nux 4.0 series:
  Fix Released
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  This bug is exported from the Coverity Integration Manager on Canonical's 
servers. For information on how this is done please see this website: 
https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
  CID: 10653
  Checker: PW.PARAMETER_HIDDEN
  Category: No category available
  CWE definition: No definition available
  File: /tmp/buildd/nux-2.4.0/NuxGraphics/GLTextureResourceManager.cpp
  Function: No function name available
  Code snippet:
  834 // const BYTE* Src = _image.GetSurface(MipIndex, 
slice).GetPtrRawData();
  835 // int RowByteSize = _image.GetSurface(MipIndex, 
slice).GetPitch();
  836 // int NumRows = _image.GetSurface(MipIndex, 
slice).GetBlockHeight();
  837 
  CID 10653 - PW.PARAMETER_HIDDEN
  declaration hides parameter "slice" (declared at line 831)
  838 for (int slice = 0; slice < 
ImageSurface::GetLevelDim(_image.GetFormat(), _image.GetDepth(), MipIndex); 
slice++)
  839 {
  840   const BYTE *Src = _image.GetSurface(MipIndex, 
slice).GetPtrRawData();
  841   int RowByteSize = _image.GetSurface(MipIndex, 
slice).GetPitch();
  842   int NumRows = _image.GetSurface(MipIndex, 
slice).GetBlockHeight();
  843

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/937588/+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 986191] Re: [11.04→12.04 upgrade] Dash is always empty due to zeitgeist crash: Unable to upgrade from schema version 3

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  [11.04→12.04 upgrade] Dash is always empty due to zeitgeist crash:
  Unable to upgrade from schema version 3

Status in libzeitgeist:
  Fix Committed
Status in Unity:
  Fix Released
Status in unity-lens-applications:
  Fix Released
Status in Zeitgeist Framework:
  Fix Committed
Status in libzeitgeist package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released
Status in libzeitgeist source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released
Status in unity-lens-applications source package in Precise:
  Fix Released
Status in zeitgeist source package in Precise:
  Fix Released

Bug description:
  Test case:
  1. Perform upgrade from 11.04 to 12.04
  2. Reboot system
  3. Start the dash (Super)
 -> The dash should not be empty
 -> Zeitgeist should not crash (zeitgeist-daemon)

  ===

  Every time I open the dash pressing the super key, I get an empty
  dash. This has been happening for a long time now, I'm running unity-
  2d.

  Please see screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.10.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,vpswitch,mousepoll,place,gnomecompat,wall,regex,resize,compiztoolbox,snap,session,animation,grid,move,fade,imgpng,workarounds,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  Date: Fri Apr 20 10:39:58 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libzeitgeist/+bug/986191/+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 976067] Re: Missing album art

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Missing album art

Status in Unity:
  Fix Released
Status in Music Lens:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-music package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released
Status in unity-lens-music source package in Precise:
  Fix Released

Bug description:
  Test case:
  1. Open the dash
  2. Switch to the music lens
  3. Search for music
 -> Songs that are from albums should have their covers displayed in the 
search results

  
  ===

  Open the dash -> Music Lens -> my music dosn't always have the picture of the 
album
  System up to date with Unity 5.8.0. Sometimes it works well but sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0+bzr2252ubuntu0+677 [origin: LP-PPA-unity-team]
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
  Uname: Linux 3.2.0-22-generic-pae i686
  ApportVersion: 2.0-0ubuntu4
  Architecture: i386
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120406)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/976067/+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 1014610] Re: Unity is slow and pausing occasionally (when its DrawList size spikes, to almost 6000!)

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Unity is slow and pausing occasionally (when its DrawList size spikes,
  to almost 6000!)

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Ubutter:
  Fix Released
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in nux source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  Performance fix - only way of testing is performing the benchmarking steps 
again to check if there is improvement.

  [Regression Potential]
  Redraw/refresh problems.

  Original description:

  I'm finding my development Unity sometimes pauses (stops responding
  for a little while). When this happens I notice its DrawList has
  spiked to several thousand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1014610/+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 893688] Re: Unity.ActivationResponse does not work properly for python scopes

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Unity.ActivationResponse does not work properly for python scopes

Status in libunity:
  Fix Released
Status in Unity:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in vala package in Ubuntu:
  Fix Released
Status in libunity source package in Precise:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]

  1) Run `python -c "from gi.repository import Unity; print 
Unity.ActivationResponse.new(Unity.HandledType.SHOW_DASH, '')"`
  2) The command shouldn't cause a segmentation fault

  [Regression Potential]
  Besides gir not working, nothing else comes to mind.

  Original Report

  When attempting to use a custom activation of a lens result in a scope
  written in python, Unity.ActivationResponse does not work as
  advertised at
  https://wiki.ubuntu.com/Unity/Lenses#Handling_Activation, which
  suggests that the line
  Unity.ActivationResponse.new(Unity.HandledType.SHOW_DASH) should pass
  a response to keep the dash open.  Instead, an error in generated
  suggesting that a second argument needs to be passed to the function.
  On adding a second argument, the error further suggests that it needs
  to be a string.  On using a string, the following error is generated:

  TypeError: can't convert return value to desired type
   ../pathtolens/lens.py:100: Warning: g_object_get_qdata: assertion 
G_IS_OBJECT (object)' failed GObject.MainLoop().run()
   ../pathtolens/lens.py:100: Warning: g_object_set_qdata_full: 
assertionG_IS_OBJECT (object)' failed GObject.MainLoop().run()
   ../pathtolens/lens.py:100: Warning: g_object_unref: assertion `G_IS_OBJECT 
(object)' failed GObject.MainLoop().run()

  Similar errors are generated when using other "Unity.Handletype"s
  (although using NOT_HANDLED only produces the TypeError part, not any
  of the warnings.)

  This issue is also described at http://askubuntu.com/questions/78826
  /cant-get-activate-uri-signal-working-when-making-a-lens

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/893688/+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 937576] Re: Coverity PW.PARAMETER_HIDDEN - CID 10651

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Coverity PW.PARAMETER_HIDDEN - CID 10651

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Nux 4.0 series:
  Fix Released
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  This bug is exported from the Coverity Integration Manager on Canonical's 
servers. For information on how this is done please see this website: 
https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
  CID: 10651
  Checker: PW.PARAMETER_HIDDEN
  Category: No category available
  CWE definition: No definition available
  File: /tmp/buildd/nux-2.4.0/Nux/AnimatedTextureArea.cpp
  Function: No function name available
  Code snippet:
   76 m_UserTexture = Texture;
   77 
   78 if (m_UserTexture)
   79 {
  CID 10651 - PW.PARAMETER_HIDDEN
  declaration hides parameter "Texture" (declared at line 74)
   80   ObjectPtr< CachedTextureFrameAnimation > Texture = 
GetGraphicsDisplay()->GetGraphicsEngine()->CacheResource(m_UserTexture);
   81   ObjectPtr AnimatedTexture = 
Texture->m_Texture; //Texture->m_Texture.CastRef();
   82   ObjectPtr Texture2D = Texture->m_Texture; 
//Texture->m_Texture.CastRef();
   83 
   84   AnimatedTexture->SetFiltering(GL_LINEAR, GL_LINEAR);
   85   AnimatedTexture->SetWrap(GL_CLAMP, GL_CLAMP, GL_CLAMP);

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/937576/+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 937564] Re: Coverity SECURE_CODING - CID 10659

2015-10-13 Thread Jaime Pérez
** Changed in: unity (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  Coverity SECURE_CODING - CID 10659

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Nux 4.0 series:
  Fix Released
Status in Unity:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  This bug is exported from the Coverity Integration Manager on Canonical's 
servers. For information on how this is done please see this website: 
https://wiki.ubuntu.com/CanonicalProductStrategy/Coverity
  CID: 10659
  Checker: SECURE_CODING
  Category: No category available
  CWE definition: http://cwe.mitre.org/data/definitions/676.html
  File: /tmp/buildd/nux-2.4.0/tools/unity_support_test.c
  Function: main()
  Code snippet:
  844 free (results.error);
  845 
  846   // drop result file
  847   if (results.result != 5) {
  CID 10659 - SECURE_CODING
  [VERY RISKY]. Using "sprintf" can cause a buffer overflow when done 
incorrectly.  Because sprintf() assumes an arbitrarily long string, callers 
must be careful not to overflow the actual space of the destination. Use 
snprintf() instead, or correct precision specifiers.
  848 sprintf(resultfilename, "/tmp/unity_support_test.%i", results.result);
  849 resultfile = open(resultfilename, O_CREAT|O_WRONLY|O_EXCL, 0666);
  850 if (resultfile > 0)
  851   close(resultfile);
  852   }
  853

To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/937564/+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 1505688] Re: Alerts like for calendar events should use a default sound different from alarms

2015-10-13 Thread Łukasz Zemczak
** Tags added: lt-blocker lt-category-visible

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

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505688/+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 1505688] Re: Alerts like for calendar events should use a default sound different from alarms

2015-10-13 Thread Launchpad Bug Tracker
** Branch linked: lp:~charlesk/indicator-datetime/15.10-lp-1505688
-different-default-sounds-for-alarms-and-events

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

Title:
  Alerts like for calendar events should use a default sound different
  from alarms

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Currently the new default alarm suond is used and it is not
  appropriate for calendar events

  Choose something like Marimbach

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

2015-10-13 Thread quequotion
However, it's the people *not* represented on launchpad that you're
*even more* wrong about.

-- 
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, _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 390508] Re: notifyOSD ignores the expire timeout parameter

2015-10-13 Thread quequotion
>>mpt

Just because I don't agree with you doesn't mean I don't understand your
lexicon.

I just think you're wrong. The group disproportionately represented on
launchpad is not who you think it is.

-- 
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, _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 1473269] Re: Wily login screen shows an all black notification bubble

2015-10-13 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/wily-proposed/notify-osd

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

Title:
  Wily login screen shows an all black notification bubble

Status in gtk+3.0 package in Ubuntu:
  Opinion
Status in notify-osd package in Ubuntu:
  In Progress

Bug description:
  Wily login screen shows an all black notification bubble. No idea what
  it says, obviously.

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