[Kernel-packages] [Bug 1777420] Re: Login loop after inactivity in login screen
Didn't manage to reproduce on 4.17.3 ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Fix Released Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] Re: Login loop after inactivity in login screen
I've updated to bionic from xenial recently, so I'm sure this issue always existed. Installed 4.17.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Incomplete Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1777420] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153936/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1777420] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153933/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153930/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1777420] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153931/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153938/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1777420] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153932/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153935/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153929/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153928/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1777420] Re: Login loop after inactivity in login screen
apport information ** Tags added: apport-collected bionic ** Description changed: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: yan 15467 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2018-05-28 (21 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + IwConfig: + lono wireless extensions. + + enp0s31f6 no wireless extensions. + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 + Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-22-generic N/A + linux-backports-modules-4.15.0-22-generic N/A + linux-firmware 1.173.1 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 11/16/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0505 + dmi.board.asset.tag: Default string + dmi.board.name: Z170M-PLUS + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153927/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to
[Kernel-packages] [Bug 1777420] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153937/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1777420] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1777420/+attachment/5153934/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux package in Ubuntu: Confirmed Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yan 15467 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-28 (21 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=5971ee8e-0793-4798-890d-992475d56d8a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/16/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1777420] [NEW] Login loop after inactivity in login screen
Public bug reported: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1777420 Title: Login loop after inactivity in login screen Status in linux-meta package in Ubuntu: New Bug description: I have Kubuntu 18.04 installed with /home/$USER directory using ecryptfs. As a display manager I use standard sddm and sddm-locker. If I leave my PC for a weekend powered on and locked then I'm unable to log in on monday. When I enter correct password in sddm - it prints that I entered incorrect password. If I switch to any virtual terminal and try to login there I'm immediately thrown out of session back to login prompt. That's what I see in logs: auth.log: Jun 18 12:59:55 yanPC login[14123]: pam_ecryptfs: Passphrase file wrapped Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session opened for user yan by LOGIN(uid=0) Jun 18 12:59:56 yanPC systemd-logind[770]: New session 1757 of user yan. Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC login[14031]: pam_unix(login:session): session closed for user yan Jun 18 12:59:56 yanPC login[14031]: pam_ecryptfs: Error setting up private mount Jun 18 12:59:56 yanPC systemd-logind[770]: Removed session 1757. syslog: Jun 18 12:59:56 yanPC systemd[1]: Started Session 1757 of user yan. Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Service has no hold-off time, scheduling restart. Jun 18 12:59:56 yanPC systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 12. Jun 18 12:59:56 yanPC systemd[1]: Stopped Getty on tty3. Jun 18 12:59:56 yanPC systemd[1]: Started Getty on tty3. kern.log: Jun 18 12:59:26 yanPC kernel: [870256.029760] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1756.scope Jun 18 12:59:56 yanPC kernel: [870285.302824] cgroup: fork rejected by pids controller in /user.slice/user-1000.slice/session-1757.scope If I login as root from virtual terminal and systemctl restart sddm.service then I'm able to login from anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1777420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296270] Re: Have to login twice after suspending
Same issue Mint 18.2. I've noticed if I wait for about 10 seconds afte resume from suspend and enter the password the password would be asked only once -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296270 Title: Have to login twice after suspending Status in gnome-screensaver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [ The bug ] After resuming from suspend, the screen is locked. I enter my password correctly and takes me to the screen I was at before suspending. Within 10 seconds the screen is automatically locked and I have to re-enter my password to get it unlocked. [ How to reproduce this bug ] Suspend your machine. Wake it from suspend. [ Environment ] lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Codename: trusty apt-cache policy linux-generic linux-generic: Installed: 3.13.0.18.22 Candidate: 3.13.0.19.23 Version table: 3.13.0.19.23 0 500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages *** 3.13.0.18.22 0 100 /var/lib/dpkg/status --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jobin 2887 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=755cc019-dd1c-4b7d-a70c-bbaaa6aa03c9 InstallationDate: Installed on 2014-03-17 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316) MachineType: Hewlett-Packard HP 630 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=e65dde38-8db3-4375-af07-da5265597b0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 07/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3672 dmi.board.vendor: Hewlett-Packard dmi.board.version: 23.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd07/22/2011:svnHewlett-Packard:pnHP630NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3672:rvr23.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 630 Notebook PC dmi.product.version: 058A10004C1000260 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1296270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
! IMPORTANT By the way the limitation for non latin users are stricter. For example cyrillic symbols in UTF8 consume 2bits, not 1. So filename may be maximux 71 symbols. AFAIR chinese symbols consume 3 bytes... IMPORTANT ! PS Change the description please -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/344878 Title: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) Status in eCryptfs: Fix Released Status in ecryptfs-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Natty: Won't Fix Status in linux source package in Natty: Won't Fix Status in ecryptfs-utils source package in Oneiric: Won't Fix Status in linux source package in Oneiric: Won't Fix Status in ecryptfs-utils source package in Precise: Invalid Status in linux source package in Precise: Fix Released Bug description: === IMPORTANT: eCryptfs can only store filenames of up to 143 characters when filename encryption is enabled. The remaining 112 characters are used for storing metadata such as the encrypted filename prefix, the signature of the filename encryption key, and an identifier for the cipher used, as well as random bytes to make /foo/file and /bar/file encrypt to different ciphertext and padding bytes to achieve proper cipher block size alignment. This bug is considered 'fixed' by the upstream maintainers. The eCryptfs kernel error message has been reduced to a debug level log message and eCryptfs now correctly reports its maximum supported filename length through the statfs() syscall. This is all that can be done without implementing a completely new encrypted filename design. A design that allows 255 character filenames without introducing other design limitations has not been identified and no one is currently working to come up with such a design. Please do not add comments or create new bugs saying that mv reports 'File name too long' or that you can't create a long filename in your eCryptfs mounts. It is an unfortunate design limitation that cannot be avoided at this time. Please do create new bugs when an application generates filenames that are too long to be stored in an eCryptfs mount. The application may be able to use the statfs() syscall to check the filename length limits of eCryptfs. Note that this does not include something like a torrent or ftp client trying to download a file with a long filename. The application is not generating the filename in those cases, it is just downloading the file that the user told it to download. === When trying to create a new file with a relatively long filename (f. ex. dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt) I get an error: file name to long, when in fact the file name is not to long, but the encrypted name created for this file is to long, so, the file was not created. this is no problem when I try to create a file, but when I'm copying a lot of files to my home folder I get some: filename to long error's and it's hard to fix (first locate the file, create shorter name, move again) so, maybe you could create a check for to long filenames? I'm using ext4 here... mv dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt /home/jens/ mv: cannot stat `/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt': File name too long libecryptfs0: Installed: 71-0ubuntu2 Candidate: 71-0ubuntu2 Version table: *** 71-0ubuntu2 0 500 http://be.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/344878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
Faced this on trusrty when was executin ecryptfs-migrate... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/344878 Title: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) Status in eCryptfs: Fix Released Status in ecryptfs-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Natty: Won't Fix Status in linux source package in Natty: Won't Fix Status in ecryptfs-utils source package in Oneiric: Won't Fix Status in linux source package in Oneiric: Won't Fix Status in ecryptfs-utils source package in Precise: Invalid Status in linux source package in Precise: Fix Released Bug description: === IMPORTANT: eCryptfs can only store filenames of up to 143 characters when filename encryption is enabled. The remaining 112 characters are used for storing metadata such as the encrypted filename prefix, the signature of the filename encryption key, and an identifier for the cipher used, as well as random bytes to make /foo/file and /bar/file encrypt to different ciphertext and padding bytes to achieve proper cipher block size alignment. This bug is considered 'fixed' by the upstream maintainers. The eCryptfs kernel error message has been reduced to a debug level log message and eCryptfs now correctly reports its maximum supported filename length through the statfs() syscall. This is all that can be done without implementing a completely new encrypted filename design. A design that allows 255 character filenames without introducing other design limitations has not been identified and no one is currently working to come up with such a design. Please do not add comments or create new bugs saying that mv reports 'File name too long' or that you can't create a long filename in your eCryptfs mounts. It is an unfortunate design limitation that cannot be avoided at this time. Please do create new bugs when an application generates filenames that are too long to be stored in an eCryptfs mount. The application may be able to use the statfs() syscall to check the filename length limits of eCryptfs. Note that this does not include something like a torrent or ftp client trying to download a file with a long filename. The application is not generating the filename in those cases, it is just downloading the file that the user told it to download. === When trying to create a new file with a relatively long filename (f. ex. dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt) I get an error: file name to long, when in fact the file name is not to long, but the encrypted name created for this file is to long, so, the file was not created. this is no problem when I try to create a file, but when I'm copying a lot of files to my home folder I get some: filename to long error's and it's hard to fix (first locate the file, create shorter name, move again) so, maybe you could create a check for to long filenames? I'm using ext4 here... mv dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt /home/jens/ mv: cannot stat `/home/jens/dfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqbdfkmqsdgjfmqsldjfmlsqkjlqkdmfsmgjlqlskdqshgpoizehmlqkbgmlqbgmqb.txt': File name too long libecryptfs0: Installed: 71-0ubuntu2 Candidate: 71-0ubuntu2 Version table: *** 71-0ubuntu2 0 500 http://be.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/344878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1382128] [NEW] No bluetooth interfaces after suspend
Public bug reported: sudo killall bluetoothd helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 16 18:58:03 2014 InstallationDate: Installed on 2014-08-14 (62 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) InterestingModules: bnep rfcomm btusb bluetooth MachineType: ASUSTeK Computer INC. 1018P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=UUID=abb4e533-fc94-4834-83ed-0920535dd8ad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1018P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd01/03/2011:svnASUSTeKComputerINC.:pn1018P:pvrx.x:rvnASUSTeKComputerINC.:rn1018P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1018P dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 74:F0:6D:AB:B8:6D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:913753 acl:1548 sco:0 events:858 errors:0 TX bytes:14 acl:811 sco:0 commands:402 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1382128 Title: No bluetooth interfaces after suspend Status in “bluez” package in Ubuntu: New Bug description: sudo killall bluetoothd helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 16 18:58:03 2014 InstallationDate: Installed on 2014-08-14 (62 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) InterestingModules: bnep rfcomm btusb bluetooth MachineType: ASUSTeK Computer INC. 1018P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic root=UUID=abb4e533-fc94-4834-83ed-0920535dd8ad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1018P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd01/03/2011:svnASUSTeKComputerINC.:pn1018P:pvrx.x:rvnASUSTeKComputerINC.:rn1018P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1018P dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 74:F0:6D:AB:B8:6D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:913753 acl:1548 sco:0 events:858 errors:0 TX bytes:14 acl:811 sco:0 commands:402 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1207487] Re: Brightness Controls work but brightness doesnt change
Christopher, I have always found a workaround, is there still need to boot at another kernel? (Also how to save error report to a file?) My netbook - Asus eeepc 1018p The WORKAROUND: http://itsfoss.com/fix-brightness-ubuntu-1310/ pen a terminal and create the following configuration file, if it does not exist: touch /usr/share/X11/xorg.conf.d/20-intel.conf Now we need to edit this file. You can use any editor be it a terminal one or graphical. sudo gedit /usr/share/X11/xorg.conf.d/20-intel.conf Add the following lines to this file: Section Device Identifier card0 Driver intel Option Backlight intel_backlight BusID PCI:0:2:0 EndSection Save it. Log out and log in back. The brightness control should be working through function keys now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1207487 Title: Brightness Controls work but brightness doesnt change Status in “linux” package in Ubuntu: Expired Bug description: I am unable to change the brigthness of the screen, the controls work properly but changing the brightness level has no impact on the screen brightness. It feels like the old intel brightness regression bug. The brightness is always at the full level. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 2 00:35:28 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.10.0-3-generic, x86_64: installed bbswitch, 0.7, 3.10.0-4-generic, x86_64: installed bbswitch, 0.7, 3.10.0-5-generic, x86_64: installed nvidia-304, 304.88, 3.10.0-4-generic, x86_64: installed nvidia-304, 304.88, 3.10.0-5-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397d] NVIDIA Corporation GF108M [GeForce GT 520M] [10de:0df7] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-06-02 (60 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130601) MachineType: LENOVO HuronRiver Platform MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic root=UUID=f80879ea-b397-4778-bb59-f9fb5c8fa4ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Thu Aug 1 22:15:43 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2-0ubuntu1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1207487] Re: Brightness Controls work but brightness doesnt change
This bug is still in trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1207487 Title: Brightness Controls work but brightness doesnt change Status in “linux” package in Ubuntu: Expired Bug description: I am unable to change the brigthness of the screen, the controls work properly but changing the brightness level has no impact on the screen brightness. It feels like the old intel brightness regression bug. The brightness is always at the full level. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 2 00:35:28 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.10.0-3-generic, x86_64: installed bbswitch, 0.7, 3.10.0-4-generic, x86_64: installed bbswitch, 0.7, 3.10.0-5-generic, x86_64: installed nvidia-304, 304.88, 3.10.0-4-generic, x86_64: installed nvidia-304, 304.88, 3.10.0-5-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397d] NVIDIA Corporation GF108M [GeForce GT 520M] [10de:0df7] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-06-02 (60 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130601) MachineType: LENOVO HuronRiver Platform MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic root=UUID=f80879ea-b397-4778-bb59-f9fb5c8fa4ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Thu Aug 1 22:15:43 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2-0ubuntu1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
