Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard
I can confirm the problem on light system Fujitsu Futro S720 with Radeon HD 8280E (Kabini). Downgrade mesa packages solved the problem ( deb https://snapshot.debian.org/archive/debian/20240214T00Z/ sid main contrib non-free non-free-firmware added to apt sources and then aptitude -o Acquire::Check-Valid-Until=false … ) Aptitude 0.8.13: log report Tue, Mar 5 2024 20:00:47 +0100 IMPORTANT: this log only lists intended actions; actions which fail due to dpkg problems may not be completed. Will install 9 packages, and remove 0 packages. 3869 kB of disk space will be freed [HOLD, DEPENDENCIES] libgtk2.0-common:amd64 2.24.33-3 [HOLD, DEPENDENCIES] occt-misc:amd64 7.6.3+dfsg1-7 [DOWNGRADE] libegl-mesa0:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] libgbm1:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] libgl1-mesa-dri:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] libglapi-mesa:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] libglx-mesa0:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] libxatracker2:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] mesa-va-drivers:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] mesa-vdpau-drivers:amd64 24.0.2-1 -> 23.3.5-1 [DOWNGRADE] mesa-vulkan-drivers:amd64 24.0.2-1 -> 23.3.5-1 -- Zito [ 353.611] X.Org X Server 1.21.1.11 X Protocol Version 11, Revision 0 [ 353.611] Current Operating System: Linux futro2 6.7.7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.7.7-1 (2024-03-02) x86_64 [ 353.611] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.7.7-amd64 root=UUID=da2fd605-3371-4cba-b986-a2e2711eb69f ro [ 353.612] xorg-server 2:21.1.11-2 (https://www.debian.org/support) [ 353.612] Current version of pixman: 0.42.2 [ 353.612]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 353.612] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 353.612] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 5 19:51:19 2024 [ 353.613] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 353.613] (==) No Layout section. Using the first Screen section. [ 353.613] (==) No screen section available. Using defaults. [ 353.613] (**) |-->Screen "Default Screen Section" (0) [ 353.613] (**) | |-->Monitor "" [ 353.614] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 353.614] (==) Automatically adding devices [ 353.614] (==) Automatically enabling devices [ 353.614] (==) Automatically adding GPU devices [ 353.614] (==) Automatically binding GPU devices [ 353.614] (==) Max clients allowed: 256, resource mask: 0x1f [ 353.614] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 353.614]Entry deleted from font path. [ 353.614] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 353.614] (==) ModulePath set to "/usr/lib/xorg/modules" [ 353.614] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 353.614] (II) Loader magic: 0x55cdf6a59f00 [ 353.614] (II) Module ABI versions: [ 353.614]X.Org ANSI C Emulation: 0.4 [ 353.614]X.Org Video Driver: 25.2 [ 353.614]X.Org XInput driver : 24.4 [ 353.614]X.Org Server Extension : 10.0 [ 353.616] (++) using VT number 7 [ 353.616] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 353.619] (II) xfree86: Adding drm device (/dev/dri/card0) [ 353.619] (II) Platform probe for /sys/devices/pci:00/:00:01.0/drm/card0 [ 353.628] (--) PCI:*(0@0:1:0) 1002:9837:1734:1202 rev 0, Mem @ 0xc000/268435456, 0xd000/8388608, 0xfeb0/262144, I/O @ 0xf000/256, BIOS @ 0x/131072 [ 353.628] (II) LoadModule: "glx" [ 353.628] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 353.631] (II) Module glx: vendor="X.Org Foundation" [ 353.631]compiled for 1.21.1.11, module version = 1.0.0 [ 353.631]ABI class: X.Org Server Extension, version 10.0 [ 353.631] (II) Applying OutputClass "Radeon" to /dev/dri/card0 [ 353.631]loading driver: radeon [ 353.631] (==) Matched radeon as autoconfigured driver 0 [ 353.631] (==) Matched ati as autoconfigured driver 1 [ 353.631] (==) Matched modesetting as autoconfigured driver 2 [ 353.631] (==) Matched fbdev as autoconfigured driver 3 [ 353.631] (==) Matched vesa as autoconfigured driver 4 [ 353.631] (==) Assigned the driver
Bug#1063151: igb: unpredictable interface names for four port nic
I was curious today and tried to build latest systemd and it is fixed already! I have done a git bisect and the commit fixing the problem is https://github.com/systemd/systemd/commit/af7417ac7b07bc01232982bf46e9d72e69e7f820 Regards -- Zito
Bug#1063151: igb: unpredictable interface names for four port nic
Is it definitely a BIOS problem? If yes, we can close the bug of course. I have a little bit of time to investigate the problem further: (My knowledge is limited) kory:/sys/bus/pci# for x in $(find . -name 'address' -print|sort); do echo -n "$x "; cat $x; done ./slots/0-1/address :3a:00 ./slots/0-2/address :3a:02 ./slots/0-3/address :5d:02 ./slots/0/address :17:01 ./slots/1/address :5d:00 ./slots/4/address :ae:00 ./slots/5/address :17:00 ./slots/6/address :00:1c kory:/sys/bus/pci# lspci -tvv|head -25 -+-[:00]-+-00.0 Intel Corporation Sky Lake-E DMI3 Registers | +-05.0 Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers | +-05.2 Intel Corporation Sky Lake-E RAS | +-05.4 Intel Corporation Sky Lake-E IOAPIC | +-08.0 Intel Corporation Sky Lake-E Ubox Registers | +-08.1 Intel Corporation Sky Lake-E Ubox Registers | +-08.2 Intel Corporation Sky Lake-E Ubox Registers | +-11.0 Intel Corporation C620 Series Chipset Family MROM 0 | +-11.5 Intel Corporation C620 Series Chipset Family SSATA Controller [AHCI mode] | +-14.0 Intel Corporation C620 Series Chipset Family USB 3.0 xHCI Controller | +-14.2 Intel Corporation C620 Series Chipset Family Thermal Subsystem | +-16.0 Intel Corporation C620 Series Chipset Family MEI Controller #1 | +-16.1 Intel Corporation C620 Series Chipset Family MEI Controller #2 | +-16.4 Intel Corporation C620 Series Chipset Family MEI Controller #3 | +-17.0 Intel Corporation C620 Series Chipset Family SATA Controller [AHCI mode] | +-1c.0-[01]--+-00.0 Intel Corporation I350 Gigabit Network Connection | |+-00.1 Intel Corporation I350 Gigabit Network Connection | |+-00.2 Intel Corporation I350 Gigabit Network Connection | |\-00.3 Intel Corporation I350 Gigabit Network Connection | +-1c.4-[02-03]00.0-[03]00.0 Matrox Electronics Systems Ltd. Integrated Matrox G200eW3 Graphics Controller | +-1c.5-[04]--+-00.0 Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe | |\-00.1 Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe | +-1f.0 Intel Corporation C621 Series Chipset LPC/eSPI Controller | +-1f.2 Intel Corporation C620 Series Chipset Family Power Management Controller | +-1f.4 Intel Corporation C620 Series Chipset Family SMBus kory:/sys/bus/pci# lspci -nnv|sed -n '/^00:1c/,/^$/ p;' |grep -Pi '^0|devname|slot' 00:1c.0 PCI bridge [0604]: Intel Corporation C620 Series Chipset Family PCI Express Root Port #1 [8086:a190] (rev f9) (prog-if 00 [Normal decode]) DeviceName: SLOT 6 Physical Slot: 6 Capabilities: [40] Express Root Port (Slot+), MSI 00 00:1c.4 PCI bridge [0604]: Intel Corporation C620 Series Chipset Family PCI Express Root Port #5 [8086:a194] (rev f9) (prog-if 00 [Normal decode]) Physical Slot: 6 Capabilities: [40] Express Root Port (Slot+), MSI 00 00:1c.5 PCI bridge [0604]: Intel Corporation C620 Series Chipset Family PCI Express Root Port #6 [8086:a195] (rev f9) (prog-if 00 [Normal decode]) Physical Slot: 6 Capabilities: [40] Express Root Port (Slot-), MSI 00 Any idea what to gather next? Thanks -- Zito
Bug#1063151: igb: unpredictable interface names for four port nic
Dear Valentin, On Tue, Feb 06, 2024 at 03:58:45PM +0100, Valentin wrote: > I suspect the issue might be somewhere in your udev configuration. > > You can get the evaluated udev rules by running 'udevadm test ' > > So running 'udevadm test /sys/class/net/ens6f2' and 'udevadm test /sys/class/ > net/eth0' and comparing outputs should tell you/everyone else whats different > for those devices and why they use different naming schemes. Output of both commands attached… > The old ethX names depend on the order of initialization and is therefore > unstable. > The new format (e.g. ens6f2) depends on pci device numbers and is stable. Yes, unstable are old names, right Some errors are reported for eth0 interface: eth0: Policy *slot* yields "ens6f0". eth0: Could not set AlternativeName= or apply AlternativeNamesPolicy=, ignoring: File exists eth0: /usr/lib/udev/rules.d/80-net-setup-link.rules:11 NAME 'ens6f0' eth0: /usr/lib/udev/rules.d/99-systemd.rules:68 RUN '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name --prefix=/net/ipv4/neigh/$name --prefix=/net/ipv6/conf/$name --prefix=/net/ipv6/neigh/$name' eth0: sd-device: Created db file '/run/udev/data/n69' for '/devices/pci:00/:00:1c.0/:01:00.0/net/eth0' ens6f0: Failed to rename network interface 69 from 'eth0' to 'ens6f0': File exists The bug should be reassigned to udev. Thank you very much for tip! -- Zito Trying to open "/etc/systemd/hwdb/hwdb.bin"... Trying to open "/etc/udev/hwdb.bin"... Trying to open "/usr/lib/systemd/hwdb/hwdb.bin"... Trying to open "/lib/systemd/hwdb/hwdb.bin"... Trying to open "/lib/udev/hwdb.bin"... === trie on-disk === tool version: 252 file size:12210802 bytes header size 80 bytes strings2564306 bytes nodes 9646416 bytes Loading kernel module index. Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Found container virtualization none. Using default interface naming scheme 'v252'. Parsed configuration file "/usr/lib/systemd/network/99-default.link" Parsed configuration file "/usr/lib/systemd/network/73-usb-net-by-mac.link" Created link configuration context. Reading rules file: /usr/lib/udev/rules.d/50-firmware.rules Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules Reading rules file: /usr/lib/udev/rules.d/55-dm.rules Reading rules file: /usr/lib/udev/rules.d/56-dm-parts.rules Reading rules file: /usr/lib/udev/rules.d/56-lvm.rules Reading rules file: /usr/lib/udev/rules.d/60-autosuspend.rules Reading rules file: /usr/lib/udev/rules.d/60-block.rules Reading rules file: /usr/lib/udev/rules.d/60-bridge-network-interface.rules Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /usr/lib/udev/rules.d/60-drm.rules Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules Reading rules file: /usr/lib/udev/rules.d/60-fido-id.rules Reading rules file: /usr/lib/udev/rules.d/60-infiniband.rules Reading rules file: /usr/lib/udev/rules.d/60-input-id.rules Reading rules file: /usr/lib/udev/rules.d/60-kpartx.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-dm.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules Reading rules file: /usr/lib/udev/rules.d/60-qemu-guest-agent.rules Reading rules file: /usr/lib/udev/rules.d/60-sensor.rules Reading rules file: /usr/lib/udev/rules.d/60-serial.rules Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules Reading rules file: /usr/lib/udev/rules.d/68-del-part-nodes.rules Reading rules file: /usr/lib/udev/rules.d/69-lvm.rules Reading rules file: /usr/lib/udev/rules.d/70-camera.rules Reading rules file: /usr/lib/udev/rules.d/70-joystick.rules Reading rules file: /usr/lib/udev/rules.d/70-memory.rules Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules Reading rules file: /usr/lib/udev/rules.d/71-seat.rules Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules Reading rules file: /usr/lib/udev/rules.d/73-special-net-names.rules Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules Reading rules file: /usr/lib/udev/rules.d/80-debian-compat.rules Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules Reading rules file: /usr/lib/udev/rules.d/80-ifupdown.rules Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules Reading rules file: /usr/lib/udev/rules.d/81-net-dhcp.rules Reading rules file:
Bug#1038114: Acknowledgement (hstr: no longer works with kernel linux-image-6.3.0-1-amd64)
Workaround: bobekpc:~# cat /etc/sysctl.d/10-hstr.conf dev.tty.legacy_tiocsti = 1 -- Zito
Bug#1022043: apt-cacher-ng: sometimes fails to download some index files - maybe a race condition
Package: apt-cacher-ng Version: 3.7.4-1~bpo11+1 Severity: normal Dear Maintainer, I have errors while updating apt database with several concurrent requests. I usually run apt update using Fabric framework on many servers in the same moment and apt-cacher-ng has a trouble with this. Apt shows that some Release file has invalid signature or some other problem with index files. I found this errors in error log: ns1:/srv/cache/apt-cacher-ng/debrep/dists/bullseye# tail /var/log/apt-cacher-ng/apt-cacher.err Wed Oct 19 13:47:18 2022|Error creating file item for debrep/dists/bullseye-updates/InRelease -- check file permissions! Wed Oct 19 13:47:18 2022|Failure to move file /srv/cache/apt-cacher-ng/debrep/dists/bullseye-backports/InRelease out of the way or cannot create /srv/cache/apt-cacher-ng/debrep/dists/bullseye-backports/InRelease.1666180038 - errno: File exists Wed Oct 19 13:47:18 2022|Error creating file item for debrep/dists/bullseye-backports/InRelease -- check file permissions! Wed Oct 19 13:47:18 2022|Failure to move file /srv/cache/apt-cacher-ng/debsecrep/dists/bullseye-security/InRelease out of the way or cannot create /srv/cache/apt-cacher-ng/debsecrep/dists/bullseye-security/InRelease.1666180038 - errno: File exists Wed Oct 19 13:47:18 2022|Error creating file item for debsecrep/dists/bullseye-security/InRelease -- check file permissions! Wed Oct 19 13:47:18 2022|/srv/cache/apt-cacher-ng/adoptopenjdk/dists/bullseye/InRelease.1666180038 storage error [Checked size beyond EOF], check file AND directory permissions, last errno: File exists Wed Oct 19 13:47:18 2022|Failure to move file /srv/cache/apt-cacher-ng/debsecrep/dists/bullseye-security/InRelease out of the way or cannot create /srv/cache/apt-cacher-ng/debsecrep/dists/bullseye-security/InRelease.1666180038 - errno: File exists Wed Oct 19 13:47:18 2022|Error creating file item for debsecrep/dists/bullseye-security/InRelease -- check file permissions! Wed Oct 19 13:47:18 2022|Failure to move file /srv/cache/apt-cacher-ng/debrep/dists/bullseye/InRelease out of the way or cannot create /srv/cache/apt-cacher-ng/debrep/dists/bullseye/InRelease.1666180038 - errno: File exists Wed Oct 19 13:47:18 2022|Error creating file item for debrep/dists/bullseye/InRelease -- check file permissions! ns1:/srv/cache/apt-cacher-ng/debrep/dists/bullseye# ls -la total 3684 drwxr-xr-x 5 apt-cacher-ng apt-cacher-ng 4096 Oct 19 13:47 . drwxr-xr-x 15 apt-cacher-ng apt-cacher-ng 4096 Oct 13 18:35 .. drwxr-xr-x 5 apt-cacher-ng apt-cacher-ng 4096 Oct 14 06:25 contrib -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 19 13:47 InRelease -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Sep 27 16:49 InRelease.1664901121 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 4 22:03 InRelease.1664963050 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 5 11:44 InRelease.1664967465 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 32768 Oct 14 06:25 InRelease.1664967466 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 5 13:07 InRelease.1664968046 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 16384 Oct 14 06:25 InRelease.1664968047 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 5 14:27 InRelease.1664976362 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 5 15:26 InRelease.1664987237 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 5 18:27 InRelease.1665135746 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 7 11:42 InRelease.1665143341 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 7 14:27 InRelease.1665146115 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 7 14:35 InRelease.1665423845 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 16384 Oct 14 06:25 InRelease.1665423846 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 10 19:44 InRelease.1665917759 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 12:55 InRelease.1665917760 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 12:56 InRelease.1665922621 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 16384 Oct 16 14:17 InRelease.1665922622 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 14:17 InRelease.1665937102 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 18:18 InRelease.1665937103 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 18:18 InRelease.1665943973 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 20:12 InRelease.1665943974 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 16 20:12 InRelease.1666009621 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 17 14:35 InRelease.1666037442 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 17 22:10 InRelease.1666037443 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 17 22:55 InRelease.1666075608 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 115947 Oct 18 08:46 InRelease.1666075609 -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 32768 Oct 18 08:46
Bug#1010658: set smtp_authenticators=login works!
Sorry, I was not subscribed to the bugreport… :-( I have added set smtp_authenticators=login and things works now! [2022-05-12 16:47:53] 5< 250-PIPELINING [2022-05-12 16:47:53] 5< 250-SIZE 52428800 [2022-05-12 16:47:53] 5< 250-ENHANCEDSTATUSCODES [2022-05-12 16:47:53] 5< 250 X-SZNEXTENSIONS [2022-05-12 16:47:53] smtp_authenticate: Trying method login [2022-05-12 16:47:53] smtp_auth_gsasl: using mech LOGIN [2022-05-12 16:47:53] Authenticating (LOGIN)... [2022-05-12 16:47:53] 5> AUTH LOGIN [2022-05-12 16:47:53] 5< 334 VXNlcm5hbWU6 [2022-05-12 16:47:53] 5> <<>> [2022-05-12 16:47:53] 5< 334 UGFzc3dvcmQ6 … So the problem is with the SMTP server side? Thank you very much! -- Zito
Bug#601627: closed by Bastian Germann (Re: /usr/sbin/saslauthd: ldap connection shutdown problem)
On Tue, Apr 19, 2022 at 03:57:05PM +, Debian Bug Tracking System wrote: > Please use LDAP_OPT_TIMEOUT that is available with newer versions. I am not certain if I understand your advise. I have searched sources version 2.1.28 (lak.c), and the value for LDAP_OPT_TIMEOUT parameter is used from the option ldap_timeout and correspond to - a citation from file LDAP_SASLAUTHD laying by: ldap_timeout: <5> Specify a number of seconds a search can take before timing out. It defaults to five seconds. The bug I reported was about 15 minutes delay, when Active Directory servers closes LDAP connection without activity on it. But it worked for another twelve more years as is :-) I have already logcheck ignore rule and forget about it. Cheers -- Zito
Bug#997849: confirmation
I can confirm this. Unstable (version 2.3.1-1): zito@bobek:~$ ip a s dev wlp3s0 3: wlp3s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:24:d7:f3:8d:e8 brd ff:ff:ff:ff:ff:ff inet 192.168.1.120/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0 valid_lft 74258sec preferred_lft 74258sec inet6 fe80::d1b4:870a:5e9d:43c7/64 scope link noprefixroute valid_lft forever preferred_lft forever zito@bobek:~$ /usr/lib/nagios/plugins/check_icmp -s 192.168.1.120 192.168.1.120 check_icmp: Cannot bind to IP address 192.168.1.120: Socket operation on non-socket Buster (2.2-6): nms2:~# dpkg -l --no-pager monitoring-plugins-basic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++---- ii monitoring-plugins-basic 2.2-6amd64Plugins for nagios compatible monitoring systems (basic) nms2:~# ip a s dev eth0 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:bb:d9:67 brd ff:ff:ff:ff:ff:ff inet 10.0.156.83/24 brd 10.0.156.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febb:d967/64 scope link valid_lft forever preferred_lft forever nms2:~# /usr/lib/nagios/plugins/check_icmp -s 10.0.156.83 10.0.156.83 OK - 10.0.156.83: rta 0.013ms, lost 0%|rta=0.013ms;200.000;500.000;0; pl=0%;40;80;; rtmax=0.045ms rtmin=0.005ms Cheers -- Zito
Bug#995370: pidgin: segmentation fault on malloc/free
On Fri, Oct 01, 2021 at 12:08:50AM -0500, Richard Laager wrote: > On 9/30/21 7:16 AM, Vaclav Ovsik wrote: > > after ugprade of pidgin:amd64 to 2.14.7-1 from 2.14.1-1+b1 > > Are you in any position to bisect this by building the intermediate 2.14.x > versions of Pidgin? > -- > Richard OK, I gave it some time to remember Mercurial… :-) Fortunately it is similar to Git. zito@bobekpc:/data-ssd/pidgin$ hg bisect -b The first bad revision is: changeset: 40901:f25ce9376564 branch: release-2.x.y user:Gary Kramlich date:Tue Jun 01 17:34:45 2021 -0500 summary: Fix a logic error in jabber that caused a user after free https://keep.imfreedom.org/pidgin/pidgin/rev/f25ce9376564 It is between v2.14.4 and v2.14.5. This is the changeset causing segfaults. Can you report this upstream please? -- Zito
Bug#991273: acng: for testing dist fails to download by-hash translations
Hello, On Mon, Jul 26, 2021 at 02:49:22PM +0200, Eduard Bloch wrote: > Hallo, > * Václav Ovsík [Mon, Jul 19 2021, 03:05:39PM]: > > Package: apt-cacher-ng > > Version: 3.3.1-2~bpo10+1 > > Severity: normal > > That's an ancient version in backports. Sorry for not having updated > this for a long time. I am very sorry, but the problem is not in acng :-(. Please, excuse me. I have done upgrade of the host debian.i.cz with acng to Bullseye with Apt-Cacher-NG/3.6.4, but the problem remains. I have done some further investigations and the problem is in the Checkpoint firewall of our organization :-/. > … > > zito@ser1:~/admin$ curl --head > > http://debian.i.cz:/debian/dists/bullseye/non-free/i18n/by-hash/SHA256/1719a3a7f5c969d9780aec600763314a8b55aaaed3016a76fa9a7a020c1e584c > > HTTP/1.1 200 OK > > Content-Length: 50436 > > Last-Modified: Tue, 15 Jun 2021 01:57:32 GMT > > This looks very wrong and indicates a file truncation in the cache. I > suggest to go to the admin webpage and run a cleanup operation > (Expiration task, with "check sizes and checksums" and "consider > incomplete files as damaged" checkboxes checked). No truncated, but exchanged with other file (and yes, maybe truncated)! The problem is with HTTP pipelining. bobekpc:~# file /var/lib/apt/lists/partial/ftp.debian.cz_debian_dists_sid_main_i18n_Translation-en.bz2.FAILED /var/lib/apt/lists/partial/ftp.debian.cz_debian_dists_sid_main_i18n_Translation-en.bz2.FAILED: gzip compressed data, max compression, from Unix, original size modulo 2^32 4212331769 bobekpc:~# zcat /var/lib/apt/lists/partial/ftp.debian.cz_debian_dists_sid_main_i18n_Translation-en.bz2.FAILED|head bin/afioutils/afio bin/bashshells/bash bin/bash-static shells/bash-static bin/brltty admin/brltty bin/bsd-csh shells/csh bin/btrfs admin/btrfs-progs bin/btrfs-convert admin/btrfs-progs bin/btrfs-find-root admin/btrfs-progs bin/btrfs-image admin/btrfs-progs bin/btrfs-map-logical admin/btrfs-progs This is Contents file, not Translations… (gzip/bzip2…) Workarounds: * move to https transport (Checkpoint FW can't inspect it) * apt -o Acquire::http::Pipeline-Depth=0 update I hope this report can help someone else with Checkpoint FW in his Internet connection path with HTTP inspection turned on… Excuse me, sorry for the effort you had with this report :-( Regards -- Zito
Bug#991273: acng: for testing dist fails to download by-hash translations
Package: apt-cacher-ng Version: 3.3.1-2~bpo10+1 Severity: normal Dear Maintainer, I tried to install bullseye machine and it fails to download some translations and installation fails: Jul 19 10:29:53 in-target: E: Failed to fetch http://debian.i.cz:/debian/dists/bullseye/non-free/i18n/by-hash/SHA256/1719a3a7f5c969d9780aec600763314a8b55aaaed3016a76fa9a7a020c1e584c File has unexpected size (50436 != 91475). Mirror sync in progress? [IP: 10.0.156.66 ] Jul 19 10:29:53 in-target:Hashes of expected file: Jul 19 10:29:53 in-target: - Filesize:91475 [weak] Jul 19 10:29:53 in-target: - SHA256:1719a3a7f5c969d9780aec600763314a8b55aaaed3016a76fa9a7a020c1e584c Jul 19 10:29:53 in-target: - MD5Sum:c3ad4b048f3df02478a64b33ef776008 [weak] Jul 19 10:29:53 in-target:Release file created at: Mon, 19 Jul 2021 08:07:25 + Jul 19 10:29:53 in-target: E: Failed to fetch http://debian.i.cz:/debian/dists/bullseye/contrib/i18n/by-hash/SHA256/57e6201d62bf60faf1a188ac528d0717cce16b6cfa1c9b91a0b89cc5b16e10f3 Jul 19 10:29:53 in-target: E: Some index files failed to download. They have been ignored, or old ones used instead. Its obvious from the curl output: zito@ser1:~/admin$ curl --head http://debian.i.cz:/debian/dists/bullseye/non-free/i18n/by-hash/SHA256/1719a3a7f5c969d9780aec600763314a8b55aaaed3016a76fa9a7a020c1e584c HTTP/1.1 200 OK Content-Length: 50436 Last-Modified: Tue, 15 Jun 2021 01:57:32 GMT Content-Type: application/octet-stream Date: Mon Jul 19 12:21:12 2021 Server: Debian Apt-Cacher NG/3.3.1 X-Original-Source: http://ftp.cz.debian.org/debian/dists/bullseye/non-free/i18n/by-hash/SHA256/1719a3a7f5c969d9780aec600763314a8b55aaaed3016a76fa9a7a020c1e584c Connection: Keep-Alive zito@ser1:~/admin$ curl --head http://ftp.cz.debian.org/debian/dists/bullseye/non-free/i18n/by-hash/SHA256/1719a3a7f5c969d9780aec600763314a8b55aaaed3016a76fa9a7a020c1e584c HTTP/1.1 200 OK Date: Mon, 19 Jul 2021 12:21:24 GMT Server: Apache/2.4.38 (Debian) Last-Modified: Tue, 08 Jun 2021 02:07:45 GMT ETag: "16553-5c4379fb85020" Accept-Ranges: bytes Content-Length: 91475 Maybe can be workarounded using some configuration pattern. Regards -- Zito -- Package-specific info: -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apt-cacher-ng depends on: ii adduser 3.118 ii debconf [debconf-2.0]1.5.71 ii dpkg 1.19.7 ii libatomic1 8.3.0-6 ii libbz2-1.0 1.0.6-9.2~deb10u1 ii libc62.28-10 ii libevent-2.1-6 2.1.8-stable-4 ii libevent-pthreads-2.1-6 2.1.8-stable-4 ii libgcc1 1:8.3.0-6 ii liblzma5 5.2.4-1 ii libssl1.11.1.1d-0+deb10u6 ii libstdc++6 8.3.0-6 ii libsystemd0 241-7~deb10u7 ii libwrap0 7.6.q-28 ii lsb-base 10.2019051400 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages apt-cacher-ng recommends: ii ca-certificates 20200601~deb10u2 Versions of packages apt-cacher-ng suggests: pn avahi-daemon pn doc-base ii libfuse2 2.9.9-1+deb10u1 -- Configuration Files: /etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: '/etc/apt-cacher-ng/security.conf' -- debconf information: apt-cacher-ng/cachedir: keep apt-cacher-ng/proxy: keep apt-cacher-ng/bindaddress: keep apt-cacher-ng/gentargetmode: No automated setup apt-cacher-ng/port: keep * apt-cacher-ng/tunnelenable: false
Bug#929608: pmciscoios can be really helpful
Fellow maintainer, please, enable pmciscoios. I can benefit from it too. Our Cisco switches log with double timestamp… :( e.g. Apr 21 09:16:53 sw-brn02.brn.i.cz 13134: Apr 21 07:16:53.208: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/27, changed state to up People want to solve this, so I will now have to rebuild the package. :-( -- Zito
Bug#977135: clamav-freshclam: logcheck rules patch
Package: clamav-freshclam
Version: 0.102.4+dfsg-0+deb10u1
Severity: wishlist
Dear Maintainer,
log message format changed a bit. There is a new word "database".
Dec 11 12:00:40 ns1 freshclam[1200]: daily.cld database is up to date (version:
26014, sigs: 4399154, f-level: 63, builder: raynman)
Dec 11 12:00:40 ns1 freshclam[1200]: main.cld database is up to date (version:
59, sigs: 4564902, f-level: 60, builder: sigmgr)
Dec 11 12:00:40 ns1 freshclam[1200]: bytecode.cld database is up to date
(version: 331, sigs: 94, f-level: 63, builder: anvilleg)
Please update /etc/logcheck/ignore.d.server/clamav-freshclam rules:
diff --git a/logcheck/ignore.d.server/clamav-freshclam
b/logcheck/ignore.d.server/clamav-freshclam
index 2608bd39..10f8c59b 100644
--- a/logcheck/ignore.d.server/clamav-freshclam
+++ b/logcheck/ignore.d.server/clamav-freshclam
@@ -1,6 +1,6 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: ClamAV update process
started at .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: Received signal: (wake
up|re-opening log file)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]:
(bytecode|daily|main)\.c(l|v)d (is up to date|updated) \(version: [0-9]+, sigs:
[0-9]+, f-level: [0-9]+, builder: \w+\)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]:
(bytecode|daily|main)\.c(l|v)d database (is up to date|updated) \(version:
[0-9]+, sigs: [0-9]+, f-level: [0-9]+, builder: \w+\)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: Clamd successfully
notified about the update\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]:
--$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: Database updated
\([0-9]+ signatures\) from .* \(IP: [0-9.]+\)$
Thanks
--
Zito
-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav
Config file: clamd.conf
---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime disabled
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "5"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertEncrypted disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled
AlgorithmicDetection = "yes"
BlockMax disabled
PhishingAlwaysBlockSSLMismatch disabled
PhishingAlwaysBlockCloak
Bug#952591: python3-urllib3: doesn't work with python3-six 1.14.0-2
On Wed, Feb 26, 2020 at 02:42:31PM +, Simon McVittie wrote: > Control: tags -1 + moreinfo unreproducible > > On Wed, 26 Feb 2020 at 15:24:26 +0100, Vaclav Ovsik wrote: > > there is an incompatilibity of python3-urllib3 with python3-six > > 1.14.0-2 > ... > > AttributeError: module 'six' has no attribute 'ensure_str' > > Are you sure you're not using an older local copy of 'six' - perhaps via > PYTHONPATH or /usr/local - rather than the distro version? This works > fine for me: OMG sorry. I was searching in /usr/local, but forgot to look at ~/.local/lib :-( I feel like idiot, sorry -- Zito
Bug#943967: /usr/share/vim/vim81/debian.vim: runtimepath overriden in debian.vim without /etc/vim path
Package: vim-common Version: 2:8.1.0875-5 Severity: normal File: /usr/share/vim/vim81/debian.vim Dear Maintainer, A directory /etc/vim is missing from the VIM runtimepath and so my syntax file at /etc/vim/syntax/dhcpd.vim is not loaded after upgrade to the Debian Buster release. You mentioned addition of /etc/vim into the default 'runtimepath' in changelog for version 2:8.1.0693-2. That is true, but this default runtimepath is overriden in the debian.vim file. zito@confl-priv:~$ vim -D Entering Debug mode. Type "cont" to continue. /usr/share/vim/vimrc line 10: runtime! debian.vim >set rtp runtimepath=~/.vim,/etc/vim,/usr/share/vim/vimfiles,/usr/share/vim/vim81,/usr/share/vim/vimfiles/after,/etc/vim/after,~/.vim/after >n /usr/share/vim/vimrc line 26: syntax on >set rtp runtimepath=~/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vim81,/usr/share/vim/vimfiles/after,/var/lib/vim/add ons/after,~/.vim/after > Addition a line bellow into /etc/vim/vimrc fixes the problem a dirty way. @@ -8,6 +8,8 @@ " This line should not be removed as it ensures that various options are " properly set to work with the Vim-related packages available in Debian. runtime! debian.vim +" FIXME bugworkaround FIXME +set runtimepath=~/.vim,/etc/vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vim81,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,/etc/vim/after,~/.vim/after " Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc. " This happens after /etc/vim/vimrc(.local) are loaded, so it will override Thanks for your work! Cheers -- Zito *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-common depends on: ii xxd 2:8.1.0875-5 Versions of packages vim-common recommends: ii vim 2:8.1.0875-5 ii vim-tiny 2:8.1.0875-5 vim-common suggests no packages. -- Configuration Files: /etc/vim/vimrc changed [not included] -- no debconf information
Bug#922031: certbot: Debian 9 systemd timer inactive after upgrade to 0.28.0-1~deb9u1
Hello Harlan, On Mon, Feb 11, 2019 at 06:45:46PM -0500, Harlan Lieberman-Berg wrote: > ... > > Hello Václav, > > Hm, that's strange. I went back and checked, and the timer file was > present in the 0.10 version as well. The timer used to work, and now > no longer does, correct? Exactly. I speak to colleague and he is also affected on one machine. > Can you send the output of `systemctl show certbot.timer`? attached... I left the thing as is on one server (anketa). The timer is still inactive... anketa:~# systemctl list-timers --all NEXT LEFT LAST PASSED UNIT ACTIVATES Tue 2019-02-12 08:39:00 CET 4min 18s left Tue 2019-02-12 08:09:01 CET 25min ago phpsessionclean.timerphpsessionclean.service Tue 2019-02-12 09:10:54 CET 36min leftMon 2019-02-11 20:36:35 CET 11h agoapt-daily.timer apt-daily.service Tue 2019-02-12 20:30:40 CET 11h left Mon 2019-02-11 20:30:40 CET 12h agosystemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service Wed 2019-02-13 06:11:23 CET 21h left Tue 2019-02-12 06:39:20 CET 1h 55min ago apt-daily-upgrade.timer apt-daily-upgrade.service n/a n/a Tue 2019-01-29 00:18:30 CET 2 weeks 0 days ago certbot.timercertbot.service 5 timers listed. anketa:/var/log/letsencrypt# ll -lrt /var/log/letsencrypt/ | tail -15 -rw-r--r-- 1 root root 642 Jan 26 00:42 letsencrypt.log.12 -rw-r--r-- 1 root root 642 Jan 26 12:58 letsencrypt.log.11 -rw-r--r-- 1 root root 642 Jan 27 00:01 letsencrypt.log.10 -rw-r--r-- 1 root root 642 Jan 27 12:44 letsencrypt.log.9 -rw-r--r-- 1 root root 642 Jan 28 00:06 letsencrypt.log.8 -rw-r--r-- 1 root root 973 Jan 28 10:09 letsencrypt.log.7 -rw-r--r-- 1 root root 17371 Jan 28 10:09 letsencrypt.log.6 -rw-r--r-- 1 root root 2976 Jan 28 10:13 letsencrypt.log.5 -rw-r--r-- 1 root root 10862 Jan 28 10:13 letsencrypt.log.4 -rw-r--r-- 1 root root 24656 Jan 28 10:15 letsencrypt.log.3 -rw-r--r-- 1 root root 26076 Jan 28 10:16 letsencrypt.log.2 -rw-r--r-- 1 root root 642 Jan 28 12:26 letsencrypt.log.1 -rw-r--r-- 1 root root 297 Jan 29 00:18 letsencrypt.log-20190203.gz -rw-r--r-- 1 root root20 Feb 3 06:25 letsencrypt.log-20190210.gz -rw-r--r-- 1 root root 0 Feb 10 06:25 letsencrypt.log As the certbot was not run anymore, logrotate started to rotate letsencrypt.log file. I have logrotate configured to use dateext to not fulfill incremental backups with cruft. Renamed logfile series are backed-up repeatedly... With date extension they are static and go to backup only one times. BTW: certbot with its thousand files is a bit inconvenient. Every time certbot runs, it rotates all thousand files, so they all go to backup everyday. This is upstream problem probably... The times of some of the above logfiles are from Jan 28, because I was solving a change of the LE authentication method. Thanks for your time and effort -- Zito Unit=certbot.service NextElapseUSecRealtime=infinity NextElapseUSecMonotonic=infinity LastTriggerUSec=49y 3w 6d 17h 18min 30.552506s LastTriggerUSecMonotonic=1w 3d 4h 8min 41.634499s Result=success AccuracyUSec=1min RandomizedDelayUSec=12h Persistent=yes WakeSystem=no RemainAfterElapse=yes Id=certbot.timer Names=certbot.timer Requires=-.mount sysinit.target var.mount WantedBy=timers.target Conflicts=shutdown.target Before=shutdown.target certbot.service timers.target After=-.mount time-sync.target sysinit.target var.mount Triggers=certbot.service RequiresMountsFor=/var/lib/systemd/timers Description=Run certbot twice daily LoadState=loaded ActiveState=inactive SubState=dead FragmentPath=/lib/systemd/system/certbot.timer UnitFileState=enabled UnitFilePreset=enabled StateChangeTimestamp=Tue 2019-01-29 08:14:17 CET StateChangeTimestampMonotonic=907468902955 InactiveExitTimestamp=Fri 2019-01-18 20:10:53 CET InactiveExitTimestampMonotonic=64450831 ActiveEnterTimestamp=Fri 2019-01-18 20:10:53 CET ActiveEnterTimestampMonotonic=64450831 ActiveExitTimestamp=Tue 2019-01-29 08:14:17 CET ActiveExitTimestampMonotonic=907468902955 InactiveEnterTimestamp=Tue 2019-01-29 08:14:17 CET InactiveEnterTimestampMonotonic=907468902955 CanStart=yes CanStop=yes CanReload=no CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=yes OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=yes AssertResult=yes ConditionTimestamp=Fri 2019-01-18 20:10:53 CET ConditionTimestampMonotonic=64239605 AssertTimestamp=Fri 2019-01-18 20:10:53 CET AssertTimestampMonotonic=64239605 Transient=no Perpetual=no StartLimitIntervalSec=1000 StartLimitBurst=5 StartLimitAction=none InvocationID=242ece5a59404f9ea996e16b505f3aa4
Bug#922031: upgrade from backport version is ok
Must to correct... I found a server where was backported version, that is: [UPGRADE] python3-certbot-apache:amd64 0.28.0-1~bpo9+1 -> 0.28.0-1~deb9u1 and the timer is running OK. -- Zito
Bug#922031: certbot: Debian 9 systemd timer inactive after upgrade to 0.28.0-1~deb9u1
Package: certbot Version: 0.28.0-1~deb9u1 Severity: important Dear Maintainer, after the latest certbot upgrade on Debian Stretch python-certbot-apache:amd64 0.10.2-1 -> 0.28.0-1~deb9u1 there is no periodic certificate renew task. LE sent me a first email about a first certificate expiration. vidle1:~# systemctl list-timers --all NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2019-02-11 16:27:43 CET 2h 36min left Mon 2019-02-11 05:59:09 CET 7h ago apt-daily.timer apt-daily.se Mon 2019-02-11 20:48:40 CET 6h left Sun 2019-02-10 20:48:40 CET 17h agosystemd-tmpfiles-clean.timer systemd-tmpf Tue 2019-02-12 06:53:13 CET 17h left Mon 2019-02-11 06:58:01 CET 6h ago apt-daily-upgrade.timer apt-daily-up n/a n/a Tue 2019-01-29 00:12:14 CET 1 weeks 6 days ago certbot.timercertbot.serv 4 timers listed. I have this problem on all my hosts with certbot. Starting timer by hand seems ok. systemctl start certbot.timer Regards -- Zito *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages certbot depends on: ii init-system-helpers 1.48 ii python3 3.5.3-1 ii python3-certbot 0.28.0-1~deb9u1 certbot recommends no packages. Versions of packages certbot suggests: pn python-certbot-doc ii python3-certbot-apache 0.28.0-1~deb9u1 pn python3-certbot-nginx -- no debconf information
Bug#816685: postfix disconnect matching rule
Hi,
I just solved this, because my servers have received disconnect messages
too.
rt:/etc/logcheck/ignore.d.server# cat postfix-local
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ postfix/smtpd\[[[:digit:]]+\]:
(dis)?connect from
It is simple modification of an original rule of postfix rules file.
rt:/etc/logcheck/ignore.d.server# fgrep 'connect from' postfix*
postfix:^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
postfix/smtpd\[[[:digit:]]+\]: (dis)?connect from [^[:space:]]+$
postfix-local:^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+
postfix/smtpd\[[[:digit:]]+\]: (dis)?connect from
Simple removing
[^[:space:]]+$
from the end of the original rule solves the problem with spaces.
Maybe logcheck practise is to match the whole line every time, then
.*$
can be appropriate. But I thing it is needless.
--
Zito
Bug#660103: editmoin: patch for different session cookie names
Hi,
I just created a small patch for the problem of changing Moin cookie
name. It is a simplification in reality :).
The file ~/.moin_ids should contain name/value cookie pairs
(MOIN_SESS.=).
The corresponding extraction command from Firefox db is:
sqlite3 -separator ' ' ~/.mozilla/*/*.default/cookies.sqlite \
"SELECT 'https://' || host, name || '=' || value
FROM moz_cookies WHERE name LIKE 'MOIN_SESSION%'" >~/.moin_ids
Example:
zito@bobekpc:~/deb/editmoin-1.17$ fgrep localhost ~/.moin_ids
https://localhost
MOIN_SESSION_80_ROOT_MyWiki=92857dbbe9c40573f2f81d001eca7b4beb6322e2
https://localhost
MOIN_SESSION_80_ROOT_MyWiki2=ca7337dc28b2b7834372a8bb72cc62c472e85e94
The manual page should be corrected accordingly.
Hope it will work
Cheers
--
Zito
--- editmoin.orig 2017-09-12 12:32:49.533875187 +0200
+++ editmoin 2017-09-12 12:32:52.637876860 +0200
@@ -333,16 +333,13 @@
raise Error, "no suitable url found for shortcut '%s'" % shortcut
-def get_urlopener(moinurl, cookievalue=None, cookiename="MOIN_SESSION"):
+def get_urlopener(moinurl, cookie=None):
urlopener = urllib.FancyURLopener()
proxy = os.environ.get("http_proxy")
if proxy:
urlopener.proxies.update({"http": proxy})
-if cookievalue:
-# moinmoin < 1.6
-urlopener.addheader("Cookie", "MOIN_ID=%s" % cookievalue)
-# moinmoin >= 1.6
-urlopener.addheader("Cookie", "%s=%s" % (cookiename, cookievalue))
+if cookie:
+urlopener.addheader("Cookie", cookie)
return urlopener
def fetchfile(urlopener, url, id, template):
@@ -443,7 +440,7 @@
for morsel in cookie.values():
sw = morsel.key.startswith
if sw("MOIN_SESSION") or sw("MOIN_ID"):
-return morsel.key, morsel.value
+return "%s=%s" % (morsel.key, morsel.value)
raise Error("Couldn't obtain session cookie from server")
def edit(url, template=None, editfile_func=editfile):
@@ -456,24 +453,14 @@
user = get_user(url)
if user:
# Moin >= 1.7
-cookiename, cookievalue = get_session_cookie(user, url)
-urlopener = get_urlopener(url, cookievalue, cookiename)
-moinfile = fetchfile(urlopener, url, cookievalue, template)
+cookie = get_session_cookie(user, url)
+urlopener = get_urlopener(url, cookie)
+moinfile = fetchfile(urlopener, url, cookie, template)
else:
# Moin < 1.7
-cookievalue = get_id(url)
-moinfile = None
-for cookiename in ("MOIN_SESSION_80_ROOT", "MOIN_SESSION_443_ROOT"):
-try:
-urlopener = get_urlopener(url, cookievalue, cookiename)
-moinfile = fetchfile(urlopener, url, cookievalue, template)
-break
-except:
-pass
-if not moinfile:
-urlopener = get_urlopener(url, cookievalue)
-moinfile = fetchfile(urlopener, url, cookievalue, template)
-
+cookie = get_id(url)
+urlopener = get_urlopener(url, cookie)
+moinfile = fetchfile(urlopener, url, cookie, template)
try:
page_edited = editfile_func(moinfile)
if page_edited:
Bug#865620: confirmed
Hi, I can confirm this. My small local fixup: # cat /etc/systemd/system/apcupsd.service.d/override.conf [Unit] After=network-online.target Cheers -- Zito
Bug#868766: clamav-freshclam: please update logcheck rules
Package: clamav-freshclam
Version: 0.99.2+dfsg-0+deb8u2
Severity: wishlist
Dear Maintainer,
there is a tiny improvement to logcheck file please:
diff --git a/logcheck/ignore.d.server/clamav-freshclam
b/logcheck/ignore.d.server/clamav-freshclam
index 73df35f..2608bd3 100644
--- a/logcheck/ignore.d.server/clamav-freshclam
+++ b/logcheck/ignore.d.server/clamav-freshclam
@@ -1,6 +1,6 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: ClamAV update process
started at .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: Received signal: (wake
up|re-opening log file)$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: (daily|main)\.c(l|v)d
(is up to date|updated) \(version: [0-9]+, sigs: [0-9]+, f-level: [0-9]+,
builder: \w+\)$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]:
(bytecode|daily|main)\.c(l|v)d (is up to date|updated) \(version: [0-9]+, sigs:
[0-9]+, f-level: [0-9]+, builder: \w+\)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: Clamd successfully
notified about the update\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]:
--$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: Database updated
\([0-9]+ signatures\) from .* \(IP: [0-9.]+\)$
Thanks
--
Zito
Bug#845382: BUG: soft lockup when radeon modesetting
On Thu, Mar 30, 2017 at 12:40:46AM +0200, Dominik George wrote: > I can confirm this issue. > > I found a workaround by setting radeon.hard_reset=1, which resets the > PCI bus after loading the firmware. Both Audio and KMS work with this > option set. Please, what kernel version and hardware? I tried Debian kernel 4.9.18-1 (package 4.9.0-2-amd64) and with enabled HDMI audio in BIOS of Asus M2A-VM HDMI the lockup shows :(. vdr:~# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.9.0-2-amd64 root=UUID=632652f0-7f3c-4316-a74d-d05f2fd4b3ae ro radeon.hard_reset=1 netconsole=@192.168.1.50/,@192.168.1.120/ -- Zito
Bug#854398: fusiondirectory: missing dependency on php-mbstring
Package: fusiondirectory Version: 1.0.19-1 Severity: minor Dear Maintainer, the setup process reveal missing php-mbstring. The package should depend on it. Cheers -- Zito -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fusiondirectory depends on: ii apache2 [httpd] 2.4.25-3 ii fusiondirectory-smarty3-acl-render 1.0.19-1 ii gettext 0.19.8.1-2 ii javascript-common 11 ii libarchive-extract-perl 0.80-1 ii libcrypt-cbc-perl 2.33-1 ii libfile-copy-recursive-perl 0.38-1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libnet-ldap-perl1:0.6500+dfsg-1 ii libpath-class-perl 0.37-1 ii libperl5.24 [libdigest-sha-perl]5.24.1-1 ii libterm-readkey-perl2.37-1 ii libxml-twig-perl1:3.50-1 ii mini-httpd [httpd] 1.23-1.1 ii openssl 1.1.0c-2 ii php 1:7.0+49 ii php-cas 1.3.3-4 ii php-curl1:7.0+49 ii php-fpdf3:1.8.1.dfsg-2 ii php-gd 1:7.0+49 ii php-imagick 3.4.3~rc2-2 ii php-imap1:7.0+49 ii php-ldap1:7.0+49 ii php-recode 1:7.0+49 ii php7.0 [php]7.0.15-1 ii php7.0-cli [php-cli]7.0.15-1 ii php7.0-curl [php-curl] 7.0.15-1 ii php7.0-gd [php-gd] 7.0.15-1 ii php7.0-imap [php-imap] 7.0.15-1 ii php7.0-ldap [php-ldap] 7.0.15-1 ii php7.0-recode [php-recode] 7.0.15-1 ii schema2ldif 1.2-1 ii smarty-gettext 1.5.0-2 ii smarty3 3.1.31+20161214.1.c7d42e4+selfpack1-1 fusiondirectory recommends no packages. Versions of packages fusiondirectory suggests: pn argonaut-server ii fusiondirectory-schema 1.0.19-1 ii slapd 2.4.44+dfsg-3 -- no debconf information
Bug#845382: reported upstream
https://bugs.freedesktop.org/show_bug.cgi?id=98987
Bug#845382: it is not debian specific
Hi, the problem is not Debian specific. I tried to build latest upstream kernel commit 43c4f67c966deb1478dc9acbf66ab547287d530f (49 commits after 4.9-rc7) and the problem is more or less the same: zito@bobek:~/radeon/4.9.0rc7$ fgrep -m1 -h BUG radeon-kms-messages??.txt [ 15.730673] BUG: unable to handle kernel NULL pointer dereference at 006c [ 44.148004] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [run-parts:379] [ 48.148004] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [systemd-fstab-g:445] [ 44.144003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [(d-logind):400] [ 44.152004] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [upstart:387] [ 48.148013] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworker/1:2:51] [ 15.316493] BUG: unable to handle kernel NULL pointer dereference at 006c [ 48.152014] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [smartd:452] Circa 1 of 10 boots the problem not perform, but the problem is during shutdown in that case (shutdown hangs). I tried also older Debian kernels. The version 4.7.x - very similar, version 4.6.x - the score of successfull boot up is a bit bigger, but problem is there too. My subjective view is the problem (probably some very old kernel bug) is more propagating in newner kernel versions. -- Zito
Bug#844773: RFS: ustr/1.0.4-6
On Wed, Nov 23, 2016 at 06:39:28PM +, Gianfranco Costamagna wrote: > control: owner -1 ! > control: tags -1 moreinfo > > > >I am looking for a sponsor for my package "ustr" > > >* Added dependency on quilt and include /usr/share/quilt/quilt.make > in the debian/rules. > > ^^ why? > > also: > -include /usr/share/topgit/tg2quilt.mk > > /usr/share/topgit/tg2quilt.mk: > > > why? you don't even seem to build-depend on that package. > > Please be more verbose in changelog, more verbosity means more > chances to get your package quickly sponsored :) more verbose changelog https://anonscm.debian.org/cgit/users/zito-guest/pkg-ustr.git/commit/?id=ce9e9f893750fb938f21b74b0163f0d6979e405b package reuploaded to mentors Thanks -- Zito
Bug#845382: more boot BUG logs
I added netconsole into /boot/grub/grub.cfg and did more attempts to boot. Logs are attached in the archive. zito@bobek:~$ fgrep -m 1 BUG radeon-kms-messages* radeon-kms-messages.txt:[ 64.148004] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworker/1:2:51] radeon-kms-messages1.txt:[ 14.147686] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages2.txt:[ 15.379376] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages3.txt:[ 13.890714] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages4.txt:[ 14.579563] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages5.txt:[ 15.651245] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages6.txt:[ 48.148004] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [smartd:457] radeon-kms-messages7.txt:[ 15.472800] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages8.txt:[ 14.282438] BUG: unable to handle kernel NULL pointer dereference at 006c radeon-kms-messages9.txt:[ 14.860173] BUG: unable to handle kernel NULL pointer dereference at 006c There is NULL pointer dereference in most cases. -- Zito radeon-kms-messages.tar.xz Description: application/xz
Bug#845382: BUG: soft lockup when radeon modesetting
Package: src:linux Version: 4.8.7-1 Severity: normal Dear Maintainer, I'm unable to boot into functional system with KMS radeon. When radeon.modeset=0 on kernel command-line system it starts and run OK. Without disabled modeset, mostly the screen goes blank, but sometimes the messages stays on console. System is locked and not respond to sysrq or so. Kernel stack is displayed periodically as watchdog initiates. Captured messages (using netconsole) are attached. Regards -- Zito -- Package-specific info: ** Version: Linux version 4.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) ** Command line: BOOT_IMAGE=/vmlinuz-4.8.0-1-amd64 root=UUID=632652f0-7f3c-4316-a74d-d05f2fd4b3ae ro radeon.modeset=0 ** Not tainted ** Kernel log: [3.010746] scsi 6:0:0:1: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 [3.011944] scsi 6:0:0:2: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 [3.013151] scsi 6:0:0:3: Direct-Access Generic STORAGE DEVICE 9317 PQ: 0 ANSI: 0 [3.082153] sd 6:0:0:3: [sde] Attached SCSI removable disk [3.083229] sd 6:0:0:0: [sdb] Attached SCSI removable disk [3.084577] sd 6:0:0:1: [sdc] Attached SCSI removable disk [3.085913] sd 6:0:0:2: [sdd] Attached SCSI removable disk [4.576131] floppy0: no floppy controllers found [4.637754] PM: Starting manual resume from disk [4.637800] PM: Hibernation image partition 8:2 present [4.637801] PM: Looking for hibernation image. [4.639867] PM: Image not found (code -22) [4.639868] PM: Hibernation image not present or could not be loaded. [5.144483] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [6.504046] random: crng init done [6.629488] ip_tables: (C) 2000-2006 Netfilter Core Team [6.773851] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [6.774077] systemd[1]: Detected architecture x86-64. [6.870642] systemd[1]: Set hostname to . [8.285798] systemd[1]: Listening on LVM2 metadata daemon socket. [8.286228] systemd[1]: Listening on LVM2 poll daemon socket. [8.286680] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [8.286996] systemd[1]: Listening on Device-mapper event daemon FIFOs. [8.287353] systemd[1]: Listening on Journal Audit Socket. [8.287674] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [8.287972] systemd[1]: Listening on RPCbind Server Activation Socket. [9.059352] loop: module loaded [9.149613] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [9.498760] RPC: Registered named UNIX socket transport module. [9.498803] RPC: Registered udp transport module. [9.498837] RPC: Registered tcp transport module. [9.498871] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 10.258718] systemd-journald[221]: File /var/log/journal/0ca8a8b0a1569675c187692c5066cae3/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 10.623394] systemd-journald[221]: Received request to flush runtime journal from PID 1 [ 11.485959] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input6 [ 11.486007] ACPI: Power Button [PWRB] [ 11.486125] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7 [ 11.486164] ACPI: Power Button [PWRF] [ 11.552262] piix4_smbus :00:14.0: SMBus Host Controller at 0xb00, revision 0 [ 11.552358] piix4_smbus :00:14.0: Auxiliary SMBus Host Controller at 0xb10 [ 11.724952] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 11.739879] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05 [ 11.740025] sp5100_tco: PCI Vendor ID: 0x1002, Device ID: 0x4385, Revision ID: 0x14 [ 11.740083] sp5100_tco: failed to find MMIO address, giving up. [ 11.868374] [drm] Initialized drm 1.1.0 20060810 [ 11.877794] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 11.877895] sr 4:0:1:0: Attached scsi generic sg1 type 5 [ 11.877981] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 11.878062] sd 6:0:0:1: Attached scsi generic sg3 type 0 [ 11.878149] sd 6:0:0:2: Attached scsi generic sg4 type 0 [ 11.878229] sd 6:0:0:3: Attached scsi generic sg5 type 0 [ 11.990613] parport_pc 00:04: reported by Plug and Play ACPI [ 11.990714] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] [ 12.280244] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.295488] k8temp :00:18.3: Temperature readouts might be wrong - check erratum #141 [ 12.350432] input: PC Speaker as /devices/platform/pcspkr/input/input8 [ 12.483323] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully [ 12.494928] flexcop-pci: will use
Bug#844773: RFS: ustr/1.0.4-6
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ustr" * Package name: ustr Version : 1.0.4-6 Upstream Author : James Antill <ja...@and.org> * URL : http://www.and.org/ustr/ * License : LGPL, BSD, MIT Section : libs It builds those binary packages: libustr-1.0-1 - Micro string library: shared library libustr-1.0-1-dbg - Micro string library: debugging symbols libustr-dev - Micro string library: development stuff libustr-doc - Micro string library: documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ustr Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/u/ustr/ustr_1.0.4-6.dsc Changes since the last upload: * Patch fixes/autoconf: - Fixed race condition on creation shared library symbolic links when make runs parallel. Thanks to Yann E. MORIN <yann.morin.1...@free.fr>. - Fixed FTBFS (LDFLAGS with -pie): move LDFLAGS before -shared. Thanks to Helmut Grohne <hel...@subdivi.de>. Closes: #843459 * Patch fixes/man-spelling: added corrections. * Added fixes/attr-nonnull: to disable nonnull attribute. * Added fixes/suppress-warn: to suppress warning about indentation. * Added hardening=+all in the debian/rules. * Changed Vcs-Git to URL with https. * Changed Standards-Version to 3.9.8. * Added dependency on quilt and include /usr/share/quilt/quilt.make in the debian/rules. * For libustr-doc added Multi-Arch: foreign. Regards -- Václav Ovsík
Bug#843108: python-django-horizon: not compatible with Django 1.10 or JQuery 3.1.1-1
Package: python-django-horizon
Version: 3:10.0.0-1
Severity: normal
Dear Maintainer,
while I'm experimenting with Newton OS release on Sid the two problems
revealed.
* Django 1.10 - some actions don't work because of CSRF missing
[Thu Nov 03 16:31:18.604797 2016] [wsgi:error] [pid 10577:tid 139689449191168]
[client 192.168.29.70:50192] UserWarning: A {% csrf_token %} was used in a
template, but the context did not provide the value. Th is is usually caused
by not using RequestContext., referer:
http://controller.os2.i.cz/project/network_topology/
* JQuery 3.1.1-1 - drop-down menus don't work.
Downgrade Django to 1.8.15-1~bpo8+1 and libjs-jquery to 1.11.3+dfsg-4~bpo8+1
solve the problems.
--
Zito
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-django-horizon depends on:
ii python-babel 2.3.4+dfsg.1-2
ii python-ceilometerclient 2.6.1-2
ii python-cinderclient 1:1.9.0-2
ii python-django1:1.10.1-1
ii python-django-babel 0.5.1-2
ii python-django-compressor 2.0-4
ii python-django-openstack-auth 2.4.1-2
ii python-django-pyscss 2.0.2-6
ii python-glanceclient 1:2.5.0-3
ii python-heatclient1.4.0-2
ii python-iso8601 0.1.11-1
ii python-keystoneclient1:3.2.0-2
ii python-memcache 1.57-2
ii python-netaddr 0.7.18-2
ii python-neutronclient 1:6.0.0-2
ii python-novaclient2:6.0.0-2
ii python-oslo.concurrency 3.14.0-2
ii python-oslo.config 1:3.17.0-3
ii python-oslo.i18n 3.9.0-3
ii python-oslo.policy 1.14.0-2
ii python-oslo.serialization2.13.0-2
ii python-oslo.utils3.16.0-2
ii python-pbr 1.10.0-1
ii python-pint 0.7.2-3
ii python-pyscss1.3.5-2
ii python-six 1.10.0-3
ii python-swiftclient 1:3.1.0-2
ii python-tz2015.7+dfsg-0.1
ii python-xstatic 1.0.0-4
ii python-xstatic-angular 1.3.7.0-2
ii python-xstatic-angular-bootstrap 0.11.0.3-1
ii python-xstatic-angular-fileupload12.0.4.0+dfsg1-1
ii python-xstatic-angular-gettext 2.1.0.2-2
ii python-xstatic-angular-lrdragndrop 1.0.2.2-1
ii python-xstatic-angular-schema-form 0.8.13.0-2
ii python-xstatic-bootstrap-datepicker 0.0.0.1-3
ii python-xstatic-bootstrap-scss3.2.0.1-1
ii python-xstatic-bootswatch3.3.5.2-2
ii python-xstatic-d33.4.11-3
ii python-xstatic-font-awesome 4.1.0-1
ii python-xstatic-hogan 2.0.0.2-1
ii python-xstatic-jasmine 2.1.2.0-1
ii python-xstatic-jquery1.7.2.0+dfsg1-3
ii python-xstatic-jquery-migrate1.2.1.1+dfsg1-1
ii python-xstatic-jquery-ui 1.10.1.1+debian+dfsg1-5
ii python-xstatic-jquery.quicksearch2.0.4.1-1
ii python-xstatic-jquery.tablesorter2.14.5.1-2
ii python-xstatic-jsencrypt 2.0.0.2-1
ii python-xstatic-magic-search 0.2.5.1-1
ii python-xstatic-mdi 1.4.57.0-1
ii python-xstatic-objectpath1.2.1.0-2
ii python-xstatic-rickshaw 1.5.0.2-2
ii python-xstatic-roboto-fontface 0.4.3.2-1
ii python-xstatic-smart-table 1.4.5.3-1
ii python-xstatic-spin 1.2.8.0+dfsg1-1
ii python-xstatic-term.js 0.0.4.2-2
ii python-xstatic-tv4 1.2.7.0-2
ii python-yaml 3.12-1
pn python:any
python-django-horizon recommends no packages.
Versions of packages python-django-horizon suggests:
ii memcached 1.4.31-1
-- no debconf information
Bug#816850: postfix-policyd-spf-python: crash on latin chars in recipient
I was wrong with the subject of my previous post.
The problem is with latin character in recipient.
vidle1:/tmp# /usr/bin/policyd-spf
line = lineraw.decode('UTF-8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 11:
invalid continuation byte
>From the net can be received virtualy anything and the policy server
should cope with it.
--
Zito
u2.query
Description: Binary data
Bug#816850: postfix-policyd-spf-python: crash on UTF-8 in recipient
Hi,
there is probably more problems of this type. I have this errors in log
file:
Oct 16 07:35:07 vidle1 policyd-spf[2233]: Traceback (most recent call last):
Oct 16 07:35:07 vidle1 policyd-spf[2233]: File "/usr/bin/policyd-spf", line
654, in
Oct 16 07:35:07 vidle1 policyd-spf[2233]: line = lineraw.decode('UTF-8')
Oct 16 07:35:07 vidle1 policyd-spf[2233]: UnicodeDecodeError: 'utf-8' codec
can't decode byte 0xe1 in position 23: invalid continuation byte
Oct 16 07:35:07 vidle1 postfix/spawn[1771]: warning: command
/usr/bin/policyd-spf exit status 1
Oct 16 07:35:07 vidle1 postfix/smtpd[32580]: warning: premature end-of-input
on private/policyd-spf while reading input attribute name
Oct 16 07:35:07 vidle1 postfix/smtpd[32580]: warning: problem talking to
server private/policyd-spf: Success
Oct 16 07:35:07 vidle1 postfix/smtpd[32580]: NOQUEUE: reject: RCPT from
smtp-out3.iol.cz[194.228.2.91]: 451 4.3.5 Server configuration problem;
from= to= proto=ESMTP
helo=
The address to=... from the last log line was evidently written by mistake with
`á' istead of ascii `a'.
zito@bobek:~$ unicode á
U+00E1 LATIN SMALL LETTER A WITH ACUTE
UTF-8: c3 a1 UTF-16BE: 00e1 Decimal: Octal: \0341
á (Á)
Uppercase: 00C1
Category: Ll (Letter, Lowercase)
Unicode block: 0080..00FF; Latin-1 Supplement
Bidi: L (Left-to-Right)
Decomposition: 0061 0301
The mail server is running Debian Jessie
ii postfix-policyd-spf-python 1.3.1-1allPostfix
policy server for SPF checking
Regards
--
Zito
Bug#796455: automatic inventory checks of what?
Hi Matt, I'm not certain about what inventory you write this wishlist, there are at least two meaning: 1) inventory of service checks The URL you mentioned http://mathias-kettner.com/checkmk_inventory_checks.html is about this. 2) HW/SW inventory - that is information from dmidecode, operating system, packages installed... - the agent plugin mk_inventory does this on monitored host - on monitoring system this must be configured to process data using code from /usr/share/check_mk/inventory. upstream describe it at https://mathias-kettner.com/checkmk_inv.html ad agent load: - the problem is, that mk_inventory.linux plugin assumes existence of directory /var/lib/check_mk_agent, which is not instantiated by deb package. The plugin can't create timestamp file there and is run everytime the agent is run. - plugin should be pathed to do mkdir -p $MK_VARDIR - deb pkg check-mk-agent should create /var/lib/check_mk_agent? - with existing timestamp file, the inventory is created only onetime in four hours without WATO on monitoring system you must define active check, that will transform received data from /var/lib/check_mk/persisted into /var/lib/check_mk/inventory in regular intervals. I did this now main.mk using: ... active_checks['cmk_inv'] = [] ... # HW/SW Inventory extra_service_conf['check_interval'] += [ ( 120, [], ALL_HOSTS, ['Check_MK HW/SW Inventory$'] ), ] extra_service_conf['retry_interval'] += [ ( 120, [], ALL_HOSTS, ['Check_MK HW/SW Inventory$'] ), ] ... # HW/SW Inventory active_checks['cmk_inv'] += [ ( None, [], ['foo.example.com'] ), ] I don't think this should be in different package. Regards -- Zito
Bug#826953: check-mk-server: missing dir /usr/share/check_mk/inventory/
Package: check-mk-server Version: 1.2.6p12-1~bpo8+1 Severity: normal Dear Maintainer, directory /usr/share/check_mk/inventory and its content is missing in source package. diff --git a/debian/check-mk-server.install b/debian/check-mk-server.install index 97aa51e..d21b8cb 100644 --- a/debian/check-mk-server.install +++ b/debian/check-mk-server.install @@ -9,6 +9,7 @@ var/lib/check_mk/precompiled usr/bin/check_mk usr/share/check_mk/checks usr/share/check_mk/checks-man +usr/share/check_mk/inventory usr/share/check_mk/modules usr/share/check_mk/pnp-templates usr/share/check_mk/notifications Thanks -- Zito -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages check-mk-server depends on: ii adduser 3.113+nmu3 ii check-mk-config-icinga 1.2.6p12-1~bpo8+1 ii debconf [debconf-2.0] 1.5.56 ii python 2.7.9-1 Versions of packages check-mk-server recommends: ii check-mk-doc 1.2.6p12-1~bpo8+1 ii snmp 5.7.2.1+dfsg-1 check-mk-server suggests no packages. -- Configuration Files: /etc/check_mk/conf.d/README [Errno 13] Permission denied: u'/etc/check_mk/conf.d/README' /etc/check_mk/main.mk changed [not included] -- debconf information excluded
Bug#818502: git bisect show the commit
Theodore Ts'o comment on bugzilla.kernel.org... https://bugzilla.kernel.org/show_bug.cgi?id=102731#c43 -- Zito
Bug#818502: git bisect show the commit
I found a commit using git bisect, that vanilla kernel at this commit https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424 don't have the bug (>100 iterations). I left the test running to be sure... -- Zito
Bug#818502: kernel 3.17 is probably OK
Hi, report from testing so far. apate:~# getSystemId Libsmbios version: 2.2.28 Product Name: PowerEdge 1950 Vendor: Dell Inc. BIOS Version: 2.3.1 System ID: 0x01B3 Service Tag:BYV0W3J Express Service Code: 26052565375 I tested using shell oneliner in VM: i=0; while :; do let i=i+1; echo; echo "run $i ..."; echo; sleep 5; apt install -y linux-source || break; sleep 5; apt remove --auto-remove -y linux-source || break; done I took current kernel version from stable Linux apate 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux and did it 10 runs till crash. Number of iterations needed to crash was: 18, 6, 22, 10, 28, 16, 9, 1, 1, 6 I took kernel version 3.17 Linux apate 3.17-1-amd64 #1 SMP Debian 3.17-1~exp1 (2014-10-14) x86_64 GNU/Linux http://snapshot.debian.org:/archive/debian/20141130T220818Z/pool/main/l/linux/linux-image-3.17-1-amd64_3.17-1~exp1_amd64.deb and after 179 iterations there was no crash in VM. I think this kernel version is OK. Any suggestions what to test now? Thanks -- Zito
Bug#818502: kernel 4.3.5-1~bpo8+1 is OK probably
Hi, I can play a bit with a server PE 1950 over weekend, so I start to test with current backports kernel 4.3 apate:~# uname -a Linux apate 4.3.0-0.bpo.1-amd64 #1 SMP Debian 4.3.5-1~bpo8+1 (2016-02-23) x86_64 GNU/Linux after two hours of testing according to the bugreport it seems no problem with this kernel as hypervisor. So probably current workaround for this old CPUs and virtulization is to install this kernel from backports on hypervisor. -- Zito
Bug#818502: linux-image-3.16.0-4-amd64: data corruption in KVM VM & hypervisor with Intel CPU with early IntelVT
Package: src:linux Version: 3.16.7-ckt20-1+deb8u4 Severity: normal Dear Maintainer, I have very ugly and probably hard to analyze problem with filesystem corruption on KVM virtual and the hypervisor running on hardware with CPU from early IntelVT era (Both hypervisor and VM are Debian Jessie of course). I can report this problem meantime for hypervisor on Intel Xeon E5410 [1](Dell PowerEdge 1950) Intel Xeon E5430 [2](Dell PowerEdge 1950) Intel Core2 Duo E8400 [3] (some PC) the problem is NOT with the newer HW/CPU: Intel Xeon X5650 [4](Dell PowerEdge R710) Intel Xeon L5520 [5](Dell PowerEdge R710) Until Jessie we had no problems. After migration to Debian Jessie there was several times filesystem corruption on VM running monitoring several hosts using Icinga and writing performance data into RRD files. The snippets from syslog are produced with zfgrep -h -i -e 'Linux version ' -e Memory: -e EXT4 syslog-20*gz >/tmp/mong.syslog.txt attached... Now I invent the method for reproducing the problem in reasonable time. 1) Prepare a new VM storage 2G, RAM 256MiB 2) Install Debian Jessie (PXE, CD...) 200MB swap, root fs the rest 3) Shutdown a new VM and decrease memory allocation to 90MiB for it 4) Start VM and do some package management torture :). I used: while :; do apt install -y linux-source; sleep 10; apt remove --auto-remove -y linux-source; sleep 10; done On "faulty" CPU you get after a while: Unpacking gcc-4.9 (4.9.2-10) ... dpkg: unrecoverable fatal error, aborting: unable to fsync updated status of `man-db': Read-only file system rm: cannot remove ‘/var/cache/etckeeper/packagelist.pre-install’: Read-only file system E: Sub-process /usr/bin/dpkg returned an error code (2) E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/etckeeper ]; then etckeeper post-install; fi' E: Sub-process returned an error code W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. ... and in another terminal running journalctl -f: Mar 17 15:19:49 keryvm1 ssh-audit[1159]: zito : root access using connection 10.0.156.88 34352 172.30.1.29 22 Mar 17 15:19:49 keryvm1 logger[1186]: [audit zito as root/1156 on pts/1/10.0.156.88:34352->172.30.1.29:22]: #=== session opened === Mar 17 15:19:50 keryvm1 logger[1190]: [audit zito as root/1156 on pts/1/10.0.156.88:34352->172.30.1.29:22] /root: journalctl -f Mar 17 15:22:31 keryvm1 kernel: EXT4-fs error (device vda2): ext4_mb_generate_buddy:757: group 5, block bitmap and bg descriptor inconsistent: 4196 vs 4194 f$ ee clusters Mar 17 15:22:31 keryvm1 kernel: Aborting journal on device vda2-8. Mar 17 15:22:31 keryvm1 kernel: EXT4-fs (vda2): Remounting filesystem read-only Mar 17 15:22:31 keryvm1 kernel: [ cut here ] Mar 17 15:22:31 keryvm1 kernel: WARNING: CPU: 0 PID: 6534 at /build/linux-U7H2aZ/linux-3.16.7-ckt20/fs/ext4/ext4_jbd2.c:266 __ext4_handle_dirty_metadata+0x18$ /0x1d0 [ext4]() Mar 17 15:22:31 keryvm1 kernel: Modules linked in: nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_generic snd_hda_intel ppdev s$ d_hda_controller snd_hda_codec ttm drm_kms_helper snd_hwdep evdev psmouse joydev pcspkr serio_raw i2c_piix4 snd_pcm drm snd_timer snd pvpanic i2c_core parpor$ _pc soundcore virtio_balloon parport virtio_console processor thermal_sys button autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid virtio_net virtio_blk sg sr_mod cdrom ata_generic ehci_pci uhci_hcd ehci_hcd ata_piix libata floppy virtio_pci virtio_ring virtio usbcore usb_common scsi_mod Mar 17 15:22:31 keryvm1 kernel: CPU: 0 PID: 6534 Comm: dpkg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt20-1+deb8u4 Mar 17 15:22:31 keryvm1 kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140531_083030-gandalf 04/01/2014 Mar 17 15:22:31 keryvm1 kernel: 0009 8150dcff 810677d7 Mar 17 15:22:31 keryvm1 kernel: 8800027f2570 ffe2 88be0328 Mar 17 15:22:31 keryvm1 kernel: a023fde0 a022065e 8800031514b0 8800027f2570 Mar 17 15:22:31 keryvm1 kernel: Call Trace: Mar 17 15:22:31 keryvm1 kernel: [] ? dump_stack+0x41/0x51 Mar 17 15:22:31 keryvm1 kernel: [] ? warn_slowpath_common+0x77/0x90 Mar 17 15:22:31 keryvm1 kernel: [] ? __ext4_handle_dirty_metadata+0x18e/0x1d0 [ext4] Mar 17 15:22:31 keryvm1 kernel: [] ? ext4_dirty_inode+0x25/0x60 [ext4] Mar 17 15:22:31 keryvm1 kernel: [] ? ext4_free_blocks+0x602/0xb90 [ext4] Mar 17 15:22:31 keryvm1 kernel: [] ? jbd2_journal_extend+0x71/0x1a0
Bug#818502: Kernel Bug Tracker – Bug 102731
for reference https://bugzilla.kernel.org/show_bug.cgi?id=102731 -- Zito
Bug#539617: I seconded for an option --quiet or so
Hi,
I have prepared some by hand upgrade recipe for fabric, where I have in
fabfile.py...
def _ensure_perl_readline():
rlname = run("""perl -MTerm::ReadLine -e
'print(Term::ReadLine->ReadLine())'""", quiet=True)
if not rlname == "Term::ReadLine::Gnu":
run('aptitude install -q -q libterm-readline-gnu-perl')
@parallel
def aptitude_update():
run('aptitude update', quiet=True)
def aptitude_upgrade():
run('DEBIAN_FRONTEND=readline aptitude -q -q safe-upgrade')
@task
@runs_once
def upgrade():
_ensure_perl_readline()
execute(aptitude_update)
execute(aptitude_upgrade)
The output of dpkg is problem. I want to have tty because of debconf
interactive questions. Now the output is e.g.:
zito@ser1:~/admin$ fab -H nsi1.brn.i.cz upgrade
[nsi1.brn.i.cz] Executing task 'upgrade'
[nsi1.brn.i.cz] run: aptitude install -q -q libterm-readline-gnu-perl
[nsi1.brn.i.cz] out: The following NEW packages will be installed:
[nsi1.brn.i.cz] out: libterm-readline-gnu-perl
[nsi1.brn.i.cz] out: 0 packages upgraded, 1 newly installed, 0 to remove and 1
not upgraded.
[nsi1.brn.i.cz] out: Need to get 99.1 kB of archives. After unpacking 266 kB
will be used.
[nsi1.brn.i.cz] out: Selecting previously unselected package
libterm-readline-gnu-perl.
[nsi1.brn.i.cz] out: (Reading database ...
[nsi1.brn.i.cz] out: (Reading database ... 5%
[nsi1.brn.i.cz] out: (Reading database ... 10%
[nsi1.brn.i.cz] out: (Reading database ... 15%
[nsi1.brn.i.cz] out: (Reading database ... 20%
[nsi1.brn.i.cz] out: (Reading database ... 25%
[nsi1.brn.i.cz] out: (Reading database ... 30%
[nsi1.brn.i.cz] out: (Reading database ... 35%
[nsi1.brn.i.cz] out: (Reading database ... 40%
[nsi1.brn.i.cz] out: (Reading database ... 45%
[nsi1.brn.i.cz] out: (Reading database ... 50%
[nsi1.brn.i.cz] out: (Reading database ... 55%
[nsi1.brn.i.cz] out: (Reading database ... 60%
[nsi1.brn.i.cz] out: (Reading database ... 65%
[nsi1.brn.i.cz] out: (Reading database ... 70%
[nsi1.brn.i.cz] out: (Reading database ... 75%
[nsi1.brn.i.cz] out: (Reading database ... 80%
[nsi1.brn.i.cz] out: (Reading database ... 85%
[nsi1.brn.i.cz] out: (Reading database ... 90%
[nsi1.brn.i.cz] out: (Reading database ... 95%
[nsi1.brn.i.cz] out: (Reading database ... 100%
[nsi1.brn.i.cz] out: (Reading database ... 4 files and directories
currently installed.)
[nsi1.brn.i.cz] out: Preparing to unpack
.../libterm-readline-gnu-perl_1.24-2+b1_amd64.deb ...
[nsi1.brn.i.cz] out: Unpacking libterm-readline-gnu-perl (1.24-2+b1) ...
[nsi1.brn.i.cz] out: Processing triggers for man-db (2.7.0.2-5) ...
[nsi1.brn.i.cz] out: Setting up libterm-readline-gnu-perl (1.24-2+b1) ...
[nsi1.brn.i.cz] out:
[nsi1.brn.i.cz] Executing task 'aptitude_update'
[nsi1.brn.i.cz] Executing task 'aptitude_upgrade'
[nsi1.brn.i.cz] run: DEBIAN_FRONTEND=readline aptitude -q -q safe-upgrade
[nsi1.brn.i.cz] out: The following packages will be upgraded:
[nsi1.brn.i.cz] out: linux-image-3.16.0-4-amd64
[nsi1.brn.i.cz] out: 1 packages upgraded, 0 newly installed, 0 to remove and 0
not upgraded.
[nsi1.brn.i.cz] out: Need to get 0 B/33.8 MB of archives. After unpacking
1,024 B will be used.
[nsi1.brn.i.cz] out: Do you want to continue? [Y/n/?]
[nsi1.brn.i.cz] out: Preconfiguring packages ...
[nsi1.brn.i.cz] out: (Reading database ...
[nsi1.brn.i.cz] out: (Reading database ... 5%
[nsi1.brn.i.cz] out: (Reading database ... 10%
[nsi1.brn.i.cz] out: (Reading database ... 15%
[nsi1.brn.i.cz] out: (Reading database ... 20%
[nsi1.brn.i.cz] out: (Reading database ... 25%
[nsi1.brn.i.cz] out: (Reading database ... 30%
[nsi1.brn.i.cz] out: (Reading database ... 35%
[nsi1.brn.i.cz] out: (Reading database ... 40%
[nsi1.brn.i.cz] out: (Reading database ... 45%
[nsi1.brn.i.cz] out: (Reading database ... 50%
[nsi1.brn.i.cz] out: (Reading database ... 55%
[nsi1.brn.i.cz] out: (Reading database ... 60%
[nsi1.brn.i.cz] out: (Reading database ... 65%
[nsi1.brn.i.cz] out: (Reading database ... 70%
[nsi1.brn.i.cz] out: (Reading database ... 75%
[nsi1.brn.i.cz] out: (Reading database ... 80%
[nsi1.brn.i.cz] out: (Reading database ... 85%
[nsi1.brn.i.cz] out: (Reading database ... 90%
[nsi1.brn.i.cz] out: (Reading database ... 95%
[nsi1.brn.i.cz] out: (Reading database ... 100%
[nsi1.brn.i.cz] out: (Reading database ... 44468 files and directories
currently installed.)
[nsi1.brn.i.cz] out: Preparing to unpack
.../linux-image-3.16.0-4-amd64_3.16.7-ckt20-1+deb8u3_amd64.deb ...
[nsi1.brn.i.cz] out: Unpacking linux-image-3.16.0-4-amd64
(3.16.7-ckt20-1+deb8u3) over (3.16.7-ckt20-1+deb8u2) ...
[nsi1.brn.i.cz] out: Setting up linux-image-3.16.0-4-amd64
(3.16.7-ckt20-1+deb8u3) ...
[nsi1.brn.i.cz] out: /etc/kernel/postinst.d/initramfs-tools:
[nsi1.brn.i.cz] out: update-initramfs: Generating
/boot/initrd.img-3.16.0-4-amd64
[nsi1.brn.i.cz] out: W: Possible missing firmware
/lib/firmware/tigon/tg3_tso5.bin for module tg3
Bug#793377: A mouse and keyboard problem (randomly lose keystrokes)
On Wed, Sep 30, 2015 at 10:02:29PM +0200, Sven Arvidsson wrote: > On Wed, 2015-09-30 at 21:18 +0200, Václav Ovsík wrote: > > After reboot there is some delay time (several seconds), that when > > USB > > keyboard or mouse is idle longer than this delay it froze. > > Next keystroke after this delay is lost, but this lost keystroke > > wakes > > keyboard up and next keystrokes are sent again, until there is > > another > > longer delay. Mouse must be woke-up by pressing button. This woke-up > > click is lost, but mouse works, until another delay normally. > > > > Simple disconnect and reconnect both devices fixes this problem till > > another reboot. > > Could you try this: > http://askubuntu.com/questions/80638/how-to-disable-auto-power-off-of-usb-devices-like-usb-mouse My previous description wasn't accurate. The keyboard lost keystrokes randomly really - not exactly the first hit when suspended. zito@bobek:~$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M |__ Port 8: Dev 3, If 0, Class=Application Specific Interface, Driver=, 12M |__ Port 8: Dev 3, If 1, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/3p, 480M |__ Port 1: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 4: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 5, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 4: Dev 5, If 3, Class=Application Specific Interface, Driver=, 12M After reboot the keyboard and the mouse autosuspends: zito@bobek:~$ for x in /sys/bus/usb/devices/*/power/autosuspend; do echo "$x: $(cat $x)"; done /sys/bus/usb/devices/1-1.1/power/autosuspend: 2 /sys/bus/usb/devices/1-1.2.1/power/autosuspend: 2 /sys/bus/usb/devices/1-1.2.2/power/autosuspend: 2 /sys/bus/usb/devices/1-1.2/power/autosuspend: 2 /sys/bus/usb/devices/1-1.4/power/autosuspend: 2 /sys/bus/usb/devices/1-1/power/autosuspend: 2 /sys/bus/usb/devices/2-1.8/power/autosuspend: 2 /sys/bus/usb/devices/2-1/power/autosuspend: 2 /sys/bus/usb/devices/usb1/power/autosuspend: 2 /sys/bus/usb/devices/usb2/power/autosuspend: 2 zito@bobek:~$ for x in /sys/bus/usb/devices/*/power/level; do echo "$x: $(cat $x)"; done /sys/bus/usb/devices/1-1.1/power/level: auto /sys/bus/usb/devices/1-1.2.1/power/level: auto /sys/bus/usb/devices/1-1.2.2/power/level: auto /sys/bus/usb/devices/1-1.2/power/level: auto /sys/bus/usb/devices/1-1.4/power/level: auto /sys/bus/usb/devices/1-1/power/level: auto /sys/bus/usb/devices/2-1.8/power/level: auto /sys/bus/usb/devices/2-1/power/level: auto /sys/bus/usb/devices/usb1/power/level: auto /sys/bus/usb/devices/usb2/power/level: auto Disconnecting & reconnecting the keyboard and the mouse, the problem is gone: zito@bobek:~$ for x in /sys/bus/usb/devices/*/power/autosuspend; do echo "$x: $(cat $x)"; done /sys/bus/usb/devices/1-1.1/power/autosuspend: 2 /sys/bus/usb/devices/1-1.2.1/power/autosuspend: 2 /sys/bus/usb/devices/1-1.2.2/power/autosuspend: 2 /sys/bus/usb/devices/1-1.2/power/autosuspend: 2 /sys/bus/usb/devices/1-1.4/power/autosuspend: 2 /sys/bus/usb/devices/1-1/power/autosuspend: 2 /sys/bus/usb/devices/2-1.8/power/autosuspend: 2 /sys/bus/usb/devices/2-1/power/autosuspend: 2 /sys/bus/usb/devices/usb1/power/autosuspend: 2 /sys/bus/usb/devices/usb2/power/autosuspend: 2 zito@bobek:~$ for x in /sys/bus/usb/devices/*/power/level; do echo "$x: $(cat $x)"; done /sys/bus/usb/devices/1-1.1/power/level: auto /sys/bus/usb/devices/1-1.2.1/power/level: on /sys/bus/usb/devices/1-1.2.2/power/level: on /sys/bus/usb/devices/1-1.2/power/level: auto /sys/bus/usb/devices/1-1.4/power/level: auto /sys/bus/usb/devices/1-1/power/level: auto /sys/bus/usb/devices/2-1.8/power/level: auto /sys/bus/usb/devices/2-1/power/level: auto /sys/bus/usb/devices/usb1/power/level: auto /sys/bus/usb/devices/usb2/power/level: auto Both reconnected HID devices has power level on. -- Zito
Bug#788169: libustr-dev, libustr-1.0-1-dbg: copyright file missing after upgrade (policy 12.5)
Hi, thanks for the bug-report! I overlooked this :( Ustr bug-fix version 1.0.4-5 is waiting for a sponsor at http://mentors.debian.net/package/ustr https://anonscm.debian.org/cgit/users/zito-guest/pkg-ustr.git/tag/?id=debian/1.0.4-5 Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788218: RFS: ustr/1.0.4-5
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package ustr
* Package name: ustr
Version : 1.0.4-5
Upstream Author : James Antill ja...@and.org
* URL : http://www.and.org/ustr/
* License : LGPL, BSD, MIT
Section : libs
It builds those binary packages:
libustr-1.0-1 - Micro string library: shared library
libustr-1.0-1-dbg - Micro string library: debugging symbols
libustr-dev - Micro string library: development stuff
libustr-doc - Micro string library: documentation
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/ustr
Alternatively, one can download the package with dget using this command:
dget -x http://mentors.debian.net/debian/pool/main/u/ustr/ustr_1.0.4-5.dsc
Changes since the last upload:
* Fixed transition from the doc directory to a symlink
/usr/share/doc/PACKAGE for libustr-1.0-1-dbg and libustr-dev
by added {libustr-1.0-1-dbg,libustr-dev}.maintscript.
Closes: #788169
Regards
--
Václav Ovsík
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737214: problem persist in 1.1.35-3
Hi,
I tried to setup DS Admin today:
[15/03/30:11:02:44] - [Setup] Info Are you ready to set up your servers?
[15/03/30:11:02:57] - [Setup] Info yes
[15/03/30:11:02:57] - [Setup] Info Creating directory server . . .
[15/03/30:11:03:01] - [Setup] Info Your new DS instance 'pkit' was
successfully created.
[15/03/30:11:03:01] - [Setup] Info Creating the configuration directory server
. . .
[15/03/30:11:03:01] - [Setup] Info Beginning Admin Server creation . . .
[15/03/30:11:03:01] - [Setup] Info Creating Admin Server files and directories
. . .
[15/03/30:11:03:01] - [Setup] Info Updating adm.conf . . .
[15/03/30:11:03:01] - [Setup] Info Updating admpw . . .
[15/03/30:11:03:01] - [Setup] Info Registering admin server with the
configuration directory server . . .
[15/03/30:11:03:02] - [Setup] Info Updating adm.conf with information from
configuration directory server . . .
[15/03/30:11:03:02] - [Setup] Info Updating the configuration for the httpd
engine . . .
Error updating console.conf:
/usr/lib/x86_64-linux-gnu/dirsrv/cgi-bin/config: error while loading shared
libraries: libsoftokn3.so: cannot open shared object file: No such file or
directory
[15/03/30:11:03:02] - [Setup] Fatal Failed to create and configure the admin
server
[15/03/30:11:03:02] - [Setup] Fatal Exiting . . .
Last fix (add-softokn-ldlibpath.diff) solves problem in start-ds-admin, but
setup-ds-admin should be solved separately probably.
I succeeded (setup-ds-admin) with a change attached.
Kindly Regards
--
Zito
--- AdminServer.pm~ 2015-03-10 09:02:35.0 +0100
+++ AdminServer.pm 2015-03-30 12:24:26.25200 +0200
@@ -371,6 +371,7 @@
my $savepath = $ENV{SHLIB_PATH} || $ENV{LD_LIBRARY_PATH};
$ENV{LD_LIBRARY_PATH} = ;
libpath_add(/usr/lib/x86_64-linux-gnu);
+libpath_add(/usr/lib/x86_64-linux-gnu/nss);
libpath_add($savepath);
$ENV{SHLIB_PATH} = $ENV{LD_LIBRARY_PATH};
my $cmd = /usr/lib/x86_64-linux-gnu/dirsrv/cgi-bin/config op=set configuration.nsSuiteSpotUser=\$user\;
Bug#777460: not a patch
On Fri, Mar 06, 2015 at 06:25:57PM +0100, Matthias Klose wrote: Control: tags -1 - patch the workaround doesn't work. These header files are installed as system headers, and really have to be fixed. What a pity I prepared gcc detection in autoconf and --std=gnu89, but this sounds logical. If the problem is in headers included in another project... I will look at this. -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765099: /usr/lib/PXELINUX/pxelinux.0: pxelinux.0 backward configuration incompatibility?
On Mon, Oct 13, 2014 at 10:18:45PM +0200, Daniel Baumann wrote: Ady2 pointed out what i've overlooked: you're using a global append, please see http://www.syslinux.org/wiki/index.php/Directives/append#default I have red the above documentation carefully and the problem is clear to me now. Sorry for wasteful bug-report :(. I will adapt old configs to this new semantics. Thanks you very much for pointing me to the above page. Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762018: systemd: v215 - rootfs left in read-only - not everytime
Hi, On Thu, Sep 18, 2014 at 08:08:48PM +0200, Sjoerd Simons wrote: ... Are you using laptop-mode-tools ? Yes, I use laptop-mode-tools 1.65-2 I'm running on Dell Latitude E6520 with SSD 256GB. I tried five reboots today, and one time the startup was successful (read-write root). The rest startups was with read-only root. bobek:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert Edata ssd -wi-ao 128.00g Ehome ssd -wi-ao 20.00g Eroot ssd -wi-ao 36.00g Eswap ssd -wi-ao 8.00g boot ssd -wi-ao 256.00m LVs with `E' prefix uses LUKS bobek:~# cat /etc/crypttab # target device source device key file options root /dev/mapper/ssd-Erootnonediscard,luks swap /dev/mapper/ssd-Eswap/etc/keys/mykey discard,luks home /dev/mapper/ssd-Ehome/etc/keys/mykey discard,luks data /dev/mapper/ssd-Edata/etc/keys/mykey discard,luks I have removed ipmitool, so the service ipmievd is away (there was errors about inserting ipmi_si module). The log is now shorter, error messages at start are: bobek:~# journalctl -p err|head -- Logs begin at Fri 2014-09-19 09:44:06 CEST, end at Fri 2014-09-19 10:18:04 CEST. -- Sep 19 09:44:07 bobek systemd-udevd[358]: Error calling EVIOCSKEYCODE on device node '/dev/input/event16' (scan code 0x150, key code 190): Invalid argument Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: chmod(/var) failed: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: chmod(/var/log) failed: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: chmod(/var/lib) failed: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: chmod(/var/lib/systemd) failed: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: chmod(/var/lib/systemd/coredump) failed: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: Failed to create file /var/log/wtmp: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: Failed to create file /var/log/btmp: Read-only file system Sep 19 09:44:09 bobek systemd-tmpfiles[3284]: chmod(/var/cache) failed: Read-only file system Maybe the problem is about some race condition? -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762018: systemd: v215 - rootfs left in read-only - not everytime
On Fri, Sep 19, 2014 at 01:58:06PM +0200, Sjoerd Simons wrote: ... I'ts most likely laptop-mode-tools, can you remove it and let me know if that helps? I removed it and tried startup 3 times. All startups were successful. I install laptop-mode-tools back and tried: 1. fail 2. ok 3. ok 4. fail I removed it again and did a reboot. Startup was successful. I will leave laptop-mode-tools removed now. It really looks like there is some problem with it. Thanks -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721352: ustr: do not use cross-built binaries during the build
Dear Peter, Thank you very much for your precise step by step guide! I think you should public it somewhere, maybe wiki.debian.org. On Sun, Aug 17, 2014 at 10:51:11PM +0300, Peter Pentchev wrote: ... OK, so it wasn't quite simple, but, well, I do believe this is still one of the simplest ways to create a cross-build environment from scratch on a recent Debian system. Here's hoping that this didn't scare you too much, and here's hoping that it actually helped :) :). I started to play with bootstrap.sh. (There are some chunks of patches, that are applied upstream (gcc-4.9) and need to be dropped in bootstrap.sh.) Thank you very much for your great help! Cheers -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757945: approx: delivers outdated data
Package: approx
Version: 5.3-1
Severity: normal
Dear Maintainer,
Thank you for your time and work on packaging Approx.
I'm using Approx for long time. I have no problems on central
locality, where approx is running on architecture amd64.
I noticed some problems on remote locality and solved this by cleaning
Approx's cache.
I looked on problem a bit more today.
I'm running a regular job to prepare the PXE boot with Debian installer.
Debian installer on my remote locality behaved strangely (different
versions of kernel and modules...)
My script does this:
...
MIRROR=http://localhost:/debian
...
curl -s
$MIRROR/dists/$dist/main/installer-$arch/current/images/netboot/netboot.tar.gz \
| tar -zxf -
...
The extracted installer is outdated. I looked into cache and yes:
-rw-r--r-- 1 approx approx 13688418 Jun 13 2013
/var/cache/approx/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz
I have switched debug and verbose on and try to download the file using
curl from upstream and via Approx:
zito@lin:~$ curl -v
http://ftp.debian.cz/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz
/dev/null
* About to connect() to ftp.debian.cz port 80 (#0)
* Trying 195.113.161.73...
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0* connected
* Connected to ftp.debian.cz (195.113.161.73) port 80 (#0)
GET
/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz
HTTP/1.1
User-Agent: curl/7.26.0
Host: ftp.debian.cz
Accept: */*
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
HTTP/1.1 200 OK
Date: Tue, 12 Aug 2014 16:01:39 GMT
Server: Apache/2.2.22 (Debian)
Last-Modified: Thu, 24 Apr 2014 07:45:31 GMT
ETag: 1e00443-d1474b-4f7c5088e3cc0
Accept-Ranges: bytes
Content-Length: 13715275
Content-Type: application/x-gzip
{ [data not shown]
3 13.0M3 526k0 0 225k 0 0:00:59 0:00:02 0:00:57
234k^C
The upstream returned header Last-Modified: Thu, 24 Apr 2014 07:45:31 GMT.
zito@lin:~$ curl -v
http://localhost:/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz
/dev/null
* About to connect() to localhost port (#0)
* Trying 127.0.0.1...
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:--
0* connected
* Connected to localhost (127.0.0.1) port (#0)
GET
/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz
HTTP/1.1
User-Agent: curl/7.26.0
Host: localhost:
Accept: */*
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
HTTP/1.1 200 OK
Last-Modified: Thu, 13 Jun 2013 10:15:26 GMT
Content-Type: text/plain
Content-Length: 13688418
Date: Tue, 12 Aug 2014 16:03:37 GMT
Server: approx/5.3 Ocamlnet/3.5.1
{ [data not shown]
100 13.0M 100 13.0M0 0 97.9M 0 --:--:-- --:--:-- --:--:-- 99.6M
* Connection #0 to host localhost left intact
* Closing connection #0
Approx returned old data.
Aug 12 18:03:37 lin approx[5897]: Connection from 127.0.0.1 port 38302
Aug 12 18:03:37 lin approx[5897]: Request: GET
/debian/dists/stable/main/installer-amd64/current/images/netboot/netboot.tar.gz
Aug 12 18:03:37 lin approx[5897]: User-Agent: curl/7.26.0
Aug 12 18:03:37 lin approx[5897]: Host: localhost:
Aug 12 18:03:37 lin approx[5897]: Accept: */*
Aug 12 18:03:37 lin approx[5897]: = delivering from cache
Aug 12 18:03:37 lin approx[5897]: Local response
Aug 12 18:03:37 lin approx[5897]: Last-Modified: Thu, 13 Jun 2013 10:15:26
GMT
Aug 12 18:03:37 lin approx[5897]: Content-Type: text/plain
Aug 12 18:03:37 lin approx[5897]: Content-Length: 13688418
I hope this is not my miss-configuration somewhere...
Cheers
--
Zito
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages approx depends on:
ii adduser 3.113+nmu3
ii curl 7.26.0-1+wheezy9
ii debconf [debconf-2.0]1.5.49
ii libc62.13-38+deb7u3
ii libpcre3 1:8.30-5
ii rsyslog [system-log-daemon] 5.8.11-3
ii update-inetd 4.43
ii xinetd [inet-superserver]
Bug#751621: steam launcher crash
Hi Mike, thank you for work on this package! On Sun, Aug 03, 2014 at 11:42:05PM -0400, Michael Gilbert wrote: /home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/tier0/threadtools.cpp (2024) : Assertion Failed: File exists It looks like you have file somewhere on your system that the steam binary wants to overwrite but bails out instead. It's not clear which file is the problem. I recommend forwarding this to Valve, since no changes can be made to the steam binary. You may also want to give the newer 1.0.0.48-1 package a try. You are right. I just tried to run steam 1.0.0.48-1 on son's computer under test user and it works OK. The bug is fixed upstream already. This bug can be closed. Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721352: ustr: do not use cross-built binaries during the build
Hi Peter, thanks you for your attention on the ustr packaging. My work on ustr is a bit stuck for some time. One reason is that upstream has no activity for some time (great work of James Antill without bugs fortunately), the other is I tried to prepare cross-build chroot (sbuild) without much success. I'm not educated on cross-building yet :(. Can you direct me how you are cross-building ustr please? Is it possible without Ubuntu packages on current Debian Unstable? Thanks for all patches. I will look at these after some brain restoration :). I forgot almost everything... Cheers -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725826: equivalent bug resolved in icinga #686036
Hi, while considering about switch nagios3 - icinga, I have tested the problem on Icinga and I'm glad the problem is resolved for Wheezy in Icinga already (#686036). I think, the fix can be very similar. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722012: [buildd-tools-devel] Bug#722012: Sbuild::Conf: missing use File::Spec
On Sun, Sep 08, 2013 at 12:11:57AM +0100, Roger Leigh wrote: ... Does this fix work for you? Seems fine here with a cursory test. bobek:~# sbuild-adduser zito The user `zito' is already a member of `sbuild'. # Setup tasks for sudo users: # BUILD # HOME directory in chroot, user:sbuild, 0770 perms, from ... Since the File::Spec-catfile is a class method call, I don't think that the use File::Spec is necessary here, or at the very least wasn't necessary previously. I'm wondering if this is broken due to the recent Perl 5.18 transition since it was working fine before that. Loading of the File::Spec (require File::Spec at least, use is more nice?) is surely necessary. There is no need to import any symbols, but the Perl must load the module to use classes with it. Missing File::Spec in the past may be working due to module was used by some other module from Sbuild or any other Perl module Sbuild uses. If the module was used by some Perl module included within it, then transition to the version 5.18 can affect the bug I think. Cheers -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722012: another Perl problem in sbuild-createchroot
Hi,
I'm not certain to start another bug report...
bobek:~# sbuild-createchroot
--make-sbuild-tarball=/var/lib/sbuild/sid-amd64.tar.gz sid `mktemp -d`
http://br0.localdomain:/debian
...
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
'tempfile' can't be called as a method at /usr/sbin/sbuild-createchroot line
395.
To fix:
--- sbuild-createchroot~2013-05-18 00:36:09.0 +0200
+++ sbuild-createchroot 2013-09-08 13:37:08.919671295 +0200
@@ -137,7 +137,7 @@
use Sbuild::Sysconfig;
use Sbuild::Conf qw();
use File::Path qw(mkpath rmtree);
-use File::Temp ();
+use File::Temp qw(tempfile);
use File::Copy;
use Cwd qw(abs_path);
@@ -392,7 +392,7 @@
# the sbuild chroot directory created, unless it's been requested to keep the
# directory.
if ($conf-get('MAKE_SBUILD_TARBALL')) {
-my ($tmpfh, $tmpfile) = File::Temp-tempfile(XX);
+my ($tmpfh, $tmpfile) = tempfile(XX);
my @program_list;
# Change program arguments accordingly
result is:
bobek:~# sbuild-createchroot
--make-sbuild-tarball=/var/lib/sbuild/sid-amd64.tar.gz sid `mktemp -d`
http://br0.localdomain:/debian
...
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I: chroot /tmp/tmp.97dJrCDdo3 has been removed.
I: Successfully set up sid chroot.
I: Run sbuild-adduser to add new sbuild users.
Maybe, more Perl related problems will appear...
Cheers
--
Zito
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716678: resource-agents: pgsql: bashism
Package: resource-agents Version: 1:3.9.2-5+deb7u1 Severity: normal File: /usr/lib/ocf/resource.d/heartbeat/pgsql Dear Maintainer, HA cluster with configured PostgreSQL log: Jul 11 11:02:19 ser2 lrmd: [8924]: info: RA output: (postgres:monitor:stderr) /usr/lib/ocf/resource.d//heartbeat/pgsql: 647: [: monitor: unexpected operator every minute :(. There is the bashism on the line num. 647. Easy fix: --- pgsql~ 2013-01-06 23:50:54.0 +0100 +++ pgsql 2013-07-11 11:11:47.164778276 +0200 @@ -644,7 +644,7 @@ pgsql_validate_all rc=$? -[ $1 == validate-all ] exit $rc +[ $1 = validate-all ] exit $rc if [ $rc -ne 0 ] then This bug is fixed in unstable version 1:3.9.3+git20121009-3. Thanks for your work! Cheers -- Zito -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages resource-agents depends on: ii cluster-glue 1.0.9+hg2665-1 ii libc6 2.13-38 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libnet1 1.1.4-2.1 ii libplumb2 1.0.9+hg2665-1 ii libplumbgpl2 1.0.9+hg2665-1 ii python2.7.3-4 resource-agents recommends no packages. resource-agents suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714281: more info patch
Hi, I rebuilt nagios-plugins with `nostrip' option, so I found the place/places where the plugin fails. To clarify things a bit - I'm preparing a new monitoring system and access from its new IP address is not allowed everywhere yet. So some checks fails now and some (check_nt in this case) segfaults. I have a 35 core dumps now and it was dumped at two places: 18 times: Core was generated by `/usr/lib/nagios/plugins/check_nt -H 192.168.71.23 -p 12489 -v MEMUSE -p 12489 -'. ... (gdb) frame 2 #2 main (argc=13, argv=0x7fffad2b6458) at check_nt.c:278 278 mem_commitLimit=atof(strtok(recv_buffer,)); 17 times: Core was generated by `/usr/lib/nagios/plugins/check_nt -H 192.168.71.23 -p 12489 -v SERVICESTATE -p 1'. ... (gdb) frame 2 #2 main (argc=13, argv=0x7fff44d25368) at check_nt.c:268 268 return_code=atoi(strtok(recv_buffer,)); A connection to agent didn't transfer the required data and recv_buffer is (gdb) print recv_buffer $1 = '\000' repeats 8191 times A call to strtok() returned NULL and atoi() segfaults on such argument. It is a bad idea to call atoi() on strtok() returned value without testing. Nagios plugins rebuilt with the patch attached works without a segfault for one day now. Cheers -- Zito #! /bin/sh /usr/share/dpatch/dpatch-run ## 10_check_nt_npe.dpatch by Vaclav Ovsik vaclav.ov...@i.cz ## ## DP: Fixes some NULL pointer dereference in check_nt. @DPATCH@ diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' nagios-plugins-1.4.16~/plugins/check_nt.c nagios-plugins-1.4.16/plugins/check_nt.c --- nagios-plugins-1.4.16~/plugins/check_nt.c 2013-06-29 18:11:20.0 +0200 +++ nagios-plugins-1.4.16/plugins/check_nt.c2013-06-29 18:22:52.0 +0200 @@ -94,6 +94,7 @@ char *description=NULL,*counter_unit = NULL; char *minval = NULL, *maxval = NULL, *errcvt = NULL; char *fds=NULL, *tds=NULL; + char *numstr; double total_disk_space=0; double free_disk_space=0; @@ -265,7 +266,10 @@ asprintf(send_buffer,%s%u%s%s, req_password,(vars_to_check==CHECK_SERVICESTATE)?5:6, (show_all==TRUE) ? ShowAll : ShowFail,value_list); fetch_data (server_address, server_port, send_buffer); - return_code=atoi(strtok(recv_buffer,)); + numstr = strtok(recv_buffer,); + if (numstr == NULL) + die(STATE_UNKNOWN, _(could not fetch information from server\n)); + return_code=atoi(numstr); temp_string=strtok(NULL,); output_message = strdup (temp_string); } @@ -275,8 +279,14 @@ asprintf(send_buffer,%s7, req_password); fetch_data (server_address, server_port, send_buffer); - mem_commitLimit=atof(strtok(recv_buffer,)); - mem_commitByte=atof(strtok(NULL,)); + numstr = strtok(recv_buffer,); + if (numstr == NULL) + die(STATE_UNKNOWN, _(could not fetch information from server\n)); + mem_commitLimit=atof(numstr); + numstr = strtok(NULL,); + if (numstr == NULL) + die(STATE_UNKNOWN, _(could not fetch information from server\n)); + mem_commitByte=atof(numstr); percent_used_space = (mem_commitByte / mem_commitLimit) * 100; warning_used_space = ((float)warning_value / 100) * mem_commitLimit; critical_used_space = ((float)critical_value / 100) * mem_commitLimit;
Bug#709014: /etc/init.d/smstools: init script reload action should not start disabled service
Package: smstools Version: 3.1.14-1.2 Severity: normal File: /etc/init.d/smstools Dear Maintainer, after server upgrade to Debian Wheezy and so smstools 3.1.14-1.2 I have been hit by problem that smsd was started by logrotate postrotate action: invoke-rc.d smstools reload /dev/null I have disabled smstools (update-rc.d smstools disable): rt:/etc# ls -la /etc/rc?.d/*smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc0.d/K01smstools - ../init.d/smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc1.d/K01smstools - ../init.d/smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc2.d/K01smstools - ../init.d/smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc3.d/K01smstools - ../init.d/smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc4.d/K01smstools - ../init.d/smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc5.d/K01smstools - ../init.d/smstools lrwxrwxrwx 1 root root 18 Nov 26 2010 /etc/rc6.d/K01smstools - ../init.d/smstools The reload action starts smsd and should not. According to invoke-rc.d's bugreport http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502195 this is problem of init-script and not invoke-rc.d. Please, can you modify the init script smstools to test if a smsd is running like e.g. the apache does? Thanks for your time. Cheers -- Zito -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smstools depends on: ii adduser 3.113+nmu3 ii debconf 1.5.49 ii libc62.13-38 ii libmm14 1.4.2-4 ii ucf 3.0025+nmu3 smstools recommends no packages. smstools suggests no packages. -- Configuration Files: /etc/logcheck/ignore.d.server/smstools [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/smstools' /etc/logrotate.d/smstools changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707878: reversed patch...
Hi,
the patch in bugreport was reversed of course :(.
The correct patch attached.
Cheers
--
Zito
--- /usr/lib/ocf/resource.d/heartbeat/Pure-FTPd~ 2013-01-06 23:50:54.0 +0100
+++ /usr/lib/ocf/resource.d/heartbeat/Pure-FTPd 2013-05-11 22:53:36.294700215 +0200
@@ -206,6 +206,9 @@
exit $OCF_ERR_ARGS
fi
+piddir=${OCF_RESKEY_pidfile%/*}
+[ -e $piddir ] || mkdir $piddir
+
case $1 in
start) PureFTPd_start
;;
Bug#707878: resource-agents: Pure-FTPd RA should create directory for pidfile
Package: resource-agents
Version: 1:3.9.2-5+deb7u1
Severity: normal
Dear Maintainer,
as of Wheezy, /var/run (/run) directory is tmpfs filesystem without
persistent directories. Pure-FTPd System V init script handles this
by creating /var/run/pure-ftpd by itself early.
I was very confused by behaviour of Heartbeat with configured RA
Pure-FTPd, because pure-ftpd creates directory lately by itself, but
without pidfile! I was hunting the problem for hours :).
It was not evident to me the pidfile parent directory is missing
after machine reboot during first FTP startup. FTP daemon was started,
but Heartbeat was not know about it and tried to start it again and
again without success of course (address was used by orphaned daemon
already).
The correct behaviour is back after inserting this:
--- /usr/lib/ocf/resource.d/heartbeat/Pure-FTPd 2013-05-11 22:53:36.294700215
+0200
+++ /usr/lib/ocf/resource.d/heartbeat/Pure-FTPd~2013-01-06
23:50:54.0 +0100
@@ -206,9 +206,6 @@
exit $OCF_ERR_ARGS
fi
-piddir=${OCF_RESKEY_pidfile%/*}
-[ -e $piddir ] || mkdir $piddir
-
case $1 in
start) PureFTPd_start
;;
Thanks for your work!
Cheers
--
Zito
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages resource-agents depends on:
ii cluster-glue 1.0.9+hg2665-1
ii libc6 2.13-38
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libnet1 1.1.4-2.1
ii libplumb2 1.0.9+hg2665-1
ii libplumbgpl2 1.0.9+hg2665-1
ii python2.7.3-4
resource-agents recommends no packages.
resource-agents suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697698: broken configury with glibc headers moved to the multiarch location
Dear Matthias, On Tue, Jan 08, 2013 at 05:43:46PM +0100, Matthias Klose wrote: Package: ustr Version: 1.0.4-3 Severity: serious Tags: sid wheezy patch the configury is broken with glibc headers moved to the multiarch location, resulting in a wrong value for HAVE_STDINT. I didn't check for other brokenness. A patch is included in http://launchpadlibrarian.net/127920247/ustr_1.0.4-3_1.0.4-3ubuntu1.diff.gz which includes patches to cross build the package. As a side note, it would be nice to make the -dev package m-a: same as well. Thank you for a patch! My intention is to play a bit with the problem you identified. I red some information about cross-building, but must to say I'm still not able to setup the right environment for building the package. Please can you give me some link or info how to do cross build of some package in sane way? I have added deb http://www.emdebian.org/debian sid main into my sources.list. Installed emdebian-toolchain-armel. I have installed gcc-4.7-arm-linux-gnueabi (also tried 4.6...), but symlinks arm-linux-gnueabi-gcc and others was not created. pdebuild-cross stops at: make[1]: arm-linux-gnueabi-gcc: Command not found Please, How to setup the symlink the right way? Maybe I'm going in completely wrong way? Cheers -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671707: isc-dhcp-client: missing udp checksum patch
Package: isc-dhcp-client
Version: 4.2.4-4
Followup-For: Bug #671707
Dear Maintainer,
After switching the type of network interface of KVM virtual host
(Debian Sid) to virtio, I have got:
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:16:3e:52:3d:8b
Sending on LPF/eth0/00:16:3e:52:3d:8b
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
5 bad udp checksums in 5 packets
No DHCPOFFERS received.
Unable to obtain a lease on first try. Exiting.
Failed to bring up eth0.
I have configured a static bridge br0 and dnsmasq serving DHCP requests
of my virtual hosts.
I found this bug-report after some googling. I have tried to rebuild
isc-dhcp package with a patch dhcp-4.2.2-xen-checksum.patch from Fedora
project (attached) and the resulting dhclient works ok.
The patch is extracted from
http://mirror.karneval.cz/pub/linux/fedora/linux/releases/17/Fedora/source/SRPMS/d/dhcp-4.2.4-0.4.rc1.fc17.src.rpm
I have refreshed the patch using quilt.
Can you add this patch into the Debian package too?
Thanks for your work!
Cheers
--
Zito
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
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 isc-dhcp-client depends on:
ii debianutils 4.3.4
ii iproute 20120521-3
ii isc-dhcp-common 4.2.4-4
ii libc62.16-0experimental1
isc-dhcp-client recommends no packages.
Versions of packages isc-dhcp-client suggests:
pn avahi-autoipd none
pn resolvconf none
-- no debconf information
Index: isc-dhcp-4.2.4/common/bpf.c
===
--- isc-dhcp-4.2.4.orig/common/bpf.c 2013-01-16 01:03:10.0 +0100
+++ isc-dhcp-4.2.4/common/bpf.c 2013-01-16 01:03:10.0 +0100
@@ -485,7 +485,7 @@
offset = decode_udp_ip_header (interface,
interface - rbuf,
interface - rbuf_offset,
- from, hdr.bh_caplen, paylen);
+ from, hdr.bh_caplen, paylen, 0);
/* If the IP or UDP checksum was bad, skip the packet... */
if (offset 0) {
Index: isc-dhcp-4.2.4/common/dlpi.c
===
--- isc-dhcp-4.2.4.orig/common/dlpi.c 2013-01-16 01:03:10.0 +0100
+++ isc-dhcp-4.2.4/common/dlpi.c 2013-01-16 01:03:10.0 +0100
@@ -693,7 +693,7 @@
length -= offset;
#endif
offset = decode_udp_ip_header (interface, dbuf, bufix,
- from, length, paylen);
+ from, length, paylen, 0);
/*
* If the IP or UDP checksum was bad, skip the packet...
Index: isc-dhcp-4.2.4/common/lpf.c
===
--- isc-dhcp-4.2.4.orig/common/lpf.c 2013-01-16 01:03:10.0 +0100
+++ isc-dhcp-4.2.4/common/lpf.c 2013-01-16 01:03:10.0 +0100
@@ -29,19 +29,33 @@
#include dhcpd.h
#if defined (USE_LPF_SEND) || defined (USE_LPF_RECEIVE)
#include sys/ioctl.h
+#include sys/socket.h
#include sys/uio.h
#include errno.h
#include asm/types.h
#include linux/filter.h
#include linux/if_ether.h
+#include linux/if_packet.h
#include netinet/in_systm.h
-#include net/if_packet.h
#include includes/netinet/ip.h
#include includes/netinet/udp.h
#include includes/netinet/if_ether.h
#include net/if.h
+#ifndef PACKET_AUXDATA
+#define PACKET_AUXDATA 8
+
+struct tpacket_auxdata
+{
+ __u32 tp_status;
+ __u32 tp_len;
+ __u32 tp_snaplen;
+ __u16 tp_mac;
+ __u16 tp_net;
+};
+#endif
+
/* Reinitializes the specified interface after an address change. This
is not required for packet-filter APIs. */
@@ -67,10 +81,14 @@
struct interface_info *info;
{
int sock;
- struct sockaddr sa;
+ union {
+ struct sockaddr_ll ll;
+ struct sockaddr common;
+ } sa;
+ struct ifreq ifr;
/* Make an LPF socket. */
- if ((sock = socket(PF_PACKET, SOCK_PACKET,
+ if ((sock = socket(PF_PACKET, SOCK_RAW,
htons((short)ETH_P_ALL))) 0) {
if (errno == ENOPROTOOPT || errno == EPROTONOSUPPORT ||
errno == ESOCKTNOSUPPORT || errno == EPFNOSUPPORT ||
@@ -85,11 +103,17 @@
log_fatal (Open a socket for LPF: %m);
}
+ memset (ifr, 0, sizeof ifr);
+ strncpy (ifr.ifr_name, (const char *)info - ifp, sizeof ifr.ifr_name);
+ ifr.ifr_name[IFNAMSIZ-1] = '\0';
+ if (ioctl (sock, SIOCGIFINDEX, ifr))
+ log_fatal (Failed to get interface index: %m);
+
/* Bind to the interface name */
memset (sa,
Bug#698112: confirmation
Hi, I can confirm this on i386 virtual machine: Jan 14 09:13:28 ipbx kernel: [8686326.314568] asterisk[21321]: segfault at 1 ip b7501b77 sp b53dd684 error 4 in libc-2.11.3.so[b748c000+14] Jan 14 09:29:12 ipbx kernel: [ 167.335659] asterisk[1181]: segfault at 1 ip b751ab77 sp b53ba684 error 4 in libc-2.11.3.so[b74a5000+14] Jan 14 09:33:51 ipbx kernel: [ 36.331820] asterisk[1001]: segfault at 1 ip b7477b77 sp b5319684 error 4 in libc-2.11.3.so[b7402000+14] I have downgraded to revision 2+squeeze8 Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649217: Bug#638979: grub-mount, os-prober and symlinks traversal failures
On Sun, Nov 18, 2012 at 10:18:13AM +, Colin Watson wrote:
On Fri, Nov 16, 2012 at 08:04:19PM +0100, Václav Ovsík wrote:
affects 638979 +os-prober
thanks
There is already a patch?
http://lists.gnu.org/archive/html/grub-devel/2012-10/msg00021.html
No, that fixes a regression in 2.00 which caused any
symlink-to-directory encountered in a directory's contents to cause the
directory to appear as though it were empty. That bug was not present
in 1.99, where this bug was originally reported in Debian, so please
don't conflate them.
Sorry for my laziness and the low effort to understand a thread I gave
a link :(.
To prove I can give a more effort to this thing I sit down to change
os-prober code to comply with grub-mount feature (symlink behaviour).
A first level of problem is duplicating output of the same kernel/initrd
filename pairs. Duplicates appears because the patterns tried are not
disjunctive at the line 15 of /usr/lib/linux-boot-probes/mounted/90fallback.
for kernpat in /vmlinuz /vmlinux /boot/vmlinuz /boot/vmlinux /boot/vmlinuz* \
/boot/vmlinux* /vmlinuz* /vmlinux* /kernel-*
/boot/kernel-*; do
I don't know why there are pattern pairs /vmlinuz and /vmlinuz* and so
on. Shell wild-card /vmlinuz* is expanded in the alphabetical order,
so potential /vmlinuz alone is expanded always first if exists. I'm not
certain the reasoning... aha in between is /boot/vmlinuz, so if both
exists /vmlinuz and /boot/vmlinuz, they appear in that order
(/boot/vmlinuz appears before /vmlinuzsomething).
...initrd patterns at the line 27...:
initrdname=$(echo $kernfile | sed
s/vmlinu[zx]/initrd\*/)
# Yellow Dog Linux appends .img to it.
initrdname1=${initrdname}.img
The following patch removes duplicates from expanded patterns of kernels and
initrd images:
--- /usr/lib/linux-boot-probes/mounted/90fallback~ 2012-11-18
20:40:05.050334822 +0100
+++ /usr/lib/linux-boot-probes/mounted/90fallback 2012-11-18
21:16:50.846268406 +0100
@@ -21,6 +21,8 @@
fi
for kernfile in $(eval ls $mpoint$kernpat 2/dev/null); do
kernbasefile=$(echo $kernfile | sed s!^$mpoint!!)
+ echo $kernfile_seen | fgrep -q $kernbasefile continue
+ kernfile_seen=$kernfile_seen $kernbasefile
if [ -f $kernfile ] [ ! -L $kernfile ]; then
initrdname=$(echo $kernfile | sed
s/vmlinu[zx]/initrd\*/)
# Yellow Dog Linux appends .img to it.
@@ -35,7 +37,7 @@
# And Gentoo's also
initrdname4=$(echo $kernfile | sed
s/kernel/initramfs\*/)
foundinitrd=0
- for initrd in $(eval ls $initrdname $initrdname1
$initrdname2 $initrdname3 $initrdname4 2/dev/null); do
+ for initrd in $(eval ls $initrdname $initrdname1
$initrdname2 $initrdname3 $initrdname4 2/dev/null | sort | uniq); do
if [ $initrd != $kernfile ] [ -f
$initrd ] [ ! -L $initrd ]; then
initrd=$(echo $initrd | sed
s!^$mpoint!!)
result
$partition:$kernbootpart::$kernbasefile:$initrd:root=$mappedpartition
Before the patch:
bobek:~# /usr/lib/linux-boot-probes/50mounted-tests /dev/mapper/vg-deboot
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/boot/vmlinuz-3.2.0-4-amd64:/boot/initrd.img-3.2.0-4-amd64:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
After the patch:
bobek:~# /usr/lib/linux-boot-probes/50mounted-tests /dev/mapper/vg-deboot
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/boot/vmlinuz-3.2.0-4-amd64:/boot/initrd.img-3.2.0-4-amd64:root=/dev/dm-23
I hope the above change is worth doing anyway.
We can go further and try to identify the identical file's with
different filenames. (This problem is introduced by grub-mount behaviour
on symlinks.)
--- /usr/lib/linux-boot-probes/mounted/90fallback~zito1 2012-11-19
01:04:58.817863969 +0100
+++ /usr/lib/linux-boot-probes/mounted/90fallback 2012-11-19
01:49:23.941785223 +0100
@@ -9,6 +9,11 @@
mpoint=$3
type=$4
+getmd5()
+{
+ md5sum $1 | cut -f1 -d ' '
+}
+
mappedpartition=$(mapdevfs $partition 2/dev/null) ||
mappedpartition=$partition
exitcode=1
@@ -24,6 +29,7 @@
echo $kernfile_seen | fgrep -q $kernbasefile continue
kernfile_seen=$kernfile_seen $kernbasefile
if [ -f $kernfile ] [ ! -L $kernfile ]; then
+ kernmd5
Bug#649217: grub-mount, os-prober and symlinks traversal failures
affects 638979 +os-prober thanks There is already a patch? http://lists.gnu.org/archive/html/grub-devel/2012-10/msg00021.html Cheers -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649217: bug #649217: confirmation and reason found!
Hi,
I am hit by this problem too. I am running Sid.
I debootstrap a second root filesystem into logical volume vg/deboot to
reinstall my original root filesystem. After re-installation of my system from
i386 to amd64 (deboostrap) I decided to save second root filesystem as second
rescue system.
deboot vg -wi-a--- 1.00g
It is ext4 including boot directory, important items follows:
bobek:/tmp# mount /dev/mapper/vg-deboot /mnt/
bobek:/mnt# ls -la vmlinuz initrd.img boot/
lrwxrwxrwx 1 root root 30 Nov 10 18:30 initrd.img -
/boot/initrd.img-3.2.0-4-amd64
lrwxrwxrwx 1 root root 26 Nov 10 18:30 vmlinuz - boot/vmlinuz-3.2.0-4-amd64
boot/:
total 15864
drwxr-xr-x 2 root root 4096 Nov 10 18:34 .
drwxr-xr-x 24 root root 4096 Nov 10 21:58 ..
-rw-r--r-- 1 root root 2100042 Oct 22 18:57 System.map-3.2.0-4-amd64
-rw-r--r-- 1 root root 128869 Oct 22 18:57 config-3.2.0-4-amd64
-rw-r--r-- 1 root root 11170966 Nov 10 18:34 initrd.img-3.2.0-4-amd64
-rw-r--r-- 1 root root 2828288 Oct 22 18:54 vmlinuz-3.2.0-4-amd64
After update-grub I ended with 5 times menuentry for vg-deboot :(.
Investigating the problem I found a kernel/initrd is searched on mounted
partition. A partition is mounted using grub-mount preferably.
You can see this in the /usr/lib/linux-boot-probes/50mounted-tests
Grub-mount is in reality based on fuse.
bobek:/usr/lib/linux-boot-probes# grub-mount /dev/mapper/vg-deboot /mnt/1
bobek:/usr/lib/linux-boot-probes# mount|grep /mnt/1
grub-mount on /mnt/1 type fuse.grub-mount
(rw,nosuid,nodev,relatime,user_id=0,group_id=0)
bobek:/usr/lib/linux-boot-probes# ls -la /mnt/1/{vmlinuz,initrd.img,boot/}
-r--r--r-- 0 root root 32979968 Nov 10 18:30 /mnt/1/initrd.img
-r--r--r-- 0 root root 2828288 Nov 10 18:30 /mnt/1/vmlinuz
/mnt/1/boot/:
total 37147
dr-xr-xr-x 0 root root0 Nov 10 18:34 .
dr-xr-xr-x 0 root root0 Jan 1 1970 ..
-r--r--r-- 0 root root 2100042 Oct 22 18:57 System.map-3.2.0-4-amd64
-r--r--r-- 0 root root 128869 Oct 22 18:57 config-3.2.0-4-amd64
-r--r--r-- 0 root root 32979968 Nov 10 18:34 initrd.img-3.2.0-4-amd64
-r--r--r-- 0 root root 2828288 Oct 22 18:54 vmlinuz-3.2.0-4-amd64
Symlinks are converted into regular files! :(.
A code in the /usr/lib/linux-boot-probes/mounted/90fallback:
...
21 if [ -f $kernfile ] [ ! -L $kernfile ]; then
...
There is a test on $kernfile and body of condition is processed only for
regular file - no symlink. And this is the problem with grub-mount.
The symlink in the root directory is not recognized and things are processed
several times.
bobek:/tmp/xxx# /usr/lib/linux-boot-probes/50mounted-tests
/dev/mapper/vg-deboot
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/boot/vmlinuz-3.2.0-4-amd64:/boot/initrd.img-3.2.0-4-amd64:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/vmlinuz:/initrd.img:root=/dev/dm-23
Disabling grub-mount in ./50mounted-tests uncovers the problem.
bobek:/tmp/xxx# ./50mounted-tests /dev/mapper/vg-deboot
/dev/mapper/vg-deboot:/dev/mapper/vg-deboot::/boot/vmlinuz-3.2.0-4-amd64:/boot/initrd.img-3.2.0-4-amd64:root=/dev/dm-23
bobek:/tmp/xxx# diff /usr/lib/linux-boot-probes/50mounted-tests 50mounted-tests
37c37
if type grub-mount /dev/null 21 \
---
if false type grub-mount /dev/null 21 \
Cheers
--
Zito
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596900: relative DDE link - workaround
Hi Eliad, I have googling relative DDE link in LibreOffice and found this bug-report and also found discussion under http://openoffice.blogs.com/openoffice/2006/06/pasting_openoff.html A workaround mentioned in discussion worked for me! Instead a simple relative path - e.g. ../foobar.ods you should write file:../foobar.ods and voila it works :). Kind Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648811: DRBD+OCFS2: general protection fault: 0000 [#1] SMP
Hi, I can confirm a bug. I tried DRBD (two primaries) with OCFS2 too. It seems I hit a very similar bug after I did a reboot renamed nodes and did mount ocfs2 by hand. Two identical nodes boot1 and boot2 guests on libvirt/KVM (different irons): Linux boot1 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux i linux-image-2.6.32-5-amd642.6.32-45 Linux 2.6.32 for 64-bit PCs Virtuals have configured ttyS0 console (both attached), so I cutpaste what was on the consoles: == boot1 == [ 9985.562785] general protection fault: [#1] SMP [ 9985.563235] last sysfs file: /sys/fs/o2cb/interface_revision [ 9985.563707] CPU 0 [ 9985.563893] Modules linked in: ocfs2 quota_tree drbd lru_cache cn nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs loop snd_pcm snd_timer snd soundcore snd_page_alloc psmouse virtio_balloon button serio_raw pcspkr processor evdev i2c_piix4 i2c_core ext4 mbcache jbd2 crc16 dm_mod ata_generic virtio_blk ata_piix uhci_hcd ehci_hcd 8139too libata floppy thermal thermal_sys virtio_pci virtio_ring virtio 8139cp mii usbcore nls_base scsi_mod [last unloaded: scsi_wait_scan] [ 9985.566703] Pid: 0, comm: swapper Not tainted 2.6.32-5-amd64 #1 Bochs [ 9985.566703] RIP: 0010:[8129eb2e] [8129eb2e] fib_get_table+0x2b/0x3a [ 9985.566703] RSP: 0018:880001803bb8 EFLAGS: 00010286 [ 9985.566703] RAX: 8801 RBX: 880001803c20 RCX: 880001803c20 [ 9985.566703] RDX: c3f000ff53f000ff RSI: 00fe RDI: 816d35b0 [ 9985.566703] RBP: 880001803cd0 R08: 816d35b0 R09: 011fa8c0 [ 9985.566703] R10: 0002 R11: R12: 88001f9d0480 [ 9985.566703] R13: R14: 880001803c20 R15: 88001f9d04f8 [ 9985.566703] FS: () GS:88000180() knlGS: [ 9985.566703] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 9985.566703] CR2: 018c9808 CR3: 1dd98000 CR4: 06f0 [ 9985.566703] DR0: DR1: DR2: [ 9985.566703] DR3: DR6: 0ff0 DR7: 0400 [ 9985.566703] Process swapper (pid: 0, threadinfo 8142e000, task 814891f0) [ 9985.566703] Stack: [ 9985.566703] 812a427e 88001f9db000 880001803cd0 [ 9985.566703] 0 8125e1b1 8800182371a8 880001803c90 0002 [ 9985.566703] 0 ffea 011fa8c0 8800181b1000 880018057800 [ 9985.566703] Call Trace: [ 9985.566703] IRQ [ 9985.566703] [812a427e] ? fib4_rule_action+0x35/0x54 [ 9985.566703] [8125e1b1] ? fib_rules_lookup+0x89/0xc3 [ 9985.566703] [812a4474] ? fib_lookup+0x2d/0x3d [ 9985.566703] [8103a311] ? enqueue_task+0x5f/0x68 [ 9985.566703] [81271d9f] ? ip_route_input+0x59e/0xcbf [ 9985.566703] [8104a45a] ? try_to_wake_up+0x289/0x29b [ 9985.566703] [8106504b] ? autoremove_wake_function+0x9/0x2e [ 9985.566703] [8103aa06] ? __wake_up_common+0x44/0x72 [ 9985.566703] [810ad4e8] ? cpupri_set+0x10c/0x135 [ 9985.566703] [81295e3e] ? arp_process+0x20f/0x60b [ 9985.566703] [a00737fb] ? cp_rx_poll+0x2d8/0x3bd [8139cp] [ 9985.566703] [8125039f] ? net_rx_action+0xae/0x1c9 [ 9985.566703] [81053d6f] ? __do_softirq+0xdd/0x1a6 [ 9985.566703] [81011cac] ? call_softirq+0x1c/0x30 [ 9985.566703] [8101322b] ? do_softirq+0x3f/0x7c [ 9985.566703] [81053bdf] ? irq_exit+0x36/0x76 [ 9985.566703] [81012922] ? do_IRQ+0xa0/0xb6 [ 9985.566703] [810114d3] ? ret_from_intr+0x0/0x11 [ 9985.566703] EOI [ 9985.566703] [8102c584] ? native_safe_halt+0x2/0x3 [ 9985.566703] [8101758d] ? default_idle+0x34/0x51 [ 9985.566703] [8100fe97] ? cpu_idle+0xa2/0xda [ 9985.566703] [8151c140] ? early_idt_handler+0x0/0x71 [ 9985.566703] [8151ccdd] ? start_kernel+0x3dc/0x3e8 [ 9985.566703] [8151c3b7] ? x86_64_start_kernel+0xf9/0x106 [ 9985.566703] Code: 85 f6 b8 fe 00 00 00 0f 44 f0 48 89 f0 83 e0 01 48 c1 e0 03 48 03 87 f0 01 00 00 48 8b 10 eb 03 48 8b 12 48 85 d2 75 03 31 c0 c3 39 72 10 48 8b 02 0f 18 08 48 89 d0 75 e7 c3 48 8b 42 10 48 85 [ 9985.566703] RIP [8129eb2e] fib_get_table+0x2b/0x3a [ 9985.566703] RSP 880001803bb8 [ 9985.594195] ---[ end trace 49c80a52371bee10 ]--- [ 9985.594581] Kernel panic - not syncing: Fatal exception in interrupt [ 9985.595102] Pid: 0, comm: swapper Tainted: G D2.6.32-5-amd64 #1 [ 9985.595650] Call Trace: [ 9985.595857] IRQ [812faf69] ? panic+0x86/0x143 [ 9985.596356] [81011673] ? apic_timer_interrupt+0x13/0x20 [ 9985.596869] [811b89f1] ? vgacon_cursor+0x0/0x140 [ 9985.597342]
Bug#679577: reset and not reboot
System is doing hard reset (in kernel panic) and not reboot of course, sorry for bad words. -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#474956: Status of this policycoreutils bug?
Hi,
On Thu, May 17, 2012 at 08:51:42PM +0300, Touko Korpela wrote:
Can you send new patch against current version if this issue is still
present? Sorry for extra work, maintainer sent latest mail only to bug
address (that isn't cc:d automatically to submitter).
sorry for a delay.
It is quite long time I wrote the code. :)
Ok, I have updated Debian Sid in the virtual machine and tried to run
se_aptitude. It still eats all the CPU thread.
The unified diff between the original version of open_init_pty.c I based
my rewrite on and the version in the current package 2.1.10-8 is:
--- open_init_pty.c.orig2008-04-07 18:17:14.0 +0200
+++ /tmp/policycoreutils-2.1.10/run_init/open_init_pty.c2012-06-25
00:11:23.0 +0200
@@ -153,7 +153,7 @@
}
if (child_pid 0) {
- perror(Fork:);
+ perror(forkpty():);
fflush(stdout);
fflush(stderr);
exit(EX_OSERR);
@@ -162,7 +162,7 @@
/* in the child */
struct termios s_tty_attr;
if (tcgetattr(fileno(stdin), s_tty_attr)) {
- perror(Child:);
+ perror(forkpty child:);
fflush(stdout);
fflush(stderr);
exit(EXIT_FAILURE);
So almost nothing changed.
First chunk is OK, because the error condition is caused during the call
to forkpty(). The second chunk is IMO not correct and my original
perror(tcgetattr(stdout,...)) seems to be more legit (error in the
tcgetattr()).
I'm attaching the open_init_pty.c with the cosmetic change of the first
error message. (BTW: no semicolon in the perror(), it is appended
always by perror()).
BTW: I already tried to post the code upstream in the past:
http://marc.info/?l=selinuxm=120826832520733w=2
... and reactions.
Thanks for your time!
Kindly regards
--
Zito
/* -*- Mode: C -*-
* open_init_pty.c ---
* Author : Manoj Srivastava ( sriva...@glaurung.internal.golden-gryphon.com )
* Created On : Fri Jan 14 10:48:28 2005
* Created On Node : glaurung.internal.golden-gryphon.com
* Last Modified By : Manoj Srivastava
* Last Modified On : Thu Sep 15 00:57:00 2005
* Last Machine Used: glaurung.internal.golden-gryphon.com
* Update Count : 92
* Status : Unknown, Use with caution!
* HISTORY :
* Description :
*
* Distributed under the terms of the GNU General Public License v2
*
* open_init_pty
*
* SYNOPSIS:
*
* This program allows a systems administrator to execute daemons
* which need to work in the initrc domain, and which need to have
* pty's as system_u:system_r:initrc_t
*
* USAGE:
*
* * arch-tag: a5583d39-72b9-4cdf-ba1b-5678ea4cbe20
*/
#include stdio.h
#include stdlib.h
#include string.h
#include unistd.h
#include signal.h
#include errno.h
#include sysexits.h
#include pty.h /* for openpty and forkpty */
#include utmp.h /* for login_tty */
#include termios.h
#include fcntl.h
#include sys/select.h
#include sys/wait.h
#define MAXRETR 3 /* The max number of IO retries on a fd */
#define BUFSIZE 2048 /* The ring buffer size */
static struct termios saved_termios;
static int saved_fd = -1;
static enum { RESET, RAW, CBREAK } tty_state = RESET;
static int tty_semi_raw(int fd)
{
struct termios buf;
if (tty_state == RESET) {
if (tcgetattr(fd, saved_termios) 0) {
return -1;
}
}
buf = saved_termios;
/*
* echo off, canonical mode off, extended input processing off,
* signal chars off
*/
buf.c_lflag = ~(ECHO | ICANON | IEXTEN | ISIG);
/*
* no SIGINT on break, CR-to-NL off, input parity check off, do not
* strip 8th bit on input,output flow control off
*/
buf.c_iflag = ~(BRKINT | ICRNL | INPCK | ISTRIP | IXON);
/* Clear size bits, parity checking off */
buf.c_cflag = ~(CSIZE | PARENB);
/* set 8 bits/char */
buf.c_cflag |= CS8;
/* Output processing off
buf.c_oflag= ~(OPOST); */
buf.c_cc[VMIN] = 1; /* one byte at a time, no timer */
buf.c_cc[VTIME] = 0;
if (tcsetattr(fd, TCSANOW, buf) 0) {
return -1;
}
tty_state = RAW;
saved_fd = fd;
return 0;
}
static void tty_atexit(void)
{
if (tty_state != CBREAK tty_state != RAW) {
return;
}
if (tcsetattr(saved_fd, TCSANOW, saved_termios) 0) {
return;
}
tty_state = RESET;
return;
}
/* The simple ring buffer */
struct ring_buffer
{
char *buf;
char *wptr;
char *rptr;
size_t size;
size_t count;
};
static void ringbuf_init(struct ring_buffer *b, char *buf, size_t size)
{
b-buf = b-wptr = b-rptr = buf;
b-size = size;
b-count = 0;
}
static int ringbuf_isempty(struct ring_buffer *b)
{
return b-count == 0;
}
static size_t ringbuf_space(struct ring_buffer *b)
{
if ( b-rptr b-wptr )
return b-rptr - b-wptr;
if ( b-rptr b-wptr || b-count == 0 )
return b-buf + b-size - b-wptr;
return 0;
}
static size_t
Bug#676155: libustr-1.0-1: please convert to multiarch
Hi, On Tue, Jun 05, 2012 at 07:39:33AM +0200, Helmut Grohne wrote: Package: libustr-1.0-1 Version: 1.0.4-2 Severity: important The libustr-1.0-1 package does currently (correctly) not have any Multi-Arch tags. It therefore prevents libsemanage1 and therefore passwd from exercising their multiarch capabilities. Since your package contains only a single shared library it seems like an easy candidate to move that library to /usr/lib/triplet and mark the package as Multi-Arch: same. The severity of this bug is set to important as this is part of a release goal. Thanks for your help. There is already prepared a version 1.0.4-3 waiting for the sponsor. The previous releases sponsored Kees Cook. I sent him an email about a week ago. I'm waiting to his response now. In the case he will not be interested to continue sponsor this package I will send an email to the mentors mailing list. I have uploaded the new package on mentors: http://mentors.debian.net/package/ustr Changes: ustr (1.0.4-3) unstable; urgency=low * Changed debian/watch, upstream ftp is no longer available * Changed Standards-Version to 3.9.3 * Support Multi-Arch for shared library * Changed debian/copyright to machine-readable format * Hardening: append CPPFLAGS to CFLAGS * Added patch fixes/man-spelling, to fix spelling errors in man-pages reported newly by the lintian * Added debian/source/format with 1.0 version number libustr-dev can't be multi-arch, because headers ustr-conf.h and ustr-conf-debug.h and ustr-import utility are architecture dependent. Hmm, I'm going to add Closes: #676155 into changelog now... Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676218: RFS: ustr/1.0.4-3 [RC] -- enable hardening flags and multiarch
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package ustr It builds those binary packages: libustr-1.0-1 - Micro string library: shared library libustr-1.0-1-dbg - Micro string library: debugging symbols libustr-dev - Micro string library: development stuff libustr-doc - Micro string library: documentation The library libustr-1.0-1 is present on every Debian system in fact, because libsemanage1 depends on it and passwd depends on libsemanage1. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/ustr Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/u/ustr/ustr_1.0.4-3.dsc Changes since the last upload: ustr (1.0.4-3) unstable; urgency=low * Changed debian/watch, upstream ftp is no longer available * Changed Standards-Version to 3.9.3 * Support Multi-Arch for shared library. Closes: #676155 * Changed debian/copyright to machine-readable format * Hardening: append CPPFLAGS to CFLAGS * Added patch fixes/man-spelling, to fix spelling errors in man-pages reported newly by the lintian * Added debian/source/format with 1.0 version number -- Vaclav Ovsik vaclav.ov...@i.cz Wed, 30 May 2012 09:48:12 +0200 Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676218: RFS: ustr/1.0.4-3 [RC] -- enable hardening flags and multiarch
On Tue, Jun 05, 2012 at 11:44:57AM -0300, David Bremner wrote: Václav Ovsík vaclav.ov...@i.cz writes: Package: sponsorship-requests Severity: important Does the RC in your subject refer to release critical? If so, what RC bug does this close? You catch me. I search on http://www.debian.org/Bugs/Developer, that RC bug is only severity serious and above. I'm going to decrease severity of RFS and retitle this bug. Sorry. Thanks -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573387: anacron leaks file descriptors
Hi Peter, On Mon, Apr 16, 2012 at 10:53:17PM +0300, Peter Eisentraut wrote: Calling lvs directly from the command line also shows messages about leaked file descriptors, so I'm not convinced that this is a problem in anacron. I don't know what you mean lvs directly from the command line. I never noticed such messages from LVM commands ran from bash, dash. The only other case I noticed is LVM under Midnight Commander. Midnight Commander has this problem too. Hmm, I should report this problem on MC too :). Also note that anacron is not a long-running process, so even if there were a resource leak of some kind, it doesn't necessarily follow that that's a problem worth fixing. Maybe you are right, but bugs should be fixed. Ok, I will try to inspect this problem a bit deeper... I ran the Anacron trough strace and after a short inspection of lvs message and strace output I found one of leaked descriptors. The following attached patch solves the message in the test case. Unfortunately I'm afraid it is only a part :(. But as I'm looking back on other leaked descriptors I originally reported, these are probably inherited from parent processes of Anacron. Can you accept the attached patch or rewrite it to your taste (maybe report upstream)? I think, that after applying the fix this bug can be closed. Other leaked descriptors should be reported to other packages. Thanks for your time and work. Best Regards -- Zito --- main.c.orig 2012-04-17 09:48:32.0 +0200 +++ main.c 2012-04-17 10:27:49.207407827 +0200 @@ -467,6 +467,7 @@ record_start_time(); read_tab(cwd); +if (close(cwd)) die_e(Can't close file descriptor %d, cwd); arrange_jobs(); if (testing_only)
Bug#667595: libraw1394-11: dvgrab fails to grab video
Hi Simon, On Thu, Apr 05, 2012 at 01:38:36AM -0700, Simon Kirby wrote: Package: libraw1394-11 Version: 2.0.8-1 Severity: important Hello! I am hitting this too, but with MythTV's firewire streaming of mpeg2. It seems to be gcc-4.6 miscompiling the library. A build of 2.0.7 or 2.0.8 with gcc-4.6 4.6.3-2 does not work, while with gcc-4.5, it does work. I have narrowed the problem to the output from fw.c, the fw_set_port() function. Wrapped in #pragma GCC optimize (-O1) and restoring -O2 again, it works. The problem seems to be at the call to ioctl(fd, FW_CDEV_IOC_GET_INFO, get_info) -- this seems to clobber filename, for some reason. I don't see what is wrong here. Thanks for investigation! I think, there are another problems - DV stream corrupted with dropouts. I thought it was dropouts originated from camera, but later grabs (with older library) was without dropouts. I think there are more problems with libraw1394-11 than device filename corruption only. You sent the reply to sub...@bugs.debian.org and so the new bug-report was opened (667595). (You should send replies to 664...@bugs.debian.org). I'm going to try join these bugs - 664562, 667595. -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637179: confirm the bug on Dell Latitude D830
Hi, I have the same issue. We have static DHCP on LAN and I have got a guest IP address now :(. The driver logs the right MAC address, but ifconfig, ip, dhclient reads a strange address: Linux bobek 3.0.0-1-amd64 #1 SMP Sun Jul 24 15:06:18 UTC 2011 x86_64 GNU/Linux [1.174608] tg3.c:v3.119 (May 18, 2011) [1.193701] tg3 :09:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [1.295029] tg3 :09:00.0: setting latency timer to 64 [1.353155] tg3 :09:00.0: eth0: Tigon3 [partno(BCM95755m) rev a002] (PCI Express) MAC address 00:1d:09:c9:cb:6d [1.353160] tg3 :09:00.0: eth0: attached PHY is 5755 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0]) [1.353163] tg3 :09:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [1.353166] tg3 :09:00.0: eth0: dma_rwctrl[7618] dma_mask[64-bit] zito@bobek:~$ sudo ethtool -P eth0 Permanent address: 00:1d:09:c9:cb:6d zito@bobek:~$ ip link show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 link/ether aa:00:04:00:0a:04 brd ff:ff:ff:ff:ff:ff zito@bobek:~$ sudo ifconfig eth0 eth0 Link encap:Ethernet HWaddr aa:00:04:00:0a:04 inet addr:192.168.65.26 Bcast:192.168.65.31 Mask:255.255.255.240 inet6 addr: fe80::a800:4ff:fe00:a04/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10515 errors:0 dropped:0 overruns:0 frame:0 TX packets:9743 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3830493 (3.6 MiB) TX bytes:1000607 (977.1 KiB) Interrupt:17 zito@bobek:~$ sudo lspci -vv -s 09:00.0 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02) Subsystem: Dell Device 01fe Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 48 Region 0: Memory at f1bf (64-bit, non-prefetchable) [size=64K] Expansion ROM at ignored [disabled] Capabilities: [48] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Product Name: Broadcom NetXtreme Gigabit Ethernet Controller Read-only fields: [PN] Part number: BCM95755m [EC] Engineering changes: 01FE.004 [SN] Serial number: 0123456789 [MN] Manufacture ID: 31 34 65 34 [RV] Reserved: checksum good, 28 byte(s) reserved Read/write fields: [YA] Asset tag: XYZ01234567 [RW] Read-write area: 107 byte(s) free End Capabilities: [58] Vendor Specific Information: Len=78 ? Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0300c Data: 41b1 Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 4096 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 4us, L1 64us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial
Bug#637179: a little stupid workaround...
to fix your address on eth0, you can do ifdown eth0 ip link set address $(ethtool -P eth0 | sed -e 's/Permanent address: //;') dev eth0 ifup eth0 maybe, this can be useful for a while for someone... Problem: I just try to boot kernel 2.6.39 and the bad address is still there :(, will continue to analyse this tomorrow. -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637179: the problem is the package dnet-common and not linux-image...
Hi, the MAC address is changed by the startup script /etc/init.d/decnet. The Ethernet lookup service gives me: AA0004 DEC Local logical address for systems running Internet Assigned Numbers Authority AA0004 DIGITAL EQUIPMENT CORPORATION IEEE Registration Authority I don't know exactly why I have the package dnet-common in my system :(, loaded by some dependency probably. Looking on reverse dependencies I found chain dnet-common - libdnet - libroar1 - libroar-compat1 - quicktime-x11utils. but quicktime-x11utils is from multimedia repository. I think the default dnet-common configuration is a bug: bobek:~# debconf-show dnet-common dnet-common/nodename: linux dnet-common/nodeaddr: 1.10 * dnet-common/configure-action: skip and leave config as it is dnet-common/warning: bobek:~# cat /etc/default/decnet # DNET_INTERFACES specifies the names of ethernet interfaces whose # MAC address is to be set to the DECnet node address DNET_INTERFACES=all # DNET_DAEMONS lists the daemons to start when dnet-progs is installed. # DNET_DAEMONS=dnetd phoned dnroute_FLAGS=-v -2 # The following two lines enable routing, note that if you are # being a router, then add dnroute to the DNET_DAEMONS too #ROUTING=1 PRIORITY=32 bobek:~# We can reassign the bug against dnet-common package. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600661: the bug confirmed
Hi, I have this problem too. This is a duplicate to bug #569775 assigned to network-manager now. I found this problem on two virtual machines installed recently. The machines were installed using the PXE and the DHCP was left the network interface configuration method. I did some changes in the /etc/ntp.conf and restarted ntpd. I was quite long confused, that I changed settings but without any effect. I noticed ntpd args in the ps output lately. This is a bit counterintuitive. In the case the modification time of /etc/ntp.conf is greater the modification time of /var/lib/ntp/ntp.conf.dhcp the later should be regenerated in the startup script. Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606376: a similar problems with the 2.6.37
Hi, I have a similar problem. Not too much load I think. Only some big rsync running (heavy NET and HDD load) and some normal work on desktop (desktop was slow)... My dist is Sid architecture i386, kernel is amd64. Linux bobek 2.6.37-2-amd64 #1 SMP Sun Feb 27 12:32:01 UTC 2011 x86_64 GNU/Linux Five times the message block: Mar 17 13:30:46 bobek kernel: [18580.109862] kworker/0:0: page allocation failure. order:0, mode:0x4020 Mar 17 13:30:46 bobek kernel: [18580.109871] Pid: 0, comm: kworker/0:0 Tainted: P2.6.37-2-amd64 #1 Mar 17 13:30:46 bobek kernel: [18580.109875] Call Trace: Mar 17 13:30:46 bobek kernel: [18580.109878] IRQ [810bb259] ? __alloc_pages_nodemask+0x6a6/0x72c Mar 17 13:30:46 bobek kernel: [18580.109897] [810e3b7d] ? alloc_pages_current+0x9f/0xc2 Mar 17 13:30:46 bobek kernel: [18580.109903] [810eb09d] ? new_slab+0x60/0x1ab Mar 17 13:30:46 bobek kernel: [18580.109909] [810eb829] ? __slab_alloc+0x274/0x335 Mar 17 13:30:46 bobek kernel: [18580.109915] [8125fc4c] ? __netdev_alloc_skb+0x15/0x2f Mar 17 13:30:46 bobek kernel: [18580.109921] [8125fc4c] ? __netdev_alloc_skb+0x15/0x2f Mar 17 13:30:46 bobek kernel: [18580.109926] [810ebcc9] ? __kmalloc_node_track_caller+0xcc/0x12a Mar 17 13:30:46 bobek kernel: [18580.109932] [8125f4c7] ? __alloc_skb+0x72/0x12e Mar 17 13:30:46 bobek kernel: [18580.109937] [8125fc4c] ? __netdev_alloc_skb+0x15/0x2f Mar 17 13:30:46 bobek kernel: [18580.109992] [a021680a] ? tg3_alloc_rx_skb+0x93/0x119 [tg3] Mar 17 13:30:46 bobek kernel: [18580.110010] [a021b718] ? tg3_poll_work+0x427/0xa94 [tg3] Mar 17 13:30:46 bobek kernel: [18580.110028] [a021beb2] ? tg3_poll+0x8f/0x1a8 [tg3] Mar 17 13:30:46 bobek kernel: [18580.110035] [8121e9d2] ? mix_pool_bytes_extract+0x59/0x154 Mar 17 13:30:46 bobek kernel: [18580.110041] [81269bdc] ? net_rx_action+0xa8/0x206 Mar 17 13:30:46 bobek kernel: [18580.110049] [8104ca5d] ? __do_softirq+0xcf/0x1b6 Mar 17 13:30:46 bobek kernel: [18580.110055] [81091507] ? handle_IRQ_event+0xf4/0x10a Mar 17 13:30:46 bobek kernel: [18580.110061] [8100a91c] ? call_softirq+0x1c/0x30 Mar 17 13:30:46 bobek kernel: [18580.110066] [8100beff] ? do_softirq+0x3f/0x79 Mar 17 13:30:46 bobek kernel: [18580.110072] [8104c8f5] ? irq_exit+0x36/0x79 Mar 17 13:30:46 bobek kernel: [18580.110077] [8100b65a] ? do_IRQ+0x9f/0xb5 Mar 17 13:30:46 bobek kernel: [18580.110084] [8131a3d3] ? ret_from_intr+0x0/0x11 Mar 17 13:30:46 bobek kernel: [18580.110087] EOI [a04a006a] ? acpi_idle_enter_simple+0xd4/0x106 [processor] Mar 17 13:30:46 bobek kernel: [18580.110114] [a04a0063] ? acpi_idle_enter_simple+0xcd/0x106 [processor] Mar 17 13:30:46 bobek kernel: [18580.110121] [8124fd66] ? cpuidle_idle_call+0xa2/0x108 Mar 17 13:30:46 bobek kernel: [18580.110127] [81008bcb] ? cpu_idle+0xb2/0x124 Mar 17 13:30:46 bobek kernel: [18580.110132] [813132bc] ? start_secondary+0x1e5/0x1eb Mar 17 13:30:46 bobek kernel: [18580.110136] Mem-Info: Mar 17 13:30:46 bobek kernel: [18580.110139] Node 0 DMA per-cpu: Mar 17 13:30:46 bobek kernel: [18580.110143] CPU0: hi:0, btch: 1 usd: 0 Mar 17 13:30:46 bobek kernel: [18580.110148] CPU1: hi:0, btch: 1 usd: 0 Mar 17 13:30:46 bobek kernel: [18580.110150] Node 0 DMA32 per-cpu: Mar 17 13:30:46 bobek kernel: [18580.110155] CPU0: hi: 186, btch: 31 usd: 41 Mar 17 13:30:46 bobek kernel: [18580.110159] CPU1: hi: 186, btch: 31 usd: 51 Mar 17 13:30:46 bobek kernel: [18580.110169] active_anon:101261 inactive_anon:37651 isolated_anon:1 Mar 17 13:30:46 bobek kernel: [18580.110171] active_file:66626 inactive_file:263690 isolated_file:67 Mar 17 13:30:46 bobek kernel: [18580.110173] unevictable:932 dirty:179311 writeback:10721 unstable:0 Mar 17 13:30:46 bobek kernel: [18580.110174] free:2538 slab_reclaimable:24948 slab_unreclaimable:7017 Mar 17 13:30:46 bobek kernel: [18580.110176] mapped:12595 shmem:884 pagetables:1116 bounce:0 Mar 17 13:30:46 bobek kernel: [18580.110181] Node 0 DMA free:8032kB min:40kB low:48kB high:60kB active_anon:404kB inactive_anon:656kB active_file:180kB inactive_file:5236kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15684kB mlocked:0kB dirty:4932kB writeback:304kB mapped:0kB shmem:0kB slab_reclaimable:260kB slab_unreclaimable:1076kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Mar 17 13:30:46 bobek kernel: [18580.110200] lowmem_reserve[]: 0 2002 2002 2002 Mar 17 13:30:46 bobek kernel: [18580.110207] Node 0 DMA32 free:2120kB min:5704kB low:7128kB high:8556kB active_anon:404640kB inactive_anon:149948kB active_file:266324kB inactive_file:1049524kB unevictable:3728kB isolated(anon):4kB isolated(file):268kB present:2050652kB mlocked:3728kB
Bug#612829: temporary workaround
Hi, I did a workaround logcheck rule file for myself: bobek:~# cat /etc/logcheck/ignore.d.server/emptyline-workaround ^$ I hope it can help. Cheers -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607616: libgnutls26: the GnuTLS searches CA certs by subject and stops on first? (fails on more CA with the same subj)
Hello, On Tue, Jan 25, 2011 at 10:57:37PM +0100, Nikos Mavrogiannopoulos wrote: On 01/20/2011 05:58 PM, Václav Ovsík wrote: On Thu, Jan 20, 2011 at 05:22:12PM +0100, Nikos Mavrogiannopoulos wrote: Hello, Indeed I'm mistaken. The reported problem is about order of certificates with the same subject DN in the repository during verifying certificate. I have server certificates issued by older and newer CA certificate both valid of course. GnuTLS must find the right certificate of CA from two or even more with the same subject DN. I tried to examine in the bug-report, that based on the order of two CA certificates with the same subject DN IN THE REPOSITORY the GnuTLS fails on newer or older server certificate. There was no change on server sides or so. I changed CA cert order only on the client side repository. Yes gnutls does stop on first match no matter if expired of not... Is there merit in supporting lists that contain duplicates of certificates? Changing subject DN on certificate renewals is maybe good practice, but AFAIK not required. Administrators of our company CA (Microsoft CA) simply did not change it. Their choice, OK. No don't take my point as being that changing the DN is recommended. I am not suggesting that. What I suggest is that the old certificate can be removed from the list once the renewed one is added. I mention this, because it could work-around the problem and I met this recommendation it the past (for example to append the year to CA subject DN). Renewed certificate of CA can't be removed immediately of course. A new CA certificate must be issued at least in the End_Of_Life(CA) - The_Longest_Life_Duration_CA_issued_Cert. For example you have CA with Not After 2012-01-01 and you are issuing certs with one year validity - the date you can issue the last cert with this CA is 2011-01-01. This CA must issue CRL till its end in 2012-01-01. You need a new CA for certs after 2011-01-01. You have two CA certs valid between 2011-01-01 - 2012-01-01 both must issue CRL, only newer is issuing certs. I solved my problem with LDAPS servers simply by pointing only to Root CA (not whole CA bundle). The LDAPS server gives the certificate chain with the right intermediate CA, so things works now on every server :). OpenSSL handles this smoothly and I think it is bug otherwise. When OpenSSL's c_rehash is called on directory of X.509 certificates, it numbers hashes with aabbccdd.n, where n is for resolution of the same Subjects. So when I look into my repository: I note it as an issue to the gnutls verification functionality, and I'll fix it together with some other issues, by adding a more advanced verification subsystem. Great! I think it will be worth either in my special case exists a work-around. Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607616: libgnutls26: the GnuTLS searches CA certs by subject and stops on first? (fails on more CA with the same subj)
Hi Nikos, On Mon, Dec 20, 2010 at 05:03:28PM +0100, Nikos Mavrogiannopoulos wrote: You cannot reorder certificates on will. For TLS/SSL the certificates have to be ordered (from RFC5246): This is a sequence (chain) of certificates. The sender's certificate MUST come first in the list. Each following certificate MUST directly certify the one preceding it. I'm not sure correctly understood, but I think your reply is not relevant to a problem I reported. The above citation is about order of certificates in the chain sent in the TLS protocol by server right? The reported problem is about order of certificates with the same subject DN in the repository during verifying certificate. I have server certificates issued by older and newer CA certificate both valid of course. GnuTLS must find the right certificate of CA from two or even more with the same subject DN. I tried to examine in the bug-report, that based on the order of two CA certificates with the same subject DN IN THE REPOSITORY the GnuTLS fails on newer or older server certificate. There was no change on server sides or so. I changed CA cert order only on the client side repository. Thanks for your time. Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607616: libgnutls26: the GnuTLS searches CA certs by subject and stops on first? (fails on more CA with the same subj)
On Thu, Jan 20, 2011 at 05:22:12PM +0100, Nikos Mavrogiannopoulos wrote: Hello, Indeed I'm mistaken. The reported problem is about order of certificates with the same subject DN in the repository during verifying certificate. I have server certificates issued by older and newer CA certificate both valid of course. GnuTLS must find the right certificate of CA from two or even more with the same subject DN. I tried to examine in the bug-report, that based on the order of two CA certificates with the same subject DN IN THE REPOSITORY the GnuTLS fails on newer or older server certificate. There was no change on server sides or so. I changed CA cert order only on the client side repository. Yes gnutls does stop on first match no matter if expired of not... Is there merit in supporting lists that contain duplicates of certificates? Changing subject DN on certificate renewals is maybe good practice, but AFAIK not required. Administrators of our company CA (Microsoft CA) simply did not change it. Their choice, OK. OpenSSL handles this smoothly and I think it is bug otherwise. When OpenSSL's c_rehash is called on directory of X.509 certificates, it numbers hashes with aabbccdd.n, where n is for resolution of the same Subjects. So when I look into my repository: zito@bobek:~$ ls -la /etc/ssl/certs|grep ICZ lrwxrwxrwx 1 root root18 Jan 19 08:56 0e87c968.0 - ICZ-Issuing-CA.pem lrwxrwxrwx 1 root root20 Jan 19 08:56 0e87c968.1 - ICZ-Issuing-CA-1.pem lrwxrwxrwx 1 root root53 Jan 19 08:52 ICZ-Issuing-CA-1.pem - /usr/local/share/ca-certificates/ICZ-Issuing-CA-1.crt lrwxrwxrwx 1 root root51 Jan 19 08:52 ICZ-Issuing-CA.pem - /usr/local/share/ca-certificates/ICZ-Issuing-CA.crt lrwxrwxrwx 1 root root48 Jan 19 08:52 ICZ-Root-CA.pem - /usr/local/share/ca-certificates/ICZ-Root-CA.crt lrwxrwxrwx 1 root root15 Jan 19 08:56 d0d1f6f2.0 - ICZ-Root-CA.pem Certificates ICZ-Issuing-CA.pem and ICZ-Issuing-CA-1.pem (more recent) have the same hash, so symlinks 0e87c968.0 0e87c968.1 exists. I don't look into OpenSSLs internals how it implements this in its X509_STORE structures... The concurrence of two CA certs will remain until older and everything it issued will expire. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604956: linux-image-2.6.36-trunk-amd64 2.6.36-1~experimental.1 is also affected
Hi, I installed linux-image-2.6.36-trunk-amd64 version 2.6.36-1~experimental.1 from experimental and the problem is there too. Dec 10 10:55:16 bobek kernel: [ 1756.474167] kvm[16483]: segfault at ff8c ip f720c047 sp f684618c error 6 in libc-2.11.2.so[f7148000+14] I'm running unstable on desktop. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563706: the bug #585352 appeared in #563706 already
Hi, the bug #585352 appeared in #563706. A primary problem is visible from shell output of /usr/lib/rootstrap/modules/uml fortunately. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563706: the rootstrap bug
Hi, I have just discovered this problem too. The bug should be reassigned to the rootstrap package. The rootstrap module /usr/lib/rootstrap/modules/uml creates static dev entries using MAKEDEV (package makedev), witch is from Squeeze up no longer priority required but only extra! Simple workaround is to add the package makedev by hand in /etc/rootstrap/rootstrap.conf ... [debian] ... include=makedev ... Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588184: confirm bug on Sid/i386
Hi, this bug can be merged with #534314. I can confirm behaviour described by martin f. krafft. The bug is probably in the binary /usr/lib/openoffice/program/soffice.bin witch is called when -no-oosplash option is used. I have amd64 kernel, but binary architecture i386. z...@bobek:~$ /usr/lib/openoffice/program/soffice.bin terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' while z...@bobek:~$ /usr/lib/openoffice/program/oosplash.bin z...@bobek:~$ executes normaly. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600026: etckeeper: composed author email with hostname with duplicit dnsdomain part
On Wed, Oct 13, 2010 at 11:37:47AM -0400, Joey Hess wrote: Vaclav Ovsik wrote: Hi, some servers can have DNS domain (or its part) in hostname. I have this on servers despite it is not recommended to distinguish servers with the same name, but different domain name in prompt (PS1 redefined with \H). Instead of composing hostname the FQDN can be retrieved from hostname command: diff --git a/etckeeper/commit.d/50vcs-commit b/etckeeper/commit.d/50vcs-commit index 959babb..340f32b 100755 --- a/etckeeper/commit.d/50vcs-commit +++ b/etckeeper/commit.d/50vcs-commit @@ -21,11 +21,7 @@ else logfile= fi -hostname=`hostname` -dnsdomainname=`dnsdomainname 2/dev/null || true` -if [ -n $dnsdomainname ]; then - hostname=$hostname.$dnsdomainname -fi +hostname=`hostname -f` That's what I used to have, but hostname -f does something horrible on Solaris. Then diff --git a/etckeeper/commit.d/50vcs-commit b/etckeeper/commit.d/50vcs-commit index 959babb..c52da87 100755 --- a/etckeeper/commit.d/50vcs-commit +++ b/etckeeper/commit.d/50vcs-commit @@ -21,7 +21,7 @@ else logfile= fi -hostname=`hostname` +hostname=`hostname|sed 's/\..*//;'` dnsdomainname=`dnsdomainname 2/dev/null || true` if [ -n $dnsdomainname ]; then hostname=$hostname.$dnsdomainname will probably work everywhere. Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596493: sudo -i patch from Fedora
Hi,
the Fedora project solved the problem with HOME and sudo -i by the patch
attached (from package sudo-1.7.4p4-2.fc13.src.rpm), as I notice by
colleague.
Regards
--
Zito
--- env.c Wed Aug 18 15:27:03 2010
+++ env.c Tue Sep 14 11:41:50 2010
@@ -608,10 +608,16 @@
#ifdef ENV_DEBUG
memset(env.envp, 0, env.env_size * sizeof(char *));
#endif
-if (def_env_reset || ISSET(sudo_mode, MODE_LOGIN_SHELL)) {
- /* Reset HOME based on target user unless keeping old value. */
- reset_home = TRUE;
+/* Reset HOME based on target user if configured to. */
+if (ISSET(sudo_mode, MODE_RUN)) {
+ if (def_always_set_home ||
+ ISSET(sudo_mode, MODE_RESET_HOME | MODE_LOGIN_SHELL) ||
+ (ISSET(sudo_mode, MODE_SHELL) def_set_home))
+ reset_home = TRUE;
+}
+
+if (def_env_reset || ISSET(sudo_mode, MODE_LOGIN_SHELL)) {
/* Pull in vars we want to keep from the old environment. */
for (ep = old_envp; *ep; ep++) {
int keepit;
@@ -696,6 +702,11 @@
if (!ISSET(didvar, DID_USERNAME))
sudo_setenv(USERNAME, user_name, FALSE);
}
+
+ /* If we didn't keep HOME, reset it based on target user. */
+ if (!ISSET(didvar, KEPT_HOME))
+ reset_home = TRUE;
+
/*
* Set MAIL to target user in -i mode or if MAIL is not preserved
* from user's environment.
@@ -709,13 +720,6 @@
sudo_putenv(cp, ISSET(didvar, DID_MAIL), TRUE);
}
} else {
- /* Reset HOME based on target user if configured to. */
- if (ISSET(sudo_mode, MODE_RUN)) {
- if (def_always_set_home || ISSET(sudo_mode, MODE_RESET_HOME) ||
- (ISSET(sudo_mode, MODE_SHELL) def_set_home))
- reset_home = TRUE;
- }
-
/*
* Copy environ entries as long as they don't match env_delete or
* env_check.
@@ -765,7 +769,7 @@
}
/* Set $HOME to target user if not preserving user's value. */
-if (reset_home !ISSET(didvar, KEPT_HOME))
+if (reset_home)
sudo_setenv(HOME, runas_pw-pw_dir, TRUE);
/* Provide default values for $TERM and $PATH if they are not set. */
Bug#596493: sudo -i upstream bugreport
The patch I sent in previous message seems to be the same from upstream bugreport: http://www.sudo.ws/bugs/show_bug.cgi?id=440 Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508604: init script suspend/shutdown from upstream
Hi, I just took tools/libvirt-guests.init.in tools/libvirt-guests.sysconf and modify init script a little (remove bashisms) and put it on a server. It is not final shape probably, but maybe it can be useful as starting point... Best Regards -- Zito libvirt-bin-guests.tar.bz2 Description: Binary data
Bug#596847: problem with reseting HOME and sudo -i
Hi, there is also problem with the reseting HOME interactive sudo mode. The old behaviour was, that HOME was kept in common use e.g. sudo xlogo so $HOME/.Xauthority was accessible for xlogo. And HOME was reset in the case of interactive sudo sudo -i and HOME is /root in that case. That is according to sudo man page describing env HOME, options -H -s... When HOME is appended into env_keep, then HOME is kept even in interactive mode, so sudo -i is non functional! Best Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584996: FYI: a solution from awesome-de...@naquadah.org
Hi, I just try to find something about a placement problem (widgets wlan, cpu) and found a reply from awesome-de...@naquadah.org... http://www.mail-archive.com/awesome-de...@naquadah.org/msg05175.html You should simply place obvious.wlan().widget instead of obvious.wlan() into Wibox. That works for me. Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573953: Info received (a segfault on ImageMagicks display rendering)
Oh, reportbug didn't insert awesome version... awesome3.4.5-1 -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481068: the problem still exists
Hi, On Mon, Mar 15, 2010 at 04:40:37PM -0700, Chris Taylor wrote: close 481068 thanks It works for me, and after nearly 2 weeks without a response from the Sorry, I didn't receive the previous update. BTS is not sending to submitter by itself AFAIK and I was not subscribed to bug explicitly... bug submitter I am going to close this bug. If this is in error feel free to re-open it and provide more information. OK. I try reproduce the problem without confusing ssh call this time: On the Etch: z...@nagios:~$ socat -V|head -2 socat by Gerhard Rieger - see www.dest-unreach.org socat version 1.4.3.1 on Apr 13 2006 15:56:26 z...@nagios:~$ socat SYSTEM:'printf %b 1\n2\n3\n' STDOUT 1 2 3 z...@nagios:~$ On the Sid: z...@bobek:~$ socat -V|head -2 socat by Gerhard Rieger - see www.dest-unreach.org socat version 1.7.1.2 on Feb 11 2010 19:13:27 z...@bobek:~$ socat SYSTEM:'printf %b 1\n2\n3\n' STDOUT 1sh: line 1: 2: command not found sh: line 2: 3: command not found z...@bobek:~$ I think the problem still exists... Regards -- Zito -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538248: [r...@bobek.localdomain: Anacron job 'cron.daily' on bobek]
Hi,
I wrote a script draft yesterday, that should collect some information for
further backups.
z...@bobek:/etc/cron.daily$ cat sysinfo-local
#!/bin/sh
DSTDIR=/var/backups/sysinfo
mkdir -p $DSTDIR
cd $DSTDIR
mount mount.out
blockdev --report blockdev-report.out
sfdisk -l sfdisk-l.out 21
for d in /dev/hd? /dev/sd?
do
sfdisk -d $d sfdisk-d.${d##/dev/}.out 21
done
pvs lvm-pvs.out
vgs lvm-vgs.out
lvs lvm-lvs.out
dmidecode dmidecode.out
lspci lspci.out
dpkg --get-selections dpkg-get-selections.out
Cron output (the script run by anacron after resume from suspend) is
attached. I tried to google strange messages and found this bug-report.
This bug-report should be reassigned somewhere?
Regards
--
Zito
---BeginMessage---
/etc/cron.daily/sysinfo-local:
File descriptor 3 (/var/run/pm-utils/locks/pm-suspend.lock (deleted)) leaked on
pvs invocation. Parent PID 20848: /bin/sh
File descriptor 4 (/dev/input/event12) leaked on pvs invocation. Parent PID
20848: /bin/sh
File descriptor 5 (/dev/input/event2) leaked on pvs invocation. Parent PID
20848: /bin/sh
File descriptor 6 (/dev/input/event3) leaked on pvs invocation. Parent PID
20848: /bin/sh
File descriptor 7 (/dev/input/event4) leaked on pvs invocation. Parent PID
20848: /bin/sh
File descriptor 8 (/dev/input/event5) leaked on pvs invocation. Parent PID
20848: /bin/sh
File descriptor 9 (inotify) leaked on pvs invocation. Parent PID 20848: /bin/sh
File descriptor 10 (socket:[10191]) leaked on pvs invocation. Parent PID 20848:
/bin/sh
File descriptor 11 (/) leaked on pvs invocation. Parent PID 20848: /bin/sh
File descriptor 3 (/var/run/pm-utils/locks/pm-suspend.lock (deleted)) leaked on
vgs invocation. Parent PID 20848: /bin/sh
File descriptor 4 (/dev/input/event12) leaked on vgs invocation. Parent PID
20848: /bin/sh
File descriptor 5 (/dev/input/event2) leaked on vgs invocation. Parent PID
20848: /bin/sh
File descriptor 6 (/dev/input/event3) leaked on vgs invocation. Parent PID
20848: /bin/sh
File descriptor 7 (/dev/input/event4) leaked on vgs invocation. Parent PID
20848: /bin/sh
File descriptor 8 (/dev/input/event5) leaked on vgs invocation. Parent PID
20848: /bin/sh
File descriptor 9 (inotify) leaked on vgs invocation. Parent PID 20848: /bin/sh
File descriptor 10 (socket:[10191]) leaked on vgs invocation. Parent PID 20848:
/bin/sh
File descriptor 11 (/) leaked on vgs invocation. Parent PID 20848: /bin/sh
File descriptor 3 (/var/run/pm-utils/locks/pm-suspend.lock (deleted)) leaked on
lvs invocation. Parent PID 20848: /bin/sh
File descriptor 4 (/dev/input/event12) leaked on lvs invocation. Parent PID
20848: /bin/sh
File descriptor 5 (/dev/input/event2) leaked on lvs invocation. Parent PID
20848: /bin/sh
File descriptor 6 (/dev/input/event3) leaked on lvs invocation. Parent PID
20848: /bin/sh
File descriptor 7 (/dev/input/event4) leaked on lvs invocation. Parent PID
20848: /bin/sh
File descriptor 8 (/dev/input/event5) leaked on lvs invocation. Parent PID
20848: /bin/sh
File descriptor 9 (inotify) leaked on lvs invocation. Parent PID 20848: /bin/sh
File descriptor 10 (socket:[10191]) leaked on lvs invocation. Parent PID 20848:
/bin/sh
File descriptor 11 (/) leaked on lvs invocation. Parent PID 20848: /bin/sh
---End Message---
