[Dx-packages] [Bug 1623768] Re: Adapt to new Totem icon name
This bug was fixed in the package xubuntu-artwork - 16.10.1 --- xubuntu-artwork (16.10.1) yakkety; urgency=medium [ Pasi Lallinaho ] * Update wallpaper (desktop and plymouth) (LP: #1629650) [ Sean Davis ] * Add support for new icon naming for Totem (LP: #1623768) * Add 64px xfce4-notifyd icon * Add audio-volume-off symbolic icon -- Sean Davis Tue, 04 Oct 2016 17:36:49 -0400 ** Changed in: xubuntu-artwork (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1623768 Title: Adapt to new Totem icon name Status in humanity-icon-theme package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Fix Committed Status in moka-icon-theme package in Ubuntu: Fix Released Status in ubuntukylin-theme package in Ubuntu: Confirmed Status in xubuntu-artwork package in Ubuntu: Fix Released Bug description: Totem has changed its icon name for easier integration with flatpak -Icon=totem +Icon=org.gnome.Totem If your icon theme will be used in Ubuntu 16.04 LTS also, then I recommend making a symlink from the totem icon to the new org.gnome.Totem icon. Alternatively, you could drop the icon and let users use the high resolution icons shipped by Totem itself. See also bug 1618138 which lists some other app icon name changes but those icons aren't shipped in all themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
Is Nexus4 a no longer supported device? :O This is the only phone what a new user can buy. I don't think it's a good decision. -- 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/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
This bug was fixed in the package unity-settings-daemon - 15.04.1+16.10.20161003-0ubuntu1 --- unity-settings-daemon (15.04.1+16.10.20161003-0ubuntu1) yakkety; urgency=medium [ Dmitry Shachnev ] * Upstart: Split XDG_CURRENT_DESKTOP properly and start only on Unity sessions [ Iain Lane ] * Check XDG_CURRENT_DESKTOP properly in the keyboard plugin (LP: #1554878) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Mon, 03 Oct 2016 10:15:27 + ** Changed in: unity-settings-daemon (Ubuntu) Status: Fix Committed => Fix Released -- 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/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
This bug was fixed in the package indicator-bluetooth - 0.0.6+16.10.20161003-0ubuntu1 --- indicator-bluetooth (0.0.6+16.10.20161003-0ubuntu1) yakkety; urgency=medium [ Robert Ancell ] * Correctly use XDG_CURRENT_DESKTOP (LP: #1554878) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Mon, 03 Oct 2016 10:15:04 + ** Changed in: indicator-bluetooth (Ubuntu) Status: Fix Committed => Fix Released -- 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/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Committed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+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 1630391] [NEW] Zeitgeist-fts consumes 6 - 900 mb memory and slows down the system
Public bug reported: Zeitgeist-fts consumes 6 - 900 mb memory and slows down the system. I have tried to kill it, but it comes back after reboot and ends up using that much again after a couple of hours. I'm on Ubuntu 16.10 Beta 2 fully updated. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: zeitgeist (not installed) ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 4 17:59:58 2016 InstallationDate: Installed on 2016-08-18 (47 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: zeitgeist UpgradeStatus: Upgraded to yakkety on 2016-09-14 (20 days ago) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1630391 Title: Zeitgeist-fts consumes 6 - 900 mb memory and slows down the system Status in zeitgeist package in Ubuntu: New Bug description: Zeitgeist-fts consumes 6 - 900 mb memory and slows down the system. I have tried to kill it, but it comes back after reboot and ends up using that much again after a couple of hours. I'm on Ubuntu 16.10 Beta 2 fully updated. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: zeitgeist (not installed) ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 4 17:59:58 2016 InstallationDate: Installed on 2016-08-18 (47 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: zeitgeist UpgradeStatus: Upgraded to yakkety on 2016-09-14 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1630391/+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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
gnome-session (3.20.2-1ubuntu6) yakkety; urgency=medium * Set DesktopNames back to Unity. There are many buggy components that don't know how to deal with XDG_CURRENT_DESKTOP having multiple values, and it's too close to the release to fix them all. -- Iain Lane Mon, 03 Oct 2016 17:37:57 +0100 -- 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/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Committed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+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
This bug was fixed in the package accountsservice - 0.6.42-0ubuntu1 --- accountsservice (0.6.42-0ubuntu1) yakkety; urgency=medium * New upstream bugfix release. - allow a user to change his own data even if he's remote - add way to set password hint independent of password - conform to modern systemd library naming scheme - disable GVFS support in service, since it's not needed and has bad side effects * Drop patches applied in new version: - 0014-libsystemd.patch - change-own-data-inactive.patch * Add 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) -- Jeremy Bicha Tue, 04 Oct 2016 09:04:41 -0400 ** Changed in: accountsservice (Ubuntu) Status: Confirmed => 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 Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug 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 1554504] Re: [mako] Calendar reminder does not wake phone when airplane mode is enabled
These seems specific to the Nexus 4, moving to backlog as it is no longer actively supported ** Summary changed: - Calendar reminder does not wake phone when airplane mode is enabled + [mako] Calendar reminder does not wake phone when airplane mode is enabled ** Changed in: canonical-devices-system-image Milestone: 14 => backlog -- 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/1554504 Title: [mako] Calendar reminder does not wake phone when airplane mode is enabled Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Incomplete Bug description: If airplane mode is enabled, the phone seems to go into a deep sleep where it doesn't wake up for a calendar reminder. The reminder does not sound until the power button is pressed to wake the phone, in some cases this has been more than an hour after the reminder was scheduled for. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
These seems specific to the Nexus 4, moving to backlog as it is no longer actively supported ** Summary changed: - Alarm doesn't ring when screen locked + [mako] Alarm doesn't ring when screen locked ** Changed in: canonical-devices-system-image Milestone: 14 => backlog -- 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/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1126108] Re: Indicator disappears entirely when disabling / turning off bluetooth
This issue also effects 16.10.
--
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/1126108
Title:
Indicator disappears entirely when disabling / turning off bluetooth
Status in indicator-bluetooth package in Ubuntu:
Fix Released
Bug description:
Bug 1116289 made the BT indicator disappear when there is no hardware.
However, with that version I now also have it disappear when my
existing BT hardware is merely disabled. I. e. I disable BT from the
indicator, then it disappears, leaving me no obvious method to turn it
back on again. I can re-enabble it in control-center, and then the
indicator comes back.
I think when it sees no actual BT hardware it ought to check rfkill
whether there is disabled BT hardware:
$ grep -r . /sys/class/rfkill/rfkill0/{type,state,soft,persistent}
/sys/class/rfkill/rfkill0/type:bluetooth
/sys/class/rfkill/rfkill0/state:1
/sys/class/rfkill/rfkill0/soft:0
/sys/class/rfkill/rfkill0/persistent:1
After disabling BT from the indicator, "soft" changes to 1:
$ grep -r . /sys/class/rfkill/rfkill0/{type,state,soft,persistent}
/sys/class/rfkill/rfkill0/type:bluetooth
/sys/class/rfkill/rfkill0/state:0
/sys/class/rfkill/rfkill0/soft:1
/sys/class/rfkill/rfkill0/persistent:1
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: indicator-bluetooth 0.0.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Fri Feb 15 12:08:26 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-02-08 (7 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130207.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: indicator-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108/+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
** Also affects: gnome-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unity-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: accountsservice (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu Xenial) Status: New => Triaged ** Changed in: unity-control-center (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: unity-control-center (Ubuntu Xenial) Status: New => Triaged ** Changed in: ubuntu-gnome Status: Confirmed => Triaged ** Changed in: ubuntu-gnome Importance: Undecided => Low -- 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 Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug 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 1628260] Re: Upgrade libglew package to also include libglew2
libglew2 seems to be included in Debian unstable: https://launchpad.net/debian/+source/glew -- You received this bug notification because you are a member of DX Packages, which is subscribed to glew in Ubuntu. https://bugs.launchpad.net/bugs/1628260 Title: Upgrade libglew package to also include libglew2 Status in glew package in Ubuntu: New Bug description: Currently glew package only includes versions up to 1.13, but the latest release is 2.0. As a developer, it would be best to have libglew2 and libglew2-dev available on Ubuntu. See http://glew.sourceforge.net/ for more information about the new (and previous) version(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1628260/+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
This bug was fixed in the package gnome-control-center - 1:3.20.1-2ubuntu2 --- gnome-control-center (1:3.20.1-2ubuntu2) yakkety; urgency=medium * Cherrypick commits from the 3.20 branch since there was never a 3.20.2 release. See patch headers or git for descriptions of issues fixed. - 0002-mouse-Make-touchpad-capability-checking-on-wayland-w.patch - 0007-universal-access-allow-focus-on-row-switches.patch - 0008-mouse-allow-focus-on-switches-in-the-Touchpad-sectio.patch - 0014-network-fix-some-SSID-escaping-issues.patch - 0016-user-accounts-Fix-missing-records-in-the-history-dia.patch (LP: #1443052) - 0020-privacy-React-to-changes-in-permissions-store.patch - 0021-privacy-Update-for-PermissionStore-DBus-API-changes.patch - 0025-power-Fix-hiding-wi-fi-mobile-broadband-toggles.patch - 0026-power-Fix-wifi-device-state-when-opening-power-panel.patch - 0027-printers-Fix-compilation-warning.patch - 0028-display-Fix-possible-crash-on-startup.patch -- Jeremy Bicha Tue, 04 Oct 2016 06:52:59 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => 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 Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug 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
