[Touch-packages] [Bug 1952546] [NEW] lightdm segfaults
Public bug reported: [313348.119392] lightdm[2134371]: segfault at 1ec40 ip 7efcd5819f0b sp 7ffcececb2e0 error 4 in libc-2.31.so[7efcd57a4000+178000] [313348.119421] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [376858.385348] lightdm[2199477]: segfault at 557d21107adc ip 7fc4457eaf0b sp 7ffebbdb0960 error 4 in libc-2.31.so[7fc445775000+178000] [376858.385365] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [426947.200392] lightdm[2719494]: segfault at 0 ip 7f15ab8d937e sp 7ffc23e2d490 error 4 in libc-2.31.so[7f15ab861000+178000] [426947.200412] Code: 84 5c ff ff ff 0f 1f 80 00 00 00 00 48 8d 0c 58 0f b7 11 66 85 d2 0f 84 45 ff ff ff 48 8d 04 d8 83 ea 01 4c 8b 80 80 00 00 00 <49> 8b 30 48 89 b0 80 00 00 00 66 89 11 49 c7 40 08 00 00 00 00 e9 [443215.562461] lightdm[2991210]: segfault at 1ec40 ip 7f3f905bbf0b sp 7ffda4c1dcf0 error 4 in libc-2.31.so[7f3f90546000+178000] [443215.562482] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [465392.489452] lightdm[3119309]: segfault at 313d ip 7f8b7b802f0b sp 7ffc8d7ac920 error 4 in libc-2.31.so[7f8b7b78d000+178000] [465392.489467] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [529507.631380] traps: lightdm[3180400] general protection fault ip:7fe39b5a837e sp:7ffd759e0d60 error:0 in libc-2.31.so[7fe39b53+178000] [540575.109029] traps: lightdm[3340750] general protection fault ip:7f3250ab5f0b sp:7fff1bad56a0 error:0 in libc-2.31.so[7f3250a4+178000] [619372.324869] lightdm[3364875]: segfault at 0 ip 7f39c392237e sp 7ffe234b6540 error 4 in libc-2.31.so[7f39c38aa000+178000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 Uname: Linux 5.13.19 x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Nov 28 01:45:39 2021 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1952546 Title: lightdm segfaults Status in lightdm package in Ubuntu: New Bug description: [313348.119392] lightdm[2134371]: segfault at 1ec40 ip 7efcd5819f0b sp 7ffcececb2e0 error 4 in libc-2.31.so[7efcd57a4000+178000] [313348.119421] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [376858.385348] lightdm[2199477]: segfault at 557d21107adc ip 7fc4457eaf0b sp 7ffebbdb0960 error 4 in libc-2.31.so[7fc445775000+178000] [376858.385365] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [426947.200392] lightdm[2719494]: segfault at 0 ip 7f15ab8d937e sp 7ffc23e2d490 error 4 in libc-2.31.so[7f15ab861000+178000] [426947.200412] Code: 84 5c ff ff ff 0f 1f 80 00 00 00 00 48 8d 0c 58 0f b7 11 66 85 d2 0f 84 45 ff ff ff 48 8d 04 d8 83 ea 01 4c 8b 80 80 00 00 00 <49> 8b 30 48 89 b0 80 00 00 00 66 89 11 49 c7 40 08 00 00 00 00 e9 [443215.562461] lightdm[2991210]: segfault at 1ec40 ip 7f3f905bbf0b sp 7ffda4c1dcf0 error 4 in libc-2.31.so[7f3f90546000+178000] [443215.562482] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [465392.489452] lightdm[3119309]: segfault at 313d ip 7f8b7b802f0b sp 7ffc8d7ac920 error 4 in libc-2.31.so[7f8b7b78d000+178000] [465392.489467] Code: 0f b7 02 83 c0 01 66 89 02 0f b7 c0 48 3b 05 ec 03 15 00 0f 83 86 00 00 00 48 8b 56 10 48 85 d2 74 7d 64 8b 04 25 18 00 00 00 <4c> 8b 52 10 85 c0 74 9d eb 4a 0f 1f 00 48 8b 50 10 49 89 c0 4c 89 [529507.631380] traps: lightdm[3180400] general protection fault ip:7fe39b5a837e sp:7ffd759e0d60 error:0 in libc-2.31.so[7fe39b53+178000] [540575.109029] traps: lightdm[3340750] general protection fault
[Touch-packages] [Bug 1950879] [NEW] Lightdm Desktop Selection Can't Scroll to End of List
Public bug reported: I've got multiple desktops installed on some machines accessed by many users with different preferences. When they connect via VNC using the slick greeter, the desktop selection list is cut-off on the bottom of the screen. There is no way to scroll and as far as I can tell no way to reduce the font size to make more fit in the list, and least nothing documented. There is also no man page for lightdm.conf. I am using this on Ubuntu 21.10 but have the same problem on Ubuntu 20.04 and Debian Bullseye. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: lightdm 1.30.0-0ubuntu4 Uname: Linux 5.15.2 x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sat Nov 13 18:01:21 2021 InstallationDate: Installed on 2021-11-11 (2 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1950879 Title: Lightdm Desktop Selection Can't Scroll to End of List Status in lightdm package in Ubuntu: New Bug description: I've got multiple desktops installed on some machines accessed by many users with different preferences. When they connect via VNC using the slick greeter, the desktop selection list is cut-off on the bottom of the screen. There is no way to scroll and as far as I can tell no way to reduce the font size to make more fit in the list, and least nothing documented. There is also no man page for lightdm.conf. I am using this on Ubuntu 21.10 but have the same problem on Ubuntu 20.04 and Debian Bullseye. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: lightdm 1.30.0-0ubuntu4 Uname: Linux 5.15.2 x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sat Nov 13 18:01:21 2021 InstallationDate: Installed on 2021-11-11 (2 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1950879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1949535] Re: X-forwarding no longer works
Yes Bullseye, you can close this ticket. Something went wrong during the upgrade. I re-installed it now it is working. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 9 Nov 2021, Lucas Kanashiro wrote: > Date: Tue, 09 Nov 2021 15:08:27 - > From: Lucas Kanashiro <1949...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1949535] Re: X-forwarding no longer works > > This is confusing Robert, is your target system running Debian Bullseye? > There is no Debian release called Bullet. Do you have any custom > configuration in the server or client side? Please provide more > information, for instance detailed steps, so we can attempt to reproduce > it. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1949535 > > Title: > X-forwarding no longer works > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > I operate a Linux based Internet hosting service that includes Linux > shell servers of various flavors. I control these from home using > Ubuntu 21.10 presently. Until recently, X-forwarding has worked from > all but ancient Redhat 6.2 servers. I recently upgraded my debian > shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com > from my workstation nanook.eskimo.com ceased to function. It simply > says "Cannot open DISPLAY". At the time, all the others continued to > work. Today, when I went to do upgrades, now ssh -X is forwarding > across the board to all flavors of Linux. I did an ssh -V, nothing > obvious wrong in the connection. > > debug1: Authentications that can continue: publickey,password > debug1: Next authentication method: publickey > debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA > SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent > debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA > SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent > debug1: Authentication succeeded (publickey). > Authenticated to igloo.eskimo.com ([204.122.16.128]:22). > debug1: channel 0: new [client-session] > debug1: Requesting no-more-sessi...@openssh.com > debug1: Entering interactive session. > debug1: pledge: network > debug1: client_input_global_request: rtype hostkeys...@openssh.com > want_reply 0 > debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug1: Sending environment. > debug1: Sending env LANG = en_US.UTF-8 > debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 > debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 > debug1: channel 0: free: client-session, nchannels 1 > debug1: fd 2 clearing O_NONBLOCK > Connection to igloo.eskimo.com closed. > Transferred: sent 3748, received 3820 bytes, in 6.4 seconds > Bytes per second: sent 589.4, received 600.8 > > I don't see anything obviously wrong here but still it does not work, I get: > xclock > Error: Can't open display: > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ssh (not installed) > Uname: Linux 5.13.19 x86_64 > ApportVersion: 2.20.11-0ubuntu71 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: MATE > Date: Tue Nov 2 17:31:14 2021 > SourcePackage: openssh > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1949535/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1949535 Title: X-forwarding no longer works Status in openssh package in Ubuntu: Incomplete Bug description: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recently upgraded my debian shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com from my workstation nanook.eskimo.com ceased to function. It simply says "Cannot open DISPLAY". At the time, all the others continued to work. Today, when I went to do upgrades, now ssh -X is forwarding across the board to all flavors of Linux. I did an ssh -V, nothing obvious wrong in the connection. debug1: Authentications that can continue: publickey,password debug1: Next authentication method:
Re: [Touch-packages] [Bug 1949535] Re: X-forwarding no longer works
I am originating from a Ubuntu 21.10 system to a Debian Bullet system, but now I can't get X-forwarding to work from any site I connect to when originating from Ubuntu 21.10. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Mon, 8 Nov 2021, Paride Legovini wrote: > Date: Mon, 08 Nov 2021 15:43:10 - > From: Paride Legovini <1949...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1949535] Re: X-forwarding no longer works > > Hello Robert and thanks for your bug report. You wrote: > >> I recently upgraded my debian shell server to Bullet > > but I'm not sure I get what you mean. Is it a Debian system or an Ubuntu > system? If it's upgrading a Debian system that broke your setup then > there's nothing I can see that points to a bug in Ubuntu. Moreover: what > is Bullet? Did you mean Bullseye or Bookworm? > > If you think there's actually a bug in Ubuntu here please share more of > your reasoning, possibly providing a reproducer, e.g. by ssh -X to a > container or VM. I'm marking this bug report as Incomplete for the > moment. Feel free to change it back to New after commenting back. > Thanks! > > ** Changed in: openssh (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1949535 > > Title: > X-forwarding no longer works > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > I operate a Linux based Internet hosting service that includes Linux > shell servers of various flavors. I control these from home using > Ubuntu 21.10 presently. Until recently, X-forwarding has worked from > all but ancient Redhat 6.2 servers. I recently upgraded my debian > shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com > from my workstation nanook.eskimo.com ceased to function. It simply > says "Cannot open DISPLAY". At the time, all the others continued to > work. Today, when I went to do upgrades, now ssh -X is forwarding > across the board to all flavors of Linux. I did an ssh -V, nothing > obvious wrong in the connection. > > debug1: Authentications that can continue: publickey,password > debug1: Next authentication method: publickey > debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA > SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent > debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA > SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent > debug1: Authentication succeeded (publickey). > Authenticated to igloo.eskimo.com ([204.122.16.128]:22). > debug1: channel 0: new [client-session] > debug1: Requesting no-more-sessi...@openssh.com > debug1: Entering interactive session. > debug1: pledge: network > debug1: client_input_global_request: rtype hostkeys...@openssh.com > want_reply 0 > debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug1: Sending environment. > debug1: Sending env LANG = en_US.UTF-8 > debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 > debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 > debug1: channel 0: free: client-session, nchannels 1 > debug1: fd 2 clearing O_NONBLOCK > Connection to igloo.eskimo.com closed. > Transferred: sent 3748, received 3820 bytes, in 6.4 seconds > Bytes per second: sent 589.4, received 600.8 > > I don't see anything obviously wrong here but still it does not work, I get: > xclock > Error: Can't open display: > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ssh (not installed) > Uname: Linux 5.13.19 x86_64 > ApportVersion: 2.20.11-0ubuntu71 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: MATE > Date: Tue Nov 2 17:31:14 2021 > SourcePackage: openssh > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1949535/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1949535 Title: X-forwarding no longer works Status in openssh package in Ubuntu: Incomplete Bug description: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recen
[Touch-packages] [Bug 1949535] [NEW] X-forwarding no longer works
Public bug reported: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recently upgraded my debian shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com from my workstation nanook.eskimo.com ceased to function. It simply says "Cannot open DISPLAY". At the time, all the others continued to work. Today, when I went to do upgrades, now ssh -X is forwarding across the board to all flavors of Linux. I did an ssh -V, nothing obvious wrong in the connection. debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Authentication succeeded (publickey). Authenticated to igloo.eskimo.com ([204.122.16.128]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 2 clearing O_NONBLOCK Connection to igloo.eskimo.com closed. Transferred: sent 3748, received 3820 bytes, in 6.4 seconds Bytes per second: sent 589.4, received 600.8 I don't see anything obviously wrong here but still it does not work, I get: xclock Error: Can't open display: ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ssh (not installed) Uname: Linux 5.13.19 x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Tue Nov 2 17:31:14 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1949535 Title: X-forwarding no longer works Status in openssh package in Ubuntu: New Bug description: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recently upgraded my debian shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com from my workstation nanook.eskimo.com ceased to function. It simply says "Cannot open DISPLAY". At the time, all the others continued to work. Today, when I went to do upgrades, now ssh -X is forwarding across the board to all flavors of Linux. I did an ssh -V, nothing obvious wrong in the connection. debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Authentication succeeded (publickey). Authenticated to igloo.eskimo.com ([204.122.16.128]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 2 clearing O_NONBLOCK Connection to igloo.eskimo.com closed. Transferred: sent 3748, received 3820 bytes, in 6.4 seconds Bytes per second: sent 589.4, received 600.8 I don't see anything obviously wrong he
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Not an issue, found that I was using the wrong GPU driver for my hardware, when I fixed that it fixed the shutdown issue as well as some graphics issues. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Wed, 30 Jun 2021, Dan Streetman wrote: > Date: Wed, 30 Jun 2021 22:26:48 - > From: Dan Streetman <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > please reopen if this is still an issue > > ** Changed in: systemd (Ubuntu) > Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > Invalid > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service → > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service → > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service → > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: Invalid Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/sy
[Touch-packages] [Bug 1929754] [NEW] Influx installed without my installing it
Public bug reported: On my webserver, recently upgraded to 21.04, I am chasing some security issues and I find two instances of influxdb running. That's interesting because I never installed it, further checking apt it shows NOT installed, yet, there it is. The parent process is systemd, of course fucking Poettering polluting my system again, and it seems to be linked to the lingering function of systemd sessions. I don't want it, is there a way to get rid of it other than replacing Ubuntu with a non systemd Linux like mxlinux? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.6 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed May 26 14:51:10 2021 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.12.4 root=UUID=a9844279-752c-4aeb-9338-a7771c7b5d06 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1929754 Title: Influx installed without my installing it Status in systemd package in Ubuntu: New Bug description: On my webserver, recently upgraded to 21.04, I am chasing some security issues and I find two instances of influxdb running. That's interesting because I never installed it, further checking apt it shows NOT installed, yet, there it is. The parent process is systemd, of course fucking Poettering polluting my system again, and it seems to be linked to the lingering function of systemd sessions. I don't want it, is there a way to get rid of it other than replacing Ubuntu with a non systemd Linux like mxlinux? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.6 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed May 26 14:51:10 2021 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.12.4 root=UUID=a9844279-752c-4aeb-9338-a7771c7b5d06 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.n
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
Ok the other machine I was having this issue with is a kvm-qemu virtual machine acting as a mail server. On it I remove xorg-xserver-video* and with those removed it no longer hangs. So it seems somehow xserver graphics/video are involved. My workstation is using intel internal graphics and it is an i7-9700k so I use the kernel based x-server on it and don't need the others. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
I removed a bunch of stuff I did not really need, game servers, xorg- xserver drivers for hardware I did not have, kvm-qemu stuff that I have not used on this machine since last July, tor, and after getting rid of a bunch of cruft, it does reboot properly so now I have to figure out which application breaks it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
I accidentally saved the reboot image attachment before I completed the comment, so that's where it hangs. This time I only waited about a minute and a half before holding down control+alt+del to force the reboot, but I've walked away for an hour and let it sit, it does not finish beyond this point. Strangely reboot and shutdown work but not systemctl reboot. Tried deleting tor to see if it was causing issues, got past thermald but still hung, see logs2. ** Attachment added: "systemctl reboot after removing tor." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498330/+files/logs2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
** Attachment added: "Picture of Monitor at please reboot hangs." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498329/+files/reboot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
** Attachment added: "Log of what happened after I typed systemctl reboot" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498328/+files/logs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
I accidentally saved the reboot image attachment before I completed the comment, so that's where it hangs. This time I only waited about a minute and a half before holding down control+alt+del to force the reboot, but I've walked away for an hour and let it sit, it does not finish beyond this point. Strangely reboot and shutdown work but not systemctl reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
I have TWO unrelated machines one a KVM-Qemu virtual machine, and one my physical workstation, both exhibit this behavior. I'll try to get some logs for you. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Mon, 17 May 2021, Dan Streetman wrote: > Date: Mon, 17 May 2021 12:16:07 - > From: Dan Streetman <1928...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute > 21.04 > > sudo systemctl reboot works fine for me. You should check your logs to > see what hung your reboot, or attach your journal logs from a boot where > you reproduced the problem. > > ** Changed in: systemd (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1928564 > > Title: > systemctl reboot hangs the machine under hirsute 21.04 > > Status in systemd package in Ubuntu: > Incomplete > > Bug description: > If you type "systemctl reboot" instead of rebooting the machine hangs > hard, nothing except a hard power cycle seems to get it's attention. > This is true of both physical hardware and virtual machines, it was > NOT a problem under groovy. > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: systemd 247.3-3ubuntu3 > Uname: Linux 5.12.4 x86_64 > ApportVersion: 2.20.11-0ubuntu65 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: MATE > Date: Sat May 15 19:12:59 2021 > InstallationDate: Installed on 2020-08-10 (278 days ago) > InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 > root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 > SourcePackage: systemd > SystemdFailedUnits: > Error: command ['systemctl', 'status', '--full', '●'] failed with exit code > 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use > systemd-escape?). > Unit \xe2\x97\x8f.service could not be found. > UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) > dmi.bios.date: 06/04/2020 > dmi.bios.release: 16.2 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1602 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME Z390-A > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: ASUS_MB_CNL > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release:
[Touch-packages] [Bug 1928564] [NEW] systemctl reboot hangs the machine under hirsute 21.04
Public bug reported: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: New Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
This resulted in a several hour outage and a 44 mile round trip drive that should not have been necessary. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: New Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1926686] Re: lightdm segfaults
Yes, I have other things segfaulting with libc-2.31.so as well but ubuntu-bug would not allow me to originate a bug report on a library. On 4/30/21 4:39 PM, Gunnar Hjalmarsson wrote: > OTOH... If you haven't enabled the guest session feature, the difference > between the lightdm versions in focal-release and focal-proposed can't > possibly cause the segfault. > > Did you possibly install everything from focal-proposed? In that case > you may be actually 'testing' this upload: > > https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.3 > > After all the error message includes "error 4 in libc-2.31.so". > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1926686 Title: lightdm segfaults Status in lightdm package in Ubuntu: Incomplete Bug description: [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip 7f7260003f0b sp 7fffbb5a0600 error 4 in libc-2.31.so[7f725ff8e000+178000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 Uname: Linux 5.10.32 x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 29 20:55:18 2021 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926686] Re: lightdm segfaults
Ok, I've installed the old version to see if this occurs, this was not a frequent problem with this version so I'm unlikely to have an answer overnight. However, I was under the impression that the purpose of proposed was to test and get feedback and fix such things before it entered mainstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1926686 Title: lightdm segfaults Status in lightdm package in Ubuntu: Incomplete Bug description: [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip 7f7260003f0b sp 7fffbb5a0600 error 4 in libc-2.31.so[7f725ff8e000+178000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 Uname: Linux 5.10.32 x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 29 20:55:18 2021 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926686] [NEW] lightdm segfaults
Public bug reported: [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip 7f7260003f0b sp 7fffbb5a0600 error 4 in libc-2.31.so[7f725ff8e000+178000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 Uname: Linux 5.10.32 x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 29 20:55:18 2021 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1926686 Title: lightdm segfaults Status in lightdm package in Ubuntu: New Bug description: [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip 7f7260003f0b sp 7fffbb5a0600 error 4 in libc-2.31.so[7f725ff8e000+178000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 Uname: Linux 5.10.32 x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 29 20:55:18 2021 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915092] Re: lib-gtk-3 / lib-gtk-3-dev NOT compatible
Since you can't compile against the library without the header file, it would make sense to me to remove the matching library but at any rate, I understand the issue and thank you for your assistance. I found a different calendar that does what I need so I'm good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: Invalid Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915092] Re: lib-gtk-3 / lib-gtk-3-dev NOT compatible
I just re-installed everything and it pulled what was missing but at this point it's clearly not your issue so feel free to close this ticket. It would be nice if there were a dev file to match the most recent libs but I realize if you choose proposed, bugs come with that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915092] Re: lib-gtk-3 / lib-gtk-3-dev NOT compatible
That got me past that BUT it deleted: caja caja-admin caja-mediainfo caja-rename caja-seahorse evolution evolution-plugin-bogofilter evolution-plugin-pstimport evolution-plugins evolution-plugins-experimental folder-color-caja libevolution libgail-3-0 libgtk-3-bin mate-desktop-environment mate-desktop-environment-core mate-desktop-environment-extra mate-desktop-environment-extras ubuntu-mate-core So I had to re-install my desktop, then California needed libecal-1.2 and Ubuntu 20.10 ships with libecal-2.0 so I'm still stuck but thanks for your assistance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915092] Re: lib-gtk-3 / lib-gtk-3-dev NOT compatible
I am sorry, it is 20.10 not 20.04. In Synaptic, under Settings -> Repositories -> Developer Options I have Pre-released updates (groovy- proposed) checked so perhaps that is why I have this version. Here is the output of apt policy libgtk-3-0: libgtk-3-0: Installed: 3.24.23-1ubuntu1.1 Candidate: 3.24.23-1ubuntu1.1 Version table: *** 3.24.23-1ubuntu1.1 100 100 /var/lib/dpkg/status 3.24.23-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915092] [NEW] lib-gtk-3 / lib-gtk-3-dev NOT compatible
Public bug reported: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: New Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS
I'm seeing this in 19.10 as well. Good to know it's gone for at least two years without being fixed, way to go Canonical! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: cups 2.2.0-2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvi
[Touch-packages] [Bug 1850041] Re: Systemd-analyze blame returns "Bootup is not yet finished"
I am experiencing this also. If I disable plymouth-quit-wait.service then boot completes but leaves me in text mode until I type control- alt-f7. This worked properly prior to 19.10 upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1850041 Title: Systemd-analyze blame returns "Bootup is not yet finished" Status in systemd package in Ubuntu: Confirmed Bug description: Every time I run systemd-analyze blame, I get the message: Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. This, even if my laptop is on for several hours. Running systemctl list-jobs, returns: JOB UNIT TYPE STATE 1 graphical.target start waiting 95 systemd-update-utmp-runlevel.service start waiting 89 system-getty.slice start waiting 87 getty.target start waiting 21 setvtrgb.service start waiting 112 plymouth-quit-wait.service start running 88 getty@tty1.service start waiting 2 multi-user.targetstart waiting Boot time is about 90 seconds, before and after upgrading from 19.04 to 19.10. All applications start and run normally. My system is Ubuntu Budgie 19.10, working on a Dell Inspiron Laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Oct 27 09:54:26 2019 MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=2b7d5523-743f-465d-a24c-fadc4a3aa0f4 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2019-10-23 (3 days ago) dmi.bios.date: 11/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd11/30/2012:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1850041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1842205] Re: 18 second delay during login
I've included them per your request but I do not think it will help much because the issue isn't boot time, that happens in about 4 seconds, it's login time, and specifically the time between when the X server starts and displays saved apps and when it gets around to drawing the panels and background. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Sun, 1 Sep 2019, lotuspsychje wrote: > Date: Sun, 01 Sep 2019 11:53:47 - > From: lotuspsychje > Reply-To: Bug 1842205 <1842...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1842205] Re: 18 second delay during login > > Thank you for reporting this bug and make ubuntu better! > > Could you attach these outputs too please: > > systemd-analyze blame and > systemd-analyze critical-chain > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1842205 > > Title: > 18 second delay during login > > Status in systemd package in Ubuntu: > New > > Bug description: > I am experiencing an 18 second delay during login between the > time the X-server and saved applications start, and the background, > panels, and rest of the Mate desktop draw. > > I have tried new user with no configuration to eliminate user > configuration date. I've tried > different desktop environments to eliminate them. I've tried different > greeters and different > display managers. Symptoms don't change. > > Out of desperation I grabbed the most recent systemd off of github and > compiled and installed > it, version 243 verses version 240 shipped with Ubuntu 19.04. > > With version 243 login no longer has delay but audio breaks. The fact > that replacing systemd > got rid of the delay tells me the delay is in that package. I can find > nothing in the logs that > would give me a clue as to what is wrong, no errors in that time frame, in > fact NOTHING logs during > that interval. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5.4 > ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21 > Uname: Linux 5.0.0-27-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > CurrentDesktop: MATE > Date: Sun Sep 1 03:19:08 2019 > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency > root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash > xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1 > SourcePackage: systemd > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/06/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1105 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME Z390-A > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: ASUS_MB_CNL > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > modified.conffile..etc.systemd.journald.conf: [modified] > modified.conffile..etc.systemd.logind.conf: [modified] > modified.conffile..etc.systemd.networkd.conf: [modified] > modified.conffile..etc.systemd.resolved.conf: [modified] > modified.conffile..etc.systemd.system.conf: [modified] > modified.conffile..etc.systemd.timesyncd.conf: [modified] > modified.conffile..etc.systemd.user.conf: [modified] > mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575 > mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198 > mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575 > mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197 > mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198 > mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197 > mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1842205 Title: 18 second delay during login Status in systemd package in Ubuntu: New Bug descrip
[Touch-packages] [Bug 1842205] Re: 18 second delay during login
Requested by lotuspsychje ** Attachment added: "Output of systemd-analyze blame" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+attachment/5286068/+files/blame -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1842205 Title: 18 second delay during login Status in systemd package in Ubuntu: New Bug description: I am experiencing an 18 second delay during login between the time the X-server and saved applications start, and the background, panels, and rest of the Mate desktop draw. I have tried new user with no configuration to eliminate user configuration date. I've tried different desktop environments to eliminate them. I've tried different greeters and different display managers. Symptoms don't change. Out of desperation I grabbed the most recent systemd off of github and compiled and installed it, version 243 verses version 240 shipped with Ubuntu 19.04. With version 243 login no longer has delay but audio breaks. The fact that replacing systemd got rid of the delay tells me the delay is in that package. I can find nothing in the logs that would give me a clue as to what is wrong, no errors in that time frame, in fact NOTHING logs during that interval. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.4 ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21 Uname: Linux 5.0.0-27-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Sep 1 03:19:08 2019 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1105 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.systemd.journald.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] modified.conffile..etc.systemd.networkd.conf: [modified] modified.conffile..etc.systemd.resolved.conf: [modified] modified.conffile..etc.systemd.system.conf: [modified] modified.conffile..etc.systemd.timesyncd.conf: [modified] modified.conffile..etc.systemd.user.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575 mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198 mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575 mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197 mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198 mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197 mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842205] Re: 18 second delay during login
Requested by lotuspsychje ** Attachment added: "Output of systemd-analyze critical-chain" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+attachment/5286069/+files/critical-chain -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1842205 Title: 18 second delay during login Status in systemd package in Ubuntu: New Bug description: I am experiencing an 18 second delay during login between the time the X-server and saved applications start, and the background, panels, and rest of the Mate desktop draw. I have tried new user with no configuration to eliminate user configuration date. I've tried different desktop environments to eliminate them. I've tried different greeters and different display managers. Symptoms don't change. Out of desperation I grabbed the most recent systemd off of github and compiled and installed it, version 243 verses version 240 shipped with Ubuntu 19.04. With version 243 login no longer has delay but audio breaks. The fact that replacing systemd got rid of the delay tells me the delay is in that package. I can find nothing in the logs that would give me a clue as to what is wrong, no errors in that time frame, in fact NOTHING logs during that interval. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.4 ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21 Uname: Linux 5.0.0-27-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Sep 1 03:19:08 2019 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1105 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.systemd.journald.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] modified.conffile..etc.systemd.networkd.conf: [modified] modified.conffile..etc.systemd.resolved.conf: [modified] modified.conffile..etc.systemd.system.conf: [modified] modified.conffile..etc.systemd.timesyncd.conf: [modified] modified.conffile..etc.systemd.user.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575 mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198 mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575 mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197 mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198 mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197 mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842205] [NEW] 18 second delay during login
Public bug reported: I am experiencing an 18 second delay during login between the time the X-server and saved applications start, and the background, panels, and rest of the Mate desktop draw. I have tried new user with no configuration to eliminate user configuration date. I've tried different desktop environments to eliminate them. I've tried different greeters and different display managers. Symptoms don't change. Out of desperation I grabbed the most recent systemd off of github and compiled and installed it, version 243 verses version 240 shipped with Ubuntu 19.04. With version 243 login no longer has delay but audio breaks. The fact that replacing systemd got rid of the delay tells me the delay is in that package. I can find nothing in the logs that would give me a clue as to what is wrong, no errors in that time frame, in fact NOTHING logs during that interval. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.4 ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21 Uname: Linux 5.0.0-27-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Sep 1 03:19:08 2019 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1105 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.systemd.journald.conf: [modified] modified.conffile..etc.systemd.logind.conf: [modified] modified.conffile..etc.systemd.networkd.conf: [modified] modified.conffile..etc.systemd.resolved.conf: [modified] modified.conffile..etc.systemd.system.conf: [modified] modified.conffile..etc.systemd.timesyncd.conf: [modified] modified.conffile..etc.systemd.user.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575 mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198 mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575 mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197 mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198 mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197 mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1842205 Title: 18 second delay during login Status in systemd package in Ubuntu: New Bug description: I am experiencing an 18 second delay during login between the time the X-server and saved applications start, and the background, panels, and rest of the Mate desktop draw. I have tried new user with no configuration to eliminate user configuration date. I've tried different desktop environments to eliminate them. I've tried different greeters and different display managers. Symptoms don't change. Out of desperation I grabbed the most recent systemd off of github and compiled and installed it, version 243 verses version 240 shipped with Ubuntu 19.04. With version 243 login no longer has delay but audio breaks. The fact that replacing systemd got rid of the delay tells me the delay is in that package. I can find nothing in the logs that would give me a clue as to what is wrong, no errors in that time frame, in fact NOTHING logs during that interval. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5.4 ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21 Uname: Linux 5.0.0-27-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Sep 1 03:19:08 2019 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash xdg.force_integrated=1
[Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Tried the most recent proposed kernel, 5.2.0-8 today, still gets stuck at the target reboot reached. Not a huge deal at this point as the magic-sys-request is working so I can at least force the reboot from the keyboard at that point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1730908] Re: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/
[35965.264754] audit: type=1400 audit(1559942671.706:29): apparmor="DENIED" operation="open" profile="man_groff" name="/usr/local/lib64/libgcc_s.so.1" pid=17962 comm="troff" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1730908 Title: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux- gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Status in apparmor package in Ubuntu: Expired Bug description: Since I installed Ubuntu 17.10 I cannot print anymore. The only thing I see in the logs are many lines like the following: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 I'm not sure it is the cause of my problems, but there is at least a problem with apparmor's configuration in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1730908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
I could not find what was going wrong with update-grub2, it showed it doing the right thing but did not alter the boot screen. I purged grub and all it's configuration from my workstation then re-installed, now it is working again. I installed 4.15.18 and systemctl reboot is not getting stuck on that kernel. I'll try to do a binary search to narrow it further as time allows. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Apr 2019, Kai-Heng Feng wrote: > Date: Tue, 23 Apr 2019 08:03:12 - > From: Kai-Heng Feng > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Does the system have boot loader other than GRUB installed? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondeman
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Actually there was petiboot which I never did get successfully working. Wanted to be able to kexec-boot because the BIOS in this old Mac is so very painfully slow. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Apr 2019, Kai-Heng Feng wrote: > Date: Tue, 23 Apr 2019 08:03:12 - > From: Kai-Heng Feng > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Does the system have boot loader other than GRUB installed? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.serv
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Grub and Grub2 are installed, no others, not lilo, etc. I do not know WHERE it is finding 5.0.9 at, no remnants in the boot, modules, initramfs directories. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Apr 2019, Kai-Heng Feng wrote: > Date: Tue, 23 Apr 2019 08:03:12 - > From: Kai-Heng Feng > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Does the system have boot loader other than GRUB installed? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Well I've managed to screw up my machine massively and don't know how to get it back to a sane state. I deleted what I thought were all traces of 5.0.9 that I had compiled and re-ran update-grub2, then I installed: rw-r--r-- 1 nanook rmtonly 10877978 Apr 22 23:20 linux-headers-4.15.18-041518_4.15.18-041518.201804190330_all.deb -rw-r--r-- 1 nanook rmtonly 1056602 Apr 22 23:20 linux-headers-4.15.18-041518-generic_4.15.18-041518.201804190330_amd64.deb -rw-r--r-- 1 nanook rmtonly 1059488 Apr 22 23:20 linux-headers-4.15.18-041518-lowlatency_4.15.18-041518.201804190330_amd64.deb -rw-r--r-- 1 nanook rmtonly 52634544 Apr 22 23:21 linux-image-4.15.18-041518-generic_4.15.18-041518.201804190330_amd64.deb -rw-r--r-- 1 nanook rmtonly 52642100 Apr 22 23:21 linux-image-4.15.18-041518-lowlatency_4.15.18-041518.201804190330_amd64.deb And ran another update-grub2 with the following output: ourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.0.0-13-lowlatency Found initrd image: /boot/initrd.img-5.0.0-13-lowlatency Found linux image: /boot/vmlinuz-5.0.0-13-lowlatency Found initrd image: /boot/initrd.img-5.0.0-13-lowlatency Found linux image: /boot/vmlinuz-4.15.18-041518-lowlatency Found initrd image: /boot/initrd.img-4.15.18-041518-lowlatency Found linux image: /boot/vmlinuz-4.15.18-041518-generic Found initrd image: /boot/initrd.img-4.15.18-041518-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Found Mac OS X on /dev/sda2 done So I expected to see 4.15 generic and low latency in addition to 5.0.0-13-lowlatency in my boot menu, but instead I see 5.0.9 (which even though I've removed vmlinux-5.0.9 starts to boot) and 5.0.13, 4.15.18 doesn't show up. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Apr 2019, Kai-Heng Feng wrote: > Date: Tue, 23 Apr 2019 05:12:05 - > From: Kai-Heng Feng > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Prebuilt binaries can be found here: > https://kernel.ubuntu.com/~kernel-ppa/mainline/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
I'm going to need a bit of help with respect to where to find old canonical kernel packages so I can find at what point it broke exactly. I did compile 5.0.9 from kernel.org source and it does reboot properly so I do know for certain that it is a kernel issue. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Mon, 22 Apr 2019, Kai-Heng Feng wrote: > Date: Mon, 22 Apr 2019 02:50:57 - > From: Kai-Heng Feng > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > If this doesn't happen to v4.15, please run a kernel bisection to find > the regression commit. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED]
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Yes. It has been an issue for a while. It was a problem with 16.04, 16.10, fixed in 17.04, 17.10, 18.04, broken again in 18.10 and 19.04. Since I installed the development release I thought I'd try to get to the bottom of it this time around. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Thu, 18 Apr 2019, Kai-Heng Feng wrote: > Date: Thu, 18 Apr 2019 09:38:13 - > From: Kai-Heng Feng > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > It can be a kernel bug. Do you see this issue if the system boots under > kernel v4.18? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-loc
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Yes, I've deleted the failing packages, game servers, debomatic, etc, or in one case masked it so systemd should not try to run it. On Tue, April 16, 2019 11:27 pm, Sebastien Bacher wrote: > see > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachmen > t/5256102/+files/SystemdFailedUnits.txt > > -- > You received this bug notification because you are subscribed to the bug > report. https://bugs.launchpad.net/bugs/1824893 > > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does not > affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash > vt.handoff=1 SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service â > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service â > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service â > /lib/systemd/system/user@.service.d/timeout.conf > > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnA > ppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:c > vnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscripti > ons > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalia
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Sorry, which faulty units are those? -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 16 Apr 2019, Sebastien Bacher wrote: > Date: Tue, 16 Apr 2019 14:23:23 - > From: Sebastien Bacher > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Thanks, I don't see anything obvious in the log, setting as New again > for now (would be good to see if removing the faulty units pointed in > the previous comment makes a difference though) > > ** Changed in: systemd (Ubuntu) > Status: Incomplete => New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/sy
Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
I've added the last 250 lines of the log, if that's not enough let me know. Once it says it's reached target reboot the next thing it does is send a kill signal to all processes, including journalctl so there is not much useful information beyond that point. Also I can not switch virtual terminals at that point, no keyboard input has any effects at that point including magic sys req key. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 16 Apr 2019, Sebastien Bacher wrote: > Date: Tue, 16 Apr 2019 08:49:56 - > From: Sebastien Bacher > Reply-To: Bug 1824893 <1824...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target > Reboot but then does not reboot > > Thank you for your bug report. Could you attach your journalctl log from > that shutdown to the bug? > > The log on > https://launchpadlibrarian.net/419441276/SystemdFailedUnits.txt also > shows that some systemd unit are failing on your system, maybe one of > those is creating the issue... > > (also when it's hanging can you switch into another vt for debugging?) > > ** Changed in: systemd (Ubuntu) > Importance: Undecided => Low > > ** Changed in: systemd (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824893 > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > Incomplete > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does > not affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 > SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service ÿÿ > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service ÿÿ > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service ÿÿ > /lib/systemd/system/user@.service.d/timeout.conf > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: Incomplete Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd6
[Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
** Attachment added: "Last 250 lines of journalctl log for shutdown" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachment/5256268/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: Incomplete Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824893] [NEW] When I type systemctl reboot system reaches Target Reboot but then does not reboot
Public bug reported: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1784969] Re: upowerd segfaults over and over again.
I am no longer running this version. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Fri, 15 Feb 2019, Sebastien Bacher wrote: > Date: Fri, 15 Feb 2019 15:27:30 - > From: Sebastien Bacher > Reply-To: Bug 1784969 <1784...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1784969] Re: upowerd segfaults over and over again. > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please try to obtain a backtrace following the > instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload > the backtrace (as an attachment) to the bug report. This will greatly > help us in tracking down your problem. > > ** Changed in: upower (Ubuntu) > Importance: Undecided => High > > ** Changed in: upower (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1784969 > > Title: > upowerd segfaults over and over again. > > Status in upower package in Ubuntu: > Incomplete > > Bug description: > [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp > 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] > [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp > 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] > [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp > 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] > [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp > 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] > [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp > 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] > [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp > 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] > [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp > 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] > [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp > 7fff74956fa0 error 4 in upowerd[561c77131000+39000] > [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp > 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] > [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp > 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] > [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp > 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: upower 0.99.7-2 > ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 > Uname: Linux 4.15.0-26-lowlatency x86_64 > ApportVersion: 2.20.9-0ubuntu7.3 > Architecture: amd64 > CurrentDesktop: MATE > Date: Wed Aug 1 01:55:16 2018 > SourcePackage: upower > UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1784969/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1784969 Title: upowerd segfaults over and over again. Status in upower package in Ubuntu: Incomplete Bug description: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+3900
Re: [Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path
I have since upgraded to 18.10 and I don't even see an apparmor profile
for ntp anymore.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 27 Nov 2018, Seth Arnold wrote:
> Date: Tue, 27 Nov 2018 01:07:37 -
> From: Seth Arnold <1727...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name
> lookup - disconnected path
>
> Andrew, you could try adding:
>
> flags=(attach_disconnected)
>
> to the profile attachment line:
>
> /usr/sbin/ntpd flags=(attach_disconnected) {
>
> And add:
>
> /run/systemd/journal/dev-log w,
>
> to the profile, then run:
>
> apparmor_parser --replace /etc/apparmor.d/usr.sbin.ntpd # or whatever
> the filename is
>
> See if that lets you get useful logs, any new messages in dmesg or
> auditd logs, etc.
>
> Thanks
>
> ** Also affects: openntpd (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1739943).
> https://bugs.launchpad.net/bugs/1727202
>
> Title:
> [17.10 regression] AppArmor ntp denial: Failed name lookup -
> disconnected path
>
> Status in ntp package in Ubuntu:
> Fix Released
> Status in openntpd package in Ubuntu:
> New
> Status in ntp source package in Xenial:
> Invalid
> Status in openntpd source package in Xenial:
> New
> Status in ntp source package in Zesty:
> Invalid
> Status in openntpd source package in Zesty:
> New
> Status in ntp source package in Artful:
> Fix Released
> Status in openntpd source package in Artful:
> New
> Status in ntp source package in Bionic:
> Fix Released
> Status in openntpd source package in Bionic:
> New
>
> Bug description:
> [Impact]
>
> * NTP has new isolation features which makes it trigger apparmor issues.
> * Those apparmor issues not only clutter the log and make other things
> less readable, they also prevent ntp from reporting its actual
> messages.
> * Fix is opening the apparmor profile to follow ntp through the
> disconnect by the isolation feature.
>
> [Test Case]
>
> * This is hard to trigger, but then also not. Which means it is not
> entirely sorted out when it triggers and when not, but the following
> does trigger it in tests of Pitti and also mine (while at the same time
> sometimes it does not - mabye I had other guests or kvm instead of lxd)
>
> * First install ntp in Artful (or above unless fixed)
> * Install ntp and check demsg for denies
> * Once an issue triggers instead of the error in syslog you'll see the
> apparmor Deny like:
> apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
> disconnected path" error=-13 profile="/usr/sbin/ntpd"
> name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
> requested_mask="w" denied_mask="w" fsuid=0 ouid=0
>
> [Regression Potential]
>
> * We are slightly opening up the apparmor profile which is far lower risk
> than adding more constraints. So safe from that POV.
>
> * OTOH one could think this might be a security issue, but in fact this
> isn't a new suggestion if you take a look at [1] with an ack by Seth of
> the Security Team.
>
> [Other Info]
>
> * n/a
>
> [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html
>
>
>
> Merely installing and starting ntp.service in Ubuntu 17.10 now causes
> this AppArmor violation:
>
> audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
> operation="sendmsg" info="Failed name lookup - disconnected path"
> error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
> pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
>
> (many times). This hasn't happened in earlier Ubuntu releases yet.
>
> This was spotted by Cockpit's integration tests, as our "ubuntu-
> stable" image now moved to 17.10 after its release.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> Date: Wed Oct 25 03:19:34 2017
> SourcePackage: ntp
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1727202
Title:
[17.10 regression] AppArmor ntp denial: Failed name lookup -
disconnected path
Status in ntp package in Ubuntu:
Fix
Re: [Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)
Sorry but I did a fresh install and is now working. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Wed, 24 Oct 2018, Daniel van Vugt wrote: > Date: Wed, 24 Oct 2018 09:04:23 - > From: Daniel van Vugt > Reply-To: Bug 1799203 <1799...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1799203] Re: [Mac-Pro 1, > 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to > Ubuntu 18.10) > > Can you please run this command: > > dpkg -l > dpkgl.txt > > and send us the resulting file? > > ** This bug is no longer a duplicate of bug 210472 > Timidity daemon doesn't play nice with pulse audio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799203 > > Title: > [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after > upgrading to Ubuntu 18.10) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from > 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions > at all. The kernel seems to detect the hadware okay: > > hwinfo --sound > 22: PCI 1b.0: 0403 Audio device >[Created at pci.378] >Unique ID: u1Nb.8PjrOxLnqG6 >SysFS ID: /devices/pci:00/:00:1b.0 >SysFS BusID: :00:1b.0 >Hardware Class: sound >Model: "Intel 631xESB/632xESB High Definition Audio Controller" >Vendor: pci 0x8086 "Intel Corporation" >Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" >Revision: 0x09 >Driver: "snd_hda_intel" >Driver Modules: "snd_hda_intel" >Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) >IRQ: 36 (119384 events) >Module Alias: "pci:v8086d269Asvsdbc04sc03i00" >Driver Info #0: > Driver Status: snd_hda_intel is active > Driver Activation Cmd: "modprobe snd_hda_intel" >Config Status: cfg=new, avail=yes, need=no, active=unknown > > But there is no sound output, pavucontrol does not show ANY hardware to > configure. I have > purged and reinstalled both pulseaudio and alsa to noavail, I"ve force > reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up > in pavucontrol and there is no audio output. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: pulseaudio 1:12.2-0ubuntu4 > Uname: Linux 4.18.0-10-lowlatency x86_64 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', > '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', > '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code > 1: > CurrentDesktop: MATE > Date: Mon Oct 22 04:11:54 2018 > LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: pulseaudio > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10) Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [Created at pci.378] Unique ID: u1Nb.8PjrOxLnqG6 SysFS ID: /devices/pci:00/:00:1b.0 SysFS BusID: :00:1b.0 Hardware Class: sound Model: "Intel 631xESB/632xESB High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporati
Re: [Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)
Ah okay well then it's a mystery, kernel could see it as hwinfo sound showed, pulse audio could not even after purging reinstalling it and alsa. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Oct 2018, Daniel van Vugt wrote: > Date: Tue, 23 Oct 2018 03:51:58 - > From: Daniel van Vugt > Reply-To: Bug 1799203 <1799...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1799203] Re: [Mac-Pro 1, > 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to > Ubuntu 18.10) > > It appears "AudioIPC Server" is actually Firefox. It shows up as such > in: > > Settings > Sound > Applications > > when Firefox is playing audio. > > So I don't think that's related to this bug at all. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799203 > > Title: > [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after > upgrading to Ubuntu 18.10) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from > 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions > at all. The kernel seems to detect the hadware okay: > > hwinfo --sound > 22: PCI 1b.0: 0403 Audio device >[Created at pci.378] >Unique ID: u1Nb.8PjrOxLnqG6 >SysFS ID: /devices/pci:00/:00:1b.0 >SysFS BusID: :00:1b.0 >Hardware Class: sound >Model: "Intel 631xESB/632xESB High Definition Audio Controller" >Vendor: pci 0x8086 "Intel Corporation" >Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" >Revision: 0x09 >Driver: "snd_hda_intel" >Driver Modules: "snd_hda_intel" >Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) >IRQ: 36 (119384 events) >Module Alias: "pci:v8086d269Asvsdbc04sc03i00" >Driver Info #0: > Driver Status: snd_hda_intel is active > Driver Activation Cmd: "modprobe snd_hda_intel" >Config Status: cfg=new, avail=yes, need=no, active=unknown > > But there is no sound output, pavucontrol does not show ANY hardware to > configure. I have > purged and reinstalled both pulseaudio and alsa to noavail, I"ve force > reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up > in pavucontrol and there is no audio output. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: pulseaudio 1:12.2-0ubuntu4 > Uname: Linux 4.18.0-10-lowlatency x86_64 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', > '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', > '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code > 1: > CurrentDesktop: MATE > Date: Mon Oct 22 04:11:54 2018 > LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: pulseaudio > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10) Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [Created at pci.378] Unique ID: u1Nb.8PjrOxLnqG6 SysFS ID: /devices/pci:00/:00:1b.0 SysFS BusID: :00:1b.0 Hardware Class: sound Model: "I
Re: [Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)
If you have the indicator Applet installed there are not one but three speaker symbols each doing different things, it shows up under the middle drop-down menu under Playback Streams. I'll be honest, I am not familiar with the internals of Ubuntu's audio system. Back in the old days when you had /dev/audio and you wrote to it, or used ioctl calls to change the bit rate or width, I could grock it, now it's too much of a hack for me to keep track of. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Oct 2018, Daniel van Vugt wrote: > Date: Tue, 23 Oct 2018 03:30:19 - > From: Daniel van Vugt > Reply-To: Bug 1799203 <1799...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1799203] Re: [Mac-Pro 1, > 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to > Ubuntu 18.10) > > I mean; what is "audioIPCServer"? Where are you seeing that? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799203 > > Title: > [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after > upgrading to Ubuntu 18.10) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from > 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions > at all. The kernel seems to detect the hadware okay: > > hwinfo --sound > 22: PCI 1b.0: 0403 Audio device >[Created at pci.378] >Unique ID: u1Nb.8PjrOxLnqG6 >SysFS ID: /devices/pci:00/:00:1b.0 >SysFS BusID: :00:1b.0 >Hardware Class: sound >Model: "Intel 631xESB/632xESB High Definition Audio Controller" >Vendor: pci 0x8086 "Intel Corporation" >Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" >Revision: 0x09 >Driver: "snd_hda_intel" >Driver Modules: "snd_hda_intel" >Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) >IRQ: 36 (119384 events) >Module Alias: "pci:v8086d269Asvsdbc04sc03i00" >Driver Info #0: > Driver Status: snd_hda_intel is active > Driver Activation Cmd: "modprobe snd_hda_intel" >Config Status: cfg=new, avail=yes, need=no, active=unknown > > But there is no sound output, pavucontrol does not show ANY hardware to > configure. I have > purged and reinstalled both pulseaudio and alsa to noavail, I"ve force > reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up > in pavucontrol and there is no audio output. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: pulseaudio 1:12.2-0ubuntu4 > Uname: Linux 4.18.0-10-lowlatency x86_64 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', > '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', > '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code > 1: > CurrentDesktop: MATE > Date: Mon Oct 22 04:11:54 2018 > LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: pulseaudio > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10) Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [C
Re: [Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10)
The in place upgrade did not install audioIPCServer but a fresh install did. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Oct 2018, Daniel van Vugt wrote: > Date: Tue, 23 Oct 2018 02:50:28 - > From: Daniel van Vugt > Reply-To: Bug 1799203 <1799...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1799203] Re: [Mac-Pro 1, > 1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to > Ubuntu 18.10) > > Can you please elaborate on where/how you see audio components missing > in the upgrade? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799203 > > Title: > [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after > upgrading to Ubuntu 18.10) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from > 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions > at all. The kernel seems to detect the hadware okay: > > hwinfo --sound > 22: PCI 1b.0: 0403 Audio device >[Created at pci.378] >Unique ID: u1Nb.8PjrOxLnqG6 >SysFS ID: /devices/pci:00/:00:1b.0 >SysFS BusID: :00:1b.0 >Hardware Class: sound >Model: "Intel 631xESB/632xESB High Definition Audio Controller" >Vendor: pci 0x8086 "Intel Corporation" >Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" >Revision: 0x09 >Driver: "snd_hda_intel" >Driver Modules: "snd_hda_intel" >Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) >IRQ: 36 (119384 events) >Module Alias: "pci:v8086d269Asvsdbc04sc03i00" >Driver Info #0: > Driver Status: snd_hda_intel is active > Driver Activation Cmd: "modprobe snd_hda_intel" >Config Status: cfg=new, avail=yes, need=no, active=unknown > > But there is no sound output, pavucontrol does not show ANY hardware to > configure. I have > purged and reinstalled both pulseaudio and alsa to noavail, I"ve force > reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up > in pavucontrol and there is no audio output. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: pulseaudio 1:12.2-0ubuntu4 > Uname: Linux 4.18.0-10-lowlatency x86_64 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', > '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', > '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code > 1: > CurrentDesktop: MATE > Date: Mon Oct 22 04:11:54 2018 > LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: pulseaudio > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10) Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [Created at pci.378] Unique ID: u1Nb.8PjrOxLnqG6 SysFS ID: /devices/pci:00/:00:1b.0 SysFS BusID: :00:1b.0 Hardware Class: sound Model: "Intel 631xESB/632xESB High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" Revision
Re: [Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not
It obviously would be good to have in place upgrades work properly. I can see after the re-install there are new components to the audio system that did not get installed by the upgrade, AudioIPCServer among others. However not a huge show stopper since work station is temporarily expendable and I do not have sound on servers. Also, sound via x2go works on servers even after in place upgrade. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 23 Oct 2018, Daniel van Vugt wrote: > Date: Tue, 23 Oct 2018 02:24:16 - > From: Daniel van Vugt > Reply-To: Bug 1799203 <1799...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1799203] Re: [Mac-Pro 1, > 1] Kernel Detects Sound Chip but PulseAudio does not > > Thanks for figuring that out. It sounds like the problem is now fixed > for you. > > I will now set the bug to Incomplete so it will stay open for 60 days > but close automatically thereafter if nobody else comments about the > issue. > > > ** Changed in: pulseaudio (Ubuntu) > Status: New => Incomplete > > ** Summary changed: > > - [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not > + [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after > upgrading to Ubuntu 18.10) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1799203 > > Title: > [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after > upgrading to Ubuntu 18.10) > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from > 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions > at all. The kernel seems to detect the hadware okay: > > hwinfo --sound > 22: PCI 1b.0: 0403 Audio device >[Created at pci.378] >Unique ID: u1Nb.8PjrOxLnqG6 >SysFS ID: /devices/pci:00/:00:1b.0 >SysFS BusID: :00:1b.0 >Hardware Class: sound >Model: "Intel 631xESB/632xESB High Definition Audio Controller" >Vendor: pci 0x8086 "Intel Corporation" >Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" >Revision: 0x09 >Driver: "snd_hda_intel" >Driver Modules: "snd_hda_intel" >Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) >IRQ: 36 (119384 events) >Module Alias: "pci:v8086d269Asvsdbc04sc03i00" >Driver Info #0: > Driver Status: snd_hda_intel is active > Driver Activation Cmd: "modprobe snd_hda_intel" >Config Status: cfg=new, avail=yes, need=no, active=unknown > > But there is no sound output, pavucontrol does not show ANY hardware to > configure. I have > purged and reinstalled both pulseaudio and alsa to noavail, I"ve force > reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up > in pavucontrol and there is no audio output. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: pulseaudio 1:12.2-0ubuntu4 > Uname: Linux 4.18.0-10-lowlatency x86_64 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', > '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', > '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code > 1: > CurrentDesktop: MATE > Date: Mon Oct 22 04:11:54 2018 > LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: pulseaudio > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not (after upgrading to Ubuntu 18.10) Status
Re: [Touch-packages] [Bug 1799203] Re: [Mac-Pro 1, 1] Kernel Detects Sound Chip but PulseAudio does not
On Mon, October 22, 2018 6:51 pm, Daniel van Vugt wrote: > ** Summary changed: > > > - Kernel Detects Sound Chip but PulseAudio does not > + [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not > > > ** Tags added: cosmic > > > -- > You received this bug notification because you are subscribed to the bug > report. https://bugs.launchpad.net/bugs/1799203 > > > Title: > [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not > > > Status in pulseaudio package in Ubuntu: > New > > > Bug description: > I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from > 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions > at all. The kernel seems to detect the hadware okay: > > hwinfo --sound 22: PCI 1b.0: 0403 Audio device > [Created at pci.378] > Unique ID: u1Nb.8PjrOxLnqG6 > SysFS ID: /devices/pci:00/:00:1b.0 > SysFS BusID: :00:1b.0 > Hardware Class: sound > Model: "Intel 631xESB/632xESB High Definition Audio Controller" > Vendor: pci 0x8086 "Intel Corporation" > Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" > Revision: 0x09 > Driver: "snd_hda_intel" > Driver Modules: "snd_hda_intel" > Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) > IRQ: 36 (119384 events) > Module Alias: "pci:v8086d269Asvsdbc04sc03i00" > Driver Info #0: > Driver Status: snd_hda_intel is active > Driver Activation Cmd: "modprobe snd_hda_intel" > Config Status: cfg=new, avail=yes, need=no, active=unknown > > > But there is no sound output, pavucontrol does not show ANY hardware to > configure. I have purged and reinstalled both pulseaudio and alsa to > noavail, I"ve force reloaded alsa, I've restarted pulseaudio. Nothing > makes the hardware show up in pavucontrol and there is no audio output. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: pulseaudio 1:12.2-0ubuntu4 > Uname: Linux 4.18.0-10-lowlatency x86_64 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', > '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', > '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', > '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit > code 1: CurrentDesktop: MATE > Date: Mon Oct 22 04:11:54 2018 > LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: pulseaudio > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnA > ppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:c > vnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799203/+subscri > ptions > This problem only occurs with an in-place upgrade. I did a fresh install and audio is working again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: [Mac-Pro 1,1] Kernel Detects Sound Chip but PulseAudio does not Status in pulseaudio package in Ubuntu: New Bug description: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [Created at pci.378] Unique ID: u1Nb.8PjrOxLnqG6 SysFS ID: /devices/pci:00/:00:1b.0 SysFS BusID: :00:1b.0 Hardware Class: sound Model: "Intel 631xESB/632xESB High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" Revision: 0x09 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) IRQ: 36 (119384 events) Module Alias: "pci:v8086d269Asvsdbc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown But there is no sound output, pavucontrol does not show ANY hardware to configure. I have purged and reinstalled both pulseaudio and alsa to noavail, I"ve force reloaded alsa, I've restarted pulseaudio. Nothing makes
[Touch-packages] [Bug 1799203] [NEW] Kernel Detects Sound Chip but PulseAudio does not
Public bug reported: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [Created at pci.378] Unique ID: u1Nb.8PjrOxLnqG6 SysFS ID: /devices/pci:00/:00:1b.0 SysFS BusID: :00:1b.0 Hardware Class: sound Model: "Intel 631xESB/632xESB High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" Revision: 0x09 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) IRQ: 36 (119384 events) Module Alias: "pci:v8086d269Asvsdbc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown But there is no sound output, pavucontrol does not show ANY hardware to configure. I have purged and reinstalled both pulseaudio and alsa to noavail, I"ve force reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up in pavucontrol and there is no audio output. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.18.0-10-lowlatency x86_64 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Mon Oct 22 04:11:54 2018 LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.family: MacPro dmi.product.name: MacPro2,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799203 Title: Kernel Detects Sound Chip but PulseAudio does not Status in pulseaudio package in Ubuntu: New Bug description: I have a 2006 vintage Mac-Pro 1,1. The audio has worked fine from 12.04 through 18.04, but upon upgrade to 18.10 it no longer functions at all. The kernel seems to detect the hadware okay: hwinfo --sound 22: PCI 1b.0: 0403 Audio device [Created at pci.378] Unique ID: u1Nb.8PjrOxLnqG6 SysFS ID: /devices/pci:00/:00:1b.0 SysFS BusID: :00:1b.0 Hardware Class: sound Model: "Intel 631xESB/632xESB High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x269a "631xESB/632xESB High Definition Audio Controller" Revision: 0x09 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xf2f0-0xf2f03fff (rw,non-prefetchable) IRQ: 36 (119384 events) Module Alias: "pci:v8086d269Asvsdbc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown But there is no sound output, pavucontrol does not show ANY hardware to configure. I have purged and reinstalled both pulseaudio and alsa to noavail, I"ve force reloaded alsa, I've restarted pulseaudio. Nothing makes the hardware show up in pavucontrol and there is no audio output. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.18.0-10-lowlatency x86_64 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Mon Oct 22 04:11:54 2018 LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio dmi.bios.date: 07/02/07 dmi.bios.vendo
[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab
This is affecting me as well but oddly not all hosts. One host will be problematic for a while then it will shift to another. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1577575 Title: NFS share does not mount on boot using fstab Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577575/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784969] [NEW] upowerd segfaults over and over again.
Public bug reported: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2 ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 Uname: Linux 4.15.0-26-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 1 01:55:16 2018 SourcePackage: upower UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1784969 Title: upowerd segfaults over and over again. Status in upower package in Ubuntu: New Bug description: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2 ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 Uname: Linux 4.15.0-26-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 1 01:55:16 2018 SourcePackage: upower UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1784969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1739943] [NEW] apparmor ntpd profile problem [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnect
Public bug reported: It would seem apparmor is denying ntpd access to log: [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor 2.11.0-2ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-22.25-lowlatency 4.13.13 Uname: Linux 4.13.0-22-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 24 01:02:15 2017 InstallationDate: Installed on 2017-08-14 (132 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) KernLog: ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-22-lowlatency root=UUID=a3646d61-5a64-4011-9bd5-bb806d3e3e8c ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to artful on 2017-10-19 (65 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1739943 Title: apparmor ntpd profile problem [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Status in apparmor package in Ubuntu: New Bug description: It would seem apparmor is denying ntpd access to log: [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor 2.11.0-2ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-22.25-lowlatency 4.13.13 Uname: Linux 4.13.0-22-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 24 01:02:15 2017 InstallationDate: Installed on 2017-08-14 (132 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) KernLog: ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-22-lowlatency root=UUID=a3646d61-5a64-4011-9bd5-bb806d3e3e8c ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to artful on 2017-10-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1739943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
