[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate
More complex changes: https://github.com/hughsie/PackageKit/pull/252 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Bionic: Triaged Bug description: Test Case: 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Actual result It hangs and generate this crashes when the user closes the debconf window. The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722185] Re: gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate
** Changed in: packagekit (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Summary changed: - gnome-software (11) g_io_channel_shutdown → pk_client_helper_copy_stdout_cb → g_main_dispatch → g_main_context_dispatch → g_main_context_iterate + Crash installing packages using debconf ** Description changed: - Test Case: + [Impact] + Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. + + [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt - Actual result - It hangs and generate this crashes when the user closes the debconf window. + Expected result: + A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. - The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. - If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + Actual result: + The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. + + Crash reports: + https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad ** Changed in: packagekit (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf
** Description changed: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. + [Regression Potential] + The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. + Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. [Regression Potential] The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
** Changed in: packagekit (Ubuntu)
Status: Confirmed => Triaged
** Changed in: packagekit (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: packagekit (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Also affects: packagekit (Ubuntu Cosmic)
Importance: Medium
Assignee: Robert Ancell (robert-ancell)
Status: Triaged
** Also affects: gnome-software (Ubuntu Cosmic)
Importance: Medium
Assignee: Robert Ancell (robert-ancell)
Status: Triaged
** Also affects: packagekit (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-software (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gnome-software (Ubuntu Bionic)
Status: New => Triaged
** Changed in: packagekit (Ubuntu Bionic)
Status: New => Triaged
** Changed in: packagekit (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: gnome-software (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: gnome-software (Ubuntu Bionic)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: packagekit (Ubuntu Bionic)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1552792
Title:
gnome software leaves dependencies installed
Status in GNOME Software:
Invalid
Status in Release Notes for Ubuntu:
Fix Released
Status in gnome-software package in Ubuntu:
Triaged
Status in packagekit package in Ubuntu:
Triaged
Status in gnome-software source package in Bionic:
Triaged
Status in packagekit source package in Bionic:
Triaged
Status in gnome-software source package in Cosmic:
Triaged
Status in packagekit source package in Cosmic:
Triaged
Bug description:
Using gnome software (or another PackageKit or aptdaemon based UI) to
install an application - removal of that package leaves behind
dependencies
Installing an application with ubuntu software centre only leaves
behind config files (seen in synaptic labelled for complete removal).
After installing and then removing alarm clock with USC -
sudo apt-get autoremove
[sudo] password for wolf:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
After cleaning up and then reinstalling with gnome software, followed
by the removal
sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED
libappindicator1 libindicator7
0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
After this operation, 184 kB disk space will be freed.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar 3 16:23:45 2016
InstallationDate: Installed on 2015-10-29 (126 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
It looks like the PackageKit change will be accepted upstream - this stops the autoremove functionality to only remove dependencies of packages being removed. This matches the old aptd behaviour. GNOME Software will have to be distro patched however, as upstream considers this functionality not reliable - since we have limited backends on Ubuntu we can enable it however. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: Triaged Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in packagekit source package in Cosmic: Triaged Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
Sure, sounds like a good idea. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: Triaged Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in packagekit source package in Cosmic: Triaged Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: Triaged Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in packagekit source package in Cosmic: Triaged Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757747] Re: Please port your package away from Qt 4
** Changed in: lightdm (Ubuntu) Status: New => Triaged ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1757747 Title: Please port your package away from Qt 4 Status in lightdm package in Ubuntu: Triaged Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758956] Re: Upstream translation not imported/synced
I've uploaded simple-scan 3.28.0-0ubuntu1 which has only translation changes from the current release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1758956 Title: Upstream translation not imported/synced Status in Ubuntu Translations: In Progress Status in evolution-data-server package in Ubuntu: New Status in simple-scan package in Ubuntu: New Bug description: There has been a similar report recently, but I'm not sure if it was the exact same one. If I look at the POT template for simple-scan it looks like it is up to date with the upstream one: same strings count, same strings. The PO file though doesn't seem to have been imported, at least for the Italian language. The last changed date in Launchpad is set to 2016-03-15, but the upstream translation for the 3.28 cycle has been completed (and it was complete also for the 3.26 cycle). A few links to check things out: * The Launchpad Italian translation: https://translations.launchpad.net/ubuntu/bionic/+source/simple-scan/+pots/simple-scan/it/+translate * The upstream Italian translation: https://l10n.gnome.org/vertimus/simple-scan/master/po/it Upstream hasn't branched 3.28 yet, so I wonder if this is just a matter of waiting for a new release to be imported in Launchpad. On a side note: simple-scan doesn't seem to be the only package with this "problem" (template in sync with upstream, but not the actual translations). I could see at least evolution-data-server, and gnome- online-accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1758956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735415] Re: VNC client does not exits after logout
Was fixed in lightdm 1.25.1
** Changed in: lightdm
Status: Fix Committed => Fix Released
** Changed in: lightdm (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: lightdm (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1735415
Title:
VNC client does not exits after logout
Status in Light Display Manager:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Trusty:
New
Status in lightdm source package in Xenial:
New
Status in lightdm source package in Zesty:
New
Status in lightdm source package in Artful:
New
Status in lightdm source package in Bionic:
Fix Released
Bug description:
I have setup the remote desktop using the "[VNCServer]" configuration section.
When I log in using a VNC client and log out with the desktop panel menu,
the VNC client(remmina) does not exits.
I found that a VNC connection(TCP 5900) remains alive even though the Xvnc
server exits.
I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".
static gboolean
read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
{
...
client_socket = g_socket_accept (socket, NULL, &error);
...
if (client_socket)
{
...
g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
}
return TRUE;
}
I think that "g_object_unref(client_socket)" should be called after
g_signal_emit().
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1735415/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf
Merged upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. [Regression Potential] The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774617] Re: Filter out snaps from GNOME Software
I've reassigned it to software-properties - that is where those settings live. ** Package changed: gnome-software (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1774617 Title: Filter out snaps from GNOME Software Status in software-properties package in Ubuntu: Triaged Bug description: An option should be provided in Software & Updates to filter out snaps from GNOME Software. Perhaps this should also affect the command-line (just as disabling restricted and multiverse would affect the command- line). Perhaps a dialogue box should be created when turning off snaps and the dialogue should ask whether to remove snapd entirely (first removing the snaps) or to set the refresh timer to monthly ( which is as close to turning it off as possible, timer CLI is here: https://snapdocs.labix.org/configuration-options/87 ), or to remove all snaps, or just to remove them from GNOME Software (for snaps, this could just hide apps that have their source listed as 'Snap Store'). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Jun 1 10:33:24 2018 InstallationDate: Installed on 2017-08-03 (301 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-04-22 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1774617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717490] Re: LightDM keeps plain text login password in memory
** Changed in: lightdm Importance: Undecided => Medium ** Changed in: lightdm Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1717490 Title: LightDM keeps plain text login password in memory Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: New Bug description: The lightdm process keeps the user password in memory, if the lightdm- greeter is used. This seems to be the case on Ubuntu up to the recent 17.04 version. The issue was validated with lightdm 1.22.0-0ubuntu2 (17.04) and 1.10.6-0ubuntu1 (14.04) Example: root@victim:~# ps fauxw | grep lightdm root 889 0.0 0.2 379344 8436 ?SLsl 12:43 0:00 /usr/sbin/lightdm root 968 1.3 1.8 379900 72804 tty7 Ssl+ 12:43 0:01 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root 1103 0.0 0.1 243564 6724 ?Sl 12:43 0:00 \_ lightdm --session-child 12 19 root 2074 0.0 0.0 21328 976 pts/0S+ 12:45 0:00 \_ grep --color=auto lightdm root@victim:~# gcore 1103 [...] Saved corefile core.1103 root@victim:~# strings core.1103 | grep -A5 -B5 secretpassword ttyCH0 ttyCH1 #...ttyCH63 # Moxa Intellio serial _pammodutil_getspnam_svbl_2 secretpassword gkr_system_authtok -UN*X-FAIL-svbl svbl 1000:1000:svbl,,, /home/svbl root@victim:~# As far as I can tell it seems that the password is not cleared form memory after passing it to PAM. This is not a direct vulnerability or breaking a security boundary (root access required to dump the memory) but it seems not to be necessary for lightdm to keep the pw in memory. A similar issue was reported to gnome-keyring-daemon, where the need of keeping the password is a bit more understandable (https://bugzilla.gnome.org/show_bug.cgi?id=764014). Do you see any reason why LightDM needs to keep the password in memory? To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1717490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735415] Re: VNC client does not exits after logout
Thanks for the fix!
https://github.com/CanonicalLtd/lightdm/commit/8283fc7b84e456760172f042bafc5827b6fcf29e
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1735415
Title:
VNC client does not exits after logout
Status in Light Display Manager:
Fix Committed
Status in lightdm package in Ubuntu:
New
Status in lightdm source package in Trusty:
New
Status in lightdm source package in Xenial:
New
Status in lightdm source package in Zesty:
New
Status in lightdm source package in Artful:
New
Status in lightdm source package in Bionic:
New
Bug description:
I have setup the remote desktop using the "[VNCServer]" configuration section.
When I log in using a VNC client and log out with the desktop panel menu,
the VNC client(remmina) does not exits.
I found that a VNC connection(TCP 5900) remains alive even though the Xvnc
server exits.
I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".
static gboolean
read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
{
...
client_socket = g_socket_accept (socket, NULL, &error);
...
if (client_socket)
{
...
g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
}
return TRUE;
}
I think that "g_object_unref(client_socket)" should be called after
g_signal_emit().
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1735415/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699637] Re: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Can you attach /var/log/lightdm/lightdm.log - that might give a better idea where this is occurring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1699637 Title: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Status in Light Display Manager: New Status in lightdm package in Ubuntu: New Bug description: lightdm work fine with xfce4(arch linux),but when i check it's status by systemd,it show this message. Jun 21 15:55:38 archlinux systemd[1]: Starting Light Display Manager... Jun 21 15:55:38 archlinux systemd[1]: Started Light Display Manager. Jun 21 15:55:38 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 21 15:55:38 archlinux lightdm[465]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid Jun 21 15:55:47 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 21 15:55:47 archlinux lightdm[607]: pam_unix(lightdm:session): session opened for user jaken by (uid=0) Jun 21 17:58:33 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1699637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 836616] Re: 100% cpu usage in lightdm
That screenshot shows Xorg (and compiz) running at 100% CPU, not LightDM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 972537] Re: lightdm doesn't allow expired passwords
** Changed in: lightdm (Ubuntu Precise) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/972537 Title: lightdm doesn't allow expired passwords Status in lightdm package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in unity-greeter source package in Precise: Triaged Bug description: [Impact] Kerberos accounts on Ubuntu 12.04.1 can't force password changes via unity-greeter. [Test Case] 1. Set up a Kerberos server and client machine (see http://bobthegnome.blogspot.co.nz/2012/11/testing-kerberos-in-ubuntu.html) 2. Log into unity-greeter on client machine Expected result: Unity Greeter shows appropriate prompts to change password and can log in once password changed/ Observed result: Some prompts skipped, password not changed and unable to log in. [Regression Potential] Potential of breaking other authentication. This has been tested with the lightdm regression tests. In Ubuntu 12.04, when logging in using the unity greeter in lightdm (1.1.9-0ubuntu1) with a user using Kerberos with an expired password, the login screen doesn't give the user the appropriate feedback to set their new password. The text console works correctly. The previous LTS used GDM, which behaved correctly. The normal prompting for this is: Username: cmo-test Password: Password expired. You must change it now. Enter new password: Enter it again: Instead, in lightdm, it is: Username: cmo-test Password: Enter it again: The "Password expired" message is never shown, and "Enter it again" is shown in the box instead of "Enter new password". If you use lighdm- gtk-greeter, you get the "password expired" message printed under the box, but still have the same prompting, never asking for the new password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/972537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 856269] Re: lightdm does not ask for a new password with pam_winbind or pam_krb5 authentications when the password is expired
** Changed in: lightdm (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/856269
Title:
lightdm does not ask for a new password with pam_winbind or pam_krb5
authentications when the password is expired
Status in lightdm package in Ubuntu:
Confirmed
Bug description:
I'm using an up-to-date oneiric workstation joined through samba and
winbind to an AD domain controlled by a Windows server.
When the password of a domain user is expired and when pam_winbind is
used as first authentication, lightdm does not ask for a new password
and does not allow to login, displaying the message "Invalid password,
please try again".
Instead, when pam_krb5 is used as first authentication, lightdm asks
two times for a password ("Enter it again:") and then allows to login
even if the password is expired.
When using a text console to login, the password changing dialog is
immediately presented (as it happens in natty with gdm).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/856269/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374379] Re: lightdm's session-cleanup-script get's called on unlock
** Changed in: lightdm/1.10 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.12 Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1374379 Title: lightdm's session-cleanup-script get's called on unlock Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in Light Display Manager 1.12 series: Won't Fix Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Won't Fix Bug description: When I unlock the screen after it has been locked by light locker the session-cleanup-script of lightdm get's called. I used to use the session-cleanup-script to umount some volumes on logout. I don't want to umount the volumes on lock or unlock. Maybe this is related to lightdm's #1249515 and might actually be a bug in lightdm!? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker 1.4.0-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: XFCE Date: Fri Sep 26 12:02:17 2014 InstallationDate: Installed on 2014-08-09 (47 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1374379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100469] Re: session processes left running after session logout
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1100469 Title: session processes left running after session logout Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Bug description: The fix for the zombie processes seems to have create the opposite issue, if you log in and out there is a session process left running, that happens for every session opened and closed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1100469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656399] Re: Returning to existing session is unreliable and can leave on blank screen
** Changed in: lightdm/1.18 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.10 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.20 Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1656399 Title: Returning to existing session is unreliable and can leave on blank screen Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in Light Display Manager 1.20 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: [Impact] Due to a logic bug LightDM returning to an existing session from a greeter can be unreliable. This case is common in systems which use the greeter as a lock screen. The bug was introduced in revision 1954 to fix bug 1296276. The race condition seems to have been made more likely to the change in revision 2437 to fix bug 1637758. [Test Case] 1. Log into a session 2. Switch to the greeter (e.g. dm-tool switch-to-greeter) 3. Log in again Expected result Returned to existing session Observed result Not always returned, can end up on blank screen. Since this is a race condition this may not occur on some systems. [Regression Potential] Low, the fix is to correct a logic bug that made LightDM think it hadn't stopped a session correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1656399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517685] Re: XDMCP server starts without authentication if configured key does not exist
** Changed in: lightdm (Ubuntu Precise) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1517685 Title: XDMCP server starts without authentication if configured key does not exist Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Confirmed Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Vivid: Fix Released Status in lightdm source package in Wily: Fix Released Bug description: [Impact] An incorrectly configured XDMCP server will start without authentication instead of disabling XDMCP / stopping LightDM. [Test Case] 1. Set up LightDM to run an XDMCP server using an XDM authentication key, i.e. in lightdm.conf: [XDMCPServer] enabled=true key=key-name 2. Do not create /etc/lightdm/keys.conf or do not define 'key-name' in keys.conf. 3. Start LightDM 4. Connect XDMCP client. Expected result: Either LightDM doesn't start or the XDMCP server doesn't start. Observed result: XDMCP server starts without authentication, any XDMCP client is able to connect. Debug message printed to log warning about missing key, but not easy to spot. [Regression Potential] Low - change is to not start LightDM if this case occurs. This could affect someone who currently has a misconfigured LightDM. In this case a warning message is printed to the log. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1517685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 915382] Re: ACPI events to shutdown/reboot don't generate a popup like after logging in
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/915382 Title: ACPI events to shutdown/reboot don't generate a popup like after logging in Status in lightdm package in Ubuntu: Triaged Bug description: There was a bug against virt-manager* where sending a "reboot" or "shutdown" event to a client seemingly doesn't do anything. Turns out that this only happens on the login screen, inside a session you get a popup asking what to do after the power button has been pushed. So something is wrong on the lightdm session, that prevents the popup from happening. This happens on real hw as well; if you hit the power button while looking at the login screen, nothing happens. * bug 228690 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/915382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases
** Changed in: lightdm Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1663157 Title: Guest session processes are not confined in 16.10 and newer releases Status in Light Display Manager: New Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Status in lightdm source package in Artful: Fix Released Bug description: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1663157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Changed in: lightdm/1.10 Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: lightdm/1.2 Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Vivid: Fix Released Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....
** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1264543 Title: Trusty sometimes boots with inactive keyboard . Status in lightdm package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing ++F2 and withing the terminal. Logout and login from the terminal followed by ++F7 to reaccess X does not bring back the keyboard. My current workaround is to use suspend and then reactivate. This always finds the keyboard after which all is normal. The problem began after an update to something (I'm not sure what as the problem is spasmodic). It was first noticed some two or three weeks ago. WORKAROUND: Works in Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-all 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: [ 26.884218] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 550.563790] audit_printk_skb: 138 callbacks suppressed [ 550.563794] type=1400 audit(1388145574.597:67): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2772 comm="apparmor_parser" [ 550.563802] type=1400 audit(1388145574.597:68): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" [ 550.564387] type=1400 audit(1388145574.597:69): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" Date: Fri Dec 27 16:23:05 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:9901] InstallationDate: Installed on 2013-10-21 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=b0a5ccea-5d55-4be4-838d-195afa498cc5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: FM2A55M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Fri Dec 27 11:50:49 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: radeon To manage notifications ab
[Touch-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Changed in: lightdm (Ubuntu Wily) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: New Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Vivid: Fix Released Status in lightdm source package in Wily: Fix Committed Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 619632]
Ping :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/619632 Title: Use gettext for translating user messages Status in PolicyKit: Unknown Status in Ubuntu Translations: Fix Released Status in policykit-1 package in Ubuntu: Fix Released Bug description: Binary package hint: policykit-1 PolicyKit currently requires translations to be in the XML, e.g.: Install system color profiles Instalovat systémové profily barev This makes it hard to modify translations after build-time and to provide only a set of translations (i.e. a language pack). It would be better to have: Install system color profiles And use the standard gettext system. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/619632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
** Changed in: packagekit (Ubuntu Cosmic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in packagekit source package in Cosmic: Fix Committed Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
** Description changed: - Using gnome software (or another PackageKit or aptdaemon based UI) to - install an application - removal of that package leaves behind - dependencies + [Impact] + Installing an application them removing it leaves dependencies behind. - Installing an application with ubuntu software centre only leaves behind - config files (seen in synaptic labelled for complete removal). + [Test Case] + 1. Ensure that GNOME Sudoku is not installed: + $ sudo apt remove gnome-sudoku libqqwing2v5 + 2. Check if you have any packages that need autoremoval: + $ sudo apt autoremove --no-act + 3. Open GNOME Software. + 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). + 5. Uninstall GNOME Sudoku. + 6. Check if you have any packages that need autoremoval: + $ sudo apt autoremove --no-act - After installing and then removing alarm clock with USC - + Expected result: + The packages in step 6 are the same as in step 2 (which might be none). - sudo apt-get autoremove - [sudo] password for wolf: - Reading package lists... Done - Building dependency tree - Reading state information... Done - 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. + Observed result: + The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. - After cleaning up and then reinstalling with gnome software, followed by - the removal - - sudo apt-get autoremove - Reading package lists... Done - Building dependency tree - Reading state information... Done - The following packages will be REMOVED - libappindicator1 libindicator7 - 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. - After this operation, 184 kB disk space will be freed. - - ProblemType: Bug - DistroRelease: Ubuntu 16.04 - Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 - ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 - Uname: Linux 4.4.0-10-generic x86_64 - ApportVersion: 2.20-0ubuntu3 - Architecture: amd64 - CurrentDesktop: XFCE - Date: Thu Mar 3 16:23:45 2016 - InstallationDate: Installed on 2015-10-29 (126 days ago) - InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) - SourcePackage: gnome-software - UpgradeStatus: No upgrade log present (probably fresh install) + [Regression Potential] + This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. ** Changed in: gnome-software (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: gnome-software (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Committed Status in packagekit package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Fix Committed Status in packagekit source package in Cosmic: Fix Committed Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touc
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
The bug is marked for bionic (18.04 LTS) but we'd want it to be well tested in Cosmic first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: Triaged Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in packagekit source package in Cosmic: Triaged Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
I opened an issue upstream about this: https://gitlab.gnome.org/GNOME /gnome-control-center/issues/229 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
** Changed in: packagekit (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727306] Re: window appears informing you need root privileges
Can you describe what you were trying to install and the method you were using? ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1727306 Title: window appears informing you need root privileges Status in lightdm package in Ubuntu: Incomplete Bug description: when you try to install the application window appears informing you need root privileges, enter your password, only responds to the close button ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:01:48 2017 InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1727306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727306] Re: window appears informing you need root privileges
** Changed in: lightdm (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1727306 Title: window appears informing you need root privileges Status in lightdm package in Ubuntu: New Bug description: when you try to install the application window appears informing you need root privileges, enter your password, only responds to the close button ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:01:48 2017 InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1727306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508592] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: evolution-data-server (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1508592 Title: Build with multiarch support Status in evolution-data-server package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1508592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508607] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: gupnp (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1508607 Title: Build with multiarch support Status in gupnp package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1508607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508605] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libzeitgeist (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1508605 Title: Build with multiarch support Status in libzeitgeist package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1508605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508616] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: gnome-control-center-signon (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch ** Tags added: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1508616 Title: Build with multiarch support Status in gnome-control-center-signon package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1508616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508627] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: gtkglext (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtkglext in Ubuntu. https://bugs.launchpad.net/bugs/1508627 Title: Build with multiarch support Status in gtkglext package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkglext/+bug/1508627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508621] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: gssdp (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1508621 Title: Build with multiarch support Status in gssdp package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1508621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508634] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: srtp (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to srtp in Ubuntu. https://bugs.launchpad.net/bugs/1508634 Title: Build with multiarch support Status in srtp package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/srtp/+bug/1508634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508639] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libmimic (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmimic in Ubuntu. https://bugs.launchpad.net/bugs/1508639 Title: Build with multiarch support Status in libmimic package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmimic/+bug/1508639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508638] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: pygobject-2 (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1508638 Title: Build with multiarch support Status in pygobject-2 package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1508638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508641] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libical (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libical in Ubuntu. https://bugs.launchpad.net/bugs/1508641 Title: Build with multiarch support Status in libical package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libical/+bug/1508641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508653] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: whoopsie (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1508653 Title: Build with multiarch support Status in whoopsie package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1508653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508650] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libdmapsharing (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdmapsharing in Ubuntu. https://bugs.launchpad.net/bugs/1508650 Title: Build with multiarch support Status in libdmapsharing package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/1508650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508652] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libopenobex (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libopenobex in Ubuntu. https://bugs.launchpad.net/bugs/1508652 Title: Build with multiarch support Status in libopenobex package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1508652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508654] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1508654 Title: Build with multiarch support Status in telepathy-mission-control-5 package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1508654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508655] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: neon27 (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/1508655 Title: Build with multiarch support Status in neon27 package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/1508655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508663] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: libkate (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libkate in Ubuntu. https://bugs.launchpad.net/bugs/1508663 Title: Build with multiarch support Status in libkate package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libkate/+bug/1508663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508669] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: zbar (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zbar in Ubuntu. https://bugs.launchpad.net/bugs/1508669 Title: Build with multiarch support Status in zbar package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/1508669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508671] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: tbb (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tbb in Ubuntu. https://bugs.launchpad.net/bugs/1508671 Title: Build with multiarch support Status in tbb package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tbb/+bug/1508671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508672] [NEW] Build with multiarch support
Public bug reported: Build with multiarch support ** Affects: xapian-core (Ubuntu) Importance: Medium Status: Triaged ** Tags: multiarch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xapian-core in Ubuntu. https://bugs.launchpad.net/bugs/1508672 Title: Build with multiarch support Status in xapian-core package in Ubuntu: Triaged Bug description: Build with multiarch support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xapian-core/+bug/1508672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: Triaged Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442609] Re: Guest session needs read access to "/proc/net/dev" and/or "/proc/*/net/dev" for network traffic applications
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1442609 Title: Guest session needs read access to "/proc/net/dev" and/or "/proc/*/net/dev" for network traffic applications Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: I'm customizing my guest sessions in Xubuntu 15.04 and discovered that xfce4-netload-plugin can't show current net traffic. After investigating netload plugin source code, I've found that a possible reason for this strange behaviour is that guest sessions are unable to read /proc/net/dev and/or /proc//net/dev. Could you please review current apparmor profile for lightdm-guest- session so it can get read access to /proc/net/dev? To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1442609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442611] Re: Guest session can't write on /var/run/screen
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1442611 Title: Guest session can't write on /var/run/screen Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: I'm customizing guest sessions in Xubuntu 15.04 in my school computer lab and dicovered that I'm unable to open user terminal in epoptes. The main reason for this problem is that epoptes uses screen for opening client terminals remotely on server session, but screen is currently unable to write on /var/run/screen for guest sessions. Could you please review current apparmor profile for lightdm-guest- session so it can get write access to /var/run/screen? To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1442611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478087] Re: Add libaudit support
** Changed in: lightdm Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in audit package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Triaged Status in shadow source package in Trusty: Triaged Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Bug description: -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1478087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc
** Changed in: lightdm (Ubuntu) Status: New => Triaged ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1509829 Title: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc Status in lightdm package in Ubuntu: Triaged Bug description: When logging into lightdm guest session, mozc gives an error saying "Failed to start Kana/Kanji conversion program. You need to reboot". Thus Japanese text cannot be input. [possibly related messages] 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.866:709): apparmor="DENIED" operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv" 10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 audit(1445787629.870:710): apparmor="DENIED" operation="bind" profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" family="unix" sock_type="stream" protocol=0 requested_mask="bind" denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 26 00:45:41 2015 InstallationDate: Installed on 2015-10-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509780] Re: High cpu usage when lightdm screenlock is active
What does 'top' say is the process that is using 100% CPU? It's probably the greeter or a child process, not lightdm. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1509780 Title: High cpu usage when lightdm screenlock is active Status in lightdm package in Ubuntu: Incomplete Bug description: When my system ist going to screenlock the cpu usage goes to 100 percent and the fanspeed goes up. When i switch with STRG+ALT+F1 to a terminal before the screenlock ist active, the system works fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 25 11:08:38 2015 EcryptfsInUse: Yes LightdmGreeterLog: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf upstart: indicator-application-main-Prozess (1164) wurde mit dem Status 1 beendet LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf upstart: indicator-application-main-Prozess (1074) wurde von TERM-Signal beendet upstart: indicator-messages-main-Prozess (1072) wurde von TERM-Signal beendet SourcePackage: lightdm UpgradeStatus: Upgraded to wily on 2015-10-10 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1509780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511841] Re: autologin fails for administrator user
The relevant parts from the LightDM log are: [+1.01s] DEBUG: Seat seat0: Display server ready, starting session authentication [+1.01s] DEBUG: Session pid=857: Started with service 'lightdm-autologin', username 'bouncysteve' [+1.09s] DEBUG: Session pid=857: Authentication complete with return value 0: Success [+1.09s] DEBUG: Seat seat0: Session authenticated, running command [+1.09s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0 [+1.10s] DEBUG: Session pid=857: Running command /usr/sbin/lightdm-session mate-session [+1.10s] DEBUG: Creating shared data directory /var/lib/lightdm-data/bouncysteve [+1.10s] DEBUG: Session pid=857: Logging to .xsession-errors [+1.80s] DEBUG: Activating VT 7 [+1.80s] DEBUG: Activating login1 session c1 [+1.80s] DEBUG: Seat seat0 changes active session to c1 [+1.80s] DEBUG: Session c1 is already active [+1.82s] DEBUG: Session pid=857: Exited with return value 1 Which says the autologin did complete, but the session exited for some reason. You may be able to find out why by looking at ~/.xsession- errors. Otherwise the issue is probably in mate-session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511841 Title: autologin fails for administrator user Status in lightdm package in Ubuntu: New Bug description: I had two user accounts on the machine, an administrator and a normal user. I edited a conf file in /etc/lightdm to auto login the unprivileged user, which worked fine. I then deleted the unprivlieged user and changed the config file to autologin the remaining user. This does not work, a password prompt is always presented to this user. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic i686 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: i386 CurrentDesktop: MATE Date: Fri Oct 30 20:06:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-26 (33 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:905): WARNING **: [PIDs] Failed to execute command: upstart ** (lightdm-gtk-greeter:905): WARNING **: Failed to load user image: Failed to open file '/home/bouncysteve/.face': Permission denied SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1511841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511921] Re: Fail to start on systemd
LightDM is running via systemd everywhere on Ubuntu, we need more information on what exactly is not working. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511921 Title: Fail to start on systemd Status in lightdm package in Ubuntu: Incomplete Bug description: On upstart init system work fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic i686 ApportVersion: 2.19.1-0ubuntu4 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 31 09:49:25 2015 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1511921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312526] Re: lightdm fails to start session unless user selects session
Removing lightdm task as it is the responsibility of the greeters to choose a valid session. ** No longer affects: lightdm (Ubuntu) ** Changed in: unity-greeter (Ubuntu) Status: Confirmed => Triaged ** Changed in: unity-greeter (Ubuntu) Importance: Undecided => High ** Changed in: unity-greeter (Ubuntu) Milestone: None => ubuntu-16.04 ** Summary changed: - lightdm fails to start session unless user selects session + Greeter uses previous session even if it is not available -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1312526 Title: Greeter uses previous session even if it is not available Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Triaged Bug description: I install using preseed files, and clobber a bit of /etc to configure ubuntu to be suitable for users to login with network credentials. I use pam to make a home directory when users login with network credentials. On first boot, logging into the VTs works fine but I cannot log into the lightdm dislpay manager. If I type my username and password right, I get a "Failed to start session" message and get bounced back to the start of the login process. If, however, I click one of the session types, e.g. 'ubuntu' or 'fluxbox', then I can log in. (I've tried uninstalling fluxbox, this doesn't seem to help). At which point I can login, which I believe works until I reboot the machine. (I will test this shortly). If I install the lightdm-gtk-greeter package then I do not encounter this bug. Instead, I am automatically logged into the alphabetically first session type (at least, if I've got fluxbox available vs. either ubuntu or xfce, that seems to be what I get, if only ubuntu is install I get an ubunut session by default so I assume the preference is alphabetical). It does not seem to matter if I specify a user-session=something (I have also tried not setting user-session at all) in lightdm.conf (well, I haven't tried it with the gtk-greeter, but it doesn't matter with the unity greeter). I've tried all of the other lightdm-greeter packages, and lightdm- greeter-gtk is the only one that does not suffer from this bug. the most relvant message in the logs I can find is: DEBUG: Seat: Failed to find session configuration true Seat: Can't find session 'true' What I would expect to happen is to get some default session; getting the alphabetically first session is kind-of/sort-of reasonable. Total failure is not. 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 NonfreeKernelModules: openafs ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 24 22:08:08 2014 LightdmConfig: [SeatDefaults] user-session=true greeter-hide-users=true greeter-allow-guest=false session-setup-script=/bin/sh -l /etc/profile SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1312526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Changed in: lightdm/1.16 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: Triaged Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478087] Re: Add libaudit support
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in audit package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Triaged Status in shadow source package in Trusty: Triaged Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Bug description: -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1478087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468057] Re: Emit a warning about "logind-load-seats=true" and "xdg-seat=seatXXXX" option for LightDM 1.12+
** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Description changed: - LightDM 1.12 introduced a new logind-based mechanism for loading seats. - Such a feature was later backported to 1.10.3 (so it can be used in - Ubuntu 14.04 LTS), but it was made optional: + [Impact] - [LightDM] - logind-load-seats=true + [Test Case] + 1. Add login-load-seats=true into lightdm.conf + 2. Run LightDM + 3. Check /var/log/lightdm/lightdm.log - Now that we're halfway from a new Ubuntu LTS release, I think it would - be useful if next LightDM release could emit a warning about "logind- - load-seats=true" deprecation if it's set in lightdm.conf. Something like - this: + Expected result: + A warning should be there that this option is no longer required. - WARNING: Option "logind-load-seats=true" was specific for 1.10 series. - You can safely remove it now. + Observed result: + No warning is shown. ** Description changed: [Impact] + Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. ** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Description changed: [Impact] Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. + + [Regression potential] + Low. The change just checks for presence of an option and generates a log message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1468057 Title: Emit a warning about "logind-load-seats=true" and "xdg-seat=seat" option for LightDM 1.12+ Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Triaged Bug description: [Impact] Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. [Regression potential] Low. The change just checks for presence of an option and generates a log message. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1468057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507033] Re: lightdm.conf is sensitive to trailing whitespace
** Also affects: ubuntu Importance: Undecided Status: New ** Also affects: Ubuntu Vivid Importance: Undecided Status: New ** Package changed: ubuntu => lightdm (Ubuntu) ** Changed in: lightdm (Ubuntu) Status: New => Fix Released ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Summary changed: - lightdm.conf is sensitive to trailing whitespace + lightdm.conf boolean values false if have trailing whitespace ** Description changed: - It appears that lightdm.conf is sensitive to trailing spaces. I get - different behavior with + [Impact] + Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. - greeter-hide-users=true + [Test Case] + 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) + 2. Run LightDM - and + Expected result: + The configured value is interpreted as true. - greeter-hide-users=true_ + Observed result: + The configured value is interpreted as false. - where the _ in the second example represents a trailing space. Without - the space, the greeter hides the list of users as I expected. With the - space, the greeter displays the list of users as if the greeter-hide- - users parameter is not set to true. + [Regression potential] + Low. We just strip trailing whitespace when checking for the value "true". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Triaged Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Description changed: - Currently LightDM connects to an XDMCP enabled X server using the first - suitable address in the XDMCP Request packet. However, some clients may - put a number of addresses in this message and potentially they are not - all routable. If the address the request message came from is in the - list we should use that first as that is more likely to be a routable - address. This also matches the behaviour of GDM which ignores the - contents of the Request packet anyway. + [Impact] + Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. + + [Test Case] + 1. Start LightDM with XDMCP enabled + 2. Connect with a client that puts a number of addresses in the Request packet + + Expected result: + LightDM prefers the address the Request came from over the other addresses. + + Observed result: + LightDM always picks the first address. + + [Regression Potential] + There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). ** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Triaged Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511259] Re: Session child does not inherit all LC_* variables
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Also affects: ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu (Ubuntu) Status: Fix Released => Fix Committed ** Package changed: ubuntu (Ubuntu) => lightdm (Ubuntu) ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => In Progress ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: In file session-child.c in function session_child_run() variable `locale_var_names` contains explicit list of locale environment variables to inherit. This list lacks of some LC_* variables: LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION. As a result, these variables are not inherited by child session. Therefore, processes inside desktop session set these variables to the value of LANG, instead of appropriate values configured in /etc/locale.conf. $ more /etc/locale.conf LANG=en_US.UTF-8 LC_CTYPE=pl_PL.UTF-8 LC_NUMERIC=pl_PL.UTF-8 LC_TIME=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 LC_MONETARY=pl_PL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=pl_PL.UTF-8 LC_NAME=pl_PL.UTF-8 LC_ADDRESS=pl_PL.UTF-8 LC_TELEPHONE=pl_PL.UTF-8 LC_MEASUREMENT=pl_PL.UTF-8 LC_IDENTIFICATION=pl_PL.UTF-8 LC_ALL= Inside desktop session: $ locale LANG=en_US.utf8 LC_CTYPE=pl_PL.UTF-8 LC_NUMERIC=pl_PL.UTF-8 LC_TIME=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 LC_MONETARY=pl_PL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= Notice wrong values of LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION (en_US.utf8 instead pl_PL.UTF-8). Fix: Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION to the `locale_var_names` array in file session- child.c. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470587] Re: dm-tool manpage has a typo
** Description changed: - Running Ubuntu 14.04.2 LTS on armhf with lightdm version 1.10.5-0ubuntu1 + [Impact] + Small typo in dm-tool man page. - The the dm-tool lock option has a typo that says "swith" instead of - "switch" in the manpage + [Test Case] + 1. View man page: + $ man dm-tool + + Expected result: + Says "switch" + + Observed result: + Says "swith" + + [Regression potential] + About as low as you can get... ** No longer affects: lightdm (Ubuntu Wily) ** No longer affects: lightdm (Ubuntu Utopic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1470587 Title: dm-tool manpage has a typo Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Small typo in dm-tool man page. [Test Case] 1. View man page: $ man dm-tool Expected result: Says "switch" Observed result: Says "swith" [Regression potential] About as low as you can get... To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1470587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511545] Re: Implement XDMCP ForwardQuery
** Description changed: - If LightDM receives and XDMCP ForwardQuery it currently ignores it. It - should send back a Willing to the address specified in the query - request. + [Impact] + LightDM ignores the XDMCP ForwardQuery request. + + [Test Case] + 1. Set up XDMCP so queries are forwarded through a server + 2. Connect to LightDM + + Observed result: + Connection fails + + Expected result: + Connection succeeds. + + [Regression Potential] + Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => In Progress ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: lightdm (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511545 Title: Implement XDMCP ForwardQuery Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] LightDM ignores the XDMCP ForwardQuery request. [Test Case] 1. Set up XDMCP so queries are forwarded through a server 2. Connect to LightDM Observed result: Connection fails Expected result: Connection succeeds. [Regression Potential] Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511545/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: In Progress Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511259] Re: Session child does not inherit all LC_* variables
** Description changed: - In file session-child.c in function session_child_run() variable - `locale_var_names` contains explicit list of locale environment - variables to inherit. This list lacks of some LC_* variables: LC_PAPER, - LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION. - As a result, these variables are not inherited by child session. - Therefore, processes inside desktop session set these variables to the - value of LANG, instead of appropriate values configured in - /etc/locale.conf. + [Impact] + Not all system locale variables are passed to sessions. - $ more /etc/locale.conf - LANG=en_US.UTF-8 - LC_CTYPE=pl_PL.UTF-8 - LC_NUMERIC=pl_PL.UTF-8 - LC_TIME=pl_PL.UTF-8 - LC_COLLATE=pl_PL.UTF-8 - LC_MONETARY=pl_PL.UTF-8 - LC_MESSAGES=en_US.UTF-8 - LC_PAPER=pl_PL.UTF-8 - LC_NAME=pl_PL.UTF-8 - LC_ADDRESS=pl_PL.UTF-8 - LC_TELEPHONE=pl_PL.UTF-8 - LC_MEASUREMENT=pl_PL.UTF-8 - LC_IDENTIFICATION=pl_PL.UTF-8 - LC_ALL= + [Test Case] + 1. Edit /etc/locale.conf and set LC_PAPER to a particular value + 2. Start LightDM + 3. Log into a session - Inside desktop session: + Expected result: + LC_PAPER is set to the value in /etc/locale.conf - $ locale - LANG=en_US.utf8 - LC_CTYPE=pl_PL.UTF-8 - LC_NUMERIC=pl_PL.UTF-8 - LC_TIME=pl_PL.UTF-8 - LC_COLLATE=pl_PL.UTF-8 - LC_MONETARY=pl_PL.UTF-8 - LC_MESSAGES=en_US.UTF-8 - LC_PAPER="en_US.utf8" - LC_NAME="en_US.utf8" - LC_ADDRESS="en_US.utf8" - LC_TELEPHONE="en_US.utf8" - LC_MEASUREMENT="en_US.utf8" - LC_IDENTIFICATION="en_US.utf8" - LC_ALL= + Observed result: + LC_PAPER is not set. - Notice wrong values of LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, - LC_MEASUREMENT and LC_IDENTIFICATION (en_US.utf8 instead pl_PL.UTF-8). - - Fix: - - Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and - LC_IDENTIFICATION to the `locale_var_names` array in file session- - child.c. + [Regression potential] + Low. We just added to an existing list of LC_* variables that are passed through to sessions. ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468057] Re: Emit a warning about "logind-load-seats=true" and "xdg-seat=seatXXXX" option for LightDM 1.12+
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1468057 Title: Emit a warning about "logind-load-seats=true" and "xdg-seat=seat" option for LightDM 1.12+ Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. [Regression potential] Low. The change just checks for presence of an option and generates a log message. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1468057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm (Ubuntu Vivid) Status: Fix Committed => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470587] Re: dm-tool manpage has a typo
** Changed in: lightdm (Ubuntu Vivid) Status: Fix Committed => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1470587 Title: dm-tool manpage has a typo Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Small typo in dm-tool man page. [Test Case] 1. View man page: $ man dm-tool Expected result: Says "switch" Observed result: Says "swith" [Regression potential] About as low as you can get... To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1470587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
