Bug#1055205: closed by Vincent Blut (Re: Bug#1055205: chrony: SysV problems after upgrade)

2023-11-02 Thread Richard Lucassen
On Thu, 02 Nov 2023 12:27:05 +
"Debian Bug Tracking System"  wrote:

Hello Vincent,

Ok, thnx for your explanation! I changed it to disable (and
indeed there is only a K link) and I'll see at the next upgrade.

Richard.

> This is an automatic notification regarding your Bug report
> which was filed against the chrony package:
> 
> #1055205: chrony: SysV problems after upgrade
> 
> It has been closed by Vincent Blut .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Vincent Blut
>  by replying to this email.
> 
> 


-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+------+
| Richard Lucassen, Utrecht|
+--+



Bug#1016006: dbus-daemon systemd dependency

2022-07-25 Thread Richard Lucassen
Package: dbus-daemon
Version: 1.14.0-1
Severity: critical
Justification: breaks unrelated software

Version 1.14.0-2 seems to depend on systemd which breaks my sys-V system and an 
update will remove many packages. There is no mention of a dependency change in 
the changelogs.

Richard.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dbus-daemon depends on:
ii  dbus-bin 1.14.0-1
ii  dbus-session-bus-common  1.14.0-1
ii  libapparmor1 3.0.4-3
ii  libaudit11:3.0.7-1+b1
ii  libc62.33-8
ii  libcap-ng0   0.8.3-1
ii  libdbus-1-3  1.14.0-1
ii  libexpat12.4.8-1
ii  libselinux1  3.4-1
ii  libsystemd0  251.2-7

dbus-daemon recommends no packages.

dbus-daemon suggests no packages.

-- no debconf information



Bug#959075: Still not working on Debian testing

2020-07-05 Thread richard lucassen
On Sun, 05 Jul 2020 09:58:46 +0800
Paul Wise  wrote:

> On Sat, 2020-07-04 at 18:08 +0200, richard lucassen wrote:
> 
> > Rereading it, I don't know if this issue was present in 2.9 or
> > earlier. I just noticed it while testing the new version.
> 
> Would you mind downgrading to 2.9 and testing it?
> You can install it from Debian buster or snapshot.d.o

I tried to find out which line causes this error and it is line 12
in /etc/network/if-pre-up.d/ifenslave:

ip link add dev "$IFACE" type bond

It has nothing to do with the ifenslave package:

# modprobe -rv bonding
rmmod bonding
# ip link add dev bond0 type bond
RTNETLINK answers: File exists

And ifenslave_2.9 loads the bonding module in "add_master()":

# If the bonding module is not yet loaded, load it.
if [ ! -r /sys/class/net/bonding_masters ]; then
    modprobe -q bonding
fi

HTH,

R.

-- 
richard lucassen
https://contact.xaq.nl/



Bug#959075: Still not working on Debian testing

2020-07-05 Thread richard lucassen
On Sun, 05 Jul 2020 09:58:46 +0800
Paul Wise  wrote:

> > Rereading it, I don't know if this issue was present in 2.9 or
> > earlier. I just noticed it while testing the new version.
> 
> Would you mind downgrading to 2.9 and testing it?
> You can install it from Debian buster or snapshot.d.o

No message indeed:

# wget
http://ftp.nl.debian.org/debian/pool/main/i/ifenslave/ifenslave_2.9_all.deb

# ifdown bond0

# modprobe -rv bonding

# dpkg --purge ifenslave

# dpkg -i ifenslave_2.9_all.deb

# ifup bond0
#

(no message)

# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v5.7.0-1-amd64

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth2 (primary_reselect always)
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0
ARP Polling Interval (ms): 2000
ARP IP target/s (n.n.n.n form): 10.234.0.33, 10.234.0.34

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:b1:1c:33:94:d8
Slave queue ID: 0

Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:b1:1c:33:94:d9
Slave queue ID: 0

-- 
richard lucassen
https://contact.xaq.nl/



Bug#959075: Still not working on Debian testing

2020-07-04 Thread richard lucassen
On Sat, 04 Jul 2020 13:41:33 +0800
Paul Wise  wrote:

> Is this a regression from 2.9 or just an old bug still present?

