[Dx-packages] [Bug 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
The main issue is when I updated to 0.6.55 the new Meson based build systemd didn't build with systemd support by default. So I've uploaded a build with this enabled. There may still be an underlying issue, but this should fix the eoan issues. ** Changed in: accountsservice (Ubuntu) Status: Confirmed => Fix Committed -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice: New Status in accountsservice package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1841382/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
Upstream bug report opened: https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/80 ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/issues #80 https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/80 -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
If the above theory is correct then this commit caused the bug: https://gitlab.freedesktop.org/accountsservice/accountsservice/commit/9b4108755a6e1f5f04d80fef92dd3f81423857ad This commit came when we migrated from 0.6.45 to 0.6.50, which explains why this is being seen in disco and eoan. -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
It looks like it's crashing in this code: username = act_user_get_user_name (user); if (g_hash_table_lookup (priv->system_users_by_name, username) != NULL) { and username is probably NULL. A possible cause of this is the user object for some reason might not have a DBus proxy backing it. -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841382/+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 1841079] Re: Speech Dispatcher and other non-human users should not be shown on LightdDM login screen and session menus
Can you please test accountsservice 0.6.55-0ubuntu7 and confirm if this fixes these users? -- 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/1841079 Title: Speech Dispatcher and other non-human users should not be shown on LightdDM login screen and session menus Status in accountsservice package in Ubuntu: Triaged Status in accountsservice source package in Eoan: Triaged Bug description: Steps to reproduce: 1. Download Ubuntu MATE 19.10 alpha ISO - 20190822 2. Install it using Entire-disk erase scenario with default settings 3. Reboot system Expected results: * LightDM shows only just created username Actual results: * LightDM shows two user names, Speech Dispatcher is selected by default Note: problem occurs on VM and on real hardware; Minimal desktop installation is affected too; OEM installation is affected by bug 1840971 . ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: speech-dispatcher 0.9.1-2 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Aug 22 19:02:42 2019 InstallationDate: Installed on 2019-08-22 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841079/+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 1789502] Re: Update to 0.6.50
** Changed in: accountsservice (Ubuntu) Status: In Progress => Fix Committed -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: Fix Committed Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
** Attachment added: "accountsservice_0.6.50-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+attachment/5190482/+files/accountsservice_0.6.50-0ubuntu1.debian.tar.xz -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
** Patch added: "accounts-service-0.6.50.debdiff" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+attachment/5190483/+files/accounts-service-0.6.50.debdiff -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
indicator-messages was updated in https://code.launchpad.net/~robert- ancell/indicator-messages/has-messages/+merge/355127 -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1789502] Re: Update to 0.6.50
On Thu, Sep 6, 2018 at 9:42 PM Sebastien Bacher wrote: > Hey Robert, > > Le 06/09/2018 à 10:27, Robert Ancell a écrit : > > I'm also looking at dropping the XHasMessages, BackgroundFile and > > KeyboardLayouts patches, as these are all obsolete with LightDM 1.26 - > > Is there anywhere else that might be using them? > > How "obsolete"? XHasMessages is (was?) using by unity-greeter to > indicate with an icon that there are pending messages in the session. > Did that feature got removed or superseeded? > > LightDM 1.26 uses the AccountsService extention mechanism to store this data, so the patch is obsolete. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
Patches are here: https://gitlab.freedesktop.org/rancell/accountsservice/tree/ubuntu Please test / look over. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
I'm also looking at dropping the XHasMessages, BackgroundFile and KeyboardLayouts patches, as these are all obsolete with LightDM 1.26 - Is there anywhere else that might be using them? Does anyone know if the InputSources and FormatsLocale is still applicable and which components use it? If they are still used I'd like to fix those to use the AccountsService extension mechanism - then we can drop the patches. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
I don't have it currently in a branch but I'm working on doing that. -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
Gunnar - could you perhaps have a look at 0010-set-language.patch? In particular I'm not sure how we want to do the fallback language property handling in src/user.c - the new code uses autogenerated property handling so we can't intercept it as easily. I guess we could just set the fallback values on initialization? -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
I have all the patches updated except for 0010-set-language.patch -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: accountsservice (Ubuntu) Status: New => In Progress -- 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/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1772338] Re: Deprecation warning compiling against unity.vapi
That tag comes from src/unity-appinfo-manager.vala so a code change is required: https://code.launchpad.net/~robert-ancell/libunity/update-deprecation-tags/+merge/353363 -- 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/1772338 Title: Deprecation warning compiling against unity.vapi Status in libunity package in Ubuntu: Triaged Bug description: Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it with "Version". The copy of unity.vapi shipped by libunity-dev in bionic still uses the Deprecated attribute, however. I.e. in unity.vapi: [Deprecated (replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); Should instead be: [Version (deprecated = true, replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); This causes a deprecation warning when compiling against it, regardless of whether any deprecated calls are actually being made by the code being compiled. While a minor issue, it would be good to have fixed since it makes it impossible to develop against it with fatal warnings enabled, which is bad for QA. The Unity build seems to generate that file as per usual (as a valac build artefact) so I would assume this should be fixed by a simple rebuild using vala >= 0.31.1, but surely the version of libunity-dev that shipped with bionic would have been rebuild against valac that ships with bionic (0.40)? So I'm not sure why Deprecated is still present in the vapi. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libunity-dev 7.1.4+18.04.20180209.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 21 10:45:08 2018 InstallationDate: Installed on 2015-07-22 (1033 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1772338/+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 1772338] Re: Deprecation warning compiling against unity.vapi
** Changed in: libunity (Ubuntu) Status: Confirmed => Triaged ** Changed in: libunity (Ubuntu) Importance: Undecided => Medium -- 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/1772338 Title: Deprecation warning compiling against unity.vapi Status in libunity package in Ubuntu: Triaged Bug description: Vala 0.31.1 deprecated the "Deprecated" code attribute, replacing it with "Version". The copy of unity.vapi shipped by libunity-dev in bionic still uses the Deprecated attribute, however. I.e. in unity.vapi: [Deprecated (replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); Should instead be: [Version (deprecated = true, replacement = "AppInfoManager.get_default")] public static Unity.AppInfoManager get_instance (); This causes a deprecation warning when compiling against it, regardless of whether any deprecated calls are actually being made by the code being compiled. While a minor issue, it would be good to have fixed since it makes it impossible to develop against it with fatal warnings enabled, which is bad for QA. The Unity build seems to generate that file as per usual (as a valac build artefact) so I would assume this should be fixed by a simple rebuild using vala >= 0.31.1, but surely the version of libunity-dev that shipped with bionic would have been rebuild against valac that ships with bionic (0.40)? So I'm not sure why Deprecated is still present in the vapi. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libunity-dev 7.1.4+18.04.20180209.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 21 10:45:08 2018 InstallationDate: Installed on 2015-07-22 (1033 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1772338/+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 872908] Re: Blank entry in switch user account menu
** Changed in: indicator-session Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/872908 Title: Blank entry in switch user account menu Status in Session Menu: Fix Committed Status in indicator-session package in Ubuntu: Fix Released Bug description: An account with no name (only a username) will show a row in the Switch User Account menu with a face icon, but no name. To reproduce: 1. From a terminal, create a new account using adduser: adduser testing 2. Enter a password twice 3. Leave the optional values as the default by pressing enter (Full Name, Room Number, etc.) 4. Open the switch user account menu, and notice the blank entry ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.22.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,grid,compiztoolbox,place,mousepoll,move,imgpng,wall,vpswitch,regex,gnomecompat,session,unitymtgrabhandles,snap,animation,expo,fade,scale,workarounds,ezoom,unityshell] Date: Wed Oct 12 10:57:24 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-10-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/872908/+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 1350393] Re: Recent accountsservice update causes login window to hang
** Changed in: accountsservice (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1325353] Re: Lock/Switch stay in session menu even if disabled
** Changed in: indicator-session Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: indicator-session (Ubuntu Trusty) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- 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/1325353 Title: Lock/Switch stay in session menu even if disabled Status in Session Menu: In Progress Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: In Progress Bug description: [Impact] Session indicator no longer honours the lockdown settings that worked in 12.04 LTS. There are no alternative settings to perform the same behaviour. This functionality is required in large installations where users are not allowed to perfom these actions (e.g. corporate installations / labs / public terminals). [Test Case] 1. Create the file /usr/share/glib-2.0/schemas/lockdown.gschema.override: [org.gnome.desktop.lockdown] disable-lock-screen=true disable-user-switching=true 2. Reboot 3. Log into a session Expected result: Opening the session indicator should not show any options to lock the screen or switch the user. Observed result: "Lock/Switch Account" and user list shown for installations with more than one user. "Lock" shown for installations with one user. [Regression Potential] Potential for modified options to be shown/hidden incorrectly. Risk reduced by using existing regression tests, adding new test for lockdown and manually testing each case. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1325353/+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 1699216] Re: Encrypted home support
Hi Jememy. Nice work on the patches! I've been working with the AccountsService upstream and I'd like to work out how we can get these patches in. I think we can make this work with a couple of changes: - Instead of making the CreateUserEncrypt() method you could make a new account type ACCOUNT_TYPE_ENCRYPTED (src/user.h). Since upstream can't currently support this though 'useradd' it should then fail the call when this account type is encrypted. - We then can carry the change in Debian/Ubuntu by modifying debian/patches/0002-create-and-manage-groups-like-on-a-debian-system.patch (I'm working on merging in 0006-adduser_instead_of_useradd.patch which should be in the same patch). Please open a bug on bugzilla.freedesktop.org with the patch and I will help review there. I'm also working on how we can get our adduser changes upstream so we don't have to carry this patch either (https://bugs.freedesktop.org/show_bug.cgi?id=73838) I've pinged upstream but I think everyone is on break now (and I will be for the next two weeks too) but will pick this up when I'm back. ** Bug watch added: freedesktop.org Bugzilla #73838 https://bugs.freedesktop.org/show_bug.cgi?id=73838 -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1699216] Re: Encrypted home support
Oh, there was one last point: - You should add a "SupportsEncrypted" property (or similar name) to the AccountsService daemon. That way you can make the g-c-c patch DTRT and also make it more upstreamable. -- 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/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1640409] Re: show my login name in menu bar not working.
Unity Control Center is toggling the "show-real-name-on-panel" GSetting but indicator-session appears not to be using it. -- 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/1640409 Title: show my login name in menu bar not working. Status in indicator-session package in Ubuntu: Triaged Bug description: I check the checkbox "show my login name in menu bar" but my login name does not appear. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+16.10.20161003.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 9 08:43:12 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-11-06 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1640409/+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 1640409] Re: show my login name in menu bar not working.
Confirmed this works in Xenial. ** Package changed: unity-control-center (Ubuntu) => indicator-session (Ubuntu) -- 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/1640409 Title: show my login name in menu bar not working. Status in indicator-session package in Ubuntu: Triaged Bug description: I check the checkbox "show my login name in menu bar" but my login name does not appear. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+16.10.20161003.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 9 08:43:12 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-11-06 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1640409/+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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
This is affecting Ubuntu 16.10 now as XDG_CURRENT_DESKTOP is now set to "Unity:Unity7" (e.g. bug 1629668) -- 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 1600502] Re: extra set of icons are installed in wrong directory
** Changed in: indicator-session (Ubuntu) Status: New => Triaged -- 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/1600502 Title: extra set of icons are installed in wrong directory Status in indicator-session package in Ubuntu: Triaged Bug description: indicator-session icons are being installed to /usr/share/icons/hicolor/ and /usr/share/icons/hicolor/icons/ Excerpt from the build log: https://launchpad.net/ubuntu/+source/indicator-session/12.10.5+16.04.20160412-0ubuntu3/+build/10198014 -rw-r--r-- root/root 256 2016-07-01 08:44 ./usr/share/icons/hicolor/16x16/actions/system-log-out.png -rw-r--r-- root/root 732 2016-07-01 08:44 ./usr/share/icons/hicolor/16x16/actions/system-restart.png -rw-r--r-- root/root 540 2016-07-01 08:44 ./usr/share/icons/hicolor/16x16/actions/system-shutdown.png -rw-r--r-- root/root 256 2016-07-01 08:44 ./usr/share/icons/hicolor/icons/16x16/actions/system-log-out.png -rw-r--r-- root/root 732 2016-07-01 08:44 ./usr/share/icons/hicolor/icons/16x16/actions/system-restart.png -rw-r--r-- root/root 540 2016-07-01 08:44 ./usr/share/icons/hicolor/icons/16x16/actions/system-shutdown.png I am attaching a merge proposal to fix this. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-session 12.10.5+16.04.20160412-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jul 9 14:13:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-09 (90 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1600502/+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 1389336] Re: Use geoclue-2.0
I had a look at what is required for libunity-webapps and it just appears to be using geoclue to work out what country you are in to show the appropriate Amazon store. Since Geoclue 2.0 doesn't provide this (it just gives a co-ordinate) the easiest solution is to make libunity- webapps contact http://geoip.ubuntu.com/lookup directly to get the country. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: In Progress Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Fix Committed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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
Removing pyxdg as it doesn't make use of XDG_CURRENT_DESKTOP ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: unity-control-center (Ubuntu) Status: Triaged => Fix Committed ** No longer affects: pyxdg (Ubuntu) -- 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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Fix Committed -- 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 pyxdg package in Ubuntu: Confirmed 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 1389336] Re: Use geoclue-2.0
You can switch to using the Ubuntu service in geoclue by seting: [wifi] url=http://geoip.ubuntu.com/v1/geolocate in /etc/geoclue/geoclue.conf -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: In Progress Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1389336] Re: Use geoclue-2.0
I've proposed a change to geoip.ubuntu.com to provide a Google/Mozilla Location Service compatible API. This means we can configure Geoclue 2.0 to use this service. Then I propose we drop geoclue (1.0) and ubuntu-geoip from the archive. ** Changed in: webkit2gtk (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Triaged Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1389336] Re: Use geoclue-2.0
** Changed in: webkit2gtk (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Triaged Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 891083] Re: ubuntu wont log out/shut down
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released -- 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/891083 Title: ubuntu wont log out/shut down Status in Session Menu: Confirmed Status in indicator-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Fix Released Bug description: logout: $ /usr/lib/indicator-session/gtk-logout-helper --logout ** (gtk-logout-helper:31585): DEBUG: Dialog type: logout ** (gtk-logout-helper:31585): DEBUG: Showing dialog to ask for user confirmation ** (gtk-logout-helper:31585): DEBUG: Dialog return response: 'okay' ** (gtk-logout-helper:31585): DEBUG: Asking Session manager to 'Logout' ** (gtk-logout-helper:31585): WARNING **: SessionManager action failed: Logout has been locked down ** (gtk-logout-helper:31585): DEBUG: Falling back to using ConsoleKit for action ** (gtk-logout-helper:31585): WARNING **: Unable to fallback to ConsoleKit for logout as it's a session issue. We need some sort of session handler. ** (gtk-logout-helper:31585): DEBUG: Finished action, quiting shutdown: $ /usr/lib/indicator-session/gtk-logout-helper --shutdown ** (gtk-logout-helper:5226): DEBUG: Dialog type: shutdown ** (gtk-logout-helper:5226): DEBUG: Showing dialog to ask for user confirmation ** (gtk-logout-helper:5226): DEBUG: Dialog return response: 'okay' ** (gtk-logout-helper:5226): DEBUG: Asking Session manager to 'RequestShutdown' ** (gtk-logout-helper:5226): DEBUG: Finished action, quiting release:11.10 indicator-session 0.3.7.1-0ubuntu1.1 what i expected: to be able to log out/shut down from unity bar what happened instead:nothing ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: indicator-session 0.3.7.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Nov 16 18:34:08 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: indicator-session UpgradeStatus: Upgraded to oneiric on 2011-11-13 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/891083/+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 1059928] Re: Lightdm [Kubuntu) not displaying user thumbnail photos
Is this still applicable? ** No longer affects: lightdm ** Changed in: lightdm (Ubuntu) Status: Confirmed => Incomplete -- 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/1059928 Title: Lightdm [Kubuntu) not displaying user thumbnail photos Status in accountsservice package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Incomplete Bug description: On the Kubuntu login screen (I'm assuming lightdm?), there are just generic pictures for users. I expected it to display my photo along with my user name, as I configured in System Settings -> Account Details -> Change your image. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 1 21:53:35 2012 EcryptfsInUse: Yes InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1059928/+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 1325259] Re: Log out/Lock not functional with user with no password
** Package changed: lightdm (Ubuntu) => indicator-session (Ubuntu) -- 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/1325259 Title: Log out/Lock not functional with user with no password Status in indicator-session package in Ubuntu: New Bug description: when creating a user account with no password, the lock and logout functions dont work. you must click on another users name to log out or lock the account. i think that the lock should take you back to the user selection screen without disrupting the windows in your account. the log out should sign out and discard your windows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 31 16:00:45 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-30 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-05-30 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1325259/+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 878836] Re: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions
This is a problem that won't be solved in Ubuntu until we use Unity8 + Mir for displaying. Other systems are already using greeters as lockscreens, so the work has been done for this. Closing lightdm and unity-greeter tasks to reduce any confusion. -- 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/878836 Title: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions Status in Ayatana Design: Fix Committed Status in Session Menu: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Won't Fix Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Won't Fix Status in indicator-session source package in Precise: Fix Released Bug description: Use Unity Greeter to fulfil lock screen as well as login functions. Desired Solution: - Replace the current lock screen with the Unity Greeter - perhaps use 'light locker', see http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh [FFe] This is a FFe to implement in unity a lockscreen that looks like unity-greeter inside unity. The code for unity was ready before FF, but to improve PAM support we had to delay it See more at https://code.launchpad.net/~andyrock/unity/lockscreen/+merge/206291 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878836/+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 878836] Re: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions
** No longer affects: lightdm ** Changed in: unity-greeter (Ubuntu) Status: Triaged => Won't Fix ** Changed in: lightdm (Ubuntu) Status: Triaged => Won't Fix -- 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/878836 Title: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions Status in Ayatana Design: Fix Committed Status in Session Menu: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Won't Fix Status in unity package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Won't Fix Status in indicator-session source package in Precise: Fix Released Bug description: Use Unity Greeter to fulfil lock screen as well as login functions. Desired Solution: - Replace the current lock screen with the Unity Greeter - perhaps use 'light locker', see http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh [FFe] This is a FFe to implement in unity a lockscreen that looks like unity-greeter inside unity. The code for unity was ready before FF, but to improve PAM support we had to delay it See more at https://code.launchpad.net/~andyrock/unity/lockscreen/+merge/206291 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878836/+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 1553592] Re: 16.04 casper 15_autologin file contains obsolete lightdm configuration
While this configuration is old, it will continue to work. However, if this file is changed then accountsservice should also be updated to look in the new location. I did look at this a while ago and decided it was too much to fix (and I'm not confident enough in this area) when I changed the configuration file conventions. It should be updated however. It should be fixed at some point though. ** Package changed: lightdm (Ubuntu) => casper (Ubuntu) ** Changed in: casper (Ubuntu) Importance: Undecided => Low ** Changed in: casper (Ubuntu) Status: New => Triaged ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu) Status: New => Triaged ** Changed in: accountsservice (Ubuntu) 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/1553592 Title: 16.04 casper 15_autologin file contains obsolete lightdm configuration Status in accountsservice package in Ubuntu: Triaged Status in casper package in Ubuntu: Triaged Bug description: /usr/share/initramfs-tools/scripts/casper-bottom/15autologin the lightdm section of the file contains a lightdm configuration that is incorrect for 15.10 and later for example it writes out /root/etc/lightdm/lightdm.conf according to the lightdm wiki this should be /root/etc/lightdm/lightdm.conf.d/xyz.conf Additionally using [SeatDefaults] is wrong. Again according the wiki [SeatDefaults] is obsolete and should be [Seat:*] Think this is probably why manual live CD creators and those who use Pinguy ISO Builder cannot create a lightdm autologin live CD ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.17.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 5 21:07:13 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1553592/+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 1534485] Re: Stop using Ubuntu Software Centre reviews database
** Changed in: unity-lens-applications (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1534485 Title: Stop using Ubuntu Software Centre reviews database Status in unity-lens-applications package in Ubuntu: Triaged Bug description: We're looking at migrating from Ubuntu Software Centre to GNOME Software. This will break the reviews support in the Unity dash. We need another solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1534485/+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 1534485] [NEW] Stop using Ubuntu Software Centre reviews database
Public bug reported: We're looking at migrating from Ubuntu Software Centre to GNOME Software. This will break the reviews support in the Unity dash. We need another solution. ** Affects: unity-lens-applications (Ubuntu) Importance: Medium Status: Triaged ** Tags: gnome-software-ubuntu ** Changed in: unity-lens-applications (Ubuntu) Status: New => Triaged ** Changed in: unity-lens-applications (Ubuntu) Importance: Undecided => Medium ** Tags added: gnome-software-ubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1534485 Title: Stop using Ubuntu Software Centre reviews database Status in unity-lens-applications package in Ubuntu: Triaged Bug description: We're looking at migrating from Ubuntu Software Centre to GNOME Software. This will break the reviews support in the Unity dash. We need another solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1534485/+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 1508656] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: pocketsphinx (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of DX Packages, which is subscribed to pocketsphinx in Ubuntu. https://bugs.launchpad.net/bugs/1508656 Title: Build with multiarch support Status in pocketsphinx package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pocketsphinx/+bug/1508656/+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 1508658] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: sphinxbase (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of DX Packages, which is subscribed to sphinxbase in Ubuntu. https://bugs.launchpad.net/bugs/1508658 Title: Build with multiarch support Status in sphinxbase package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sphinxbase/+bug/1508658/+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 1508612] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libunity-webapps (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1508612 Title: Build with multiarch support Status in libunity-webapps package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1508612/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1473269] Re: Wily login screen shows an all black notification bubble
** Changed in: notify-osd (Ubuntu) Importance: Undecided => High ** Changed in: unity-greeter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1473269 Title: Wily login screen shows an all black notification bubble Status in notify-osd package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: Wily login screen shows an all black notification bubble. No idea what it says, obviously. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1473269/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1498775] Re: Greeter auth doesn't unlock unity lockscreen
Also - confirming after reboot the changes worked. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1498775 Title: Greeter auth doesn't unlock unity lockscreen Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Using current wily - use indicator-session to go to the greeter (e.g pick another user in the list) - select your normal user back - enter your password you should go back to an unlocked session but it's still locked... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1498775/+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 1498775] Re: Greeter auth doesn't unlock unity lockscreen
I've uploaded a version to wily with libaudit support disabled. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1498775 Title: Greeter auth doesn't unlock unity lockscreen Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Using current wily - use indicator-session to go to the greeter (e.g pick another user in the list) - select your normal user back - enter your password you should go back to an unlocked session but it's still locked... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1498775/+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 1498775] Re: Greeter auth doesn't unlock unity lockscreen
I've managed to reproduce on a VM, however commenting out the PAM changes seems to have no effect - it still shows the Unity lockscreen when returning from the greeter. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1498775 Title: Greeter auth doesn't unlock unity lockscreen Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Using current wily - use indicator-session to go to the greeter (e.g pick another user in the list) - select your normal user back - enter your password you should go back to an unlocked session but it's still locked... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1498775/+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 1498775] Re: Greeter auth doesn't unlock unity lockscreen
tyhicks / others - does the libaudit functionality work if we revert the PAM configuration? i.e. is it a way forward to revert this PAM change until we work out what the problem is? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1498775 Title: Greeter auth doesn't unlock unity lockscreen Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Using current wily - use indicator-session to go to the greeter (e.g pick another user in the list) - select your normal user back - enter your password you should go back to an unlocked session but it's still locked... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1498775/+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 1497928] Re: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service:11:bluez_update_device:___lambda5_:____lambda5__object_manager_interfaces_added:g_closure_invo
The stack traces are suggesting the crash is due to there not being a cached property "UUIDs" for the device. We check for NULL in the other properties, not for this one. This is probably bad that this property doesn't exist but we still shouldn't crash. -- 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/1497928 Title: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth- service:11:bluez_update_device:___lambda5_:lambda5__object_manager_interfaces_added:g_closure_invoke:signal_emit_unlocked_R Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-bluetooth. This problem was most recently seen with version 0.0.6+15.10.20150915-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5819c2721723a35013649535ed691c84f7eb06d7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1497928/+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 1498775] Re: Greeter auth doesn't unlock unity lockscreen
I'm having trouble reproducing this as my graphics drivers just show a black screen when X quits. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1498775 Title: Greeter auth doesn't unlock unity lockscreen Status in Unity: New Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: New Bug description: Using current wily - use indicator-session to go to the greeter (e.g pick another user in the list) - select your normal user back - enter your password you should go back to an unlocked session but it's still locked... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1498775/+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 1483205] Re: unity-control-center needs bluetooth packages
This is because unity-control-center needs the GSettings schema from indicator-bluetooth and schemas need to be installed otherwise the control center would crash. Otherwise indicator-bluetooth would just be a recommends. A solution would be to make an indicator-bluetooth-schemas package that just contained the schema. ** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1483205 Title: unity-control-center needs bluetooth packages Status in indicator-bluetooth package in Ubuntu: New Status in unity-control-center package in Ubuntu: New Bug description: Hi, unity-control-center seems to require indicator-bluetooth which then pulls in a bunch of bluetooth packages. Any chance of updating it so bluetooth is optional? I don't have bluetooth enabled, and would prefer not to have bluetooth packages installed (indicator-bluetooth, bluez, indicator-bluetooth, gir1.2-gnomebluetooth-1.0, libbluetooth3, etc.) Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1483205/+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 1475623] Re: zeitgeist ftbfs with GCC 5
Patch filed upstream and upload to the GCC 5.1 PPA. ** Changed in: zeitgeist (Ubuntu) Status: In Progress => Fix Committed -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in Zeitgeist Framework: Unknown Status in zeitgeist package in Ubuntu: Fix Committed Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5
** Bug watch added: freedesktop.org Bugzilla #91443 https://bugs.freedesktop.org/show_bug.cgi?id=91443 ** Also affects: zeitgeist via https://bugs.freedesktop.org/show_bug.cgi?id=91443 Importance: Unknown Status: Unknown -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in Zeitgeist Framework: Unknown Status in zeitgeist package in Ubuntu: In Progress Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5
Note this only happens in the tests with strings > 15 characters in length. I suspect that must be the boundary where std::string starts mallocing the contents. -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in zeitgeist package in Ubuntu: In Progress Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5
I think the issue is the std::string object is going out of scope in the tests. The tests are like this: g_assert_cmpstr (std::string ("scheme_no_spaces_in_uris"), ==, StringUtils::MangleUri("scheme:no spaces in uris").c_str ()); Inside the g_assert_cmpstr macro the two strings are stored in variables. Nothing is left holding the result of MangleUri () so the result from c_str () is no longer valid. I guess GCC 5.1 is more agressive in destroying the std:string than it used to be? -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in zeitgeist package in Ubuntu: In Progress Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5
https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-016/+build/7656245 is a build failing with test. -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in zeitgeist package in Ubuntu: Confirmed Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5
The first build log is implying that Mir is not built / linekd correctly: /usr/lib/x86_64-linux-gnu/libmirprotobuf.so.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteStringMaybeAliased(int, std::string const&, google::protobuf::io::CodedOutputStream*)' -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in zeitgeist package in Ubuntu: Confirmed Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/+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 1475623] Re: zeitgeist ftbfs with GCC 5
The linked build in comment 1 is for telephony-service, not zeitgeist. -- 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/1475623 Title: zeitgeist ftbfs with GCC 5 Status in zeitgeist package in Ubuntu: Confirmed Bug description: see https://launchpadlibrarian.net/211752996/buildlog_ubuntu-wily-amd64.zeitgeist_0.9.14-2.2ubuntu6~gcc5.1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1475623/+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 1466289] Re: Update to 0.6.40
** Changed in: accountsservice (Ubuntu) Status: New => In Progress ** Changed in: accountsservice (Ubuntu) Importance: Undecided => Medium ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1466289 Title: Update to 0.6.40 Status in accountsservice package in Ubuntu: In Progress Bug description: Update to 0.6.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1466289/+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 1466289] [NEW] Update to 0.6.40
Public bug reported: Update to 0.6.40 ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- 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/1466289 Title: Update to 0.6.40 Status in accountsservice package in Ubuntu: New Bug description: Update to 0.6.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1466289/+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 1466289] Re: Update to 0.6.40
Required for gnome-control-center 3.16 (bug 1466245) -- 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/1466289 Title: Update to 0.6.40 Status in accountsservice package in Ubuntu: New Bug description: Update to 0.6.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1466289/+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 1460271] Re: Update evolution-data-server to 3.16
Required for gnome-contacts 3.16 (bug 1463657) -- 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/1460271 Title: Update evolution-data-server to 3.16 Status in evolution-data-server package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu: Triaged Bug description: Update to 3.16. Debian currently has this in experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+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 1199221]
I'm going to close this since Zeitgeist provides GIR bindings which can be accessed from Python 3. -- 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/1199221 Title: Package zeitgeist-python for python3 aka make package python3-zeitgeist Status in Zeitgeist Framework: Fix Released Status in zeitgeist package in Ubuntu: Confirmed Bug description: At the moment the package python-zeitgeist installs in python2.7 location and does not have a python3.x installation which makes python3 migration tougher. Expectation: Have a second package python3-zeitgeist which installs in python3.x location To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1199221/+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 1440373]
I'm going to close this since Zeitgeist provides GIR bindings which can be accessed from Python 3. -- 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/1440373 Title: please build a python3-zeitgeist package and let zeitgeist depend on it Status in Zeitgeist Framework: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in zeitgeist package in Ubuntu: Fix Released Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please build a python3-zeitgeist package and let zeitgeist depend on it To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1440373/+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 1440373] Re: please build a python3-zeitgeist package and let zeitgeist depend on it
We also need to add zeitgeist-datahub to the seed so this is not removed from the images. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Medium -- 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/1440373 Title: please build a python3-zeitgeist package and let zeitgeist depend on it Status in Zeitgeist Framework: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Status in zeitgeist package in Ubuntu: Triaged Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please build a python3-zeitgeist package and let zeitgeist depend on it To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1440373/+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 1440373] Re: please build a python3-zeitgeist package and let zeitgeist depend on it
This turns out to be quite simple. libzeitgeist-2.0-0 has Recommends: zeitgeist | zeitgeist-core. If we switch these around we should avoid pulling in the metapackage that pulls in python-zeitgeist (which nothing uses). We already have Python 3 support by using the GIR package. -- 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/1440373 Title: please build a python3-zeitgeist package and let zeitgeist depend on it Status in Zeitgeist Framework: Confirmed Status in ubuntu-meta package in Ubuntu: Triaged Status in zeitgeist package in Ubuntu: Triaged Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please build a python3-zeitgeist package and let zeitgeist depend on it To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1440373/+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 1440373] Re: please build a python3-zeitgeist package and let zeitgeist depend on it
** Changed in: zeitgeist (Ubuntu) Status: New => Triaged ** Changed in: zeitgeist (Ubuntu) Importance: Undecided => Medium -- 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/1440373 Title: please build a python3-zeitgeist package and let zeitgeist depend on it Status in Zeitgeist Framework: Confirmed Status in zeitgeist package in Ubuntu: Triaged Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please build a python3-zeitgeist package and let zeitgeist depend on it To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/1440373/+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 1460271] Re: Update to 3.16
This requires indicator-datetime to be updated: https://code.launchpad.net/~robert-ancell/indicator-datetime/libecal-3.16/+merge/260789 ** Summary changed: - Update to 3.16 + Update evolution-data-server to 3.16 ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~robert-ancell/indicator-datetime/libecal-3.16 ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-datetime (Ubuntu) Status: New => Triaged -- 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/1460271 Title: Update evolution-data-server to 3.16 Status in evolution-data-server package in Ubuntu: Triaged Status in indicator-datetime package in Ubuntu: Triaged Bug description: Update to 3.16. Debian currently has this in experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1460271/+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 1405349] Re: switching to activated guest session causes screen blank
More investigation shows that this is actually a Unity bug. The black screen you are seeing is the lock screen but Unity doesn't have a lock screen when in guest mode. The lock screen is triggered when you switch users via the indicator. You can also trigger this by typing alt+ctrl+L inside the guest session. It will show a black screen that disappears when you move the mouse. The solution should be that Unity does nothing when the lock screen is requested to be activated. ** No longer affects: lightdm ** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1405349 Title: switching to activated guest session causes screen blank Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in unity package in Ubuntu: Confirmed Status in unity source package in Trusty: New Bug description: Hi, I switch to activated guest session, but the screen remains blank. I have to wake it up with keyboard/mouse action. How to reproduce: 1. login with your account normally. 2. switch to guest session from the panel menu "Switch Account... -> Guest Session", now it's under guest session and the display is normal. 3. switch back to your user account, then switch to guest session again. 4. The screen remains blank. I can't reproduce this issue under Precise. Vivid snapshot 22-Mar-2015 can also reproduce this issue. Package: lightdm 1.10.3-0ubuntu2 unity-settings-daemon-14.04.0+14.10.20140606~0ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150205-07:08 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin Package: lightdm 1.10.3-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Tags: trusty third-party-packages Uname: Linux 3.13.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1405349/+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 1260884] Re: Please update glew to 1.10.0
** No longer affects: unity (Ubuntu) ** No longer affects: nux (Ubuntu) ** No longer affects: unity -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1260884 Title: Please update glew to 1.10.0 Status in glew package in Ubuntu: Fix Released Bug description: The current version of glew in ubuntu is outdated and blocking other updates. Can someone please update to 1.10, which might break other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1260884/+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 1393843] Re: Log in prompt appears twice or three times after suspend
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) ** No longer affects: unity-greeter -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1393843 Title: Log in prompt appears twice or three times after suspend Status in unity package in Ubuntu: New Bug description: Hi, since my update to 14.04.1 LTS I experience difficulties with unlocking my screen after waking up my maschine. After logging the desktio is shown only for a short moment, following another screen lock. I have to unlock the screen again then. This happens after every suspend, sometimes even three times. I am happy to provide additional data. cheers ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Tue Nov 18 17:03:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-13 (673 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter allow-guest=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393843/+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 1396700] Re: Needs to be updated to bluez5
** Changed in: indicator-bluetooth (Ubuntu) Assignee: Robert Ancell (robert-ancell) => Lars Uebernickel (larsu) -- 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/1396700 Title: Needs to be updated to bluez5 Status in indicator-bluetooth package in Ubuntu: In Progress Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.
** No longer affects: lightdm (Ubuntu) ** No longer affects: lightdm -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413790 Title: It's possible to bypasss lockscreen if user is in nopasswdlogin group. Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Lightdm should not emit logind "unlock" signal when the user is not prompted for a password. This can lead to a security issue: # Log-in (unity session). # Add the current user to nopasswdlogin group. # Lock the sessions. # Session indicator->Switch account... # "Login" in again. Expected behavior: The lockscreen is still active. Current behavior: The session in unlocked. We could workaround the issue directly in unity, but IMHO would be cleaner to avoid that lightdm is emitting the logind signal. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413790/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
You suggest that version 1.1.1 has this fixed so I had a look through the log to see what has changed. I *think* this may be the fix you need: https://github.com/FreeRDP/Remmina/commit/348e01d27869a577ad5df9bf6286f876b34a40c0 ** No longer affects: unity (Ubuntu) ** No longer affects: unity ** Changed in: remmina (Ubuntu) Status: Confirmed => Triaged ** Also affects: remmina (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: remmina (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: remmina (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: remmina (Ubuntu Precise) Status: New => Triaged ** Changed in: remmina (Ubuntu Trusty) Status: New => Triaged ** Changed in: remmina (Ubuntu Utopic) Status: New => Triaged ** Changed in: remmina (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: remmina (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: remmina (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: remmina (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in remmina package in Ubuntu: Fix Released Status in remmina source package in Precise: Triaged Status in remmina source package in Trusty: Triaged Status in remmina source package in Utopic: Triaged Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 To reproduce this bug, you will have to Enable Workspaces In Ubuntu Unity, like this: System Settings > Appearance > Behavior > Enable Workspaces Essentially, when using the Unity desktop (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. Also, I do use multiple monitors, but this too might be unrelated to the bug. I think the essential thing, is that I have Workspaces enabled. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1370014/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
As I understand it the sourceforge.net project is obsolete and Remmina is now developed on https://github.com/FreeRDP/Remmina. That will probably be why there is no response to your bug report. I think the current developers don't have access to the old project to remove it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in remmina package in Ubuntu: Fix Released Status in remmina source package in Precise: Triaged Status in remmina source package in Trusty: Triaged Status in remmina source package in Utopic: Triaged Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 To reproduce this bug, you will have to Enable Workspaces In Ubuntu Unity, like this: System Settings > Appearance > Behavior > Enable Workspaces Essentially, when using the Unity desktop (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. Also, I do use multiple monitors, but this too might be unrelated to the bug. I think the essential thing, is that I have Workspaces enabled. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1370014/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
Lonnie - we don't update to newer versions of packages in stable releases, see https://wiki.ubuntu.com/StableReleaseUpdates ** Tags removed: upgrade-software-version -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in Unity: New Status in remmina package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 To reproduce this bug, you will have to Enable Workspaces In Ubuntu Unity, like this: System Settings > Appearance > Behavior > Enable Workspaces Essentially, when using the Unity desktop (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. Also, I do use multiple monitors, but this too might be unrelated to the bug. I think the essential thing, is that I have Workspaces enabled. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1370014/+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 1409530] Re: password dialog missing after suspend
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1409530 Title: password dialog missing after suspend Status in unity package in Ubuntu: New Bug description: Intermittently after returning from suspend, the password text box will be missing, making it impossible to unlock the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 11 13:59:03 2015 InstallationDate: Installed on 2014-11-30 (42 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1409530/+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 1396700] Re: Needs to be updated to bluez5
** Changed in: indicator-bluetooth (Ubuntu) Status: Triaged => In Progress -- 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/1396700 Title: Needs to be updated to bluez5 Status in indicator-bluetooth package in Ubuntu: In Progress Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1396700] Re: Needs to be updated to bluez5
** Changed in: indicator-bluetooth (Ubuntu) Status: New => Triaged -- 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/1396700 Title: Needs to be updated to bluez5 Status in “indicator-bluetooth” package in Ubuntu: Triaged Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1396700] Re: Needs to be updated to bluez5
** Changed in: indicator-bluetooth (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1396700 Title: Needs to be updated to bluez5 Status in “indicator-bluetooth” package in Ubuntu: New Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1393852] Re: No password prompt is given after locking the screen
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1393852 Title: No password prompt is given after locking the screen Status in “unity” package in Ubuntu: New Bug description: Hi, occasionally when I lock my screen there is not prompt for entering the password presented. Therefore, I cannot unlock the screen anymore. The only thing displayed is my Username in a frame, but not the username itself. There are two ways to workaround the bug. Either rebooting the maschine or suspending it(for which I used another bug in the pwer management that enables me to suspend the maschine anyway). In the latter case a new login screen is displayed, very often with a textfield to enter the password Please notice that this is only one bug in a series of issues with logging in in lightdm. I expect the issues to be interrelated and therefore sugest to have a look on the other reports as well, which a avaliable through my profile. I will provide direkt links later. cheers ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Tue Nov 18 17:18:29 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-13 (673 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter allow-guest=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393852/+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 1374466] Re: Screen lock has no place to type in a password
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374466 Title: Screen lock has no place to type in a password Status in “unity” package in Ubuntu: New Bug description: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. Just as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1358745 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 26 09:59:59 2014 InstallationDate: Installed on 2014-09-23 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1374466/+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 1340312] Re: Preferred monitor rotation forgotten on reboot
** Project changed: unity-control-center => unity-control-center (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1340312 Title: Preferred monitor rotation forgotten on reboot Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Status in “unity-control-center” package in Ubuntu: New Bug description: I prefer to turn my secondary monitor to a portrait orientation for reading long log file lists. Ubuntu lets me configure the rotation this way, but when I reboot, the setting is forgotten. Lenovo Group Limited 19" / fglrx AMD video driver / Ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1340312/+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 1298620] Re: unity: enable natural scrolling by default
** Project changed: unity-control-center => unity-control-center (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1298620 Title: unity: enable natural scrolling by default Status in “unity” package in Ubuntu: Invalid Status in “unity-control-center” package in Ubuntu: New Bug description: Testing trusty desktop on a laptop, natural scrolling is off by default. In this day and age, this makes no sense; ios and Android have conditioned users to understand that when they want to scroll a document, they touch it and drag it in the direction they want it to go. The option can be changed by the user, but it's important to have the default that gives the best initial impression to the user. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Mar 27 20:58:38 2014 InstallationDate: Installed on 2014-03-27 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298620/+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 1311344] Re: [sticky keys] shift key is stuck down after suspending/resuming
** No longer affects: unity-control-center -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311344 Title: [sticky keys] shift key is stuck down after suspending/resuming Status in “unity” package in Ubuntu: Invalid Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: With stick keys enabled, the shift key is stuck down after suspending/resuming. To reproduce: 1) Enables stick keys 2) Suspend the screen closing the lid 3) Open the lid This breaks both unity lockscreen and lightdm [Workaround] Press shift key before entering the passowrd. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:27:14 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-02 (475 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311344/+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 1320286] Re: On LTSP thick client gnome-settings-daemon gets loaded before unity-settings-daemon
** No longer affects: unity-settings-daemon -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1320286 Title: On LTSP thick client gnome-settings-daemon gets loaded before unity- settings-daemon Status in Gnome Settings Daemon: New Status in Unity: Incomplete Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Incomplete Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: On amd64 ltsp fat client, gnome-settings-daemon gets loaded before unity-settings-daemon, and thus unity-panel-service doesn't start at all. manually running /usr/lib/unity/unity-panel-service after logging into the unity desktop is a work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1320286/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Changed in: unity-settings-daemon (Ubuntu) Status: New => In Progress ** Changed in: unity-settings-daemon (Ubuntu) Assignee: (unassigned) => Jackson Doak (noskcaj) ** No longer affects: unity-settings-daemon -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in “gnome-desktop3” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “unity-control-center” package in Ubuntu: In Progress Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys
** Project changed: unity-settings-daemon => unity-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1280759 Title: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: There are shortcuts to open lenses in Unity, for example "Super + A" for App Lens, or "Super + F" for Files Lens, etc. There are also shortcuts in the Launcher "Super + 1 to 9" to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator --> Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press "Super + F". WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press "Ctrl + S" (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press "Ctrl + S" while Persian layout is active, I am typing "Ctrl + س". But keyboard-wise, I am always pressing the same keyboard binding. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1280759/+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 1370069] Re: Login does not work
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1370069 Title: Login does not work Status in “unity” package in Ubuntu: New Bug description: After screen lock the login does not display a field where a password can be typed and thus there seems to be no way to login to machine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Sep 16 16:53:05 2014 DistUpgraded: 2014-04-11 11:51:55,755 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Subsystem: Hewlett-Packard Company Device [103c:18e4] Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1002:6771] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:90b8] InstallationDate: Installed on 2013-11-05 (315 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=ef4f067e-192b-4f3f-873d-bfb295641eec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to trusty on 2014-04-11 (158 days ago) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.18 dmi.board.asset.tag: CZC3427KBP dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3427KBP dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP EliteDesk 800 G1 TWR dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 4 10:17:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370069/+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 1366642] Re: Resume laptop sometimes shows no lock screen, sometimes lock screen with no text input.
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1366642 Title: Resume laptop sometimes shows no lock screen, sometimes lock screen with no text input. Status in “unity” package in Ubuntu: New Bug description: Resuming on 14.04 sometimes fails to show the lock screen, rarely it may show the lock screen but have no input to type the password. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Sep 6 22:05:56 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (287 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1366642/+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 1365039] Re: Could not get session id for session
Please attach /var/log/lightdm/lightdm.log after a failed boot. ** Changed in: lightdm Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1365039 Title: Could not get session id for session Status in Light Display Manager: Incomplete Status in “systemd-shim” package in Ubuntu: New Bug description: A few hours back we got two packages upgraded: systemd-shim (7.2) and lightdm (1.11.8-0ubuntu1). On that pc, i've closed the session then shutdown: everything was stable, and its a fresh standard installation using upstart for booting. Here are the troubles met at the next cold boot (verbosy mode): - the boot process goes well until "Add swap on /dev/sdb2" as expected, but then nothing, only hdd activity continuing hardly scanning, and no errors/warnings printed. Had to force a hardware's reset, can't call tty1-6 (system not responsive ??) - second cold boot: the system load fsck on the /home partition, then the process continue to boot, made a pause at load the swap partition again, the hdd was activity working a few (long) seconds, so i've tried to switch to tty1 and successed. I've reconfigured lightdm and tried startx : it seemed to continue its processes even if the hdd was again hardly scanning unsually. But i only got a black screen: no mouse pointer, no tty. So reboot again. - third try: same issue, but was able to open tty when it did a pause at swap partition loading: so i reconfigured lightdm and choose gdm as default that time. Startx was ran and after some hard hdd scanning, it finally loaded a degraded login screen: no mouse but the keyboard was working. After login validation, gnome-shell appeared as expected, but again no mouse; a ctrl+alt+T opened a terminal, where i'm right now, to report that issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-2 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Sep 3 17:15:43 2014 SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1365039/+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 1358745] Re: Screen lock has no place to type in a password
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1358745 Title: Screen lock has no place to type in a password Status in “unity” package in Ubuntu: New Bug description: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1358745/+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 1351610] Re: LightDM looses focus
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1351610 Title: LightDM looses focus Status in “unity” package in Ubuntu: New Bug description: Sometimes after I wake up from suspend, LightDM seems to lost focus to a window in the desktop. I have a blinking cursor in the LightDM screen, and if I start typing anything the cursor doesn't move, and the only way to bypass this is wait the screen to turn off and on again (here I can type the password). This also happens when locking the screen. Description: Ubuntu 14.04.1 LTS Release: 14.04 Lightdm version: 1.10.1-0ubuntu1 How to reproduce: * Open a window and click on a text box (ex: login form in some web page in a browser). * Lock the screen * Try to type your password to unlock it: the cursor blinks but doesn't move at all; * Wait for the screen to turn off, do something to wake up the screen and login; * Whatever you typed will be on the text input of the window you had focus (in this example: the login form of the web page) What was supposed to happen: * After locking the screen or waking from suspend, I expected that typing my password would unlock the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351610/+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 1311403] Re: Can't type password after resume.
** No longer affects: lightdm (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+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 1325353] Re: Lock/Switch stay in session menu even if disabled
** Changed in: indicator-session (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: indicator-session (Ubuntu Trusty) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1325353 Title: Lock/Switch stay in session menu even if disabled Status in The Session Menu: In Progress Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: [Impact] Session indicator no longer honours the lockdown settings that worked in 12.04 LTS. There are no alternative settings to perform the same behaviour. This functionality is required in large installations where users are not allowed to perfom these actions (e.g. corporate installations / labs / public terminals). [Test Case] 1. Create the file /usr/share/glib-2.0/schemas/lockdown.gschema.override: [org.gnome.desktop.lockdown] disable-lock-screen=true disable-user-switching=true 2. Reboot 3. Log into a session Expected result: Opening the session indicator should not show any options to lock the screen or switch the user. Observed result: "Lock/Switch Account" and user list shown for installations with more than one user. "Lock" shown for installations with one user. [Regression Potential] Potential for modified options to be shown/hidden incorrectly. Risk reduced by using existing regression tests, adding new test for lockdown and manually testing each case. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1325353/+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 1325353] Re: Lock/Switch stay in session menu even if disabled
** Description changed: + [Impact] + Session indicator no longer honours the lockdown settings for screen locking and user switching that worked in 12.04 LTS. There is no alternative settings to perform the same behaviour. This functionality is required in large installations where users are not allowed to perfom these actions (e.g. corporate installations / labs / public terminals). - In a university computer lab session we disable shutdown, restart, suspend, hibernate, switch user, and lock screen. - Some are done with polkit (suspend, hibernate) and then the suspend menuitem is not shown on the session menu. - Some are done with dconf e.g. + [Test Case] - # Show real name (and wider session menu as a result); lab also disable shutdown - [com.canonical.indicator.session] - show-real-name-on-panel=true - suppress-logout-restart-shutdown=true - suppress-restart-menuitem=true - suppress-shutdown-menuitem=true - user-show-menu=false - - # Quiet login screens - [com.canonical.unity-greeter] - play-ready-sound=false - - # Update-notifier - [com.ubuntu.update-notifier] - no-show-notifications=true - - # Software installation not possible for normal users - [desktop.gnome.unity.lenses.applications] - display-available-apps=false - - # Disable the lock screen & print-setup not on laptops, but in labs + 1. Create the file /usr/share/glib-2.0/schemas/lockdown.gschema.override: [org.gnome.desktop.lockdown] disable-lock-screen=true - disable-print-setup=true disable-user-switching=true + 2. Reboot + 3. Log into a session - # Screensaver lockdown in labs - [org.gnome.desktop.screensaver] - lock-enabled=false - user-switch-enabled=false + Expected result: + Opening the session indicator should not show any options to lock the screen or switch the user. - # Logout prompt - [org.gnome.SessionManager] - logout-prompt=false + Observed result: + "Lock/Switch Account" and user list shown (for installations with more than one user). "Lock" shown for installations with one user. - This works fine except there is no value for suppress-lock-menuitem or - suppress-switch-menuitem or suppress-lock-switch-menuitem, and the - Lock/Switch User menuitem still appears; even though it is non- - functional. Clicking on it blacks out the screen for a second and then - shows the desktop again. + [Regression Potential] + Potential for modified options to be shown/hidden incorrectly. Risk reduced by using existing regression tests, adding new test for lockdown and manually testing each case. ** Description changed: [Impact] - Session indicator no longer honours the lockdown settings for screen locking and user switching that worked in 12.04 LTS. There is no alternative settings to perform the same behaviour. This functionality is required in large installations where users are not allowed to perfom these actions (e.g. corporate installations / labs / public terminals). + Session indicator no longer honours the lockdown settings that worked in 12.04 LTS. There are no alternative settings to perform the same behaviour. This functionality is required in large installations where users are not allowed to perfom these actions (e.g. corporate installations / labs / public terminals). [Test Case] 1. Create the file /usr/share/glib-2.0/schemas/lockdown.gschema.override: [org.gnome.desktop.lockdown] disable-lock-screen=true disable-user-switching=true 2. Reboot 3. Log into a session Expected result: Opening the session indicator should not show any options to lock the screen or switch the user. Observed result: "Lock/Switch Account" and user list shown (for installations with more than one user). "Lock" shown for installations with one user. [Regression Potential] Potential for modified options to be shown/hidden incorrectly. Risk reduced by using existing regression tests, adding new test for lockdown and manually testing each case. ** Description changed: [Impact] Session indicator no longer honours the lockdown settings that worked in 12.04 LTS. There are no alternative settings to perform the same behaviour. This functionality is required in large installations where users are not allowed to perfom these actions (e.g. corporate installations / labs / public terminals). [Test Case] 1. Create the file /usr/share/glib-2.0/schemas/lockdown.gschema.override: [org.gnome.desktop.lockdown] disable-lock-screen=true disable-user-switching=true 2. Reboot 3. Log into a session Expected result: Opening the session indicator should not show any options to lock the screen or switch the user. Observed result: - "Lock/Switch Account" and user list shown (for installations with more than one user). "Lock" shown for installations with one user. + "Lock/Switch Account" and user list shown for installations with more than one user. "Lock" shown for installations with one user. [Regression Potential] Potential for modified o
[Dx-packages] [Bug 1345505] Re: lightdm leaks keystrokes to window "behind" greeter
It's actually unity showing a lock screen here, reassigning. ** Package changed: lightdm (Ubuntu) => unity (Ubuntu) ** Summary changed: - lightdm leaks keystrokes to window "behind" greeter + lock scren leaks keystrokes to window "behind" greeter -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1345505 Title: lock scren leaks keystrokes to window "behind" greeter Status in “unity” package in Ubuntu: New Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/+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