In /etc/logcheck/ignore.d.server/syslogd, there is already a regular
expression to match these sorts of things:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd [.0-9]{5}#[0-9]+: restart
\(remote reception\)\.$
However, as the original poster points out, this regular expression does
not actually work
My gnome-system-tools menu items use gksu, as described above. However,
this stops them from working. I get the same problem that is described
in https://launchpad.net/distros/ubuntu/+source/sudo/+bug/5100 - it
tells me that my password is invalid. Running, for example, disks-admin
from a root
I installed from a Dapper liveCD a few days ago, and manually created my
partitions using the install program's tool. However, when I rebooted,
I got an error that is the equivalent of the old non-system disk or
disk error. Basically, none of my partitions were marked with the
bootable flag, and
I can confirm this on an Intel dual core Pentium. I synchronized my
clock with an NTP server on Friday, and started up NTP, which should
have kept it in sync. I rebooted today (Sunday) to install a video card,
and my clock is several hours wrong again - I suspect because it got set
from the
In /etc/logcheck/ignore.d.server/syslogd, there is already a regular
expression to match these sorts of things:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd [.0-9]{5}#[0-9]+: restart
\(remote reception\)\.$
However, as the original poster points out, this regular expression does
not actually work
** Changed in: logcheck (Ubuntu)
Status: Won't Fix = Confirmed
--
logcheck in dapper reports normal syslog restarts
https://bugs.launchpad.net/bugs/116773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Summary changed:
- update-initramfs is vulnurable to power loss
+ update-initramfs is vulnerable to power loss
--
update-initramfs is vulnerable to power loss
https://bugs.launchpad.net/bugs/197602
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm using a Lenovo R61i Thinkpad, and I have the same problem.
$ cat /etc/issue
Ubuntu 7.10 \n \l
$ xrandr
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request: 151 (RANDR)
Minor opcode of failed request: 6 ()
Serial number
I had the same problem - upgrading from feisty to gutsy on a xen box,
the postinst scripts for things like module-init-tools and procps were
failing with a segmentation fault:
# dpkg --configure procps
Setting up procps (1:3.2.7-3ubuntu5) ...
Segmentation fault
dpkg: error processing procps
Even after this, running update-rc.d (or even psql, the client for
postgresql) gave me segfaults.
I have now installed libc6-xen, and the segfaults go away.
The description for libc6-xen says This set of libraries is optimized
for the Xen hypervisor, and will be selected instead when running
As has been pointed out right at the top of the thread, GNOME has very
clear rules and guidelines about how applications should behave in order
to fit in with the rest of the environment:
http://developer.gnome.org/projects/gup/hig/
Currently, Rhythmbox violates those guidelines, as clearly
apticron's purpose is to be run by cron every so often, and check the
apt repositories.
It completely fails to run in edgy and feisty, because it uses dash-
incompatible bashisms, and edgy and feisty use dash.
Surely completely failing to run is at least equivalent to a crash?
--
Bashism in
I have a duplicatable crash, when moving from an article with a video
and two mp3 attachments to another one.
gdb backtrace isn't awfully useful, but...
[0279] main private debug: thread 2953206688 joined
(playlist/playlist.c:247)
[0278] main playlist debug: thread 2936421280 joined
I didn't say you should run update-java-alternatives. I am aware that
you do not want to overwrite the user's choices. This, however, is
exactly the problem. The user's choices are currently LOST, because the
path changes.
We need to keep the user's choices from upgrade to upgrade. If you
I did everything as described in:
https://help.ubuntu.com/community/UbuntuBackports
and:
http://ubuntuforums.org/showthread.php?t=153402
And you're rejecting this (perfectly valid) request because it's not
done via the right channel? What *is* the right channel, if I've done
something wrong?
Public bug reported:
I had sun-java5-jdk=1.5.0-08-0ubuntu1 installed, and selected as my
default JVM:
# ls -l /etc/alternatives/java.1.gz
lrwxrwxrwx 1 root root 59 2006-11-16 08:29 /etc/alternatives/java.1.gz -
/usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/man/man1/java.1.gz
I then received the
I don't think it's specific to sun-java5 - it would happen regardless of
which JDK was selected, and which was upgraded, wouldn't it? In fact,
it will actually happen to any /etc/alternatives link, whether java or
otherwise, which includes a version name in the path of the target.
--
java
17 matches
Mail list logo