Re: [Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Will do, thanks.Michael Peek On Thu, 2020-08-20 at 15:10 +, Paride Legovini wrote: > Hi Michael and thanks for all the digging. If I understand > correctlythere are two issues here: > 1. The slapd crash due to the caseExactMatch/caseExactIA5Match typo, > forwhich you submitted a fix upstream [1]. > 2. The need to "start ; stop ; restart" the slapd service in order > toavoid the "invalid per syntax" errors. > What I suggest is to: > A. Let's wait for upstream to comment on or pickup your patch. > We'llthen be able to cherry-pick the fix from the upstream > repository. Thismakes things easier to manage and give us more > confidence on thecorrectness on the patch (could be obvious for a > ldap/autofs expert, Iam not.) > B. File a separate bug for the "start ; stop ; restart" thing, > whichappears to be unrelated. If you do so, please make it clear it's > aBionic -> Focal regression. Having a minimal steps to reproduce > theissue from a fresh Focal install would be the best. > What do you think? > Paride > [1] https://www.spinics.net/lists/autofs/msg02276.html > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: New Status in openldap package in Ubuntu: New Status in autofs package in Debian: Unknown Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+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 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
I didn't realize that this was considered unusual. AutoFs integration has been a critical part of our infrastructure across multiple departments at our university for decades, starting with NIS/NIS+. Without AutoFS integration we would be ... very, very sad. I have filed a bug report w/ Debian and included a patch against Debian Sid's autofs-5.1.6 source package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968675 Since this is the same source file as Ubuntu 20.04 uses I've included the patch file for your use, on the off chance that it would make things easier (attached). Looking at the up-stream source from https://mirrors.edge.kernel.org/pub/linux/daemons/autofs/v5/ it appears that version 5.1.2's autofs.schema file was correct. The typo first appears in 5.1.3, released in May 24th 2017, and has affected every release of autofs since. I have also submitted a bug report, including a patch file, to the aut...@vger.kernel.org mailing list for the autofs developers. Michael Peek On Tue, 2020-08-18 at 16:42 +, Robie Basak wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Since this affects an unusual end-user configuration, I'm setting > Importance to Low, and I don't expect anyone to work on this soon. > However if you can help definitively explain what needs adjusting to fix > this correctly, then that would be helpful and we can try to help get > that fix landed. Caveat: normally we'd expect an explanation and patch > to be sent to Debian first. > > I'm deferring a decision on whether or not this requires a fix in > openldap until the above is clear. > > ** Changed in: autofs (Ubuntu) >Importance: Undecided => Low > > ** Changed in: openldap (Ubuntu) >Importance: Undecided => Low > ** Bug watch added: Debian Bug tracker #968675 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968675 ** Patch added: "autofs-5.1.6-schema-fix.diff" https://bugs.launchpad.net/bugs/1891548/+attachment/5402829/+files/autofs-5.1.6-schema-fix.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: New Status in openldap package in Ubuntu: New Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
As a follow-up, I figured out a workaround for the following error that
I reported earlier:
adding new entry "ou=auto.master,dc=example,dc=org"ldap_add: Invalid
syntax (21) additional info: objectClass: value #1 invalid per
syntax
Original steps:
1) Install /etc/ldap/slapd.conf (which includes the "caseExactIA5Match"
fixed version of the autofs schema)
2) Start slapd
3) Attempts to enter an automountMap entry causes an invalid syntax
error
Workaround:
1) Install /etc/ldap/slapd.conf (which includes the "caseExactIA5Match"
fixed version of the autofs schema)
2) start slapd
3) stop and restart slapd again
4) Attempts to enter automountMap entry now succeed
Why this is necessary I can't say but the behavior is consistent. This
extra restart was not necessary for versions of slapd+autofs that
shipped with 18.04 and previous Ubuntu versions.
Also I'm going to further show my ignorance here and say that I found
"caseExactMatch" in several other schema files too. I'm wondering why
other users haven't run into something similar?
# find /etc/ldap/schema/ -type f -exec grep -q caseExactMatch {} \;
-print/etc/ldap/schema/corba.schema/etc/ldap/schema/duaconf.ldif/etc/ld
ap/schema/core.schema <-- commented
out/etc/ldap/schema/duaconf.schema/etc/ldap/schema/java.schema/etc/ldap
/schema/core.ldif <-- commented
out/etc/ldap/schema/java.ldif/etc/ldap/schema/autofs.schema
Thank you again for your help on this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1891548
Title:
autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Status in autofs package in Ubuntu:
New
Status in openldap package in Ubuntu:
New
Bug description:
Ubuntu Release:
# lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Version of packages in use:
# dpkg -l autofs autofs-ldap slapd | grep '^ii'
ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based
automounter for Linux
ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for
autofs
ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd)
Expected:
No errors from slaptest
Actual Output:
5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType
inappropriate matching rule: "caseExactMatch"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+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 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
SORRY -- This is the correct autofs-fixed.schema. That last one was a file I was poking around with using a schema I found online. The only difference between this file and the one that ships with autofs-ldap is "caseExactMatch" -> "caseExactIA5Match". ** Attachment added: "autofs-fixed.schema" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401483/+files/autofs-fixed.schema -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: New Status in openldap package in Ubuntu: New Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+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 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
** Attachment added: "Replaced "exactCaseMatch" w/ "exactCaseIA5Match" to fix bug that caused slapd to crash on startup" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401476/+files/autofs-fixed.schema -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: New Status in openldap package in Ubuntu: New Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+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 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Attached is an example /etc/ldap/slapd.conf file that I'm working from.
Maybe there's a problem in here somewhere that I'm not catching.
Including it just in case. Database password is "superSecretPassword"
-> "{MD5}Yy8s0xf5ONysHHbtpvA+ig==". The include for
/etc/ldap/schema/autofs.schema has been replaced with /etc/ldap/schema
/autofs-fixed.schema (see additional attachment below).
** Attachment added: "Example /etc/ldap/slapd.conf file -- aybe a problem in
here somewhere?"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401475/+files/slapd.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1891548
Title:
autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Status in autofs package in Ubuntu:
New
Status in openldap package in Ubuntu:
New
Bug description:
Ubuntu Release:
# lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Version of packages in use:
# dpkg -l autofs autofs-ldap slapd | grep '^ii'
ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based
automounter for Linux
ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for
autofs
ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd)
Expected:
No errors from slaptest
Actual Output:
5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType
inappropriate matching rule: "caseExactMatch"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+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 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
** Attachment added: "LDAP entries to recreate my test setup" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401474/+files/input.ldif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: New Status in openldap package in Ubuntu: New Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()
I have not come across this bug yet in 16.04. It may have been fixed. Michael On 10/26/2016 06:08 PM, Joshua Powers wrote: > ** Changed in: openssh (Ubuntu) >Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Status in openssh package in Ubuntu: Incomplete Bug description: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
*** This bug is a duplicate of bug 1003842 *** https://bugs.launchpad.net/bugs/1003842 I reformatted over 14.04 and installed 16.04 as a fresh start. I use a slightly customized server install ISO image that includes my own preseed file for automation. My approach is to start with a bare-bones server install on all machines and then install extra packages based on the machine's function (ubuntu-desktop on workstations, for instance). According to my installation logs, dnsmasq was installed during an "apt-get install ubuntu-desktop unity-tweak-tool" on a workstation (which of those two packages actually resulted in a dependency on dnsmasq I don't know), and on a server it was installed during an "apt-get install polipo". Michael On 04/28/2016 06:01 AM, Thomas Hood wrote: > *** This bug is a duplicate of bug 1003842 *** > https://bugs.launchpad.net/bugs/1003842 > > What remains unexplained is why the dnsmasq package was installed on > your machine at all. Is it the case that dnsmasq was not installed > before the upgrade and it was installed after the upgrade? In that case, > please file a new bug report describing that particular misbehavior. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in dnsmasq package in Ubuntu: Incomplete Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmasq is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmasq? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1575644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
I'll give it a go and see if any problems occur. Thanks for your help! Michael On 04/27/2016 03:21 PM, Thomas Hood wrote: > That name service does not work properly when dnsmasq is installed is > most probably due to bug #1003842. If that is the case then if you > remove 8.8.8.8 from the list of nameserver addresses then name service > will work reliably. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in resolvconf package in Ubuntu: Incomplete Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmasq is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmasq? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
No, it does not work when dnsmasq is installed. At least, not reliably. I discovered this when apache2 started ignoring the configuration for my virtual hosts because it couldn't resolve the virtual host names. I could reach some hosts, like archive.ubuntu.com for instance whenever I did an apt-get update, or I would have noticed it right away. Michael On 04/27/2016 01:59 PM, Thomas Hood wrote: > Everything looks correct. Does name service work both when dnsmasq is > installed and when it is not installed? If so then there is no problem. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in resolvconf package in Ubuntu: Incomplete Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmasq is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmasq? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
Ah, I understand now. Sorry. Michael On 04/27/2016 12:42 PM, Thomas Hood wrote: > The answer to the question "shouldn't those DNS servers should be > included in /etc/resolv.conf regardless of the presence of dnsmasq?" is > "no". Resolvconf doesn't list any nameserver addresses after any > loopback address, unless > TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no in > /etc/default/resolvconf. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in resolvconf package in Ubuntu: Incomplete Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmasq is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmasq? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
Maybe I'm just confused about how resolvconf and dnsmasq should work, but here's how it's working on my new 16.04 system: root@ecoli:~# dpkg -l | grep dnsmasq ii dnsmasq 2.75-1 all Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-base 2.75-1 amd64 Small caching DNS proxy and DHCP/TFTP server root@ecoli:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp0s10 iface enp0s10 inet static address 160.36.130.174 netmask 255.255.255.0 network 160.36.130.0 broadcast 160.36.130.255 gateway 160.36.130.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 160.36.0.66 160.36.128.66 8.8.8.8 dns-search nimbios.org root@ecoli:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search nimbios.org root@ecoli:~# dpkg --purge dnsmasq (Reading database ... 429253 files and directories currently installed.) Removing dnsmasq (2.75-1) ... Purging configuration files for dnsmasq (2.75-1) ... root@ecoli:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 160.36.0.66 nameserver 160.36.128.66 nameserver 8.8.8.8 search nimbios.org root@ecoli:~# dpkg -l | grep dnsmasq ii dnsmasq-base 2.75-1 amd64 Small caching DNS proxy and DHCP/TFTP server root@ecoli:~# apt-get install dnsmasq Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: dnsmasq 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/16.0 kB of archives. After this operation, 71.7 kB of additional disk space will be used. Selecting previously unselected package dnsmasq. (Reading database ... 429242 files and directories currently installed.) Preparing to unpack .../dnsmasq_2.75-1_all.deb ... Unpacking dnsmasq (2.75-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... Setting up dnsmasq (2.75-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... root@ecoli:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search nimbios.org root@ecoli:~# dpkg -l | grep dnsmasq ii dnsmasq 2.75-1 all Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-base 2.75-1 amd64 Small caching DNS proxy and DHCP/TFTP server root@ecoli:~# This is on a machine that was previously running 14.04, and now has a fresh re-formatted/re-installed 16.04. Under 14.04 this wasn't a problem. This just started under 16.04. And the contents of my /etc/network/interfaces hasn't changed from 14.04. Michael On 04/27/2016 12:21 PM, msp3k wrote: > They are specified in /etc/network/interfaces just as you instructed, > and the dnsmasq-base package is installed. But when dnsmasq is > installed then resolvconf generates an incorrect /etc/resolv.conf. If I > remove the dnsmasq package then resolvconf works properly and generates > the expected contents for /etc/resolv.conf. > > This is a new bug with 16.04. It was not present under 14.04, and the > contents of my /etc/network/interfaces file has not changed. > > Michael > > On 04/27/2016 12:06 PM, Thomas Hood wrote: >> Not dnsmasq but dnsmasq-base is pulled in by ubuntu-desktop. >> >> If you define your interfaces statically using /etc/network/interfaces >> then you have to add the nameserver information >> /etc/network/interfaces on lines like "dns-nameserver 1.2.3.4". See >> resolvconf(8) for more info. >> >> ** Changed in: resolvconf (Ubuntu) >> Status: New => Incomplete >> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in resolvconf package in Ubuntu: Incomplete Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), ap
Re: [Touch-packages] [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
They are specified in /etc/network/interfaces just as you instructed, and the dnsmasq-base package is installed. But when dnsmasq is installed then resolvconf generates an incorrect /etc/resolv.conf. If I remove the dnsmasq package then resolvconf works properly and generates the expected contents for /etc/resolv.conf. This is a new bug with 16.04. It was not present under 14.04, and the contents of my /etc/network/interfaces file has not changed. Michael On 04/27/2016 12:06 PM, Thomas Hood wrote: > Not dnsmasq but dnsmasq-base is pulled in by ubuntu-desktop. > > If you define your interfaces statically using /etc/network/interfaces > then you have to add the nameserver information > /etc/network/interfaces on lines like "dns-nameserver 1.2.3.4". See > resolvconf(8) for more info. > > ** Changed in: resolvconf (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in resolvconf package in Ubuntu: Incomplete Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmask is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmask? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+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 1575644] [NEW] resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
Public bug reported: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmask is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmask? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used Status in resolvconf package in Ubuntu: New Bug description: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmask is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmask? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+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 1555171] Re: systemd does not shut down rsyslog
Nevermind. Apparently "systemctl stop " doesn't do what I thought it should do. Rsyslogd can be stopped with: systemctl disable rsyslog systemctl stop rsyslog After issuing the disable command, the stop command worked as I expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog Status in rsyslog package in Ubuntu: New Bug description: This bug is 100% reproducible. Example output: Script started on Wed 09 Mar 2016 10:04:42 AM EST root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5219 1 0 10:04 ?00:00:00 /usr/sbin/rsyslogd -n root 5240 5227 0 10:04 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# systemctl stop rsyslog Warning: Stopping rsyslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop syslog Warning: Stopping syslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop rsyslogd Failed to stop rsyslogd.service: Unit rsyslogd.service not loaded. root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5254 1 0 10:05 ?00:00:00 /usr/sbin/rsyslogd -n root 5263 5227 0 10:05 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# exit Script done on Wed 09 Mar 2016 10:05:12 AM EST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1555171/+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 1555171] Re: systemd does not shut down rsyslog
This is on Ubuntu Server 16.04 beta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog Status in rsyslog package in Ubuntu: New Bug description: This bug is 100% reproducible. Example output: Script started on Wed 09 Mar 2016 10:04:42 AM EST root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5219 1 0 10:04 ?00:00:00 /usr/sbin/rsyslogd -n root 5240 5227 0 10:04 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# systemctl stop rsyslog Warning: Stopping rsyslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop syslog Warning: Stopping syslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop rsyslogd Failed to stop rsyslogd.service: Unit rsyslogd.service not loaded. root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5254 1 0 10:05 ?00:00:00 /usr/sbin/rsyslogd -n root 5263 5227 0 10:05 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# exit Script done on Wed 09 Mar 2016 10:05:12 AM EST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1555171/+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 1555171] [NEW] systemd does not shut down rsyslog
Public bug reported: This bug is 100% reproducible. Example output: Script started on Wed 09 Mar 2016 10:04:42 AM EST root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5219 1 0 10:04 ?00:00:00 /usr/sbin/rsyslogd -n root 5240 5227 0 10:04 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# systemctl stop rsyslog Warning: Stopping rsyslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop syslog Warning: Stopping syslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop rsyslogd Failed to stop rsyslogd.service: Unit rsyslogd.service not loaded. root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5254 1 0 10:05 ?00:00:00 /usr/sbin/rsyslogd -n root 5263 5227 0 10:05 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# exit Script done on Wed 09 Mar 2016 10:05:12 AM EST ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog Status in rsyslog package in Ubuntu: New Bug description: This bug is 100% reproducible. Example output: Script started on Wed 09 Mar 2016 10:04:42 AM EST root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5219 1 0 10:04 ?00:00:00 /usr/sbin/rsyslogd -n root 5240 5227 0 10:04 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# systemctl stop rsyslog Warning: Stopping rsyslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop syslog Warning: Stopping syslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop rsyslogd Failed to stop rsyslogd.service: Unit rsyslogd.service not loaded. root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5254 1 0 10:05 ?00:00:00 /usr/sbin/rsyslogd -n root 5263 5227 0 10:05 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# exit Script done on Wed 09 Mar 2016 10:05:12 AM EST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1555171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()
I tried following one of the links to ubuntu.com, but was told "Sorry, you are not a member of a group that is allowed to see the data from error reports." If you think it's safe to do so, I can reply with the last few links. Would it be safe to assume that they are listed in a newest-first order? Thanks, Michael On 01/05/2016 09:17 PM, Seth Arnold wrote: > It may not be making its way to errors.ubuntu.com. If you've got the GUI > installed, you can find a link to reported issues via the control panel, > security & privacy, diagnostics --> "show previous reports". I didn't > see any errors that matched _IO_vfprintf_internal(), though I did notice > that the pam_winbind module was segfaulting a lot for someone... > > Thanks > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Status in openssh package in Ubuntu: New Bug description: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+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 1530914] [NEW] sshd crashed with SIGSEGV in _IO_vfprintf_internal()
Public bug reported: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Status in openssh package in Ubuntu: New Bug description: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
My understanding is that if you type: dpkg -l unity And see the version number 7.2.x, then you have the patch. Michael Peek On 03/18/2015 05:11 AM, Jonathan Laserson wrote: How do I obtain the fix? This still happens. I have Ubuntu 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
On 12/10/2014 09:24 PM, Andrea Azzarone wrote: Please consider answering the question markes ad *** IMPORTANT *** in the description. 2014-12-11 1:26 GMT+01:00 harrychillboy 1311...@bugs.launchpad.net: Bug description: *** IMPORTANT ** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** 1. Yes. Dual monitors. 2. No. The problem is random. 3. Yes. We have just switched to gnome-screensaver for testing purposes. Initial tests look promising. 4. Included auth.log entries in a previous message 5. unity7.2.3+14.04.20140826-0ubuntu1 Michael Peek -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
1) The bug just bit my boss again. Here's the auth.log: Dec 10 09:13:23 anolis compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 10 09:13:23 anolis compiz: PAM adding faulty module: pam_kwallet.so Dec 10 09:15:01 anolis CRON[21745]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 10 09:15:01 anolis CRON[21744]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 10 09:15:01 anolis CRON[21744]: pam_unix(cron:session): session closed for user root Dec 10 09:15:03 anolis CRON[21745]: pam_unix(cron:session): session closed for user root Dec 10 09:20:42 anolis sshd[21993]: Accepted publickey for root from 160.36.130.180 port 33420 ssh2: RSA fe:34:35:5b:47:90:1b:7f:fb:cb:7d:5c:2e:32:69:f5 Dec 10 09:20:42 anolis sshd[21993]: pam_unix(sshd:session): session opened for user root by (uid=0) Dec 10 09:20:56 anolis compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 10 09:20:56 anolis compiz: PAM adding faulty module: pam_kwallet.so Dec 10 09:21:01 anolis CRON[22258]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 10 09:21:03 anolis CRON[22258]: pam_unix(cron:session): session closed for user root Dec 10 09:22:02 anolis sshd[22333]: Accepted publickey for root from 160.36.130.180 port 33431 ssh2: RSA fe:34:35:5b:47:90:1b:7f:fb:cb:7d:5c:2e:32:69:f5 Dec 10 09:22:02 anolis sshd[22333]: pam_unix(sshd:session): session opened for user root by (uid=0) There's nothing out of the ordinary here compared to my other hosts. There's a mysterious complaint about pam_kwallet.so, but all of my hosts complain about that. 2) There is something new to note: When the bug bites, not only is there no password field, but the indicator apps also disappear from the top-right of the screen. I noticed this when I tried to switch to another user in hopes of being able to log back in. Attached is a screenshot I grabbed via vinagre. 3) I set System Settings Universal Access Typing On Screen Keyboard = On We'll see if the problem persists when using gnome-screensaver. Michael Peek On 11/23/2014 08:40 AM, Andrea Azzarone wrote: Can you post your auth.log? ** Attachment added: Screenshot from 2014-12-10 09:21:32.png https://bugs.launchpad.net/bugs/1311316/+attachment/4277621/+files/Screenshot%20from%202014-12-10%2009%3A21%3A32.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
1) Maybe I'm just derping, but how do I run gnome-screensaver? $ ps -ef | grep -i screensaver peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver $ gnome-screensaver ** (gnome-screensaver:24665): WARNING **: screensaver already running in this session 2) If this is an LDAP issue, then why does it only affect 1 out of my 110 users? I thank you guys for your hard work on this, and if there is anything I can do to help track down the source of the problem let me know. Michael Peek On 12/08/2014 01:57 PM, Andrea Azzarone wrote: All these services (login, lightdm, polkit-1, sudo, sshd) are working fine. They run as root that's why. Try to lock using gnome-screensaver (without running it as root!) and let me know if you can unlock the screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Okay, I set System Settings Universal Access Typing On Screen Keyboard = On Then I hit alt+control+L to lock. Sure enough, I got what looks like gnome-screensaver. Via an SSH login I confirmed that gnome-screensaver was indeed running, and running as me and not as root. Entering my password returned me to the desktop with no problem. I repeated the lock test four times. I'll ask my boss to make the same settings change and let me know if/how that changes things for him, and pass the results on to you guys. Michael Peek On 12/09/2014 09:28 AM, Andrea Azzarone wrote: You need to enable accessibility (e.g. on screen keyabord) from the control center. 2014-12-09 14:56 GMT+01:00 msp3k p...@nimbios.org: 1) Maybe I'm just derping, but how do I run gnome-screensaver? $ ps -ef | grep -i screensaver peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver $ gnome-screensaver ** (gnome-screensaver:24665): WARNING **: screensaver already running in this session 2) If this is an LDAP issue, then why does it only affect 1 out of my 110 users? I thank you guys for your hard work on this, and if there is anything I can do to help track down the source of the problem let me know. Michael Peek On 12/08/2014 01:57 PM, Andrea Azzarone wrote: All these services (login, lightdm, polkit-1, sudo, sshd) are working fine. They run as root that's why. Try to lock using gnome-screensaver (without running it as root!) and let me know if you can unlock the screen. -- You received this bug notification because you are a bug assignee. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I must have missed something. Permissions on what path? And what should the permissions be? Michael Peek On 12/06/2014 09:03 AM, Andrea Azzarone wrote: We released a fix but it does not work. The one we released was about text entry not showing randomly on multimonitor and seems to be fixed. Probably what you can reproduce now is a problem with permissions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I am using ldap as well. Out of 80 hosts and 110 users this bug only affects one user on one host. (Unfortunately that user happens to be one of my bosses.) It's irregular, but frequent. Michael Peek On 12/05/2014 09:06 AM, Andrea Azzarone wrote: @Philipp also I just read you are using ldap. That can be a different issue (maybe is solved in trunk because now unity and lightdm do not share pam configuration). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Light-locker is not installed on our machines. On 12/01/2014 10:56 AM, LGB [Gábor Lénárt] wrote: I don't know if it helps, but I always had problems like no input field for password or the double unlock (if the first problem does not occur, unlock presented another unlock field with a sightly different screen) problem on my notebook. Then I noticed, I have a package installed named light-locker (I am not sure about the name though, just by heart now). After removing that package I had no problem like these since then! Since I've installed meta-packages xubuntu-desktop and lubuntu-desktop as well (so I can test different desktops) it can be a reason as (if I am correct) these packages depends on light-locker. Removing them caused those meta packages to be removed as well (again, if I remember well enough), but at least since then I have no problem with regular ubuntu (unity) desktop lockingunlocking. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Out of 90-somethign users this bug only seems to affect one user. (Of course, that user happens to be one of my bosses...) Because the problem is hard to reproduce I have a feeling that it'lll be difficult to track down and fix. Michael On 11/03/2014 05:18 PM, Bruce MacNaughton wrote: msp3k - I got the same thing but just ran unity --replace in a terminal window I had left open on the desktop. I didn't check to see if could open a terminal. But running unity --replace from the desktop (w/o dash, launcher, panel, menu bar, etc.) resulted in getting them all back. It was ugly - many errors but it worked. Everything seems fine afterwards. Any idea when I can specifically target the software for an update? The fix clearly hasn't hit me yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I would like to know the answer to that as well. Back in the good 'ol days the screen lock was a separate process, and pkill -9 gnome-screensaver would bring back the desktop. But now...? There is a process called /usr/lib/unity/unity-panel-service --lockscreen-mode, but if I kill -9 on it, it just comes back with a new PID. Michael On 11/03/2014 08:38 AM, Bruce MacNaughton wrote: I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
When I do that, I get the desktop back, but no dash, launcher, or panel. On 11/03/2014 08:54 AM, Erik wrote: unity --replace On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton bmacnaugh...@msn.com wrote: I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1358745] [NEW] Screen lock has no place to type in a password
Public bug reported: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: A screenshot snippet showing the bug biting https://bugs.launchpad.net/bugs/1358745/+attachment/4181575/+files/ligthdm-screenlock-password-bug.png -- 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/1358745 Title: Screen lock has no place to type in a password Status in “lightdm” package in Ubuntu: New Bug description: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1358745/+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
