[Touch-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
Fixed on vivid. I attempted to connect using the ethernet interfaces address (Xephyr :1 -query ) and was not able to when this option is enabled. ** Tags removed: verification-needed ** Tags added: verification-done-vivid -- 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 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: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Vivid: Fix Committed 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
[Touch-packages] [Bug 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-done ** Tags added: verification-done-vivid -- 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 Vivid: Fix Committed Status in lightdm source package in Wily: Fix Committed 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 1514908] Re: add support for non-root X sessions
*** This bug is a duplicate of bug 1292324 *** https://bugs.launchpad.net/bugs/1292324 ** This bug has been marked a duplicate of bug 1292324 Support non-root X -- 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/1514908 Title: add support for non-root X sessions Status in lightdm package in Ubuntu: New Bug description: Xenial now has an xserver which supports running it as a normal user with the help of logind and libpam-systemd. Consider adding support for it like GDM has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1514908/+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 1292324] Re: Support non-root X
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: New => Triaged ** Changed in: lightdm (Ubuntu) Importance: Undecided => Wishlist -- 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/1292324 Title: Support non-root X Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Bug description: Support running X as an unprivileged user. Currently X servers are run as root means a large complex process has access to services it might not need (i.e. potential security and stability problems). It would be nice to run each X server as either an unprivileged user or in the session they are being used in. Logind provides a system for sharing access to the display and input devices so this can be done - this seems like the most likely implementation of non-root X. For more information see Hans de Goede request: http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1292324/+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
** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu) ** Changed in: lightdm-gtk-greeter (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/1509780 Title: High cpu usage when lightdm screenlock is active Status in lightdm-gtk-greeter package in Ubuntu: New 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-gtk-greeter/+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 1513699] Re: Light DM creates login loop
The log shows you are logging into your session, but it quits after 10 second. Can you try this and then look at the contents of ~/.xsession- errors after this occurs? ** 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/1513699 Title: Light DM creates login loop Status in lightdm package in Ubuntu: Incomplete Bug description: After updating Ubuntu, I restarted the computer. The Light DM Display screen came up. I thought nothing of it until I tried logging in. Instead of logging in, it would go black for a second and bring me to the login page again. I've tried all sorts of commands from online Ubuntu support groups. Nothing has worked. My laptop is 5 yrs old, so I don't know if it's telling me it's dead. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 Date: Thu Nov 5 20:38:03 2015 InstallationDate: Installed on 2014-03-18 (598 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1513699/+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 1470655] Re: Update to PackageKit 1.0
We discussed at the Desktop team sprint that we should drop aptdaemon, so I think we can do this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1470655 Title: Update to PackageKit 1.0 Status in click package in Ubuntu: New Status in packagekit package in Ubuntu: Triaged Bug description: Update to 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1470655/+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 1470655] Re: Update to PackageKit 1.0
We can probably just sync from Debian when ready. The only substantial change seems to the virtual packagekit-system-interface provides which is probably not necessary anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1470655 Title: Update to PackageKit 1.0 Status in click package in Ubuntu: New Status in packagekit package in Ubuntu: Triaged Bug description: Update to 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1470655/+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 1467267] Re: Please sync to 1.0.6 from Debian (main)
I updated the patches so NM 1.0.6 compiles in lp:~robert-ancell/network- manager/update-1.0.6. However when I run it I don't see any network devices. Please review the patches and check if I've updated them correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1467267 Title: Please sync to 1.0.6 from Debian (main) Status in network-manager package in Ubuntu: Triaged Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Fix Released Bug description: === NetworkManager-1.0.6 Overview of changes since NetworkManager-1.0.4 === This is a new stable release of NetworkManager. Notable changes include: * Improved capture portal detection. * Default route through WiFi connection is now preferred to Mobile Broadband if both are available. * Expose a flag to determine whether a particular connection is metered via API and client tools. * Add support for locking connections to a channel within a particular band. * Add support for configuring Wake-on-LAN capabilitites. * Allow overriding the MTU for team device. * Usual pile of bug fixes and robustness improvements. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 0.9.10.0-4ubuntu16 ProcVersionSignature: Ubuntu 4.0.0-2.4-generic 4.0.5 Uname: Linux 4.0.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jun 21 16:56:40 2015 IpRoute: default via 192.168.1.1 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-06-13T08:56:31.598901 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 802-3-ethernet 1434898501 dim. 21 juin 2015 16:55:01 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth1activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1467267/+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 1467267] Re: Please sync to 1.0.6 from Debian (main)
** Changed in: network-manager-applet (Ubuntu) Status: Fix Released => Triaged ** Changed in: network-manager-pptp (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1467267 Title: Please sync to 1.0.6 from Debian (main) Status in network-manager package in Ubuntu: Triaged Status in network-manager-applet package in Ubuntu: Triaged Status in network-manager-pptp package in Ubuntu: Triaged Bug description: === NetworkManager-1.0.6 Overview of changes since NetworkManager-1.0.4 === This is a new stable release of NetworkManager. Notable changes include: * Improved capture portal detection. * Default route through WiFi connection is now preferred to Mobile Broadband if both are available. * Expose a flag to determine whether a particular connection is metered via API and client tools. * Add support for locking connections to a channel within a particular band. * Add support for configuring Wake-on-LAN capabilitites. * Allow overriding the MTU for team device. * Usual pile of bug fixes and robustness improvements. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 0.9.10.0-4ubuntu16 ProcVersionSignature: Ubuntu 4.0.0-2.4-generic 4.0.5 Uname: Linux 4.0.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jun 21 16:56:40 2015 IpRoute: default via 192.168.1.1 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-06-13T08:56:31.598901 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 802-3-ethernet 1434898501 dim. 21 juin 2015 16:55:01 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth1activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1467267/+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 1470655] Re: Update to PackageKit 1.0
Blocking gnome-packagekit (bug 1470657) ** Changed in: packagekit (Ubuntu) Importance: Wishlist => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1470655 Title: Update to PackageKit 1.0 Status in click package in Ubuntu: New Status in packagekit package in Ubuntu: Triaged Bug description: Update to 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1470655/+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 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/1511259 Title: Session child does not inherit all LC_* variables 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 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 1511545] Re: Implement XDMCP ForwardQuery
** 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/1511545 Title: Implement XDMCP ForwardQuery 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: 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 1511545] Re: Implement XDMCP ForwardQuery
** Changed in: lightdm/1.16 Status: Fix Committed => Fix Released ** 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/1511545 Title: Implement XDMCP ForwardQuery 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: 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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** 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/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 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: 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
[Touch-packages] [Bug 1511259] Re: Session child does not inherit all LC_* variables
** 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/1511259 Title: Session child does not inherit all LC_* variables 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 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 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** 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/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 Released 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** 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/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 Released 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/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/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 Released 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 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** 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/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 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 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 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 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 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 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
[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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Summary changed: - apparmor rules too tight for chromium + Chromium not working in guest session (need more AppArmor rules) -- 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 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 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
** Summary changed: - Guest session can't read "/proc/net/dev" and/or "/proc/*/net/dev" + Guest session needs read access to "/proc/net/dev" and/or "/proc/*/net/dev" for network traffic applications -- 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 Committed 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 1478087] Re: Add libaudit support
** Summary changed: - ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3 + Add libaudit support -- 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 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 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 1442609] Re: Guest session can't read "/proc/net/dev" and/or "/proc/*/net/dev"
** Changed in: lightdm Status: Triaged => Fix Committed ** Changed in: lightdm Milestone: None => 1.17.0 -- 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 can't read "/proc/net/dev" and/or "/proc/*/net/dev" Status in Light Display Manager: Fix Committed 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 1506771] Re: 'Unable to create session' when logging in to a newly created user
What tool are you using to create the user account? xfce4-settings? ** Changed in: lightdm (Ubuntu) Status: New => Incomplete ** 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/1506771 Title: 'Unable to create session' when logging in to a newly created user Status in lightdm package in Ubuntu: Incomplete Bug description: Similar but not the same as 1056833. After creating a new user I was unable to login to her id from lightdm. I could login on a text console and then run startx. I think the problem is that /var/lib/AccountService/user/$user had Xsession=ubuntu instead of xfce. I do not have any Unity code on my machine. There is no option in the create-user dialogue to select a session type, not in the lightdm login screen. I will do some more testing and report back when I have finished this bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 CurrentDesktop: XFCE Date: Fri Oct 16 09:08:34 2015 LightdmConfig: [SeatDefaults] greeter-session = unity-greeter allow-guest = false SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-08-23 (418 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1506771/+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 1506771] Re: 'Unable to create session' when logging in to a newly created user
When I create a user here there is no XSession set in /var/lib/AccountService/user/$user -- 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/1506771 Title: 'Unable to create session' when logging in to a newly created user Status in lightdm package in Ubuntu: Incomplete Bug description: Similar but not the same as 1056833. After creating a new user I was unable to login to her id from lightdm. I could login on a text console and then run startx. I think the problem is that /var/lib/AccountService/user/$user had Xsession=ubuntu instead of xfce. I do not have any Unity code on my machine. There is no option in the create-user dialogue to select a session type, not in the lightdm login screen. I will do some more testing and report back when I have finished this bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 CurrentDesktop: XFCE Date: Fri Oct 16 09:08:34 2015 LightdmConfig: [SeatDefaults] greeter-session = unity-greeter allow-guest = false SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-08-23 (418 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1506771/+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
Merge proposal? -- 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: Triaged 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 1506771] Re: 'Unable to create session' when logging in to a newly created user
Can you get a /var/log/lightdm/lightdm.log after this occurs? The log attached here seems to show a successful login (i.e. your existing user). It does sound like the configuration has chosen an invalid session and so LightDM returns you to the greeter. -- 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/1506771 Title: 'Unable to create session' when logging in to a newly created user Status in lightdm package in Ubuntu: Incomplete Bug description: Similar but not the same as 1056833. After creating a new user I was unable to login to her id from lightdm. I could login on a text console and then run startx. I think the problem is that /var/lib/AccountService/user/$user had Xsession=ubuntu instead of xfce. I do not have any Unity code on my machine. There is no option in the create-user dialogue to select a session type, not in the lightdm login screen. I will do some more testing and report back when I have finished this bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 CurrentDesktop: XFCE Date: Fri Oct 16 09:08:34 2015 LightdmConfig: [SeatDefaults] greeter-session = unity-greeter allow-guest = false SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-08-23 (418 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1506771/+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 1506771] Re: 'Unable to create session' when logging in to a newly created user
The LightDM log seems to be missing. Is the user file for an existing user or one that has just been created? I want to check if XSession is set at user creation time or by something else later. My best guess is either two things are happening: - Something at user creation time is setting XSession to an invalid value. - The greeter you are using (lightdm-gtk-greeter?) is choosing an invalid session when you try and log in - it should not do this. -- 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/1506771 Title: 'Unable to create session' when logging in to a newly created user Status in lightdm package in Ubuntu: Incomplete Bug description: Similar but not the same as 1056833. After creating a new user I was unable to login to her id from lightdm. I could login on a text console and then run startx. I think the problem is that /var/lib/AccountService/user/$user had Xsession=ubuntu instead of xfce. I do not have any Unity code on my machine. There is no option in the create-user dialogue to select a session type, not in the lightdm login screen. I will do some more testing and report back when I have finished this bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: i386 CurrentDesktop: XFCE Date: Fri Oct 16 09:08:34 2015 LightdmConfig: [SeatDefaults] greeter-session = unity-greeter allow-guest = false SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-08-23 (418 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1506771/+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 Milestone: None => 1.17.0 ** Changed in: lightdm Status: Triaged => Fix Committed -- 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 Committed 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 1504049] Re: apparmor rules too tight for chromium
Laércio - can you open a new bug for this? -- 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: apparmor rules too tight for chromium 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 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.16 Status: Triaged => Fix Committed ** Changed in: lightdm/1.16 Milestone: None => 1.16.5 -- 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 Committed Status in Light Display Manager 1.10 series: Triaged 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm/1.14 Milestone: None => 1.14.3 ** Changed in: lightdm/1.10 Milestone: None => 1.10.6 -- 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 Committed Status in Light Display Manager 1.10 series: Triaged 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Also affects: lightdm/1.16 Importance: Undecided Status: New ** Also affects: lightdm/1.10 Importance: Undecided Status: New ** Also affects: lightdm/1.2 Importance: Undecided Status: New ** Also affects: lightdm/1.14 Importance: Undecided Status: New ** Changed in: lightdm/1.2 Status: New => Won't Fix ** Changed in: lightdm/1.2 Importance: Undecided => Low ** Changed in: lightdm/1.14 Status: New => Triaged ** Changed in: lightdm/1.16 Status: New => Triaged ** Changed in: lightdm/1.14 Importance: Undecided => Medium ** Changed in: lightdm/1.16 Importance: Undecided => Medium ** Changed in: lightdm Milestone: None => 1.17.0 ** Changed in: lightdm/1.10 Importance: Undecided => Low ** Changed in: lightdm/1.10 Status: New => Triaged ** Changed in: lightdm Status: Triaged => Fix Committed -- 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 Committed Status in Light Display Manager 1.10 series: Triaged 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm/1.14 Status: Triaged => Fix Committed -- 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 Committed Status in Light Display Manager 1.10 series: Triaged 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm/1.10 Status: Triaged => Fix Committed -- 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 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: 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 1504442] Re: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1504442 Title: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128) Status in gconf package in Ubuntu: New Bug description: This package failed to configure during an upgrade. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gconf2 3.2.6-3ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Fri Oct 9 01:34:43 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/sbin/gconf-schemas InstallationDate: Installed on 2013-03-08 (944 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/sbin/gconf-schemas --register-all --no-signal ProcEnviron: LANGUAGE=C TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash PythonArgs: ['/usr/sbin/gconf-schemas', '--register-all', '--no-signal'] SourcePackage: gconf Title: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128) UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1504442/+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 1489018] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1
*** This bug is a duplicate of bug 1406641 *** https://bugs.launchpad.net/bugs/1406641 ** This bug is no longer a duplicate of bug 1489017 package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 ** This bug has been marked a duplicate of bug 1468199 package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 ** This bug is no longer a duplicate of bug 1468199 package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 ** This bug has been marked a duplicate of bug 1406641 package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1489018 Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post- installation 脚本 返回了错误号 1 Status in gconf package in Ubuntu: New Bug description: nautilus-open-terminal ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: nautilus-open-terminal: Install nautilus-open-terminal: Configure Architecture: i386 Date: Wed Aug 26 22:15:56 2015 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2015-08-25 (1 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1489018/+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 1489017] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1
*** This bug is a duplicate of bug 1406641 *** https://bugs.launchpad.net/bugs/1406641 ** This bug has been marked a duplicate of bug 1468199 package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 ** This bug is no longer a duplicate of bug 1468199 package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 ** This bug has been marked a duplicate of bug 1406641 package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1489017 Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post- installation 脚本 返回了错误号 1 Status in gconf package in Ubuntu: New Bug description: nautilus-open-terminal ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: nautilus-open-terminal: Install nautilus-open-terminal: Configure Architecture: i386 Date: Wed Aug 26 22:15:56 2015 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2015-08-25 (1 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1489017/+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 1440549] Re: please convert python scripts to python3
This seems to be causing failures when the files contain non valid ASCII, see bug 1406641 and bug 1504442 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1440549 Title: please convert python scripts to python3 Status in gconf package in Ubuntu: Incomplete Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. Please convert the two python scripts installed with the gconf2 package to Python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1440549/+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 1468199] Re: package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
*** This bug is a duplicate of bug 1406641 ***
https://bugs.launchpad.net/bugs/1406641
** This bug has been marked a duplicate of bug 1406641
package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-processus
script post-installation installé a retourné une erreur de sortie d'état 1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1468199
Title:
package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装 post-
installation 脚本 返回错误状态 1
Status in gconf package in Ubuntu:
Confirmed
Bug description:
Traceback (most recent call last):
File "/usr/sbin/gconf-schemas", line 125, in
trim(os.path.join(defaults_dest,"%gconf-tree.xml"), get_valid_languages())
File "/usr/sbin/gconf-schemas", line 18, in get_valid_languages
langs.add(l.split('_')[0])
TypeError: 'str' does not support the buffer interface
dpkg: 处理软件包 gconf2 (--unpack)时出错：
子进程 已安装 post-installation 脚本 返回错误状态 1
在处理时有错误发生：
update-notifier-common
gconf2
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: gconf2 3.2.6-3ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Wed Jun 24 14:26:54 2015
DuplicateSignature: package:gconf2:3.2.6-3ubuntu1:子进程 已安装 post-installation
脚本 返回错误状态 1
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2015-06-23 (1 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
dpkg 1.17.25ubuntu1
apt 1.0.9.7ubuntu4
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu1 failed to install/upgrade: 子进程 已安装
post-installation 脚本 返回错误状态 1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1468199/+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 1406641] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
** Changed in: gconf (Ubuntu) Status: Confirmed => Triaged ** Changed in: gconf (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1406641 Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in gconf package in Ubuntu: Triaged Bug description: Used command : sudo apt-get install gconf-editor ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: gconf-defaults-service: Install gconf-editor: Install gconf-defaults-service: Configure gconf-editor: Configure Architecture: amd64 Date: Tue Dec 30 21:09:48 2014 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2014-02-10 (322 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to trusty on 2014-11-08 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1406641/+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 1504442] Re: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128)
** Changed in: gconf (Ubuntu) Status: New => Triaged ** Changed in: gconf (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1504442 Title: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128) Status in gconf package in Ubuntu: Triaged Bug description: This package failed to configure during an upgrade. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: gconf2 3.2.6-3ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Fri Oct 9 01:34:43 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/sbin/gconf-schemas InstallationDate: Installed on 2013-03-08 (944 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/sbin/gconf-schemas --register-all --no-signal ProcEnviron: LANGUAGE=C TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash PythonArgs: ['/usr/sbin/gconf-schemas', '--register-all', '--no-signal'] SourcePackage: gconf Title: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128) UpgradeStatus: Upgraded to wily on 2015-09-15 (24 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1504442/+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: apparmor rules too tight for chromium
** Changed in: lightdm/1.10 Importance: Undecided => Medium ** Changed in: lightdm/1.10 Status: New => Fix Committed ** Changed in: lightdm/1.10 Milestone: None => 1.10.6 ** Changed in: lightdm/1.14 Importance: Undecided => Medium ** Changed in: lightdm/1.14 Status: New => Fix Committed ** Changed in: lightdm/1.14 Milestone: None => 1.14.3 ** Changed in: lightdm/1.16 Importance: Undecided => Medium ** Changed in: lightdm/1.16 Status: New => Fix Committed ** Changed in: lightdm/1.16 Milestone: None => 1.16.4 ** Changed in: lightdm (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Trusty) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Wily) 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/1504049 Title: apparmor rules too tight for chromium 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 chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Triaged 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: Triaged Bug description: Hi, when running chromium, I get lots of apparmor alerts and warnings, although actions seem to be legitimate and normal. Looks as if the apparmor ruleset is too tight. See attached logs. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 45.0.2454.101-0ubuntu1.1201 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DP.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.DP.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.DP.3: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.3: edid-base64: AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA== dpms: On modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Thu Oct 8 11:48:15 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2015-09-03 (34 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) InstalledPlugins: Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: N3150-NUC 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:
[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium
** Description changed: - Hi, + [Impact] + Unable to run Chromium from guest session. - when running chromium, I get lots of apparmor alerts and warnings, - although actions seem to be legitimate and normal. Looks as if the - apparmor ruleset is too tight. + [Test Case] + 1. Start Ubuntu + 2. From greeter select guest session + 3. Load Chromium - See attached logs. + Expected result: + Chromium runs. - ProblemType: Bug - DistroRelease: Ubuntu 15.10 - Package: chromium-browser 45.0.2454.101-0ubuntu1.1201 - ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 - Uname: Linux 4.2.0-14-generic x86_64 - ApportVersion: 2.19-0ubuntu1 - Architecture: amd64 - CurrentDesktop: XFCE - DRM.card0.DP.1: - edid-base64: - dpms: On - modes: - enabled: disabled - status: disconnected - DRM.card0.DP.2: - edid-base64: - dpms: On - modes: - enabled: disabled - status: disconnected - DRM.card0.DP.3: - edid-base64: - dpms: On - modes: - enabled: disabled - status: disconnected - DRM.card0.HDMI.A.1: - edid-base64: - dpms: On - modes: - enabled: disabled - status: disconnected - DRM.card0.HDMI.A.2: - edid-base64: - dpms: On - modes: - enabled: disabled - status: disconnected - DRM.card0.HDMI.A.3: - edid-base64: AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA== - dpms: On - modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400 - enabled: enabled - status: connected - Date: Thu Oct 8 11:48:15 2015 - Desktop-Session: - 'xubuntu' - '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' - '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' - DetectedPlugins: - - Env: - 'None' - 'None' - InstallationDate: Installed on 2015-09-03 (34 days ago) - InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) - InstalledPlugins: - - Load-Avg-1min: 0.47 - Load-Processes-Running-Percent: 0.2% - MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet splash vt.handoff=7 - SourcePackage: chromium-browser - UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 07/16/2015 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: P1.10 - dmi.board.name: N3150-NUC - 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.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC: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. - gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' - modified.conffile..etc.default.chromium.browser: [deleted] + 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. -- 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: apparmor rules too tight for chromium 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 chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Triaged Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in
[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
Agreed, that seems the best way forward. I was a little worried that the -version text is long and complicated compared to other programs and -version might not work as expected on other X servers. -- 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: Triaged 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Summary changed: - xserver-allow-tcp features doesn't work with Xorg version 1.16.0 + xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 ** Also affects: lightdm (Ubuntu Wily) Importance: Medium Status: Triaged ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => High ** Also affects: lightdm Importance: Undecided Status: New ** Changed in: lightdm Status: New => Triaged ** Changed in: lightdm Importance: Undecided => High ** Changed in: lightdm (Ubuntu Wily) 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/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Vivid: Triaged Status in lightdm source package in Wily: Triaged Bug description: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver- command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the "xserver-allow-tcp=true" is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) ### i haven't /etc/lightdm/lightdm.conf when i tried to create it and write the lines above it was worse, my system didin't start. after a few experiment i have found something that works: i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf before it was: [SeatDefaults] # Dump core xserver-command=X -core now: [SeatDefaults] # Dump core xserver-command=X -core xserver-allow-tcp=true and it works! 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
I've patched the vivid / wily versions since we know that X.org 1.17 is used. We still need to decide how to fix this for the LightDM project in a generic way. ** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => Fix Committed ** Changed in: lightdm (Ubuntu Wily) Status: Triaged => Fix Committed -- 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: Triaged Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Committed 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Description changed: - In order to enable X11 forwarding from an external host you must - explicitly set the Xserver to listen by overriding the xserver-command. - Previously you could set the xserver-allow-tcp=true and it would do this - automatically. + [Impact] + xserver-allow-tcp=true option no longer works with X.org 1.17. - I would have expected this change in behaviour to show up in - README.Debian.gz but since it did not, perhaps the functionality of the - "xserver-allow-tcp=true" is not working as expected. + [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 - Below shows my before (no TCP listener on 6000) and after (TCP listener - on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. + Expected result: + Able to connect - Before (14.10): + Observed result: + Unable to connect - ~$ cat /etc/lightdm/lightdm.conf - - [SeatDefaults] - xserver-allow-tcp=true - - After (15.04): - - ~$ cat /etc/lightdm/lightdm.conf - - [SeatDefaults] - xserver-command=X -core -listen tcp - xserver-allow-tcp=true - - ProblemType: Bug - DistroRelease: Ubuntu 15.04 - Package: lightdm 1.14.0-0ubuntu2 - ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 - Uname: Linux 3.19.0-15-generic x86_64 - ApportVersion: 2.17.2-0ubuntu1 - Architecture: amd64 - CurrentDesktop: Unity - Date: Mon Apr 27 17:33:26 2015 - InstallationDate: Installed on 2014-12-18 (130 days ago) - InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) - LightdmConfig: - [SeatDefaults] - xserver-command=X -core -listen tcp - xserver-allow-tcp=true - SourcePackage: lightdm - UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) - - ### - i haven't /etc/lightdm/lightdm.conf - when i tried to create it and write the lines above it was worse, my system didin't start. - after a few experiment i have found something that works: - i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf - - before it was: - [SeatDefaults] - # Dump core - xserver-command=X -core - - now: - [SeatDefaults] - # Dump core - xserver-command=X -core - xserver-allow-tcp=true - - and it works! + [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. -- 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: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Vivid: Triaged Status in lightdm source package in Wily: Triaged 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 1244578] Re: lightdm-session runs xrdb with -nocpp option
** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- 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/1244578 Title: lightdm-session runs xrdb with -nocpp option Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Committed Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Utopic: Fix Committed Status in lightdm source package in Vivid: Fix Committed Bug description: [Impact] lightdm-session runs xrdb for .Xresources file with the -nocpp option (Line 37 and 43), which prevents the xrdb from preprocessing the .Xresources file. Many configurations like the popular solarized color theme (https://github.com/solarized/xresources/blob/master/solarized) use this and you find some complaints about in on the internet https://bbs.archlinux.org/viewtopic.php?id=164108 https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163129 http://superuser.com/questions/655857/urxvt-uses-pink-instead-of-solarized-until-i-run-xrdb-xresources/656213 I don't see a reason for not using the preprocessor and so did the editor of Xsession (the option is not used in /etc/X11/Xsession.d/30x11-common_xresources) [Test Case] - Install solarized theme https://github.com/solarized/xresources/blob/master/solarized - Load default Xresources file (xrdb < .XDefaults ) - Now every macro supported by CPP will not work. [Regression Potential] * No regression potential advised, small (0.001%) load average increase on startup time because of enabling Cpp. [Solution] Backport default wily session to older releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1244578/+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: apparmor rules too tight for chromium
** Also affects: chromium-browser (Ubuntu Wily) Importance: Undecided Status: Confirmed ** Also affects: lightdm (Ubuntu Wily) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Also affects: chromium-browser (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Trusty) 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/1504049 Title: apparmor rules too tight for chromium Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: New Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: New Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: New Bug description: Hi, when running chromium, I get lots of apparmor alerts and warnings, although actions seem to be legitimate and normal. Looks as if the apparmor ruleset is too tight. See attached logs. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 45.0.2454.101-0ubuntu1.1201 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DP.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.DP.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.DP.3: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.3: edid-base64: AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA== dpms: On modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Thu Oct 8 11:48:15 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2015-09-03 (34 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) InstalledPlugins: Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: N3150-NUC 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.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC: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. gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome
[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium
** Changed in: lightdm Importance: Undecided => Medium ** Changed in: lightdm Status: New => Fix Committed ** Changed in: lightdm Milestone: None => 1.17.0 -- 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: apparmor rules too tight for chromium Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: New Status in Light Display Manager 1.14 series: New Status in Light Display Manager 1.16 series: New Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: New Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: New Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: New Bug description: Hi, when running chromium, I get lots of apparmor alerts and warnings, although actions seem to be legitimate and normal. Looks as if the apparmor ruleset is too tight. See attached logs. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: chromium-browser 45.0.2454.101-0ubuntu1.1201 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DRM.card0.DP.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.DP.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.DP.3: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.2: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.3: edid-base64: AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA== dpms: On modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Thu Oct 8 11:48:15 2015 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2015-09-03 (34 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) InstalledPlugins: Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: N3150-NUC 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.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC: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. gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to:
