date:20161110

[Dx-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-10 Thread Michael Terry

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

** Also affects: pay-service (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: telephony-service (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: sync-monitor (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-10 Thread Launchpad Bug Tracker

** Branch linked: lp:~mterry/mediascanner2/snap-root

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-10 Thread Launchpad Bug Tracker

** Branch linked: lp:~mterry/address-book-service/snap-root

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-10 Thread Michael Terry

** Also affects: address-book-service (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1639472] Re: Alarm should provide GAction for toggling them

2016-11-10 Thread Treviño

Charles, yes.

Basically new desing requires toggalble alarms using a switch from the
indicator. So we'd need the backend to do provide an action in order to
do that.

Devid volunteered to help, but if this is a too big change I can handle
that too.

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

Title:
  Alarm should provide GAction for toggling them

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime should provide a GAaction for toggling the
  activation of alarms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1638716] Re: Hardcoded path in recoverable-problem may cause problems in Snappy

2016-11-10 Thread Charles Kerr

** Branch linked: lp:~charlesk/indicator-session/lp-1638716-recoverable-
whoopsie

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

Title:
  Hardcoded  path in recoverable-problem may cause problems in Snappy

Status in indicator-session package in Ubuntu:
  Triaged

Bug description:
  As described by mterry in 

  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.

  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638716/+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 1638716] Re: Hardcoded path in recoverable-problem needs evaluation for Snappy

2016-11-10 Thread Charles Kerr

Happily recoverable errors are handled in libwhoopsie, so indicator-
session can farm out that work.

Similar normalization patch in UAL:
https://code.launchpad.net/~ted/ubuntu-app-launch/recoverable-whoopsie/+merge/310212

** Changed in: indicator-session (Ubuntu)
   Status: Confirmed => Triaged

** Summary changed:

- Hardcoded  path in recoverable-problem needs evaluation for Snappy
+ Hardcoded  path in recoverable-problem may cause problems in Snappy

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

Title:
  Hardcoded  path in recoverable-problem may cause problems in Snappy

Status in indicator-session package in Ubuntu:
  Triaged

Bug description:
  As described by mterry in 

  > And I left the "/usr/share/apport/recoverable_problem" hardcoded path in
  > src/recoverable-problem.c. That seems like more of a deb-based reporting
  > tool anyway. And I wasn't sure there is some plan for snappy to include
  > an error reporting tool or what.

  I suspect we don't need this recoverable error anymore in indicator-
  session, so we could remove it. If we do still need it, we need to see
  if this approach needs any modification in the snappy world

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638716/+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 1611466] Re: Calendar crashes on ESC typing.

2016-11-10 Thread Charles Kerr

I'm marking this bug as closed due to your last comment on no longer
being able to reproduce it, either through an update or some other
reason. If the problem reappears for you in the future, please submit a
backtrace using the method linked to by seb128 in the comment above.
Thank you again for taking the time to report this bug and helping to
make Ubuntu better. Please submit any future bugs you may find.

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

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

Title:
  Calendar crashes on ESC typing.

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  When you click on date, it opens the calendar, if you type the ESC
  button on keyboard, the graphical interface crashes and in a few
  seconds it restart. During this few seconds or a minute, all the
  system stay frozen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1611466/+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 1639472] Re: Alarm should provide GAction for toggling them

2016-11-10 Thread Charles Kerr

Marco, could you explain more what you're asking for here? A way to
toggle on/off whether alarms will go off?

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

Title:
  Alarm should provide GAction for toggling them

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime should provide a GAaction for toggling the
  activation of alarms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1443052] Re: User accounts login history showing incorrect history - patch

2016-11-10 Thread Launchpad Bug Tracker

This bug was fixed in the package accountsservice - 0.6.40-2ubuntu11.3

---
accountsservice (0.6.40-2ubuntu11.3) xenial; urgency=medium

  * debian/patches/wtmp-fix-logout.patch:
- Backport 0.6.43 commit to fix logout records when a user
  shuts down or restarts their computer (LP: #1443052)

 -- Nikita Yerenkov-Scott   Tue, 25 Oct 2016
16:15:26 +0100

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

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1443052] Re: User accounts login history showing incorrect history - patch

2016-11-10 Thread Launchpad Bug Tracker

This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.3

---
accountsservice (0.6.35-0ubuntu7.3) trusty; urgency=medium

  * debian/patches/wtmp-fix-logout.patch:
 - Backport 0.6.43 commit to fix logout records when a user
   shuts down or restarts their computer (LP: #1443052)

 -- Nikita Yerenkov-Scott   Mon, 31 Oct 2016
20:12:38 +

** Changed in: accountsservice (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1443052] Update Released

2016-11-10 Thread Brian Murray

The verification of the Stable Release Update for accountsservice has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Released

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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

[Dx-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

2016-11-10 Thread Martin Pitt

Hello errors.ubuntu.com, or anyone else affected,

Accepted ido into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ido/13.10.0+16.04.20161028-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ido (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

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

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

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

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

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

  ===

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+subscriptions

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

[Dx-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Dx-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Dx-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Dx-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Dx-packages] [Bug 1639472] Re: Alarm should provide GAction for toggling them

[Dx-packages] [Bug 1638716] Re: Hardcoded path in recoverable-problem may cause problems in Snappy

[Dx-packages] [Bug 1638716] Re: Hardcoded path in recoverable-problem needs evaluation for Snappy

[Dx-packages] [Bug 1611466] Re: Calendar crashes on ESC typing.

[Dx-packages] [Bug 1639472] Re: Alarm should provide GAction for toggling them

[Dx-packages] [Bug 1443052] Re: User accounts login history showing incorrect history - patch

[Dx-packages] [Bug 1443052] Re: User accounts login history showing incorrect history - patch

[Dx-packages] [Bug 1443052] Update Released

[Dx-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

13 matches

Site Navigation

Mail list logo

Footer information