Rereading it, I don't know if this issue was present in 2.9 or earlier.
I just noticed it while testing the new version.

-- 
richard lucassen
https://contact.xaq.nl/



Bug#959075: Still not working on Debian testing

2020-07-04 Thread richard lucassen
On Sat, 04 Jul 2020 13:41:33 +0800
Paul Wise  wrote:

> > Ok, two remaining cometic issues in 2.11 than :-)
> 
> Sounds like the issue is fixed then, marked it as fixed.

Yep
 
> > # ifup bond0
> > /etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error
> > /etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error
> > 
> > You get this error when you try to set a /sys/ option that is not
> > allowed, but the script does not tell which option throws an error.
> > See diff attached.
> 
> I'll apply the patch you sent in another upload.

Maybe "[warning]" is better than "[error]"
 
> > Another cosmetic issue:
> > 
> > # ifdown bond0
> > # modprobe -rv bonding
> > rmmod bonding
> > # ifup bond0
> > RTNETLINK answers: File exists
> > # 
> 
> Is this a regression from 2.9 or just an old bug still present?

Still present.

R.


-- 
richard lucassen
http://contact.xaq.nl/



Bug#959075: Still not working on Debian testing

2020-07-03 Thread richard lucassen
On Fri, 03 Jul 2020 10:42:26 +0800
Paul Wise  wrote:

> > $ dpkg -l | grep ifenslave
> > ii  ifenslave2.10+nmu2
> > 
> > The lines "bond-slaves" and "bond-primary" still do not work:
> 
> Please retry your test with ifenslave 2.11.

Oops, sorry, I missed that one, I did not realize I'm on testing, not
sid :-(

Ok, two remaining cometic issues in 2.11 than :-)

# ifup bond0
/etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error
/etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error

You get this error when you try to set a /sys/ option that is not
allowed, but the script does not tell which option throws an error. See
diff attached. Example updelay and downdelay are apparently not allowed
using arp and this patch will tell you what went wrong:

iface bond0 inet static
address 10.234.0.33
netmask 255.255.255.0
network 10.234.0.0
broadcast 10.234.0.255
bond-slaves eth2 eth3
bond-mode active-backup
bond-primary eth2
bond-downdelay 200
bond-updelay 200
bond-arp_interval 2000
bond-arp_ip_target 10.234.0.32, 10.234.0.34

# ifup bond0
[error] unable to set downdelay to 200
[error] unable to set updelay to 200


Another cosmetic issue:

# ifdown bond0
# modprobe -rv bonding
rmmod bonding
# ifup bond0
RTNETLINK answers: File exists
# 

But when loading the kernel module before ifup then the RTNETLINK
error disappears:

# ifdown bond0
# modprobe -rv bonding
rmmod bonding
# modprobe -v bonding
insmod /lib/modules/5.7.0-1-amd64/kernel/drivers/net/bonding/bonding.ko 
# ifup bond0
# 

For the rest is seems to be ok now, thnx! :)

Just my 2 cts,

R.

-- 
richard lucassen
https://contact.xaq.nl/
--- /etc/network/if-pre-up.d/ifenslave	2020-07-02 10:35:20.0 +0200
+++ /etc/network/if-pre-up.d/ifenslave.new	2020-07-03 11:03:15.807658451 +0200
@@ -36,8 +36,10 @@
 	# $1 = basename of the file in bonding/ to write to.
 	# $2 = value to write. Won't write if $2 is empty.
 	if [ -n "$2" ] ; then
-		echo "$2" > "/sys/class/net/$BOND_MASTER/bonding/$1"
-		return $?
+		echo "$2" > "/sys/class/net/$BOND_MASTER/bonding/$1" 2>/dev/null
+		EXITCODE=$?
+		[ ${EXITCODE} -ne 0 ] && echo "[error] unable to set $1 to $2"
+		return ${EXITCODE}
 	fi
 	return 0
 }


Bug#959075: Still not working on Debian testing

2020-07-02 Thread richard lucassen
Debian testing:

$ dpkg -l | grep ifenslave
ii  ifenslave2.10+nmu2
all  configure network interfaces for parallel routing (bonding)


The lines "bond-slaves" and "bond-primary" still do not work:

iface bond0 inet static
address 10.234.0.32
netmask 255.255.255.0
network 10.234.0.0
broadcast 10.234.0.255
bond-slaves eth2 eth3
bond-mode active-backup
bond-primary eth2
bond-arp_interval 2000
bond-arp_ip_target 10.234.0.33, 10.234.0.34

# ifup bond0
# 

# cat /proc/net/bonding/bond0 
Ethernet Channel Bonding Driver: v5.7.0-1-amd64

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: None
MII Status: down
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0
ARP Polling Interval (ms): 2000
ARP IP target/s (n.n.n.n form): 10.234.0.33, 10.234.0.34

I miss the slaves eth2 and eth3, so I add them by manually:

# echo "+eth2" > /sys/class/net/bond0/bonding/slaves
# echo "+eth3" > /sys/class/net/bond0/bonding/slaves

[or:]

# ip link set eth2 master bond0
# ip link set eth3 master bond0

# echo eth2 > /sys/class/net/bond0/bonding/primary

# cat /proc/net/bonding/bond0 
Ethernet Channel Bonding Driver: v5.7.0-1-amd64

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth2 (primary_reselect always)
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0
ARP Polling Interval (ms): 2000
ARP IP target/s (n.n.n.n form): 10.234.0.33, 10.234.0.34

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:b1:1c:33:94:d8
Slave queue ID: 0

Slave Interface: eth3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:b1:1c:33:94:d9
Slave queue ID: 0


-- 
richard lucassen
http://contact.xaq.nl/



Bug#959075: Still not working on Debian testing

2020-06-26 Thread richard lucassen
Quick & Dirty workaround:

Add a line in /etc/network/if-pre-up.d/ifenslave just under #!/bin/sh

BOND_MASTER=$IFACE

The BOND_MASTER variable is empty.

-- 
richard lucassen
http://contact.xaq.nl/



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

2018-07-25 Thread richard lucassen
On Tue, 24 Jul 2018 21:51:21 +0200
Sebastian Andrzej Siewior  wrote:

> > That looks like a different issue.  Does it still happen if you
> > remove clamav-unofficial-sigs?
> 
> This is #902899, the strace shows
> 
> |clamd: yara_exec.c:177: yr_execu
> 
> so were done here :)

Yep, that did it :) Thnx!

R.

-- 
richard lucassen
http://contact.xaq.nl/



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

2018-07-24 Thread richard lucassen
On Tue, 24 Jul 2018 08:19:15 +0200
Sebastian Andrzej Siewior  wrote:

> Is the kernel complaining about something like in the other report
> where it claimed something about a deadlock?

No, no words like fanotify, deadlock or blocked appear in the logs.

I blocked and upgraded one of the (production) servers. After
upgrade clamd is running but as soon as a mail is received, it exits. I
ran an "strace -f -p " on a running clamd and sent a mail. The
output is here:

http://tmp.xaq.nl/clamd.strace

$ dpkg --get-selections | grep clam
clamav  install
clamav-base install
clamav-daemon   install
clamav-freshclaminstall
libclamav7:i386 install
libclamunrar7   install

plus a vanilla install of clamav-unofficial-sigs.

R.

-- 
richard lucassen
http://contact.xaq.nl/



Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

2018-07-23 Thread Richard Lucassen
Same here (6 Postfix front-end servers), non-systemd, non-GUI system
running Debian Stretch. Downgrading to 0.99 is a workaround.
ScanOnAccess is set to false.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+



Bug#745737: AW: Bug#745737: scli segfaults on show command

2015-02-07 Thread Richard Lucassen
On Fri, 25 Apr 2014 21:34:54 +0200 =?utf-8?Q?Stefan_Bauer?=
 wrote:
> -Ursprüngliche Nachricht-
> Von:  Richard Lucassen 
> > Here you are:
> > 
> > (gdb) run /usr/bin/scli
> > "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
> > 100 scli version 0.4.0 (c) 2001-2010 Juergen Schoenwaelder
> > 500 snmp: no access to '/usr/bin/scli': Permission denied
> 
> Richard,
> 
> can you check your permissions? Thats the first error message that
> jumps to my mind from your log.

Sorry for late reply, I missed this reply I fear. The permissions are
simply 755. Otherwise I could not be able to start scli, could I? :)

I wonder why I get a "permission denied", this is not what I'd expect.
Anyway, apparently something has changed in the meantime, querying an
Ubuntu-8.04 snmpd using scli under "testing" (I never removed the
package) now works properly.

Maybe it's better to assign this bug as closed and let scli enter
testing again (hope it's possible when testing is in freeze state)

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766920: initramfs-tools: update-initramfs makes system unbootable due to missing rootfs

2014-11-12 Thread Richard Lucassen
On Mon, 27 Oct 2014 00:54:54 +
Ben Hutchings  wrote:

> > Processing triggers for initramfs-tools (0.116) ...
> > update-initramfs: Generating /boot/initrd.img-3.16-3-amd64
> > /803: No such file or directory
> > [update continues]
> > 
> > After a reboot, the system is unbootable due to a missing rootfs.
> [...]
> 
> We support hexadecimal device numbers in the 'root=' kernel parameter
> when booting, but do not expect to see them at build time in the mount
> table.

[..]

> You are recommended to specify the root device on the kernel command
> line using the syntax 'root=UUID=...'

Setting fstab to UUID does not make any difference, OTOH, setting
lilo.conf to root="UUID=x" resolves the problem. The command "mount"
does not show up with "803" anymore.

As an initramfs nitwit, I'd say it seems to be a bug anyway. Am I right
or wrong?

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766920: initramfs-tools: update-initramfs makes system unbootable due to missing rootfs

2014-10-27 Thread Richard Lucassen
On Mon, 27 Oct 2014 00:54:54 +
Ben Hutchings  wrote:

> > After a reboot, the system is unbootable due to a missing rootfs.
> [...]
> 
> We support hexadecimal device numbers in the 'root=' kernel parameter
> when booting, but do not expect to see them at build time in the mount
> table.
> 
> Please provide the output of 'mount' on one such system.

Sorry, I forgot to mention that:

# mount | grep 803
803 on / type ext4
(rw,noatime,nodiratime,discard,errors=remount-ro,data=ordered)

(this is another system that had the same problem btw)
 
> You are recommended to specify the root device on the kernel command
> line using the syntax 'root=UUID=...'

I use lilo:

boot=/dev/sda
root=/dev/sda3
map=/boot/map
delay=20
compact
prompt
timeout=20
default=Linux

image=/vmlinuz
label=Linux
read-only
initrd=/initrd.img

[..]

I tried both, UUID= and /dev/sda3 in /etc/fstab, but the result was the
same. I haven't tried lilo.conf yet. I'll let you know.

BTW, UUID is great for mounting removable devices, but for fixed
devices it may be problem: you cannot simply copy images to a disk
without adapting the UUID. E.g.: I run a big number of devices and the
disks are copies of a central image. Using UUID would make things more
complex than using /dev/sdX in that case.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766920: initramfs-tools: update-initramfs makes system unbootable due to missing rootfs

2014-10-26 Thread Richard Lucassen
Package: initramfs-tools
Version: 0.116
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

During an update, this is what I see:

[..]
Processing triggers for initramfs-tools (0.116) ...
update-initramfs: Generating /boot/initrd.img-3.16-3-amd64
/803: No such file or directory
[update continues]

After a reboot, the system is unbootable due to a missing rootfs. As you can
see below, the root fs is 803 (which in fact is /dev/sda3)

A workaround is to set a symlink:

# ln -s /dev/root /803

After that, run:

# dpkg-reconfigure linux-image-3.16-3-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16-3-amd64
/etc/kernel/postinst.d/zz-runlilo:
Warning: LBA32 addressing assumed
Added Linux  *
Added LinuxOLD
Added memtest
One warning was issued.

I've seen this issue on a few systems running Debian Testing. In all cases it
was /dev/sda3 as rootfs.

Richard.

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.8M Sep 24 18:07 /boot/initrd.img-3.14-2-amd64
-rw-r--r-- 1 root root 4.1M Oct 26 21:14 /boot/initrd.img-3.16-2-amd64
-rw-r--r-- 1 root root 4.1M Oct 26 21:23 /boot/initrd.img-3.16-3-amd64
-- /proc/cmdline
auto BOOT_IMAGE=Linux ro root=803

-- resume
RESUME=UUID=eb986d31-94bc-4e46-b772-d2171f5b7cf0
-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
unix_diag  12521  0 
tcp_diag   12512  0 
inet_diag  17340  1 tcp_diag
nf_conntrack_netlink35433  0 
xt_connmark12637  1 
ipt_REJECT 12465  2 
xt_set 13071  2 
ip_set_hash_ip 25974  1 
ip6t_REJECT12468  2 
xt_NFLOG   12462  7 
ip_set 34886  2 ip_set_hash_ip,xt_set
nfnetlink_log  17201  2 xt_NFLOG
nfnetlink  12989  5 nfnetlink_log,ip_set,nf_conntrack_netlink
nf_conntrack_ipv6  13605  6 
nf_defrag_ipv6 33358  1 nf_conntrack_ipv6
xt_tcpudp  12527  21 
xt_length  12460  3 
xt_limit   12601  3 
xt_conntrack   12681  11 
iptable_filter 12536  1 
iptable_nat12646  0 
nf_conntrack_ipv4  18455  7 
nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
nf_nat_ipv412912  1 iptable_nat
ip6table_filter12540  1 
ip6table_mangle12540  0 
iptable_mangle 12536  1 
ip6_tables 26025  2 ip6table_filter,ip6table_mangle
ip_tables  26011  3 iptable_filter,iptable_mangle,iptable_nat
x_tables   27111  15 
ip6table_filter,ip6table_mangle,xt_length,ip_tables,xt_tcpudp,xt_NFLOG,xt_limit,xt_conntrack,xt_set,iptable_filter,xt_connmark,ipt_REJECT,iptable_mangle,ip6_tables,ip6t_REJECT
hid_generic12393  0 
usbhid 44467  0 
hid   102264  2 hid_generic,usbhid
sr_mod 21903  0 
cdrom  47424  1 sr_mod
ata_generic12490  0 
iTCO_wdt   12831  0 
iTCO_vendor_support12649  1 iTCO_wdt
evdev  17445  1 
ehci_pci   12512  0 
uhci_hcd   43499  0 
ehci_hcd   69837  1 ehci_pci
coretemp   12820  0 
hpilo  16902  0 
usbcore   195340  4 uhci_hcd,ehci_hcd,ehci_pci,usbhid
ata_piix   33592  0 
kvm_intel 139077  0 
acpi_power_meter   17372  0 
libata177457  2 ata_generic,ata_piix
kvm   388597  1 kvm_intel
radeon   1336879  1 
sg 29973  0 
ttm69670  1 radeon
drm_kms_helper 49210  1 radeon
e1000e203664  0 
drm   249955  4 ttm,drm_kms_helper,radeon
ptp17692  1 e1000e
pps_core   17225  1 ptp
pcspkr 12595  0 
hpwdt  12894  0 
psmouse98616  0 
serio_raw  12849  0 
i2c_algo_bit   12751  1 radeon
i2c_core   46012  4 drm,drm_kms_helper,i2c_algo_bit,radeon
lpc_ich20768  0 
mfd_core   12601  1 lpc_ich
bnx2   83625  0 
i7core_edac22278  0 
ipmi_si48709  0 
edac_core  47369  2 i7core_edac
ipmi_msghandler39917  1 ipmi_si
crc32c_intel   21809  0 
usb_common 12440  1 usbcore
button 12944  0 
processor  28221  0 
nf_nat_ftp 12460  0 
nf_conntrack_ftp   16783  1 nf_nat_ftp
nf_nat_tftp12422  0 
nf_nat 18241  4 nf_nat_ftp,nf_nat_ipv4,nf_nat_tftp,iptable_nat
nf_conntrack_tftp  12433  1 nf_nat_tftp
nf_conntrack   87432  12 
nf_nat_ftp,nf_nat,nf_nat_ipv4,nf_nat_tftp,xt_conntrack,nf_conntrack_netlink,xt_connmark,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4,nf_conntrack_ipv6,nf_conntrack_tftp
8021q  27858  0 
garp   13117 

Bug#745737: scli segfaults on show command

2014-04-24 Thread Richard Lucassen
Package: scli
Version: 0.4.0-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When a server is queried for a large number of entries, scli segfaults. I've 
seen this on Debian Wheezy and Debian testing, both querying Ubuntu-8.04-LTS 
servers as well as Debian Wheezy servers. When a query is sent to an 
unconfigured Debian snmp server (system info only), everything seems to be ok.

$ scli 172.18.0.1
100 scli version 0.4.0 (c) 2001-2010 Juergen Schoenwaelder
(172.18.0.1) scli > show
500 noResponse 3.57 vpm
500 noResponse 3.75 vpm
500 noResponse 3.89 vpm
Segmentation fault1 vpm
$ 

Richard.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages scli depends on:
ii  libc6 2.18-4
ii  libglib2.0-0  2.40.0-2
ii  libgnet2.0-0  2.0.8-2.2
ii  libgsnmp0 0.3.0-2
ii  libncurses5   5.9+20140118-1
ii  libreadline6  6.3-6
ii  libtinfo5 5.9+20140118-1
ii  libxml2   2.9.1+dfsg1-3

scli recommends no packages.

scli suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#724609: wmbattery stopped working with kernel 3.10-3

2013-10-01 Thread richard lucassen
[addendum]

The wmbattery compiled from git displays 70% of charge while "acpi"
shows 100%. And the battery is definitly charged at 100%.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#724609: [workaround] wmbattery stopped working with kernel 3.10-3

2013-10-01 Thread richard lucassen
$ git clone git://git.kitenet.net/wmbattery

compiling from the git source makes wmbattery work again.

R.

-- 
__
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#724609: wmbattery stopped working with kernel 3.10-3

2013-10-01 Thread richard lucassen
Oops, indeed, it's got nothing to do with the kernel.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#712414: openvpn: UDP server stops after update to "2.2.1-8+deb7u1"

2013-06-15 Thread Richard Lucassen
Package: openvpn
Version: 2.2.1-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After an upgrade, all tunnels to a UDP server stopped working. Here's what's in 
the logs:

Jun 15 18:32:58 server-10.250.3.0-udp-1195-tun2[21034]: 1.2.3.4:36595 TLS 
Error: TLS key negotiation failed to occur within 60 seconds (check your 
network connectivity)

Jun 15 18:32:58 server-10.250.3.0-udp-1195-tun2[21034]: 1.2.3.4:36595 TLS 
Error: TLS handshake failed

Jun 15 18:32:58 server-10.250.3.0-udp-1195-tun2[21034]: 1.2.3.4:36595 
SIGUSR1[soft,tls-error] received, client-instance restarting

And lots of these:

Jun 15 18:32:56 server-10.250.3.0-udp-1195-tun2[21034]: 1.2.3.4:36595 write 
UDPv4 []: Invalid argument (code=22)

There were two instances of an OpenVPN server that stopped working. Downgrading 
to the previous version (2.2.1-8) resolved the problem.

R.

-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.7 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  initscripts2.88dsf-41
ii  libc6  2.13-38
ii  liblzo2-2  2.06-1
ii  libpam0g   1.1.3-7.1
ii  libpkcs11-helper1  1.09-1
ii  libssl1.0.01.0.1e-2
ii  net-tools  1.60-24.2

openvpn recommends no packages.

Versions of packages openvpn suggests:
ii  openssl 1.0.1e-2
pn  resolvconf  

-- debconf information:
  openvpn/create_tun: false


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#555325: gq: version 1.3.4 completely unusable

2009-11-09 Thread richard lucassen
Package: gq
Version: 1.3.4
Severity: grave

Debian testing on an amd64:

After a few crashes the first minutes I threw away all ~/.gq* files and
directories. I tried to add a new server. Impossible to enter the bind
dn. It simply forgets it. On the first search it crashes. I have seen
about 10 crashes in the very few first 10 minutes. This is completely
unusable. This version should never have been transferred to testing
IMHO. In this state it is better to remove gq completely.

Workaround: get the sources from the oldstable repository, recompile it
and downgrade to 1.0. Do not forget to:

echo gq hold | dpkg --set-selections

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#554358: apt-get update segfaults on Etch, testing, on i386 and amd64 [notabug]

2009-11-04 Thread richard lucassen
Was a corrupted diff file. Plae change to notabug

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#554358: apt-get update segfaults on Etch, testing, on i386 and amd64

2009-11-04 Thread richard lucassen
Package: apt
Version: 0.7.23.1
Severity: grave

Since this morning. Seen on machines running Etch, testing, both on i386
and amd64:

# apt-get update
Hit http://abcx.utr.xaq.nl testing Release.gpg
[..]
Get:11 http://abcx.utr.xaq.nl unstable/main 2009-11-04-0016.39.pdiff
[5,001kB] E: Method rred has died unexpectedly! 
E: Sub-process rred received a segmentation fault.

On Sarge and Ubuntu-8.04-LTS: no problem.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#551355: gpsim crashes on loading a cod file since update glibc

2009-10-20 Thread richard lucassen
libgtk2 problem. See bug 551762:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551762

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#551355: gpsim crashes on loading a cod file since update glibc

2009-10-19 Thread richard lucassen
addition: only the windows RAM and EEPROM cause the crash.

Reproduce:

1) throw away ~/.gpsim

2) start gpsim

3) open RAM window

4) open .cod file

5) crash

Items 3) and 4) may be inversed.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#551355: gpsim crashes on loading a cod file since update glibc

2009-10-19 Thread richard lucassen
Reproduce:

1) throw away ~/.gpsim

2) start gpsim

3) open RAM window

4) open .cod file

5) crash

Items 3) and 4) may be inversed.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#551355: gpsim crashes on loading a cod file sind update glibc

2009-10-19 Thread richard lucassen
Apparently this only occurs when the source code window is actvated. I
threw away the ~/.gpsim and reconfigured gpsim. For the moment I'm not
able to reproduce it.

To be continued (?)

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#551355: gpsim crashes on loading a cod file sind update glibc

2009-10-17 Thread Richard Lucassen
The version reported is 0.24, but this is a vanilla version installed
with "checkinstall". The original deb sources (0.22) run into the same
problems.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#551355: gpsim crashes on loading a cod file sind update glibc

2009-10-17 Thread Richard Lucassen
Package: gpsim
Version: 0.24.0-1
Severity: grave
Justification: renders package unusable

After an update last week, gpsim has become unusable. As soon as a cod file is 
loaded, gpsim crashes:

*** glibc detected *** gpsim: realloc(): invalid pointer: 0xb7acd2ae ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb71cb8f4]
/lib/i686/cmov/libc.so.6(realloc+0x242)[0xb71d0332]
/lib/libglib-2.0.so.0(g_realloc+0x3a)[0xb738b02a]
[snip]

