[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-17 Thread Jeff Turner
Sorry, turns out the /etc/systemd/system service file needs to be a symlink to trigger the bug. This will do it: su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service

[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-16 Thread Jeff Turner
Replicated on my local Ubuntu 20.04 system with systemd 245.4-4ubuntu3.1. It's a PEBCAK error where a user writes a .service file containing %i's, but instead of naming the file foo@bar.service, just names it foo.service. To replicate: cd /etc/systemd/system curl -s -o testemail2jira.service

[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-16 Thread Jeff Turner
Attached is /var/crash/_usr_lib_systemd_systemd.0.crash ** Attachment added: "/var/crash/_usr_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+attachment/5393190/+files/_usr_lib_systemd_systemd.0.crash -- You received this bug notification because

[Touch-packages] [Bug 1887744] [NEW] systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798

2020-07-15 Thread Jeff Turner
Public bug reported: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at

[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook

2018-01-18 Thread Jeff Turner
Logged at https://github.com/sickill/stderred/issues/63 ** Bug watch added: github.com/sickill/stderred/issues #63 https://github.com/sickill/stderred/issues/63 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook

2018-01-18 Thread Jeff Turner
I think I figured out the cause. Basically PEBCAK.. There's a program called stderred (https://github.com/sickill/stderred) which colorizes stderr to differentiate it from stdout, via a LD_PRELOAD hook. I have had this set for years in my ~/.bashrc: root@jturner-home:~# echo $LD_PRELOAD

[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files

2018-01-18 Thread Jeff Turner
Sure, I've attached update-initramfs -v output, and confirmed that the generated initrd is unusable, both with kvm and a real computer. ** Attachment added: "Output of 'update-initramfs -v' that generates an unusable initrd."

[Touch-packages] [Bug 1729836] [NEW] update-initramfs generating unbootable initrd files

2017-11-03 Thread Jeff Turner
Public bug reported: After running 'update-initramfs -u -k $(uname -r)', Linux will not boot. With 'quiet splash' set in grub, it appears to freeze after the 'Loading ramdisk...' message, and if booted in recovery mode, I see the following kernel panic: Freeing unused kernel memory: 948k Freeing

[Touch-packages] [Bug 1347504] [NEW] display screen keeps moving around when curser gets close to edge

2014-07-23 Thread Jeff Turner
Public bug reported: ithe display moves both up and sideways on all desktops i have installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia