[Bug 1823110] [NEW] Screen not resized when rotating 90*
Public bug reported: Running 19.04 beta on a Microsoft Surface Pro 3. Screen resolution 2160x1440 works in normal landscape mode (Docked mode) however if I rotate the device 90* clockwise or counter-clockwise, the screen resolution doesn't change to 1440x2160. The screen actually rotates however it hasn't flipped the dimensions to fit. This was previously working on Ubuntu 18.10. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: disco ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823110 Title: Screen not resized when rotating 90* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1823110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Andreas, As per comment #25, I've added the absolute path to auto.DataVol1 in /etc/auto.master as I can confirm it working. With you comment on having: automount: sss [NOTFOUND=continue] files as part of /etc/nsswitch.conf, I suggest that to not break people's existing configs, that this may be a default for the the package developers for all the relevant switch options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD
Additional points: * Able to always reproduce * Able to manually mount volumes (doing so as temp workaround) dpkg -l sssd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii sssd 2.3.1-2 amd64System Security Services Daemon -- metapackage root@ROC-Cube:~# dpkg -l autofs Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--== ii autofs 5.1.6-3ubuntu1 amd64kernel-based automounter for Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] [NEW] Automount fails due to SSSD config (Groovy Gorilla)
Public bug reported: Using the same automount config from 20.04, Groovy Gorilla fails to automount mount points with SSD errors such as the following: -From journalctl -xe: Sep 25 04:04:43 ROC-Cube systemd[1]: Stopping Automounts filesystems on demand... ░░ Subject: A stop job for unit autofs.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A stop job for unit autofs.service has begun execution. ░░ ░░ The job identifier is 8075. Sep 25 04:04:43 ROC-Cube automount[1838]: umount_autofs_indirect: ask umount returned busy /mnt/GGData Sep 25 04:04:44 ROC-Cube systemd[1]: autofs.service: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit autofs.service has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube systemd[1]: Stopped Automounts filesystems on demand. ░░ Subject: A stop job for unit autofs.service has finished ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A stop job for unit autofs.service has finished. ░░ ░░ The job identifier is 8075 and the job result is done. Sep 25 04:04:44 ROC-Cube systemd[1]: Starting Automounts filesystems on demand... ░░ Subject: A start job for unit autofs.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit autofs.service has begun execution. ░░ ░░ The job identifier is 8075. Sep 25 04:04:44 ROC-Cube automount[13523]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:04:44 ROC-Cube systemd[1]: tmp-auto8NobgK.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit tmp-auto8NobgK.mount has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube automount[13523]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:04:44 ROC-Cube systemd[2685]: tmp-autoxIakpM.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit UNIT has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube systemd[1]: tmp-autoxIakpM.mount: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit tmp-autoxIakpM.mount has successfully entered the 'dead' state. Sep 25 04:04:44 ROC-Cube systemd[1]: Started Automounts filesystems on demand. ░░ Subject: A start job for unit autofs.service has finished successfully ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit autofs.service has finished successfully. ░░ ░░ The job identifier is 8075. >From tail /var/log/syslog: Sep 25 04:13:38 ROC-Cube automount[13523]: umount_autofs_indirect: ask umount returned busy /mnt/GGData Sep 25 04:13:40 ROC-Cube systemd[1]: autofs.service: Succeeded. Sep 25 04:13:40 ROC-Cube systemd[1]: Stopped Automounts filesystems on demand. Sep 25 04:13:40 ROC-Cube systemd[1]: Starting Automounts filesystems on demand... Sep 25 04:13:40 ROC-Cube automount[15237]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:13:40 ROC-Cube systemd[2685]: tmp-autonc2nfm.mount: Succeeded. Sep 25 04:13:40 ROC-Cube automount[15237]: setautomntent: lookup(sss): setautomntent: No such file or directory Sep 25 04:13:40 ROC-Cube systemd[1]: tmp-autonc2nfm.mount: Succeeded. Sep 25 04:13:40 ROC-Cube systemd[1]: Started Automounts filesystems on demand. Sep 25 04:13:40 ROC-Cube systemd[2685]: tmp-autopnDion.mount: Succeeded. >From auto.DataVol1: root@ROC-Cube:~# cat /etc/auto.DataVol1 #/mnt/GGData-fstype=nfs 10.0.0.13:/GGData Tracktion -fstype=nfs 10.0.0.13:/GGData/Tracktion C64 -fstype=nfs 10.0.0.13:/GGData/C64 Development -fstype=nfs 10.0.0.13:/GGData/Development Retro -fstype=nfs 10.0.0.13:/GGData/Retro Inkscape-fstype=nfs 10.0.0.13:/GGData/Inkscape >From /etc/auto.master: /mnt/GGData auto.DataVol1 --ghost ** Affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Trying to restart SSSD give the following errors with journlctl -xe: The job identifier is 11972 and the job result is failed. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD Sudo Service responder socket. ░░ Subject: A start job for unit sssd-sudo.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-sudo.socket has finished with a failure. ░░ ░░ The job identifier is 12071 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD AutoFS Service responder socket. ░░ Subject: A start job for unit sssd-autofs.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-autofs.socket has finished with a failure. ░░ ░░ The job identifier is 11968 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder socket. ░░ Subject: A start job for unit sssd-pam.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-pam.socket has finished with a failure. ░░ ░░ The job identifier is 12073 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder private socket. ░░ Subject: A start job for unit sssd-pam-priv.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-pam-priv.socket has finished with a failure. ░░ ░░ The job identifier is 12074 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD SSH Service responder socket. ░░ Subject: A start job for unit sssd-ssh.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-ssh.socket has finished with a failure. ░░ ░░ The job identifier is 12070 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD PAC Service responder socket. ░░ Subject: A start job for unit sssd-pac.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-pac.socket has finished with a failure. ░░ ░░ The job identifier is 12075 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'. Sep 25 04:22:56 ROC-Cube systemd[1]: Dependency failed for SSSD NSS Service responder socket. ░░ Subject: A start job for unit sssd-nss.socket has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit sssd-nss.socket has finished with a failure. ░░ ░░ The job identifier is 12069 and the job result is dependency. Sep 25 04:22:56 ROC-Cube systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'. And syslog: root@ROC-Cube:~# tail /var/log/syslog Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD PAM Service responder private socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD SSH Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD PAC Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'. Sep 25 04:24:47 ROC-Cube systemd[1]: Dependency failed for SSSD NSS Service responder socket. Sep 25 04:24:47 ROC-Cube systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'. ** Summary changed: - Automount fails due to SSSD + Automount fails due to SSSD config (Groovy Gorilla) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bu
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
I never looked at SSD closely prior to upgrading from 20.04 to 20.10 so I don't know what was there before as it 'just worked'. Presently though, the only thing under /etc/sssd is an empty conf.d (/etc/sssd/conf.d) directory. I did reinstall the SSSD packages after upgrade to 20.10 however the /etc/sssd directory didn't change from being empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Nope, there's no files under /etc/sssd and I didn't touch this directory when upgrading to the Groovy daily image. When I have a moment, I'll install 20.04 in a VM for a comparison of what should be in /etc/sssd But as far as /etc/nsswitch.conf goes: # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: files systemd sss group: files systemd sss shadow: files sss gshadow:files hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines networks: files protocols: db files services: db files sss ethers: db files rpc:db files netgroup: nis sss sudoers:files sss automount: sss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
I installed 20.04 fresh in a Gnome Boxes VM and installed autofs (sudo apt-get install autofs). SSSD was not installed as a dependancy. Then, I installed SSSD (sudo apt-get install sssd) just to see what /etc/sssd looked like and it's actually the same. there's no config file under /etc/sssd and and empty /etc/sssd/conf.d directory I executed a systemctl start sssd and it threw the same errors. I didn't have autofs configured and did not try to start autofs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
After doing a fresh install of 20.04 in a VM and then installing autofs, I've concluded that SSSD isn't needed for my setup. This does leave the question why SSSD was installed and if it was installed upon upgrade to Groovy. Either way, it seems that when SSSD is installed (either on 20.04 or 20.10), SSSD doesn't come with a working config under /etc/sssd On my install of Groovy, I removed SSSD and now my automounts are working correctly. Should SSSD have a default working config under /etc/sssd when its packages are installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Understood. I guess the last thing I can do here is take the 20.04 VM I've made and upgrade it to Groovy to see if SSSD is installed as a dependancy of something else. I'll do that over the next day or two. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
I wouldn't suggest that SSSD has anything done particularly for AutoFS but I would make a case for the package maintainers having a default /etc/sssd config file(s) that if nothing else has options commented/hashed out and ready ti be uncommented and used. This would be much like how *insert your favourite packge here* have a long list of commented options. Grnted, this isn't a serious issue, rather, a small quality of life improvement. :) Oh, one last point. If SSSD comes unconfigured and there unused 'out of the box', should another (meta)package have SSSD dependancy in the first place? (Ref: Timo comment #11) Your thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Same here aas in comment #15. I didn't have SSSD installed prior to the upgrade and it was "ubuntu-desktop-minimal" that pulled SSSD in. Not only did it break my automount but also login and sudo would take about a 4 seconds delay to succeed - as I guess it was trying to auth via SSS. Grepped from the update log: apt.log: Installing sssd as Recommends of ubuntu-desktop-minimal apt.log:MarkInstall sssd:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log:Installing python3-sss as Depends of sssd apt.log: MarkInstall python3-sss:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log:Installing sssd-ad as Depends of sssd apt.log: MarkInstall sssd-ad:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log: Installing libsss-idmap0 as Depends of sssd-ad apt.log:MarkInstall libsss-idmap0:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing sssd-ad-common as Depends of sssd-ad apt.log:MarkInstall sssd-ad-common:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log:Installing sssd-common as Depends of sssd-ad-common apt.log: MarkInstall sssd-common:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log: Installing libc-ares2 as Depends of sssd-common apt.log: Installing libdhash1 as Depends of sssd-common apt.log: Installing libini-config5 as Depends of sssd-common apt.log: Installing libsss-certmap0 as Depends of sssd-common apt.log:MarkInstall libsss-certmap0:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing libsss-nss-idmap0 as Depends of sssd-common apt.log:MarkInstall libsss-nss-idmap0:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing libnss-sss as Recommends of sssd-common apt.log:MarkInstall libnss-sss:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing libpam-sss as Recommends of sssd-common apt.log:MarkInstall libpam-sss:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log:Installing libpam-pwquality as Depends of libpam-sss apt.log: Installing libsss-sudo as Recommends of sssd-common apt.log:MarkInstall libsss-sudo:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: Installing sssd-krb5-common as Depends of sssd-ad apt.log:MarkInstall sssd-krb5-common:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log:Installing sssd-ipa as Depends of sssd apt.log: MarkInstall sssd-ipa:amd64 < none -> 2.3.1-2 @un uN Ib > FU=0 apt.log: Installing libipa-hbac0 as Depends of sssd-ipa apt.log:Installing sssd-krb5 as Depends of sssd apt.log: MarkInstall sssd-krb5:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log:Installing sssd-ldap as Depends of sssd apt.log: MarkInstall sssd-ldap:amd64 < none -> 2.3.1-2 @un uN IPb > FU=0 apt.log: Installing ldap-utils as Recommends of sssd-ldap apt.log:Installing sssd-proxy as Depends of sssd apt.log: MarkInstall sssd-proxy:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: new important dependency: sssd-tools:amd64 apt.log: Installing sssd-tools as Recommends of ubuntu-desktop-minimal apt.log:MarkInstall sssd-tools:amd64 < none -> 2.3.1-2 @un uN IPb > FU=0 apt.log:Installing sssd-dbus as Recommends of sssd-tools apt.log: MarkInstall sssd-dbus:amd64 < none -> 2.3.1-2 @un uN > FU=0 apt.log: new important dependency: sssd:amd64 apt.log: Installing sssd as Recommends of ubuntu-desktop-minimal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Hi, Well this explains why this is starting to happen: https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/390221 They're adding Active Directory to the new user creation in the installer. There's also a design doc that explicitly mentions SSSD: https://docs.google.com/document/d/1_KEGJa2-ka1oNCzMvLlQg9rNW9JESzHAcgqrjP3DkW4/edit?ts=5f561950# SHame is going to break other set-ups along the way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897153] Re: Automount fails due to SSSD config (Groovy Gorilla)
Hi, Sorry for the delay in getting back to you. As mentioned, adding the absolut path to my auto.DataVol1 file has fixed the issue for me. I think it would be preferably to add files to nsswitch.conf rather than looking for conf entries in /etc/sssd. For me, the only thing inside /etc/sssd is a /etc/sssd/conf.d directory. Both /etc/sssd & /etc/sssd/conf.d have no configuration files. I susptect that if I were to set-up the new Active Directory login, that /etc/sssd would be populated with the appropriate .conf files however I still suggest just adding a fallback to msswitch would be less invasive. G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897153 Title: Automount fails due to SSSD config (Groovy Gorilla) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250440] Re: bbswitch-dkms 0.7-2: bbswitch kernel module failed to build
Hi, I've removed 3.12.0-031200-generic and that fixed the issue. I then went on to do a clean install just for the peace-of-mind that my system doesn't have any left-overs from all the up/cross-grading of packages in my attempt to stabilse things. Now on a fresh install and I am still seeing this in DMESG: [ 1696.035720] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035757] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035795] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035832] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035870] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035907] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035945] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.035982] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 1696.036020] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) I still get some odd ubuntu crash-handler dialogue box pop up when I log in. They normally have something to do with xorg. I cancel these and the system "seems" fine. I'm mentioning this just in case. Cheers, G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250440 Title: bbswitch-dkms 0.7-2: bbswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1250440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714504] Re: App indicator is not always displayed
I can confirm that removing the extraneous Indicator packages does the job. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714504 Title: App indicator is not always displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1714504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714504] Re: App indicator is not always displayed
The same is happening for me with the Synology Cloudstation Client and additionally, Cadence, the Jackd manager app. Also only happening under X and not Wayland. This was actually working before Ubuntu got it's hands on it so it was a recent update. The version on Gnome Extensions I assume has had the same patches applied as it is not displaying icons now either. It stopped working two updates ago. Happens at log-in. But to add a twist to the plot, I have the exact same behaviour with Ubuntu 17.04 running Unity 7! I would have missing app-icons under X but they would display fine under Wayland. Yet still, with this current version of the problem, it only started happening in the past month. Therefore, I put it to you that the issue is not so much with this package but potentially a patch in X that was recently applied. Probably the same patch they used in the previous version of Ubuntu at some point. Likely to be an Ubuntu customisation of X rather than the appindicator package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714504 Title: App indicator is not always displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1714504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714504] Re: App indicator is not always displayed
Since it works under Wayland and not under X, should this be tagged Xorg rather than Wayland? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714504 Title: App indicator is not always displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1714504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450562] [NEW] libdrm-intel1 2.4.60 breaks Valvle/Steam games
Public bug reported: Referring to this bug: https://github.com/ValveSoftware/steam-for- linux/issues/3506 The only option to get games working again is to take the libdrm-intel 2.4.56 lib files from the .deb and copy them to your local steam install as an override for 2.4.60 system lib. ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450562 Title: libdrm-intel1 2.4.60 breaks Valvle/Steam games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1450562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Since updating this morning, my Trusty install is now showing:
Apr 4 17:03:26 Gavin dbus[848]: [system] Activated service
'org.freedesktop.login1' failed: Cannot launch daemon, file not found or
permissions invalid
libpam-systemd-204-5ubuntu16
Also can't mount external drives and anything else that depends on
policykit. Can unlock admin under settings either although I am in the
'adm' group.
For example, trying to run update-manager yields:
org.freedesktop.PolicyKit.Error.Failed: ('system-bus-name', {'name':
':1.178'}): org.debian.apt.update-cache
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295521
Title:
Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to
break
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
I was indeed suffering from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264 They have patched systemd-services and things are working again for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302264] Re: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL
I can confirm that the fix is working for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302264 Title: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028806] Re: 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver)
I have the exact same hardware as the OP and the same symptoms. Is there any information I can submit to progress this bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028806 Title: 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1028806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039143] Re: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected
This bug has a lot of information in it and it is still marked as incomplete. I am happy to help contribute information to progress this report. Just let me know what information is required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039143 Title: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039143] Re: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected
@Joseph S, I'm installaing 3.7.0-7.15 (https://launchpad.net/~francisbrwn9/+archive/kernels/+build/4065747) in an effort to solve another problem so I will let you know how this Kernel goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039143 Title: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039143] Re: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected
Errata: Wrong Kernel link. It should be https://launchpad.net/~xorg- edgers/+archive/ppa/+build/4065823. It's the Kernel that is part of xorg-edgers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039143 Title: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039143] Re: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected
@Joseph, Well there's no difference by using the xorg-edgers Kernel: Dec 17 04:32:54 gavin-N53SV kernel: [ 39.407752] usb 3-4: new full-speed USB device number 3 using xhci_hcd Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426452] usb 3-4: New USB device found, idVendor=046d, idProduct=c52b Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426460] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426463] usb 3-4: Product: USB Receiver Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426466] usb 3-4: Manufacturer: Logitech Dec 17 04:32:54 gavin-N53SV mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:14.0/usb3/3-4" Dec 17 04:32:54 gavin-N53SV mtp-probe: bus: 3, device: 3 was not an MTP device Dec 17 04:32:54 gavin-N53SV kernel: [ 39.431715] logitech-djreceiver 0003:046D:C52B.0006: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-4/input2 Dec 17 04:32:54 gavin-N53SV kernel: [ 39.431975] logitech-djreceiver 0003:046D:C52B.0006: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32 Dec 17 04:32:54 gavin-N53SV kernel: [ 39.432184] logitech-djreceiver: probe of 0003:046D:C52B.0006 failed with error -32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039143 Title: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039143] Re: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected
@Joseph, Ok, I've now installed the Kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.7-raring/ and I am still getting the exact same error messages. The device will always work if I hotplug once booted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039143 Title: 046d:c52b USB3 port Logitech mouse using unifying receiver not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028806] Re: 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver)
I'm installaing 3.7.0-7.15 (https://launchpad.net/~xorg- edgers/+archive/ppa/+build/4065823) in an effort to solve another problem so I will let you know how this Kernel goes. It's the Kernel that is part of xorg-edgers. Well there's no difference by using the xorg-edgers Kernel: Dec 17 04:32:54 gavin-N53SV kernel: [ 39.407752] usb 3-4: new full-speed USB device number 3 using xhci_hcd Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426452] usb 3-4: New USB device found, idVendor=046d, idProduct=c52b Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426460] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426463] usb 3-4: Product: USB Receiver Dec 17 04:32:54 gavin-N53SV kernel: [ 39.426466] usb 3-4: Manufacturer: Logitech Dec 17 04:32:54 gavin-N53SV mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:14.0/usb3/3-4" Dec 17 04:32:54 gavin-N53SV mtp-probe: bus: 3, device: 3 was not an MTP device Dec 17 04:32:54 gavin-N53SV kernel: [ 39.431715] logitech-djreceiver 0003:046D:C52B.0006: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-4/input2 Dec 17 04:32:54 gavin-N53SV kernel: [ 39.431975] logitech-djreceiver 0003:046D:C52B.0006: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32 Dec 17 04:32:54 gavin-N53SV kernel: [ 39.432184] logitech-djreceiver: probe of 0003:046D:C52B.0006 failed with error -32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028806 Title: 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1028806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028806] Re: 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver)
Ok, I've now installed the Kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.7-raring/ and I am still getting the exact same error messages. The device will always work if I hotplug once booted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028806 Title: 046d:c52b Cannot use logitech mouse M324 (Unifying Receiver) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1028806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
@Daniel (internalkernel) Just confirming so it isn't lost in the midst, you changed 'exec lightdm' to 'exec lightdm -d' and now you are getting Lightdm performing correctly each time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
@Pieter I agree, it is not a fix (well, a permanent and proper one anyway) but it does suggest that it's a race condition and that it is in the Binary itself and not the /etc/init/lightdm script as some of the other potential "fixes" have tried to remedy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
@Clint I'm happy to participate in collecting the data on a quiet day over the Christmas break when I don't really need to use my computer for any real activity. Are you talking about a debug-level log of X or something similar? Tell me what you would like to see and I'll strip the '-d' from the 'exec lightdm -d' line of /etc/init/lightdm and set other X switches or what ever may be required for that level of information. Do you just want the standard logs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
I thought I'd try stripping the config back to the original without the '-d' in the 'exec lightdm -d' line and after six reboots, not one failure. I'll leave the config in its original state now and if/when the symptoms reappear, I'll grab all the logs and post them up here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
We need to get this bug assigned and marked with priority. This problem when in the hands of a non-technical Ubuntu user will not go to and TTY to run 'sudo lightdm'. A non-technical user would just say that its broken and install another OS. This bug is going to cause customer attrition if it isnt addressed. How can we push this along? More info? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Actually, manually running "sudo lightdm" does no always work for me either. I'm starting to wnder if this is fixable by modifying the init scripts or whether the problem is deeper in LightDM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
In the /etc/init/lightdm.conf I've changed exec lightdm to exec lightdm -d as a way to catch some extra debugging information in the lightdm log file and lo, now it never fails. Hmmm, I wonder if writing debug information as slowed things down just enough to avoid a race condition inside the lightdm binary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066410] Re: lightdm doesn't load correctly on Ubuntu 12.10
It certainly looking like some kind of race condition when SSDs are involved. Adding a "sleep x" command doesn't help no matter how many seconds I tell it to sleep for. Also starting lightdm manually (instead of using the init script) more often fails than succeeds. This confirms for me that it isn't just a script problem, rather, it looks as if it is somewhere in the Xorg binaries or a deeper script somewhere I suppose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066410 Title: lightdm doesn't load correctly on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066410] Re: lightdm doesn't load correctly on Ubuntu 12.10
After a surprising 5 successful restarts with 'sleep 6' added into /etc/init/lighdm.conf file, I thought that some recent updates might have fixed it. I've kept an eye on the updates that were being applied and they don't look to be related but hey, the proof was in the pudding - five successful restarts. I then commented out the 'sleep 6' and Lightdm is back to being a recalcitrant and not starting. Adding 'sleep 6' back in got it going again. I suspect that after my hybrid HDD starts caching again that it will break due to some race condition. For me previously, it sometime wont even start when I execute 'sudo lightdm' from the command-line. When it fails after trying to manually start it, I have a series of about 20 "Error writing to daemon: Broken pipe" messages appear on the console. I've attached my /var/log/lightdm/x-0-greeter.log file. It looks as if the broken pipe message may have some relationship to DBUS. ** Attachment added: "Errors in x-0-greeter.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+attachment/3439688/+files/x-0-greeter.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066410 Title: lightdm doesn't load correctly on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066410] Re: lightdm doesn't load correctly on Ubuntu 12.10
Ok all, I've done some digging around it Lightdm is trying to start before UDEV reports the graphics devices as being ready. Please see #969489 By adding 'and stopped udevtrigger to lightdm.conf has fixed the issue for me. /etc/init/lightdm.conf: start on ((filesystem and runlevel [!06] and started dbus #Added the following line and stopped udevtrigger and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or stopped udev-fallback-graphics)) or runlevel PREVLEVEL=S) There is opinion that UDEV needs the full path to 'card0' but I suggest that for those with more than one graphics card (eg. Optimus) that a race condition could happen if your nVidia appears first. I don't know yet if this is possible though, someone with a better understanding than me of UDEV would have to comment on that. Either way, I'm inclined to mark this ticket as a duplicate of #969489 as it is an older ticket with more substance. This ticket has a lot more heat so can I suggest that you all head over to the other ticket and mark it as affecting you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066410 Title: lightdm doesn't load correctly on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
All, There is a lot more heat in #1066410 but not as much progress as I've seen here. I've suggested that #1066410 is marked as a duplicate of this ticket and those people come here and mark it as affecting them also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
I've tried adding "and stopped udevtrigger" and "sleep x" and both work more often than not but it is still unreliable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
I've installed Evolution 3.44.1-0ubuntu1 from the proposed updates and text now displays background as expected. This is resolved for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
I'm also having this with Jammy. I am using Wayland with the AMD opensource GPU drivers. The following appears in syslog: Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677203] evolution[23936]: segfault at 0 ip 7fef9c195536 sp 7ffe2be1cf88 error 4 in libwebkit2gtk-4.0.so.37.56.4[7fef9bc43000+2739000] Apr 19 15:45:56 ROC-Cube kernel: [ 1629.677216] Code: 89 e7 ff d3 eb d2 e8 c9 e2 ab ff 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 8b 47 28 48 8d 15 c1 2a 00 00 48 8b b8 a8 01 00 00 <48> 8b 07 48 8b 40 30 48 39 d0 75 06 31 c0 c3 0f 1f 00 ff e0 66 0f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Actually, a correction. Evolution starts fine but if I go to type an email (or reply) the editor window is blank. Closing the new or reply message window THEN crashes Evolution. ** Attachment added: "image832.png" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+attachment/5581390/+files/image832.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Attached crash file. ** Attachment added: "_usr_bin_evolution.1000.crash" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+attachment/5581391/+files/_usr_bin_evolution.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Apr 19 16:00:48 ROC-Cube systemd[4105]: app-gnome-org.inkscape.Inkscape-29481.scope: Consumed 25.374s CPU time. Apr 19 16:00:51 ROC-Cube kernel: [ 2524.702434] evolution[28125]: segfault at 0 ip 7f6cf7dc4536 sp 7ffc3fc482e8 error 4 in libwebkit2gtk-4.0.so.37.56.4[7f6cf7872000+2739000] Apr 19 16:00:51 ROC-Cube kernel: [ 2524.702443] Code: 89 e7 ff d3 eb d2 e8 c9 e2 ab ff 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 8b 47 28 48 8d 15 c1 2a 00 00 48 8b b8 a8 01 00 00 <48> 8b 07 48 8b 40 30 48 39 d0 75 06 31 c0 c3 0f 1f 00 ff e0 66 0f Apr 19 16:00:51 ROC-Cube systemd[1]: Starting Process error reports when automatic reporting is enabled... Apr 19 16:00:51 ROC-Cube systemd[1]: Started crash report submission. Apr 19 16:00:51 ROC-Cube whoopsie[33941]: [16:00:51] Using lock path: /var/lock/whoopsie/lock Apr 19 16:00:51 ROC-Cube systemd[1]: whoopsie.service: Deactivated successfully. Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_opt_ExpanDrive_SharedSupport_exfs.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_share_teams_teams.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_bin_nextcloud.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_bin_gnome-calendar.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_libexec_gnome-shell-calendar-server.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:/var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitWebProcess.1000.crash already marked for upload, skipping Apr 19 16:00:51 ROC-Cube systemd[1]: Started crash report submission. Apr 19 16:00:51 ROC-Cube whoopsie[33945]: [16:00:51] Using lock path: /var/lock/whoopsie/lock Apr 19 16:00:51 ROC-Cube systemd[1]: whoopsie.service: Deactivated successfully. Apr 19 16:00:51 ROC-Cube whoopsie-upload-all[33940]: INFO:root:Collecting info for /var/crash/_usr_bin_evolution.1000.crash... Apr 19 16:00:54 ROC-Cube whoopsie-upload-all[33940]: INFO:root:Marking /var/crash/_usr_bin_evolution.1000.crash for whoopsie upload Apr 19 16:00:54 ROC-Cube whoopsie-upload-all[33940]: INFO:root:Waiting for whoopsie to upload reports (timeout: 20 s) Apr 19 16:00:54 ROC-Cube whoopsie-upload-all[33940]: INFO:root: missing (remaining: 20 s): /var/crash/_usr_bin_evolution.1000.uploaded Apr 19 16:00:54 ROC-Cube systemd[1]: Started crash report submission. Apr 19 16:00:54 ROC-Cube whoopsie[35085]: [16:00:54] Using lock path: /var/lock/whoopsie/lock Apr 19 16:00:54 ROC-Cube whoopsie[35085]: [16:00:54] Parsing /var/crash/_usr_bin_evolution.1000.crash. Apr 19 16:00:54 ROC-Cube whoopsie[35085]: [16:00:54] Uploading /var/crash/_usr_bin_evolution.1000.crash. Apr 19 16:00:55 ROC-Cube systemd[4105]: app-gnome-org.gnome.Evolution-28125.scope: Consumed 15.552s CPU time. Apr 19 16:00:57 ROC-Cube whoopsie[35085]: [16:00:57] Sent; server replied with: No error Apr 19 16:00:57 ROC-Cube whoopsie[35085]: [16:00:57] Response code: 200 Apr 19 16:00:57 ROC-Cube whoopsie[35085]: [16:00:57] Reported OOPS ID 14381f7c-bfa6-11ec-8ad4-fa163e993415 Apr 19 16:00:57 ROC-Cube systemd[1]: whoopsie.service: Deactivated successfully. Apr 19 16:01:04 ROC-Cube whoopsie-upload-all[33940]: INFO:root:All reports uploaded successfully Apr 19 16:01:04 ROC-Cube systemd[1]: apport-autoreport.service: Deactivated successfully. Apr 19 16:01:04 ROC-Cube systemd[1]: Finished Process error reports when automatic reporting is enabled. Apr 19 16:01:04 ROC-Cube systemd[1]: apport-autoreport.service: Consumed 2.810s CPU time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
This bug may be related to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1272001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
This is not a bug rather a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967020] Re: WebKitWebProcess crashed with SIGSEGV
Evolution-3.44.0-1ubuntu1 in Jammy proposed fixes the issue. ** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967020 Title: WebKitWebProcess crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
Hi, Sure, the output is as follows: gsettings get org.gnome.desktop.interface gtk-theme 'Yaru-blue-dark' gsettings get org.gnome.desktop.interface color-scheme 'prefer-dark' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] [NEW] Evolution dark background in HTML message (Jammy 22.04)
Public bug reported: When using a dark theme in Jammy (22.04) beta, Evolution will display a dark background with black text for HTML emails in the message preview. Previously in Impish, the background was white with dark text. This only occurs when using a dark theme, If you use a light theme, the background of the email is also light. Release: Ubuntu Jammy Jellyfish (development branch) Please see attached screenshot. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Attachment added: "Example of HTML email rendering using Jammy 22.04" https://bugs.launchpad.net/bugs/1969251/+attachment/5580994/+files/image832.png ** Summary changed: - Evolution dark background in HTML message + Evolution dark background in HTML message (Jammy 22.04) ** Package changed: evolution (Ubuntu) => yaru-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969251] Re: Evolution dark background in HTML message (Jammy 22.04)
One quick question. On 21.10 the preview rendered with a white background even when using a dark theme. Please see the attached. And thanks for looking at this bug/question. I appreciate it. :) G. ** Attachment added: "White background previously with 21.10" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+attachment/5581004/+files/Screenshot%20from%202022-04-16%2011-13-33.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969251 Title: Evolution dark background in HTML message (Jammy 22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