I have seen this on an amd64 and an i386 system. Recompiling the source deb 
makes no difference. Even the latest vanilla 0.24: same problem. Maybe it's not 
a gpsim problem but a glibc problem, but the package is unusable now.

R.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#526874: Dependency error in Etch volatile

2009-05-04 Thread richard lucassen
Package: libclamav-dev
Version: 0.95.1+dfsg-0volatile2
Severity: serious

There's a problem in the volatile Etch reository. When updating
libclamav to the newest volatile version, I get this:

The following packages have been kept back:
  libclamav-dev

An "apt-get dist-upgrade" gives the same message. However, an "apt-get
install libclamav-dev" gives: 

The following packages have unmet dependencies:
  libclamav-dev: Depends: libtommath-dev but it is not installable

Well, there's the problem, libtommath is only available in Lenny and
higher. An "apt-get -b source libtommath" from the testing repository
gives dependency errors (debhelper > 6)

Libclamav-dev is needed to build the latest version of havp (a scanning
proxy), which is (unfortunately) not in the volatile project (in which
it should be IMHO ;-)

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+----------+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#453102: samba mount from Windows does not show all directories and files

2007-12-05 Thread richard lucassen
Samba 3.0.14a-3sarge10 still has the same problem as reported for
3.0.14a-3sarge9: some directories and files aren't shown in the windows
explorer.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]