Package: mailagent
Version: 1:3.1-81-4+b1
Severity: minor
Dear Maintainer,
The latest version of mailagent can be found at:
https://github.com/rmanfredi/mailagent.git
and fixes problems that will matter to people using the POST
action in their mailagent rules, when interfacing with the
Quoting Michael Biebl:
: What happens if you boot into emergency mode (add emergency to the
: kernel command line)?
: This will start a very minimal system without any networking or started
: services. Can you successfully login?
:
: What happens if you boot into rescue mode (add rescue to the
I quickly grepped through /etc/init.d/* files (I know systemd does
not use these anymore excepted when there is no unit and it calls
some of these scripts). There are many files that set a PATH explicitly
and which starts whith /usr/local/s?bin:
$ grep -l PATH=/usr/local/ /etc/init.d/*
Quoting Michael Biebl:
: Fwiw, you can use the builtin systemd autofs support.
: Define the network mount in /etc/fstab and add x-systemd.automount to
: the mount options. Would be interesting to know if you get the hangs as
: well then.
I tried to add the following line to /etc/fstab:
Quoting Michael Biebl:
: Could you uncomment those autofs mounts and try again?
I commented the line in /etc/auto.master.d/usr_local.autofs, to read:
#/auto/usr_local /etc/auto.master.d/usr_local--timeout=1800 --ghost
and it now works (I left the other autofs mountpoints since they are
Quoting Michael Biebl:
: Please boot with systemd as PID 1 and try to get a debug shell on tty9
: by adding systemd.debug-shell=1 to the kernel command line.
:
: On tty9 you can then inspect the system.
: The output of
: systemctl status dbus
: systemctl status systemd-logind
: systemctl
Package: systemd
Version: 232-25+deb9u6
Severity: important
Hello,
I recently upgraded my workstation from Debian 7 to Debian 9, and
enabled systemd. After the migration, everything worked fine.
My system froze this morning, so I rebooted and then after booting,
it did not display the XDM
Quoting Kurt Roeckx:
: > ii libssl1.0.0 1.0.1k-1
:
: You should really upgrade (or downgrade) that version. That's not
: from any release. It's from just before the jessie release and
: has many known security issues.
It's funny that "apt-get upgrade" is not proposing to upgrade it.
I just
Package: openssl
Version: 1.0.1e-2+deb7u20
Severity: important
After an "apt-get upgrade" in Debian wheezy, my openssl is unusable.
Launching:
$ openssl -v
openssl: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0: version
`OPENSSL_1.0.1s' not found (required by openssl)
Doing the
Package: uptimed
Version: 1:0.3.17-4
Followup-For: Bug #654830
Yes, I noticed the same strange thing recently. It was working fine
up to a few weeks (not sure exactly when it got wrong) but now the
boot entry has been duplicated and this creates impossible values,
as initially reported:
#
Hello Brian,
So your tests demonstrate that it may be a compiler optimization bug.
In order to confirm that, could you please try to compile xmalloc.c with -O3,
and see if it runs (the normal optimization is -O2).
Also, could you show in the bug report which compiler you are using and which
Hi Luca,
I'm building with gcc 4.8 here when developing, and it works fine.
I recommend building with gcc 4.8 or with clang, rather than removing
optimizations from xmalloc.c, which is a hotspot in the application!
Cheers,
Raphael
--
To UNSUBSCRIBE, email to
Brian,
It's bad news to know that the program runs without optimizations but
fails when compiled with optimizations: that either means the program
is incorrectly doing something undefined, that leads to this different
behaviour, or that some of the optimizations performed by the compiler
are
Hi Brian,
The gdb trace shows that compiler optimizations are preventing debugging:
some variables having been optimized out, and therefore their printed value,
if any, is inconsistent.
In order to remove optimizations in the malloc() implementation, you need to
go into the source tree of
Daniel,
This is a grave bug indeed. Since it appears very early in the
initialization process and I cannot reproduce it here obviously,
I am going to need your help to spot what is going on.
Obviously, you're going to have to run it through gdb, but you
need to go past the initial SIGSEGV
Dan,
The log.txt attached to the bug report shows that you're running under gdb
and gdb is getting a SIGSEGV, halting you in sig_compute_pc_index().
This is perfectly normal, as gtk-gnutella is triggering a SIGSEGV on purpose,
and trapping it, in order to compute where the current PC is stored
Package: xpdf
Version: Unable to install xpdf -- broken package dependencies
Severity: important
Trying to install xpdf from testing I get:
xpdf : Depends: libpoppler19 (= 0.18.4) but it is not going to be installed
Recommends: poppler-utils
E: Unable to correct problems, you
Package: mksh
Version: 46-2
Severity: normal
Logging with a shell set to mksh in /etc/passwd leads to weird behaviour:
hitting ^C kills the shell, and the session. This happens when logging on
the console, within an xterm, or remotely via ssh.
Workaround: running:
exec mksh
as the
Package: cups
Version: 1.5.3-1
Severity: important
Since upgrading from 1.3.x to 1.5.3, I now get the following error:
hp[1325]: prnt/backend/hp.c 839: ERROR: null print job total=0
whenever I try to print anything.
-- System Information:
Debian Release: squeeze/sid
APT prefers
Package: libc6-dev
Version: 2.13-27
Severity: important
The packaged ucontext.h file does a:
#include sys/ucontext.h
but that file is missing from the package, hence the ucontext.h header
cannot be included in programs.
-- System Information:
Debian Release: squeeze/sid
APT prefers
Quoting Jonathan Nieder:
: Raphael Manfredi wrote:
:
: The packaged ucontext.h file does a:
:
: #include sys/ucontext.h
:
: but that file is missing from the package, hence the ucontext.h header
: cannot be included in programs.
:
: $ dpkg-query -S /usr/include/i386-linux-gnu/sys
Bonjour Julien,
Quoting Julien ÉLIE:
Where is this error logged? (In mailagent?)
Yes, the error is logged in mailagent's .bak file, where plain stderr
messages go.
Does the error happen every time you POST a message via mailagent?
Yes.
Does the error happen if you directly use inews -h?
READER
200 tours.ram.loc InterNetNews NNRP server INN 2.5.3 (20110413 snapshot) ready
(posting ok)
POST
340 Ok, recommended message-ID jerj0f$76u$1...@tours.ram.loc
Date: Sat, 14 Jan 2012 08:07:51 +
From: Raphael Manfredi raphael_manfr...@pobox.com
Newsgroups: ml.lilypond.devel
Subject: test only
:07:51 +
From: Raphael Manfredi raphael_manfr...@pobox.com
Newsgroups: ml.lilypond.devel
Subject: test only
Message-ID: 20120114080751.GA1821@home
This message is a test.
.
235 Article transferred OK
QUIT
205 Bye!
Connection closed by foreign host.
Looks
Package: inn2
Version: 2.5.2+20110413-1+b2
Severity: normal
Since I upgraded to Perl 5.14.2, I get the following errors when
using mailagent's POST command (which calls inews -h to inject
the news message):
Remote error: Bizarre copy of UNKNOWN.
There must be something wrong with one of the
Package: dpkg-dev
Version: 1.15.8.8
Severity: grave
Justification: renders package unusable
The following happens when I attempt to install 1.16.1.2:
tar: unrecognized option `--warning=no-timestamp'
Try `tar --help' or `tar --usage' for more information.
dpkg-deb: error: subprocess tar returned
Package: glade-2
Version: 2.6.8-2
Severity: grave
Justification: renders package unusable
Running glade-2 now displays the following error:
--
Gtk-Message: Failed to load module gail
(glade-2:6322): Gtk-WARNING **: GtkSpinButton: setting an
Quoting Josselin Mouette:
: This package is no longer in unstable; it???s not even in squeeze.
Comment je maintiens le GUI GTK2 de gtk-gnutella maintenant alors?
Il y a un paquet de remplacement pour glade-2?
Raphael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Package: dansguardian
Version: 2.10.1.1-1
Severity: important
It is not possible to reload dansguardian dynamically (under the dansguardian
UID) by launching dansguardian -r or dansguardian -g. Both calls end-up
killing dansguardian altogether, with the following errors in syslog:
Package: dansguardian
Version: 2.10.1.1-1
Severity: normal
The French translation messages incorrectly use ecute; instead of the
correct eacute HTML escape for é.
Under vi messages, the following command fixes it:
:%s/ecute/\eacute/g
Thanks,
Raphael
-- System Information:
Debian
Hello Thomas,
: The info documentation is in the octave3.2-info package.
: Please indicate whether this solves your problems.
Indeed, after installing the octave3.2-info package, the doc command
was working. However, the info subsystem was not working properly
and I had to upgrade it (my
Package: octave3.2
Version: 3.2.3-1
Severity: normal
At the octave command prompt:
octave:1 doc
info: /usr/share/info/octave3.2.info: No such file or directory
I've queried all Debian packages, there is no package providing that file.
-- System Information:
Debian Release: lenny/sid
APT
Quoting Mark Purcell:
: On Friday 02 October 2009 22:05:54 Raphael Manfredi wrote:
: After upgrading to the new hplip, I'm no longer able to launch
: hp-devicesetup.
:
: I get the following messages:
:
: warning: Qt/PyQt 4 initialization failed.
: error: hp-devicesetup -u/--gui
Package: hplip
Version: 3.9.4b-1
Severity: grave
Justification: renders package unusable
After upgrading to the new hplip, I'm no longer able to launch hp-devicesetup.
I get the following messages:
warning: Qt/PyQt 4 initialization failed.
error: hp-devicesetup -u/--gui requires
Package: logcheck-database
Version: 1.3.3
Severity: normal
The violations.d/sudo pattern contains:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ sudo: .*$
This line is not catching explicit calls to /usr/bin/sudo since the
auth.log file will then contain:
Sep 17 15:50:54 tours /usr/bin/sudo: ram :
Package: logcheck
Version: 1.3.3
Severity: normal
After upgrading to the latest logcheck, I've noticed that some local
rules I have written no longer filter out the logs properly.
I've been able to correlate the non-matching to the presence of the
'/' (slash) character or '[' (left bracket) in
Package: initscripts
Version: 2.87dsf-2+b1
Severity: grave
Justification: causes non-serious data loss
I apt-geet install initscript and it failed to grab the corresponding
sysvinit-utils package.
This caused /sbin/fstab-decode to be missing and therefore /etc/init.d/umountfs
would not properly
Package: apt
Version: 0.7.21
Severity: important
I'm unable to update from unstable via apt-get update. I get:
W: Failed to fetch
http://http.us.debian.org/debian/dists/unstable/main/binary-i386/Packages.gz
Hash Sum mismatch
This is highly inconvenient because I can no longer rely on
Package: uptimed
Version: 1:0.3.16-1
Severity: normal
After seeing that my bug #482643 had been closed, I upgraded to the newest
version. Now when I type:
uprecords -a
I get:
# Uptime | System Boot up
Quoting Thibaut VARENE:
: BTW, if my assumption is right, it means that there's a binary
: incompatibility between versions of uptimed/libuptimed. I've forwarded
: upstream about this.
Upgrading libuptimed indeed fixed the problems. My old data now
show up properly, and the system name is indeed
Quoting Thibaut VARENE:
: I'm thinking about something broader:
: - keep the .old no matter what on each save
: - when starting, if there's a .old and no records then use the .old
: and print an alert message.
This is really required. After a power failure, my machine rebooted and
fsck did the
This bug has been closed by submission #43 in SVN.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Revision #44 of SVN closes this bug by protecting every . on a line by itself
if the -i option is not given to sendmail in the mailopt config variable.
The manual was updated to reflect this option, it is now supplied by default
when you install your initial configuration with mailagent -I and
Quoting Kartik Mistry:
: Is this similar to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384453 ?
: Please check.
I checked, but it's not related to that bug. Here the window continues to
be updated just fine, simply the CPU graph is reset, that is the existing
history on the left
Quoting Kartik Mistry:
: Thanks for reporting bug. I will discuss with upstream and let report know
: about progress.
I discovered accidentally that if there is a window partially covering the
xosview window, then a CPU frequency change does not cause a reset of the
CPU line. However, if
Package: initscripts
Version: 2.86.ds1-57
Severity: important
Since I upgraded my Debian systems to use initscripts, my NFS filesystems
are no longer mounted at boot time.
I see a:
Waiting for...
message with one of my mounted NFS partition at boot time on the console,
but it hangs
Quoting Petter Reinholdtsen:
: Can you provide the content of /etc/network/interfaces and /etc/fstab?
: NFS mounts are done when all interfaces are up. Are there some
: interfaces listed that are not brought up during boot?
I don't use /etc/network/interfaces on this machine. It uses the
old
Quoting Petter Reinholdtsen:
: [Raphael Manfredi]
: I don't use /etc/network/interfaces on this machine. It uses the
: old /etc/init.d/network hardwired configuration which says:
:
: Wow. I have never seen such setup, and it will not work with the
: current way NFS mounting is handled
Quoting Petter Reinholdtsen:
: The scripts involved are /etc/network/if-up.d/mountnfs and
: /etc/init.d/mountnfs.sh. The first do the real mounting when the last
: network interface is brought up, and the second wait for the first to
: complete before continuing the boot. Could it be that these
Package: uptimed
Version: 1:0.3.12-2
Severity: important
Apparently, uptimed is not updating its /var/spool/uptimed/records file
in a safe way: after a system crash, I have seen on many occasions fsck
clearing the corresponding inode and loosing all the uptime records.
The update procedure
Hello Thibaut,
Quoting Thibaut VARENE:
: [EMAIL PROTECTED] wrote:
: The update procedure should be something like:
:
: rename /var/spool/uptimed/records as /var/spool/uptimed/records.old
: write new data to /var/spool/uptimed/records.new
: fsync()
: rename
Package: xosview
Version: 1.8.3+debian-6
Severity: minor
I use CPU frequency scaling and whenver the CPU speed changes, xosview
resets the sliding bar showing the CPU load and restarts displaying on
the right. This is annoying, especially when the CPU speed changes
frequently.
-- System
Package: amanda-client
Version: 1:2.5.2p1-3
Severity: important
With the 2.5.2 client, I'm running:
amrecover -C normal -s b.example.com -t b.example.com -d /dev/ndat
And I get:
AMRECOVER Version 2.5.2p1. Contacting server on b.example.com ...
[request failed: error sending REQ: send
Quoting Bdale Garbee:
: severity 470202 important
: tags 470202 +moreinfo +unreproducible
: thanks
:
: Hello Raphael. Sorry you're having trouble with amanda. I don't see the
: problem here, so suspect there might be something unusual in your config
: files. Can you send me a copy of them to
Package: amanda-server
Version: 1:2.5.2p1-1
Severity: grave
Justification: renders package unusable
After upgrading from 2.5.1, my amcheck -c now fails with:
WARNING: paris: selfcheck request failed: error sending REQ: send REQ to
paris.ram.loc failed: Socket operation on non-socket
I did not
Quoting Atsuhito Kohda:
: what happend if you run
: sh -x /var/lib/dpkg/info/texlive-common.postinst configure
I get:
+ for i in updmap.d/10tetex-base.cfg fmt.d/01tetex.cnf language.d/00tetex.cnf
language.d/10tetex.cnf
+ '[' -r /etc/texmf/updmap.d/10tetex-base.cfg ']'
+ for i in
Package: texlive-latex-base
Version: 2007-11
Severity: important
Here is the error I get:
Setting up texlive-latex-base (2007-11) ...
Installing new version of config file
/etc/texmf/updmap.d/10texlive-latex-base.cfg ...
Running mktexlsr. This may take some time... done.
Running updmap-sys.
Quoting Ralf Stubner:
: Raphael Manfredi wrote:
: Package: texlive-latex-base
: Version: 2007-11
: Severity: important
: [...]
: (/usr/share/texmf-texlive/tex/generic/babel/hyphen.cfg
: ! I can't find file `ushyph1.tex'.
:
: Hmm, this bug looks identical to #435812, which should have been
Quoting Hilmar Preusse:
: For any reason your language.dat file
: (/var/lib/texmf/tex/generic/config/language.dat) contains an entry
: for the file ushyph1.tex, which is not provided by TeX Live.
:
: -rw-r--r-- 1 root root 12191 Aug 3 12:54
/var/lib/texmf/tex/generic/config/language.dat
:
:
Package: texlive-latex-base
Version: 2007-10
Severity: normal
Here's the error I get:
Setting up texlive-latex-base (2007-10) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Building format(s) --all --cnffile
Package: libsqlite3
Severity: normal
This is because the library is not compiled with the following cpp flag:
SQLITE_ENABLE_COLUMN_METADATA
As such, some of the metadata functions are not available even though they
are documented.
-- System Information:
Debian Release: testing/unstable
Same as Thomas. I don't use DailySet1, but my config was heavily inspired
by that template.
Also, things ran perfectly in 2.4.x until I upgraded to 2.5.x -- the only
thing that does not seem to work now is this email in case of problems.
Also, cron,log contains nothing unusual, just (CR is
Package: amanda-server
Version: 1:2.5.0-2
Severity: normal
I had no problem with 2.4.x. I upgraded to 2.5.0 without touching any
configuration file, and now I no longer get an e-mail when I run:
amcheck -mcw myconfig
and there is a problem, for instance no tape in the drive. Again,
+0200, Raphael Manfredi wrote:
: On my machine, procinfo displays:
: [...procinfo displaying 4 disks...]
: However, I have only *one* IDE disk on this machine.
:
: Do still experience this misbehavior with sysutils_1.3.8.5.1 as
: currently present in Woody (oldstable), Sarge (stable), Etch
...
:
: On Sun, 03 Jun 2001 23:30:21 +0200, Raphael Manfredi wrote:
: The amount of context switches seems to be followed by a stuck number
: that remains fixed, yielding an improper amount.
:
: For instance, my procinfo -d displays:
:
: context : 36382
:
: and a few seconds later
Package: twiki
Version: 20040902-3
Severity: important
Tags: patch
The following patch MUST be applied:
http://docs.indymedia.org/pub/Sysadmin/ImcDocsLog/fix_whitespace-20040901.diff
This makes the whole routine questionable -- this is rather amateurish code.
The patch above does fix the
66 matches
Mail list logo
