Package: hylafax-server
Version: 1:4.2.1-5sarge1
I have upgraded from woody to sarge. Then I noticed some problems:
1. I found wrong symbolic link named bin in folder
/var/spool/hylafax/etc/ pointing to etc/bin. I have removed it.
2. I have changed file /var/spool/hylafax/etc/hosts.hfaxd.
Package: hylafax-server
Version: 2:4.3.1-7
Severity: normal
Script faxaddmodem generates faulty file config.ttyS0 for US Robotics
modem.
ATI0
5601
ATI3
U.S. Robotics 56K FAX EXT Rev. 11.16.63
Outgoing faxes are not send and error No local dialtone is displayed.
After digging a lot I found
***
I have upgraded samba. /var/log/aptitude says:
Aptitude 0.2.15.9: dziennik operacji
Fri Feb 17 17:42:54 2006
[UAKTUALNIONY] samba 3.0.14a-3 - 3.0.14a-3sarge1
[UAKTUALNIONY] samba-common 3.0.14a-3 - 3.0.14a-3sarge1
[UAKTUALNIONY] samba-doc 3.0.14a-3 -
Package: samba
Version: 3.0.14a-3sarge1
Severity: normal
I have upgraded samba. /var/log/aptitude says:
Aptitude 0.2.15.9: dziennik operacji
Fri Feb 17 17:42:54 2006
[UAKTUALNIONY] samba 3.0.14a-3 - 3.0.14a-3sarge1
[UAKTUALNIONY] samba-common 3.0.14a-3 -
Since this bug seems to not be reproducible, it is likely that we won't be
able to debug it based on this information. We can still hold the bug open
for a while, in case the problem happens for you again.
Yes -- this is the best solution for now.
It's interesting to note that, once
On 2005-11-11 I have upgraded my system Debian Woody to Debian Sarge. I
can see similar oplock problems in my log files since then as described
in a bug report. This makes our file-database crush every time.
Kernel: 2.4.18-686
Samba: 3.0.14a-Debian
From log.smbd:
[2006/02/06 07:40:19, 0]
situation.
Thanks for response.
Steve Langasek napisał(a):
On Mon, Feb 06, 2006 at 05:05:41PM +0100, Leszek Dubiel wrote:
On 2005-11-11 I have upgraded my system Debian Woody to Debian Sarge. I
can see similar oplock problems in my log files since then as described
in a bug report
Package: python-zsi
Version: 1.7-2
Severity: normal
Tool wsdl2py generates two files -- one for service description and one
for types description.
But service location is not handled properely, because it ignores
protocol name -- it assumes that http is used and port 80. I would
suggest to
Package: python-zsi
Version: 1.7-2
Severity: normal
Open python console:
from ZSI.ServiceProxy import ServiceProxy
service = ServiceProxy('https://www.ecod.pl/webserv2/EDIservice.asmx?WSDL')
Traceback (most recent call last):
File stdin, line 1, in ?
File
Subject: cupsys-bsd conflicts with rlinetd or depends on openbsd-inetd
Package: cupsys-bsd
Severity: normal
*** Please type your report below this line ***
I have upgraded my system and cupsys-bsd failed to finish configuration.
To solve the problem i have had to install openbsd-inetd.
I think
Subject: bash: problem trapping SIGPIPE
Package: bash
Version: 3.1dfsg-8
Severity: normal
*** Please type your report below this line ***
Please write a script:
#!/bin/bash
{
shopt
for s in $(seq 64); do
if trap 'true' $s; then
echo $s -- success;
When process gets killed you will be left with important.lock file still
there, and no other processes would be able to work.
Also when using timeout with -l option, then someone else could break
the lock: delete important.lock and create new important.lock file. So
command rm -f of the
Package: debfoster
Version: 2.7-1
Severity: normal
*** Please type your report below this line ***
Package libconsole has an important priority, but debfoster reports it
as an orphan.
# egrep ^MaxPriori /etc/debfoster.conf
MaxPriority = optional
# aptitude show libconsole | egrep Priori
Package: exim4
Version: 4.80-7
Severity: important
After upgradading debian to woody I started to get exim crashed for some
emails (a few emails for few thousand deliveries).
Email is delivered to exim, put into the queue, and never delivered.
Running the queue gives error message:
Woody has been out of support for, IIRC, ten years.
Sorry! This is wheezy, debian version 7.4.
That being said, signal 11 errors usually indicate faulty hardware,
most probably bad RAM or a bad CPU. Please check with memtest or other
tools.
Strange thing is that it started to occur
After upgrading from wheezy to jessie I was unable to boot, because
/boot/initrd.img-3.16.0-4-686-pae contained only script
/sbin/fsck.reiserfs, which called exec /sbin/reiserfsck -q $ADD_OPTS
$@, but /sbin/reiserfsck was missing in initrd file.
--
To UNSUBSCRIBE, email to
Package: perl
Version: 5.20.2-3+deb8u4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
The program
#!/usr/bin/perl
use utf8;
use locale;
use strict;
use warnings;
binmode
I have cut down my report to bare minimum:
# exim -be '${if crypteq{xxx}{aaa}{yes}{no}}'
no
# exim -be '${if crypteq{xxx}{$aaa}{yes}{no}}'
Failed: unknown variable name "aaa"
# exim -be '${if crypteq{xxx}{\$aaa}{yes}{no}}'
Segmentation fault
Subject: ca-certificates: on fresh debian install typical ssl session fails on
Thawte certificates
Package: ca-certificates
Version: 20141019+deb8u1
Severity: normal
Dear Maintainer,
After updating from Debian Jessie 8.2 to 8.3 some certificates got broken. When
I run command:
echo
Package: exim4
Version: 4.84-8+deb8u2
Severity: important
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Here's the script to reproduce error:
#!/bin/bash
exec 2>&1
printf '' >/tmp/mypassfile
The same bug with version 2:4.3.3+dfsg-2:
Selecting previously unselected package samba-common.
Preparing to unpack .../samba-common_2%3a4.3.3+dfsg-2_all.deb ...
*/var/lib/dpkg/tmp.ci/preinst: 5: [: =: unexpected operator**
*Unpacking samba-common (2:4.3.3+dfsg-2) ...
Selecting previously
Package: perl
Version: 5.20.2-3+deb8u6
Severity: normal
This is stripped out program version that causes error:
printf "\x41\x9c\x5a\x0a" | perl -CS -e '$_ = <>; /^(.*)$/ && print
"($1)\n"; /[^#]*/;'
It displays:
(A�Z)
Malformed UTF-8 character (fatal) at -e line 1,
This still happens with 5.24.1-1. It can be reduced to
printf "\x9c\x5a" | perl -CI -ne '/[^#]*/'
The byte sequence is indeed invalid utf8 (as shown by iconv as well),
but you're explicitly telling Perl (with -CS) that it's getting utf8 on
stdin. This is a recipe for problems.
So I'm not
Package: perl
Version: 5.20.2-3+deb8u6
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I am reading big string from file (2 megabytes), then add parentheses to
the beginning and end of that string, finally do parsing with regular
I see this on current sid/amd64 (Perl 5.24) too fwiw, and also in an
amd64 chroot with Perl 5.22. I've no idea why it goes away for you on
stretch. Can you confirm that? Are you only testing on i386 or on amd64
as well?
Problem goes away on "stretch", perl version "subversion 1 (v5.24.1)
At the present time that is the current expected behavior. I see no
bug here. Except for the bug of using escape sequences with echo.
But that is a bug in any shell script that uses it and not in either
bash or dash.
Bob
Please close the bug. I have found that it is echo behaviour instead
Package: bash
Version: 4.3-11+b1
Severity: normal
Dear Maintainer, :)
Create file /tmp/test that contains:
echo 'a\nb'
Now run this two commands:
sh /tmp/mytest
bash /tmp/mytest
One of these commands prints two lines while other prints one line:
root@orion:/tmp#
I confirm -- bug still happens very ocassionaly on version as below:
Exim version 4.84_2 #2 built 14-Jun-2017 14:38:31
Copyright (c) University of Cambridge, 1995 - 2014
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007
- 2014
Berkeley DB: Berkeley DB 5.3.28: (September
I solve this problem by adding notes to keepers file and I don't use
debfoster to update that file.
This is troublesome anyway...
root@orion:~# cat /var/lib/debfoster/keepers
# podstawowe działanie systemu, pakiety które jeśli nie są
zainstalowane, to system nie jest przyjemny, albo
#
Package: debfoster
Version: 2.7-2.1+b1
Severity: normal
Dear Maintainer,
I have clean installation, keepers file is updated, command "debfoster
-s" show NO packages.
Then I install package libdatetime-perl, add this package to keepers
list.
Debfoster -s shows:
root@orion:~#
Package: perl
Version: 5.24.1-3+deb9u2
Severity: normal
Dear Maintainer,
this optimization has bitten me once again, so I report this as a bug...
Run the code:
#!/usr/bin/perl -CSDA
use utf8;
use strict;
use warnings;
my %h;
$h{'Góry'} = 1;
'Góry' =~ /\A[[:alnum:]]*\z/ or die "error 1";
Package: btrfs-progs
Version: 4.20.1-2
Severity: normal
Dear Maintainer,
1. created some subvolumes, transfered them successfully to another BTRFS file
system with send/receive
2. created new subvolume, cp -a --reflink=always files, send to the same system
and got error
Another system has
I made further tests.
This system runs since 2018-02, so maybe it is spoiled from some bugs in
debian stretch (ver 9).
Checking disk took 68 hours:
# time btrfs check --mode=lowmem --progress /dev/sda1
Opening filesystem to check...
Checking filesystem on /dev/sda1
UUID:
Another test with "--repair" make BUG_ON:
time btrfs check --mode=lowmem --progress --repair /dev/sda1
enabling repair mode
WARNING: low-memory mode repair support is only partial
Opening filesystem to check...
Checking filesystem on /dev/sda1
UUID: 666a7089-d716-44ff-8081-56b969b58eff
[1/7]
This bug is not relevant in current stable release of debian.
Maybe something wash changed upstream.
Upstream but still open:
https://rt.perl.org/Public/Bug/Display.html?id=129802
Current test:
root@gamma:~# cat /etc/issue
Debian GNU/Linux 10 \n \l
root@gamma:~# perl --version
This is
Still happens with:
This is perl 5, version 28, subversion 1 (v5.28.1) built for
i686-linux-gnu-thread-multi-64int
(with 61 registered patches, see perl -V for more detail)
# printf "\x9c\x5a" | perl -CI -ne '/[^#]*/'
Malformed UTF-8 character: \x9c (unexpected continuation byte 0x9c,
Could you please try --mode=lowmem ? Besides requiring drastically less
memory, it's also a cleanish rewrite of the code, and seems quite mature
already. Thus, it's likely it can succeed where --mode=original fails.
Yes! It succeeded, although it took three days to finish, while copying
Package: btrfs-progs
Version: 4.20.1-2
Severity: normal
I was told some time ago to file a bug on this. When checking btrfs file
system I get below error. I have only one such faulty disk formatted
with BTRFS, so I don't have
any more details about this bug.
root@gamma# btrfs check /dev/sda1
Package: btrfs-progs
Version: 4.20.1-2
Severity: normal
I was told some time ago to file a bug on this.
When checking btrfs file system I get below error.
I have only one such faulty disk formatted with BTRFS, so I don't have
any more details about this bug.
root@gamma# btrfs check
Package: perl
Version: 5.24.1-3+deb9u5
Severity: normal
I was trying to make program below as simple as possible, but I don't
understand where is the bug introduced.
The task is to make a copy of hash such that keys in new hash are made only out
of alphanumerics and underscores "_". Hashes
Since 2017 I don't get that error anymore. Please close the bug.
Package: apt
Version: 1.8.2.1
Severity: normal
I've completely switched to using "apt" for all debian package management. I'm
fine with the "apt" tool, it fits all my needs except one... serarching.
For example I look for package to read/write JSON data in perl. In old days I
used the command
Package: fetchmail
Version: 6.4.0~beta4-3
Severity: normal
I restarted fetchmail with command:
# service fetchmail restart
but it didn't start. Then I tried:
# service fetchmail stop
# service fetchmail start
# invoke-rc.d fetchmail stop
# invoke-rc.d fetchmail start
#
W dniu 24.05.2020 o 18:49, Lee pisze:
You can use awk to put the lines together and then grep:
$ apt search perl | awk -v RS="" '{gsub("\n",""); print $0}' | grep
JSON | grep -i data
Yes... you're right.. but it's hard to remember... and I find myself
going back to "apt-cache" ...
W
Package: gnome-shell-extension-prefs
Version: 3.36.3-1
Severity: normal
Dear Maintainer,
I have standard Debian installation -- installed from scratch stable
distribution, upgraded to testing.
I was unable to go into preferences of any extension.
So I run from terminal gnome-tweaks to see
W dniu 31.10.2020 o 09:29, Matthias Andree pisze:
Control: tags -1 + moreinfo
fetchmail 6.4.13 contains some additional PID handling fixes, but it's
unclear whether those fixes address the issue described here. The logs
provided are insufficient. Please provide logs with full debug trace.
W dniu 01.11.2020 o 21:30, Matthias Andree pisze:
Hi Leszek,
Unfortunately, this has two issues:
1. part of it is in Polish, a language I cannot understand,
2. apparently the debug-run masks the bug. Please
2a. try creating a logfile,
2b. then configure fetchmail to log to the logfile
I have the same bug. All Images from google.com (notifications from
Google itself), or Allegro.pl (biggest online store in Poland) appear
broken.
Thunderbird version
# dpkg -l | egrep thunderb; cat /etc/issue
ii thunderbird 1:78.11.0-1 amd64 mail/news
> It results in a grub.cfg line like:
> linux /root/boot/vmlinuz-4.2.0-1-amd64
root=UUID=d430d7ee-8059-11e5-9834-502690aa641f ro rootflags=subvol=root
rootflags=degraded
> and apparently the 2nd rootflags= is simply ignored.
My tests shows that first "rootflags" is ignored, and the second
Package: btrfs-progs
Version: 4.20.1-2
Severity: minor
When one imports subvolume through btrfs send ... | btrfs receive ...
then snapshot gets "Received UUID" from remote system.
When you "btrfs sub snap -r ...", create readonly snapshot of received
snapshot, then "Received UUID" is
Network sometimes starts and quite often doesn't start and I have to
restart server manually:
ifupdown-pre.service: Main process exited, code=exited, status=1/FAILURE
# dpkg -l | grep ifupdown
ii ifupdown 0.8.35 amd64 high level tools
to configure network
Package: src:linux
Version: 5.10.84-1
Severity: normal
X-Debbugs-Cc: les...@dubiel.pl
After upgrading from bullseye to buster there is huge amount of errors:
[10122.779046] dmar_fault: 842 callbacks suppressed
[10122.779047] DMAR: DRHD: handling fault status reg 2
[10122.779060] DMAR: [DMA
Some more tests were done on:
- ubuntu 22.04 (5.15.0-23)
- ubuntu 20.04 (5.13.0-35)
- fedora 35 (5.14.10-300)
- debian 10 (4.19.0-19)
- debian 11 (5.10.0-11) - bash 5.1-2
- debian testing (5.16.0-5)
Error is only on debian 11.
If you upgrade bash 5.1-2 to 5.1-6 then but is resolved.
So the
I believe this is the same bug as reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003012 and upstream
in https://lists.gnu.org/archive/html/bug-bash/2022-01/msg0.html
Hmm... looks sililar. Thank you.
So what should we do now? Upgrade bash from testing? Or wait until
I have just upgraded to debian version 11.3.
Bug is still there:
root@orion:~# cat /etc/debian_version
11.3
root@orion:~# ./make_test.sh
there is a BUG on your system...
-xx-x--x-- 1 5551 2022-03-11 14:45:33.671864216 +0100
Some more info:
On Ubuntu 21.04 the bug is not present: bash has version
"5.1-2ubuntu1" and libc6 has version "2.33-0ubuntu5".
Server has been upgradeded to bullseye.
Booting takes 2 minutes... quite long...
> Could you please share your /etc/network/interfaces?
# cat /etc/network/interfaces
auto lo lan
iface lo inet loopback
iface lan inet static
address 192.168.18.3/21
gateway 192.168.18.1
# cat
Package: samba
Version: 2:4.13.13+dfsg-1~deb11u3
Severity: normal
After upgrade from buster to bullseye samba full audit started to log ALL
activity
despite opitons in /etc/samba/smb.conf stayed the same.
There are two options in /etc/samba/smb.conf
vfs objects = full_audit
Package: nmap
Version: 7.91+dfsg1+really7.80+dfsg1-2
Severity: normal
Nmap not working any more -- probably after upgrade to Bullseye:
# nmap -sP -oG - 192.168.16.0/21
# Nmap 7.80 scan initiated Thu May 5 08:56:54 2022 as: nmap -sP -oG -
192.168.16.0/21
nmap: Target.cc:503: void
Package: fail2ban
Version: 0.11.2-2
Severity: important
Hacker tries to guess user password on SMTP -- Exim4.
Then fail2ban stops blocking him, because it thinks there are "Too many errors".
This is not the case -- there are errors, because hackers are attacking.
I restart fail2ban manually
ot cleared,
and I'm surprised no one replied to your bug!
Leszek Dubiel writes:
Package: btrfs-progs
Version: 4.20.1-2
Severity: minor
When one imports subvolume through btrfs send ... | btrfs receive ...
then snapshot gets "Received UUID" from remote system.
When you "btrfs
Package: btrfs-progs
Version: 5.10.1-2
Severity: important
Hello :) :)
I am doing regular backukps send/receive.
I get a lot of messages like this:
WARNING: capabilities set multiple times per file: /mnt/sda2/2022-11-11
23:58:02 169205882/ZK_83308/Documents/fk-2228.jpg
WARNING:
Package: btrfs-progs
Version: 5.10.1-2
Severity: normal
When trying to replace device in BTRFS
different numbers of required free space are reported.
When using device name:
# btrfs replace start /dev/sda3 /dev/sdb3 /
ERROR: target device smaller than source device (required 5982920449536
Package: bsd-mailx
Version: 8.1.2-0.20180807cvs-2
Severity: normal
This command sends email correctly:
echo test | mail -s test leszek
Running this one displays error, but mail is sent anyway:
echo test | HOME="" mail -s test leszek
64 matches
Mail list logo
