Bug#1063837: coreutils: shred: documentation bug: 3>- should be 3>&-

[Greg Wooledge]

Package: coreutils
Version: 9.1-1
Severity: minor
Tags: upstream

The info page for shred includes this example code:

 i=$(mktemp)
 exec 3<>"$i"
 rm -- "$i"
 echo "Hello, world" >&3
 shred - >&3
 exec 3>-

The last line is incorrect.  It should be "exec 3>&-" which closes file
descriptor 3.  As written, the example code creates or truncates a
file literally named "-" instead.

This same error appears on
https://www.gnu.org/software/coreutils/manual/html_node/shred-invocation.html
(as of today) so I believe it's an upstream bug.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u4
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information

Bug#355442: mawk: missing Posix ERE curly braces

[Greg Wooledge]

The version of mawk shipped with bullseye still has this bug (or what
upstream calls a known limitation).

I've also verified that the bug occurs with upstream mawk, version
1.3.4-20200120, both with and without the --without-builtin-regex
compile time option.

unicorn:~/tmp/mawk-1.3.4-20200120$ ./configure --without-builtin-regex
[ output omitted ]
unicorn:~/tmp/mawk-1.3.4-20200120$ make
[ output omitted ]
unicorn:~/tmp/mawk-1.3.4-20200120$ echo 99 | ./mawk '/^9{1}/'
unicorn:~/tmp/mawk-1.3.4-20200120$ 

(Output should have been 99.)

Since it's failing even with --without-builtin-regex I figure this might
be something upstream should hear about, so I'm Cc-ing Mr. Dickey.

Bug#991853: archive.debian.org: Invalid SSL/TLS certificate, https fails

[Greg Wooledge]

Package: www.debian.org
Severity: normal

Apologies if this is the wrong pseudo-package; I couldn't find one
for archive.debian.org specifically.

Attempts to download a package from the archive.debian.org site using
https with command line tools fail.  These examples are performed on a
bullseye host:


$ wget 
https://archive.debian.org/debian/pool/main/a/apt/apt-transport-https_0.9.7.9+deb7u7_amd64.deb
--2021-08-03 08:26:17--  
https://archive.debian.org/debian/pool/main/a/apt/apt-transport-https_0.9.7.9+deb7u7_amd64.deb
Resolving archive.debian.org (archive.debian.org)... 217.196.149.234, 
193.62.202.28, 130.89.148.13, ...
Connecting to archive.debian.org (archive.debian.org)|217.196.149.234|:443... 
connected.
ERROR: The certificate of ‘archive.debian.org’ is not trusted.
ERROR: The certificate of ‘archive.debian.org’ doesn't have a known issuer.
The certificate's owner does not match hostname ‘archive.debian.org’

$ curl 
https://archive.debian.org/debian/pool/main/a/apt/apt-transport-https_0.9.7.9+deb7u7_amd64.deb
 > apt-transport-https_0.9.7.9+deb7u7_amd64.deb
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.


If I go to https://archive.debian.org/debian/pool/main/a/apt/ in
Google Chrome, I'm prompted with the standard warning about an
invalid certificate; if I choose to go forward despite that, I get:


Not Found
The requested URL was not found on this server.

Apache Server at archive.debian.org Port 443


Finally, I will note that it would be most helpful if the archive.debian.org
site can be accessed directly by older systems using the apt-transport-https
package.  If this is impossible due to security concerns, then downloading
the packages by hand on a newer system, and then moving them over to the
older systems, would still be better than the current situation, which is
that the packages are completely inaccessible in environments where plain
http is blocked.

Bug#991578: [Aptitude-devel] Bug#991578: aptitude: document state indicator letters more clearly

[Greg Wooledge]

On Wed, Jul 28, 2021 at 10:06:45AM +0200, Axel Beckert wrote:
> From my mind there are also some more possible states, which seem not
> to be documented in the manual at all on a first glance. IIRC these
> are:
> 
> H or h = on hold
> U or u = unpacked, but not configured, e.g. if the configure step in
>  the previous run failed.
> B  = broken (dependencies are not fullfilled)
> F  = forbidden version

For whatever reason, the aptitude developers did not include all of
the state letters in the man page.  They only included the "most
common" ones, even though the example right above that section includes
a letter that isn't in their list ("h").

This patch only moves things around within the man page.  I didn't add
any additional content, because I was going for a minimalist change.

A larger set of state letters is documented at
 (more
specifically, )
which I *think* is what the man page is referring to when it talks about an
"aptitude reference manual" or "reference guide".

I don't know whether that's a complete set either.

The developers chose to keep that information out of the man page,
and I didn't want to step on any toes, so I kept it out of my patch
as well.  If the developers would like the full set of state letters to
be documented in the man page, I would definitely welcome that.

Bug#991578: aptitude: document state indicator letters more clearly

[Greg Wooledge]

Package: aptitude
Version: 0.8.13-3
Severity: wishlist
Tags: patch

This patch improves the documentation of the state indicator letters, used
in the output of the "search" and "why" actions.

-- Package-specific info:
Terminal: rxvt-unicode-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 10.2.1 20210110
Compiled against:
  apt version 6.0.0
  NCurses version 6.2
  libsigc++ version: 2.10.4
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.2.20201114
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff06399000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7fa53929c000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7fa539261000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7fa539232000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7fa539229000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7fa539123000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fa538fe)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7fa538fc5000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7fa538da3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa538d81000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fa538bb4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa538a7)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fa538a56000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa53888f000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fa538875000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fa538858000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fa538845000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fa53881d000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fa5387fa000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7fa53871d000)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7fa5386f5000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7fa53864)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7fa53852)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7fa538507000)
/lib64/ld-linux-x86-64.so.2 (0x7fa5398c1000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa538501000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fa5384f4000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7fa5384eb000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7fa5384c5000)

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common   0.8.13-3
ii  libapt-pkg6.0 2.2.4
ii  libboost-iostreams1.74.0  1.74.0-9
ii  libc6 2.31-13
ii  libcwidget4   0.5.18-5
ii  libgcc-s1 10.2.1-6
ii  libncursesw6  6.2+20201114-2
ii  libsigc++-2.0-0v5 2.10.4-2
ii  libsqlite3-0  3.34.1-3
ii  libstdc++610.2.1-6
ii  libtinfo6 6.2+20201114-2
ii  libxapian30   1.4.18-3

Versions of packages aptitude recommends:
ii  libdpkg-perl1.20.9
ii  sensible-utils  0.0.14

Versions of packages aptitude suggests:
pn  apt-xapian-index
pn  aptitude-doc-en | aptitude-doc  
pn  debtags 
ii  tasksel 3.68

-- no debconf information
--- aptitude-0.8.13/doc/en/manpage.xml  2020-05-20 23:32:38.0 -0400
+++ aptitude-0.8.13-edited/doc/en/manpage.xml   2021-07-27 15:21:10.599153571 
-0400
@@ -696,32 +696,12 @@
 ihA raptor-utils- Raptor RDF Parser utilities
 
   
-   Each search result is listed on a separate line.  The
-   first character of each line indicates the current state
-   of the package: the most common states are
-   p, meaning that no trace of the package
-   exists on the system, c, meaning that
-   the package was deleted but its configuration files remain
-   on the system, i, 

Bug#988676: pinfo: tag table corrupt after repeating total-search

[Greg Wooledge]

Package: pinfo
Version: 0.6.13-1.1
Severity: normal

I get the message "Tag table is corrupt, trying to fix..." when repeating
a total-search after starting pinfo on a sub-node inside a larger page tree.

Steps to reproduce:

pinfo date
s
%F
f
f

This assumes Debian's default configuration with KEY_TOTALSEARCH_1 = 's'
and KEY_SEARCH_AGAIN_1='f'.

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pinfo depends on:
ii  install-info  6.7.0.dfsg.2-6
ii  libc6 2.31-11
ii  libncursesw6  6.2+20201114-2
ii  libreadline8  8.1-1
ii  libtinfo6 6.2+20201114-2

pinfo recommends no packages.

pinfo suggests no packages.

-- no debconf information

Bug#905564: /etc/default/su

[Greg Wooledge]

There is no /etc/default/su file by default, but if you create one and
put

ALWAYS_SET_PATH yes

in it, then su *does* change the PATH variable, and this avoids the warning
message from login.

ii  util-linux 2.33.1-0.1   amd64miscellaneous system utilities

unicorn:~$ cat /etc/default/su
ALWAYS_SET_PATH yes
unicorn:~$ echo "$PATH"
/home/greg/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin
unicorn:~$ su
Password:
root@unicorn:/home/greg# echo "$PATH"
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
root@unicorn:/home/greg#

Bug#930693: ksh: previous versions have the info

[Greg Wooledge]

Having ksh removed from buster is definitely not my preferred outcome.
Getting one line added to the copyright file would be ideal, but if
that's not allowed, then I can live with "fixed after buster".

Bug#930693: ksh: no Source field in copyright file

[Greg Wooledge]

Package: ksh
Version: 93u+20120801-3.4
Severity: serious
Justification: Policy 12.5

There is no Source field, nor any other information saying where the
upstream sources were obtained, in the copyright file.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ksh depends on:
ii  binfmt-support  2.2.0-2
ii  libc6   2.28-10

ksh recommends no packages.

ksh suggests no packages.

-- debconf-show failed

Bug#929984: lspci: please make -nn the default

[Greg Wooledge]

Package: pciutils
Version: 1:3.5.2-1
Severity: wishlist

Very frequently, people ask for help with their devices (video, network,
etc.) and someone asks them to show the output of lspci.  Which they
eventually do.  But it would be *so* much more helpful if they would
show the output of "lspci -nn" instead.  Unfortunately, educating the
entire helper community to ask for lspci -nn instead of plain lspci is
an extremely slow process.

It would be great if -nn were the default.  People requesting help could
get that help much more quickly and with less wasted effort, if we didn't
have to go through an extra round of asking for information.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pciutils depends on:
ii  libc6 2.28-10
ii  libkmod2  26-1
ii  libpci3   1:3.5.2-1

pciutils recommends no packages.

Versions of packages pciutils suggests:
ii  bzip2  1.0.6-9
ii  curl   7.64.0-3
ii  wget   1.20.1-1.1

-- debconf-show failed

Bug#929677: su: man page: runuser(8) vs. runuser(1)

[Greg Wooledge]

Package: util-linux
Version: 2.33.1-0.1
Severity: minor

The su(1) man page mentions runuser(1) (which is correct) in the DESCRIPTION
section, but runuser(8) (which does not exist) in the SEE ALSO section.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages util-linux depends on:
ii  fdisk  2.33.1-0.1
ii  libaudit1  1:2.8.4-3
ii  libblkid1  2.33.1-0.1
ii  libc6  2.28-10
ii  libcap-ng0 0.7.9-2
ii  libmount1  2.33.1-0.1
ii  libpam0g   1.3.1-5
ii  libselinux12.8-1+b1
ii  libsmartcols1  2.33.1-0.1
ii  libsystemd0241-3
ii  libtinfo6  6.1+20181013-2
ii  libudev1   241-3
ii  libuuid1   2.33.1-0.1
ii  login  1:4.5-1.1
ii  zlib1g 1:1.2.11.dfsg-1

util-linux recommends no packages.

Versions of packages util-linux suggests:
pn  dosfstools  
ii  kbd 2.0.4-4
ii  util-linux-locales  2.33.1-0.1

-- debconf-show failed

Bug#878625:

[Greg Wooledge]

I just discovered today that this bug is related to (and is perhaps the
fundamental cause of) other issues I've been seeing.

Specifically, systemd-logind not being able to recognize my NIS user
account resulted in my not being able to start X (via startx) without
hacking the Xwrapper.config to revert to running X as root.  This was
reported under Debian Bug#833182 because at the time, one of my symptoms
(the "drmSetMaster(): Permission denied" error) matched the subject of
that bug, and I am also on Intel graphics.  So, it seemed like the same
bug.

The other symptoms, which I only noticed more recently, were the complete
lack of all XDG_* environment variables and the lack of a /run/user/MYUID
directory, all of which were supposed to be present in my login sessions.

After installing nscd and rebooting (it didn't work until reboot), all
of these symptoms have been cleared up.  I was able to remove the
needs_root_rights=yes line in the /etc/X11/Xwrapper.config file and
start X without root again.

I don't know if there's a less drastic measure than rebooting that can
make nscd "kick in".

Bug#833182: drmSetMaster failed: Permission denied

[Greg Wooledge]

Actually, won't need a new bug: it's already filed.  Bug#878625.

Bug#833182: drmSetMaster failed: Permission denied

[Greg Wooledge]

Yesterday I noticed another issue and wondered if it might be related
to this one.  Turns out: yes, it is.

The issue as I observed it was the complete lack of all XDG_* environment
variables when I logged in.  Didn't matter whether it was console or ssh.
(There was also no /run/user/MYUID directory created for me.)

After some digging, I found that there is a known issue in recent
systemd: 

Long story short, any user defined by a network service like NIS will not
work in systemd because systemd-logind runs (by default config) in a
no-networking-allowed sandbox.  And my user account is defined in NIS.

There are multiple possible workarounds.  The one I tried first was
installing the nscd package.  That didn't fix it immediately, but it
*did* fix it after rebooting.  So, I never moved on to other potential
solutions such as defining a drop-in override for systemd-logind to turn
off the IPAddressDeny=any feature.  That may be better or worse; I can't
say.

My problem may be different from others in this thread, despite the
same symptomatic error message in the X log.  I'm going to open a
separate bug against the nis package just in case; if it turns out that
I'm wrong, then the bug can be marked as a duplicate.

Bug#881771: Unclear which interface name will be used

[Greg Wooledge]

In the release notes, there's a udevadm command which is supposed to
tell us what the new interface name will be, but I had some trouble
interpreting the output.

wooledg:~$ udevadm test-builtin net_id /sys/class/net/eno1 2>/dev/null
ID_NET_NAMING_SCHEME=v240
ID_NET_NAME_MAC=enxa08cfdc389e0
ID_OUI_FROM_DATABASE=Hewlett Packard
ID_NET_NAME_ONBOARD=eno1
ID_NET_LABEL_ONBOARD=enOnboard Lan
ID_NET_NAME_PATH=enp0s31f6

That's after the upgrade to buster; I did not save the results from
before the upgrade, but basically it would have been the same command
with /sys/class/net/eth0 as the final argument, with the same output.

I thought the new interface name would be enp0s31f6 but it turned out
to be eno1 instead.

tl;dr: there's nothing "predicatable" about these names.

Bug#833182: drmSetMaster failed: Permission denied

[Greg Wooledge]

On Tue, Apr 02, 2019 at 12:10:59AM +0200, Thanatermesis wrote:
> If you installed systemd, maybe you need to install libpam-systemd too to
> solve this issue

It's installed.  I showed it specifically because it was mentioned in
this bug.

> El lun., 1 abr. 2019 a las 17:18, Greg Wooledge ()
> escribió:
> 
> > Various packages that are installed:
> >
> > wooledg:~$ dpkg -l linux-image\* libpam-systemd xserver-xorg-\* | grep
> > '^.i'
> > ii  libpam-systemd:amd64241-1amd64
> > system and service manager - PAM module

Bug#833182: drmSetMaster failed: Permission denied

[Greg Wooledge]

I ran into this bug upon upgrading from stretch to buster today.

This system is an HP EliteDesk desktop PC with:

00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM 
Registers [8086:191f] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:1912] (rev 06)


I have the relevant non-free firmware installed.

wooledg:~$ sudo dmesg | grep -i firmware
[sudo] password for wooledg: 
[0.194776] Spectre V2 : Enabling Restricted Speculation for firmware calls
[0.231494] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[3.892737] i915 :00:02.0: firmware: direct-loading firmware 
i915/skl_dmc_ver1_27.bin
[3.893012] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin 
(v1.27)


Under stretch, I was able to run 'startx' from tty1 as my non-root user
account, without needs_root_rights=yes in Xwrapper.config.  X ran as me,
using the modeset driver, and logged in ~/.local/share/xorg/.

After the upgrade, running startx gave me these errors:

wooledg:~$ grep EE .local/share/xorg/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1140.120] (EE) systemd-logind: failed to get session: PID 1762 does not 
belong to any known session
[  1140.193] (EE) modeset(0): drmSetMaster failed: Permission denied
[  1140.193] (EE)
[  1140.193] (EE) AddScreen/ScreenInit failed for driver 0
[  1140.193] (EE)
[  1140.193] (EE)
[  1140.193] (EE) Please also check the log file at 
"/home/wooledg/.local/share/xorg/Xorg.0.log" for additional information.
[  1140.193] (EE)
[  1140.205] (EE) Server terminated with error (1). Closing log file.


I used lynx from the console to search for a workaround.  I tried purging
the xserver-xorg-legacy package, without success.  I tried reinstalling
it, without success.

I ended up putting needs_root_rights=yes in /etc/X11/Xwrapper.config.
Now, it runs as root, and logs in /var/log/, but at least it's working.

wooledg:~$ grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1178.050] (EE) systemd-logind: failed to get session: PID 1812 does not 
belong to any known session
[  1178.270] (II) Initializing extension MIT-SCREEN-SAVER


I can't tell whether the systemd-logind error is relevant or not.

Various packages that are installed:

wooledg:~$ dpkg -l linux-image\* libpam-systemd xserver-xorg-\* | grep '^.i'
ii  libpam-systemd:amd64241-1amd64
system and service manager - PAM module
ii  linux-image-4.19.0-4-amd64  4.19.28-2amd64
Linux 4.19 for 64-bit PCs (signed)
ii  linux-image-4.9.0-7-amd64   4.9.110-3+deb9u2 amd64
Linux 4.9 for 64-bit PCs
ii  linux-image-4.9.0-8-amd64   4.9.144-3.1  amd64
Linux 4.9 for 64-bit PCs
ii  linux-image-amd64   4.19+104 amd64
Linux for 64-bit PCs (meta-package)
ii  xserver-xorg-core   2:1.20.3-1   amd64
Xorg X server - core server
ii  xserver-xorg-input-all  1:7.7+19 amd64
X.Org X server -- input driver metapackage
ii  xserver-xorg-input-libinput 0.28.2-1 amd64
X.Org X server -- libinput input driver
ii  xserver-xorg-input-wacom0.34.99.1-1  amd64
X.Org X server -- Wacom input driver
ii  xserver-xorg-legacy 2:1.20.3-1   amd64
setuid root Xorg server wrapper
ii  xserver-xorg-video-all  1:7.7+19 amd64
X.Org X server -- output driver metapackage
ii  xserver-xorg-video-amdgpu   18.1.99+git20190207-1amd64
X.Org X server -- AMDGPU display driver
ii  xserver-xorg-video-ati  1:18.1.99+git20190207-1  amd64
X.Org X server -- AMD/ATI display driver wrapper
ii  xserver-xorg-video-fbdev1:0.5.0-1amd64
X.Org X server -- fbdev display driver
ii  xserver-xorg-video-intel2:2.99.917+git20180925-2 amd64
X.Org X server -- Intel i8xx, i9xx display driver
ii  xserver-xorg-video-nouveau  1:1.0.16-1   amd64
X.Org X server -- Nouveau display driver
ii  xserver-xorg-video-qxl  0.1.5-2+b1   amd64
X.Org X server -- QXL display driver
ii  xserver-xorg-video-radeon   1:18.1.99+git20190207-1  amd64
X.Org X server -- AMD/ATI Radeon display driver
ii  xserver-xorg-video-vesa 1:2.4.0-1amd64
X.Org X server -- VESA display driver
ii  xserver-xorg-video-vmware   1:13.3.0-2   amd64
X.Org X server -- VMware display driver

Bug#885414: base-files: lack of quoting in shell variable expansions in /etc/profile

[Greg Wooledge]

On Sun, Jan 14, 2018 at 01:35:30AM +0100, Santiago Vila wrote:
> On Tue, 26 Dec 2017, Greg Wooledge wrote:
> 
> > -if [ -r $i ]; then
> > -  . $i
> > +if [ -r "$i" ]; then
> > +  . "$i"
> 
> Thanks for the report.
> 
> Before I just apply the patch: Is there a standard somewhere
> specifying what kind of filenames are allowed in /etc/profile.d?

Not that I'm aware of.  The glob pattern in /etc/profile appears
to be the only restriction.

Bug#885414: base-files: lack of quoting in shell variable expansions in /etc/profile

[Greg Wooledge]

Package: base-files
Version: 9.9+deb9u3
Severity: normal
Tags: patch

--- /usr/share/base-files/profile   2016-03-04 06:00:00.0 -0500
+++ /tmp/profile2017-12-26 15:49:08.839804524 -0500
@@ -26,8 +26,8 @@
 
 if [ -d /etc/profile.d ]; then
   for i in /etc/profile.d/*.sh; do
-if [ -r $i ]; then
-  . $i
+if [ -r "$i" ]; then
+  . "$i"
 fi
   done
   unset i


-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.1.4+dfsg-1
ii  mawk [awk]  1.3.3-17+b3

base-files recommends no packages.

base-files suggests no packages.

-- debconf-show failed

Bug#868892: tasksel: Unexpected mass package removal with no way to cancel

[Greg Wooledge]

On Wed, Jul 19, 2017 at 01:45:42PM -0300, Henrique de Moraes Holschuh wrote:
> But with the patch, at least there is now an "exit" button when it is
> run in standalone mode...

Yes, that appears to work for me in standalone mode.  I'm not in a
good position to test it within d-i.

Bug#868892: tasksel: Unexpected mass package removal with no way to cancel

[Greg Wooledge]

Package: tasksel
Version: 3.39
Severity: normal

I was trying to help someone in #debian who wanted to install the
Standard set of packages after his netinst had failed to do so due to
a lack of network connection at the time.  I thought that perhaps he
could use tasksel to achieve this, so I tried it on my own computer
first.

I ran "sudo tasksel", and was given the dialog, without any "Standard"
task to choose.  So be it.  I reported that to the user.

But then there was no obvious way for me to escape from tasksel.  There
is no Cancel button -- just an OK button.  Ctrl-C did not work.

So I did what seemed obvious at the time -- I unselected all the tasks
(only one had been selected; I think it was ssh server), and then
selected OK.

Instead of just letting me out, it started deleting packages.  It happened
extremely quickly (on this computer), with no prompt, no warning of
any kind.  Ctrl-C still did not work.  When tasksel finally exited on
its own, there was a long string of ^C^C^C^C^C^C^C... on the terminal.

The only way to figure out what happened, then, is to check the logs.

$ grep remove /var/log/dpkg.log
2017-07-07 11:52:38 startup packages remove
2017-07-07 11:52:48 startup packages remove
2017-07-07 11:52:48 remove exim4:all 4.89-2+deb9u1 
2017-07-19 10:05:49 startup packages remove
2017-07-19 10:05:50 remove python-docutils:all 0.13.1+dfsg-2 
2017-07-19 10:05:50 remove docutils-common:all 0.13.1+dfsg-2 
2017-07-19 10:05:50 remove docutils-doc:all 0.13.1+dfsg-2 
2017-07-19 10:05:50 remove libsoftware-license-perl:all 0.103012-1 
2017-07-19 10:05:50 remove libdata-section-perl:all 0.26-1 
2017-07-19 10:05:50 remove libmro-compat-perl:all 0.12-1 
2017-07-19 10:05:50 remove libclass-c3-perl:all 0.32-1 
2017-07-19 10:05:50 remove libalgorithm-c3-perl:all 0.10-1 
2017-07-19 10:05:50 remove libarchive-extract-perl:all 0.80-1 
2017-07-19 10:05:50 remove libasprintf0c2:amd64 0.19.3-2 
2017-07-19 10:05:50 remove libpod-readme-perl:all 1.1.2-1 
2017-07-19 10:05:50 remove libnamespace-autoclean-perl:all 0.28-1 
2017-07-19 10:05:51 remove libnamespace-clean-perl:all 0.27-1 
2017-07-19 10:05:51 remove libb-hooks-endofscope-perl:all 0.21-1 
2017-07-19 10:05:51 remove libclass-c3-xs-perl:amd64 0.14-1+b1 
2017-07-19 10:05:51 remove libmoox-handlesvia-perl:all 0.001008-2 
2017-07-19 10:05:51 remove libmoo-perl:all 2.002005-1 
2017-07-19 10:05:51 remove libdata-perl-perl:all 0.002009-1 
2017-07-19 10:05:51 remove librole-tiny-perl:all 2.05-1 
2017-07-19 10:05:51 remove libclass-method-modifiers-perl:all 2.12-1 
2017-07-19 10:05:51 remove libclass-xsaccessor-perl:amd64 1.19-2+b7 
2017-07-19 10:05:51 remove libcpan-changes-perl:all 0.42-1 
2017-07-19 10:05:51 remove libmodule-build-perl:all 0.422000-1 
2017-07-19 10:05:51 remove libcpan-meta-perl:all 2.150010-1 
2017-07-19 10:05:51 remove libgetopt-long-descriptive-perl:all 0.100-1 
2017-07-19 10:05:51 remove libsub-exporter-perl:all 0.986-1 
2017-07-19 10:05:51 remove libdata-optlist-perl:all 0.110-1 
2017-07-19 10:05:51 remove libdevel-lexalias-perl:amd64 0.05-1+b4 
2017-07-19 10:05:52 remove libdevel-caller-perl:amd64 2.06-1+b4 
2017-07-19 10:05:52 remove libdevel-globaldestruction-perl:all 0.14-1 
2017-07-19 10:05:52 remove libtype-tiny-perl:all 1.05-1 
2017-07-19 10:05:52 remove liblist-moreutils-perl:amd64 0.416-1+b1 
2017-07-19 10:05:52 remove libexporter-tiny-perl:all 0.042-1 
2017-07-19 10:05:52 remove libfile-slurp-perl:all .19-6 
2017-07-19 10:05:52 remove libimport-into-perl:all 1.002005-1 
2017-07-19 10:05:52 remove libintl-xs-perl:amd64 1.26-2+b1 
2017-07-19 10:05:52 remove libintl-perl:all 1.26-2 
2017-07-19 10:05:52 remove libio-stringy-perl:all 2.111-2 
2017-07-19 10:05:52 remove libisccc90:amd64 1:9.9.5.dfsg-9+deb8u10 
2017-07-19 10:05:52 remove libisc95:amd64 1:9.9.5.dfsg-9+deb8u10 
2017-07-19 10:05:52 remove libjasper1:amd64 1.900.1-debian1-2.4+deb8u3 
2017-07-19 10:05:52 remove libterm-ui-perl:all 0.46-1 
2017-07-19 10:05:52 remove liblog-message-simple-perl:all 0.10-2 
2017-07-19 10:05:52 remove liblog-message-perl:all 0.8-1 
2017-07-19 10:05:53 remove liblwres90:amd64 1:9.9.5.dfsg-9+deb8u10 
2017-07-19 10:05:53 remove libparams-validate-perl:amd64 1.26-1 
2017-07-19 10:05:53 remove libpackage-stash-perl:all 0.37-1 
2017-07-19 10:05:53 remove libmodule-implementation-perl:all 0.09-1 
2017-07-19 10:05:53 remove libmodule-load-conditional-perl:all 0.68-1 
2017-07-19 10:05:53 remove libmodule-pluggable-perl:all 5.2-1 
2017-07-19 10:05:53 remove libmodule-runtime-perl:all 0.014-2 
2017-07-19 10:05:53 remove libmodule-signature-perl:all 0.81-1 
2017-07-19 10:05:53 remove libpackage-constants-perl:all 0.06-1 
2017-07-19 10:05:53 remove libpackage-stash-xs-perl:amd64 0.28-3+b1 
2017-07-19 10:05:53 remove libpadwalker-perl:amd64 2.2-2+b1 
2017-07-19 10:05:53 remove libpango1.0-0:amd64 1.40.5-1 
2017-07-19 10:05:53 remove libpangox-1.0-0:amd64 0.0.2-5+b2 
2017-07-19 10:05:53 remove libpangoxft-1.0-0:amd64 1.40.5-1 
2017-07-19 

Bug#860264: Acknowledgement (nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ...")

[Greg Wooledge]

I believe I was able to get this working by making a change to the
/etc/network/interfaces file:

# allow-hotplug eth0
auto eth0
iface eth0 inet dhcp

I replaced the allow-hotplug with auto.  Now, after booting, it appears
to be working:

wooledg:~$ sudo systemctl status nfs-server
* nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor prese
  Drop-In: /etc/systemd/system/nfs-server.service.d
   `-waitlonger.conf
   Active: active (exited) since Mon 2017-04-17 08:57:17 EDT; 2min 17s ago
  Process: 555 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/
  Process: 552 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS
 Main PID: 555 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/nfs-server.service

Apr 17 08:57:17 wooledg systemd[1]: Starting NFS server and services...
Apr 17 08:57:17 wooledg systemd[1]: Started NFS server and services.

wooledg:~$ /sbin/showmount -e
Export list for wooledg:
/home ebase-fla.eeg.ccf.org,ebase.eeg.ccf.org

I only tested one time, though.  There might still be a race condition.

Inspiration for this came from
https://unix.stackexchange.com/questions/209832/debian-systemd-network-online-target-not-working
which shows an Ubuntu unit file (not present on my stretch installation).
This unit uses the "ifquery --list --exclude lo --allow auto" command to
try to determine which interfaces it should wait for.  This command did
not work for me, since my interface had been created by the installer with
"allow-hotplug" instead of "auto".

So, on the theory that maybe systemd's "network-online.target" is doing
something similar to this, I tried the change.  It seemed to work.

Systemd brags about how great its documentation is, but it doesn't bother
explaining what network-online.target actually does, or how to make it
work.

Digging around some more (for the benefit of anyone who may be reading
this bug report and trying to learn, as I am):

wooledg:~$ systemctl list-dependencies network-online.target
network-online.target
* `-networking.service

wooledg:~$ cat /lib/systemd/system/networking.service
[...]
[Service]
Type=oneshot
EnvironmentFile=-/etc/default/networking
ExecStartPre=-/bin/sh -c '[ "$CONFIGURE_INTERFACES" != "no" ] && [ -n 
"$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle'
ExecStart=/sbin/ifup -a --read-environment
ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
RemainAfterExit=true
TimeoutStartSec=5min

wooledg:~$ man ifquery
[...]
   -l, --list
  For  ifquery,  list all the interfaces which match the specified
  class.  If no class specified, prints all the interfaces  listed
  as auto.
[...]

Again, the reference to "auto".  Apparently "allow-hotplug" breaks all
kinds of things.

Bug#860264: nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ..."

[Greg Wooledge]

Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: normal

The NFS server starts before DNS is working, causing exportfs to fail:

wooledg:~$ sudo systemctl status nfs-kernel-server
[sudo] password for wooledg:
* nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor prese
  Drop-In: /etc/systemd/system/nfs-server.service.d
   `-waitlonger.conf
   Active: active (exited) since Wed 2017-04-12 16:39:29 EDT; 6min ago
 Main PID: 513 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/nfs-server.service

Apr 12 16:39:29 wooledg systemd[1]: Starting NFS server and services...
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase
Apr 12 16:39:29 wooledg exportfs[510]: exportfs: Failed to resolve ebase-fla
Apr 12 16:39:29 wooledg systemd[1]: Started NFS server and services.

I attempted to work around this by creating a drop-in unit thing:

wooledg:~$ cat /etc/systemd/system/nfs-server.service.d/waitlonger.conf
[Unit]
Wants= network-online.target
After= network-online.target

But this didn't help.  With or without the drop-in thing, the exportfs
command fails at boot time.  If I login and manually run "exportfs -a"
or restart nfs-kernel-server (or nfs-server), then it's fine.

For now, I'm willing to entertain any kludge workarounds.  This is just
a desktop workstation.  But anyone experiencing this on a server may
want a more robust fix.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
151   udp  40904  mountd
151   tcp  50855  mountd
152   udp  53578  mountd
152   tcp  40253  mountd
153   udp  33327  mountd
153   tcp  47879  mountd
133   tcp   2049  nfs
134   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
134   udp   2049  nfs
1002273   udp   2049
1000211   udp  56937  nlockmgr
1000213   udp  56937  nlockmgr
1000214   udp  56937  nlockmgr
1000211   tcp  41093  nlockmgr
1000213   tcp  41093  nlockmgr
1000214   tcp  41093  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/home   ebase(ro,sync,no_subtree_check) ebase-fla(ro,sync,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs
/home   
ebase.eeg.ccf.org(ro,root_squash,sync,wdelay,no_subtree_check,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=1)
/home   
ebase-fla.eeg.ccf.org(ro,root_squash,sync,wdelay,no_subtree_check,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=1)
/   
ebase.eeg.ccf.org(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=390003:390004:390005:1)
/   
ebase-fla.eeg.ccf.org(ro,root_squash,sync,no_wdelay,no_subtree_check,v4root,fsid=0,uuid=57cd3d98:68de46b4:b8aded3c:8e2f7c10,sec=390003:390004:390005:1)

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-kernel-server depends on:
ii  init-system-helpers  1.47
ii  keyutils 1.5.9-9
ii  libblkid12.29.2-1
ii  libc62.24-9
ii  libcap2  1:2.25-1
ii  libsqlite3-0 3.16.2-3
ii  libtirpc10.2.5-1.1
ii  libwrap0 7.6.q-26
ii  lsb-base 9.20161125
ii  netbase  5.4
ii  nfs-common   1:1.3.4-2.1
ii  ucf  3.0036

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- debconf-show failed

Bug#781532: Acknowledgement (x2x: All key events received as keycode 204 (NoSymbol))

[Greg Wooledge]

FYI, the problem (all keyboard events received as NoSymbol) continues
for me in the stretch version of x2x (1.30-3).

Reinstalling my x2x_1.27.svn.20060501-4_amd64.deb package (and putting it
on hold) continues to be my only known workaround.

Bug#834770: manpages: console(4) missing

[Greg Wooledge]

Package: manpages
Version: 3.74-1
Severity: normal

The console(4) man page is missing.  Several other man pages in this
package refer to it.

It looks like the man page is not installed due to some conflict with
the old console-tools package which is no longer in Debian but may
still be installed on some people's systems.  The end result is that
anyone who *doesn't* have the old wheezy (or older) console-tools
doesn't get the man page at all.  That doesn't seem right


-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

manpages depends on no packages.

manpages recommends no packages.

Versions of packages manpages suggests:
ii  man-db [man-browser]  2.7.0.2-5

-- debconf-show failed

Bug#833925: Acknowledgement (nfs-kernel-server: no_root_squash broken on amd64)

[Greg Wooledge]

Additional information:

Changing the /etc/exports entry from this:

/home   -no_subtree_cheeck arc1(ro,no_root_squash,sync)

to this:

/home   arc1(ro,no_root_squash,sync,no_subtree_check)

works around the problem.  So apparently the actual underlying problem is
"on amd64 jessie, no_root_squash is broken in fields of lines that also
use -no_subtree_check".

And the workaround is to remove the -no_subtree_check option from every
line and add ",no_subtree_check" inside the parenthetical options of every
FIELD of every line.

This is extremely inconvenient, and a huge step backwards.  Having to
add ",sync" to every field of every line was already bad enough and
that's just 5 characters.  My /etc/exports is incredibly ugly now.
Thank god for vim's search-and-replace.

-- 
Greg Wooledge  |   "Truth belongs to everybody."
g...@wooledge.org  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |

Bug#833925: nfs-kernel-server: no_root_squash broken on amd64

[Greg Wooledge]

Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: normal

The no_root_squash option appears to work on i386, but not on amd64.

wooledg@wooledg:~$ grep '^[^#]' /etc/exports
/home   -no_subtree_check arc1(ro,no_root_squash,sync)

arc1:~# ls /net/hosts/wooledg/home/wooledg/.bash*
/net/hosts/wooledg/home/wooledg/.bash_history
/net/hosts/wooledg/home/wooledg/.bash_logout
/net/hosts/wooledg/home/wooledg/.bashrc
arc1:~# ls /net/hosts/wooledg/home/wooledg/Maildir
ls: cannot open directory /net/hosts/wooledg/home/wooledg/Maildir: Permission 
denied

This is somewhat similar to bug #492970, but it's architecture specific
and it appears to be on the server side, not the client side.  I've
confirmed with NFSv3 and NFSv4 mounts from other Debian systems, and
with an HP-UX client.

See also:
https://lists.debian.org/debian-user/2016/08/msg00245.html
https://lists.debian.org/debian-user/2016/08/msg00275.html

I filed the bug report from "wooledg" (my desktop box) because it has an
absolutely minimal configuration that still demonstrates the problem.
The real problem that I care about is on a server with many other exports
as well.  Same problem: jessie, amd64, no_root_squash is ignored.

Jessie i386 systems work fine.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  55248  status
1000241   tcp  48807  status
132   tcp   2049  nfs
133   tcp   2049  nfs
134   tcp   2049  nfs
1002272   tcp   2049
1002273   tcp   2049
132   udp   2049  nfs
133   udp   2049  nfs
134   udp   2049  nfs
1002272   udp   2049
1002273   udp   2049
1000211   udp  55895  nlockmgr
1000213   udp  55895  nlockmgr
1000214   udp  55895  nlockmgr
1000211   tcp  38500  nlockmgr
1000213   tcp  38500  nlockmgr
1000214   tcp  38500  nlockmgr
151   udp  43131  mountd
151   tcp  49060  mountd
152   udp  47185  mountd
152   tcp  49686  mountd
153   udp  52717  mountd
153   tcp  35670  mountd
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/home   -no_subtree_check arc1(ro,no_root_squash,sync)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-kernel-server depends on:
ii  libblkid1 2.25.2-6
ii  libc6 2.19-18+deb8u4
ii  libcap2   1:2.24-8
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libtirpc1 0.2.5-1
ii  libwrap0  7.6.q-25
ii  lsb-base  4.1+Debian13+nmu1
ii  nfs-common1:1.2.8-9
ii  ucf   3.0030

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- debconf-show failed

Bug#824793: mount.8: refers to package nfs-utils

[Greg Wooledge]

Package: mount
Version: 2.25.2-6
Severity: normal

In the "Mount options for nfs and nfs4" section, the mount(8) man page
says "nfs-utils package must be installed".  It should say nfs-common
instead.

-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mount depends on:
ii  libc6  2.19-18+deb8u4
ii  libmount1  2.25.2-6
ii  libselinux12.3-2
ii  libsmartcols1  2.25.2-6

mount recommends no packages.

Versions of packages mount suggests:
ii  nfs-common  1:1.2.8-9

-- debconf-show failed

Bug#812891: linux-image-3.16.0-4-686-pae: Fails to boot in 64 MB (out of memory)

[Greg Wooledge]

Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal

After upgrading this machine to Debian 8.3 (from Debian 8.2), the kernel
would not boot.  I wrote these messages down:

[time stamp]  Unpacking initramfs ...
  (bunch of stuff that scrolls by too quickly, followed by a stack trace)
[  2.726147] ---[ end Kernel panic - not syncing: Out of memory and no killable 
processes...

The machine has 64 MB of memory.  linux-image-3.16.0-4-686-pae (older
packages) did work previously.  I must be RIGHT on the edge of what the
kernel needs.

Fortunately the wheezy kernel was still installed, and I was able to boot
that one.  I've changed GRUB_DEFAULT to use that as a workaround.

I'm not sure whether this problem is actually caused by the kernel, or
some change in the initramfs.  But since using the older kernel DOES work,
this seems like the most likely place to report the problem.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge [8086:7190] (rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: agpgart-intel

00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP 
bridge [8086:7191] (rev 03) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
Reset- FastB2B+
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:04.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA 
[8086:7110] (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR-  [disabled]
Capabilities: 


** USB devices:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-3.16.0-4-686-pae depends on:
ii  debconf [debconf-2.0]   1.5.56
ii  initramfs-tools [linux-initramfs-tool]  0.120
ii  kmod18-3
ii  linux-base  3.5
ii  module-init-tools   18-3

Versions of packages linux-image-3.16.0-4-686-pae recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3
ii  libc6-i686   2.19-18+deb8u2

Versions of packages linux-image-3.16.0-4-686-pae suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02~beta2-22+deb8u1
pn  linux-doc-3.16  

Versions of packages linux-image-3.16.0-4-686-pae is related to:
pn  firmware-atheros
pn  firmware-bnx2   
pn  firmware-bnx2x  
pn  firmware-brcm80211  
pn  firmware-intelwimax 
pn  firmware-ipw2x00
pn  firmware-ivtv   
pn  firmware-iwlwifi
pn  firmware-libertas   
pn  firmware-linux  
pn  firmware-linux-nonfree  
pn  firmware-myricom
pn  firmware-netxen 
pn  firmware-qlogic 
pn  firmware-ralink 
pn  firmware-realtek
pn  xen-hypervisor  

-- debconf information:
  linux-image-3.16.0-4-686-pae/prerm/removing-running-kernel-3.16.0-4-686-pae: 
true
  linux-image-3.16.0-4-686-pae/postinst/mips-initrd-3.16.0-4-686-pae:
  linux-image-3.16.0-4-686-pae/postinst/depmod-error-initrd-3.16.0-4-686-pae: 
false

Bug#801144: tcl-expect: package require Expect fails

[Greg Wooledge]

Sergei Golovan (sgolo...@nes.ru) wrote:

> As far as I can see, you're using your own locally built Tcl which
> can't find the Tcl packages which come with Debian because they are
> placed in a different location.

titan:~$ strace -e open,fstat64 /usr/bin/tclsh8.6
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/usr/local/lib/libtcl8.6.so", O_RDONLY|O_CLOEXEC) = 3
[...]

This appears to be the real issue.  The locally installed tcl (using
the default prefix=/usr/local) drops a libtcl8.6.so in /usr/local/lib
and then ld.so/ldconfig caches it, so /usr/bin/tclsh8.6 uses it.

So I guess the fix is to manually remove the locally installed tcl
(very carefully!) and rebuild it with some other prefix.

-- 
Greg Wooledge  |   "Truth belongs to everybody."
g...@wooledge.org  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |

Bug#801144: tcl-expect: package require Expect fails

[Greg Wooledge]

Sergei Golovan (sgolo...@nes.ru) wrote:

> I can't reproduce the bug. For me 'package require Expect' loads the
> Expect package successfully.
> 
> Could you show the output of two commands in a tclsh8.6 session:
> 
> info patchlevel
> set auto_path
> 
> and also, could you look if there's some code which changes the
> auto_path variable in your ~/.tclshrc?

titan:~$ ls -ld .tcl*
ls: cannot access .tcl*: No such file or directory
titan:~$ env | grep TCL
titan:~$ /usr/bin/tclsh8.6
% info patchlevel
8.6.4
% set auto_path
/usr/local/lib/tcl8.6 /usr/local/lib /usr/lib
% package require Expect
can't find package Expect
% exit
titan:~$ ls -ld /usr/local/bin/tcl*
-rwxr-xr-x  1 root staff 13695 Apr 30 00:21 /usr/local/bin/tcldocstrip*
drwxr-sr-x 23 root staff  4096 Jul  6 14:42 /usr/local/bin/tcllib_examples1.17/
lrwxrwxrwx  1 root staff 8 Jul  6 13:07 /usr/local/bin/tclsh -> tclsh8.6*
-rwxr-xr-x  1 root staff  8272 Jul  6 13:07 /usr/local/bin/tclsh8.6*
titan:~$ ls -ld /usr/bin/tcl*
-rwxr-xr-x 1 root root 6168 Mar 17  2015 /usr/bin/tclsh8.6*
titan:~$ /usr/local/bin/tclsh8.6
% package require Expect
can't find package Expect
% info patchlevel
8.6.4
% set auto_path
/usr/local/lib/tcl8.6 /usr/local/lib /usr/local/lib/tcllib1.17


-- 
Greg Wooledge  |   "Truth belongs to everybody."
g...@wooledge.org  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |

Bug#801144: tcl-expect: package require Expect fails

[Greg Wooledge]

Package: tcl-expect
Version: 5.45-6
Severity: important

titan:~$ /usr/bin/tclsh8.6
% package require Expect
can't find package Expect

The pkgIndex file (/usr/lib/tcltk/x86_64-linux-gnu/expect5.45/pkgIndex.tcl)
seems OK, but tclsh isn't finding it.  It can be loaded by hand:

titan:~$ /usr/bin/tclsh8.6
% load [file join /usr lib x86_64-linux-gnu libexpect.so.5.45]
% package require Expect
5.45


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tcl-expect depends on:
ii  libc6  2.19-18+deb8u1
ii  libtcl8.6  8.6.2+dfsg-2

tcl-expect recommends no packages.

Versions of packages tcl-expect suggests:
ii  expect  5.45-6

-- debconf-show failed

Bug#798099: Me Too

[Greg Wooledge]

This probably has to be forwarded upstream, but yeah... xmms2-scrobbler
completely fails with last.fm after they changed whatever they changed.

It (still) works great with libre.fm.

-- 
Greg Wooledge  |   "Truth belongs to everybody."
g...@wooledge.org  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |

Bug#788303: systemd hangs on shutdown, swap related

[Greg Wooledge]

I am having what appears to be the same problem.  One of my i386
systems (a very old one) was upgraded to jessie, and whenever I do
a shutdown -r now or press Ctrl-Alt-Del on the console, it hangs
at Reached target Shutdown.

I enabled the systemd debug shell, and systemctl list-jobs during the
hang gives this:

JOB UNIT   TYPE  STATE  
525 reboot.target  start waiting
526 systemd-reboot.service start waiting
622 umount.target  start waiting
624 dev-disk-by\x2did-wwn\x2d0x5000cca325f1d454\x2dpart2.swap  stop  running
625 dev-disk-by\x2did-at...1616PLAT80_PV6904Z23JM4LN\x2dpart2.swap stop  running
626 dev-sda2.swap  stop  running
632 final.target   start waiting

If I type swapoff /dev/sda2 in the debug shell, the reboot continues
to completion, so the swap partition is definitely where it's getting
stuck.

There's nothing special about this computer, as far as I know.
No encrypted file systems, no LVM.  It has very limited RAM (64 MB),
so the swap is really used.  The disk is IDE, not SATA, because the
machine is just that old.

Here is the disk (there is only one):

# fdisk -l

Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000849bc

Device BootStart   End   Sectors   Size Id Type
/dev/sda1 63  19535039  19534977   9.3G 83 Linux
/dev/sda2   19535040  21494969   1959930   957M 82 Linux swap / Solaris
/dev/sda3   21494970  60565049  39070080  18.6G 83 Linux
/dev/sda4   60565050 312576704 252011655 120.2G 83 Linux

Here's /etc/fstab:

# cat /etc/fstab
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
# /dev/hda1   /   ext3defaults,errors=remount-ro 0   1
UUID=a748f137-7898-4238-a1aa-7615d3c93932   /   ext3
defaults,errors=remount-ro 0   1
# /dev/hda3   /var/qmail/queue  ext2sync,noatime0   2
UUID=33359184-c7f0-4986-919a-2bd976fd9d20   /var/qmail/queue  ext2  
sync,noatime0   2
# /dev/hda4   /home   ext3defaults0   2
UUID=f9c2e8fa-7e5a-4cbe-bc29-63813bfdaf67   /home   ext3
defaults0   2
# /dev/hda2   noneswapsw  0   0
UUID=29061e22-60fa-449a-a1c6-41e352b4f3d8   noneswapsw  
0   0
# /dev/hdc/media/cdrom0   iso9660 ro,user,noauto  0   0
/dev/cdrom/media/cdrom0   iso9660 ro,user,noauto  0   0
/dev/fd0/media/floppy0  autorw,user,noauto  0   0


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

Bug#781532: Acknowledgement (x2x: All key events received as keycode 204 (NoSymbol))

[Greg Wooledge]

FYI, the one-line patch suggested in the upstream bug report does NOT
work for me.  It makes key events come across, but as the wrong keys.
E.g. pressing 'z' on the HP-UX keyboard makes ']' appear on the Debian
terminal, Ctrl makes 'e' appear and so on.


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

Bug#781532: x2x: All key events received as keycode 204 (NoSymbol)

[Greg Wooledge]

Package: x2x
Version: 1.30-2
Severity: normal
Tags: upstream

I have been using x2x between my HP-UX workstation and my dual-boot
Debian box for a while.  Today I upgraded to jessie, and x2x keyboard
events stopped working entirely.  Some Google searches led me to this
page, which describes the problem in the upstream bug tracker:

https://github.com/dottedmag/x2x/issues/9

I have the same symptom described in that bug: all key events sent
from the HP-UX workstation's keyboard are received as keycode 204
(NoSymbol) on the Debian system running x2x, as confirmed by xev.

Here is my exact invocation from the HP-UX workstation:

ssh -f -X wooledg x2x -west -to :0 -resurface

where wooledg is the Debian system's hostname.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages x2x depends on:
ii  libc6 2.19-15
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxtst6  2:1.2.2-1+b1

x2x recommends no packages.

x2x suggests no packages.

-- debconf-show failed


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

Bug#747195: Incorrect filename in NEWS.Debian.gz

[Greg Wooledge]

php5-fpm package file NEWS.Debian.gz says The default Debian setup now
correctly sets the listen.owner and listen.group to www-data:www-data
in default php-fpm.conf.

However, the correct filename is actually /etc/php5/fpm/pool.d/www.conf .


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

Bug#695048: installation-reports: Must manually reboot into non-EFI mode

[Greg Wooledge]

Package: installation-reports
Severity: normal

Dear Maintainer,
   * What led up to the situation?

The machine was delivered to me with Windows XP Professional installed, and
I must keep that on the machine, and bootable.  So I booted the DVD, selected
manual partitioning, and shrunk the NTFS partition.

In the free space left over, I created a swap partition, and then an ext4
partition for the root file system.

The installed told me there was No EFI partition found.  This was greatly
confusing as it is the first time I have ever heard of EFI, and I had no
way to know what I was supposed to do about it, if anything.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Following advice from IRC, I rebooted the machine and found a BIOS option
to disable booting the DVD in EFI mode.  With that disabled, the DVD
would be forced to boot in Legacy mode.  (This BIOS did not allow me
to rearrange the order of those options, so disabling EFI was the only
choice.)

   * What was the outcome of this action?

I rebooted the installation DVD again, and this time got a different menu.
I created the same swap and ext4 partitions in the free space, and this
time the installation proceeded without any confusing messages about EFI.

   * What outcome did you expect instead?

09:36  babilen greycat: Anyway, it sounds as if you are on the right track. I 
would consider this a bug/problem with the installer btw 
(forcing GPT when started via EFI even if disk is using MBR)
09:36  babilen greycat: Would you mind filing a bugreport/installation report 
after you are done with the installation?


-- Package-specific info:

Boot method: CD
Image version: debian-wheezy-DI-b4-amd64-netinst.iso (Nov 18 mtime)
Date: Date and time of the install

Machine: HP Compaq Elite 8300 Small Form Factor
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [E]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

The installation went well except for the EFI/Legacy boot mode issue
described above.  Once I knew that I had to boot the DVD in Legacy
mode, everything worked.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7.0 (wheezy) - installer build 20121114
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux wooledg 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd 
Gen Core processor DRAM Controller [8086:0150] (rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon 
E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 
Series Chipset Family KT Controller [8086:1e3d] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection [8086:1502] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:3397]

Bug#162749: gawk: fatal internal error during popularity-contest

[Greg Wooledge]

Jeroen Schot (sc...@a-eskwadraat.nl) wrote:

 On Sun, Sep 29, 2002 at 09:02:42AM -0400, Greg Wooledge wrote:
  /etc/cron.weekly/popularity-contest:
  gawk: cmd. line:17: (FILENAME=- FNR=353) fatal error: internal error
 
 I understand that given the age of this bug (almost 9 years) it is
 very unlikely that this is available. If this is the case and you
 haven't seen this error afterwards we better close this bug.

The error is not occurring any more, so I agree.

-- 
Greg Wooledge  |   Truth belongs to everybody.
g...@wooledge.org  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |



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

Bug#628048: xmms2-scrobbler: No warning of incompatible upgrade

[Greg Wooledge]

Package: xmms2-scrobbler
Version: 0.4.0-1+b1
Severity: normal

When upgrading xmms2-scrobbler there is no warning that the configuration
files in users' home dirs need to be changed manually.  Shouldn't there
be a NEWS.Debian.gz file or something announcing the steps that must be
taken?


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

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

Versions of packages xmms2-scrobbler depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libcurl3  7.21.0-1   Multi-protocol file transfer libra
ii  libxmmsclient60.7DrNo+dfsg-2 XMMS2 - client library

xmms2-scrobbler recommends no packages.

Versions of packages xmms2-scrobbler suggests:
ii  xmms2-core0.7DrNo+dfsg-2 XMMS2 - core package

-- debconf-show failed



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

Bug#625738: 2TB SCSI disk size not recognized correctly

[Greg Wooledge]

Package: linux-image-2.6.32-5-686
Version: 2.6.32-31

I upgraded a machine from Lenny to Squeeze, and it failed to mount one
of the disks.  Here is a large swath of dmesg from the failing kernel:

[0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-31) 
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 
21:36:00 UTC 2011

...

[3.914558] scsi 4:0:0:0: Direct-Access   R0.0 
PQ: 0 ANSI: 5
[3.914564] scsi 4:0:0:0: Information Units disabled by blacklist
[3.914576] scsi target4:0:0: Beginning Domain Validation
[3.914594] scsi5 : ioc1: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, 
IRQ=18
[4.566692] scsi target4:0:0: Ending Domain Validation
[4.566756] scsi target4:0:0: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, 
offset 127)
[5.728614] scsi 4:0:5:0: Sequential-Access CERTANCE ULTRIUM 31770 
PQ: 0 ANSI: 4
[5.728625] scsi target4:0:5: Beginning Domain Validation
[6.058280] scsi target4:0:5: Domain Validation skipping write tests
[6.058283] scsi target4:0:5: Ending Domain Validation
[6.058345] scsi target4:0:5: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, 
offset 127)
[8.310955] scsi 3:0:0:0: Direct-Access ATA  SEAGATE ST32500N n/a  
PQ: 0 ANSI: 5
[8.325016] sd 2:0:0:0: [sda] 488390625 512-byte logical blocks: (250 GB/232 
GiB)
[8.325071] sd 2:0:0:0: [sda] Write Protect is off
[8.325075] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[8.325098] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.325233]  sda:
[8.332152] sd 3:0:0:0: [sdc] 488390625 512-byte logical blocks: (250 GB/232 
GiB)
[8.332201] sd 3:0:0:0: [sdc] Write Protect is off
[8.332204] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[8.332225] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.332365]  sdc:
[8.332488] st: Version 20081215, fixed bufsize 32768, s/g segs 256
[8.09] st 4:0:5:0: Attached scsi tape st0
[8.12] st 4:0:5:0: st0: try direct i/o: yes (alignment 512 B)
[8.343674] sd 4:0:0:0: [sdb] 4294967296 512-byte logical blocks: (2.19 
TB/2.00 TiB)
[8.344551] usbcore: registered new interface driver hiddev
[8.344741] sd 4:0:0:0: [sdb] Write Protect is off
[8.344745] sd 4:0:0:0: [sdb] Mode Sense: bf 00 00 08
[8.345180] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.345421]  sda1 sda2
[8.345672] sd 2:0:0:0: [sda] Attached SCSI disk
[8.345973] sd 4:0:0:0: [sdb] 13651132416 512-byte logical blocks: (6.98 
TB/6.35 TiB)
[8.347305] sdb: detected capacity change from 219902322 to 6989379796992
[8.347310]  sdb:
[8.348685] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.348837] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.348986] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.349135] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.349286] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.349435] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.349442] sd 4:0:0:0: [sdb] Unhandled error code
[8.349444] sd 4:0:0:0: [sdb] Result: hostbyte=DID_SOFT_ERROR 
driverbyte=DRIVER_OK
[8.349449] sd 4:0:0:0: [sdb] CDB: Read(16): 88 00 00 00 00 03 2d ab bf f8 
00 00 00 08 00 00
[8.349461] end_request: I/O error, dev sdb, sector 13651132408
[8.349520] Buffer I/O error on device sdb, logical block 1706391551
[8.349732] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.349886] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.350046] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.350196] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.350347] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.350497] Errataon LSI53C1030 occurred.sc-req_bufflen=0x1000,xfer_cnt=0x00
[8.350503] sd 4:0:0:0: [sdb] Unhandled error code
[8.350505] sd 4:0:0:0: [sdb] Result: hostbyte=DID_SOFT_ERROR 
driverbyte=DRIVER_OK
[8.350509] sd 4:0:0:0: [sdb] CDB: Read(16): 88 00 00 00 00 03 2d ab bf f8 
00 00 00 08 00 00
[8.350520] end_request: I/O error, dev sdb, sector 13651132408
[8.350576] Buffer I/O error on device sdb, logical block 1706391551
[8.350639] Alternate GPT is invalid, using primary GPT.
[8.350642]  sdb1
[8.353476]  sdc1 sdc2
[8.353538] input: Virtual USB MULTIMEDIA KEYBOARD as 
/devices/pci:00/:00:02.0/usb2/2-1/2-1:1.0/input/input0
[8.353610] generic-usb 0003:0B38:0003.0001: input,hidraw0: USB HID v1.10 
Keyboard [Virtual USB MULTIMEDIA KEYBOARD] on usb-:00:02.0-1
/input0
[8.353792] sd 3:0:0:0: [sdc] Attached SCSI disk
[8.363449] input: Virtual USB MULTIMEDIA KEYBOARD as 

Bug#598493: squeeze workaround

[Greg Wooledge]

Changing allow-hotplug eth0 to auto eth0 in /etc/network/interfaces
appears to work around the problem in squeeze.  I do not quite understand
why that works, though.



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

Bug#598493: still broken in squeeze release

[Greg Wooledge]

nfs-common 1:1.2.2-4
nfs-kernel-server 1:1.2.2-4
portmap 6.0.0-2

I'm seeing this issue -- or what appears to be the same issue -- on a
machine that was upgraded from lenny to squeeze.  Specifically, the
export list is empty immediately after booting:

img2:/# shutdown -r now

...

imadev:~$ ssh root@img2
root@img2's password: 
Linux img2 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 2011 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Feb 17 08:53:50 2011 from imadev.eeg.ccf.org
img2:~# showmount -e
Export list for img2:
img2:~# 


I have bootlogd enabled, and it appears to be running an exportfs -a:

Thu Feb 17 09:05:35 2011: INIT: Entering runlevel: 2
Thu Feb 17 09:05:35 2011: Using makefile-style concurrent boot in runlevel 2.
Thu Feb 17 09:05:35 2011: Starting portmap daemon...Already running..
Thu Feb 17 09:05:35 2011: Starting NFS common utilities: statd idmapd.
Thu Feb 17 09:05:36 2011: Exporting directories for NFS kernel 
daemon...exportfs: /etc/exports [1]: Neither 'subtree_check' or 
'no_subtree_check' specified for export jabba.eeg.ccf.org:/data1.
Thu Feb 17 09:05:36 2011:   Assuming default behaviour ('no_subtree_check').
Thu Feb 17 09:05:36 2011:   NOTE: this default has changed since nfs-utils 
version 1.0.x
Thu Feb 17 09:05:36 2011: 
Thu Feb 17 09:05:36 2011: exportfs: jabba.eeg.ccf.org has non-inet addr
Thu Feb 17 09:05:36 2011: exportfs: jabba.eeg.ccf.org has non-inet addr


It's giving me that non-inet addr error on every host.  So, I guess
name lookups are failing -- but I don't understand why.  It uses other
machines on the network for DNS, and that's all configured properly:

img2:~# grep host /etc/nsswitch.conf 
hosts:  files dns


img2:~# cat /etc/hosts
127.0.0.1   localhost
127.0.1.1   img2.eeg.ccf.orgimg2
10.76.143.59img2.eeg.ccf.orgimg2 boba

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


img2:~# cat /etc/resolv.conf
domain eeg.ccf.org
search eeg.ccf.org
nameserver 10.76.142.43
nameserver 10.76.142.84
nameserver 10.88.22.37


If I manually run exportfs -a after logging in, then NFS works properly
(although showmount's output is still wrong -- I'll file a separate bug
for that).



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

Bug#568194: I got bit by it

[Greg Wooledge]

We have a heterogeneous network of systems here, including many
HP-UX 10.20 workstations, with a lot of NFS cross-mounting.  After
upgrading a machine from lenny to squeeze, one of the very first
problems I encountered was that it failed to automount my home directory.

Eventually (with some suggestions from #debian@freenode) we traced it down
to an NFSv4 issue.  Apparently when autofs attempts an NFS mount in
squeeze, it attempts an NFSv4 mount.  And when it does this against an
HP-UX 10.20 NFS server, the result is a client that hangs for a few
minutes before finally failing (no, it does not seem to fall back to NFSv3
or anything else).

The configuration I had on the squeeze client *was* this:

arc3:~$ cat /etc/auto.master
#
# $Id: auto.master,v 1.4 2005/01/04 14:36:54 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc  /etc/auto.misc --timeout=60
#/smb   /etc/auto.smb
#/misc  /etc/auto.misc
#/net   /etc/auto.net
/nfs/etc/auto.net

In other words, just like it had been doing for the past several years,
it retrieved the auto.master map from NIS and used that to populate
the auto.home map which tells where everyone's home directories are.

arc3:~$ ypcat -k auto.master
/net/vol auto.vol   -rw,hard,intr
/net/appl auto.appl -rw,hard,intr
/net/hosts -hosts   -rw,hard,intr
/net/home auto.home -rw,hard,intr

But now in squeeze, apparently that is broken.  I had to manually slurp
the auto.master map information into the /etc/auto.master file and
tweak it:

arc3:~$ cat /etc/auto.master
#
# $Id: auto.master,v 1.4 2005/01/04 14:36:54 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc  /etc/auto.misc --timeout=60
#/smb   /etc/auto.smb
#/misc  /etc/auto.misc
#/net   /etc/auto.net
/nfs/etc/auto.net

# Contents of auto.master map, then add mountvers=3
/net/vol auto.vol   -rw,hard,intr,mountvers=3
/net/appl auto.appl -rw,hard,intr,mountvers=3
/net/hosts -hosts   -rw,hard,intr,mountvers=3
/net/home auto.home -rw,hard,intr,mountvers=3

This suffices as a workaround, for us, but is this really the intent?

Also I agree with Nick Leverton that the documentation is wrong or at
least confusing.  My initial diagonsis attempts began by comparing
the results of mount -t nfs ... and mount -t nfs4 ... because the
documentation said that these two options should give different behaviors.
But they do not.



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

Bug#613828: nfs-kernel-server: export list shows only one host

[Greg Wooledge]

Package: nfs-kernel-server
Version: 1:1.2.2-4
Severity: normal

The export list (from rpc.mountd) shows only one host, even when a file
system has been exported to many hosts.

img2:~# showmount -e
Export list for img2:
/data2 jabba.eeg.ccf.org
/data1 jabba.eeg.ccf.org

img2:~# grep /data1 /etc/exports
/data1  jabba.eeg.ccf.org(rw,sync,no_root_squash) 
yoda.eeg.ccf.org(rw,sync,no_root_squash) ...


It's not a problem in showmount, because I get the same results when I
query remotely from a completely different system:

imadev:~$ uname -a
HP-UX imadev B.10.20 A 9000/785 2008897791 two-user license
imadev:~$ /usr/sbin/showmount -e img2
export list for img2:
/data2 jabba.eeg.ccf.org
/data1 jabba.eeg.ccf.org

And that client, doing a showmount against a lenny box, does not truncate:

imadev:~$ /usr/sbin/showmount -e svr1a
export list for svr1a:
/cdrom @ccf_adm,@ccf_vue
/opt/app   @ccf_acq,@ccf_vue,@ccf_dvlp
...

And the squeeze client also works fine against the lenny box:

img2:~# showmount -e svr1a
Export list for svr1a:
/cdrom @ccf_adm,@ccf_vue
/opt/app   @ccf_acq,@ccf_vue,@ccf_dvlp
...


-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.iso88591, LC_CTYPE=en_US.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1   2.17.2-9 block device id library
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  libcomerr2  1.41.12-2common error description library
ii  libgssapi-krb5-21.8.3+dfsg-4 MIT Kerberos runtime libraries - k
ii  libgssglue1 0.1-4mechanism-switch gssapi library
ii  libk5crypto31.8.3+dfsg-4 MIT Kerberos runtime libraries - C
ii  libkrb5-3   1.8.3+dfsg-4 MIT Kerberos runtime libraries
ii  libnfsidmap20.23-2   An nfs idmapping library
ii  librpcsecgss3   0.19-2   allows secure rpc communication us
ii  libwrap07.6.q-19 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  nfs-common  1:1.2.2-4NFS support files common to client
ii  ucf 3.0025+nmu1  Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server 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#581339: Me too (FD warning spam in crontab)

[Greg Wooledge]

I'm getting these as well.  It's rather annoying to get these spurious
warnings every day from an otherwise-working backup script.  I am NOT
going to try the udisks thing from that Red Hat error report, because
it's a report for a totally different symptom (lvremove is failing in
that report, not spamming a warning).

Linux ebase-adm 2.6.32-5-amd64 #1 SMP Thu Nov 25 18:02:11 UTC 2010 x86_64 
GNU/Linux

ii  lvm2   2.02.66-4  The Linux Logical Volume Manager

Here's the crontab line:

15 18 * * * /usr/local/sbin/backup ebase-adm/ebase

And here's the script:
=
#!/bin/bash

# Usage: backup LVname

# Backup script for Ebase VMs.
#  1) This should ideally be run *after* the database backup has completed.
#  2) Make a snapshot of the LV the virtual machine uses for storage.
#  3) Mount the first partition of that LV on /snap.
#  4) Tar it up, or something.
#  5) Unmount, and remove the snapshot LV.

export PATH=/usr/sbin:/sbin:/usr/bin:/bin

usage() {
echo usage: backup LVname
exit 1
}

[[ $1 ]] || usage
[[ ! -e $1  ! -e /dev/$1 ]]  usage
mkdir -p /snap || exit 1

trap 'cd /; umount /snap; lvremove -f ebase-adm/snap; exit 1' 1 2 3 15
lvcreate -L 8G -n snap -s $1 || exit 1

# The file system partition begins at byte offset 32256 within the LV.
mount -o loop,ro,offset=32256 /dev/ebase-adm/snap /snap

cd /snap  rsync -a . /backup/${1//\//_}/

cd /
umount /snap
lvremove -f ebase-adm/snap
=

And here's the email from cron:

- Forwarded message from Cron Daemon r...@eeg.ccf.org -

Delivered-To: wool...@imadev.eeg.ccf.org
Delivered-To: wool...@eeg.ccf.org
X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on gateway.eeg.ccf.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00
autolearn=ham version=3.3.0
Delivered-To: r...@eeg.ccf.org
Date: Wed, 01 Dec 2010 18:15:11 -0500
From: r...@eeg.ccf.org (Cron Daemon)
To: r...@eeg.ccf.org
Subject: Cron r...@ebase-adm /usr/local/sbin/backup ebase-adm/ebase
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: HOME=/root
X-Cron-Env: PATH=/usr/bin:/bin
X-Cron-Env: LOGNAME=root

File descriptor 5 (/tmp/tmpf7ksQyy (deleted)) leaked on lvcreate invocation. 
Parent PID 4718: /bin/bash
  Logical volume snap created
File descriptor 5 (/tmp/tmpf7ksQyy (deleted)) leaked on lvremove invocation. 
Parent PID 4718: /bin/bash
  Logical volume snap successfully removed

- End forwarded message -



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

Bug#603087: amd64 squeeze install success - Dell R815

[Greg Wooledge]

Package: installation-reports

Boot method: CD (squeeze beta 1 netinst)
Image version: 
http://cdimage.debian.org/cdimage/squeeze_di_beta1/amd64/iso-cd/debian-squeeze-di-beta1-amd64-netinst.iso
Date: 2010-11-10

Machine: Dell PowerEdge R815
Processor: multiple Opteron 6128
Memory: 4 GB
Partitions: defaults using guided LVM, but I'm modifying them

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: ATI Technologies Inc RD890 PCI to PCI bridge 
(external gfx0 port A) [1002:5a13] (rev 02)
Subsystem: Dell Device [1028:0445]
00:02.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI 
express gpp port B) [1002:5a16]
Kernel driver in use: pcieport
00:03.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI 
express gpp port C) [1002:5a17]
Kernel driver in use: pcieport
00:04.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI 
express gpp port D) [1002:5a18]
Kernel driver in use: pcieport
00:09.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI 
express gpp port H) [1002:5a1c]
Kernel driver in use: pcieport
00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA 
Controller [IDE mode] [1002:4390]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ahci
00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 
Controller [1002:4397]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ohci_hcd
00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller 
[1002:4398]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ohci_hcd
00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI 
Controller [1002:4396]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ehci_hcd
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 
Controller [1002:4397]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ohci_hcd
00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller 
[1002:4398]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ohci_hcd
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI 
Controller [1002:4396]
Subsystem: Dell Device [1028:0445]
Kernel driver in use: ehci_hcd
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] 
(rev 3d)
Subsystem: Dell Device [1028:0445]
Kernel driver in use: piix4_smbus
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller 
[1002:439d]
Subsystem: Dell Device [1028:0445]
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge 
[1002:4384]
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
HyperTransport Configuration [1022:1200]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Address Map [1022:1201]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
DRAM Controller [1022:1202]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Miscellaneous Control [1022:1203]
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Link Control [1022:1204]
00:19.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
HyperTransport Configuration [1022:1200]
00:19.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Address Map [1022:1201]
00:19.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
DRAM Controller [1022:1202]
00:19.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Miscellaneous Control [1022:1203]
00:19.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Link Control [1022:1204]
00:1a.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
HyperTransport Configuration [1022:1200]
00:1a.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Address Map [1022:1201]
00:1a.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
DRAM Controller [1022:1202]
00:1a.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Miscellaneous Control [1022:1203]
00:1a.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Link Control [1022:1204]
00:1b.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
HyperTransport Configuration [1022:1200]
00:1b.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Address Map [1022:1201]
00:1b.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
DRAM Controller [1022:1202]
00:1b.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Miscellaneous Control [1022:1203]
00:1b.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor 
Link Control [1022:1204]
01:00.0 Ethernet 

Bug#426990: 'test' builtin of bash returns wrong value for '! -a FILE' operation

[Greg Wooledge]

On Tue, Nov 09, 2010 at 08:29:15PM +0900, OZAKI Masanobu wrote:
 Greg Wooledge wool...@eeg.ccf.org wrote:
  (On my system, there is no -a unary operator in the test(1) man page, but
  the command apparently supports one, undocumented.  Isn't this fun?)
 
 Neither on my system.  I found descriptions of the -a unary operator
 in the output of help test output and ksh(1) man page.
 According to Solaris 7's test(1) page
 (http://docs.sun.com/app/docs/doc/805-3172/6j31br5p3?l=ena=view),
 which summarizes variations of test command, I guess this is ksh origin
 and influenced (or polluted?:) /bin/test and bash.

It's difficult to figure out who first introduced an extension.  Most
of these things predate POSIX, and were extensions to either SVID or
BSD standards.  POSIX had the unenviable job of deciding which features
were common enough to mark as standard and which were not.

On a different note, that man page is rather dodgy.  It says

  /usr/bin/test [condition]

and then

  if condition ; then action ; fi

Are they saying that Solaris's sh would accept this?

  if -d /etc; then echo good, you have /etc; fi

That's what it LOOKS like it's saying, but surely that can't be right

 I found the
 inconsistency between bash-builtin and GNU shell util's test commands when
 porting a ksh script to bash in order to avoid a ksh's bug that randomly
 occurred on Scientific Linux.

It's easier to port a shell than a shell script. -- Larry Wall



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

Bug#426990: 'test' builtin of bash returns wrong value for '! -a FILE' operation

[Greg Wooledge]

On Fri, Nov 05, 2010 at 04:24:23PM -0500, Jonathan Nieder wrote:
  Please try
% bash -c 'test ! -a .  echo true'
  and compare with the result of
% bash -c '/usr/bin/test ! -a .  echo true'

imadev:~$ bash -c 'test ! -a .  echo true'
true
imadev:~$ bash -c '/usr/bin/test ! -a .  echo true'
imadev:~$ 

This is an extremely convoluted example.  You're echoing true if the
object does NOT exist...?  Actually, you're echoing true if the command
fails to fail.  In the /usr/bin/test -a case, the command has the right to
fail because there's no such unary operator (see below), regardless of
whether . exists in the file system.

(On my system, there is no -a unary operator in the test(1) man page, but
the command apparently supports one, undocumented.  Isn't this fun?)

  So which one is right?
 
  Both should echo true, but the former did not: I found that the former
  sometimes returns the correct result, but have not found what makes the
  difference.

POSIX does not specify -a as a unary operator.  See
http://www.opengroup.org/onlinepubs/9699919799/utilities/test.html
for details.  It specifies -a as a binary operator, but marks it as
obsolescent and suggests using two test commands instead.  This is the
same advice I give whenever the subject comes up on IRC, and also what
I mention on my pitfalls page: http://mywiki.wooledge.org/BashPitfalls#pf6

 Suggested changes:
[...]

I'll let Chet address those.  Speaking strictly as someone who supports
script writers (not shell maintainers), I'd suggest either using bash's [[
command instead of test, or avoiding the use of -a and -o in the test
command.  (Note that [[ uses  rather than -a, and || rather than -o.
So whichever advice path you choose, -a and -o as binary operators are
just plain bad.)

If you're trying to determine whether some file-object exists, use -e.

imadev:~$ bash -c 'test ! -e .  echo true'
imadev:~$ bash -c '/usr/bin/test ! -e .  echo true'
imadev:~$ 

If you're trying to run multiple tests, use multiple test commands,
and string them together with  and/or || as required.

imadev:~$ bash -c 'if test -e .  test -e ..; then echo true; fi'
true
imadev:~$ bash -c 'if /usr/bin/test -e .  /usr/bin/test -e ..; then echo 
true; fi'
true

Or use [[:

imadev:~$ bash -c 'if [[ -e .  -e .. ]]; then echo true; fi'
true



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

Bug#566844: failure in NIS setup

[Greg Wooledge]

I tried sending this two weeks ago, but it bounced back with a CNAME
lookup failure.  This will be my third attempt to send it (now with a
qmail patch applied -- I hope it's the right one...).

However, I learned a thing or two after the original message was sent,
which also need to be mentioned.

The original message:

 I ran into this bug on a standard NIS setup.  Googling the error
 message led me to this, from 2003:
 
 http://www.mail-archive.com/debian-u...@lists.debian.org/msg53003.html
 
 Specifically, this part:
 
   The 'compat' option no longer works, you need
 
   passwd: files nis
   group:  files nis
   shadow: files nis
 
   In your nsswitch.conf instead.
 
 Making that change fixed it for me.  Or at least, I no longer get the
 (ignored) error message when I su from root down to the user's account.
 The user's out to lunch, so she can't test it directly on the console
 at the moment (which was the original situation I was trying to fix).
 
 In the interest of full disclosure, this lenny box is quite a bit behind
 on its security updates.  I tried updating libc6, but that didn't help.

As it turns out, making the passwd: files nis change to nsswitch.conf
broke the ability to use +username::/other/shell in the local
passwd file to override the NIS-defined shell.

So, I had to change nsswitch back to passwd: compat and then find a
different workaround for the can't login at all problem.

It turns out, Debian is much more sensitive to the +:: line that
goes at the end of passwd than Unix systems are (or at least, it is
when it's using compat instead of nis).  On our Unix systems, we
have things like +::-24:-24::: at the end of /etc/passwd, and it's
always worked fine (I don't have a clue where the -24 came from).

On the Debian system, something changed the line to +::0:0:::.  I'm
not 100% sure, but I think it might have been an adduser command (there
is a whole group of people who have the root password, not just me --
I know that one of them attempted to add a user locally, and then
removed it later, but I don't know if that was what caused the change).

Long story short, +::0:0::: doesn't allow people to login (PAM refuses
to consult the NIS maps, it appears), but +:: works.  Similarly,
on the shell-override lines, +username::0:0:::/shell does not work,
while +username::/shell does.

Meanwhile, *something* was putting +::0:0::: in the file, though I
don't know whether that was a Debian program, or a direct human edit.

I hope someone finds this information useful.



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

Bug#457971: ethtool: fails to detect or set duplex correctly (tg3)

[Greg Wooledge]

On Sun, May 30, 2010 at 02:41:49PM +0200, Moritz Muehlenhoff wrote:
 Hi,
 The next release of Debian (6.0, code name Squeeze) will be based
 on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
 us whether the problem persists. If so, we should report it upstream
 to the kernel.org developers.

Some time after I filed this bug report, I learned that it requires
a non-obvious invocation to make ethtool actually set the duplex.
Instead of ethtool -s eth0 duplex full one must type out all of
ethtool -s autoneg off speed 100 duplex full to get it to work.

Here are my results on 2.6.32.  I commented out the duplex-setting
commands in /etc/network/interfaces and rebooted on the new kernel.

img2:~# uname -a
Linux img2 2.6.32-3-686 #1 SMP Thu Feb 25 06:14:20 UTC 2010 i686 GNU/Linux
img2:~# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok

This is normal for this machine.  The way the network switch is set up,
autonegotiation detects the speed correctly (100) but the duplex
incorrectly (should be full, detects half).

(I actually did a few mii-tool and ethtool commands prior to this, so
you're not seeing the *completely* virgin mii-tool output.  Sorry about
that.  But it's very similar, I promise.)

Next, trying to set the duplex:

img2:~# mii-tool -F 100baseTx-FD eth0
img2:~# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
img2:~# ethtool eth0 | grep -i duplex
Duplex: Half

mii-tool no longer works to set the duplex on 2.6.32.  OK, fair enough.

img2:~# ethtool -s eth0 duplex full
Cannot set new settings: Invalid argument
  not setting duplex

This error is new, and very welcome.  If the invocation is incorrect, I'd
rather be told there's an error.  (It might be nice if it said something
like You must include `autoneg off' and `speed' when setting `duplex',
but that's wishlist material.)

img2:~# ethtool -s eth0 autoneg off speed 100 duplex full
img2:~# mii-tool eth0
eth0: 100 Mbit, full duplex, link ok
img2:~# ethtool eth0 | grep -i duplex
Duplex: Full

With the full invocation, ethtool is able to set the duplex correctly,
and report it correctly; mii-tool is also able to report it correctly,
even though it failed to set it.

Speed-testing with FTP:

...
226 Transfer complete.
2903540 bytes sent in 0.83 secs (3431.0 kB/s)

So the duplex is in fact correct.



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

Bug#557819: tdb-tools: no documentation

[Greg Wooledge]

Package: tdb-tools
Version: 1.1.2~git20080615-1
Severity: normal

tdb-tools includes absolutely no documentation whatsoever.  There is no 
man page for any of the commands, and there is nothing in 
/usr/share/doc/tdb-tools/.



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

Bug#530808: xmms2: should conflict with older xmms2-client-cli

[Greg Wooledge]

Package: xmms2
Version: 0.6DrMattDestruction-1
Severity: normal


After upgrading xmms2 and xmms2-core, I couldn't play any music with
xmms2, nor could I add songs to it, nor could I get lists of anything
it's playing.

griffon:~$ xmms2 list
Log output will be stored in /home/greg/.cache/xmms2/xmms2d.log
startup failed!
ERROR: Could not connect to xmms2d: Bad protocol version

Looks like it tried to start another daemon.  But I didn't tell it to!
I'm not doing anything funny either:

griffon:~$ type xmms2
xmms2 is hashed (/usr/bin/xmms2)

Hmm, what's this?

Versions of packages xmms2 depends on:
ii  xmms2-client-cli  0.5DrLecter-2.1XMMS2 - cli client
ii  xmms2-core0.6DrMattDestruction-1 XMMS2 - core package
ii  xmms2-plugin-alsa 0.6DrMattDestruction-1 XMMS2 - ALSA output
ii  xmms2-plugin-id3v 0.6DrMattDestruction-1 XMMS2 - ID3v2 plugin
ii  xmms2-plugin-mad  0.6DrMattDestruction-1 XMMS2 - libmad based mp3 decoder
ii  xmms2-plugin-vorb 0.6DrMattDestruction-1 XMMS2 - vorbis decoder

griffon:~$ sudo apt-get install xmms2-client-cli
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  libxmmsclient-glib1 libxmmsclient-ruby1.8 libxmmsclient5
The following packages will be REMOVED:
  abraca gxmms2 libxmmsclient4
...

Well, I don't want that.  I use gxmms2 for displaying the activitity of
the daemon.

griffon:~$ sudo apt-get install xmms2-client-cli gxmms2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
gxmms2 is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  xmms2-client-cli: Depends: libxmmsclient-glib1 (= 0.6DrMattDestruction) but 
0.5DrLecter-2 is to be installed
Depends: libxmmsclient5 (= 0.6DrMattDestruction) but it is 
not going to be installed
E: Broken packages

Oh joy.  Well, let's see what happens if we let it remove gxmms2...?

griffon:~$ sudo apt-get install xmms2-client-cli
...
Fetched 154kB in 2s (71.6kB/s)   
Reading changelogs... Done
(Reading database ... 115960 files and directories currently installed.)
Removing abraca ...
Removing gxmms2 ...
Processing triggers for man-db ...
Processing triggers for menu ...
(Reading database ... 115943 files and directories currently installed.)
Preparing to replace libxmmsclient-ruby1.8 0.5DrLecter-2 (using 
.../libxmmsclient-ruby1.8_0.6DrMattDestruction-1_i386.deb) ...
Unpacking replacement libxmmsclient-ruby1.8 ...
Preparing to replace xmms2-client-cli 0.5DrLecter-2.1 (using 
.../xmms2-client-cli_0.6DrMattDestruction-1_i386.deb) ...
Unpacking replacement xmms2-client-cli ...
Preparing to replace libxmmsclient-glib1 0.5DrLecter-2 (using 
.../libxmmsclient-glib1_0.6DrMattDestruction-1_i386.deb) ...
Unpacking replacement libxmmsclient-glib1 ...
Processing triggers for man-db ...
(Reading database ... 115943 files and directories currently installed.)
Removing libxmmsclient4 ...
Selecting previously deselected package libxmmsclient5.
(Reading database ... 115937 files and directories currently installed.)
Unpacking libxmmsclient5 (from 
.../libxmmsclient5_0.6DrMattDestruction-1_i386.deb) ...
Setting up libxmmsclient5 (0.6DrMattDestruction-1) ...
Setting up libxmmsclient-glib1 (0.6DrMattDestruction-1) ...
Setting up libxmmsclient-ruby1.8 (0.6DrMattDestruction-1) ...
Setting up xmms2-client-cli (0.6DrMattDestruction-1) ...
griffon:~$ xmms2 list
-[0/5237] Squirrel Nut Zippers - I Raise Hell (05:00)
  [1/419] Tori Amos - Bells For Her (05:22)
  [2/3162] Stone Temple Pilots - Where the River Goes (08:25)
...

So at least I can play music again now, even though I can't see what it's
doing any more.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xmms2 depends on:
ii  xmms2-client-cli  0.5DrLecter-2.1XMMS2 - cli client
ii  xmms2-core0.6DrMattDestruction-1 XMMS2 - core package
ii  xmms2-plugin-alsa 0.6DrMattDestruction-1 XMMS2 - ALSA output
ii  xmms2-plugin-id3v 0.6DrMattDestruction-1 XMMS2 - ID3v2 plugin
ii  xmms2-plugin-mad  0.6DrMattDestruction-1 XMMS2 - libmad based mp3 decoder
ii  xmms2-plugin-vorb 0.6DrMattDestruction-1 XMMS2 - vorbis decoder

xmms2 recommends no packages.

xmms2 suggests no packages.

-- debconf-show failed



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

Bug#525296: Cannot set tg3 interface to full duplex

[Greg Wooledge]

On Fri, Apr 24, 2009 at 12:29:23AM +0100, Ben Hutchings wrote:
 Do you also expect to get a gigabit link or only 100 megabit?

The other end is set to 100/full.  That is what I want to set the NIC to.

 Please run mii-tool -v eth0.

img2:~# uptime
 08:37:59 up 1 min,  1 user,  load average: 0.28, 0.12, 0.04
img2:~# uname -a
Linux img2 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux
img2:~# mii-tool -v eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
  product info: vendor 00:08:18, model 24 rev 0
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 
10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 100baseTx-HD


 Is autonegotiation enabled at the other end of the link?

No.  The networking department here has a Policy of not using
autonegotiation, ever.  Every single machine is expected to be
set explicitly to the speed and duplex of the port.  You REALLY
don't want to know what I did on the machines that move around
from place to place on wheeled carts.  Truly.

 So you enable autonegotiation and then use mii-tool to override it
 behind the driver's back, and you expect this to work somehow?

I have been Googling intermittently for things like Debian tg3 force
full duplex for years and I have NEVER found a straight answer to
the relatively simple question of How do you force a NIC to 100/full?

I am not explicitly setting autonegotiation.  The driver module is
probably doing so when it's loaded by udev or discover or magical
leprechauns or whatever it is that Linux/Debian are using this year.
And since nobody can tell me how NOT to do that, that's what ends up
happening.

If you can tell me how to set my NIC to 100/full in the Correct Debian
Way, then I will happily try your suggestions.

 Forget
 it; this is not a bug.  Either use autonegotiation and fix whatever is
 wrong with the other end of the link, or disable autonegotiation and
 force settings with ethtool.

That's precisely what I don't know HOW to do.  How do I disable
autonegotiation?  Where do I do it?  In /etc/network/interfaces?
What's the syntax?  Do I have to set driver-module-specific black
magic options?  Where do I do that?  Which man page documents all
of this stuff?

#debian seems to think I can try ethtool -s eth0 autoneg off duplex full.
So let's give that a whirl:

img2:~# ethtool -s eth0 autoneg off duplex full
img2:~# ethtool eth0 | grep -i duplex
Duplex: Full
img2:~# cd /usr/bin
img2:/usr/bin# ftp vue10
...
226 Transfer complete.
4508444 bytes sent in 0.79 secs (5599.2 kB/s)

Wow, I think that actually worked.

mg2:/usr/bin# mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
  product info: vendor 00:08:18, model 24 rev 0
  basic mode:   100 Mbit, full duplex
  basic status: link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD flow-control

Final test:

img2:/usr/bin# tail /etc/network/interfaces 

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 139.137.100.23
netmask 255.255.255.0
gateway 139.137.100.100
up ethtool -s eth0 autoneg off duplex full
# up sleep 5; mii-tool -F 100baseTx-FD eth0

img2:/usr/bin# shutdown -r now
...

...

...


OK, that didn't work.  I walked over to it, found it stuck on
resolving every single hostname in /etc/exports and timing out.
Individually.  Obviously there was no working network.  Rebooted
into single-user mode and confirmed that eth0 wasn't working.

So, now, the REALLY final test:

img2:~# tail /etc/network/interfaces 

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 139.137.100.23
netmask 255.255.255.0
gateway 139.137.100.100
up ethtool -s eth0 autoneg off speed 100 duplex full
# up sleep 5; mii-tool -F 100baseTx-FD eth0

img2:~# shutdown -r now
...

img2:~# uname -a
Linux img2 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux
img2:~# mii-tool -v eth0
eth0: 100 Mbit, full duplex, link ok
  product info: vendor 00:08:18, model 24 rev 0
  basic mode:   100 Mbit, full duplex
  basic status: link ok
  capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD flow-control

OK!  We're back in action.

With any luck, Google will index this and the next poor sap who has
to try to figure out How do I set my NIC to full duplex in Debian?
will find this.

(Not that this will answer every question.  I'm sure it will still fail
for lots of other people, because the correct answer seems to be something
along the lines of It depends on which driver your NIC uses.  You're
probably screwed.  Try some other operating system and pray, or buy a
different NIC and pray, or both.)



-- 
To UNSUBSCRIBE, email to 

Bug#525296: Cannot set tg3 interface to full duplex

[Greg Wooledge]

Package: linux-image-2.6.26-1-686
Version: 2.6.26-13lenny2

Neither mii-tool nor ethtool can set my network interface to full
duplex.  This is a huge problem here.

img2:/usr/bin# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
img2:/usr/bin# mii-tool -F 100baseTx-FD eth0
img2:/usr/bin# mii-tool 
eth0: no autonegotiation, 100baseTx-HD, link ok

mg2:/usr/bin# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Half 1000baseT/Full 
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Half 1000baseT/Full 
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x00ff (255)
Link detected: yes
img2:/usr/bin# ethtool -s eth0 duplex full
img2:/usr/bin# ethtool eth0 | grep -i duplex
Duplex: Half

img2:/usr/bin# dmesg | grep eth0
[3.876281] eth0: Tigon3 [partno(N/A) rev 4201 PHY(5750)] (PCI Express) 
10/100/1000Base-T Ethernet 00:1b:78:39:80:33
[3.876281] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] WireSpeed[1] 
TSOcap[1]
[3.876281] eth0: dma_rwctrl[7618] dma_mask[64-bit]
[   22.658189] tg3: eth0: Link is up at 100 Mbps, half duplex.
[   22.658321] tg3: eth0: Flow control is off for TX and off for RX.
[   25.861528] tg3: eth0: Link is down.
[   27.903339] tg3: eth0: Link is up at 100 Mbps, half duplex.
[   27.903339] tg3: eth0: Flow control is off for TX and off for RX.
[   33.220687] eth0: no IPv6 routers present
[2170329.216069] tg3: eth0: Link is down.
[2170331.343752] tg3: eth0: Link is up at 100 Mbps, half duplex.
[2170331.343752] tg3: eth0: Flow control is off for TX and off for RX.
[2170387.843919] tg3: eth0: Link is down.
[2170389.865407] tg3: eth0: Link is up at 100 Mbps, half duplex.
[2170389.865407] tg3: eth0: Flow control is off for TX and off for RX.
[2170471.002564] tg3: eth0: Link is down.
[2170473.081719] tg3: eth0: Link is up at 100 Mbps, half duplex.
[2170473.081719] tg3: eth0: Flow control is off for TX and off for RX.

I'll try -2-686 but I don't expect it to work differently.  Then I
suppose I'll try building custom kernels, or maybe I'll try grabbing
the tg3 driver from 2.6.18 or 2.6.8, back when things worked.



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

Bug#525296: other stuff I tried

[Greg Wooledge]

First, I updated to 2.6.26-2-686 (from Lenny), but this has the same
problem for me.  No command I know will set that NIC to full duplex
under that kernel.

I tried building a custom 2.6.29.1 kernel next, but it panics when
it can't mount /dev/md0 as the root file system.  I'm not in the mood
to try to figure out how all this initrd stuff works.  Too much work.

Next, I rebooted into etch's 2.6.18-6-686 kernel (this is an etch-lenny
box, with the old kernel still there).  This works fine for me, as far
as I can tell so far.  The NIC goes into full duplex mode due to the
up sleep 5; mii-tool -F 100baseTx-FD eth0 line I have in
/etc/network/interfaces, and all the things that should be running
(NFS, Samba) appear to be running.

Then, I tried building upstream tg3 drivers against the 2.6.26-2-686
kernel headers.  I was able to build tg3-3.92n and tg3-3.98e modules
successfully, but I was not able to build 3.77e or 3.81e, nor was I
able to build the tg3.{c,h} sources yanked out of a kernel.org
2.6.18.8 source tarball -- all of those failed with messages like
error: implicit declaration of function 'netif_poll_disable' (and
many more).

I rebooted into 2.6.26-2-686 again, unloaded the tg3 driver module,
and loaded the tg3-3.92n and tg3-3.98e modules in turn, and attempted
to set the NIC to full duplex using mii-tool and ethtool.  All of
these attempts failed.  The NIC was left in half duplex mode after
bouncing up and down for a few seconds.  (Except in the case of
3.98e + ethtool, where the command aborted with an error without even
touching the NIC.)

For now, I am running on 2.6.18-6-686 since this kernel's tg3 driver
supports what I need.



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

Bug#521521: how I fixed my network

[Greg Wooledge]

Upgrading to 0.140-2 was not sufficient to fix this problem for me.
I still had an old definition for eth0 and a new definition for
eth1 in my /etc/udev/rules.d/70-persistent-net.rules file even
after rebooting.

Morever, moving that file to /var/tmp/ and rebooting to let it be
regenerated also did not solve the problem -- it was regenerated
with eth1 as the name instead of eth0.  So either there is
another file somewhere that stores persistent network interface names,
(though it's not obvious to me WHERE such a thing would be), or
the file was regenerated on the way down, instead of on the way up,
using eth1 which was still present (albeit unconfigured) at the
time.

The only thing that worked for me was to actually edit the file, changing
eth1 to eth0, and reboot.

I had really, really been hoping to avoid that, because I'm reluctant
to edit configuration files for packages about which I don't care enough
to learn their innermost secrets, since that means I'll be spammed with
prompts by dpkg about whether I want to keep the old version or install
the package maintainer's version, forever and ever.  Or at least until
a new version of Linux rewrites all the device handling for the (n+1)st
time and we scrap everything and replace it with something even more
complex and silly.  Which seems to happen every few years.



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

Bug#511797: bind9: all queries denied since last update

[Greg Wooledge]

There was no mention of this change on the Upgrades from previous
releases page, which was rather distressing when things suddenly
broke (including my ability to reach Google to figure out what I
needed to do).

The named.conf file should be edited prior to aptitude upgrade,
or at the very least, prior to aptitude dist-upgrade, so anywhere
on http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.html
prior to section 4.5 would be good.

Since this isn't i386 specific, I'd expect a single sentence with a
hyperlink to an architecture-neutral page that explains the change,
and how to edit the named.conf file appropriately.



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

Bug#481428: needs versioned dependency on libflac8

[Greg Wooledge]

Package: flac
Version: 1.2.1-1.2
Severity: normal


griffon:~$ sudo apt-get install flac
[sudo] password for greg: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  flac
1 upgraded, 0 newly installed, 0 to remove and 700 not upgraded.
Need to get 172kB of archives.
After this operation, 45.1kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org unstable/main flac 1.2.1-1.2 [172kB]
Fetched 172kB in 1s (107kB/s)
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n]? 
(Reading database ... 96460 files and directories currently installed.)
Preparing to replace flac 1.2.1-1 (using .../flac_1.2.1-1.2_i386.deb) ...
Unpacking replacement flac ...
Setting up flac (1.2.1-1.2) ...
griffon:~$ flac --help
flac: symbol lookup error: flac: undefined symbol: 
FLAC__ENTROPY_CODING_METHOD_PARTITIONED_RICE2_ESCAPE_PARAMETER
griffon:~$ ldd $(which flac)
linux-gate.so.1 =  (0xe000)
libFLAC.so.8 = /usr/lib/libFLAC.so.8 (0xb7f1b000)
libogg.so.0 = /usr/lib/libogg.so.0 (0xb7f16000)
libm.so.6 = /lib/i686/cmov/libm.so.6 (0xb7ef)
libc.so.6 = /lib/i686/cmov/libc.so.6 (0xb7da2000)
/lib/ld-linux.so.2 (0xb7f75000)
griffon:~$ dpkg -l | grep flac
ii  flac 1.2.1-1.2  
Free Lossless Audio Codec - command line too
ii  gstreamer0.8-flac0.8.4-1
FLAC plugin for GStreamer
ii  libflac4 1.1.0-11   
Free Lossless Audio Codec - runtime C librar
ii  libflac7 1.1.2-3
Free Lossless Audio Codec - runtime C librar
ii  libflac8 1.1.4-3+b1 
Free Lossless Audio Codec - runtime C librar
ii  xmms-flac1.1.4-3+b1 
Free Lossless Audio Codec - XMMS and Beep in
griffon:~$ sudo apt-get install libflac8
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  libflac8
1 upgraded, 0 newly installed, 0 to remove and 699 not upgraded.
Need to get 158kB of archives.
After this operation, 81.9kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org unstable/main libflac8 1.2.1-1.2 [158kB]
Fetched 158kB in 1s (120kB/s)
Reading changelogs... Done
(Reading database ... 96460 files and directories currently installed.)
Preparing to replace libflac8 1.1.4-3+b1 (using 
.../libflac8_1.2.1-1.2_i386.deb) ...
Unpacking replacement libflac8 ...
Setting up libflac8 (1.2.1-1.2) ...

At which point it worked correctly.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages flac depends on:
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  libflac8  1.2.1-1.2  Free Lossless Audio Codec - runtim
ii  libogg0   1.1.3-3Ogg Bitstream Library

flac recommends no packages.

-- debconf-show failed



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

Bug#476974: coreutils: date -d '18:00 -1 hour' wrong answer

[Greg Wooledge]

Package: coreutils
Version: 6.10-6
Severity: normal


These results are correct:

  griffon:~$ date
  Sun Apr 20 09:44:18 EDT 2008
  griffon:~$ date -d 'Sun Apr 20 18:00:00 EDT 2008 -1 hour'
  Sun Apr 20 17:00:00 EDT 2008
  griffon:~$ date -d '18:00:00 EDT -1 hour'
  Sun Apr 20 17:00:00 EDT 2008

But if I leave off the time zone name, I get:

  griffon:~$ date -d '18:00:00 -1 hour'
  Sun Apr 20 15:01:00 EDT 2008
  griffon:~$ date -d '18:00:00 -4 hour'
  Sun Apr 20 15:04:00 EDT 2008
  griffon:~$ date -d '18:00:00 -5 hour'
  Sun Apr 20 15:05:00 EDT 2008

This is clearly not correct or useful behavior.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages coreutils depends on:
ii  libacl1   2.2.39-1   Access control list shared library
ii  libc6 2.7-10 GNU C Library: Shared libraries
ii  libselinux1   2.0.59-1   SELinux shared libraries

coreutils recommends no packages.

-- debconf-show failed



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

Bug#469897: locate: globs do not work as documented

[Greg Wooledge]

Package: locate
Version: 4.2.33-1
Severity: normal


The manual says:

   For each given
   pattern, locate searches one or more databases of file names  and  dis-
   plays  the  file  names that contain the pattern.  Patterns can contain
   shell-style metacharacters: `*', `?', and `[]'.  The metacharacters  do
   not  treat  `/'  or `.'  specially.  Therefore, a pattern `foo*bar' can
   match a file name that contains `foo3/bar', and a pattern `*duck*'  can
   match  a  file name that contains `lake/.ducky'.

Note the use of the word contain, several times.  This seems to mean
that the pattern can be any part of the file name.  In the example given
in the manual, I would expectlocate foo*bar   to match files like:

/usr/share/doc/package/examples/foo3/bar

But in practice, it will never match any file at all (as far as I can tell).
This is what I get:

griffon:~$ sudo updatedb
griffon:~$ locate bash\*completion
griffon:~$ locate \*bash\*completion
/etc/bash_completion
/usr/share/doc/bash/BUGS.bash_completion

Without a leading * the pattern simply never matches anything at all.
What's even more confusing is that a pattern WITHOUT a * in it works the
way I would expect (and the way the manual describes):

griffon:~$ locate bash_completion
/etc/bash_completion
/etc/bash_completion.d
/etc/bash_completion.d/debconf
/etc/bash_completion.d/m-a
/etc/bash_completion.d/make_kpkg
/etc/bash_completion.d/pon
/etc/bash_completion.d/subversion
/usr/share/doc/bash/BUGS.bash_completion
/usr/share/doc/bash/changelog.bash_completion.gz
/usr/share/doc/bash/README.bash_completion.gz

Under no circumstances would I expect bash_completion to match more files
than bash*completion does.  The * version should be a superset of the _
version.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages locate depends on:
ii  findutils 4.2.33-1   utilities for finding files--find,
ii  libc6 2.7-8  GNU C Library: Shared libraries

locate recommends no packages.

-- debconf-show failed



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

Bug#457971: ethtool: fails to detect or set duplex correctly (tg3)

[Greg Wooledge]

Package: ethtool
Version: 5-1
Severity: normal

Fails to detect the current duplex setting:

img2:~# mii-tool eth0
eth0: 100 Mbit, full duplex, link ok
img2:~# ethtool eth0 | grep -i duplex
Duplex: Half

(mii-tool's output is correct.)

Fails to set the duplex correctly:

img2:~# ethtool -s eth0 duplex full
img2:~# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
img2:~# ethtool eth0 | grep -i duplex
Duplex: Half

Performing an actual transfer of data from this host to another host
reveals that, indeed, the interface is operating at the wrong duplex
setting.

The ethtool -s eth0 duplex full test seems to have caused these kernel
messages (for whatever that's worth):

Dec 27 10:45:49 img2 kernel: tg3: eth0: Link is down.
Dec 27 10:45:51 img2 kernel: tg3: eth0: Link is up at 100 Mbps, half duplex.
Dec 27 10:45:51 img2 kernel: tg3: eth0: Flow control is off for TX and off for 
RX.

Hardware information:

img2:/var/log# dmesg | egrep 'tg3|eth0'
tg3.c:v3.65 (August 07, 2006)
eth0: Tigon3 [partno(N/A) rev 4201 PHY(5750)] (PCI Express) 10/100/1000BaseT 
Ethernet 00:1b:78:39:80:33
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[1] 
eth0: dma_rwctrl[7618] dma_mask[64-bit]
...

Here's the full output of ethtool, after I used mii-tool to repair the
duplex setting:

img2:~# ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Half 1000baseT/Full 
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Half 1000baseT/Full 
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x00ff (255)
Link detected: yes

Bug #440319 is related to this one, but only as background information
about why I was trying to use ethtool at all.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages ethtool depends on:
ii  libc6  2.3.6.ds1-13etch2 GNU C Library: Shared libraries

ethtool recommends no packages.

-- no debconf information



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

Bug#383318: !: event not found

[Greg Wooledge]

I reported this a while back -- see http://bugs.debian.org/135402 for
details, including upstream's response.

Your claim that this makes scripts quit with an error seems dubious,
because csh-style history expansion is not performed when bash is
running a script.  I suspect your script has some other problem.

I also cover this issue, in slightly less detail, on
http://wooledge.org/mywiki/BashPitfalls (pitfall #22).



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

Bug#440317: reportbug crashes when trying to check packages.d.o

[Greg Wooledge]

Package: reportbug
Version: 3.31

img2:~# apt-get install reportbug
...
Setting up mime-support (3.39-1) ...

Setting up python2.4-minimal (2.4.4-3) ...
Linking and byte-compiling packages for runtime python2.4...

Setting up python2.4 (2.4.4-3) ...

Setting up python-minimal (2.4.4-2) ...
Setting up python (2.4.4-2) ...

Setting up python-central (0.5.12) ...
Setting up reportbug (3.31) ...

img2:~# reportbug ifupdown
Warning: no reportbug configuration found.  Proceeding in novice mode.
Running 'reportbug' as root is probably insecure! Continue [y|N|q|?]? y
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'root [EMAIL PROTECTED]' as your from address.
Getting status for ifupdown...
Checking for newer versions at packages.debian.org...
Traceback (most recent call last):
  File /usr/bin/reportbug, line 1747, in ?
main()
  File /usr/bin/reportbug, line 779, in main
return iface.user_interface()
  File /usr/bin/reportbug, line 1212, in user_interface
http_proxy=self.options.http_proxy, arch=arch)
  File /usr/share/reportbug/checkversions.py, line 294, in check_available
stuff = get_versions_available(package, dists, http_proxy, arch)
  File /usr/share/reportbug/checkversions.py, line 187, in 
get_versions_available
page = open_url(PACKAGES_URL % package, http_proxy)
  File /usr/share/reportbug/urlutils.py, line 133, in open_url
page = urlopen(url, proxies)
  File /usr/share/reportbug/urlutils.py, line 123, in urlopen
return _opener.open(req)
  File /usr/lib/python2.4/urllib2.py, line 364, in open
response = meth(req, response)
  File /usr/lib/python2.4/urllib2.py, line 471, in http_response
response = self.parent.error(
  File /usr/lib/python2.4/urllib2.py, line 396, in error
result = self._call_chain(*args)
  File /usr/lib/python2.4/urllib2.py, line 337, in _call_chain
result = func(*args)
  File /usr/lib/python2.4/urllib2.py, line 554, in http_error_302
return self.parent.open(new)
  File /usr/lib/python2.4/urllib2.py, line 358, in open
response = self._open(req, data)
  File /usr/lib/python2.4/urllib2.py, line 376, in _open
'_open', req)
  File /usr/lib/python2.4/urllib2.py, line 337, in _call_chain
result = func(*args)
  File /usr/share/reportbug/urlutils.py, line 74, in http_open
return decode(urllib2.HTTPHandler.http_open(self, req))
  File /usr/lib/python2.4/urllib2.py, line 1021, in http_open
return self.do_open(httplib.HTTPConnection, req)
  File /usr/lib/python2.4/urllib2.py, line 994, in do_open
r = h.getresponse()
  File /usr/lib/python2.4/httplib.py, line 866, in getresponse
response.begin()
  File /usr/lib/python2.4/httplib.py, line 336, in begin
version, status, reason = self._read_status()
  File /usr/lib/python2.4/httplib.py, line 300, in _read_status
raise BadStatusLine(line)
httplib.BadStatusLine


General information:
  New etch installation
  Linux img2 2.6.18-5-686 #1 SMP Sun Aug 12 21:57:02 UTC 2007 i686 GNU/Linux
  ii  libc6  2.3.6.ds1-13etch2 GNU C Library: Shared libraries


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

Bug#440319: media 100baseTx-FD in interfaces makes gateway line fail

[Greg Wooledge]

Package: ifupdown
Version: 0.6.8

With the following configuration in /etc/network/interfaces:

===
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 139.137.100.23
netmask 255.255.255.0
gateway 139.137.100.100
media 100baseTx-FD
# up mii-tool -F 100baseTx-FD eth0
===

The gateway line was not respected; the machine booted without a default
gateway at all.  The routing table looked like:

Destination Gateway Genmask Flags   MSS Window  irtt Iface
139.137.100.0   0.0.0.0 255.255.255.0   U 0 0  0 eth0

Also, the media 100baseTx-FD line did not actually set the interface's
media type to full duplex.  It failed to do what it was supposed to do,
as well as causing another line (above it!) to fail.

The up mii-tool -F 100baseTx-FD eth0 line also did not work as expected
(which is why it was commented out).  The interface still came up with
the wrong duplex.

The only working solution I've found so far is:

===
iface eth0 inet static
address 139.137.100.23
netmask 255.255.255.0
gateway 139.137.100.100
up sleep 3; mii-tool -F 100baseTx-FD eth0
===

I'm not using any other manual configuration of anything; nothing in any
modules or modules.conf files, etc.  Just plain old etch default
autodetecting mechanisms, whatever they may be.


Interface details:
  img2:~# dmesg | grep eth0
  eth0: Tigon3 [partno(N/A) rev 4201 PHY(5750)] (PCI Express) 10/100/1000BaseT 
Ethernet 00:1b:78:39:80:33
  eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] 
TSOcap[1] 
  eth0: dma_rwctrl[7618] dma_mask[64-bit]
  tg3: eth0: Link is up at 100 Mbps, half duplex.
  tg3: eth0: Flow control is off for TX and off for RX.
  eth0: no IPv6 routers present

  img2:~# dmesg | grep tg
  tg3.c:v3.65 (August 07, 2006)
  tg3: eth0: Link is up at 100 Mbps, half duplex.
  tg3: eth0: Flow control is off for TX and off for RX.


General information:
  New etch installation
  Linux img2 2.6.18-5-686 #1 SMP Sun Aug 12 21:57:02 UTC 2007 i686 GNU/Linux
  ii  libc6  2.3.6.ds1-13etch2 GNU C Library: Shared libraries


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

Bug#423107: rtorrent: duplicate symptoms here

[Greg Wooledge]

Package: rtorrent
Version: 0.7.4-2
Followup-For: Bug #423107


I get the same symptom as the original reporter.  Running rtorrent clears
the screen, switches the terminal into some non-canonical mode, and writes

rtorrent: symbol lookup error: rtorrent: undefined symbol: 
_ZN7torrent21max_download_unchokedEv

Recovery of the terminal at this point requires running tput cnorm and
stty sane.  No biggie for me, but someone reading this may benefit from
that.

I had a ~/.rtorrent.rc file, but I get the same symptom if I mv it to a
different name so that it's not read.  Nevertheless, I include it here for
completeness:

== begin .rtorrent.rc 
# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed. Remember to
# uncomment the options you wish to enable.

# Minumum amount of peers to connect per torrent, if available.
min_peers = 10

# Minumum amount of peers to connect per torrent.
max_peers = 40

# Maximum number of simultanious uploads per torrent.
max_uploads = 5

# Global download rate in KiB. 0 for unlimited.
#download_rate = 0

# Global upload rate in KiB. 0 for unlimited.
upload_rate = 10

# Default directory to save downloaded files. Note it doesn't support
# space yet.
#directory = ./

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
#session = 

# The ip address reported to the tracker.
#ip = 127.0.0.1

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1

# Port range to use for listening.
port_range = 6881-6889

# Start opening ports at a random position within the port range.
#port_random = no

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
#check_hash = no

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 128

# Number of sockets to simultaneously keep open.
#max_open_sockets = no default

# Dump data received from trackers to the files ./tracker_dump.time.
#tracker_dump = no

# Change the interval between each throttle tick, in milliseconds. In
# the range 1-5000 ms.
#throttle_interval = 1000
 end .rtorrent.rc 


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages rtorrent depends on:
ii  libc6   2.5-7GNU C Library: Shared libraries
ii  libcurl4-openssl7.16.2-3 Multi-protocol file transfer libra
ii  libgcc1 1:4.1.2-4GCC support library
ii  libidn110.5.18-1 GNU libidn library, implementation
ii  libkrb531.6.dfsg.1-3 MIT Kerberos runtime libraries
ii  libncurses5 5.5-1Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a  2.0.16-2 type-safe Signal Framework for C++
ii  libssl0.9.8 0.9.8c-2 SSL shared libraries
ii  libstdc++6  4.1.2-4  The GNU Standard C++ Library v3
ii  libtorrent100.11.1-1 a C++ BitTorrent library
ii  zlib1g  1:1.2.3-11   compression library - runtime

rtorrent recommends no packages.

-- no debconf information


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

Bug#397338: Acknowledgement (apache2.2-common: 2.0-2.2 upgrade fails with custom jk module)

[Greg Wooledge]

Sorry about the root@ thing.  I don't normally login to that server
as myself.  This is my normal (work) e-mail address should you need to
contact me.


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

Bug#355811: problem does not occur on 7.0.*

[Greg Wooledge]

After upgrading to

ii  xserver-xorg   7.0.11 the X.Org X server

(and related packages), the problem does not occur any longer.  (Things
aren't perfect, but this particular bug is no longer present.)

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#220025: Will fix

[Greg Wooledge]

Thomas Hood ([EMAIL PROTECTED]) wrote:

 I propose to fix this bug by adding a script at S:S99 that stops bootlogd
 if the system is being booted with the single parameter.  Anyone see any
 problem with this idea?

There are other aliases for single, such as 1.  Some people might
come up in single user mode using one of those alternative boot parameters.
I don't know whether there's an exhaustive list of all of them anywhere,
either.

I suggest using the runlevel(8) command instead, assuming that it returns
reliable information.  The man page says it's safe to use in rc scripts, but
I haven't tried it myself.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#334291: rtorrent: memory leak

[Greg Wooledge]

Qingning Huo ([EMAIL PROTECTED]) wrote:

 Many thanks for the bug report.  This looks like an upstream problem.
 Before I forward this to the upstream author, can you confirm whether
 this problem still exists in the latest version (0.3.6-1)?

It's hard to be sure, but it seems to be better:

griffon:~$ while sleep 120; do ps u 23261 | tail -1; done
greg 23261  0.1  9.6  59016 49628 pts/10   S+   Oct27   2:17 rtorrent
greg 23261  0.1 10.0  61072 51980 pts/10   S+   Oct27   2:17 rtorrent
greg 23261  0.1 10.6  60044 54880 pts/10   S+   Oct27   2:18 rtorrent
greg 23261  0.1 11.2  67236 57936 pts/10   S+   Oct27   2:18 rtorrent
greg 23261  0.1  5.5  35388 28572 pts/10   S+   Oct27   2:19 rtorrent
greg 23261  0.1  5.5  37440 28716 pts/10   S+   Oct27   2:19 rtorrent
greg 23261  0.1  6.0  42572 31116 pts/10   S+   Oct27   2:19 rtorrent
greg 23261  0.1  6.4  45660 33176 pts/10   S+   Oct27   2:19 rtorrent
greg 23261  0.1  6.8  45660 35348 pts/10   S+   Oct27   2:20 rtorrent
greg 23261  0.1  7.2  46692 37284 pts/10   S+   Oct27   2:20 rtorrent
greg 23261  0.1  7.6  48744 39552 pts/10   S+   Oct27   2:20 rtorrent
greg 23261  0.1  8.0  50800 41620 pts/10   S+   Oct27   2:21 rtorrent
greg 23261  0.1  8.4  52856 43468 pts/10   S+   Oct27   2:21 rtorrent
greg 23261  0.1  8.9  55940 46044 pts/10   S+   Oct27   2:21 rtorrent

That's with one large file being downloaded/uploaded.  Peers set to 50.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#334291: rtorrent: memory leak

[Greg Wooledge]

Package: rtorrent
Version: 0.3.4-1
Severity: normal


USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
greg 15173 21.6  0.7   6484  3816 pts/10   S+   14:48   1:07 rtorrent
greg 15173  6.5  1.6  18904  8552 pts/10   S+   14:48   1:08 rtorrent
greg 15173  4.6  2.8  33240 14668 pts/10   S+   14:48   1:08 rtorrent
[...]
greg 15173  1.2 26.0 219764 134324 pts/10  S+   14:48   1:46 rtorrent


That's all just downloading a single torrent file.

* Star Wars Revelations
* Torrent: 3292.9 / 7951.3 MB Rate:   9.3 /  31.5 KB Uploaded: 76.3 MB
*

I had to restart rtorrent twice because it kept blowing up with an error
message about failure to allocate memory (presumably because it hit my
ulimit).  I originally intended to wait until the error appeared again so
I could include it in the bug report, but I ran out of patience.  (Also,
I've raised the ulimit for this third run.)

Not sure whether it matters, but I've got max_peers = 10 in my .rtorrent.rc
file -- but for this specific file, I raised max_peers to 40 by pressing '6'
a few times on the file's download-detail screen.

$ grep '^[^#]' ~/.rtorrent.rc 
min_peers = 10
max_peers = 10
max_uploads = 5
upload_rate = 10
port_range = 6881-6889

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.31
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages rtorrent depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libcurl3  7.15.0-1   Multi-protocol file transfer libra
ii  libgcc1   1:4.0.2-2  GCC support library
ii  libidn11  0.5.18-1   GNU libidn library, implementation
ii  libncurses5   5.4-9  Shared libraries for terminal hand
ii  libsigc++-2.0-0c2 2.0.10-3   type-safe Signal Framework for C++
ii  libssl0.9.7   0.9.7g-1   SSL shared libraries
ii  libstdc++64.0.2-2The GNU Standard C++ Library v3
ii  libtorrent5   0.7.4-1a C++ BitTorrent library
ii  zlib1g1:1.2.3-1  compression library - runtime

rtorrent recommends no packages.

-- no debconf information


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

Bug#328113: [Pkg-shadow-devel] Bug#328113: man page improvements for passwd.5

[Greg Wooledge]

Christian Perrier ([EMAIL PROTECTED]) wrote:

 I don't really know what to do with your bug report. We ca n't apply
 it and I don't want to reject help. Would you be OK if I sent you the
 passwd.5.xml file so that you can make the suggested changes there
 (and review it while you're at it)

Well, it can't hurt to look at it.  Go ahead and send it, but I can't
promise anything until I see it.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#328113: [Pkg-shadow-devel] Bug#328113: man page improvements for passwd.5

[Greg Wooledge]

Christian Perrier ([EMAIL PROTECTED]) wrote:

 (reply set to the bug report)
 
 Here it is. Thanks for any comment you can make.

All right.  It looks like it was translated directly from the existing man
page, which makes applying the changes simple, except for trying to figure
out what XML tags to use for various purposes.

Is there a definitive list of the tags, all in one place, which matches
the actual set used for the man page?  For example,
http://www.lodestar2.com/people/dyork/talks/2002/ols/docbook-tutorial/frames/foil35.html
shows

  emphasis role=boldThis is some bold text./emphasis

and 
http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/docbooksys/segmentedhtml/ch09s01.html
uses

  emphasis role=strongA different type of emphasis/emphasis

but the man page you sent uses

  emphasis remap='B'Login/emphasis

Also, 
http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/build/tutorials/docbooksys/segmentedhtml/ch09s01.html
says that apostrophes must be converted into apos; but the man page has
the word user's in it, with a raw apostrophe.

I'm unclear how to put in a quoted literal character, as in:

  with seven fields delimited by colons (`:')

Is quote:/quote the proper markup for that?  It seems right, based on
http://www.docbook.org/tdg/en/html/quote.html, but I'm not sure how
closely you're following that set of tags.

Finally, what command should I use to render the XML into its man page
format, so that I can check that what I've done is correct?  (In other
words, the Docbook XML equivalent of nroff -man passwd.5 | less, or a
command to convert passwd.5.xml into passwd.5.)  I'd be happy to help out
with documentation for more than just this one man page, but I can't seem
to find the right starting point.

I'm attaching what I've got so far.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
?xml version=1.0 encoding=UTF-8?
!DOCTYPE refentry PUBLIC -//OASIS//DTD DocBook XML V4.3//EN
http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;
refentry id='passwd.5'
  !-- $Id: passwd.5.xml,v 1.9 2005/08/29 18:00:48 kloczek Exp $ --
  refmeta
refentrytitlepasswd/refentrytitle
manvolnum5/manvolnum
  /refmeta
  refnamediv id='name'
refnamepasswd/refname
refpurposeThe password file/refpurpose
  /refnamediv

  refsect1 id='description'
titleDESCRIPTION/title
para
  filename/etc/passwd/filename contains one line for each
  user account, with seven fields delimited by colons
  (quote:/quote).
  These fields are:
/para
itemizedlist mark='bullet'
  listitem
paralogin name/para
  /listitem
  listitem
paraoptional encrypted password/para
  /listitem
  listitem
paranumerical user ID/para
  /listitem
  listitem
paranumerical group ID/para
  /listitem
  listitem
parauser name or comment field/para
  /listitem
  listitem
parauser home directory/para
  /listitem
  listitem
paraoptional user command interpreter/para
  /listitem
/itemizedlist

para
  The encrypted password field may be blank, in which case no
  password is required to authenticate as the specified login name.
  (However, some applications which read the
  filenamepasswd/filename file may decide not to permit
  emphasisany/emphasis access at all if the
  emphasispassword/emphasis field is blank.)
  If the emphasispassword/emphasis field is a lower-case
  quotex/quote, then the encrypted password is actually stored in
  the citerefentryrefentrytitleshadow/refentrytitle
  manvolnum5/manvolnum/citerefentry file instead;
  there emphasis remap='B'must/emphasis be a corresponding line
  in the filenameshadow/filename file, or else the user account
  is invalid.
  If the emphasispassword/emphasis field is any other string,
  then it will be treated as an encrypted password, as specified
  by citerefentryrefentrytitlecrypt/refentrytitle
  manvolnum3/manvolnum/citerefentry.
para

para
  The comment field is used by various system utilities, such as
  citerefentryrefentrytitlefinger/refentrytitle
  manvolnum1/manvolnum/citerefentry.
/para

para
  The home directory field provides the name of the initial working
  directory.
  The emphasis remap='B'login/emphasis program uses this
  information to set the value of the envar$HOME/envar
  environmental variable.
/para

para
  The command interpreter field provides the name of the user's
  command language interpreter, or the name of the initial program
  to execute.
  The emphasis remap='B'login/emphasis program uses this
  information to set the value of the envar$SHELL/envar
  environmental variable.
  If this field is empty

Bug#328113: man page improvements for passwd.5

[Greg Wooledge]

Package: passwd
Version: 1:4.0.3-30
Severity: wishlist
Tags: patch


This probably needs to go upstream, but I'm not even sure who's in charge
of this documentation, if *anyone* at all is  Nor am I sure who's in
charge of arranging the translations, etc.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.31
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages passwd depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libpam-modules0.76-22Pluggable Authentication Modules f
ii  libpam0g  0.76-22Pluggable Authentication Modules l
ii  login 1:4.0.3-30 System login tools

passwd recommends no packages.

-- debconf information excluded
33,34c33,35
 contains various pieces of information for each user account.
 Included is
---
 contains one line for each user account, with seven fields delimited
 by colons (`:').
 These fields are
48c49
 User command interpreter
---
 Optional user command interpreter
50,58c51,61
 The password field may not be filled if shadow passwords
 have been enabled.
 If shadow passwords are being used, the encrypted password will
 be found in \fI/etc/shadow\fR.
 The encryped password consists of 13 characters from the
 64 character alphabet
 a thru z, A thru Z, 0 thru 9, \. and /.
 Refer to \fBcrypt\fR(3) for details on how this string is
 interpreted.
---
 The encrypted password field may be blank, in which case no password is
 required to authenticate as the specified login name.
 (However, some applications which read the \fBpasswd\fR file may decide
 not to permit \fIany\fR access at all if the \fIpassword\fR field is
 blank.)
 If the \fIpassword\fR field is a lower-case `x', then the encrypted
 password is actually stored in the \fBshadow\fR(5) file instead; there
 \fBmust\fR be a corresponding line in the \fBshadow\fR file, or else
 the user account is invalid.
 If the \fIpassword\fR field is any other string, then it will be treated
 as an encrypted password, as specified by \fBcrypt\fR(3).
89c92
 \fBLogin\fR uses this information to set the value of
---
 The \fBlogin\fR(1) program uses this information to set the value of
95c98
 \fBLogin\fR uses this information to set the value of the
---
 The \fBlogin\fR(1) program uses this information to set the value of the
99a103,104
 .br
 /etc/shadow \- optional encrypted password file
103a109,110
 .BR getent (1),
 .BR getpwnam (3),

Bug#325299: apt: --names-only doesn't just search names

[Greg Wooledge]

Package: apt
Version: 0.6.40.1
Severity: normal

The man page says:

  and if --names-only is given then the long description is not searched,
  only the package name is.

But:

griffon:~$ apt-cache search --names-only ming
apache-common - support files for all Apache webservers
[...]

-- Package-specific info:

-- apt-config dump --

APT ;
APT::Architecture i386;
APT::Build-Essential ;
APT::Build-Essential:: build-essential;
Dir /;
Dir::State var/lib/apt/;
Dir::State::lists lists/;
Dir::State::cdroms cdroms.list;
Dir::State::userstatus status.user;
Dir::State::status /var/lib/dpkg/status;
Dir::Cache var/cache/apt/;
Dir::Cache::archives archives/;
Dir::Cache::srcpkgcache srcpkgcache.bin;
Dir::Cache::pkgcache pkgcache.bin;
Dir::Etc etc/apt/;
Dir::Etc::sourcelist sources.list;
Dir::Etc::vendorlist vendors.list;
Dir::Etc::vendorparts vendors.list.d;
Dir::Etc::main apt.conf;
Dir::Etc::parts apt.conf.d;
Dir::Etc::preferences preferences;
Dir::Bin ;
Dir::Bin::methods /usr/lib/apt/methods;
Dir::Bin::dpkg /usr/bin/dpkg;
DPkg ;
DPkg::Pre-Install-Pkgs ;
DPkg::Pre-Install-Pkgs:: /usr/bin/apt-listchanges --apt || test $? -ne 10;
DPkg::Pre-Install-Pkgs:: /usr/sbin/dpkg-preconfigure --apt || true;
DPkg::Tools ;
DPkg::Tools::Options ;
DPkg::Tools::Options::/usr/bin/apt-listchanges ;
DPkg::Tools::Options::/usr/bin/apt-listchanges::Version 2;
Acquire ;
Acquire::http ;
Acquire::http::Proxy http://192.168.2.1:3128/;;

-- (no /etc/apt/preferences present) --


-- /etc/apt/sources.list --

deb http://ftp.us.debian.org/debian/ unstable main non-free contrib
deb-src http://ftp.us.debian.org/debian/ unstable main non-free contrib

#deb http://security.debian.org/ stable/updates main contrib non-free

#deb ftp://ftp.tux.org/pub/java/debian unstable main non-free
deb ftp://ftp.nerim.net/debian-marillat/ unstable main

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.31
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages apt depends on:
ii  libc6 2.3.5-4GNU C Library: Shared libraries an
ii  libgcc1   1:4.0.1-6  GCC support library
ii  libstdc++64.0.1-3The GNU Standard C++ Library v3

apt recommends no packages.

-- no debconf information


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

Bug#323618: java-package: incorrect size for jdk-1_5_0_*

[Greg Wooledge]

Package: java-package
Version: 0.25
Severity: normal


I had to edit /usr/share/java-package/sun-j2sdk.sh and change 130 to 128
to get java-package to work with jdk-1_5_0_03-linux-i586.bin.  I kept getting
this error:

Testing extracted archive...
Invalid size (128 MB) of extracted archive. Probably you have not
enough free disc space in the temporary directory. Note: You can
specify an alternate directory by setting the environment variable
TMPDIR.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.31
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages java-package depends on:
ii  coreutils 5.2.1-2The GNU core utilities
ii  debhelper 4.2.20 helper programs for debian/rules
ii  fakeroot  1.4.2  Gives a fake root environment

java-package recommends no packages.

-- no debconf information


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

Bug#323618: classes.jsa missing?

[Greg Wooledge]

I spoke with another user about this problem.  He reports that when he
built sun-j2sdk1.5 with java-package, his dpkg -L output includes a file
called /usr/lib/j2sdk1.5-sun/jre/lib/i386/client/classes.jsa which mine
does not.  classes.jsa does not appear anywhere at all in the output of
the java-package extraction, which I have logged at
http://wooledge.org/~greg/java-package.log for reference.  This missing
classes.jsa file might account for the size disrepancy, but I have no
idea why the java install script would omit it from the extraction.

classes.jsa is the only file that's missing from mine compared to his.

This is the original .bin file:

-rw---  1 greg greg 48772357 2005-05-14 16:42 jdk-1_5_0_03-linux-i586.bin

jsa does not appear anywhere in the script part of the .bin file.  The
first hit I get on jsa is in the compressed binary data, so I'm *really*
stumped.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#322501: lincity-ng: crashes, segmentation faults, etc.

[Greg Wooledge]

Moritz Muehlenhoff ([EMAIL PROTECTED]) wrote:

  GameView::readImage# Could not load image images/tiles/farm15.png
  Unexpected exception: Couldn't create texture: out of memory
  Vertex3f: 1
  crashed
 
  So that wasn't helpful.  But at least SDL works.
 
 This seem to be similar symptons as described in 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321898
 
 Do you have AGP support enabled/is your graphics adapter AGP capable?

(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: ATI Radeon 9000/PRO If (AGP/PCI) (ChipID = 0x4966)
(--) RADEON(0): Linear framebuffer at 0xd000
(--) RADEON(0): VideoRAM: 131072 kByte (128 bit DDR SDRAM)
(II) RADEON(0): AGP card detected

[[ snip ]]

(II) RADEON(0): [drm] DRM interface version 1.0
(II) RADEON(0): [drm] created radeon driver at busid pci::01:00.0
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0ac5000
(II) RADEON(0): [drm] mapped SAREA 0xe0ac5000 to 0x40018000
(II) RADEON(0): [drm] framebuffer handle = 0xd000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x1106/0x3189; Card 0x1002/0x4966]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0xe8b05000
(II) RADEON(0): [agp] ring handle = 0xc000
(II) RADEON(0): [agp] Ring mapped at 0x48284000
(II) RADEON(0): [agp] ring read ptr handle = 0xc0101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0x4001a000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xc0102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x48385000
(II) RADEON(0): [agp] GART texture map handle = 0xc0302000
(II) RADEON(0): [agp] GART Texture map mapped at 0x48585000
(II) RADEON(0): [drm] register handle = 0xe002
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): CP in BM mode
(II) RADEON(0): Using 8 MB GART aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for GART textures
(II) RADEON(0): Memory manager initialized to (0,0) (1280,8191)
(II) RADEON(0): Reserved area from (0,1024) to (1280,1026)
(II) RADEON(0): Largest offscreen area available: 1280 x 7165
(II) RADEON(0): Will use back buffer at offset 0x140
(II) RADEON(0): Will use depth buffer at offset 0x190
(II) RADEON(0): Will use 100352 kb for textures at offset 0x1e0
(II) RADEON(0): Render acceleration enabled
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)


Not sure what all of that means

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#322501: lincity-ng: crashes, segmentation faults, etc.

[Greg Wooledge]

 image images/tiles/industrylm3.png
GameView::readImage# Could not load image images/tiles/industrylm4.png
GameView::readImage# Could not load image images/tiles/industrylh1.png
GameView::readImage# Could not load image images/tiles/industrylh2.png
GameView::readImage# Could not load image images/tiles/industrylh3.png
GameView::readImage# Could not load image images/tiles/industrylh4.png
GameView::readImage# Could not load image images/tiles/farm0.png
GameView::readImage# Could not load image images/tiles/farm3.png
GameView::readImage# Could not load image images/tiles/farm7.png
GameView::readImage# Could not load image images/tiles/farm11.png
GameView::readImage# Could not load image images/tiles/farm15.png
Unexpected exception: Couldn't create texture: out of memory
Vertex3f: 1
crashed

So that wasn't helpful.  But at least SDL works.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#322501: lincity-ng: crashes, segmentation faults, etc.

[Greg Wooledge]

Package: lincity-ng
Version: 1.0.1-1
Severity: normal


The game seems to be highly unstable on my machine.

CRASH #1:

  The first time I ran it without any options.  It started in full screen
  mode.  I looked at Options, then clicked Continue since it was the
  first button.  The day timer in the lower left was running rather quickly,
  so I tried desperately to pause the game so I could figure out what to do!
  (I've played the original lincity but it's been a while.)  I rolled the
  mouse over some icons but couldn't figure out what they meant, and there
  were no tooltips visible.  I pressed the space bar too, hoping that might
  pause it.

  Some time during all that, the game froze up.  The sound kept playing, but
  clicking anywhere or pressing any keys had no effect.  I had to Ctrl-Alt-F2
  to a text console, kill the game with -9 (normal kill didn't work), and
  then use xrandr to put my X display back to the correct size.

  The tty showed:

  griffon:~$ lincity-ng 
  Starting lincity-ng (version 1.0.1)...
  [/home/greg/.lincity] is in the search path.
  [/usr/share/lincity-ng] is in the search path.
  LINCITY_HOME: /usr/share/lincity-ng
  OpenGL Mode 1024x768
  Killed

CRASH #2:

  griffon:~$ lincity-ng -w
  Starting lincity-ng (version 1.0.1)...
  [/home/greg/.lincity] is in the search path.
  [/usr/share/lincity-ng] is in the search path.
  LINCITY_HOME: /usr/share/lincity-ng
  OpenGL Mode 1024x768
  GameView::readImage# Could not load image images/tiles/industryhl7.png
  GameView::readImage# Could not load image images/tiles/industryhl8.png
  GameView::readImage# Could not load image images/tiles/industryhm1.png
  GameView::readImage# Could not load image images/tiles/industryhm2.png
  GameView::readImage# Could not load image images/tiles/industryhm3.png
  GameView::readImage# Could not load image images/tiles/industryhm4.png
  GameView::readImage# Could not load image images/tiles/industryhm5.png
  GameView::readImage# Could not load image images/tiles/industryhm6.png
  GameView::readImage# Could not load image images/tiles/industryhm7.png
  GameView::readImage# Could not load image images/tiles/industryhm8.png
  GameView::readImage# Could not load image images/tiles/industryhh1.png
  GameView::readImage# Could not load image images/tiles/industryhh2.png
  GameView::readImage# Could not load image images/tiles/industryhh3.png
  GameView::readImage# Could not load image images/tiles/industryhh4.png
  GameView::readImage# Could not load image images/tiles/industryhh5.png
  GameView::readImage# Could not load image images/tiles/industryhh6.png
  GameView::readImage# Could not load image images/tiles/industryhh7.png
  GameView::readImage# Could not load image images/tiles/industryhh8.png
  GameView::readImage# Could not load image images/tiles/industrylq1.png
  GameView::readImage# Could not load image images/tiles/industrylq2.png
  GameView::readImage# Could not load image images/tiles/industrylq3.png
  GameView::readImage# Could not load image images/tiles/industrylq4.png
  GameView::readImage# Could not load image images/tiles/industryll1.png
  GameView::readImage# Could not load image images/tiles/industryll2.png
  GameView::readImage# Could not load image images/tiles/industryll3.png
  GameView::readImage# Could not load image images/tiles/industryll4.png
  GameView::readImage# Could not load image images/tiles/industrylm1.png
  GameView::readImage# Could not load image images/tiles/industrylm2.png
  GameView::readImage# Could not load image images/tiles/industrylm3.png
  GameView::readImage# Could not load image images/tiles/industrylm4.png
  GameView::readImage# Could not load image images/tiles/industrylh1.png
  GameView::readImage# Could not load image images/tiles/industrylh2.png
  GameView::readImage# Could not load image images/tiles/industrylh3.png
  GameView::readImage# Could not load image images/tiles/industrylh4.png
  GameView::readImage# Could not load image images/tiles/farm0.png
  GameView::readImage# Could not load image images/tiles/farm3.png
  GameView::readImage# Could not load image images/tiles/farm7.png
  GameView::readImage# Could not load image images/tiles/farm11.png
  GameView::readImage# Could not load image images/tiles/farm15.png
  Unexpected exception: Couldn't create texture: out of memory

  The PNG files are present and readable with a standalone viewer program
  (at least the first one is).

CRASH #3:

  griffon:~$ lincity-ng -w
  Starting lincity-ng (version 1.0.1)...
  [/home/greg/.lincity] is in the search path.
  [/usr/share/lincity-ng] is in the search path.
  LINCITY_HOME: /usr/share/lincity-ng
  OpenGL Mode 1024x768
  GameView::readImage# Could not load image images/tiles/industryhl7.png
  GameView::readImage# Could not load image images/tiles/industryhl8.png
  GameView::readImage# Could not load image images/tiles/industryhm1.png
  GameView::readImage# Could not load image images/tiles/industryhm2.png
  GameView::readImage# Could not load image 

Bug#318417: findutils: man page corrections

[Greg Wooledge]

Package: findutils
Version: 4.2.22-2
Severity: minor
Tags: patch


The man page has a few errors which I have spotted.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.31
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)

Versions of packages findutils depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an

-- no debconf information
--- find.1.orig 2005-07-14 21:51:12.0 -0400
+++ find.1  2005-07-14 22:02:59.0 -0400
@@ -233,7 +233,7 @@
 was last accessed, any fractional part is ignored, so to match 
 .B \-atime 
 .BR +1 ,
-a file has to have been modified at least 
+a file has to have been accessed at least 
 .I two
 days ago.
 .IP \-cmin \fIn\fR
@@ -1041,15 +1041,15 @@
 
 .P
 .nf
-.B find /  \t( \-perm +4000 \-fprintf /root/suid.txt '%#m %u %p\en' ) , \e
-.B \t\t( \-size +100M \-fprintf /root/big.txt  '%\-10s %p\en'  )
+.B find /  \t\e( \-perm +4000 \-fprintf /root/suid.txt '%#m %u %p\en' \e) , \e
+.B   \t\t\e( \-size +100M \-fprintf /root/big.txt  '%\-10s %p\en' \e)
 
 .fi
 Traverse the filesystem just once, listing setuid files and
 directories into
 .B /root/suid.txt
 and large files into 
-.BR /root/big/txt .
+.BR /root/big.txt .
 
 .P
 .nf
@@ -1058,9 +1058,9 @@
 .fi
 Search for files in your home directory which have been modified in
 the last twenty-four hours.  This command works this way because the
-time since each file was last accessed is divided by 24 hours and any 
+time since each file was last modified is divided by 24 hours and any 
 remainder is discarded.  That means that to match 
-.B -atime 
+.B -mtime 
 .BR 0 ,
 a file will have to have a modification in the past which is less than
 24 hours ago.
@@ -1082,7 +1082,7 @@
 
 .fi
 Search for files which have read and write permission for their owner,
-and group, but which the rest of the world can read but not write to,
+and group, and which the rest of the world can read,
 without regard to the presence of any extra permission bits (for
 example the executable bit).  This will match a file which has mode
 0777, for example.

Bug#315677: gnupg: freezes when checking a signature (corrupted trustdb)

[Greg Wooledge]

Package: gnupg
Version: 1.4.1-1
Severity: normal


Actually this is a two-part bug report.  The first part is an assertion
failure:

griffon:~$ gpg --recv-keys 808D0FD0
gpg: requesting key 808D0FD0 from hkp server subkeys.pgp.net
gpg: key 808D0FD0: public key Don Armstrong [EMAIL PROTECTED] imported
gpg: ../../g10/keyring.c:1388: keyring_rebuild_cache: Assertion 
`keyblock-pkt-pkttype == PKT_PUBLIC_KEY' failed.
Aborted

That key ID was taken from an old e-mail while I was going through my
backlog of messages.  After the failure above, I attempted to reopen the
message in mutt.  The bottom line says Invoking PGP... and sits there
for a very long time (it's been 6 minutes at the time I'm writing -- it
should only be a second or two at most on this machine).

The process looks like this:

USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
greg  7418  0.0  0.2   4476  1436 pts/9SL+  22:14   0:00 gpg 
--status-fd=2 --no-verbose --quiet --batch --output - --verify 
/tmp/mutt-griffon-1000-692-428.asc /tmp/mutt-griffon-1000-692-428

Ctrl-G in mutt does not interrupt the PGP (gpg) process.  I have to kill
it manually to regain control over mutt.  When I do that, the message
opens and looks like this:

[-- PGP output follows (current time: Mon 20 Jun 2005 10:14:31 PM EDT) --]
gpg: Signature made Thu 09 Jun 2005 06:09:12 PM EDT using DSA key ID 808D0FD0
gpg: checking the trustdb
gpg: waiting for lock (held by 7397 - probably dead) ...
gpg: waiting for lock (held by 7397 - probably dead) ...
[etc.]
gpg: waiting for lock (held by 7397 - probably dead) ...

gpg: Terminated caught ... exiting
[-- End of PGP output --]

There is no process 7397.

My inbox is a Maildir in my home directory, and my home directory is an NFS
file system (OpenBSD 3.7 NFS server) with the following options:

pegasus:/home on /home type nfs (rw,nolock,addr=192.168.2.1)

Opening a different PGP-signed message (for which no key exists in my
keyring yet) works fine.  However, opening any message that has been
signed by a key that I *do* have in my keyring (even my own) triggers
this problem.

I looked through bugs.debian.org/gnupg and it appears that bug#310328
is probably related to my problem.  At least, we have the held by  -
probably dead part in common.

Here's what my .gnupg directory looks like right now:

griffon:~$ ls -lart .gnupg
total 1060
-rw---1 greg greg   4875 2004-10-13 18:53 secring.gpg
-rw-rw-r--1 greg greg412 2004-10-13 18:54 options
drwxr-xr-x  150 greg greg  19456 2005-06-20 20:16 ../
-rw---1 greg greg600 2005-06-20 20:16 random_seed
-rw-r--r--2 greg greg 11 2005-06-20 22:12 secring.gpg.lock
-rw-r--r--2 greg greg 11 2005-06-20 22:12 pubring.gpg.lock
-rw-r--r--1 greg greg 509614 2005-06-20 22:12 pubring.gpg~
-rw-r--r--2 greg greg 11 2005-06-20 22:12 .#lk0x81193f0.griffon.7397
-rw-r--r--1 greg greg 11 2005-06-20 22:12 .#lk0x8116ee0.griffon.7397
-rw-r--r--2 greg greg 11 2005-06-20 22:12 .#lk0x8115b70.griffon.7397
-rw-rw-r--1 greg greg   1280 2005-06-20 22:12 trustdb.gpg
-rw-r--r--1 greg greg 510525 2005-06-20 22:12 pubring.gpg
-rw---1 greg greg 11 2005-06-20 22:32 .#lk0x811bb18.griffon.7492
-rw---1 greg greg 11 2005-06-20 22:32 .#lk0x8115cf8.griffon.7492
drwx--2 greg greg512 2005-06-20 22:32 ./

griffon:~$ grep -v '^#' .gnupg/options 
keyring ~/.gnupg/pubring.gpg
secret-keyring ~/.gnupg/secring.gpg
default-key 486BE64C
keyring ~/.pgp/pubring.pgp
secret-keyring ~/.pgp/secring.pgp
keyserver subkeys.pgp.net
keyserver-options no-auto-key-retrieve
no-secmem-warning

Next, I made sure there were no gpg processes running, and then I removed
all the .#lk* files.  However, this did *not* fix the problem.  Attempting
to open a signed message with a known key did exactly the same thing (hung
gpg process).  Here's the new process:

greg  7552  0.0  0.2   4476  1396 pts/9SL+  22:54   0:00 gpg 
--status-fd=2 --no-verbose --quiet --batch --output - --verify 
/tmp/mutt-griffon-1000-692-443.asc /tmp/mutt-griffon-1000-692-443

And the new lock files:

-rw---1 greg greg 11 2005-06-20 22:54 .#lk0x811bb18.griffon.7552
-rw---1 greg greg 11 2005-06-20 22:54 .#lk0x8115cf8.griffon.7552

When I killed process 7552, I got this in mutt:

gpg: waiting for lock (held by 7397 - probably dead) ...

So I did the same thing *again* -- killed all the gpg processes, verified
that there were no .#lk* files, and also removed the *.lock files from
.gnupg.  It *still* hangs with the same message (held by 7397).  I don't
even know where it's getting 7397 from now, but it's pretty much stuck.

Just for the record, I can't do a --list-keys now either.

griffon:~$ gpg --list-keys wooledge
gpg: checking the trustdb
gpg: waiting for lock (held by 7397 - probably dead) ...
gpg: waiting for lock (held by 7397 - probably dead) ...

(I get a new line every few seconds until I hit ctrl-C.)

So, just 

Bug#310596: autofs: several mounts hanging on login (reverting to -7 fixes it)

[Greg Wooledge]

Package: autofs
Version: 4.1.3+4.1.4beta2-10
Severity: important

I have a sarge server which uses autofs.  When I did a dist-upgrade on
it today, from autofs 4.1.3+4.1.4beta2-7 to 4.1.3+4.1.4beta2-10, my
normal user login hung for a very long time because autofs got hung up for
several minutes on each of several different paths that it was checking.
(Eventually I did get a login shell prompt, but it took roughly 20-30
minutes!)  I even rebooted the server, thinking that stopping and
restarting the userspace automount daemons had caused it to get into a
broken state (which I have seen happen before on another Debian system).
The reboot made no difference.

I logged in as root (directly through ssh) while this was going on, and
strace'd my login shell:

wooledg  27089  0.0  0.1  2624 1108 pts/2Ss+  08:00   0:00 -ksh

# strace -p 27089
Process 27089 attached - interrupt to quit
open(/net/home/wooledg/bin/.paths, O_RDONLY|O_LARGEFILE) = -1 ENOENT
(No such file or directory)
open(/usr/bin/.paths, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file
or directory)
open(/bin/.paths, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or
directory)
open(/usr/bin/X11/.paths, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such
file or directory)
stat64(/usr/contrib/bin/X11, 0xbfffde50) = -1 ENOENT (No such file or
directory)
open(/etc/.paths, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or
directory)
stat64(/net/appl/netscape, 0xbfffde50) = -1 ENOENT (No such file or
directory)
stat64(/net/appl/tool/share/bin, 0xbfffde50) = -1 ENOENT (No such file
or directory)
stat64(/net/appl/clin/bin, 0xbfffde50) = -1 ENOENT (No such file or
directory)
umask(0)= 022
umask(022)  = 0
stat64(/usr/local/bin/uname, 0xbfffeb80) = -1 ENOENT (No such file or
directory)
[...]

/net/home/wooledg is my home directory, which is mounted by autofs.
This one works fine.  I was able to see it in df, and I was able to
get a listing of the files therein, as root, while all this was
happening.

/net/appl/netscape and /net/appl/tool/share/bin and
/net/appl/clin/bin, among others, are directories that are in my $PATH
and which are all mounted by autofs.  None of these were working
properly.  The stat64() calls took several minutes each to time out.

Downgrading to autofs 4.1.3+4.1.4beta2-7 fixes this problem for me.  My
user login works as expected once again.

Here's my configuration files, since they don't appear to be attached at
the bottom of this bug report automatically.  (Hopefully they won't be
attached later)

arc1:/# grep -v '^#' /etc/auto.master
/nfs/etc/auto.net
+auto.master

arc1:/# ypcat -k auto.master
/net/vol auto.vol   -rw,hard,intr
/net/appl auto.appl -rw,hard,intr
/net/hosts -hosts   -rw,hard,intr
/net/home auto.home -rw,hard,intr

arc1:/# ypmatch wooledg auto.home
imadev:/home/wooledg

^^^ That's the one that works fine.  imadev is an HP-UX 10.20 box.

arc1:/# ypmatch netscape auto.appl
svr2:/dsk/3/netscape:${PLATFORM}${ARCH}${OSNAME}${OSREL}

^^^ That's one of the ones that fail.  svr2 is an i386 Red Hat Linux 6.2 box.

arc1:/# ypmatch tool auto.appl
svr2:/dsk/3/tool:${PLATFORM}${ARCH}${OSNAME}${OSREL}

^^^ Another example.  They all pretty much follow this pattern.


Here's part of the /var/log/daemon.log file:

May 24 09:06:28 arc1 automount[1734]:  mount: RPC: Remote system error - 
Connection timed out
May 24 09:06:28 arc1 automount[1734]: mount(nfs): nfs: mount failure 
svr2:/dsk/3/tool/i686Linux2.4.27-2-686 on /net/appl/tool
May 24 09:06:28 arc1 automount[1734]: failed to mount /net/appl/tool
May 24 09:13:47 arc1 automount[19818]:  mount: RPC: Remote system error - 
Connection timed out
May 24 09:13:47 arc1 automount[19818]: mount(nfs): nfs: mount failure 
svr2:/dsk/3/tool/i686Linux2.4.27-2-686 on /net/appl/tool
May 24 09:13:47 arc1 automount[19818]: failed to mount /net/appl/tool
May 24 09:14:45 arc1 automount[29279]: failed to mount /net/appl/tool
May 24 09:14:47 arc1 automount[29280]: failed to mount /net/appl/netscape
May 24 09:14:47 arc1 automount[29281]:  mount: 
svr1:/dsk/2/clin/i686Linux2.4.27-2-686 failed, reason given by server: 
Permission denied
May 24 09:14:47 arc1 automount[29281]: mount(nfs): nfs: mount failure 
svr1:/dsk/2/clin/i686Linux2.4.27-2-686 on /net/appl/clin
May 24 09:14:47 arc1 automount[29281]: failed to mount /net/appl/clin


I can see two distinct problems in the log.  The first is the long
Connection timed out problem which repeats a few times.  The second is
the Permission denied, because I have forgotten to make an
i686Linux2.4.27-2-686 symlink over on svr2.  But reverting to autofs -7
makes the timeouts not happen:

May 24 09:35:50 arc1 automount[9730]: failed to mount /net/appl/tool
May 24 09:35:54 arc1 automount[9732]:  mount: 
svr1:/dsk/2/clin/i686Linux2.4.27-2-686 failed, reason given by server: 
Permission denied
May 24 09:35:54 arc1 automount[9732]: mount(nfs): nfs: mount failure 

Bug#310596: additional info...

[Greg Wooledge]

Oops... some additional information that I just learned.

I had the wrong IP address for svr2 in the /etc/hosts file.  Connections
to the old IP would have timed out.  So perhaps -10 is using /etc/hosts
preferentially whereas -7 used DNS preferentially, for name resolution.


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

Bug#310596: autofs: several mounts hanging on login (reverting to -7 fixes it)

[Greg Wooledge]

On Tue, May 24, 2005 at 06:49:56PM +0200, Steinar H. Gunderson wrote:
 On Tue, May 24, 2005 at 09:58:31AM -0400, Greg Wooledge wrote:
  I have a sarge server which uses autofs.  When I did a dist-upgrade on
  it today, from autofs 4.1.3+4.1.4beta2-7 to 4.1.3+4.1.4beta2-10, my
  normal user login hung for a very long time because autofs got hung up for
  several minutes on each of several different paths that it was checking.
  (Eventually I did get a login shell prompt, but it took roughly 20-30
  minutes!)
 
 Would you mind trying -8? It should be available from snapshot.debian.net.

All right, I've tried a few combinations of things now.

-8 and -10 both behave the same way for me.  If the correct address for
svr2 appears in /etc/hosts, then they work great.  If the incorrect
address for svr2 appears in /etc/hosts, then they hang on login as it
attempts to hit svr2 multiple times, and each mount command has to time
out after talking to a nonresponsive IP address.

With -7 there is no significant delay when the wrong IP address appears
in /etc/hosts.  The mounts fail immediately.

Clearly this is a configuration error on my part, but there has definitely
been a change in the software between -7 and -8 involving either name
lookups, or the behavior with respect to down hosts.

You can lower the severity on this one, if you still consider it a bug at
all.


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

Bug#280707: and you can't do it with sudo or su either!

[Greg Wooledge]

griffon:/var/tmp$ sudo make-jpkg jdk-1_5_0_03-linux-i586.bin 
You are real root -- unfortunately, some Java distributions have
install scripts that directly manipulate /etc, and may cause some
inconsistencies on your system. Instead, you should become a
non-root user and run:

fakeroot make-jpkg jdk-1_5_0_03-linux-i586.bin

which will allow no damage to be done to your system files and
still permit the Java distribution to successfully extract.

Aborting.

griffon:/var/tmp$ fakeroot make-jpkg jdk-1_5_0_03-linux-i586.bin 
Creating temporary directory: /tmp/make-jpkg.uRNUIH
[...]
Do you agree to the above license terms? [yes or no] 
yes
[...]
/var/tmp/jdk-1_5_0_03-linux-i586.bin: line 523: 
/usr/share/application-registry/java-web-start.applications: Permission denied
/var/tmp/jdk-1_5_0_03-linux-i586.bin: line 524: 
/usr/share/application-registry/java-web-start.applications: Permission denied
 
Done.

Testing extracted archive...
Invalid size (128 MB) of extracted archive. Probably you have not
enough free disc space in the temporary directory. Note: You can
specify an alternate directory by setting the environment variable
TMPDIR.


Aborted.

Removing temporary directory: done

griffon:/var/tmp$ su
Password: 
griffon:/var/tmp# make-jpkg jdk-1_5_0_03-linux-i586.bin 
You are real root -- unfortunately, some Java distributions have
install scripts that directly manipulate /etc, and may cause some
inconsistencies on your system. Instead, you should become a
non-root user and run:

fakeroot make-jpkg jdk-1_5_0_03-linux-i586.bin

which will allow no damage to be done to your system files and
still permit the Java distribution to successfully extract.

Aborting.

-- 
Greg Wooledge  |   Truth belongs to everybody.
[EMAIL PROTECTED]  |- The Red Hot Chili Peppers
http://wooledge.org/~greg/ |


signature.asc
Description: Digital signature

Bug#298623: installation report (i386 laptop failure)

[Greg Wooledge]

On Wed, Mar 09, 2005 at 12:09:43AM +0100, Frans Pop wrote:
 The dump probably happens because the OSS (i810_audio) audio driver does 
 not like something about your hardware. I think you will have more luck 
 with the ALSA (snd_intel8x0) modules. I would think this problem should 
 be solved after you install the alsa packages as IIRC they include 
 blacklisting for the OSS modules.
 
 Can you confirm if this is correct?

Yes, the ALSA module loads without problems.  I can't verify whether
installing the alsa-* packages blacklists the i810_audio driver, because
I no longer have the laptop with me.  In any event, I kept the manual
blacklist entries in place, because I don't ever want the user to come
back to me saying the laptop doesn't boot, or respond to ctrl-alt-del,
and by the way it says something about Oops and a lot of numbers on
the screen.

(He may have to bring it back to me today, depending on whether I got the
PPPOE configuration right on the first try.  I won't know until later.)

 [1] http://bugs.debian.org/287344 (hp pavilion ze4900)

Same as mine, except that I fumbled around more than he did.

 [2] http://bugs.debian.org/277691 (laptop Dell D600)

Definitely milder symptoms.  He didn't mention having to boot with
init=/bin/sh as I did, or doing any chroot tricks from the install CD.

 [3] http://bugs.debian.org/296188 (HP Pavillion zd8000)

Same symptom as mine.

 P.S.
 My own Toshiba Satellite A40 laptop has:
 i810_audio: Connection 0 with codec id 0
 ac97_codec: AC97 Audio codec, id: ADS116 (Unknown)
 i810_audio: AC'97 codec 0 supports AMAP, total channels = 2
 
 While yours has:
 i810_audio: Connection 0 with codec id 0
 ac97_codec: AC97 Modem codec, id: CXT48 (Unknown)
 i810_audio: codec 0 is a softmodem - skipping.

Hmm.  I don't know whether this is a difference between pre-rc2 and
whichever installer you used, or a difference caused by the presence of
a winmodem.

 It looks like this could be a kernel driver bug.

That was my assumption too.


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

Bug#298623: installation report (i386 laptop failure)

[Greg Wooledge]

Package: installation-reports

Debian-installer-version: pre-rc2 i386 netinstall ISO
uname -a: Linux xxx 2.6.8-1-386 #1 Mon Sep 13 23:29:55 EDT 2004 i686 
GNU/Linux
Date: 2005-03-08
Method: booted from netinstall CD

Machine: gateway 7320GZ laptop
Processor: Pentium IV
Memory: 512 MB (minus 32 MB for the i810 video)
Root Device: IDE disk (hda3 after reboot)
Root Size/partition table:  hda3 = root, ext3, 5.0 GB; hda4 = swap, 257032k
Output of lspci and lspci -n:
# lspci
:00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02)
:00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control 
Registers (rev 02)
:00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration 
Process Registers (rev 02)
:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated 
Graphics Device (rev 02)
:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics 
Device (rev 02)
:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #1 (rev 03)
:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #2 (rev 03)
:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #3 (rev 03)
:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI 
Controller (rev 03)
:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83)
:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03)
:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage 
Controller (rev 03)
:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 
Modem Controller (rev 03)
:01:04.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A 
IEEE-1394a-2000 Controller (PHY/Link)
:01:05.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus 
Controller
:01:06.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 
01)
:01:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g 
Wireless LAN Controller (rev 03)

# lspci -n
:00:00.0 0600: 8086:3580 (rev 02)
:00:00.1 0880: 8086:3584 (rev 02)
:00:00.3 0880: 8086:3585 (rev 02)
:00:02.0 0300: 8086:3582 (rev 02)
:00:02.1 0380: 8086:3582 (rev 02)
:00:1d.0 0c03: 8086:24c2 (rev 03)
:00:1d.1 0c03: 8086:24c4 (rev 03)
:00:1d.2 0c03: 8086:24c7 (rev 03)
:00:1d.7 0c03: 8086:24cd (rev 03)
:00:1e.0 0604: 8086:2448 (rev 83)
:00:1f.0 0601: 8086:24cc (rev 03)
:00:1f.1 0101: 8086:24ca (rev 03)
:00:1f.5 0401: 8086:24c5 (rev 03)
:00:1f.6 0703: 8086:24c6 (rev 03)
:01:04.0 0c00: 104c:8023
:01:05.0 0607: 104c:ac56
:01:06.0 0200: 14e4:4401 (rev 01)
:01:09.0 0280: 14e4:4320 (rev 03)

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [E]

Comments/Problems:

Everything works fine (except that I get the red screen if I boot linux26),
until after rebooting the installed kernel-image.  Then it fails, with
either linux (2.4.27) or linux26 (2.6.8).  Both of them Oops in the same
manner.  I'll show the 2.6.8 output here:

(This is the first line in the Shift-PageUp buffer on tty1.)
PnPBIOS: You may need to reboot with the nobiospnp option to operate stably
PnPBIOS: Check with your vendor for an updated BIOS
PnPBIOS: get_dev_node: unexpected status 0x28
PnPBIOS: 12 nodes reported by PnP BIOS: 12 recorded by driver
PCI: Using ACPI for IRQ routing
ACPI: PCI interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 169
[[ 11 more lines like that ]]
...
[[ lots of normal-looking stuff skipped ]]
...
INIT: version 2.86 booting
null symbol found
null symbol found
Activating swap.
Adding 257032k swap on /dev/hda4.  Priority:-1 extents:1
Checking root file system...
fsck 1.35 (28-Feb-2004)
/: clean, 16252/611648files, 76255/1220940 blocks
EXT3 FS on hda3, internal journal
Real Time Clock Driver v1.12
System time was Tue Mar  8 10:00:00 UTC 2005.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Tue Mar  8 10:00:02 UTC 2005.
Calculating module dependencies... done.
Loading modules...
ide-cd
hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-generic
sbp2
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins [EMAIL PROTECTED]
sr_mod
All  modules loaded.
Capability LSM initialized
Checking all file systems...
fsck 1.35 (28-Feb-2004)
Setting kernel variables ...
... done.
Mounting local filesystems...
Cleaning /tmp /var/run /var/lock.
Detecting hardware: