[Dx-packages] [Bug 1573639] Re: ownCloud Client system tray icon integration broken

2016-05-06 Thread Felicia 
The update from the proposed repository fixes the problem for me too.

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

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1193498] Re: Show quicklist even when closed

2016-05-06 Thread Cassidy James 
Still a thing in Loki. Not sure if/how we want to work around it.

** Also affects: switchboard
   Importance: Undecided
   Status: New

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

Title:
  Show quicklist even when closed

Status in libunity:
  New
Status in Switchboard:
  Opinion
Status in libunity package in Ubuntu:
  New

Bug description:
  We should show the quicklist in the dock even when Switchboard is
  closed.

  Here's a possible (somewhat dirty) workaround:

  1. Switchboard is launched
  2. Switchboard checks what plugs are available
  3. Switchboard makes sure the quicklist in its .desktop matches what's 
available

  Right now it's pretty useless to only show it when the app is open.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1193498/+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 1193498] Re: Show quicklist even when closed

2016-05-06 Thread Daniel Fore 
Also to be considered is that you can launch directly to plugs by
searching slingshot

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

Title:
  Show quicklist even when closed

Status in libunity:
  New
Status in Switchboard:
  Opinion
Status in libunity package in Ubuntu:
  New

Bug description:
  We should show the quicklist in the dock even when Switchboard is
  closed.

  Here's a possible (somewhat dirty) workaround:

  1. Switchboard is launched
  2. Switchboard checks what plugs are available
  3. Switchboard makes sure the quicklist in its .desktop matches what's 
available

  Right now it's pretty useless to only show it when the app is open.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1193498/+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 1193498] Re: Show quicklist even when closed

2016-05-06 Thread Daniel Fore 
Yeah I think the only way to do this would be to have an always running
process to do this. I'm inclined to mark it as either "opinon" or "won't
fix" because I'm not sure the benefits outway to performance drawbacks.
Opening Switchboard is fast already

** Changed in: switchboard
   Importance: Undecided => Wishlist

** Changed in: switchboard
   Status: New => Confirmed

** Changed in: switchboard
   Status: Confirmed => Opinion

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

Title:
  Show quicklist even when closed

Status in libunity:
  New
Status in Switchboard:
  Opinion
Status in libunity package in Ubuntu:
  New

Bug description:
  We should show the quicklist in the dock even when Switchboard is
  closed.

  Here's a possible (somewhat dirty) workaround:

  1. Switchboard is launched
  2. Switchboard checks what plugs are available
  3. Switchboard makes sure the quicklist in its .desktop matches what's 
available

  Right now it's pretty useless to only show it when the app is open.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1193498/+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 1295267] Re: Windows change Monitor/Desktop after screen lock

2016-05-06 Thread mreichardt 
With the Ubuntu Mate desktop, the window displacement issue does not occur on 
my system.
I just tried this - using different compositors (Marco and Compiz).

So until the window displacement issue is resolved, I am tempted to
stick to Ubuntu Mate.

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

Title:
  Windows change Monitor/Desktop after screen lock

Status in Unity:
  Fix Released
Status in Unity 7.1 series:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the windows
  are in the same position on the same monitor and desktop as I left
  them.

  What actually happens: When I unlock my computer, some or all of the
  windows have been changed to a random position on a random monitor
  and/or desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295267/+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 1573639] Re: ownCloud Client system tray icon integration broken

2016-05-06 Thread Reny 
The update from the proposed repository fixes the problem for me.

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

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1302004] Re: Indicator-datetime doesn't list in-progress events

2016-05-06 Thread Bruno Nova 
This wasn't fixed in 16.04 and 14.04 yet, right?

By the way, for those interested, I already uploaded a "fixed" version
for 16.04 to my PPA I mentioned before.

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1302004/+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-05-06 Thread Alejandro J. Cura 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

-- 
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:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Confirmed

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 1170366] Re: Broken handling of All-Day events

2016-05-06 Thread Pat McGowan 
** Changed in: indicator-datetime (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Broken handling of All-Day events

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  All-day events are not being shown on the day they occur, when that
  date is selected in the calendar, and all-day events which occur on
  Fridays seem to not be appearing at all. Furthermore, it also seems
  that all-day events which span multiple days are also handled poorly,
  listed as starting at 00:00 on the first day, and not appearing on the
  other days.

  In Online Services we have a few calendars for hours, meetings, and
  for the client engineering subteam we have review days, which we
  specify in a calendar. I have these calendars subscribed to in
  Evolution. The all-day events used to appear on the day they occurred,
  so this seems to be a regression.

  Some examples:

  All-day events; To see who is on call for reviews today, I must select
  the previous day. The event for Friday however, does not show up at
  all, so selecting Thursday dates on the calendar do not show me any
  future all-day events that occur on the Friday.

  Multi-day all-day event: I will be on holiday May 06-10, but this does
  not show correctly in the events list when I select any of those days.
  Instead, when I select the preceding Sunday May 05 in the calendar,
  the event shows as starting Monday at 00:00, rather than being an all-
  day event which spans multiple days.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu Apr 18 10:01:40 2013
  InstallationDate: Installed on 2012-10-21 (178 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to raring on 2012-12-24 (114 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1170366/+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 1170366] Re: Broken handling of All-Day events

2016-05-06 Thread Renato Araujo Oliveira Filho 
** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Broken handling of All-Day events

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  All-day events are not being shown on the day they occur, when that
  date is selected in the calendar, and all-day events which occur on
  Fridays seem to not be appearing at all. Furthermore, it also seems
  that all-day events which span multiple days are also handled poorly,
  listed as starting at 00:00 on the first day, and not appearing on the
  other days.

  In Online Services we have a few calendars for hours, meetings, and
  for the client engineering subteam we have review days, which we
  specify in a calendar. I have these calendars subscribed to in
  Evolution. The all-day events used to appear on the day they occurred,
  so this seems to be a regression.

  Some examples:

  All-day events; To see who is on call for reviews today, I must select
  the previous day. The event for Friday however, does not show up at
  all, so selecting Thursday dates on the calendar do not show me any
  future all-day events that occur on the Friday.

  Multi-day all-day event: I will be on holiday May 06-10, but this does
  not show correctly in the events list when I select any of those days.
  Instead, when I select the preceding Sunday May 05 in the calendar,
  the event shows as starting Monday at 00:00, rather than being an all-
  day event which spans multiple days.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu Apr 18 10:01:40 2013
  InstallationDate: Installed on 2012-10-21 (178 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to raring on 2012-12-24 (114 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1170366/+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 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications

2016-05-06 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

** Changed in: indicator-datetime (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-calendar-app
   Status: Fix Committed => Fix Released

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

Title:
  [calendar] Reminder notifications are not integrated into system
  notifications

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Calendar App:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  The calendar app does not use the standard notification system. You
  can't find it in the "Notifications" area of System Settings, and it
  uses its own notification sound regardless of what is set in "Sound".

  Also, reminders are not muted when the phone is in silent mode (I
  guess it's related).

  I'm on bq Aquaris, r20 and with the latest calendar-app.

  --- --- --- ---
  UX Comment:

  Calendar Notifications need to be overhauled:
  -- Calendar Notifications are displayed for too brief a period and should 
conform to the same timing as other notifications.

  -- Calendar Notifications are not currently appearing in the
  notification tray within indicators and should be.

  -- Calendar Notification title is misleading ('Alarm') and should make
  clear that the notification relates to a calendar event ('Event') and
  not a alarm-clock event.

  -- Calendar Notification's should NOT override silent mode (unlike
  clock-alarms) although the notification should still be displayed,
  appear in the notification within indicators and cause the device to
  vibrate (if enabled) - This is accepted/common behaviour for
  notifications of this type on mobile.

  Notifications Spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+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 1302004] Re: Indicator-datetime doesn't list in-progress events

2016-05-06 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1302004/+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 1170366] Re: Broken handling of All-Day events

2016-05-06 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Broken handling of All-Day events

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  All-day events are not being shown on the day they occur, when that
  date is selected in the calendar, and all-day events which occur on
  Fridays seem to not be appearing at all. Furthermore, it also seems
  that all-day events which span multiple days are also handled poorly,
  listed as starting at 00:00 on the first day, and not appearing on the
  other days.

  In Online Services we have a few calendars for hours, meetings, and
  for the client engineering subteam we have review days, which we
  specify in a calendar. I have these calendars subscribed to in
  Evolution. The all-day events used to appear on the day they occurred,
  so this seems to be a regression.

  Some examples:

  All-day events; To see who is on call for reviews today, I must select
  the previous day. The event for Friday however, does not show up at
  all, so selecting Thursday dates on the calendar do not show me any
  future all-day events that occur on the Friday.

  Multi-day all-day event: I will be on holiday May 06-10, but this does
  not show correctly in the events list when I select any of those days.
  Instead, when I select the preceding Sunday May 05 in the calendar,
  the event shows as starting Monday at 00:00, rather than being an all-
  day event which spans multiple days.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu Apr 18 10:01:40 2013
  InstallationDate: Installed on 2012-10-21 (178 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to raring on 2012-12-24 (114 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1170366/+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 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

2016-05-06 Thread Bartosz Kosiorek 
** 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 accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1512002

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Invalid
Status in policykit-1-gnome package in Ubuntu:
  Invalid
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  * Impact

  Sometimes useless "Authentication is required to change your own user
  data" prompts are displayed

  * Test case

  
  $ ssh -X localhost
  $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
  $ dbus-send --system --print-reply=literal --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts/User1001 
org.freedesktop.Accounts.User.SetXHasMessages boolean:true

  that shouldn't trigger a prompt

  * Regression potential

  it allows the change to be done without prompting in more cases,
  shouldn't have an impact on cases which were already working

  
  --

  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1512002/+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 1362962] Re: Calendar icon usually shows the wrong date

2016-05-06 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Calendar icon usually shows the wrong date

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Calendar App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Fix Committed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Problem occurs with: Ubuntu 14.10 r203
  Does not occur with: iOS, Windows Phone

  1. In the clock menu, find the calendar app and launch it.
  2. In the Launcher or Dash, find the Calendar app.

  What you see:
  1. The icon always says "25", regardless of the actual date.
  2. The icon always says "28", regardless of the actual date.

  What you should see:
  1. The icon shows the current date.
  2. The icon shows the current date.

  The equivalent for PC is bug 1362033, and for the Clock app is bug
  1362964.

  This depends on bug 1453795 for Unity letting an app change its own
  icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362962/+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 1508438] Re: Do not notify for events marked as not attending

2016-05-06 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

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

Title:
  Do not notify for events marked as not attending

Status in Canonical System Image:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This is a follow-up from bug #1371871. While it was marked as Fix
  Released, it doesn't seem to have had any effect. I'm reporting it as
  two separate bugs to reopen it now.

  I've got a few events in my calendar for meetings where I'm marked as
  not going, which I still want to see in my calendar unless I
  explicitly delete them.

  An example is a recurring event which I've got on my work calendar. During my 
holiday:
  - I'll mark myself as not attending
  - I will not delete the event
  - I don't expect to be notified

  As I'm not marked as attending, I wouldn't expect to get a reminder
  notification, even less if I'm in a different timezone and it's 3:00
  a.m. :)

  See bug 1508440 for the "display events not being attended clearly"
  part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508438/+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 1533681] Re: imported google calendar events sound when they shouldn't

2016-05-06 Thread Pat McGowan 
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

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

Title:
  imported google calendar events sound when they shouldn't

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Calendar App:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  I use the calendar-app with my work google calendar. For that calendar
  I have alarms setup to automatically send an email 24 hours, 4 hours
  and 30 minutes before any event and I choose email as the reminder (as
  opposed to popup) so that I wouldn't be bombarded with reminders all
  day. Unfortunately the calendar app does not make a distinction
  between email and popup and every event with an email reminder gets
  imported as an event that gets an event notification on the phone with
  an alarm sound. I have a lot of events in my calendar and so my phone
  is constantly making noise at all times of the day. This is
  particularly annoying at night time since I might get a reminder as
  early as 3am or 4am, which wakes me up. Of course, I could use silent
  mode at night, but, like last night, I forgot and was awoken at 6am.
  Plus, I don't necessarily want the phone in silent mode-- I'd like to
  be able to hear if a phone call comes in since that is likely an
  emergency call I need to take.

  There are a lot of different bugs related to calendar event
  notifications and if some of them were fixed, it would ameliorate this
  bug. For example, I've been hoping for a setting to disable sounds for
  just the calendar (whether via the app or system settings) but
  otherwise get calendar notifications. Being able to change the alarm
  sound to 'None' would work too. TBH at this point I don't care which
  bug is fixed, I need to get this phone to stop sounding off
  constantly.

  WORKAROUND:
  1. download https://commons.wikimedia.org/wiki/File:Silence.ogg to 
/home/phablet
  2. use gsettings to adjust the sound:
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/usr/share/sounds/ubuntu/ringtones/Marimbach.ogg'
  $ DISPLAY=:0.0 gsettings set com.canonical.indicator.datetime 
calendar-default-sound /home/phablet/Silence.ogg 
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/home/phablet/Silence.ogg'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533681/+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 1401802] Re: [Scopes] Calendar reminder notifications became queued, non-interactive and easy to miss

2016-05-06 Thread Pat McGowan 
** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Scopes] Calendar reminder notifications became queued, non-
  interactive and easy to miss

Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  With the recent indicator-datetime update the reminder notifications time out 
and are not interactive any more, meaning that:
  - can't dismiss (have to wait for the sound/notification to time out)
  - can't snooze (I know the feature didn't work, but that was a missing 
feature, not a thing we didn't want?)
  - if you missed the notification, you missed the reminder

  Not sure if the reason is the same, but they started queueing, too,
  i.e. if there's two reminders for the same time, sound will play for
  both (bug #1340248), but the two notifications will be shown one after
  another.

  This is a UX regression in my opinion, even if it fixes bug #1320880.

  There is actually no clear design for this, I'm afraid,
  
https://sites.google.com/a/canonical.com/apps-and-platform-team/3-platform/2-notifications

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20141208-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: armhf
  Date: Fri Dec 12 08:59:10 2014
  InstallationDate: Installed on 2014-12-12 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141212-020204)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  -- UX Comment --

  We've added the desired behaviour in the latest specification for
  notifications bubbles:

  Pages: 10-22 Notification bubble in normal use
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.6g43lpfdbptu

  Specific to remiders notifications: Notifications from missed calls,
  calendar events and reminders, are exceptions and won't ever be
  presented in a summary layout because of their different nature. They
  are time-sensitive (especially if these events involve other people
  actively waiting on a response) and may change the user's behaviour in
  the real world.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1401802/+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 1570812] Re: [UIFe] Window actions such as Minimize, Maximize, Restore, Move, Resize... Aren't accessible from HUD

2016-05-06 Thread Gunnar Hjalmarsson 
The desktop guide does not describe HUD at this level of detail.

** No longer affects: ubuntu-docs (Ubuntu)

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

Title:
  [UIFe] Window actions such as Minimize, Maximize, Restore, Move,
  Resize... Aren't accessible from HUD

Status in bamf package in Ubuntu:
  Fix Released
Status in hud package in Ubuntu:
  Fix Released
Status in libwnck3 package in Ubuntu:
  Fix Released

Bug description:
  The Window menu actions (those currently accessible by right-clicking
  the decorations, or by Alt+space) aren't listed in HUD.

  Moving the UIFe side of things from bug #1551986.
  ACKed: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1551986/comments/9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1570812/+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 500547] Re: "Battery low" overwritten with "incorrect urgency?"

2016-05-06 Thread Matthew Paul Thomas 
Richard, if this is happening for you, you probably have a very old test
version of notify-osd installed. Try uninstalling and reinstalling it.

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

Title:
  "Battery low" overwritten with "incorrect urgency?"

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: notify-osd

  Notify On Screen Display is a fancy flickery alert method that pops up
  on top of inconvenient places on the Desktop in order to display
  messages to the user.  When ordered to display a message:

Laptop battery low
Approximately 19 minutes remaining (12.4%)

  it now fails to draw a smooth, or transparent background and now
  overwrites the message with thin orange marker lines lines and a big
  green blob containing:

normal - report incorrect urgency?

  Ideally, the 'n' in "normal" should be capitalised and the incorrect
  typographical use of a hyphen be replaced with an emdash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/500547/+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 1295267] Re: Windows change Monitor/Desktop after screen lock

2016-05-06 Thread mreichardt 
Looking at the /var/log/Xorg.0.log, it appears that the Iiyama screen is
considered disconnected on standby - and the reconnect causes a relayout
of the desktop.

I wonder if it's possible to simply suppress or ignore those hotplug
events (?)

This is the output in the /var/log/Xorg.0.log on a standby cycle:

[ 31292.359] (--) NVIDIA(GPU-0): DFP-6: disconnected
[ 31292.359] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[ 31292.359] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[ 31292.359] (--) NVIDIA(GPU-0): 
[ 31292.362] (--) NVIDIA(GPU-0): CRT-0: disconnected
[ 31292.362] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 31292.362] (--) NVIDIA(GPU-0): 
[ 31292.365] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 31292.365] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0): 
[ 31292.365] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 31292.365] (--) NVIDIA(GPU-0): DFP-1: 330.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0): 
[ 31292.365] (--) NVIDIA(GPU-0): DFP-2: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[ 31292.365] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0): 
[ 31292.365] (--) NVIDIA(GPU-0): DFP-3: disconnected
[ 31292.365] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 31292.365] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 31292.365] (--) NVIDIA(GPU-0): 
[ 31292.366] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): connected
[ 31292.366] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): Internal DisplayPort
[ 31292.366] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): 960.0 MHz maximum pixel 
clock
[ 31292.366] (--) NVIDIA(GPU-0): 
[ 31292.366] (--) NVIDIA(GPU-0): DFP-5: disconnected
[ 31292.366] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[ 31292.366] (--) NVIDIA(GPU-0): DFP-5: 330.0 MHz maximum pixel clock
[ 31292.366] (--) NVIDIA(GPU-0): 
[ 31292.366] (--) NVIDIA(GPU-0): DFP-6: disconnected
[ 31292.366] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[ 31292.366] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
[ 31292.366] (--) NVIDIA(GPU-0): 
[ 31292.366] (--) NVIDIA(GPU-0): DFP-7: disconnected
[ 31292.366] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[ 31292.366] (--) NVIDIA(GPU-0): DFP-7: 330.0 MHz maximum pixel clock
[ 31292.366] (--) NVIDIA(GPU-0): 
[ 31292.573] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @3840x2160 
+0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}"
[ 31292.987] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID 
for display
[ 31292.987] (**) NVIDIA(0): device Idek Iiyama PL2888UH (DFP-6) (Using EDID
[ 31292.987] (**) NVIDIA(0): frequencies has been enabled on all display 
devices.)
[ 31292.992] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): connected
[ 31292.992] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): Internal 
DisplayPort
[ 31292.992] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): 960.0 MHz 
maximum pixel clock
[ 31292.992] (--) NVIDIA(GPU-0): 
[ 31293.113] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @3840x2160 
+0+0 {ViewPortIn=3840x2160, ViewPortOut=3840x2160+0+0}, DP-4: 
nvidia-auto-select @3840x2160 +3840+0 {ViewPortIn=3840x2160, 
ViewPortOut=3840x2160+0+0}"
[ 31293.482] (--) NVIDIA(GPU-0): CRT-0: disconnected
[ 31293.482] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 31293.483] (--) NVIDIA(GPU-0): 
[ 31293.485] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 31293.485] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 31293.485] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 31293.485] (--) NVIDIA(GPU-0): 
[ 31293.488] (--) NVIDIA(GPU-0): DFP-1: disconnected
[ 31293.489] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 31293.489] (--) NVIDIA(GPU-0): DFP-1: 330.0 MHz maximum pixel clock
[ 31293.489] (--) NVIDIA(GPU-0): 
[ 31293.489] (--) NVIDIA(GPU-0): DFP-2: disconnected
[ 31293.489] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[ 31293.489] (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
[ 31293.489] (--) NVIDIA(GPU-0): 
[ 31293.489] (--) NVIDIA(GPU-0): DFP-3: disconnected
[ 31293.489] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 31293.489] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 31293.489] (--) NVIDIA(GPU-0): 
[ 31293.489] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): connected
[ 31293.489] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): Internal DisplayPort
[ 31293.489] (--) NVIDIA(GPU-0): DELL P2715Q (DFP-4): 960.0 MHz maximum pixel 
clock
[ 31293.489] (--) NVIDIA(GPU-0): 
[ 31293.490] (--) NVIDIA(GPU-0): DFP-5: disconnected
[ 31293.490] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[ 31293.490] (--) NVIDIA(GPU-0): DFP-5: 330.0 MHz maximum pixel clock
[ 31293.490] (--) NVIDIA(GPU-0): 
[ 31293.490] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): connected
[ 31293.490] (--) NVIDIA(GPU-0): Idek Iiyama PL2888UH (DFP-6): Internal 
DisplayPort
[ 31293.490]

[Dx-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

2016-05-06 Thread mreichardt 
** Tags added: xenial

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

Title:
  Windows change Monitor/Desktop after screen lock

Status in Unity:
  Fix Released
Status in Unity 7.1 series:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the windows
  are in the same position on the same monitor and desktop as I left
  them.

  What actually happens: When I unlock my computer, some or all of the
  windows have been changed to a random position on a random monitor
  and/or desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295267/+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 1295267] Re: Windows change Monitor/Desktop after screen lock

2016-05-06 Thread mreichardt 
I have this problem in Ubuntu 14.04 and 16.04 with a dual 4K screen
setup (using a nvidia GPU).

Sometimes when waking the screens from standby ("Power Save Mode"), windows on 
the right screen are moved to an invisible offscreen area.
Using keyboard shortcuts, they can be moved to the visible area again.

I just ran my screens through ~10 standby cycles in different configurations.
One screen (Dell) wakes from standby almost immediately - the other (Iiyama) 
needs around 3 seconds. For simplicity, I will refer to them as quick and slow 
screen.
Both screens are connected via DisplayPort.
The driver from Ubuntu's nvidia-361 package is used.

I made the following observations:
* Window displacement happens on the right screen only.
* When the quick screen is the right screen, you can see the windows at the 
correct positions after wakeup, then the slow screen wakes up, reinitialization 
seems to be triggered (both screens are black for one second) and after that 
the windows are displaced (sometimes).
* When the quick screen is the right screen, random displacement seems to 
happen only once per Unity Session (if I logged out and in again, it happened 
again). When the slow screen is the right screen, it happens more often.
* When window displacement occurs, windows seem to be swapped between the right 
screen and the invisible offscreen area (-> windows still in the invisible 
offscreen area reappear at their former positions).
* Swapping the DisplayPort connectors at the Graphics Adapter does not have an 
impact on the behaviour.
* KDE also displaces windows on wakeup. They are moved to screen edges instead 
of invisible offscreen areas.

---

I am using the tint2 taskbar (window displacement also occurs without tint2). 
Its command line output at screen wakeup might be interesting.
There are two variants of output (see below). Window displacement may occur on 
either.
If displacement occurs, tint2 and also the menus in the title bar are often 
broken on one screen - until I restart tint2.

First variant:

/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1163: triggering tint2 restart due 
to configuration change in the root window
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1883: restarting tint2...
xRandr: Found crtc's: 3
xRandr: Linking output DP-2 with crtc 0
xRandr: Linking output DP-4 with crtc 1
xsettings: Gtk/FontName = Ubuntu 11
xsettings: Net/IconThemeName = ubuntu-mono-dark
real transparency on... depth: 32
panel items: TSC
Systray composited rendering on
tint2 : nb monitor 2, nb monitor used 2, nb desktop 1
Kernel uevent interface initialized...

Second variant:

/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1163: triggering tint2 restart due 
to configuration change in the root window
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1883: restarting tint2...
xRandr: Found crtc's: 3
xRandr: Linking output DP-2 with crtc 0
xsettings: Gtk/FontName = Ubuntu 11
xsettings: Net/IconThemeName = ubuntu-mono-dark
real transparency on... depth: 32
panel items: TSC
Systray composited rendering on
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Kernel uevent interface initialized...
tint2 : another systray is running pid=1908
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1163: triggering tint2 restart due 
to configuration change in the root window
/build/tint2-6JO0z5/tint2-0.12.7/src/tint.c 1883: restarting tint2...
xRandr: Found crtc's: 3
xRandr: Linking output DP-2 with crtc 0
xRandr: Linking output DP-4 with crtc 1
xsettings: Gtk/FontName = Ubuntu 11
xsettings: Net/IconThemeName = ubuntu-mono-dark
real transparency on... depth: 32
panel items: TSC
Systray composited rendering on
tint2 : nb monitor 2, nb monitor used 2, nb desktop 2
Kernel uevent interface initialized...

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

Title:
  Windows change Monitor/Desktop after screen lock

Status in Unity:
  Fix Released
Status in Unity 7.1 series:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I run a dual monitor configuration, with one portrait and one
  landscape.

  I nearly always have multiple applications open in multiple windows
  across both monitors and all virtual desktops.

  When I lock the screen and then unlock, my application windows will
  move from their original position.

  Sometimes they are in completely random positions;

  Other times they seem to get the monitors confused, and rather than
  being in the top half of the portrait monitor they are on the top half
  of the landscape monitor;

  Sometimes it is only a new desktop, but the monitor position is the
  same;

  Sometimes it is the same desktop, but on the other monitor.

  Description:  Ubuntu 13.10
  Release:  13.10

  What I expect to happen: When I unlock my computer, all the

[Dx-packages] [Bug 1573639] Re: ownCloud Client system tray icon integration broken

2016-05-06 Thread luca 
Thanks @nhaines : there was this bug
https://bugs.launchpad.net/bugs/1572321 filed yet.

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

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+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 1573639] Re: ownCloud Client system tray icon integration broken

2016-05-06 Thread Nathan Haines 
Luca, this is not related to this bug, which is only about the indicator
icon.  Please create a new bug regarding your issue--it can be
troubleshooted and discussed there.

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

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Triaged
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Confirmed
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Triaged
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

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