Bug#887008: rebuild
Same happened to me, but I noticed the guest modules had not been built. Did you try rebuilding them from source (virtualbox-guest-source)? Oskar
Bug#782691: varnishncsa sometimes does not start after reboot
Package: varnish Version: 4.0.2-1 Severity: normal varnishncsa sometimes does not start after reboot. I suspect varnishncsa fails because it cannot contact varnish, which has not started completely yet. Regards, Oskar Liljeblad -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16.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 Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762633: openssh-server: -N option does behave on slave sessions (runs shell when it shouldn't)
Package: openssh-server Version: 1:6.6p1-7 Severity: normal Hello The -N option is documented as 'Do not execute a remote command'. This works fine but when you run it on an existing master connection (i.e. as slave), it will actually execute a shell. To reproduce: ssh -F /dev/null -o ControlMaster=auto -o ControlPath=socket -f -N localhost ssh -F /dev/null -o ControlMaster=auto -o ControlPath=socket -N localhost The first command works as expected, but the second will launch a shell without prompt in the foreground (try 'ls /' to verify). The same issue occurs if you run '-f -N' both times (i.e. first command above twice) - it start a shell and you will see output from the shell such as uname -a before ssh goes into background. The -N command should not execute a shell. If the master connection exists already, it should instead behave as '-O forward' (request forwardings without command execution) which works correctly. Regards, Oskar Liljeblad -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-server depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii dpkg 1.17.13 ii init-system-helpers1.21 ii libc6 2.19-11 ii libcomerr2 1.42.12-1 ii libgssapi-krb5-2 1.12.1+dfsg-9 ii libkrb5-3 1.12.1+dfsg-9 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux12.3-2 ii libssl1.0.01.0.1i-2 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13 ii openssh-client 1:6.6p1-7 ii openssh-sftp-server1:6.6p1-7 ii procps 1:3.3.9-7 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages openssh-server recommends: ii ncurses-term 5.9+20140712-2 ii xauth 1:1.0.9-1 Versions of packages openssh-server suggests: pn molly-guard none pn monkeysphere none pn rssh none pn ssh-askpass none pn ufw none -- Configuration Files: /etc/pam.d/sshd 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#762428: squid-deb-proxy: does not start with unrecognized: 'netdb_filename' error
Source: squid-deb-proxy Version: 0.8.9 Severity: important After upgrading to 0.8.9 my squid-deb-proxy no longer starts: # /etc/init.d/squid-deb-proxy start Starting Squid Deb HTTP Proxy: squid-deb-proxy2014/09/22 07:11:36| cache_cf.cc(381) parseOneConfigFile: squid-deb-proxy.conf:96 unrecognized: 'netdb_filename' failed! Squid is squid3 3.1.20-2.2+deb7u2. Regards, Oskar -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760715: yubiserver: debsums reports /var/lib/yubiserver/yubiserver.sqlite changed
Package: yubiserver Version: 0.4-4 Severity: normal Hi! debsums reports that /var/lib/yubiserver/yubiserver.sqlite has changed. I don't know how to solve this, but #638726 is similar. Regards, Oskar -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yubiserver depends on: ii adduser 3.113+nmu3 ii libc6 2.19-10 ii libev41:4.15-3 ii libgcrypt11 1.5.4-2 ii libmhash2 0.9.9.9-7 ii libsqlite3-0 3.8.6-1 yubiserver recommends no packages. yubiserver 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#756479: nagios-nrpe-server: --enable-command-args
C'mon. Did you actually think nobody would complain about this? For us, nagios-nrpe-server is unusable without --enable-command-args. You haven't made nagios-nrpe-server more secure, you've just limited the options of the users. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742896: same issue
Hello, FYI, I have the same issue with my Zotac Nvidia Ion system (NVIDIA Corporation ION VGA (rev b1), pci 10de:087d). Installing the 13.0+dfsg1+internal+ffmpeg-1~bpo70~wheezyffmpeg+1 version from http://people.debian.org/~rbalint/ppa/xbmc-ffmpeg/ solved the issue for me. Also of note is that when vdpau-va-driver (0.7.3-2) is installed, XBMC crashes (both the version mentioned above and the one in wheezy-backports, 2:13.1~rc1+dfsg1-1~bpo70+1. Let me know if there is any debugging information I can provide or if there is there is additional testing to be done. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746447: libssl1.0.0: haproxy should be restarted for heartbleed bug
Package: libssl1.0.0 Version: 1.0.1g-3 Severity: minor HAProxy depends on libssl1.0.0 and needs to be restarted after libssl1.0.0 upgrade in order to fix the Heartbleed issue. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746447: Acknowledgement (libssl1.0.0: haproxy should be restarted for heartbleed bug)
I forgot to mention that the package is called haproxy and the init script is /etc/init.d/haproxy. Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744938: nmap: manual page missing text
Package: nmap Version: 6.40-0.2 Severity: minor In the PORT SCANNING BASICS The six port states recognized by Nmap section of the Nmap manual page, the actual state names are missing. This is what it says: An application is actively accepting TCP connections, UDP datagrams or SCTP associations on this port. Finding these is often the primary goal of port scanning. Security-minded people know that each open port is an avenue for attack. Attackers and pen-testers want to exploit the open ports, while administrators try to close or protect them with firewalls without thwarting legitimate users. Open ports are also interesting for non-security scans because they show services available for use on the network. A closed port is accessible (it receives and responds to Nmap probe packets), but there is no application listening on it. They can be helpful in showing that a host is up on an IP address (host discovery, or ping scanning), and as part of OS detection. Because closed ports are reachable, it may be worth scanning later in case some open up. Administrators may want to consider blocking such ports with a firewall. Then they would appear in the filtered state, discussed next. [..] But if you check http://nmap.org/book/man-port-scanning-basics.html, you'll see that it says: open An application is actively accepting TCP connections, UDP datagrams or SCTP associations on this port. Finding these is often the primary goal of port scanning. Security-minded people know that each open port is an avenue for attack. Attackers and pen-testers want to exploit the open ports, while administrators try to close or protect them with firewalls without thwarting legitimate users. Open ports are also interesting for non-security scans because they show services available for use on the network. closed A closed port is accessible (it receives and responds to Nmap probe packets), but there is no application listening on it. They can be helpful in showing that a host is up on an IP address (host discovery, or ping scanning), and as part of OS detection. Because closed ports are reachable, it may be worth scanning later in case some open up. Administrators may want to consider blocking such ports with a firewall. Then they would appear in the filtered state, discussed next. [..] Regards, Oskar -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nmap depends on: ii libc62.18-4 ii libgcc1 1:4.8.2-16 ii liblinear1 1.8+dfsg-1 ii liblua5.2-0 5.2.3-1 ii libpcap0.8 1.5.3-2 ii libpcre3 1:8.31-2 ii libssl1.0.0 1.0.1g-2 ii libstdc++6 4.8.2-16 pn python:any none nmap recommends no packages. nmap 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#740574: same here
I had the same issue, and I was able to fix it with Vincent's suggestion to downgrade libtirpc1. Also, don't forget to restart rpcbind after downgrading the package. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737188: logrotate: doesn't report permission errors unless run with -v
On Friday, January 31, 2014 at 08:24, Paul Martin wrote:
If you have a file in /etc/logrotate.d/ with incorrect permissions
according to logrotate (e.g. root root 0664) then logrotate will
silently ignore the file unless run with -v. That means that errors
are not reported to administrators at all.
Also I'm not sure why permissions of /etc/logrotate.d/ files are
important at all.
Can you give an example? Can you try with 3.8.7-1 (in testing)?
It seems to occur in 3.8.7-1 as well. The check is in config.c:
if ((sb.st_mode 07533) != 0400) {
message(MESS_DEBUG,
Ignoring %s because of bad file mode.\n,
configFile);
close(fd);
return 0;
}
Ok, I understand that you can place commands in /etc/logrotate.d files and
this is why the above check is done. But I'm not entirely sure the above
message should be MESS_DEBUG, maybe it should be MESS_NORMAL instead so that
the issue is reported to the administrator during log rotation.
Anyway, I think the priority of this bug is more like 'wishlist' now... :)
Regards,
Oskar
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737775: awstats: please make the update script log somewhere
Package: awstats Version: 7.2+dfsg-1 Severity: wishlist Troubleshooting awstats is very hard without modifying the update.sh script, because it only reports errors if awstats.pl actually fail. It would be nice if the update script could (optionally) log to /var/log/awstats.log or some such file. Regards, Oskar -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awstats depends on: ii perl 5.18.2-2 Versions of packages awstats recommends: ii coreutils 8.21-1 pn libnet-xwhois-perl none Versions of packages awstats suggests: ii apache2 2.4.7-1 ii apache2-bin [httpd] 2.4.7-1 ii apache2-mpm-prefork [httpd] 2.4.7-1 pn libgeo-ipfree-perl none ii libnet-dns-perl 0.68-1.2 ii libnet-ip-perl 1.26-1 ii liburi-perl 1.60-1 -- Configuration Files: /etc/cron.d/awstats changed [not included] -- 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#737188: logrotate: doesn't report permission errors unless run with -v
Package: logrotate Version: 3.8.1-4 Severity: normal If you have a file in /etc/logrotate.d/ with incorrect permissions according to logrotate (e.g. root root 0664) then logrotate will silently ignore the file unless run with -v. That means that errors are not reported to administrators at all. Also I'm not sure why permissions of /etc/logrotate.d/ files are important at all. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735534: ifupdown: support preferred-lifetime for v4tunnel
Package: ifupdown Version: 0.7.47.1 Severity: wishlist Please support preferred-lifetime for inet6 v4tunnel as well. Currently it is supported for inet6 static. Thanks Oskar -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-45 ii iproute2 3.12.0-1 ii libc62.17-97 ii lsb-base 4.1+Debian12 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.2.4-7 Versions of packages ifupdown suggests: ii net-tools 1.60-25 ii ppp2.4.5+git20130610-3 ii rdnssd 1.0.1-1+b1 -- 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#735203: dropbear does not exit properly in initrd
Package: dropbear Version: 2012.55-1.4 Severity: normal Hi I use dropbear to allow remote unlocking of an encrypted root filesystem. My /etc/default/dropbear contains NO_START=1 so I expect it to shut down so that OpenSSH can start instead after initrd. That also works as expected if I boot the system and enter the encryption key at the console. But if I enter the encryption key using ssh via dropbear (i.e. by sshing into the box and running 'echo -ne key /lib/cryptsetup/passfifo'), dropbear is not stopped. It remains running and prevents OpenSSH from starting. It turns out that this was because the last command in /usr/share/initramfs-tools/scripts/init-bottom/dropbear, kill `cat /var/run/dropbear.pid` kills one dropbear process, but leaves another one (with a higher pid). So my crude solution was to add the following to the same file: killall dropbear Regards, Oskar Liljeblad (os...@osk.mine.nu) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735203: master?
I guess this could be because I have configured my ssh client to always create master connections. So perhaps dropbear keeps a process running as long as the client has a master socket. For some reason this prevents OpenSSH from listening on port 22. Also, you can't stop dropbear using '/etc/init.d/dropbear stop', because the pid file no longer exists in /var/run. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723074: wordpress: wp-setup does not handle themes/plugins with spaces
Package: wordpress
Version: 3.6.1+dfsg-1~deb7u1
Severity: normal
I had a warning/failure during upgrade because of a plugin in
/var/lib/wordpress/wp-content/plugins that had space in its directory
name. It turns out to be due to improper quoting in /usr/bin/wp-setup.
Regards,
Oskar Liljeblad
--- wp-setup2013-09-13 21:10:57.0 +
+++ /usr/bin/wp-setup 2013-09-16 06:32:07.186859142 +
@@ -44,10 +44,10 @@
is_symlink_to_standard_directory() {
local symlink=$1
-if [ ! -h $symlink ]; then
+if [ ! -h $symlink ]; then
return 1
fi
-target=$(readlink $symlink)
+target=$(readlink $symlink)
if [ $target = ${target##$WP_CONTENT_ORIG_DIR} ]; then
return 1
fi
@@ -56,8 +56,8 @@
remove_symlink() {
local symlink=$1
-echo -n $(basename $symlink)
-rm -f $symlink
+echo -n $(basename $symlink)
+rm -f $symlink
}
sync_wp_content() {
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719859: icinga-web-pnp: pnp4nagios Graph/Detail buttons missing from Unhandled Host/Service Problems view
Package: icinga-web-pnp Version: 1.9.0+dfsg1-3 Severity: wishlist The PNP4Nagios extension buttons Graph and Detail for individual hosts and services are missing from the Unhandled Host/Service Problems view in Icinga-Web. They can easily be added like this: cd /usr/share/icinga-web/app/modules/Cronks/data/xml/extensions/ sed -r pnp-host-extension.xml pnp-unhandled-host-problem-extension.xml s/icinga-host-template/icinga-unhandled-host-problems/ sed -r pnp-service-extension.xml pnp-unhandled-service-problem-extension.xml s/icinga-service-template/icinga-unhandled-service-problems/ It would be extremly nice if they were included in the icinga-web-pnp package! Thanks in advance! Regards, Oskra Liljeblad (os...@osk.mine.nu) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719206: libberkeleydb-perl: please include md5sums for debsums
Package: libberkeleydb-perl Version: 0.51-1 Severity: normal Please run dh_md5sums to include checksums for debsums. Regards, Oskar Liljeblad (os...@osk.mine.nu) diff -u debian/rules.v0 debian/rules --- debian/rules.v0 2013-08-09 11:12:20.939468421 +0200 +++ debian/rules2013-08-09 11:12:27.719549213 +0200 @@ -64,6 +64,7 @@ dh_perl dh_shlibdeps dh_gencontrol + dh_md5sums dh_builddeb binary-indep: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719208: mediawiki: md5sums for Renameuser{.alias, .i18n, _body}.php files are incorrect
Package: mediawiki Version: 1:1.19.5-1 Severity: normal debsums reports that the following files have incorrect checksums: /var/lib/mediawiki/extensions/Renameuser/Renameuser.alias.php /var/lib/mediawiki/extensions/Renameuser/Renameuser.i18n.php /var/lib/mediawiki/extensions/Renameuser/Renameuser_body.php If I do 'apt-get install --reinstall mediawiki', then it will complain that the following files are incorrect: /usr/share/mediawiki-extensions/base/Renameuser/Renameuser.alias.php /usr/share/mediawiki-extensions/base/Renameuser/Renameuser.i18n.php /usr/share/mediawiki-extensions/base/Renameuser/Renameuser_body.php And if I do 'apt-get install --reinstall mediawiki-extensions-base', then it will complain about the /var/lib/mediawiki files... Is there any way to fix this? Regards, Oskar Liljeblad (os...@osk.mine.nu) -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719208: [Pkg-mediawiki-devel] Bug#719208: mediawiki: md5sums for Renameuser{.alias, .i18n, _body}.php files are incorrect
On Friday, August 09, 2013 at 12:12, Thorsten Glaser wrote: [..] Some cleanup is also needed… can you please share the output of $ ls -lad /var/lib/mediawiki/extensions/Renameuser on the affected system? If I’m right it’s a symbolic link somewhere. Yep, that's right! lrwxrwxrwx 1 root root 47 May 9 2012 /var/lib/mediawiki/extensions/Renameuser - /usr/share/mediawiki-extensions/base/Renameuser At this very moment debsums -c returns /var/lib/mediawiki/extensions/Renameuser/Renameuser.alias.php /var/lib/mediawiki/extensions/Renameuser/Renameuser.i18n.php /var/lib/mediawiki/extensions/Renameuser/Renameuser_body.php (mediawiki-extensions-base was last installed) Regards, Oskar Liljeblad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719134: mount: very old version in sid lacks crucial features
Package: mount Version: 2.20.1-5.3 Severity: wishlist Dear Maintainer, The util-linux version in debian, 2.20, is extremely old. It is 18 months or so older than 2.23. It lacks many features, such as the --partscan/-P option for losetup. Please upgrade. Regards, Oskar Liljeblad -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mount depends on: ii libblkid12.20.1-5.3 ii libc62.13-38 ii libmount12.20.1-5.3 ii libselinux1 2.1.9-5 ii libsepol12.1.4-3 mount recommends no packages. Versions of packages mount suggests: ii nfs-common 1:1.2.6-4 -- 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#659762: happens to me too
This happens to me too, in at least 50% of the cases (I have tried 4 times so far). Here's my setup: 2x300GB PV 600GB VG 500GB striped LV (2 stripes) lvm 2.02.95-4 linux-image-3.2.0-4-amd64 dmsetup 2:1.02.74-4 Here's what I do: lvcreate -i2 --size 100G --snapshot --name backup /dev/vg1/main # do some work lvremove /dev/vg1/backup and I get the exact error as described above, including frozen I/O on the original volume, /dev/vg1/main). If I do dmsetup resume /dev/mapper/vg1-main the I/O is unfrozen and everything seems to work fine. (Thanks Chris.) There's a lot of I/O activity on the original volume so perhaps that is causing the error. The physical volumes are quite slow. I don't have two snapshots, only one. This is on a replicated production system, but it's mostly reproducable, so perhaps I can try things out if you need me to. Regards, Oskar Liljeblad (os...@osk.mine.nu) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659762: lvremove failure log
After several tries, I managed to reproduce the problem. This time I ran lvremove - -f /dev/vg1/backup, and the output is attached. I hope you can make some sense out of it. /dev/vg1/mongodb is striped LV in VG vg1 on PV /dev/xvdh and PV /dev/xvdi. /dev/vg1/backup is striped snapshot LV of /dev/vg1/mongodb. I hope my setup is straightforward enough - if not, let me know what other information I can provide. Regards, Oskar Liljeblad root@mdb3:~# lvremove - -f /dev/vg1/backup #lvmcmdline.c:1055 Processing: lvremove - -f /dev/vg1/backup #lvmcmdline.c:1058 O_DIRECT will be used #libdm-config.c:789 Setting global/locking_type to 1 #libdm-config.c:789 Setting global/wait_for_locks to 1 #locking/locking.c:242 File-based locking selected. #libdm-config.c:758 Setting global/locking_dir to /run/lock/lvm #toollib.c:228 Using logical volume(s) on command line #locking/file_locking.c:236 Locking /run/lock/lvm/V_vg1 WB #locking/file_locking.c:141 _do_flock /run/lock/lvm/V_vg1:aux WB #locking/file_locking.c:141 _do_flock /run/lock/lvm/V_vg1 WB #locking/file_locking.c:51 _undo_flock /run/lock/lvm/V_vg1:aux #device/dev-cache.c:333 /dev/xvda1: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2049: Aliased to /dev/xvda1 in device cache #device/dev-cache.c:330 /dev/disk/by-uuid/f4f6befc-d80d-4017-a127-ebe1f0380ee4: Aliased to /dev/xvda1 in device cache #device/dev-cache.c:330 /dev/root: Aliased to /dev/xvda1 in device cache (preferred name) #device/dev-cache.c:333 /dev/xvdb: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2064: Aliased to /dev/xvdb in device cache #device/dev-cache.c:333 /dev/disk/by-uuid/33fe7093-3561-4890-872d-abcb59b3880f: Added to device cache #device/dev-cache.c:333 /dev/xvdb1: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2064-part1: Aliased to /dev/xvdb1 in device cache #device/dev-cache.c:330 /dev/disk/by-uuid/1718f7fb-0a10-4270-93fc-8b75ad8ed73c: Aliased to /dev/xvdb1 in device cache #device/dev-cache.c:330 /dev/xvdb2: Aliased to /dev/disk/by-uuid/33fe7093-3561-4890-872d-abcb59b3880f in device cache (preferred name) #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2064-part2: Aliased to /dev/xvdb2 in device cache #device/dev-cache.c:319 /dev/disk/by-uuid/33fe7093-3561-4890-872d-abcb59b3880f: Already in device cache #device/dev-cache.c:333 /dev/xvdh: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2160: Aliased to /dev/xvdh in device cache #device/dev-cache.c:333 /dev/xvdi: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2176: Aliased to /dev/xvdi in device cache #device/dev-cache.c:333 /dev/dm-0: Added to device cache #device/dev-cache.c:330 /dev/disk/by-id/dm-name-vg1-mongodb: Aliased to /dev/dm-0 in device cache (preferred name) #device/dev-cache.c:330 /dev/disk/by-id/dm-uuid-LVM-2A7z5mvNLamjsuxAaIuoAdACm80Pc9N4i9yDRh3s1Ji9mXPW23sygzymjCFzExst: Aliased to /dev/disk/by-id/dm-name-vg1-mongodb in device cache #device/dev-cache.c:330 /dev/disk/by-uuid/72165f22-3863-45fa-a5f3-df5b767f: Aliased to /dev/disk/by-id/dm-name-vg1-mongodb in device cache #device/dev-cache.c:330 /dev/mapper/vg1-mongodb: Aliased to /dev/disk/by-id/dm-name-vg1-mongodb in device cache (preferred name) #device/dev-cache.c:330 /dev/vg1/mongodb: Aliased to /dev/mapper/vg1-mongodb in device cache (preferred name) #device/dev-cache.c:333 /dev/dm-1: Added to device cache #device/dev-cache.c:330 /dev/disk/by-id/dm-name-vg1-backup: Aliased to /dev/dm-1 in device cache (preferred name) #device/dev-cache.c:330 /dev/disk/by-id/dm-uuid-LVM-2A7z5mvNLamjsuxAaIuoAdACm80Pc9N4jnTar3pJic4fN9jtLGEoR0SQw117iwHU: Aliased to /dev/disk/by-id/dm-name-vg1-backup in device cache #device/dev-cache.c:319 /dev/disk/by-uuid/72165f22-3863-45fa-a5f3-df5b767f: Already in device cache #device/dev-cache.c:330 /dev/mapper/vg1-backup: Aliased to /dev/disk/by-id/dm-name-vg1-backup in device cache (preferred name) #device/dev-cache.c:330 /dev/vg1/backup: Aliased to /dev/mapper/vg1-backup in device cache (preferred name) #device/dev-cache.c:333 /dev/dm-2: Added to device cache #device/dev-cache.c:330 /dev/mapper/vg1-mongodb-real: Aliased to /dev/dm-2 in device cache (preferred name) #device/dev-cache.c:333 /dev/dm-3: Added to device cache #device/dev-cache.c:330 /dev/mapper/vg1-backup-cow: Aliased to /dev/dm-3 in device cache (preferred name) #ioctl/libdm-iface.c:1687 dm status (253:0) OF [16384] (*1) #device/dev-io.c:524 Opened /dev/vg1/mongodb RO O_DIRECT #device/dev-io.c:271 /dev/vg1/mongodb: size is 1046478848 sectors #device/dev-io.c
Bug#659762: lvremove failure log
On Tuesday, January 15, 2013 at 15:36, Alasdair G Kergon wrote:
After several tries, I managed to reproduce the problem. This time I ran
lvremove - -f /dev/vg1/backup, and the output is attached. I hope you
can make some sense out of it.
#libdm-deptree.c:1547 Unable to deactivate open vg1-backup-cow (253:3)
Likely to be a bug in your udev rules.
(Does Debian still differ from upstream?)
Do you know which rules?
Are you referring to https://bugzilla.redhat.com/show_bug.cgi?id=570359?
Maybe I'm grasping at straws, but do you think this problem would be fixed
by adding the appropriate udev rules?
I did a quick comparison of Debian's udev rule files and those in lvm2 GIT.
Example:
---
Debian: /lib/udev/rules.d/56-lvm.rules
lvm2: udev/11-dm-lvm.rules
Missing in Debian:
# Do not create symlinks for inappropriate subdevices.
ENV{DM_LV_NAME}==pvmove?*|?*_vorigin, GOTO=lvm_disable
ENV{DM_LV_LAYER}==?*, GOTO=lvm_disable
# Create symlinks for top-level devices only.
ENV{DM_VG_NAME}==?*, ENV{DM_LV_NAME}==?*,
SYMLINK+=$env{DM_VG_NAME}/$env{DM_LV_NAME}, GOTO=lvm_end
---
---
Debian: (none)
lvm2: udev/69-dm-lvm-metad.rules
Missing in Debian:
SUBSYSTEM!=block, GOTO=lvm_end
# Device-mapper devices are processed only on change event or on supported
# synthesized event.
KERNEL==dm-[0-9]*, ENV{DM_UDEV_RULES_VSN}!=?*, GOTO=lvm_end
# Only process devices already marked as a PV - this requires blkid to be
# called before.
ENV{ID_FS_TYPE}==LVM2_member|LVM1_member, RUN+=$env{DM_SBIN_PATH}/pvscan
--cache --major $major --minor $minor
LABEL=lvm_end
---
---
Debian: /lib/udev/rules.d/55-dm.rules
lvm2: udev/10-dm.rules.in
Missing in Debian:
VSN stuff, whatever that is
# Decode udev control flags and set environment variables appropriately.
# These flags are encoded in DM_COOKIE variable that was introduced in
# kernel version 2.6.31. Therefore, we can use this feature with
# kernels = 2.6.31 only. Cookie is not decoded for remove event.
ENV{DM_COOKIE}==?*, IMPORT{program}=$env{DM_SBIN_PATH}/dmsetup udevflags
$env{DM_COOKIE}
---
Regards,
Oskar
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698114: apticron: report maximum urgency for all needed updates
Package: apticron Version: 1.1.55 Severity: wishlist This is similar to #668541 but not the same. It would be nice for apticron to report the maximum urgency for all packages that need to be updated. That way one could determine if upgrading can be held off for a while. Regards, Oskar Liljeblad -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695569: wordpress: plugin dirs cannot be symlinked due to plugin_basename bug
Package: wordpress Version: 3.4.2+dfsg-1 Severity: wishlist The patch for #686228 did not fix the problem when the plugin directory itself (or some ancestor directory) is a symlink. However, it fixes the problem when individual plugins are symlinks. Regards, Oskar -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686228: wordpress: plugin dirs cannot be symlinked due to plugin_basename bug
On Wednesday, September 12, 2012 at 15:09, Raphael Hertzog wrote: Right, it looks like we have to enhance plugin_basename() to be aware of the two possible locations of plugins. :-| I released 3.4.2+dfsg-1 with a fix for this issue. Can you verify whether the fix works for you? It seems to work. Thanks! Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688559: xbmc: reboot, shutdown and restart not implemented
Package: xbmc
Version: 2:11.0~git20120510.82388d5
Severity: normal
Hello
Thanks for packaging XBMC for Debian, and especially for keeping it up to
date. Reboot, shutdown and restart operations terminate XBMC, but nothing
beyond that. Looking at the source code it seems you have look at the exit
code. In xbmc-11.0~git20120510.82388d5/xbmc/XBApplicationEx.h:
// Do not change the numbering, external scripts depend on them
enum {
EXITCODE_QUIT = 0,
EXITCODE_POWERDOWN = 64,
EXITCODE_RESTARTAPP= 65,
EXITCODE_REBOOT= 66,
};
Then I look at /usr/bin/xbmc and return code 65 seems to be handled there,
but it still doesn't restart XBMC.
Regards,
Oskar
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686336: icinga-web: fix default reporting download directory
Package: icinga-web Version: 1.7.1-4 Severity: minor I know debian does not provide a package for Icinga reporting but this would simplify installing it in Debian: In /usr/share/icinga-web/app/modules/Reporting/config/module.xml there is a hardcoded path for temporary reports generated and sent by the Reporting clonk: setting name=dir.download/usr/app/modules/Reporting/data/tmp//setting This can of course be overriden by the user in /etc/icinga-web/conf.d/module_reporting.xml but wouldn't it be more sensible to set it correct by default? Maybe setting name=dir.download/var/cache/icinga-web/reports/setting or setting name=dir.download/var/spool/icinga-web/reports/setting Regards, Oskar Liljeblad -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686228: wordpress: plugin dirs cannot be symlinked due to plugin_basename bug
Package: wordpress
Version: 3.4.1+dfsg-1
Severity: normal
With the current Debian WordPress directory layout with
/usr/share/wordpress/wp-content and /var/lib/wordpress/wp-content
(and perhaps /var/www/yoursite/wp-content) it is
basically implied that you should symlink plugin directories.
Now most plugins use plugin_basename(__FILE__) to determine their basename.
It is assumed that this function returns a relative directory, but it doesn't
if the plugin is not physically located in WP_PLUGIN_DIR (or WPMU_PLUGIN_DIR).
(With physically located I mean located according to realpath (without
symlinks) - the plugin may still be reachable through WP_PLUGIN_DIR.)
This patch fixes the problem but it is crude. I can imagine that there is a
better fix. Perhaps plugins should not use __FILE__ to refer to their
location, but it seems most do.
Regards,
Oskar Liljeblad (os...@osk.mine.nu)
--- /usr/share/wordpress/wp-includes/plugin.php.v0 2012-08-30
07:53:17.170461007 +
+++ /usr/share/wordpress/wp-includes/plugin.php 2012-08-30 08:10:05.126459994
+
@@ -565,6 +565,11 @@
$mu_plugin_dir = str_replace('\\','/',WPMU_PLUGIN_DIR); // sanitize for
Win32 installs
$mu_plugin_dir = preg_replace('|/+|','/', $mu_plugin_dir); // remove
any duplicate slash
$file = preg_replace('#^' . preg_quote($plugin_dir, '#') . '/|^' .
preg_quote($mu_plugin_dir, '#') . '/#','',$file); // get relative path from
plugins dir
+ # Begin Oskar Liljeblad os...@vergic.com 2012-08-30
+ $sys_plugin_dir1 = '/usr/share/wordpress/wp-content/plugins';
+ $sys_plugin_dir2 = '/var/lib/wordpress/wp-content/plugins';
+ $file = preg_replace('#^' . preg_quote($sys_plugin_dir1, '#') . '/|^' .
preg_quote($sys_plugin_dir2, '#') . '/#','',$file); // get relative path from
plugins dir
+ # End Oskar Liljeblad os...@vergic.com 2012-08-30
$file = trim($file, '/');
return $file;
}
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686228: wordpress: plugin dirs cannot be symlinked due to plugin_basename bug
On Thursday, August 30, 2012 at 11:18, Raphael Hertzog wrote: Now most plugins use plugin_basename(__FILE__) to determine their basename. It is assumed that this function returns a relative directory, but it doesn't if the plugin is not physically located in WP_PLUGIN_DIR (or WPMU_PLUGIN_DIR). (With physically located I mean located according to realpath (without symlinks) - the plugin may still be reachable through WP_PLUGIN_DIR.) The default value of WP_PLUGIN_DIR is (see wp-includes/default-constants.php): define( 'WP_PLUGIN_DIR', WP_CONTENT_DIR . '/plugins' ); // full path, no trailing slash And the default value of WP_CONTENT_DIR with the official Debian package is /var/lib/wordpress/wp-content so WP_PLUGIN_DIR points to /var/lib/wordpress/wp-content/plugins. Given the above, I believe that there should be no problems. Please check that you have a correct version of /usr/share/wordpress/wp-config.php. Looking at the bundled plugin, akismet, I see in /usr/share/wordpress/wp-content/plugins/akismet/admin.php at least one plugin_basename(__FILE__). Wouldn't this cause a problem because plugin_basename(/usr/share/wordpress/wp-content/plugins/akismet/admin.php) with WP_PLUGIN_DIR = /var/lib/wordpress/wp-content/plugins would return /usr/share/wordpress/wp-content/plugins/akismet/admin.php And that is not a basename - it's an absolute path... Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680166: openvpn-auth-ldap: leaving Timeout unset causes openvpn to crash
Package: openvpn-auth-ldap Version: 2.0.3-2 Severity: normal If you do not set Timeout in openvpn-auth-ldap's configuration file, OpenVPN will crash. From the log file: [..] Wed Jul 4 07:24:55 2012 TCPv4_SERVER link local: [undef] Wed Jul 4 07:24:55 2012 TCPv4_SERVER link remote: [AF_INET]212.xxx.yyy.zzz:40823 Wed Jul 4 07:24:55 2012 212.xxx.yyy.zzz:40823 TLS: Initial packet from [AF_INET]212.xxx.yyy.zzz:40823, sid=c524afbb 2f3a09df openvpn: sasl.c:257: ldap_parse_sasl_bind_result: Assertion `res != ((void *)0)' failed. The fix for OpenVPN to prevent it from crashing is here: http://code.google.com/p/openvpn-auth-ldap/source/detail?r=1324 More information about the problem: http://code.google.com/p/openvpn-auth-ldap/issues/detail?id=11 I expect the fix will be included in a future version of OpenVPN in Debian. But it does not fix the problem per se. Perhaps openvpn-auth-ldap should check and make sure the timeout value is set too. Or set a reasonable default. Regards, Oskar -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677420: Usage: mountpoint output after activating swap
Package: initscripts
Version: 2.88dsf-22.1
Severity: wishlist
This is happens during boot (from my /var/log/boot):
Wed Jun 13 22:34:41 2012: [] Activating swap...^[[?25l^[[?1c^[7^[[1G[^[[32m
ok ^[[39;49m^[8^[[?25h^[[?0cdone.
Wed Jun 13 22:34:41 2012: Usage: mountpoint [-q] [-d] [-x] path
Wed Jun 13 22:34:41 2012: [] Checking root file system...fsck from
util-linux 2.20.1
My only guess is that $rootdev might be unset in /etc/init.d/checkroot.sh line
89:
[..]
log_daemon_msg Activating swap
swapon -a -v
log_end_msg $?
fi
fi
#
# Does the root device in /etc/fstab match with the actual device ?
# If not we try to use the /dev/root alias device, and if that
# fails we create a temporary node in /run.
#
if [ $rootcheck = yes ]
then
ddev=$(mountpoint -qx $rootdev)
rdev=$(mountpoint -d /)
if [ $ddev != $rdev ] [ $ddev != 4:0 ]
then
if [ $(mountpoint -qx /dev/root) = 4:0 ]
then
rootdev=/dev/root
[..]
I'll try to look into this later on.
Regards,
Oskar
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initscripts depends on:
ii coreutils 8.13-3.2
ii debianutils 4.3.1
ii file-rc 0.8.12
ii libc6 2.13-33
ii lsb-base4.1+Debian6
ii mount 2.20.1-5
ii sysvinit-utils 2.88dsf-22.1
ii ucf 3.0025+nmu3
Versions of packages initscripts recommends:
ii e2fsprogs 1.42.2-2
ii psmisc 22.16-1
initscripts suggests no packages.
-- Configuration Files:
/etc/init.d/bootlogd changed:
PATH=/sbin:/bin # No remote fs at start
DAEMON=/sbin/bootlogd
[ -x $DAEMON ] || exit 0
NAME=bootlogd
DESC=boot logger
BOOTLOGD_OPTS=-r -c
. /lib/init/vars.sh
. /lib/lsb/init-functions
SCRIPTNAME=${0##*/}
SCRIPTNAME=${SCRIPTNAME#[SK]??}
ACTION=$1
case $0 in
*stop-bootlog*)
[ $ACTION = start ] ACTION=stop
;;
esac
case $ACTION in
start)
# PATH is set above
[ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME
if [ -d /proc/1/. ]
then
umask 027
start-stop-daemon --start --quiet --exec $DAEMON -- \
$BOOTLOGD_OPTS
ES=$?
else
$DAEMON $BOOTLOGD_OPTS
ES=$?
fi
[ $VERBOSE != no ] log_end_msg $ES
;;
stop)
PATH=/bin:/sbin:/usr/bin:/usr/sbin
[ $VERBOSE != no ] log_daemon_msg Stopping $DESC $NAME
start-stop-daemon --oknodo --stop --quiet --exec $DAEMON
ES=$?
sleep 1
[ $VERBOSE != no ] log_end_msg $ES
if [ -f /var/log/boot ] [ -f /var/log/boot~ ]
then
[ $VERBOSE = no ] || log_action_begin_msg Moving boot log
file
# bootlogd writes to boot, making backup at boot~
cd /var/log {
chgrp adm boot || :
savelog -q -p -c 5 boot \
mv boot.0 boot \
mv boot~ boot.0
}
ES=$?
[ $VERBOSE = no ] || log_action_end_msg $ES
fi
;;
restart|force-reload)
/etc/init.d/bootlogd stop
/etc/init.d/bootlogd start
;;
status)
status_of_proc $DAEMON $NAME exit 0 || exit $?
;;
*)
echo Usage: $SCRIPTNAME {start|stop|restart|force-reload|status} 2
exit 3
;;
esac
:
-- 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#677420: Acknowledgement (Usage: mountpoint output after activating swap)
Strange, now it's gone. Only thing I did was remove quotes from UUID lines. E.g. now my fstab is: proc/proc proc defaults0 0 UUID=bd82eeef-787b-4195-913a-0275273d5aa9 / ext4 errors=remount-ro 0 1 UUID=0b812248-af81-48df-882d-585622f5b386 noneswap sw 0 0 UUID=93ae20c9-889d-4945-be64-8e6acaf9478b /d ext4 defaults0 3 but it used to be UUID=bd82eeef-787b-4195-913a-0275273d5aa9 ... UUID=0b812248-af81-48df-882d-585622f5b386 ... UUID=93ae20c9-889d-4945-be64-8e6acaf9478b ... Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671874: linux-2.6: build nfs-modules udeb for amd64
Package: linux-2.6 Version: 3.2.15-1 Severity: wishlist Busybox in Debian has recently been updated with NFS mount support, but in order to mount remote NFS file systems during d-i nfs modules are needed. It seems nfs-modules are already build for some other architecture but not amd64. Here is a patch to build them for amd64 - its probably not perfect but it did it for me. I have verified that d-i now will allow NFS mount as long as you pass -o nolock to mount. My next step will be to get partman to support NFS root... Regards, Oskar Liljeblad (os...@osk.mine.nu) -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.3 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671874: patch
Here is the patch. Oskar diff -u debian/changelog.v0 debian/changelog --- debian/changelog.v0 2012-05-07 13:59:52.178398016 + +++ debian/changelog 2012-05-07 14:00:57.491357168 + @@ -1,3 +1,9 @@ +linux-2.6 (3.2.15-1+oskar.1) unstable; urgency=low + + * Build nfs-modules d-i package for amd64. + + -- Oskar Liljeblad os...@osk.mine.nu Mon, 07 May 2012 16:00:32 +0200 + linux-2.6 (3.2.15-1) unstable; urgency=high * New upstream stable update: diff -u debian/control.v0 debian/control --- debian/control.v0 2012-05-07 13:56:09.241896698 + +++ debian/control 2012-05-07 13:56:32.773771687 + @@ -504,6 +504,17 @@ XC-Package-Type: udeb XB-Kernel-Version: 3.2.0-2-amd64 +Package: nfs-modules-3.2.0-2-amd64-di +Architecture: amd64 +Section: debian-installer +Priority: extra +Provides: nfs-modules +Depends: kernel-image-3.2.0-2-amd64-di +Description: NFS filesystem support + This package contains the NFS filesystem module for the kernel. +XC-Package-Type: udeb +XB-Kernel-Version: 3.2.0-2-amd64 + Package: ufs-modules-3.2.0-2-amd64-di Architecture: amd64 Section: debian-installer diff -u /dev/null debian/installer/amd64/modules/amd64/nfs-modules --- /dev/null 2011-03-04 11:53:52.0 + +++ debian/installer/amd64/modules/amd64/nfs-modules 2012-05-07 13:59:02.589373714 + @@ -0,0 +1,2 @@ +#include nfs-modules + diff -u debian/rules.gen.v0 debian/rules.gen --- debian/rules.gen.v0 2012-05-07 14:05:32.510140925 + +++ debian/rules.gen 2012-05-07 14:07:01.002797388 + @@ -17,7 +17,7 @@ $(MAKE) -f debian/rules.real binary-arch-arch ABINAME='3.2.0-2' ABINAME_PART='-2' ARCH='alpha' KERNEL_ARCH='alpha' SOURCEVERSION='3.2.15-1' UPSTREAMVERSION='3.2' VERSION='3.2' binary-arch_amd64:: binary-arch_amd64_none binary-arch_amd64_real binary-arch_amd64_rt binary-arch_amd64:: - $(MAKE) -f debian/rules.real install-udeb_amd64 ABINAME='3.2.0-2' ABINAME_PART='-2' ARCH='amd64' KERNEL_ARCH='x86' SOURCEVERSION='3.2.15-1' UPSTREAMVERSION='3.2' VERSION='3.2' PACKAGE_NAMES='kernel-image-3.2.0-2-amd64-di nic-modules-3.2.0-2-amd64-di nic-extra-modules-3.2.0-2-amd64-di nic-wireless-modules-3.2.0-2-amd64-di nic-shared-modules-3.2.0-2-amd64-di serial-modules-3.2.0-2-amd64-di usb-serial-modules-3.2.0-2-amd64-di ppp-modules-3.2.0-2-amd64-di pata-modules-3.2.0-2-amd64-di cdrom-core-modules-3.2.0-2-amd64-di firewire-core-modules-3.2.0-2-amd64-di scsi-core-modules-3.2.0-2-amd64-di scsi-modules-3.2.0-2-amd64-di scsi-common-modules-3.2.0-2-amd64-di scsi-extra-modules-3.2.0-2-amd64-di plip-modules-3.2.0-2-amd64-di floppy-modules-3.2.0-2-amd64-di loop-modules-3.2.0-2-amd64-di btrfs-modules-3.2.0-2-amd64-di ext2-modules-3.2.0-2-amd64-di ext3-modules-3.2.0-2-amd64-di ext4-modules-3.2.0-2-amd64-di isofs-modules-3.2.0-2-amd64-di jfs-modules-3.2.0-2-amd64-di ntfs-modules-3.2.0-2-amd64-di reiserfs-modules-3.2.0-2-amd64-di xfs-modules-3.2.0-2-amd64-di fat-modules-3.2.0-2-amd64-di ufs-modules-3.2.0-2-amd64-di qnx4-modules-3.2.0-2-amd64-di md-modules-3.2.0-2-amd64-di multipath-modules-3.2.0-2-amd64-di usb-modules-3.2.0-2-amd64-di usb-storage-modules-3.2.0-2-amd64-di pcmcia-storage-modules-3.2.0-2-amd64-di fb-modules-3.2.0-2-amd64-di input-modules-3.2.0-2-amd64-di event-modules-3.2.0-2-amd64-di mouse-modules-3.2.0-2-amd64-di irda-modules-3.2.0-2-amd64-di parport-modules-3.2.0-2-amd64-di nic-pcmcia-modules-3.2.0-2-amd64-di pcmcia-modules-3.2.0-2-amd64-di nic-usb-modules-3.2.0-2-amd64-di sata-modules-3.2.0-2-amd64-di core-modules-3.2.0-2-amd64-di acpi-modules-3.2.0-2-amd64-di i2c-modules-3.2.0-2-amd64-di crc-modules-3.2.0-2-amd64-di crypto-modules-3.2.0-2-amd64-di crypto-dm-modules-3.2.0-2-amd64-di efi-modules-3.2.0-2-amd64-di ata-modules-3.2.0-2-amd64-di mmc-core-modules-3.2.0-2-amd64-di mmc-modules-3.2.0-2-amd64-di nbd-modules-3.2.0-2-amd64-di squashfs-modules-3.2.0-2-amd64-di speakup-modules-3.2.0-2-amd64-di virtio-modules-3.2.0-2-amd64-di uinput-modules-3.2.0-2-amd64-di sound-modules-3.2.0-2-amd64-di zlib-modules-3.2.0-2-amd64-di' + $(MAKE) -f debian/rules.real install-udeb_amd64 ABINAME='3.2.0-2' ABINAME_PART='-2' ARCH='amd64' KERNEL_ARCH='x86' SOURCEVERSION='3.2.15-1' UPSTREAMVERSION='3.2' VERSION='3.2' PACKAGE_NAMES='kernel-image-3.2.0-2-amd64-di nic-modules-3.2.0-2-amd64-di nic-extra-modules-3.2.0-2-amd64-di nic-wireless-modules-3.2.0-2-amd64-di nic-shared-modules-3.2.0-2-amd64-di serial-modules-3.2.0-2-amd64-di usb-serial-modules-3.2.0-2-amd64-di ppp-modules-3.2.0-2-amd64-di pata-modules-3.2.0-2-amd64-di cdrom-core-modules-3.2.0-2-amd64-di firewire-core-modules-3.2.0-2-amd64-di scsi-core-modules-3.2.0-2-amd64-di scsi-modules-3.2.0-2-amd64-di scsi-common-modules-3.2.0-2-amd64-di scsi-extra-modules-3.2.0-2-amd64-di plip-modules-3.2.0-2-amd64-di floppy-modules-3.2.0-2-amd64-di loop-modules-3.2.0-2-amd64-di btrfs-modules-3.2.0-2-amd64-di ext2-modules-3.2.0-2-amd64-di ext3-modules-3.2.0-2-amd64-di ext4-modules-3.2.0-2-amd64-di isofs-modules-3.2.0-2-amd64-di jfs-modules-3.2.0-2-amd64-di ntfs-modules-3.2.0-2-amd64-di
Bug#671878: partman-base: add NFS root support to partman
Package: partman-base Severity: wishlist Debian busybox recently added support for NFS mount, I've submitted a wishlist bug for linux-2.6 to build nfs-modules udeb (#671874), and here is a wishlist bug to add NFS root support to partman. Some ideas: - use DHCP root-path option (code 17) to get host IP and export name, or ask user (default host IP is gateway IP?). A basic mount -t nfs -o nolock PATH TARGET is needed to mount the fs. Maybe I should look into creating partman-nfs or something myself, but I'm not sure where to start... Regards, Oskar Liljeblad (os...@osk.mine.nu) -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.3 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669002: s3cmd put does not set non-zero exit code on failure
Package: s3cmd Version: 0.9.9.91-1 Severity: normal s3cmd put does not set non-zero exit code on failure, making it almost unusable in automatic backup scripts. Attached is a patch to fix that. I believe this problem exists in 1.0.0 as well. Regards, Oskar Liljeblad -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.1 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash diff -u s3cmd.v0 s3cmd --- s3cmd.v0 2012-04-16 13:44:05.0 +0200 +++ s3cmd 2012-04-16 13:52:48.0 +0200 @@ -1,4 +1,4 @@ -#!/usr/bin/env python +#!/usr/bin/python ## Amazon S3 manager ## Author: Michal Ludvig mic...@logix.cz @@ -322,6 +322,7 @@ warning(uExitting now because of --dry-run) return + failures = 0 seq = 0 for key in local_list: seq += 1 @@ -338,9 +339,11 @@ response = s3.object_put(full_name, uri_final, extra_headers, extra_label = seq_label) except S3UploadError, e: error(uUpload of '%s' failed too many times. Skipping that file. % full_name_orig) + failures += 1 continue except InvalidFileError, e: warning(uFile can not be uploaded: %s % e) + failures += 1 continue speed_fmt = formatSize(response[speed], human_readable = True, floating_point = True) if not Config().progress_meter: @@ -354,6 +357,9 @@ debug(uRemoving temporary encrypted file: %s % unicodise(full_name)) os.remove(full_name) + if failures 0: + sys.exit(1) + def cmd_object_get(args): cfg = Config() s3 = S3(cfg)
Bug#620398: solution by setting REFERRALS off
For me the solution is described here: http://acksyn.org/diary/?p=227cpage=2#comment-2805 Set REFERRALS off in /etc/ldap/ldap.conf. Also, I didn't get an error in my error.log - it was only when I set LogLevel debug that I saw this: auth_ldap authenticate: user xyz authentication failed; URI /ldaptest/ [ldap_search_ext_s() for user failed][Operations error] Regards, Oskar Liljeblad (os...@osk.mine.nu) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647020: nagios-plugins-standard: fix for check_snmp to accept comma-separated list of labels
Package: nagios-plugins-standard Version: 1.4.15-3squeeze1 Severity: normal There is a bug in check_snmp which prevents it from accepting multiple labels with -l (e.g. -l label1,label2). This patch fixes that. Regards, Oskar Liljeblad diff -u -p -b nagios-plugins-1.4.15/plugins/check_snmp.c.v0 nagios-plugins-1.4.15/plugins/check_snmp.c --- nagios-plugins-1.4.15/plugins/check_snmp.c.v0 2010-07-27 22:47:16.0 +0200 +++ nagios-plugins-1.4.15/plugins/check_snmp.c 2011-10-29 15:51:51.0 +0200 @@ -753,7 +753,7 @@ process_arguments (int argc, char **argv if (labels == NULL) die (STATE_UNKNOWN, _(Could not reallocate labels\n)); } - labels++; + nlabels++; ptr = thisarg (ptr); if (strstr (ptr, ') == ptr) labels[nlabels - 1] = ptr + 1; -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646860: netcfg: do not place network and broadcast lines in /etc/network/interfaces
Package: netcfg
Severity: wishlist
Hello, it's 2011 and not 1984. Broadcast and network addresses are standardized
today.
'network' and 'broadcast' lines do not need to be written to
/etc/network/interfaces
any more. They are at best redundant, and at worst confusing users. ifconfig
calculates broadcast and network addresses correctly so they can be removed
safely from the config. Attached is a patch against netcfg-1.59.
Regards,
Oskar Liljeblad
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39.4 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -u -p static.c.v0 static.c
--- static.c.v0 2011-10-27 21:55:11.0 +0200
+++ static.c 2011-10-27 21:59:00.0 +0200
@@ -12,7 +12,6 @@
struct in_addr old_ipaddress = { 0 };
struct in_addr network = { 0 };
-struct in_addr broadcast = { 0 };
struct in_addr netmask = { 0 };
struct in_addr pointopoint = { 0 };
@@ -107,7 +106,6 @@ int netcfg_get_netmask(struct debconfcli
netmask.s_addr != old_netmask.s_addr
) {
network.s_addr = ipaddress.s_addr netmask.s_addr;
-broadcast.s_addr = (network.s_addr | ~netmask.s_addr);
/* Preseed gateway */
gateway.s_addr = ipaddress.s_addr netmask.s_addr;
@@ -189,8 +187,6 @@ static int netcfg_write_static(char *dom
fprintf(fp, iface %s inet static\n, interface);
fprintf(fp, \taddress %s\n, inet_ntop (AF_INET, ipaddress, ptr1, sizeof (ptr1)));
fprintf(fp, \tnetmask %s\n, inet_ntop (AF_INET, netmask, ptr1, sizeof (ptr1)));
-fprintf(fp, \tnetwork %s\n, inet_ntop (AF_INET, network, ptr1, sizeof (ptr1)));
-fprintf(fp, \tbroadcast %s\n, inet_ntop (AF_INET, broadcast, ptr1, sizeof (ptr1)));
if (gateway.s_addr)
fprintf(fp, \tgateway %s\n, inet_ntop (AF_INET, gateway, ptr1, sizeof (ptr1)));
if (pointopoint.s_addr)
@@ -311,10 +307,6 @@ int netcfg_activate_static(struct debcon
di_snprintfcat(buf, sizeof(buf), netmask %s,
inet_ntop (AF_INET, netmask, ptr1, sizeof (ptr1)));
-/* avoid using a third buffer */
-di_snprintfcat(buf, sizeof(buf), broadcast %s,
- inet_ntop (AF_INET, broadcast, ptr1, sizeof (ptr1)));
-
di_info(executing: %s, buf);
rv |= di_exec_shell_log(buf);
@@ -350,11 +342,6 @@ int netcfg_activate_static(struct debcon
inet_ntop (AF_INET, ipaddress, ptr1, sizeof (ptr1)),
masksize);
-/* avoid using a second buffer */
-di_snprintfcat(buf, sizeof(buf), broadcast %s dev %s,
- inet_ntop (AF_INET, broadcast, ptr1, sizeof (ptr1)),
- interface);
-
if (pointopoint.s_addr)
di_snprintfcat(buf, sizeof(buf), peer %s,
inet_ntop (AF_INET, pointopoint, ptr1, sizeof (ptr1)));
@@ -396,7 +383,7 @@ int netcfg_get_static(struct debconfclie
GET_DOMAIN, QUIT }
state = GET_IPADDRESS;
-ipaddress.s_addr = network.s_addr = broadcast.s_addr = netmask.s_addr = gateway.s_addr = pointopoint.s_addr =
+ipaddress.s_addr = network.s_addr = netmask.s_addr = gateway.s_addr = pointopoint.s_addr =
0;
debconf_metaget(client, netcfg/internal-none, description);
Bug#646863: mpt-statusd: detected non-optimal RAID status - no /dev/mptctl
Package: mpt-status Version: 1.2.0-7 Severity: important mpt-statusd: detected non-optimal RAID status is logged every 10 minutes on VMware ESX 4.x. It turned out this was because /dev/mptctl did not exist, because mptctl module was not loaded. As soon as I loaded it the message went away. So perhaps you only need to add this to the init.d script: modprobe -q mptctl || : Regards, Oskar Liljeblad -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39.4 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#341126: Bug still present (smbclient fails with 'session setup failed: SUCCESS - 0')?
On Thursday, July 07, 2011 at 07:17, Christian PERRIER wrote: What can I say - it still happens. Here are some timestamps from last time it occurred: And what is the client version? Sorry, I didn't think about that. It's quite old: 3.2.5-4lenny13 I'll see if I can upgrade to at least squeeze. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#341126: Bug still present (smbclient fails with 'session setup failed: SUCCESS - 0')?
What can I say - it still happens. Here are some timestamps from last time it occurred: -rw-r--r-- 1 root root 12431 2011-06-30 13:10 log.smbclient-failure-15491 -rw-r--r-- 1 root root 12431 2011-06-29 11:35 log.smbclient-failure-1055 -rw-r--r-- 1 root root 12429 2011-06-23 08:05 log.smbclient-failure-85942 -rw-r--r-- 1 root root 12431 2011-06-22 21:25 log.smbclient-failure-29351 -rw-r--r-- 1 root root 12429 2011-06-21 13:35 log.smbclient-failure-55561 -rw-r--r-- 1 root root 12429 2011-06-17 11:55 log.smbclient-failure-2754 -rw-r--r-- 1 root root 45437 2011-06-15 14:20 log.smbclient-failure-53373 -rw-r--r-- 1 root root 12429 2011-06-09 11:55 log.smbclient-failure-63856 -rw-r--r-- 1 root root 12429 2011-06-09 11:20 log.smbclient-failure-17381 -rw-r--r-- 1 root root 13741 2011-05-31 15:15 log.smbclient-failure-76050 -rw-r--r-- 1 root root 13743 2011-05-31 09:45 log.smbclient-failure-85956 The servers are still W2K3. My only problem is with the mssage - session setup failed: SUCCESS. Such a message indicates a bug in the code. Unfortunately I still don't know how to reproduce them. Regards, Oskar On Monday, June 06, 2011 at 07:32, Christian PERRIER wrote: tags 341126 moreinfo thanks Hello, You reported this bug a quite long time ago against smbclient. From the bug log you sometimes were'ntable to connect to a high-load W2K3. server and the faillure happened with a not very clear message. Since then, several samba versions were released. Also, in the original bug, I see the horrible socket options = TCP_NODELAY...which is found on dozensof web pages but is still as wrong as it can be. Samba devels have said and written many times that these very specific parameters should NOT be used in production environment except for very specific needs. Using them randomly is often like shooting self in feet. So, do you still experience these intemittent connection problems in a way that could be investigated? If there is no way to reproduce the bug, I'll consider closing it. Many thanks in advance for your answer -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514454: atool and non-printable characters
On Tuesday, February 24, 2009 at 03:28, Roman Mamedov wrote: I don't know - atool uses 'use locale' and then checks that each character is printable in the current locale using POSIX::isprint. The problem may be related to UTF-8 and that perhaps perl is not in UTF-8 mode by default, or that atool isn't iterating over characters correctly. I have no problems with characters like åäöÅÄÖ in my ISO-8859-1 (en_GB.ISO-8859-1) locale though. [..] Here's a patch that should fix the problem in both UTF-8 and non-UTF-8 locales. Please give it a try. [..] The patch does seem to fix the issue successfully. I've made a new release to deal with the problem. Regards, OSkar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#341126: error log
Here's a few error logs. Regards, Oskar smbclient-failure.tar.gz Description: Binary data
Bug#514454: atool and non-printable characters
On Monday, February 23, 2009 at 22:03, Roman Mamedov wrote:
[..]
I don't know - atool uses 'use locale' and then checks that each
character is printable in the current locale using POSIX::isprint.
The problem may be related to UTF-8 and that perhaps perl is not in
UTF-8 mode by default, or that atool isn't iterating over characters
correctly. I have no problems with characters like åäöÅÄÖ in my
ISO-8859-1 (en_GB.ISO-8859-1) locale though.
Here's a patch that should fix the problem in both UTF-8 and non-UTF-8
locales. Please give it a try.
Regards,
Oskar
--- /home/usel/atool2008-06-08 18:20:09.0 +0200
+++ atool 2009-02-23 19:39:57.0 +0100
@@ -23,6 +23,14 @@
# This file uses tab stops with a length of two.
#
+# XXX: We could use -CLSDA but 5.10.0 has a bug which prevents us from
+# specifying this with shebang.
+if (${^UTF8LOCALE}) {
+ use Encode qw(decode_utf8);
+ binmode( $_, :encoding(UTF-8)) for \*STDIN, \*STDOUT, \*STDERR;
+ $_ = decode_utf8( $_ ) for @ARGV, values %ENV;
+}
+
use File::Basename;
use File::Spec;
use Getopt::Long;
@@ -1630,7 +1639,7 @@
$out .= ;
} elsif ($ch eq ') {
$out .= \\';
-} elsif (!POSIX::isprint($ch)) {
+} elsif ($ch !~ /[[:print:]]/) {
$out .= sprintf('\\%03o', ord($ch));
} else {
$out .= $ch;
Bug#341126: More debug log needed to investigate that bug
On Monday, December 29, 2008 at 09:21, Christian Perrier wrote: Hi Christian! When we came back on this bug back in April-May, you sent us some debug output at level 3 from a session showing the reported failure. It would be very useful if you could send us a debug log at level 10 and not 3: LC_ALL=C smbclient -d 10 //. I have enabled logging at level 10 and I will mail back when I have another failure. Also, testing with a machine running a 3.2.* version of samba would help a lot. You explained that the machine you experience the problem on is a production machine you can't upgrade. However, you maybe have somewhere a test machine where you could install lenny on and try reaching the same Windows 2003 server with? I'll look into this. Regards, Oskar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#341126: #341126 smbclient fails with 'session setup failed: SUCCESS - 0'
On Tuesday, April 01, 2008 at 13:55, Oskar Liljeblad wrote: [..] could you reproduce your reported bug http://bugs.debian.org/341126 with newer samba versions? Could give us the smbclient commandline and debug output? I will try to reproduce the problem, and if it happens again I will enable debug output. It still happens with samba 3.0.24-6etch9. Here's a sample log: [2008/05/20 14:30:06, 3] param/loadparm.c:lp_load(4953) lp_load: refreshing parameters [2008/05/20 14:30:06, 3] param/loadparm.c:init_globals(1418) Initialising global parameters [2008/05/20 14:30:06, 3] param/params.c:pm_process(572) params.c:pm_process() - Processing configuration file /etc/samba/smb.conf [2008/05/20 14:30:06, 3] param/loadparm.c:do_section(3695) Processing section [global] [2008/05/20 14:30:06, 2] lib/interface.c:add_interface(81) added interface ip=192.168.136.120 bcast=192.168.136.255 nmask=255.255.255.0 [2008/05/20 14:30:06, 3] client/client.c:main(3651) Client started (version 3.0.24). [2008/05/20 14:30:06, 3] libsmb/namequery.c:resolve_lmhosts(939) resolve_lmhosts: Attempting lmhosts lookup for name admaps110x20 [2008/05/20 14:30:06, 3] libsmb/namequery.c:resolve_wins(836) resolve_wins: Attempting wins lookup for name admaps110x20 [2008/05/20 14:30:06, 3] libsmb/namequery.c:resolve_wins(839) resolve_wins: WINS server resolution selected and no WINS servers listed. [2008/05/20 14:30:06, 3] libsmb/namequery.c:resolve_hosts(1002) resolve_hosts: Attempting host lookup for name admaps110x20 [2008/05/20 14:30:06, 3] lib/util_sock.c:open_socket_out(874) Connecting to 192.168.136.36 at port 445 [2008/05/20 14:30:06, 3] libsmb/cliconnect.c:cli_session_setup_spnego(721) Doing spnego session setup (blob length=113) [2008/05/20 14:30:06, 3] libsmb/cliconnect.c:cli_session_setup(887) SPNEGO login failed: Unexpected information received It seems all error logs end with SPNEGO login failed: Unexpected informaton received. I hope this is of help. Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341126: [Pkg-samba-maint] Bug#341126: #341126 smbclient fails with 'session setup failed: SUCCESS - 0'
On Tuesday, April 01, 2008 at 18:07, Christian Perrier wrote: [..] It still happens with samba 3.0.24-6etch9. Any chance that you can try with an unstable machine (running samba 3.0.28a)? I'm sorry - this is a production machine at a company I used to work. Upgrading it to unstable or installation a new machine with unstable will not be possible. I can however provide some debug output and I'll try to do that next week. Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341126: #341126 smbclient fails with 'session setup failed: SUCCESS - 0'
On Wednesday, March 26, 2008 at 17:05, Oskar Liljeblad wrote: [..] could you reproduce your reported bug http://bugs.debian.org/341126 with newer samba versions? Could give us the smbclient commandline and debug output? I will try to reproduce the problem, and if it happens again I will enable debug output. It still happens with samba 3.0.24-6etch9. Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341126: #341126 smbclient fails with 'session setup failed: SUCCESS - 0'
On Sunday, March 23, 2008 at 19:00, Noèl Köthe wrote: Hi! could you reproduce your reported bug http://bugs.debian.org/341126 with newer samba versions? Could give us the smbclient commandline and debug output? I will try to reproduce the problem, and if it happens again I will enable debug output. Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472856: libmagic-dev should depend on zlib1g-dev
Package: file Version: 4.23-2 Severity: normal You won't be able to compile stuff linked to libmagic unless you link with libz as well. So libmagic-dev should depend on zlib1g-dev. Shouldn't it? Regards, Oskar -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.12 Locale: LANG=C, LC_CTYPE=en_GB.ISO-8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libmagic-dev depends on: ii libmagic1 4.23-2 File type determination library us libmagic-dev recommends no packages. Versions of packages file depends on: ii libc6 2.7-9 GNU C Library: Shared libraries ii libmagic1 4.23-2 File type determination library us -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422419: exim4: tls_verify_hosts only applies during TLS sessions
On Sunday, May 06, 2007 at 09:16, Andreas Metzler wrote:
You'd be happy with something like this?
[..]
++Listing a host in tls_verify_hosts does not directly require the host
++to actually use TLS. It can still send SMTP commands through
++unencrypted connections. Enforcing TLS for a host needs to be done
++separately using ACLs.
Thanks for the quick response, this looks all good to me!
##
hostlist youmustusedverifiedtls = blah.example.com : foo.example.com
tls_verify_hosts = +youmustusedverifiedtls
[...]
begin acl
acl_check_mail:
deny
message = No TLS encryption used
hosts = +youmustusedverifiedtls
condition = ${if eq{$tls_cipher}{}{yes}{no}}
##
I guess you could replace the condition line with
! encrypted = *
(This is what I do.)
Regards,
Oskar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422419: exim4: tls_verify_hosts only applies during TLS sessions
Package: exim4 Version: 4.63-17 Severity: minor It should be clarified in the documentation that tls_verify_hosts only applies to TLS sessions. That is, if a sending host matched in tls_verify_hosts does not attempt to use TLS, it can still send messages unencrypted. This makes tls_verify_hosts pretty useless, but that's just my humble opinion... Regards, Oskar Liljeblad ([EMAIL PROTECTED]) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21.1 Locale: LANG=C, LC_CTYPE=en_GB.ISO-8859-1 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii exim4-base4.67-1 support files for all exim MTA (v4 ii exim4-daemon-heavy4.67-1 exim MTA (v4) daemon with extended exim4 recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411497: amavisd-new: missing config options from default config
Package: amavisd-new Version: 2.4.2-5 Severity: normal The conf file bundled with the amavisd-new source tarball has a lot of configuration options that the debian configuration files lack. E.g. $max_servers. Oskar -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.2 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408536: ipmitool: impievd open daemon doesn't work
Package: ipmitool Version: 1.8.8-2 Severity: normal /etc/init.d/ipmievd start shows no error, yet ipmievd doesn't start. No process show up. If I run ipmievd open daemon from the command line, same thing - no output, no process. impievd open nodaemon works fine however. Regards, Oskar -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages ipmitool depends on: ii libc62.3.6.ds1-7 GNU C Library: Shared libraries ii libreadline5 5.2-1 GNU readline and history libraries ii libssl0.9.8 0.9.8c-3SSL shared libraries ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip ipmitool recommends no packages. -- no debconf information . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407739: bittornado: always display amount downloaded/uploaded
Package: bittornado
Version: 0.3.17-1
Severity: wishlist
Hello
I've always been annoyed by the fact that btlaunchmanycurses
doesn't show how much has been uploaded/download when the
client is not connected to any peers (or seeding).
This patch should add that output. Now it says e.g.
seeding (100.0%) - 536.6MiB dn 374.6MiB up
rather than just
seeding (100.0%)
Please let me know what you think about the patch.
Regards,
Oskar Liljeblad
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.7
Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages bittornado depends on:
ii python2.4.4-1An interactive high-level object-o
ii python-support0.5.6 automated rebuilding support for p
Versions of packages bittornado recommends:
ii mime-support 3.39-1 MIME files 'mime.types' 'mailcap
-- no debconf information
--- btlaunchmanycurses.bittornado.orig 2007-01-17 07:08:15.0 +0100
+++ btlaunchmanycurses.bittornado 2007-01-18 13:08:14.0 +0100
@@ -209,7 +209,9 @@
progress, status, peers, seeds, dist,
fmtsize(upamt), fmtsize(dnamt) )
else:
-datastr = ''+status+' ('+progress+')'
+datastr = '%s (%s) - %s dn %s up' % (
+status, progress,
+fmtsize(upamt), fmtsize(dnamt) )
self._display_line(datastr)
self._display_line(''+ljust(msg,self.mainwinw-4))
i += 1
Bug#387840: fix bmp mime entry
Package: feh Version: 1.3.4-2 Severity: wishlist Please fix MIME type for bmp images in /usr/lib/mime/packages/feh. Oskar diff -u feh.v0 feh --- feh.v0 2006-09-17 00:46:52.0 +0200 +++ feh 2006-09-17 00:47:14.0 +0200 @@ -5,6 +5,6 @@ image/pnm; feh '%s'; test=test -n $DISPLAY ; description=PNM Image; nametemplate=%s.pnm; priority=7 image/tga; feh '%s'; test=test -n $DISPLAY ; description=TGA Image; nametemplate=%s.tga; priority=7 image/argb; feh '%s'; test=test -n $DISPLAY ; description=ARGB Image; nametemplate=%s.argb; priority=7 -image/bmp; feh '%s'; test=test -n $DISPLAY ; description=BMP Image; nametemplate=%s.bmp; priority=7 +image/x-ms-bmp; feh '%s'; test=test -n $DISPLAY ; description=BMP Image; nametemplate=%s.bmp; priority=7 image/xpm; feh '%s'; test=test -n $DISPLAY ; description=XPM Image; nametemplate=%s.xpm; priority=7 image/pjpeg; feh '%s'; test=test -n $DISPLAY ; description=PJPEG Image; nametemplate=%s.pjpeg; priority=7 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.7 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages feh depends on: ii giblib1 1.2.4-4 wrapper library for imlib2, and ot ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libimlib2 1.2.1-2 powerful image loading and renderi ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii libpng12-0 1.2.8rel-5.2 PNG library - runtime ii libx11-62:1.0.0-9X11 client-side library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages feh recommends: ii wget 1.10.2-2 retrieves files from the web -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365607: crash on http://en.wikipedia.org with ttf-dejavu
On Saturday, June 24, 2006 at 19:52, Eric Dorland wrote: So, just to confirm, this only happens with ttf-dejavu? Yes, it did, but now I can't reproduce it any longer... I guess some other package was updated and that fixed the problem. So this bug can be closed... Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369206: wrong symlink in manual pages
Package: xbase-clients Version: 1:7.0.1-2 Severity: normal I keep getting these errors from cron. It seems these manual pages refer to the wrong file, e.g. .so man1x/xtrap.1x when it should be .so man1/xtrap.1x Oskar Liljeblad ([EMAIL PROTECTED]) /etc/cron.weekly/man-db: mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapreset.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/bitmap.1x: No such file or directory mandb: warning: /usr/share/man/man1/atobm.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapproto.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapstats.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapchar.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapout.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/bitmap.1x: No such file or directory mandb: warning: /usr/share/man/man1/bmtoa.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapin.1x.gz: bad symlink or ROFF `.so' request -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.7 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xbase-clients depends on: ii libc6 2.3.6-10 GNU C Library: Shared libraries ii libfontconfig1 2.3.2-5.1generic font configuration library ii libfreetype62.2.1-2 FreeType 2 font engine, shared lib ii libfs6 2:1.0.0-3X11 Font Services library ii libgl1-mesa-glx [libgl1]6.4.1-0.4A free implementation of the OpenG ii libice6 1:1.0.0-3X11 Inter-Client Exchange library ii libpng12-0 1.2.8rel-5.1 PNG library - runtime ii libsm6 1:1.0.0-4X11 Session Management library ii libx11-62:1.0.0-6X11 client-side library ii libxau6 1:1.0.0-3X11 authorisation library ii libxaw7 1:1.0.1-5X11 Athena Widget library ii libxcursor1 1.1.5.2-5X cursor management library ii libxext61:1.0.0-4X11 miscellaneous extension librar ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxi6 1:1.0.0-5X11 Input extension library ii libxkbfile1 1:1.0.2-3X11 keyboard file manipulation lib ii libxmu6 1:1.0.1-3X11 miscellaneous utility library ii libxmuu11:1.0.1-3X11 miscellaneous micro-utility li ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra ii libxss1 1:1.0.1-4X11 Screen Saver extension library ii libxt6 1:1.0.0-5X11 toolkit intrinsics library ii libxtrap6 1:1.0.0-3X11 event trapping extension libra ii libxtst61:1.0.1-3X11 Testing -- Resource extension ii libxv1 1:1.0.1-3X11 Video extension library ii libxxf86dga12:1.0.0-3X11 Direct Graphics Access extensi ii libxxf86vm1 1:1.0.0-4X11 XFree86 video mode extension l ii x11-common 1:7.0.20 X Window System (X.Org) infrastruc ii zlib1g 1:1.2.3-11 compression library - runtime xbase-clients recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#190429: confirmed!
I can confirm this bug. I also think this bug is pretty serious - the package fails at its main task. Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366182: fix statd home directory
Package: nfs-common Version: 1:1.0.7-12 Severity: wishlist Tags: patch How about this patch to fix (get rid of) old home directory for statd? (It's untested but should clean things up properly.) Regards, Oskar diff -u nfs-common.postinst.v0 nfs-common.postinst --- nfs-common.postinst.v0 2006-05-05 23:53:19.0 +0200 +++ nfs-common.postinst 2006-05-05 23:56:07.0 +0200 @@ -9,6 +9,12 @@ if ! getent passwd statd /dev/null; then adduser --system --home /var/lib/nfs --no-create-home statd fi + + if [ $2 = ] || dpkg --compare-versions $2 gt 1.0.7-12; then + usermod --home /var/lib/nfs statd + rmdir --ignore-fail-on-non-empty /home/statd + fi + if [ $2 = ] || dpkg --compare-versions $2 lt 1.0.7-10; then chown statd /var/lib/nfs/sm \ /var/lib/nfs/sm.bak \ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.7 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages nfs-common depends on: ii adduser 3.87 Add and remove users and groups ii libc6 2.3.6-7GNU C Library: Shared libraries ii libcomerr21.38+1.39-WIP-2006.04.09-1 common error description library ii libevent1 1.1a-1 An asynchronous event notification ii libkrb53 1.4.3-7MIT Kerberos runtime libraries ii libnfsidmap1 0.13-1 An nfs idmapping library ii libwrap0 7.6.dbs-9 Wietse Venema's TCP wrappers libra ii portmap 5-18 The RPC portmapper ii sysvinit 2.86.ds1-14System-V-like init utilities nfs-common recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365607: crash on http://en.wikipedia.org with ttf-dejavu
=0x1da5d50, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]) at nsHTMLFrame.cpp:531 #98 0x00689a89 in nsContainerFrame::ReflowChild ( this=value optimized out, aKidFrame=0x1e8f748, aPresContext=0x1da5d50, [EMAIL PROTECTED], [EMAIL PROTECTED], aX=0, aY=36858560, aFlags=1, [EMAIL PROTECTED]) at nsContainerFrame.cpp:905 #99 0x0069bb05 in nsHTMLScrollFrame::ReflowScrolledFrame ( this=0x1e8f990, [EMAIL PROTECTED], aAssumeHScroll=value optimized out, aAssumeVScroll=value optimized out, aMetrics=0x7faba480, aFirstPass=value optimized out) at nsGfxScrollFrame.cpp:515 #100 0x0069bd2e in nsHTMLScrollFrame::ReflowContents (this=0x1e8f990, aState=0x7fab0710, [EMAIL PROTECTED]) at nsGfxScrollFrame.cpp:570 #101 0x0069d8d8 in nsHTMLScrollFrame::Reflow (this=0x1e8f990, aPresContext=value optimized out, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]) at nsGfxScrollFrame.cpp:768 #102 0x00689a89 in nsContainerFrame::ReflowChild ( this=value optimized out, aKidFrame=0x1e8f990, aPresContext=0x1da5d50, [EMAIL PROTECTED], [EMAIL PROTECTED], aX=0, aY=36858560, aFlags=0, [EMAIL PROTECTED]) at nsContainerFrame.cpp:905 #103 0x006dbfb8 in ViewportFrame::Reflow (this=0x1e8f648, aPresContext=0x1da5d50, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]) at nsViewportFrame.cpp:239 #104 0x00668257 in IncrementalReflow::Dispatch (this=0x7fababd0, aPresContext=0x1da5d50, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]) at nsPresShell.cpp:906 #105 0x0066d953 in PresShell::ProcessReflowCommands (this=0x1e8e200, aInterruptible=1) at nsPresShell.cpp:6873 #106 0x0066dac7 in HandlePLEvent (aEvent=value optimized out) at nsPresShell.cpp:6702 #107 0x2b17ec0e0189 in PL_HandleEvent (self=0x1f22710) at plevent.c:688 #108 0x2b17ec0e0928 in PL_ProcessPendingEvents (self=0x139ec10) at plevent.c:623 #109 0x2b17ec0e1c4b in nsEventQueueImpl::ProcessPendingEvents ( this=0x1383910) at nsEventQueue.cpp:417 #110 0x0062bbd2 in event_processor_callback ( source=value optimized out, condition=4289398544, data=0xfdd98690) at nsAppShell.cpp:67 #111 0x2b17edfffadd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #112 0x2b17ee002da5 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #113 0x2b17ee00306a in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #114 0x2b17ec8d3082 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #115 0x0062c000 in nsAppShell::Run (this=0x140e2c0) at nsAppShell.cpp:139 #116 0x00b9c24e in nsAppStartup::Run (this=0x140e240) at nsAppStartup.cpp:150 #117 0x00442033 in XRE_main (argc=value optimized out, argv=value optimized out, aAppData=value optimized out) #118 0x2b17ef38c4ca in __libc_start_main () from /lib/libc.so.6 #119 0x0043d9aa in _start () at ../sysdeps/x86_64/elf/start.S:113 So it looks like a problem in libcairo2 (1.0.4-2)? I narrowed down the problem to this (non-compliant) HTML code: htmlbody style=font: x-small sans-serif;#7879; 7879 or 0x1ec7 is LATIN SMALL LETTER E WITH CIRCUMFLEX AND DOT BELOW. Regards, Oskar Liljeblad ([EMAIL PROTECTED]) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.7 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages mozilla-firefox depends on: ii firefox 1.5.dfsg+1.5.0.2-3 lightweight web browser based on M mozilla-firefox recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365607: crash on http://en.wikipedia.org with ttf-dejavu
On Monday, May 01, 2006 at 14:17, Justin Pryzby wrote:
[..]
htmlbody style=font: x-small sans-serif;#7879;
Very interesting. Thanks for narrowing it down.
It doesn't crash for me, though. It looks like it might be a pango
problem. Could you try the usual workaround, with
MOZ_DISABLE_PANGO=1?
Thanks for the quick response. I exported MOZ_DISABLE_PANGO=1
and ran firefox --debugger gdb. It crashes this time too,
but with different stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46991541412928 (LWP 2484)]
0x2abd11a8afa4 in TT_New_Context () from /usr/lib/libfreetype.so.6
(gdb) where
#0 0x2abd11a8afa4 in TT_New_Context () from /usr/lib/libfreetype.so.6
#1 0x2abd11a8b2a8 in TT_New_Context () from /usr/lib/libfreetype.so.6
#2 0x2abd11a8bf63 in TT_RunIns () from /usr/lib/libfreetype.so.6
#3 0x2abd11a90437 in TT_RunIns () from /usr/lib/libfreetype.so.6
#4 0x2abd11a8fc3b in TT_RunIns () from /usr/lib/libfreetype.so.6
#5 0x2abd11a90729 in TT_RunIns () from /usr/lib/libfreetype.so.6
#6 0x2abd11a50fa5 in FT_Load_Glyph () from /usr/lib/libfreetype.so.6
#7 0x2abd11bc6f5e in XftFontLoadGlyphs () from /usr/lib/libXft.so.2
#8 0x2abd11bc475f in XftGlyphExtents () from /usr/lib/libXft.so.2
#9 0x2abd11bc4b2b in XftTextExtents32 () from /usr/lib/libXft.so.2
#10 0x005d46df in nsFontXft::GetTextExtents32 (this=value optimized
out, aString=0x23d5c00, aLen=3816, [EMAIL PROTECTED]) at
nsFontMetricsXft.cpp:1947
#11 0x005d418d in nsFontMetricsXft::TextDimensionsCallback
(this=0x23c2a20, aString=0x7fd93108, aLen=1, aFont=0xecf, aData=0xecf)
at nsFontMetricsXft.cpp:1606
#12 0x005d7989 in nsFontMetricsXft::EnumerateGlyphs (this=0x23c2a20,
aString=value optimized out, aLen=value optimized out, aCallback=
{__pfn = 0x5d4150 nsFontMetricsXft::TextDimensionsCallback(unsigned
int const*, unsigned int, nsFontXft*, void*), __delta = 0},
aCallbackData=0x7fd96390)
at nsFontMetricsXft.cpp:1471
#13 0x005d8411 in nsFontMetricsXft::GetTextDimensions
(this=0x23c2a20, aString=0xee7, aLength=61056, [EMAIL PROTECTED],
aFontID=0x0, aContext=value optimized out)
at nsFontMetricsXft.cpp:538
#14 0x006d67de in nsTextFrame::MeasureText (this=0x23d37a8,
aPresContext=0x21a4c30, [EMAIL PROTECTED], [EMAIL PROTECTED],
aLb=0x170b1f0, [EMAIL PROTECTED],
[EMAIL PROTECTED]) at nsTextFrame.cpp:5416
#15 0x006d8e10 in nsTextFrame::Reflow (this=0x23d37a8,
aPresContext=0x21a4c30, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED])
at nsTextFrame.cpp:5980
#16 0x006b11ea in nsLineLayout::ReflowFrame (this=0x7fd96ae0,
aFrame=0x23d37a8, [EMAIL PROTECTED], aMetrics=0x0,
[EMAIL PROTECTED])
at nsLineLayout.cpp:995
#17 0x00680262 in nsBlockFrame::ReflowInlineFrame (this=0x2332ed0,
[EMAIL PROTECTED], [EMAIL PROTECTED], aLine={mCurrent =
0x23d3800}, aFrame=0x23d37a8,
aLineReflowStatus=0x7fd96a87 ) at nsBlockFrame.cpp:4013
#18 0x00680893 in nsBlockFrame::DoReflowInlineFrames
(this=0x2332ed0, [EMAIL PROTECTED], [EMAIL PROTECTED],
aLine={mCurrent = 0x23d3800},
aKeepReflowGoing=0x7fd96d8c, aLineReflowStatus=0x7fd96bcf
\002, aUpdateMaximumWidth=0, aDamageDirtyArea=1) at nsBlockFrame.cpp:3852
#19 0x00680b5a in nsBlockFrame::ReflowInlineFrames (this=0x2332ed0,
[EMAIL PROTECTED], aLine={mCurrent = 0x23d3800},
aKeepReflowGoing=0x7fd96d8c,
aDamageDirtyArea=1, aUpdateMaximumWidth=0) at nsBlockFrame.cpp:3734
#20 0x00680da7 in nsBlockFrame::ReflowLine (this=0xecf,
[EMAIL PROTECTED], aLine={mCurrent = 0x23d3800},
aKeepReflowGoing=0x7fd96d8c, aDamageDirtyArea=1)
at nsBlockFrame.cpp:2728
#21 0x00681327 in nsBlockFrame::ReflowDirtyLines (this=0x2332ed0,
[EMAIL PROTECTED], aTryPull=1) at nsBlockFrame.cpp:2262
#22 0x0068254a in nsBlockFrame::Reflow (this=0x2332ed0,
aPresContext=0x21a4c30, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED])
at nsBlockFrame.cpp:902
#23 0x00683b28 in nsBlockReflowContext::ReflowBlock
(this=0x7fd97420, aSpace=value optimized out, aApplyTopMargin=value
optimized out,
[EMAIL PROTECTED], aClearance=value optimized out,
aIsAdjacentWithTop=value optimized out, [EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]) at nsBlockReflowContext.cpp:605
#24 0x0067f8ba in nsBlockFrame::ReflowBlockFrame (this=0x2332c18,
[EMAIL PROTECTED], aLine={mCurrent = 0x2332f78},
aKeepReflowGoing=0x7fd9777c)
at nsBlockFrame.cpp:3449
#25 0x00680c4e in nsBlockFrame::ReflowLine (this=0x2332c18,
[EMAIL PROTECTED], aLine={mCurrent = 0x2332f78},
aKeepReflowGoing=0x7fd9777c,
aDamageDirtyArea=1)
at nsBlockFrame.cpp:2610
#26 0x00681327 in nsBlockFrame::ReflowDirtyLines (this=0x2332c18,
[EMAIL PROTECTED], aTryPull=1) at nsBlockFrame.cpp:2262
#27 0x0068254a in nsBlockFrame::Reflow (this=0x2332c18,
aPresContext=0x21a4c30, [EMAIL PROTECTED],
Bug#362018: libpam-ssh: pam_ssh.so auth doesn't live well with pam_krb5.so auth (from libpam-krb5)
Package: libpam-ssh Version: 1.91.0-9.1 Severity: normal I'm using openssh-server 4.2p1-8. I have modified the default /etc/pam.d/ssh, from looking like this: [..] # Standard Un*x authentication. @include common-auth # Standard Un*x authorization. @include common-account # Standard Un*x session setup and teardown. @include common-session [..] into this: [..] # Standard Un*x authentication. @include common-auth # Authenticate against ssh identities @include pam-ssh-auth # Standard Un*x authorization. @include common-account # Standard Un*x session setup and teardown. @include common-session # Start ssh-agent and add keys automaticly @include pam-ssh-session [..] Now everything works fine and as expected. However, if I introduce kerberos into this picture, like this: [..] auth sufficient pam_krb5.so ignore_root forwardable auth requiredpam_unix.so try_first_pass nullok_secure # Authenticate against ssh identities @include pam-ssh-auth account required pam_krb5.so ignore_root account required pam_unix.so session optional pam_krb5.so ignore_root session required pam_unix.so # Start ssh-agent and add keys automaticly @include pam-ssh-session Then I can log correctly, the ssh-agent is started, but it has no keys! What's wrong here?? I tried running sshd with -d, but there no messages looked peculiar to me... Nothing in auth syslog either. My password is the same in all the three places (/etc/shadow for pam_unix.so, kerberos KDC for pam_krb5.so, and .ssh/id_rsa for pam_ssh.so). Regards, Oskar -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.2 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages libpam-ssh depends on: ii libc6 2.3.6-5GNU C Library: Shared libraries an ii libpam0g 0.79-3.1 Pluggable Authentication Modules l ii libssl0.9.8 0.9.8a-8 SSL shared libraries Versions of packages libpam-ssh recommends: pn ssh-krb5 | sshnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362018: another thing
If you have enabled ForwardAgent on the client, and is running ssh-agent on the client but with *no* keys, and ssh into the server with pam_ssh.so, you'll end up with an ssh-agent on the server without any keys! In other words, ForwardAgent seems to take precedence over pam_ssh.so. Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320949: what's going on with this bug?
Can you please tell me what's going on with this bug? It's been over 200 days now... Should be an easy fix. Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322628: not fixed - need to rebuild skel.c
This bug is not fixed. Fortunately, with the applied patch sent earlier, only skel.c need to be rebuilt for it to happen! Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341126: smbclient fails with 'session setup failed: SUCCESS - 0'
Package: smbclient Version: 3.0.20b-2+b1 Severity: normal I've seen this problem several times during high load on Windows Server 2003. smbclient tries to connect to the machine but fails with the following error: session setup failed: SUCCESS - 0 The error message should be more elaborate. Perhaps smbclient should try again. Regards, Oskar Liljeblad ([EMAIL PROTECTED]) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.2 Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages smbclient depends on: ii libc6 2.3.5-8.1GNU C Library: Shared libraries an ii libcomerr2 1.38-2 common error description library ii libkrb531.3.6-5 MIT Kerberos runtime libraries ii libldap22.1.30-12OpenLDAP libraries ii libncurses5 5.5-1Shared libraries for terminal hand ii libpopt01.7-5lib for parsing cmdline parameters ii libreadline55.0-11 GNU readline and history libraries ii samba-common3.0.20b-2+b1 Samba common files used by both th smbclient recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340225: fatal: PAM: pam_setcred(): Error in service module
On Monday, November 28, 2005 at 20:57, Russ Allbery wrote: [..] Hm. I can't reproduce this with ssh-krb5 either. I just tried installing it and the current libpam-krb5 and it works correctly with me. I tried essentially the above setup as well as several different orders of the same, and everything worked great. I logged in without any trouble, got a ticket cache, and didn't get any error message like that. Are you still having trouble? Well, I took someone's advice to upgrade to openssh-server, and I did. Now it works. So I'm afraid I won't be of much help here... Perhaps it's just best to close the bug Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340225: fatal: PAM: pam_setcred(): Error in service module
Package: libpam-krb5 Version: 1.2.0-1 Severity: normal Something seems to be wrong with pam_krb5.so auth when used for ssh. I have this line in my /etc/pam.d/ssh: auth required pam_krb5.so use_first_pass forwardable This is what I get when correct password is entered: sshd[32359]: fatal: PAM: pam_setcred(): Error in service module (and ssh just disconnects me). Removing the auth-line above fixes the problem. Regards, Oskar Liljeblad ([EMAIL PROTECTED]) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4 Locale: LANG=en_US, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages libpam-krb5 depends on: ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libcomerr21.38-2 common error description library ii libkrb53 1.3.6-5MIT Kerberos runtime libraries ii libpam0g 0.79-3 Pluggable Authentication Modules l libpam-krb5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340225: fatal: PAM: pam_setcred(): Error in service module
On Monday, November 21, 2005 at 15:35, Russ Allbery wrote: [..] This is what I get when correct password is entered: sshd[32359]: fatal: PAM: pam_setcred(): Error in service module I can't duplicate this. It works great for me using the following configuration: authsufficient pam_unix.so nullok_secure authrequiredpam_krb5.so use_first_pass forwardable What version of the openssh-server package are you using? Also, do you have any session lines for pam_krb5.so? Thanks for looking into this. Sorry for not providing more info the first time. Anyway, here it is: rc openssh-server4.2p1-5 ii ssh-krb5 3.8.1p1-10 ii libkrb53 1.3.6-5 Perhaps I need to upgrade to openssh-server and purge ssh-krb5? (Perhaps then libpam-krb5 should conflict with ssh-krb5.) My /etc/pam.d/ssh: auth required pam_nologin.so @include common-auth auth required pam_krb5.so use_first_pass forwardable auth required pam_env.so @include common-account accountrequired pam_krb5.so @include common-session sessionoptional pam_motd.so sessionoptional pam_mail.so standard noenv sessionrequired pam_limits.so @include common-password Regards, Oskar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316113: Debian package for renameutils
On Monday, August 15, 2005 at 15:27, Francois Marier wrote: [..] By the way, what do you think about the following problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316113 If I understand correctly, the reason why this fails is that the file is hardlinked to its destination and then the source is deleted? It's because it is using the rename(2) syscall to perform the rename, which doesn't allow for move across file systems. Perhaps I could change qmv to use mv, just like qcp is using cp. Then I just need to make sure that the necessary safe guards are in place first. I'll look into it! Regards, Oskar Liljeblad ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322628: yy_init_globals in header file
Package: flex Version: 2.5.31-34 Severity: normal flex 2.5.31 adds this weird line to the generated header file: static int yy_init_globals (yyscan_t yyscanner ); This results in a compiler warning. Why would you want yy_init_globals in the header file? The upstream flex people are TOTALLY unresponsive, please take a look at this. I suggest the patch below. Please for the sake of my sanity, reply to this ASAP! Oskar Liljeblad ([EMAIL PROTECTED]) diff -u flex.skl.v0 flex.skl --- flex.skl.v0 2005-04-22 15:42:46.0 +0200 +++ flex.skl2005-04-22 15:42:57.0 +0200 @@ -815,7 +815,7 @@ ]]) -m4_ifdef( [[M4_YY_IN_HEADER]], +m4_ifdef( [[M4_YY_NOT_IN_HEADER]], [[ static int yy_init_globals M4_YY_PARAMS( M4_YY_PROTO_ONLY_ARG ); ]]) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.4 Locale: LANG=en_US, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages flex depends on: ii debconf [debconf-2.0] 1.4.57 Debian configuration management sy ii libc6 2.3.5-3GNU C Library: Shared libraries an ii m41.4.3-2a macro processing language Versions of packages flex recommends: ii gcc [c-compiler] 4:4.0.1-3 The GNU C compiler ii gcc-3.3 [c-compiler] 1:3.3.6-7 The GNU C compiler ii gcc-4.0 [c-compiler] 4.0.1-4The GNU C compiler -- debconf information: flex/upgrade/pre_2.5.5: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320949: libupnp0: gcc 4.0 compilation warning fix
Package: libupnp0
Version: 1.2.1-2
Severity: normal
The following warning occurs when compiling with gcc 4.0 and libupnp-dev:
In file included from /usr/include/upnp/upnp.h:40,
[..]
/usr/include/upnp/ixml.h:298: warning: type qualifiers ignored on function
return type
This patch should fix that. Would you please add this to the debian package,
as the libupnp maintainers upstream don't seem to be interested (in this or
any other patch fixing small bugs for that matter).
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
diff -u ixml/inc/ixml.h.v0 ixml/inc/ixml.h
--- ixml/inc/ixml.h.v0 2005-08-02 12:32:56.0 +0200
+++ ixml/inc/ixml.h 2005-08-02 12:34:05.0 +0200
@@ -292,7 +292,7 @@
* {\bf Node}.
*/
-const unsigned short
+unsigned short
ixmlNode_getNodeType(IXML_Node *nodeptr
/** The {\bf Node} from which to retrieve the type. */
);
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.8
Locale: LANG=C, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages libupnp0 depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
libupnp0 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315622: same thing happens if kdc cannot be reached
On Sunday, July 10, 2005 at 19:53, Russ Allbery wrote:
I can't duplicate this. On my system, there is a long timeout (about 25
seconds), but not close to 60 seconds, and login deals with it without any
trouble.
Could you provide more information about your Kerberos configuration? It
shouldn't take more than 60 seconds to time out on an unreachable KDC.
My setup is very simple.
[libdefaults]
default_realm = OSK.MINE.NU
[..]
[realms]
OSK.MINE.NU = {
kdc = alpha
admin_server = alpha
}
[..]
alpha is 192.168.1.1, and the computer I try to log in from
is 192.168.1.2. I noticed one thing on the computer I'm log in
in from though: If eth0 (192.168.1.2) is down, then log in
works (using pam_unix.so fallback) immediately.
If however eth0 is up, but alpha is down, it just sits there
as described above.
So I guess it depends on what kind of network problems you have.
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315622: same thing happens if kdc cannot be reached
Package: libpam-krb5 Version: 1.0-12 Followup-For: Bug #315622 The same thing happens if the kdc cannot be reached. It justs sits there for 60 seconds, then this happens: Login timed out after 60 seconds. Here's the relevant lines from my login: auth optional pam_krb5.so use_first_pass accountoptional pam_krb5.so Oskar Liljeblad ([EMAIL PROTECTED]) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11.9 Locale: LANG=en_US, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages libpam-krb5 depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37+1.38-WIP-0509-1 common error description library ii libkrb531.3.6-3 MIT Kerberos runtime libraries pi libpam0g0.76-22 Pluggable Authentication Modules l libpam-krb5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#257527: better patch
I think this patch is more correct! It handles the case %\... as well. Please apply it soon! Regards, Oskar Liljeblad ([EMAIL PROTECTED]) diff -u syntax/c.jsf.in.v0 syntax/c.jsf.in --- syntax/c.jsf.in.v0 2005-04-25 09:36:35.0 +0200 +++ syntax/c.jsf.in 2005-04-25 09:38:08.0 +0200 @@ -278,6 +278,8 @@ :string_control Escape * string_control \nreset + \idle + \\string_escape diouxXeEfFgGaAcspn%SC string :char Constant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272031: patch
If you have or find time to write a patch, please don't hesitate to send it to me ([EMAIL PROTECTED])! Regards, Oskar Liljeblad -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
