Public bug reported:
Binary package hint: tomcat6
Using tomcat6 package version 6.0.24-2ubuntu, after editing
/etc/default/tomcat6 to set TOMCAT6_SECURITY=yes, Tomcat breaks on
startup with (in catalina.out):
Using CATALINA_BASE: /var/lib/tomcat6
Using CATALINA_HOME: /usr/share/tomcat6
** Patch added: Quilt patch to fix the security policy location in the init.d
script
http://launchpadlibrarian.net/50021809/fix-securitypolicy-location.patch
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50018111/Dependencies.txt
--
tomcat fails to start using a
** Patch added: Patch to fix debian/tomcat6.init so it doesn't redundantly set
security manager params
http://launchpadlibrarian.net/50021843/tomcat6.init.patch
--
tomcat fails to start using a security manager
https://bugs.launchpad.net/bugs/591802
You received this bug notification
I had the same problem, with apt-get persistently reporting 'Size
mismatch' errors when fetching files from a local repository containing
.debs naughtily rebuilt without revving the version number.
In my case, my ~/.dput.cf post_upload_command calls 'debarchiver -x',
which in turn calls
Hmm. Running Jaunty, I recently let it auto-update and now all the
default search engines have disappeared, leading my to this bug. I have
both the firefox-3.0 and firefox-3.5 packages installed:
$ dpkg -l | grep firefox
ii firefox
Public bug reported:
the package creates conflict
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: oxygen-icon-theme (not installed)
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
Date: Sun Jul 10 09:12:51 2011
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/808352
Title:
package oxygen-icon-theme (not installed) failed to install/upgrade:
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
To
Public bug reported:
Binary package hint: tomcat6
Using tomcat6 package version 6.0.24-2ubuntu, after editing
/etc/default/tomcat6 to set TOMCAT6_SECURITY=yes, Tomcat breaks on
startup with (in catalina.out):
Using CATALINA_BASE: /var/lib/tomcat6
Using CATALINA_HOME: /usr/share/tomcat6
** Patch added: Quilt patch to fix the security policy location in the init.d
script
http://launchpadlibrarian.net/50021809/fix-securitypolicy-location.patch
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50018111/Dependencies.txt
--
tomcat fails to start using a
** Patch added: Patch to fix debian/tomcat6.init so it doesn't redundantly set
security manager params
http://launchpadlibrarian.net/50021843/tomcat6.init.patch
--
tomcat fails to start using a security manager
https://bugs.launchpad.net/bugs/591802
You received this bug notification
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
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
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."
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
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
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The Icinga package provides an Apache config snippet,
/etc/icinga/apache2.conf, intended to be included in a vhost.
In the most recent release (icinga-1.14.2+ds) this snippet has incorrect
authentication headers that results in the web UI being unusable,
because no HTTP
Public bug reported:
I have a nsca-ng setup on localhost, with the only customization being a
'checker' identity configured in /etc/nsca-ng/nsca-ng.local.cfg:
authorize "checker" {
password = "s2LDCy4CiK6yrlcHhTXT6agFh067XYE3"
hosts = ".*"
services = ".*"
}
and corresponding
Public bug reported:
In /usr/share/nagios4/plugins/eventhandlers there are various handy
scripts, like disable_notifications, enable_notifications and
submit_check_result, which work by writing directly to the nagios.cmd
named pipe.
Currently they are broken:
#
*** This bug is a duplicate of bug 1889556 ***
https://bugs.launchpad.net/bugs/1889556
> 1. How can I boot the system from within the Grub rescue prompt? I
don‘t have a live System and can‘t get hands on one for several days.
You can't. The part of grub that loaded from the MBR (and printed
Has anyone on an EFI system experienced this bug? I'm only seeing BIOS-
based systems affected.
My servers were AWS EC2 instances where the 'grub rescue>' state is only
a screenshot. To recover you need to reattach the broken volume to a
rescue instance and 'grub-install' to the volume there.
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
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
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
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
** Description changed:
After updating grub2 (to 2.02~beta2-36ubuntu3.26) and rebooting, my
server does not boot:
Booting from Hard Disk 0...
error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue> _
I rebooted 3 servers in this way (all running Ubuntu
> How do I tell whether my grub is ok (without rebooting)?
I too would like to know this. I have a linode server with OS on
/dev/sda, that grub-install doesn't like:
root@radish-linode:~# grub-install /dev/sda
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't
** Description changed:
After updating grub2 (to 2.02~beta2-36ubuntu3.26) and rebooting, my
server does not boot:
Booting from Hard Disk 0...
- error: symbol `grub_callow' not found.
+ error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue> _
I rebooted 3
Public bug reported:
After updating grub2 (to 2.02~beta2-36ubuntu3.26) and rebooting, my
server does not boot:
Booting from Hard Disk 0...
error: symbol `grub_callow' not found.
Entering rescue mode...
grub rescue> _
I rebooted 3 servers in this way (all running Ubuntu 16.04.6 LTS) and
all
It's happened to me a few times on 20.04.1:
$ host support.coinjar.com
support.coinjar.com has address 0.0.0.0
support.coinjar.com has IPv6 address ::
29 matches
Mail list logo