Bug#315615: autofs: Bad ordering of /etc/rc2.d/ files for NIS and AUTOFS

[Matt Weatherford]

Package: autofs
Version: 4.1.4-11
Followup-For: Bug #315615

To get this working, I moved the autofs startup to after the nis and
NFS startups...

I re-ordered /etc/rc2.d/ files by moving S19autofs to S25autofs

This works for me, as NIS and NFS start up before autofs

-Matt


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

Versions of packages autofs depends on:
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  ucf  2.0014  Update Configuration File: preserv

Versions of packages autofs recommends:
ii  nfs-common1:1.0.10-1 NFS support files common to client

-- no debconf information


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

Bug#409289: xserver-xorg-video-nv: xserver-x.org becomes sluggish and keyboard unresponsive

[Matt Weatherford]

Sure, next time it hangs I, I will gather the script and Xorg.log
output and send it in.
Prob. mon or tues at the earliest.

Thanks for all your hard work on the X subsystem, it must be a real
labor of love.

-Matt


Brice Goglin wrote:
 Matt Weatherford wrote:
   
 xorg takes up 99.7% of CPU as reported by TOP
   
 

 Could you try to attach a strace to the xorg process in case there is
 something interesting to see?

 Also, please send us the output of  /usr/share/bug/xserver-xorg/script ?
 (or at least your xorg.conf and Xorg.0.log).

   
 xorg sluggish or has Dramatic pauses when using IceDove

 xorg locked up in rdesktop session after 2 minutes of using it
 mouse pointer moves, clicks do nothing, keyboard locked up.
 Couldnt ctrl-alt-f1 into console.  Had to remotely log in with
 ssh and kill xorg
   
 

 Does something new appear in Xorg.0.log after this lockup? what about
 dmesg ?

 Brice


   



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

Bug#409289: xserver-xorg-video-nv: xserver-x.org becomes sluggish and keyboard unresponsive

[Matt Weatherford]

Package: xserver-xorg-video-nv
Version: 1:1.2.0-3
Severity: normal




Fresh, New Etch install as of 1/25 - from daily build CD
All updates taken (libc6, locales) this AM and rebooted

xorg takes up 99.7% of CPU as reported by TOP
xorg sluggish or has Dramatic pauses when using IceDove

xorg locked up in rdesktop session after 2 minutes of using it
mouse pointer moves, clicks do nothing, keyboard locked up.
Couldnt ctrl-alt-f1 into console.  Had to remotely log in with
ssh and kill xorg


This system is a Dell Precision 370


lspci output:

io:/net/home/mbw/admin# lspci
00:00.0 Host bridge: Intel Corporation 925X/XE Express Memory Controller Hub 
(rev 04)
00:01.0 PCI bridge: Intel Corporation 925X/XE Express PCI Express Root Port 
(rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) AC'97 Audio Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface 
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA 
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV37GL [Quadro FX 
330/Quadro NVS280] (rev a2)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit 
Ethernet PCI Express (rev 01)
io:/net/home/mbw/admin#



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

Versions of packages xserver-xorg-video-nv depends on:
ii  libc6   2.3.6.ds1-10 GNU C Library: Shared libraries
ii  xserver-xorg-core   2:1.1.1-15   X.Org X server -- core server

xserver-xorg-video-nv recommends no packages.

-- no debconf information


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

Bug#409289: xserver-xorg-video-nv: xserver-x.org becomes sluggish and keyboard unresponsive

[Matt Weatherford]

Brice,

Im using the Etch Stable release now on x86 hardware with the NVidia card,
it seems to be ok... sometimes I get dramatic pauses in Icedove, but
im not sure what app is responsible for that  havent had a chance to 
profile it.


I dont use unstable.

Thanks for asking... I hope you find some good testers for this.

Thank you for your contributions to Open Source in general and debian in 
particular!


-Matt


Brice Goglin wrote:

Hi Matt,

A couple months ago, you reported a bug to the Debian BTS regarding Xorg
being
very slow on a nVidia board. Did you reproduce this problem recently?
With the
latest xserver-xorg-video-nv driver 2.0.2 in unstable?

thanks,
Brice

  




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

Bug#315615: autofs: Autofs starts before NIS in boot sequence

[Matt Weatherford]

Package: autofs
Version: 4.1.4-8
Followup-For: Bug #315615


Looks like autofs starts before NIS in the boot sequence:

S19autofs@
S19nis@

since these are both in /etc/rc2.d and both S19, the start
order is alphabetically determined, and autofs starts first.

This causes problems when autofs references an NIS map as in the
following example: (In /etc/auto.master)

 /net   yp:auto_net -nosuid,tcp,soft

One possible Solution:  

rename S19autofs to S20autofs, it should still start before
all the other S20 stuff I see in /etc/rc2.d

? dont know the impact of this on other startup stuff ?

Thanks for your efforts!

-Matt



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-generic
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages autofs depends on:
ii  libc6 2.3.5-8.1  GNU C Library: Shared libraries an
ii  ucf   2.004  Update Configuration File: preserv

Versions of packages autofs recommends:
ii  nfs-common1:1.0.7-3  NFS support files common to client

-- no debconf information


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

Bug#349931: kde-clock.desktop: Can set the time zone after entering root password, but time zone does not stay set

[Matt Weatherford]

Package: kde-clock.desktop
Severity: important


Time zone changes thru /usr/bin/kcmshell kde-clock.desktop appear
to be changed by user input (after entering root password) but 
new settings do not stay set.  Reverts to UTC after closing the tool.




-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-generic
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)


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

Bug#467464: icedove crashes sometimes after SMTP send w/tls on port 587

[Matt Weatherford]

Package: icedove
Version: 1.5.0.13+1.5.0.15b.dfsg1-0etch1
Severity: important


Not sure if this is SMTP send or SMTP TLS related... outgoing mail seems
to get sent ok, and copy placed in the sent-mail folder... but icedove
closes out all windows afterwards. This is difficult to reproduce -
happens a couple of times during a normal emailing workday for me. 

I have multiple IMAP3 and IMAP4 mail boxes, only 1 single POP mail box.

I have been copying and carrying around my profile directory for at
least a year and moved it from machine to machine, version to version,
but this is the first time I have seen this problem.

I have another user in my office who is on the exact same Debian
distro, on the same network, using the same exact Dell Optiplex model as
I am, and she has reported this problem to me as well.  Her mail setup
is much simpler than mine, but uses the same UW-IMAP (vsn 4) remote
mailstore and SMTP server. 

If I can provide a log or something, please ask..

Matt


-- 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-6-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages icedove depends on:
ii  debconf [debconf-2.0]  1.5.11etch1   Debian configuration management sy
ii  libatk1.0-01.12.4-3  The ATK accessibility toolkit
ii  libc6  2.3.6.ds1-13etch5 GNU C Library: Shared libraries
ii  libcairo2  1.2.4-4   The Cairo 2D vector graphics libra
ii  libfontconfig1 2.4.2-1.2 generic font configuration library
ii  libgcc11:4.1.1-21GCC support library
ii  libglib2.0-0   2.12.4-2  The GLib library of C routines
ii  libgtk2.0-02.8.20-7  The GTK+ graphical user interface 
ii  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
ii  libpango1.0-0  1.14.8-5  Layout and rendering of internatio
ii  libstdc++6 4.1.1-21  The GNU Standard C++ Library v3
ii  libx11-6   2:1.0.3-7 X11 client-side library
ii  libxcursor11.1.7-4   X cursor management library
ii  libxext6   1:1.0.1-2 X11 miscellaneous extension librar
ii  libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio
ii  libxft22.1.8.2-8 FreeType-based font drawing librar
ii  libxi6 1:1.0.1-4 X11 Input extension library
ii  libxinerama1   1:1.0.1-4.1   X11 Xinerama extension library
ii  libxrandr2 2:1.1.0.2-5   X11 RandR extension library
ii  libxrender11:0.9.1-3 X Rendering Extension client libra
ii  libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii  myspell-en-us [myspell 1:2.0.4~rc1-3 English_american dictionary for my
ii  zlib1g 1:1.2.3-13compression library - runtime

icedove recommends no packages.

-- debconf information:
  icedove/browser: Debian



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

Bug#567422: xpvm crashes on startup

[Matt Weatherford]

Package: xpvm
Version: 1.2.5-12
Severity: important


n2:~/RDS/GroupRDS/Cori/NewNetworks xpvm 
[2] 7371
n2:~/RDS/GroupRDS/Cori/NewNetworks Connecting to PVMD already running... XPVM 
1.2.5 connected as TID=0x40098.
[globs.tcl][procs.tcl][util.tcl]
Initializing XPVM.. done.
*** glibc detected *** /usr/lib/pvm3/bin/rsh: free(): invalid next size (fast): 
0xb7bcbfd0 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb73cf624]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb73d1826]
/usr/lib/pvm3/bin/rsh[0xb77c5cdd]
/usr/lib/pvm3/bin/rsh[0xb77c3280]
/usr/lib/pvm3/bin/rsh[0xb77c8d5b]
/usr/lib/pvm3/bin/rsh[0xb77ac748]
/usr/lib/pvm3/bin/rsh[0xb77a5622]
/usr/lib/pvm3/bin/rsh(main+0x16e4)[0xb779c904]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7377455]
/usr/lib/pvm3/bin/rsh[0xb779ab01]
=== Memory map: 
b710-b7121000 rw-p  00:00 0
b7121000-b720 ---p  00:00 0
b72aa000-b72b6000 r-xp  00:00 0
b72b6000-b72b7000 rw-p  00:00 0
b72b7000-b72c1000 r-xp  00:00 0
b72c1000-b72c3000 rw-p  00:00 0
b72cc000-b7336000 r--p  00:00 0
b7336000-b7338000 rw-p  00:00 0
b7338000-b734d000 r-xp  00:00 0
b734d000-b7351000 rw-p  00:00 0
b7351000-b7353000 r-xp  00:00 0
b7353000-b7355000 rw-p  00:00 0
b7355000-b735c000 r-xp  00:00 0
b735c000-b735d000 rw-p  00:00 0
b735d000-b735f000 r-xp  00:00 0
b735f000-b7361000 rw-p  00:00 0
b7361000-b74b6000 r-xp  00:00 0
b74b6000-b74b7000 r--p  00:00 0
b74b7000-b74bc000 rw-p  00:00 0
b74bc000-b74be000 r-xp  00:00 0
b74be000-b74bf000 rw-p  00:00 0
b74bf000-b74e2000 r-xp  00:00 0
b74e2000-b74e4000 rw-p  00:00 0
b74e4000-b7576000 r-xp  00:00 0
b7576000-b7578000 rw-p  00:00 0
b7578000-b75a1000 r-xp  00:00 0
b75a1000-b75a2000 rw-p  00:00 0
b75a2000-b75ab000 r-xp  00:00 0
b75ab000-b75d4000 rw-p  00:00 0
b75d4000-b75e9000 r-xp  00:00 0
b75e9000-b75ed000 rw-p  00:00 0
b75ed000-b7601000 r-xp  00:00 0
b7601000-b7602000 rw-p  00:00 0
b7602000-b7604000 r-xp  00:00 0
b7604000-b7607000 rw-p  00:00 0
b7607000-b7741000 r-xp  00:00 0
b7741000-b775a000 rw-p  00:00 0
b775a000-b776a000 r-xp  00:00 0
b776a000-b776e000 rw-p  00:00 0
b000-b7779000 rw-p  00:00 0
b7779000-b7793000 r-xp  08:01 2637987/lib/ld-2.7.so
b7793000-b7795000 rw-p 0001a000 08:01 2637987/lib/ld-2.7.so
b7795000-b77e5000 r-xp  08:01 2409174/usr/bin/ssh
b77e5000-b77e6000 rw-p 0005 08:01 2409174/usr/bin/ssh
b77e6000-b77ea000 rw-p  00:00 0
b7bc1000-b7be2000 rw-p  00:00 0  [heap]
bf927000-bf93c000 rw-p  00:00 0  [stack]
*** glibc detected *** /usr/lib/pvm3/bin/rsh: free(): invalid next size (fast): 
0xb84ddfd0 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb74e9624]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb74eb826]
/usr/lib/pvm3/bin/rsh[0xb78dfcdd]
/usr/lib/pvm3/bin/rsh[0xb78dd280]
/usr/lib/pvm3/bin/rsh[0xb78e2d5b]
/usr/lib/pvm3/bin/rsh[0xb78c6748]
/usr/lib/pvm3/bin/rsh[0xb78bf622]
/usr/lib/pvm3/bin/rsh(main+0x16e4)[0xb78b6904]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7491455]
/usr/lib/pvm3/bin/rsh[0xb78b4b01]
=== Memory map: 
b720-b7221000 rw-p  00:00 0
b7221000-b730 ---p  00:00 0
b73c4000-b73d r-xp  00:00 0
b73d-b73d1000 rw-p  00:00 0
b73d1000-b73db000 r-xp  00:00 0
b73db000-b73dd000 rw-p  00:00 0
b73e6000-b745 r--p  00:00 0
b745-b7452000 rw-p  00:00 0
b7452000-b7467000 r-xp  00:00 0
b7467000-b746b000 rw-p  00:00 0
b746b000-b746d000 r-xp  00:00 0
b746d000-b746f000 rw-p  00:00 0
b746f000-b7476000 r-xp  00:00 0
b7476000-b7477000 rw-p  00:00 0
b7477000-b7479000 r-xp  00:00 0
b7479000-b747b000 rw-p  00:00 0
b747b000-b75d r-xp  00:00 0
b75d-b75d1000 r--p  00:00 0
b75d1000-b75d6000 rw-p  00:00 0
b75d6000-b75d8000 r-xp  00:00 0
b75d8000-b75d9000 rw-p  00:00 0
b75d9000-b75fc000 r-xp  00:00 0
b75fc000-b75fe000 rw-p  00:00 0
b75fe000-b769 r-xp  00:00 0
b769-b7692000 rw-p  00:00 0
b7692000-b76bb000 r-xp  00:00 0
b76bb000-b76bc000 rw-p  00:00 0
b76bc000-b76c5000 r-xp  00:00 0
b76c5000-b76ee000 rw-p  00:00 0
b76ee000-b7703000 r-xp  00:00 0
b7703000-b7707000 rw-p  00:00 0
b7707000-b771b000 r-xp  00:00 0
b771b000-b771c000 rw-p  00:00 0
b771c000-b771e000 r-xp  00:00 0
b771e000-b7721000 rw-p  00:00 0
b7721000-b785b000 r-xp  00:00 0
b785b000-b7874000 rw-p  00:00 0
b7874000-b7884000 r-xp  00:00 0
b7884000-b7888000 rw-p  00:00 0

Bug#567421: pvm crash possibly related to rsh

[Matt Weatherford]

Package: pvm
Version: 3.4.5-11
Severity: important


Crash:

n2:~/RDS/GroupRDS/Cori/NewNetworks mosrun -b -e nice R CMD BATCH 
create_networks.r 
[1] 6031
n2:~/RDS/GroupRDS/Cori/NewNetworks *** glibc detected *** 
/usr/lib/pvm3/bin/rsh: free(): invalid next size (fast): 0xb8466fd0 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb73e2624]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb73e4826]
/usr/lib/pvm3/bin/rsh[0xb77d8cdd]
/usr/lib/pvm3/bin/rsh[0xb77d6280]
/usr/lib/pvm3/bin/rsh[0xb77dbd5b]
/usr/lib/pvm3/bin/rsh[0xb77bf748]
/usr/lib/pvm3/bin/rsh[0xb77b8622]
/usr/lib/pvm3/bin/rsh(main+0x16e4)[0xb77af904]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb738a455]
/usr/lib/pvm3/bin/rsh[0xb77adb01]
=== Memory map: 
b710-b7121000 rw-p  00:00 0
b7121000-b720 ---p  00:00 0
b72bd000-b72c9000 r-xp  00:00 0
b72c9000-b72ca000 rw-p  00:00 0
b72ca000-b72d4000 r-xp  00:00 0
b72d4000-b72d6000 rw-p  00:00 0
b72df000-b7349000 r--p  00:00 0
b7349000-b734b000 rw-p  00:00 0
b734b000-b736 r-xp  00:00 0
b736-b7364000 rw-p  00:00 0
b7364000-b7366000 r-xp  00:00 0
b7366000-b7368000 rw-p  00:00 0
b7368000-b736f000 r-xp  00:00 0
b736f000-b737 rw-p  00:00 0
b737-b7372000 r-xp  00:00 0
b7372000-b7374000 rw-p  00:00 0
b7374000-b74c9000 r-xp  00:00 0
b74c9000-b74ca000 r--p  00:00 0
b74ca000-b74cf000 rw-p  00:00 0
b74cf000-b74d1000 r-xp  00:00 0
b74d1000-b74d2000 rw-p  00:00 0
b74d2000-b74f5000 r-xp  00:00 0
b74f5000-b74f7000 rw-p  00:00 0
b74f7000-b7589000 r-xp  00:00 0
b7589000-b758b000 rw-p  00:00 0
b758b000-b75b4000 r-xp  00:00 0
b75b4000-b75b5000 rw-p  00:00 0
b75b5000-b75be000 r-xp  00:00 0
b75be000-b75e7000 rw-p  00:00 0
b75e7000-b75fc000 r-xp  00:00 0
b75fc000-b760 rw-p  00:00 0
b760-b7614000 r-xp  00:00 0
b7614000-b7615000 rw-p  00:00 0
b7615000-b7617000 r-xp  00:00 0
b7617000-b761a000 rw-p  00:00 0
b761a000-b7754000 r-xp  00:00 0
b7754000-b776d000 rw-p  00:00 0
b776d000-b777d000 r-xp  00:00 0
b777d000-b7781000 rw-p  00:00 0
b778a000-b778c000 rw-p  00:00 0
b778c000-b77a6000 r-xp  08:01 2637987/lib/ld-2.7.so
b77a6000-b77a8000 rw-p 0001a000 08:01 2637987/lib/ld-2.7.so
b77a8000-b77f8000 r-xp  08:01 2409174/usr/bin/ssh
b77f8000-b77f9000 rw-p 0005 08:01 2409174/usr/bin/ssh
b77f9000-b77fd000 rw-p  00:00 0
b845c000-b847d000 rw-p  00:00 0  [heap]
bfd86000-bfd9b000 rw-p  00:00 0  [stack]
*** glibc detected *** /usr/lib/pvm3/bin/rsh: free(): invalid next size (fast): 
0xb9756fd0 ***
*** glibc detected *** /usr/lib/pvm3/bin/rsh: free(): invalid next size (fast): 
0xb88acfd0 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6[0xb740a624]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb740c826]
/usr/lib/pvm3/bin/rsh[0xb7800cdd]
/usr/lib/pvm3/bin/rsh[0xb77fe280]
/usr/lib/pvm3/bin/rsh[0xb7803d5b]
/usr/lib/pvm3/bin/rsh[0xb77e7748]
/usr/lib/pvm3/bin/rsh[0xb77e0622]
/usr/lib/pvm3/bin/rsh(main+0x16e4)[0xb77d7904]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb73b2455]
/usr/lib/pvm3/bin/rsh[0xb77d5b01]
=== Memory map: 
=== Backtrace: =
b710-b7121000 rw-p  00:00 0
b7121000-b720 ---p  00:00 0
b72e5000-b72f1000 r-xp  00:00 0
b72f1000-b72f2000 rw-p  00:00 0
b72f2000-b72fc000 r-xp  00:00 0
b72fc000-b72fe000 rw-p  00:00 0
b7307000-b7371000 r--p  00:00 0
b7371000-b7373000 rw-p  00:00 0
b7373000-b7388000 r-xp  00:00 0
b7388000-b738c000 rw-p  00:00 0
b738c000-b738e000 r-xp  00:00 0
b738e000-b739 rw-p  00:00 0
b739-b7397000 r-xp  00:00 0
b7397000-b7398000 rw-p  00:00 0
b7398000-b739a000 r-xp  00:00 0
b739a000-b739c000 rw-p  00:00 0
b739c000-b74f1000 r-xp  00:00 0
b74f1000-b74f2000 r--p  00:00 0
b74f2000-b74f7000 rw-p  00:00 0
b74f7000-b74f9000 r-xp  00:00 0
b74f9000-b74fa000 rw-p  00:00 0
b74fa000-b751d000 r-xp  00:00 0
b751d000-b751f000 rw-p  00:00 0
b751f000-b75b1000 r-xp  00:00 0
b75b1000-b75b3000 rw-p  00:00 0
b75b3000-b75dc000 r-xp  00:00 0
b75dc000-b75dd000 rw-p  00:00 0
b75dd000-b75e6000 r-xp  00:00 0
b75e6000-b760f000 rw-p  00:00 0
b760f000-b7624000 r-xp  00:00 0
b7624000-b7628000 rw-p  00:00 0
b7628000-b763c000 r-xp  00:00 0
b763c000-b763d000 rw-p  00:00 0
b763d000-b763f000 r-xp  00:00 0
b763f000-b7642000 rw-p  00:00 0
b7642000-b777c000 r-xp  00:00 0
b777c000-b7795000 rw-p  00:00 0
b7795000-b77a5000 r-xp  00:00 0
b77a5000-b77a9000 rw-p  00:00 0

Bug#567421: Acknowledgement (pvm crash possibly related to rsh)

[Matt Weatherford]

reassign 567421 package ssh


On 01/28/2010 04:09 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  se...@debian.org (Steinar H. Gunderson)

If you wish to submit further information on this problem, please
send it to 567...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

   


--
Matt Weatherford
Computing Core Director
Center for Studies in Demography and Ecology
218H Raitt Hall, Box 353412
University of Washington
Seattle, WA, USA, 98195 206-616-6169
http://csde.washington.edu





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

Bug#567422: Acknowledgement (xpvm crashes on startup)

[Matt Weatherford]

reassign 567422 package ssh

On 01/28/2010 04:09 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian QA Grouppacka...@qa.debian.org

If you wish to submit further information on this problem, please
send it to 567...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

   


--
Matt Weatherford
Computing Core Director
Center for Studies in Demography and Ecology
218H Raitt Hall, Box 353412
University of Washington
Seattle, WA, USA, 98195 206-616-6169
http://csde.washington.edu





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

Bug#593419: Get Mysql errors when I try to run the initial drupal6/install.php

[Matt Weatherford]

Package: drupal6
Version: 6.17-2
Severity: important


After installing Drupal6 package, I go to the web browser and 
click on install drupal in English
This results in the following error in the browser:



* user warning: You have an error in your SQL syntax; check the manual that 
corresponds to your MySQL server version for the right syntax to use near ') 
ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE 
path IN () ORDER BY fit DESC LIMIT 0, 1 in /usr/share/drupal6/includes/menu.inc 
on line 315.
* user warning: You have an error in your SQL syntax; check the manual that 
corresponds to your MySQL server version for the right syntax to use near ') 
ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE 
path IN () ORDER BY fit DESC LIMIT 0, 1 in /usr/share/drupal6/includes/menu.inc 
on line 315.


I am unsure what state drupal6 is in after this point

it looks like a bug... ?




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

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

Versions of packages drupal6 depends on:
ii  apache2   2.2.16-1   Apache HTTP Server metapackage
ii  apache2-mpm-prefork [httpd]   2.2.16-1   Apache HTTP Server - traditional n
ii  curl  7.21.0-1   Get a file from an HTTP, HTTPS or 
ii  dbconfig-common   1.8.46 common framework for packaging dat
ii  debconf [debconf-2.0] 1.5.33 Debian configuration management sy
ii  exim4-daemon-light [mail-tran 4.72-1 lightweight Exim MTA (v4) daemon
ii  mysql-client-5.1 [virtual-mys 5.1.49-1   MySQL database client binaries
ii  php5  5.3.2-1server-side, HTML-embedded scripti
ii  php5-gd   5.3.2-1GD module for php5
ii  php5-mysql5.3.2-1MySQL module for php5
ii  postgresql-client 8.4.4-2front-end programs for PostgreSQL 
ii  postgresql-client-8.4 [postgr 8.4.4-2front-end programs for PostgreSQL 
ii  wwwconfig-common  0.2.1  Debian web auto configuration

Versions of packages drupal6 recommends:
ii  mysql-server-5.1 [mysql-serve 5.1.49-1   MySQL database server binaries and
ii  postgresql8.4.4-2object-relational SQL database (su

drupal6 suggests no packages.

-- debconf information:
  drupal6/mysql/admin-pass: (password omitted)
  drupal6/password-confirm: (password omitted)
  drupal6/pgsql/app-pass: (password omitted)
  drupal6/mysql/app-pass: (password omitted)
  drupal6/pgsql/admin-pass: (password omitted)
  drupal6/app-password-confirm: (password omitted)
  drupal6/pgsql/manualconf:
  drupal6/mysql/method: unix socket
  drupal6/pgsql/authmethod-user:
  drupal6/purge: false
  drupal6/remove-error: abort
  drupal6/dbconfig-upgrade: true
  drupal6/pgsql/admin-user: postgres
  drupal6/install-error: abort
* drupal6/dbconfig-remove:
  drupal6/db/dbname: drupal6
  drupal6/pgsql/changeconf: false
  drupal6/internal/skip-preseed: false
  drupal6/pgsql/method: unix socket
  drupal6/missing-db-package-error: abort
  drupal6/upgrade-error: abort
  drupal6/remote/host:
  drupal6/db/basepath:
  drupal6/passwords-do-not-match:
  drupal6/internal/reconfiguring: false
  drupal6/pgsql/no-empty-passwords:
  drupal6/db/app-user: drupal6
* drupal6/database-type: mysql
  drupal6/upgrade-backup: true
  drupal6/dbconfig-reinstall: false
  drupal6/mysql/admin-user: root
  drupal6/pgsql/authmethod-admin: ident
  drupal6/remote/newhost:
* drupal6/dbconfig-install: true
  drupal6/remote/port:



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

Bug#624228: apt or aptitude wrong permissions on /etc/apt/conf.d/99synaptic file

[Matt Weatherford]

Package: apt
Version: 0.8.10.3
Severity: important



Fresh install of debian6

root@proteus:/etc/apt/apt.conf.d# ls -la
total 56
drwxr-xr-x 2 root root 4096 Apr 25 13:53 .
drwxr-xr-x 6 root root 4096 Apr 26 10:06 ..
-rw-r--r-- 1 root root   81 Apr 20 11:51 00CDMountPoint
-rw-r--r-- 1 root root   40 Apr 20 11:51 00trustcdrom
-rw-r--r-- 1 root root  395 Jan 25 02:57 01autoremove
-rw-r--r-- 1 root root  129 Apr 26 10:04 10periodic
-rw-r--r-- 1 root root  100 Aug  2  2010 15update-stamp
-rw-r--r-- 1 root root   85 Apr 16  2010 20archive
-rw-r--r-- 1 root root  243 Jun  6  2010 20dbus
-rw-r--r-- 1 root root  141 Dec 11 12:31 20listchanges
-rw-r--r-- 1 root root 1169 Nov 17 12:13 50unattended-upgrades
-rw-r--r-- 1 root root  182 Jan 30 10:44 70debconf
-rw-r- 1 root root   32 Apr 26 10:06 99synaptic
-rw-r--r-- 1 root root  231 Apr 18  2010 99update-notifier


**NOTE:  640 permissions on 99synaptic


root@proteus:/etc/apt/apt.conf.d# chmod 644 99synaptic 
root@proteus:/etc/apt/apt.conf.d# ls -la
total 56
drwxr-xr-x 2 root root 4096 Apr 25 13:53 .
drwxr-xr-x 6 root root 4096 Apr 26 10:06 ..
-rw-r--r-- 1 root root   81 Apr 20 11:51 00CDMountPoint
-rw-r--r-- 1 root root   40 Apr 20 11:51 00trustcdrom
-rw-r--r-- 1 root root  395 Jan 25 02:57 01autoremove
-rw-r--r-- 1 root root  129 Apr 26 10:04 10periodic
-rw-r--r-- 1 root root  100 Aug  2  2010 15update-stamp
-rw-r--r-- 1 root root   85 Apr 16  2010 20archive
-rw-r--r-- 1 root root  243 Jun  6  2010 20dbus
-rw-r--r-- 1 root root  141 Dec 11 12:31 20listchanges
-rw-r--r-- 1 root root 1169 Nov 17 12:13 50unattended-upgrades
-rw-r--r-- 1 root root  182 Jan 30 10:44 70debconf
-rw-r--r-- 1 root root   32 Apr 26 10:06 99synaptic
-rw-r--r-- 1 root root  231 Apr 18  2010 99update-notifier
root@proteus:/etc/apt/apt.conf.d# 


-- Package-specific info:

Either package shipped like this, or one of the gnome apt gui tools changed it
incorrectly.  Caused a red Do not enter icon to show up on the toolbar
for the package manager/checker and errors about bad permissions on said file



-- apt-config dump --

APT ;
APT::Architecture i386;
APT::Build-Essential ;
APT::Build-Essential:: build-essential;
APT::Install-Recommends true;
APT::Install-Suggests 0;
APT::Acquire ;
APT::Acquire::Translation environment;
APT::Authentication ;
APT::Authentication::TrustCDROM true;
APT::NeverAutoRemove ;
APT::NeverAutoRemove:: ^firmware-linux.*;
APT::NeverAutoRemove:: ^linux-firmware$;
APT::NeverAutoRemove:: ^linux-image.*;
APT::NeverAutoRemove:: ^kfreebsd-image.*;
APT::NeverAutoRemove:: ^linux-restricted-modules.*;
APT::NeverAutoRemove:: ^linux-ubuntu-modules-.*;
APT::Never-MarkAuto-Sections ;
APT::Never-MarkAuto-Sections:: metapackages;
APT::Never-MarkAuto-Sections:: restricted/metapackages;
APT::Never-MarkAuto-Sections:: universe/metapackages;
APT::Never-MarkAuto-Sections:: multiverse/metapackages;
APT::Never-MarkAuto-Sections:: oldlibs;
APT::Never-MarkAuto-Sections:: restricted/oldlibs;
APT::Never-MarkAuto-Sections:: universe/oldlibs;
APT::Never-MarkAuto-Sections:: multiverse/oldlibs;
APT::Periodic ;
APT::Periodic::Update-Package-Lists 2;
APT::Periodic::Download-Upgradeable-Packages 0;
APT::Periodic::AutocleanInterval 0;
APT::Update ;
APT::Update::Post-Invoke ;
APT::Update::Post-Invoke:: touch /var/lib/apt/periodic/update-success-stamp 
2/dev/null || true;
APT::Update::Post-Invoke-Success ;
APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] || 
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt 
org.debian.apt.CacheChanged || true;
APT::Archives ;
APT::Archives::MaxAge 30;
APT::Archives::MinAge 2;
APT::Archives::MaxSize 500;
Dir /;
Dir::State var/lib/apt/;
Dir::State::lists lists/;
Dir::State::cdroms cdroms.list;
Dir::State::mirrors mirrors/;
Dir::State::extended_states extended_states;
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::sourceparts sources.list.d;
Dir::Etc::vendorlist vendors.list;
Dir::Etc::vendorparts vendors.list.d;
Dir::Etc::main apt.conf;
Dir::Etc::netrc auth.conf;
Dir::Etc::parts apt.conf.d;
Dir::Etc::preferences preferences;
Dir::Etc::preferencesparts preferences.d;
Dir::Etc::trusted trusted.gpg;
Dir::Etc::trustedparts trusted.gpg.d;
Dir::Bin ;
Dir::Bin::methods /usr/lib/apt/methods;
Dir::Bin::dpkg /usr/bin/dpkg;
Dir::Media ;
Dir::Media::MountPath /media/cdrom;
Dir::Log var/log/apt;
Dir::Log::Terminal term.log;
Dir::Log::History history.log;
Dir::Ignore-Files-Silently ;
Dir::Ignore-Files-Silently:: ~$;
Dir::Ignore-Files-Silently:: \.disabled$;
Dir::Ignore-Files-Silently:: \.bak$;
Dir::Ignore-Files-Silently:: \.dpkg-[a-z]+$;
Acquire ;
Acquire::cdrom ;
Acquire::cdrom::mount /media/cdrom;
DPkg ;
DPkg::Pre-Install-Pkgs ;
DPkg::Pre-Install-Pkgs:: /usr/bin/apt-listchanges --apt || test $? -ne 10;
DPkg::Pre-Install-Pkgs:: 

Bug#642159: debian-installer preseed broken with apt-cacher-ng mirror

[Matt Weatherford]

Package: debian-installer
Version: 20110106+squeeze3
Severity: normal
Tags: d-i




Copied from an Ubuntu bug report, since it resembles my problem as well:


In my preseed file I set d-i mirror/http/proxy string 
http://apt-cacher:3142/;, this is an apt-cacher-ng proxy. This works correctly 
for installing the system.

I expect d-i mirror/http/proxy to only apply to the debian installer http 
proxy (apt proxy), and all other http applications, e.g., wget, curl, lynx to 
not use that setting.

Instead when I run applications from the Kickstart %post section, all HTTP 
connections are proxied; curl, wget, lynx, hg (mercurial), everything. Once the 
system installs and reboots all is good, the only remanence of the 
mirror/http/proxy setting is in /etc/apt/apt.conf, which is fine (though I 
think that should be configurable too). mirror/http/proxy is setting the 
environment variable http_proxy.

Repo:
Set d-i mirror/http/proxy string http://apt-cacher:3142/; in a preseed (use 
your local mirror).

Use a Kickstart post section like this:
%post --interpreter=/bin/bash
exec  /dev/tty3  /dev/ttyS0
chvt 3
(
echo ## http_proxy = $http_proxy
echo ## lynx dump head
lynx -dump -head http://example.com
echo ## wget
wget -O /root/test http://example.com
) 21 | /usr/bin/tee /var/log/post_install.log
chvt 1

After install check /var/log/post_install.log and it will look like:
## http_proxy = http://apt-cacher:3142/
## lynx dump head
HTTP/1.1 403 Forbidden file type or location
Date: Thu Apr 22 16:29:10 2010
Server: Debian Apt-Cacher NG/0.4.6
## wget
--2010-04-22 09:29:10-- http://example.com
Resolving apt-cacher... 10.0.0.10
Connecting to apt-cacher|10.0.0.10|:3142... connected.
Proxy request sent, awaiting response... 403 Forbidden file type or location
2010-04-22 09:29:10 ERROR 403: Forbidden file type or location.

The workaround for me it to reset $http_proxy at the top of %post:
export http_proxy=
Then all the applications that use http behave normally.

Suggestion:
Don't set $http_proxy with d-i mirror/http/proxy, maybe set $apt_http_proxy 
if d-i needs an environment variable. For users that need a general proxy a 
setting like d-i http/proxy could be created.




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

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

-- 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#407767: netselect-apt: Another Problem with host on IPv6

[Matt Weatherford]

Package: netselect-apt
Version: 0.3.ds1-14
Severity: normal


netselect-apt is reporting the fastest mirror to be in Thailand, but the
host is not reachable.

My university is doing some early IPv6 work and dont know how the connectivity
is working, but my debian squeeze system is not set up for ipv6.

I am in Seattle, WA, and find it suspicious that my fastest mirror is in 
Thailand.

so I tried it in sources.list and got the following:

Err http://ftp.v6.coe.psu.ac.th squeeze Release.gpg   
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]
Err http://ftp.v6.coe.psu.ac.th/debian/ squeeze/contrib Translation-en
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]
Err http://ftp.v6.coe.psu.ac.th/debian/ squeeze/contrib Translation-en_US
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]
Err http://ftp.v6.coe.psu.ac.th/debian/ squeeze/main Translation-en
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]
Err http://ftp.v6.coe.psu.ac.th/debian/ squeeze/main Translation-en_US
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]
Err http://ftp.v6.coe.psu.ac.th/debian/ squeeze/non-free Translation-en
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]
Err http://ftp.v6.coe.psu.ac.th/debian/ squeeze/non-free Translation-en_US
  Cannot initiate the connection to ftp.v6.coe.psu.ac.th:80 
(2001:3c8:9009:181::7). - connect (101: Network is unreachable) [IP: 
2001:3c8:9009:181::7 80]

so somehow netselect-apt is picking a mirror I cant actually get to

hope this helps the maintainers. pls. let me know if I can run any other tests 
for you guys

-Matt


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

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

Versions of packages netselect-apt depends on:
ii  netselect 0.3.ds1-14 speed tester for choosing a fast n
ii  wget  1.12-2.1   retrieves files from the web

netselect-apt recommends no packages.

netselect-apt 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#635457: gvfsd-metadata: gvfsd-metadata creates a large amount of NFS network I/O on NFS-mounted user home directory

[Matt Weatherford]

Package: gvfs
Version: 1.6.4-3
Severity: normal
File: gvfsd-metadata


I logged in to my at-work desktop Debian 6 manchine from home today (monday) 
and found it generating a large amount
of traffic to the NFS server. This traffic ceased when I killed gvfsd-metadata

The NFS server is a Sun/Oracle Unified storage 7410C if that makes any 
difference.

I have seen this error reported elsewhere see:

https://bugzilla.redhat.com/show_bug.cgi?id=561904







Here is some of the tcpdump traffic log during the event:

15:31:45.266224 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0x6d34c57 
reply ok 116 getattr [|nfs]
15:31:45.266498 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x7d34c57 
(NFSv3) 1428 write [|nfs] (DF)
15:31:45.266502 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x0 (Unk 
15024) 1428 proc-22796 (DF)
15:31:45.266504 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x1b83 (Unk 
9) 1428 null (DF)
15:31:45.266600 nfshomedirserver.edu.nfsd  clientbox.edu.895: . ack 34929 win 
32710 nop,nop,timestamp 1606072765 432261687
15:31:45.266723 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0x7d34c57 
reply ok 164 write [|nfs]
15:31:45.266874 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x8d34c57 
(NFSv3) 180 commit [|nfs] (DF)
15:31:45.267227 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0x8d34c57 
reply ok 156 commit [|nfs]
15:31:45.267499 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x9d34c57 
(NFSv3) 200 remove [|nfs] (DF)
15:31:45.267503 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0xad34c57 
(NFSv3) 192 remove [|nfs] (DF)
15:31:45.267601 nfshomedirserver.edu.nfsd  clientbox.edu.895: . ack 36929 win 
32799 nop,nop,timestamp 1606072765 432261688
15:31:45.267987 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0x9d34c57 
reply ok 148 remove [|nfs]
15:31:45.267989 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0xad34c57 
reply ok 148 remove [|nfs]
15:31:45.268125 clientbox.edu.895  nfshomedirserver.edu.nfsd: . ack 2484 win 
15787 nop,nop,timestamp 432261688 1606072765 (DF)
15:31:45.271121 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0xbd34c57 
(NFSv3) 196 create [|nfs] (DF)
15:31:45.271598 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0xbd34c57 
reply ok 276 create [|nfs]
15:31:45.271870 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0xcd34c57 
(NFSv3) 200 setattr [|nfs] (DF)
15:31:45.272225 nfshomedirserver.edu.nfsd  clientbox.edu.895: xid 0xcd34c57 
reply ok 148 setattr [|nfs]
15:31:45.272495 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0xdd34c57 
(NFSv3) 1428 write [|nfs] (DF)
15:31:45.272500 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x0 (Unk 
15024) 1428 proc-22796 (DF)
15:31:45.272502 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x1b83 (Unk 
9) 1428 null (DF)
15:31:45.272598 nfshomedirserver.edu.nfsd  clientbox.edu.895: . ack 40181 win 
32710 nop,nop,timestamp 1606072765 432261689
15:31:45.272620 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x0 (Unk 0) 
1428 proc-27772 (DF)
15:31:45.272624 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x70656420 
(Unk 1914725231) 1428 proc-1835884910 (DF)
15:31:45.272626 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x61746573 
(Unk 1937006964) 1428 proc-1970482481 (DF)
15:31:45.272628 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x73685f4d 
(Unk 776557391) 1428 proc-779116914 (DF)
15:31:45.272630 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x66775f75 
(Unk 1093563489) 1428 proc-1915646049 (DF)
15:31:45.272632 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x732e7a69 
(Unk 1600286821) 1428 proc-1949643888 (DF)
15:31:45.272635 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x3433302d 
(Unk 1952803886) 1428 proc-1684365870 (DF)
15:31:45.272637 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x0 (Unk 
17956) 1428 proc-33808 (DF)
15:31:45.272639 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x2b598ec 
(Unk 45455575) 864 proc-15792 (DF)
15:31:45.272641 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0xed34c57 
(NFSv3) 1428 write [|nfs] (DF)
15:31:45.272643 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x52345f65 
(Unk 1599616052) 1428 proc-875585368 (DF)
15:31:45.272652 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x0 (Unk 0) 
1428 proc-37908 (DF)
15:31:45.272732 nfshomedirserver.edu.nfsd  clientbox.edu.895: . ack 43037 win 
32620 nop,nop,timestamp 1606072765 432261689
15:31:45.272745 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x390adb1 
(Unk 59813297) 1428 proc-20834 (DF)
15:31:45.272749 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x786d6c00 
(Unk 40696) 1428 proc-41754770 (DF)
15:31:45.272751 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x1e (Unk 
30641) 1428 proc-29 (DF)
15:31:45.272753 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x1d (NFSv3) 
1428 proc-22 (DF)
15:31:45.272755 clientbox.edu.895  nfshomedirserver.edu.nfsd: xid 0x7ca5 (Unk 
29) 1428 proc-32003 (DF)
15:31:45.272757 clientbox.edu.895  

Bug#650578: linux-image-2.6.32-5-686: ixgbe 10gigE adapter does not support sfp+ modules

[Matt Weatherford]

Package: linux-2.6
Version: 2.6.32-39
Severity: normal
Tags: d-i ipv6


The ixgbe network interface driver does not support sfp+ modules that work fine 
everywhere else in my network.  See the ixgbe* messages from dmesg below


kahlo:~# dmesg | grep ixgbe
[   10.135286] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 
2.0.44-k2
[   10.135289] ixgbe: Copyright (c) 1999-2009 Intel Corporation.
[   10.135322] ixgbe :19:00.0: PCI INT A - GSI 32 (level, low) - IRQ 32
...lines omitted...
[   10.232305] ixgbe: :19:00.0: ixgbe_init_interrupt_scheme: Multiqueue 
Enabled: Rx Queue count = 16, Tx Queue count = 16
[   10.232310] ixgbe :19:00.0: (PCI Express:2.5Gb/s:Width x8) 
00:1b:21:c0:24:54
[   10.232386] ixgbe :19:00.0: MAC: 2, PHY: 0, PBA No: e68793-003
[   10.245908] ixgbe :19:00.0: Intel(R) 10 Gigabit Network Connection
[   10.245927] ixgbe :19:00.1: PCI INT B - GSI 42 (level, low) - IRQ 42
[   10.245943] ixgbe :19:00.1: setting latency timer to 64


*** IMPORTANT LINE BELOW:

[   10.269266] ixgbe :19:00.1: failed to initialize because an unsupported 
SFP+ module type was detected.
[   10.269430] ixgbe :19:00.1: PCI INT B disabled
kahlo:~# 
kahlo:~# 




This makes the 10gigE network card:

Intel Ethernet Server Adapter X520-DA2 - network adapter - 2 ports Mfg. Part: 
E10G42BTDA

19:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ 
Network Connection (rev 01)
19:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ 
Network Connection (rev 01)

unusable


-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-39) (da...@debian.org) (gcc version 
4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 3 04:23:54 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=/dev/sda1 ro quiet

** Not tainted

** Kernel log:
[   49.837397]  domain 0: span 5,13 level SIBLING
[   49.837399]   groups: group c294370c cpus 5 (cpu_power = 589) group c2b4370c 
cpus 13 (cpu_power = 589)
[   49.837406]   domain 1: span 4-7,12-15 level MC
[   49.837408]groups: group c2943778 cpus 5,13 (cpu_power = 1178) group 
c2983778 cpus 6,14 (cpu_power = 1178) group c29c3778 cpus 7,15 (cpu_power = 
1178) group c2903778 cpus 4,12 (cpu_power = 1178)
[   49.837420]domain 2: span 0-15 level CPU
[   49.837422] groups: group c29037e4 cpus 4-7,12-15 (cpu_power = 4712) 
group c28037e4 cpus 0-3,8-11 (cpu_power = 4712)
[   49.837430] CPU6 attaching sched-domain:
[   49.837433]  domain 0: span 6,14 level SIBLING
[   49.837435]   groups: group c298370c cpus 6 (cpu_power = 589) group c2b8370c 
cpus 14 (cpu_power = 589)
[   49.837442]   domain 1: span 4-7,12-15 level MC
[   49.837444]groups: group c2983778 cpus 6,14 (cpu_power = 1178) group 
c29c3778 cpus 7,15 (cpu_power = 1178) group c2903778 cpus 4,12 (cpu_power = 
1178) group c2943778 cpus 5,13 (cpu_power = 1178)
[   49.837456]domain 2: span 0-15 level CPU
[   49.837458] groups: group c29037e4 cpus 4-7,12-15 (cpu_power = 4712) 
group c28037e4 cpus 0-3,8-11 (cpu_power = 4712)
[   49.837466] CPU7 attaching sched-domain:
[   49.837469]  domain 0: span 7,15 level SIBLING
[   49.837471]   groups: group c29c370c cpus 7 (cpu_power = 589) group c2bc370c 
cpus 15 (cpu_power = 589)
[   49.837478]   domain 1: span 4-7,12-15 level MC
[   49.837481]groups: group c29c3778 cpus 7,15 (cpu_power = 1178) group 
c2903778 cpus 4,12 (cpu_power = 1178) group c2943778 cpus 5,13 (cpu_power = 
1178) group c2983778 cpus 6,14 (cpu_power = 1178)
[   49.837492]domain 2: span 0-15 level CPU
[   49.837495] groups: group c29037e4 cpus 4-7,12-15 (cpu_power = 4712) 
group c28037e4 cpus 0-3,8-11 (cpu_power = 4712)
[   49.837503] CPU8 attaching sched-domain:
[   49.837505]  domain 0: span 0,8 level SIBLING
[   49.837507]   groups: group c2a0370c cpus 8 (cpu_power = 589) group c280370c 
cpus 0 (cpu_power = 589)
[   49.837514]   domain 1: span 0-3,8-11 level MC
[   49.837517]groups: group c2803778 cpus 0,8 (cpu_power = 1178) group 
c2843778 cpus 1,9 (cpu_power = 1178) group c2883778 cpus 2,10 (cpu_power = 
1178) group c28c3778 cpus 3,11 (cpu_power = 1178)
[   49.837528]domain 2: span 0-15 level CPU
[   49.837531] groups: group c28037e4 cpus 0-3,8-11 (cpu_power = 4712) 
group c29037e4 cpus 4-7,12-15 (cpu_power = 4712)
[   49.837539] CPU9 attaching sched-domain:
[   49.837542]  domain 0: span 1,9 level SIBLING
[   49.837544]   groups: group c2a4370c cpus 9 (cpu_power = 589) group c284370c 
cpus 1 (cpu_power = 589)
[   49.837551]   domain 1: span 0-3,8-11 level MC
[   49.837553]groups: group c2843778 cpus 1,9 (cpu_power = 1178) group 
c2883778 cpus 2,10 (cpu_power = 1178) group c28c3778 cpus 3,11 (cpu_power = 
1178) group c2803778 cpus 0,8 (cpu_power = 1178)
[   49.837565]domain 2: span 0-15 level CPU
[   49.837567] groups: group c28037e4 cpus 0-3,8-11 (cpu_power = 4712) 
group c29037e4 cpus 4-7,12-15 (cpu_power = 4712)
[   49.837575] CPU10 attaching sched-domain:
[   

Bug#868242: open-vm-tools: VMXNET3 network interface hard locks VM after Vmware hw v8 to hw v13

[Matt Weatherford]

Package: open-vm-tools
Version: 2:10.1.5-5055683-4
Severity: normal

Dear Maintainer,


   * What led up to the situation?

Debian 9 vm working fine on HW version 8 for months using VMXNET3 network 
interface
In VMWare virtualcenter Server, VM on ESXi running VMWare 6.5, I upgraded VM 
hardware from verson 8
to version 13.

Network interface worked ok for a a while, then sporadically disconnected from 
the network for 5-20 minutes, 
eventually hard-locking the vm
 

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


I powered down the VM, deleted the VMXNET3 network interface, and added back a 
E1000 network interface.
The system has been up now without problems for 15 hours


Not sure if this is the place for this package- not sure where the VMXNET3 
driver lives - maybe that is
a remnant left over from an old VMware tools install that I did then disbled in 
favor of open-vm-tools ?

Unclear where all the parts live.  Apologies if this is user error.

Thank you for supporting Debian!

-Matt W
Seattle, WA


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

Kernel: Linux 4.9.0-3-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 open-vm-tools depends on:
ii  init-system-helpers1.48
ii  iproute2   4.9.0-1
ii  libc6  2.24-11+deb9u1
ii  libdumbnet11.12-7+b1
ii  libfuse2   2.9.7-1
ii  libgcc11:6.3.0-18
ii  libglib2.0-0   2.50.3-2
ii  libicu57   57.1-6
ii  libmspack0 0.5-1+b2
ii  libprocps6 2:3.3.12-3
ii  libssl1.0.21.0.2l-2
ii  libstdc++6 6.3.0-18
ii  libxerces-c3.1 3.1.4+debian-2
ii  libxml-security-c17v5  1.7.3-4
ii  pciutils   1:3.5.2-1

Versions of packages open-vm-tools recommends:
ii  ethtool  1:4.8-1+b1
ii  fuse 2.9.7-1
ii  lsb-release  9.20161125
ii  zerofree 1.0.4-1

Versions of packages open-vm-tools suggests:
pn  cloud-init 
pn  open-vm-tools-desktop  

-- Configuration Files:
/etc/vmware-tools/tools.conf changed:


-- no debconf information

Bug#867488: mate-screensaver: cant unlock screensaver with pam-kerberos-ldap setup

[Matt Weatherford]

Package: mate-screensaver
Version: 1.16.1-1
Severity: normal

Dear Maintainer,


I've configured Debian 9 to use LDAP and Kerberos for authentication.  I used 
PAM
to do this and modified /etc/pam.d/ .  Now I cannot unlock my mate-screensaver 
session when I am
logged in as a user from the ldap Directory. 

Here is what my "common-auth" looks like:

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)

authrequired  pam_listfile.so onerr=fail  item=group sense=allow 
file=/etc/netid.allow

#new comment out 5-18-2017
auth[success=3 default=ignore]  pam_krb5.so minimum_uid=1000


auth[success=2 default=ignore]  pam_unix.so nullok_secure try_first_pass
auth[success=1 default=ignore]  pam_ldap.so use_first_pass
# here's the fallback if no module succeeds
authrequisite   pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
authrequiredpam_permit.so

#
# already comment out
#auth sufficient pam_krb5.so use_first_pass


# and here are more per-package modules (the "Additional" block)
authoptionalpam_ssh.so use_first_pass

# end of pam-auth-update config



-

here is my /etc/pam/mate-screensaver file:

root@jaxi:/etc/pam.d# more mate-screensaver 
@include common-auth
auth optional pam_gnome_keyring.so

root@jaxi:/etc/pam.d#root@jaxi:/homes/mbw# 

here are the errors I see in /var/log/auth.log:

Jul  6 11:19:54 jaxi lightdm: pam_krb5(lightdm:auth): user mbw authenticated as 
m...@netid.washington.edu
Jul  6 11:19:54 jaxi lightdm: pam_unix(lightdm-greeter:session): session closed 
for user lightdm
Jul  6 11:19:54 jaxi lightdm[11362]: pam_unix(lightdm:session): session opened 
for user mbw by (uid=0)
Jul  6 11:19:54 jaxi systemd-logind[443]: Removed session c4.
Jul  6 11:19:54 jaxi systemd: pam_krb5(systemd-user:session): cannot create 
Kerberos context
Jul  6 11:19:54 jaxi lightdm[11362]: pam_ck_connector(lightdm:session): nox11 
mode, ignoring PAM_TTY :0
Jul  6 11:19:55 jaxi gnome-keyring-daemon[11380]: The Secret Service was 
already initialized
Jul  6 11:19:55 jaxi gnome-keyring-daemon[11380]: The PKCS#11 component was 
already initialized
Jul  6 11:19:55 jaxi gnome-keyring-daemon[11380]: The SSH agent was already 
initialized
Jul  6 11:20:05 jaxi mate-screensaver-dialog: pam_krb5(mate-screensaver:auth): 
cannot create Kerberos context
Jul  6 11:20:09 jaxi mate-screensaver-dialog: pam_unix(mate-screensaver:auth): 
authentication failure; logname= uid=153641 euid=153641 tty=:0.0 ruser= rhost=  
user=mbw
Jul  6 11:20:09 jaxi mate-screensaver-dialog: pam_ldap(mate-screensaver:auth): 
Authentication failure; user=mbw
Jul  6 11:20:11 jaxi mate-screensaver-dialog: pam_krb5(mate-screensaver:auth): 
cannot create Kerberos context
Jul  6 11:20:15 jaxi mate-screensaver-dialog: pam_unix(mate-screensaver:auth): 
authentication failure; logname= uid=153641 euid=153641 tty=:0.0 ruser= rhost=  
user=mbw
Jul  6 11:20:15 jaxi mate-screensaver-dialog: pam_ldap(mate-screensaver:auth): 
Authentication failure; user=mbw
Jul  6 11:20:17 jaxi mate-screensaver-dialog: pam_krb5(mate-screensaver:auth): 
cannot create Kerberos context
Jul  6 11:20:54 jaxi mate-screensaver-dialog: pam_krb5(mate-screensaver:auth): 
cannot create Kerberos context
Jul  6 11:21:49 jaxi su[11726]: Successful su for root by mbw



I dont intend for this to be a support request - Im happy to go read forums or 
other docs on how to resolve this if it is user error (mine)
or my configuration problem - please point me in the right direction. My 
googling so far has not helped.

My next thing to try is to log in as a user in /etc/passwd (local user, not krb 
not ldap) and see if I can unlock the screen. I'll update the ticket soon with 
that information.


thanks for supporting Debian!

Matt



*** End of the template - remove these template lines ***


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, 

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

[Matt Weatherford]

Package: nslcd
Version: 0.9.7-2
Severity: important

Dear Maintainer,


debian 7 install works fine with certificate auth.
Debian 9 install with same config files appears to not work and throws these 
erros:

Apr 25 16:41:08 nori nslcd[1376]: [52255a]  failed to bind to LDAP 
server ldap://ldi.s.uw.edu: Unknown authentication method: SASL(-4): no 
mechanism available:
Apr 25 16:41:08 nori nslcd[1376]: [52255a]  no available LDAP 
server found: Unknown authentication method: Bad file descriptor
Apr 25 16:41:13 nori nslcd[1376]: [9cf92e]  no available LDAP 
server found: Server is unavailable: Bad file descriptor
Apr 25 16:41:18 nori nslcd[1376]: [ed7263] 

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

[Matt Weatherford]

Arthur,

Im sure you have many, many other projects going but I am motivated to 
solve this problem - is there anything else I can try on my side?  I've 
sent you nslcd debug info ...  anything else I can do?


do you know of anyone who has a working cert-based auth on debian 9?

thanks,

Matt



On 4/26/17 2:08 AM, Arthur de Jong wrote:

On Tue, 2017-04-25 at 16:53 -0700, Matt Weatherford wrote:

debian 7 install works fine with certificate auth.
Debian 9 install with same config files appears to not work and
throws these erros:

Apr 25 16:41:08 nori nslcd[1376]: [52255a] <passwd(all)> failed to
bind to LDAP server ldap://ldi.s.uw.edu: Unknown authentication
method: SASL(-4): no mechanism available:
Apr 25 16:41:08 nori nslcd[1376]: [52255a] <passwd(all)> no available
LDAP server found: Unknown authentication method: Bad file descriptor
Apr 25 16:41:13 nori nslcd[1376]: [9cf92e] <group(all)> no available
LDAP server found: Server is unavailable: Bad file descriptor

Does running nslcd in debug mode provide more information?


contents of /etc/nslcd.conf:

uri ldap://ldi.s.uw.edu
ssl start_tls

tls_cacertfile  /etc/ssl/ldi/InCommonCA.crt
tls_cert/etc/ssl/ldi/ldi-client.crt
tls_key /etc/ssl/ldi/ldi-client.key

sasl_mech   EXTERNAL

So the client-side certificate is used for authentiction and that is
where it appears to fail.

Can you make the connection using the ldapsearch command-line tool? The
nslcd daemon does not do any TLS handling itself and only passes
configuration options to libldap but there are differences between TLS
libraries used.

Kind regards,

Bug#865948: nslcd crashes with libsasl2 also reporting problem in kern.log

[Matt Weatherford]

Package: nslcd
Version: 0.9.7-2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

I wish I had more information for you, but this is all I have at the moment:
   
>From /var/og/kern.log: 
>   
> 

Jun 24 09:18:14 ika kernel: [71460.143951] traps: nslcd[1813] general 
protection ip:7f1d50584837 sp:7f1d4cdd6920 error:0
Jun 24 09:18:14 ika kernel: [71460.143962]  in 
libsasl2.so.2.0.25[7f1d5057e000+1a000]

Restarting the nslcd process seemed to get it working again





*** End of the template - remove these template lines ***


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages nslcd depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u1
ii  libgssapi-krb5-2   1.15-1
ii  libldap-2.4-2  2.4.44+dfsg-5
ii  lsb-base   9.20161125

Versions of packages nslcd recommends:
ii  bind9-host [host]   1:9.10.3.dfsg.P4-12.3
ii  ca-certificates 20161130+nmu1
ii  ldap-utils  2.4.44+dfsg-5
ii  libnss-ldapd [libnss-ldap]  0.9.7-2
ii  libpam-krb5 4.7-4
ii  libpam-ldapd [libpam-ldap]  0.9.7-2
ii  nscd2.24-11+deb9u1
ii  nslcd-utils 0.9.7-2

Versions of packages nslcd suggests:
pn  kstart  

-- debconf information:
  nslcd/ldap-sasl-realm:
  nslcd/ldap-sasl-mech:
  nslcd/restart-services:
  nslcd/disable-screensaver:
  nslcd/restart-failed:
  nslcd/xdm-needs-restart:
  nslcd/ldap-sasl-secprops:
  nslcd/ldap-sasl-authzid:
  libraries/restart-without-asking: false
  nslcd/ldap-auth-type: none
  nslcd/ldap-reqcert: allow
* nslcd/ldap-uris: ldap://csde-dc3.csde.washington.edu/
* nslcd/ldap-base: DC=csde,DC=washington,DC=edu
  nslcd/ldap-cacertfile: /etc/ssl/certs/ca-certificates.crt
  nslcd/ldap-sasl-authcid:
  nslcd/ldap-binddn:
  nslcd/ldap-starttls: false
  nslcd/ldap-sasl-krb5-ccname: /var/run/nslcd/nslcd.tkt

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

[Matt Weatherford]

Update:  I logged this bug further down the stack, as it was also 
affecting the "ldap-utils" package (ldapsearch and ldapwhoami also)


I got some feedback that led us to determine that our LDAP server on 
CentOS was offering up a LOT of certificate options... scaling those 
back made the system including nslcd work again.


the other bug is Bug#861838

Thanks Arthur for the help in getting started on the debugging process 
for this.


Matt


On 5/2/17 11:59 AM, Arthur de Jong wrote:

On Thu, 2017-04-27 at 20:25 -0700, Matt Weatherford wrote:

Im sure you have many, many other projects going but I am motivated
to solve this problem - is there anything else I can try on my
side?  I've sent you nslcd debug info ...  anything else I can do?

Sorry for not replying sooner. Your ldapsearch output shows that at
least the problem is not per se in nss-pam-ldapd ;)

To get more debugging info from nslcd you could specify -d twice when
running nslcd. This also enables extra debugging in libldap which
produces a lot of output but I don't think it will include extra debug
output of the TLS library (GnuTLS on Debian).

For ldapsearch you could try passing -d1 to get debug output. I assume
the ldapsearch in your script works on older versions? From my
experience I think the certificates and keys can only be configured in
a configuration file (e.g. ldaprc in the current directory).

Maybe comparing the debug output from Debian 7 and 9 will provide some
more insights?

One thing that you could try is add the DN to bind as as binddn instead
of leaving it empty. You should probably be able to get the DN from an
ldapwhoami query on older versions of Debian.

Another thing that could help is looking in the server logs to see if
any problem is logged there (it could be a TLS version or cypher-suite
mismatch).

I don't think there should be much issues with how the key, CSR and CRT
are generated. GnuTLS should be able to handle files generated by
OpenSSL file as far as I know. Location of the files should also not be
an issue.

I have not doen client certificate authentication recently and not on
Debian.

Bug#861212: nslcd: certificate authentication fails with Unknown authentication method: SASL(-4)

[Matt Weatherford]

Makes sense to me! Thank you for all your work supporting debian ;)
Matt

> On May 6, 2017, at 11:17 AM, Arthur de Jong <adej...@debian.org> wrote:
> 
>> On Thu, 2017-05-04 at 23:01 -0700, Matt Weatherford wrote:
>> Update:  I logged this bug further down the stack, as it was also 
>> affecting the "ldap-utils" package (ldapsearch and ldapwhoami also)
>> 
>> I got some feedback that led us to determine that our LDAP server on 
>> CentOS was offering up a LOT of certificate options... scaling those 
>> back made the system including nslcd work again.
>> 
>> the other bug is Bug#861838
> 
> Thanks for following up. Since the bug is not in nss-pam-ldapd I am
> inclined to close this bug report. Any progress on this can be tracked
> in #861838 further.
> 
> Thanks,
> 
> -- 
> -- arthur - adej...@debian.org - https://people.debian.org/~adejong --

Bug#884421: nfs4-acl-tools: bizarre id problem in nfs4_setfacl

[Matt Weatherford]

Package: nfs4-acl-tools
Version: 0.3.3-3
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

I am trying to use NFSv4.1 mounts and ACL's on Debian 9, but I 
Cant set NFSv4 ACL for a particular user - other users work fine that user 
id seems to be fine

here is the behavior:

root@ika:/net/proj# nfs4_setfacl  -a A::kur...@netid.washington.edu:rwx 
/net/proj/SHAMPnetdat
Failed setxattr operation: Invalid argument

root@ika:/net/proj# mount | grep proj
tako:/export/nfsv41_proj on /net/proj type nfs4 
(rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.28.43.150,local_lock=none,addr=172.28.43.175)
root@ika:/net/proj# 

root@ika:/net/proj#



root@ika:/net/proj# 
root@ika:/net/proj# nfs4_getfacl ./SHAMPnetdat
A::296509:rwaDxtTnNcCy
A::m...@netid.washington.edu:rwx
A::m...@netid.washington.edu:rwx
A::franc...@netid.washington.edu:rwaDxtTnNcCy
A::m...@netid.washington.edu:rwx
A::m...@netid.washington.edu:rwaDxtTnNcCy
A::sa...@netid.washington.edu:rwaDxtTnNcCy
A::m...@netid.washington.edu:rwaDxtTnNcCy
A::morr...@netid.washington.edu:rwaDxtTnNcCy
A::OWNER@:rwaDxtTnNcCoy
A:g:GROUP@:rwaDxtTnNcy
A::EVERYONE@:rxtncy
root@ika:/net/proj# 
root@ika:/net/proj# id kurian
uid=296509(kurian) gid=2120296509(kurian) 
groups=191799(unixusers),90068(fs1_home),191338(svn-statnet-research),85506(csde_users),145001(morris_statnet),274390(expandrive_users),191230(svn-statnet-commons),471122(shampnetdat),2120296509(kurian)
root@ika:/net/proj# getent passwd kurian
kurian:*:296509:2120296509:Jeanette Kurian Birnbaum:/homes/kurian:/bin/bash
root@ika:/net/proj# getent group shampnetdat
shampnetdat:*:471122:dth2,morrism,mbw,kurian


This is bizarre... is there any better error message that can be produced?

NFSv41 file server is an Oracle ZFSSA Z3-2 Appliance

thanks,
Matt


*** End of the template - remove these template lines ***


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/8 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages nfs4-acl-tools depends on:
ii  libattr1  1:2.4.47-2+b2
ii  libc6 2.24-11+deb9u1

nfs4-acl-tools recommends no packages.

nfs4-acl-tools suggests no packages.

-- no debconf information

Bug#898127: remmina: ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED error:14094438:SSL routines:ssl3_read_bytes:tlsv1

[Matt Weatherford]

Package: remmina
Version: 1.2.0-rcgit.29+dfsg-1~bpo9+1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Remmina on Debian 9 does not want to connect to my Remote Desktop Windows 
2012R2 server.
Heres the error I see:

[10:33:32:169] [6526:6637] [ERROR][com.freerdp.core] - freerdp_set_last_error 
ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F]
[10:33:32:169] [6526:6637] [ERROR][com.freerdp.core.transport] - BIO_read 
returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert 
internal error
0002000F 0003


If I directly connect with xfreerdp it works fine


mbw@jaxi:~$ xfreerdp /log-level:debug  /u:NETID\\mbw  /v:senkaku
connected to senkaku:3389
Password: 
(remote desktop window pops up as expected)

mbw@jaxi:~$ xfreerdp --version
This is FreeRDP version 1.1.0-beta1 (git n/a)
mbw@jaxi:~$ which xfreerdp
/usr/bin/xfreerdp
mbw@jaxi:~$ 
mbw@jaxi:~$ 
mbw@jaxi:~$ remmina --version
StatusNotifier/Appindicator support: your desktop does support it and 
libappindicator is compiled in remmina. Good!
Remmina - 1.2.0-rcgit-29 (git rcgit-29)
mbw@jaxi:~$ 


*** End of the template - remove these template lines ***


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

Kernel: Linux 4.15.0-0.bpo.2-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 remmina depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.26-0+deb9u1
ii  dbus-x11 [dbus-session-bus]   1.10.26-0+deb9u1
ii  libatk1.0-0   2.22.0-1
ii  libavahi-client3  0.6.32-2
ii  libavahi-common3  0.6.32-2
ii  libavahi-ui-gtk3-00.6.32-2
ii  libayatana-appindicator3-10.5.2-1~bpo9+1
ii  libc6 2.24-11+deb9u3
ii  libcairo2 1.14.8-1
ii  libgcrypt20   1.7.6-2+deb9u2
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libice6   2:1.0.9-2
ii  libjson-glib-1.0-01.2.6-1
ii  libpango-1.0-01.40.5-1
ii  libsm62:1.2.2-1+b3
ii  libsoup2.4-1  2.56.0-2+deb9u1
ii  libssh-4  0.7.3-2
ii  libssl1.1 1.1.0f-3+deb9u2
ii  libvte-2.91-0 0.46.1-1
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  remmina-common1.2.0-rcgit.29+dfsg-1~bpo9+1

Versions of packages remmina recommends:
ii  remmina-plugin-rdp 1.2.0-rcgit.29+dfsg-1~bpo9+1
ii  remmina-plugin-secret  1.2.0-rcgit.29+dfsg-1~bpo9+1
ii  remmina-plugin-vnc 1.2.0-rcgit.29+dfsg-1~bpo9+1

Versions of packages remmina suggests:
pn  remmina-plugin-exec   
pn  remmina-plugin-nx 
pn  remmina-plugin-spice  
pn  remmina-plugin-telepathy  
pn  remmina-plugin-xdmcp  

-- no debconf information

Bug#884871: nfs-kernel-server: svcgssd starts anyways when "disabled" in /etc/default/nfs-kernel-server

[Matt Weatherford]

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

Dear Maintainer,

First of all, thank you for all you do to support Debian


Heres my /etc/default/nfs-kernel-server  config file, it clearly "disables 
svcgssd" :


root@filer:/etc/default# vi nfs-kernel-server 
# Number of servers to start up
RPCNFSDCOUNT=8

# Runtime priority of server (see nice(1))
RPCNFSDPRIORITY=0

# Options for rpc.mountd.
# If you have a port-based firewall, you might want to set up
# a fixed port here using the --port option. For more information,
# see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS
# To disable NFSv4 on the server, specify '--no-nfs-version 4' here
#RPCMOUNTDOPTS="--manage-gids"

### TO DEBUG USE:

RPCMOUNTDOPTS="--manage-gids --debug all"



# Do you want to start the svcgssd daemon? It is only required for Kerberos
# exports. Valid alternatives are "yes" and "no"; the default is "no".
NEED_SVCGSSD=no

# Options for rpc.svcgssd.
#RPCSVCGSSDOPTS=""


RPCNFSDCOUNT="64  --no-nfs-version 3  --no-nfs-version 4"



~   
   
~   
   
~ 

But if I restart the nfs-server process, it errors out like this:


root@filer:/etc/default# 
root@filer:/etc/default# service nfs-server restart
Job for nfs-server.service failed because the control process exited with error 
code.
See "systemctl status nfs-server.service" and "journalctl -xe" for details.
root@filer:/etc/default# journalctl -xe
Dec 20 11:38:03 filer systemd[1]: Starting NFSv4 ID-name mapping service...
-- Subject: Unit nfs-idmapd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-idmapd.service has begun starting up.
Dec 20 11:38:03 filer systemd[1]: Starting RPC security service for NFS 
server...
-- Subject: Unit rpc-svcgssd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rpc-svcgssd.service has begun starting up.
Dec 20 11:38:03 filer systemd[1]: Started NFSv4 ID-name mapping service.
-- Subject: Unit nfs-idmapd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-idmapd.service has finished starting up.
-- 
-- The start-up result is done.
Dec 20 11:38:03 filer rpc.svcgssd[10651]: ERROR: GSS-API: error in 
gss_acquire_cred(): GSS_S_FAILURE (Unspecified GSS failure.  Minor code 
Dec 20 11:38:03 filer rpc.svcgssd[10651]: unable to obtain root (machine) 
credentials
Dec 20 11:38:03 filer rpc.svcgssd[10651]: do you have a keytab entry for 
nfs/@ in /etc/krb5.keytab?
Dec 20 11:38:03 filer systemd[1]: rpc-svcgssd.service: Control process exited, 
code=exited status=1
Dec 20 11:38:03 filer systemd[1]: Failed to start RPC security service for NFS 
server.
-- Subject: Unit rpc-svcgssd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit rpc-svcgssd.service has failed.
-- 
-- The result is failed.
Dec 20 11:38:03 filer systemd[1]: rpc-svcgssd.service: Unit entered failed 
state.
Dec 20 11:38:03 filer systemd[1]: rpc-svcgssd.service: Failed with result 
'exit-code'.
Dec 20 11:38:03 filer rpc.mountd[10654]: Version 1.3.3 starting
Dec 20 11:38:03 filer systemd[1]: Started NFS Mount Daemon.
-- Subject: Unit nfs-mountd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-mountd.service has finished starting up.



I am trying to use nfs 4.1 (not 4) with no kerberos, but cant figure out how to 
start it up.
If I take out the " --no-nfs-version 4"  then nfs-server starts up ok, but I 
have version 4 enabled where I only want version 4.1 and higher working:
root@filer:~# cat /proc/fs/nfsd/versions
-2 -3 +4 +4.1 +4.2
root@filer:~# 



-- 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
133   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
1002273   udp   2049
1000241   udp  51907  status
1000241   tcp  59263  status
134   tcp   2049  nfs
134   udp   2049  nfs
1000211   udp  38357  nlockmgr
1000213   udp  38357  nlockmgr
1000214   udp  38357  nlockmgr
1000211   tcp  36441  nlockmgr
1000213   tcp  36441  nlockmgr
1000214   tcp  36441  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --debug all"
NEED_SVCGSSD=no

Bug#903840: nslcd unattentded upgrade fails/hangs at unter URI path

[Matt Weatherford]

Package: nslcd
Version: 0.9.7-2+deb9u1
Severity: normal

Dear Maintainer,

First and foremost, thank you for your contributions to Debian and for 
supporting the nslcd
package which we use every single day - very much appreciated.

I went to upgrade my debian 9 system today and got a prompt at the nslcd 
upgrade to enter the
uri path.  I entered this and the upgrade hung.  I am running upgrades over ssh 
sessions in non-interactive
mode and wonder if there is something about this upgrade that is breaking the 
script nslcd is running.

I suspect this is a minor detail.

It seems the new script is parsing the nslcd.conf file and making changes and / 
or normalizing things.
Is there a changelog that I can review to better understand what is happening 
here?

What additional info would be helpful to you that I can gather?

thanks,  Matt



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

Kernel: Linux 4.16.0-0.bpo.2-amd64 (SMP w/16 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 nslcd depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libldap-2.4-2  2.4.44+dfsg-5+deb9u2
ii  lsb-base   9.20161125

Versions of packages nslcd recommends:
ii  bind9-host [host]   1:9.10.3.dfsg.P4-12.3+deb9u4
ii  ca-certificates 20161130+nmu1+deb9u1
ii  ldap-utils  2.4.44+dfsg-5+deb9u2
ii  libnss-ldapd [libnss-ldap]  0.9.7-2+deb9u1
ii  libpam-krb5 4.7-4
ii  libpam-ldapd [libpam-ldap]  0.9.7-2+deb9u1
ii  nscd2.24-11+deb9u3
ii  nslcd-utils 0.9.7-2+deb9u1

Versions of packages nslcd suggests:
pn  kstart  

-- debconf information:
  nslcd/ldap-cacertfile: /etc/ssl/ldi/InCommonCA.crt
  nslcd/restart-services:
  nslcd/xdm-needs-restart:
  nslcd/ldap-auth-type: SASL
  nslcd/ldap-sasl-secprops:
  nslcd/restart-failed:
* nslcd/ldap-reqcert: never
  nslcd/ldap-binddn:
  nslcd/ldap-starttls: true
  libraries/restart-without-asking: false
  nslcd/ldap-sasl-krb5-ccname: /var/run/nslcd/nslcd.tkt
  nslcd/ldap-sasl-mech: EXTERNAL
* nslcd/ldap-uris: ldap://ldi.s.uw.edu
  nslcd/ldap-sasl-authcid:
* nslcd/ldap-base:
  nslcd/disable-screensaver:
  nslcd/ldap-sasl-authzid:
  nslcd/ldap-sasl-realm:

Bug#894830: freerdp-x11: Cant connect to windows2012r2 RDP with FIPS after 3/2018 Windows update

[Matt Weatherford]

Package: freerdp-x11
Version: 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
Severity: important

Dear Maintainer,

xfreerdp via remmina was working fine until march 2018 when a windows update 
apparently changed something in the negotiation protocol.  I only "know" this 
from reading on the remmina issues forum here:

https://github.com/FreeRDP/Remmina/issues/1513

would be nice to be able to use remmina on Debian 9!

Note that windows 2016 server works fine.

Heres the output of:

$ xfreerdp /log-level:debug  /v:senkaku
connected to senkaku:3389
Password: 
SSL_read: Failure in SSL library (protocol error?)
SSL_read: error:14094419:SSL routines:ssl3_read_bytes:tlsv1 alert access denied
credssp_recv() error: -1
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.
Error: protocol security negotiation or connection failure
$ 





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

Kernel: Linux 4.14.0-0.bpo.3-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 freerdp-x11 depends on:
ii  libc6 2.24-11+deb9u3
ii  libfreerdp-cache1.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-client1.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-codec1.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-common1.1.01.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-core1.11.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-crypto1.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-gdi1.1 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-locale1.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-primitives1.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-rail1.11.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libfreerdp-utils1.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libjpeg62-turbo   1:1.5.1-2
ii  libssl1.0.2   1.0.2l-2+deb9u3
ii  libwinpr-crt0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-crypto0.11.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-dsparse0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-environment0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-file0.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-handle0.11.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-heap0.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-input0.1 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-interlocked0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-library0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-path0.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-pool0.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-registry0.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-rpc0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-sspi0.1  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-synch0.1 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-sysinfo0.1   1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-thread0.11.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libwinpr-utils0.1 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libx11-6  2:1.6.4-3
ii  libxcursor1   1:1.1.14-1+deb9u1
ii  libxext6  2:1.3.3-1+b2
ii  libxfreerdp-client1.1 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.3-1+b3
ii  libxkbfile1   1:1.0.9-2
ii  libxrender1   1:0.9.10-1
ii  libxv12:1.0.11-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages freerdp-x11 recommends:
ii  libfreerdp-plugins-standard  1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2

freerdp-x11 suggests no packages.

-- no debconf information

Bug#891942: cifs-utils: mounting encrypted SMB3 shares fails with CIFS VFS: protocol revalidation - security settings mismatch, code = -5

[Matt Weatherford]

Package: cifs-utils
Version: 2:6.7-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Hi,
I've been watching with interest for the ability in debian to mount encrypted 
SMBv3 shares

WE recently spun up storage on a Netapp filer - the share requires Encrypted 
SMBv3 for the mount to be allowed.

Debian 9 stock has an older kernel and the mount option for smbv3 doesnt seem 
to work.
SO I went and got a 4.14.0-0.bpo.3 kernel from backports.  And now the mount 
command runs but I get an error from the mount.

Heres what happens:


DIRECT MOUNT OF NETAPP system:
(I have a backgrounded tail -f /var/log/syslog running)

root@rstudio:~# sudo /sbin/mount.cifs //fas8200-1.s.uw.edu/CSDE  /a --verbose  
-o rw,uid=mbw,user=mbw,domain=NETID,vers=3Password for 
mbw@//fas8200-1.s.uw.edu/CSDE:  
mount.cifs kernel mount options: 
ip=10.48.76.101,unc=\\fas8200-1.s.uw.edu\CSDE,vers=3,uid=153641,user=mbw,domain=NETID,pass=
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
root@rstudio:~# Mar  2 13:06:15 rstudio kernel: [161412.073130] CIFS VFS: 
protocol revalidation - security settings mismatch
Mar  2 13:06:15 rstudio kernel: [161412.073948] CIFS VFS: session 
8f92f72e4e00 has no tcon available for a dfs referral request
Mar  2 13:06:15 rstudio kernel: [161412.075479] CIFS VFS: cifs_mount failed 
w/return code = -5

root@rstudio:~# 
root@rstudio:~# uname -a
Linux rstudio 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) 
x86_64 GNU/Linux
root@rstudio:~# 

Mount via DFS pointer:

root@rstudio:~# sudo /sbin/mount.cifs //netid.washington.edu/wfs/csde  /a 
--verbose  -o rw,uid=mbw,user=mbw,domain=NETID,vers=3  
Password for mbw@//netid.washington.edu/wfs/csde:  
mount.cifs kernel mount options: 
ip=172.16.31.136,unc=\\netid.washington.edu\wfs,vers=3,uid=153641,user=mbw,domain=NETID,prefixpath=csde,pass=
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Mar  2 13:08:06 rstudio kernel: [161523.613992] CIFS VFS: protocol revalidation 
- security settings mismatch
root@rstudio:~# Mar  2 13:08:06 rstudio kernel: [161523.615697] CIFS VFS: 
cifs_mount failed w/return code = -5

root@rstudio:~# 


So I am not sure how to report a bug on this in the most useful/best way for 
the Debian project.
Should I install Buster alpha and try/log bug there?  Or is this useful to you?

I'd like to help out somehow to get this working, it seems like a lot of work 
has been done to get this feature moved forward.  I suspect this is either user 
error on my part or we are *really* close to getting this to work.  lmk what I 
can do to help

thanks,
Matt Weatherford
Seattle, WA USA


*** End of the template - remove these template lines ***


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

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/16 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 cifs-utils depends on:
ii  libc6 2.24-11+deb9u1
ii  libcap-ng00.7.7-3+b1
ii  libkeyutils1  1.5.9-9
ii  libkrb5-3 1.15-1+deb9u1
ii  libpam0g  1.1.8-3.6
ii  libtalloc22.1.8-1
ii  libwbclient0  2:4.5.12+dfsg-2+deb9u1
ii  samba-common  2:4.5.12+dfsg-2+deb9u1

cifs-utils recommends no packages.

Versions of packages cifs-utils suggests:
ii  keyutils   1.5.9-9
ii  smbclient  2:4.5.12+dfsg-2+deb9u1
ii  winbind2:4.5.12+dfsg-2+deb9u1

-- no debconf information

Bug#925978: shibboleth-sp2-common: fills up the /var/cache directory with incommon-metadata.xml.XXXX

[Matt Weatherford]

Package: shibboleth-sp2-common
Version: 2.6.0+dfsg1-4+deb9u1
Severity: important

Dear Maintainer,

This continues to happen, but is easy to manually clear up so low priority...  
I wanted to report it out of respect for the work you guys do & in hopes its 
already fixed in the 3.0 release
I hope this isnt my own configuration problem of some kind. User error has Not 
Been Ruled Out here  ;)

Thank you for supporting the Shibboleth package on Debian !
-Matt 
UW Seattle, WA USA


root@a:/var/cache# du -sh *
4.0Kapparmor
368Mapt
13M apt-show-versions
8.0Kdbconfig-common
2.9Mman
4.0Kprivate
664Ksamba
529Gshibboleth
4.0Ktcpdf
root@a:/var/cache#


.
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:42 InCommon-metadata.xml.183f
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:36 InCommon-metadata.xml.38a4
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:29 InCommon-metadata.xml.9cd9
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:23 InCommon-metadata.xml.1a82
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:16 InCommon-metadata.xml.12bd
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:10 InCommon-metadata.xml.e872
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  4 00:03 InCommon-metadata.xml.7823
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  3 23:57 InCommon-metadata.xml.624c
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  3 23:44 InCommon-metadata.xml.2d56
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  3 23:31 InCommon-metadata.xml.4307
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  3 23:17 InCommon-metadata.xml.a8b2
-rw-r--r-- 1 _shibd _shibd 57996190 Jan  3 23:11 InCommon-metadata.xml.6256







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

Kernel: Linux 4.19.0-0.bpo.2-amd64 (SMP w/8 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/bash
Init: systemd (via /run/systemd/system)

-- Configuration Files:
/etc/shibboleth/attribute-map.xml changed [not included]
/etc/shibboleth/shibboleth2.xml changed [not included]

-- no debconf information

Bug#929461: light-locker: Wont unlock or wake screen - have to pkill light-locker after ctrl-alt-f1

[Matt Weatherford]

Package: light-locker
Version: 1.8.0-3
Severity: normal

Dear Maintainer,

When screen locks on Dell Optiplex 9020 w/latest BIOS, i cannot wake it with 
keypresses or mouse movements
have to ctrl-alt-f1 to console, then monitor wakes up. If I ctrl-alt-f7 back to 
grapical console, I get a message about waking up soon - so something is on 
that screen - but it never wakes.
I have to pkill light-locker in order to continue - then everything works again

I am using NFSv41 home directories on this system
I am also using LDAP for user accounts and kerberos for PW. 
Not sure if that affects this or not

thanks for maintaining this package and for supporting Debian!


Some of this extra stuff may also help: (from alternatives)

x-session-manager  auto /usr/bin/mate-session
x-terminal-emulatorauto /usr/bin/gnome-terminal.wrapper
x-window-manager   auto /usr/bin/openbox

-MattW



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

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 light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libdbus-1-3  1.12.12-1
ii  libdbus-glib-1-2 0.110-4
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libsystemd0  241-3
ii  libx11-6 2:1.6.7-1
ii  libxext6 2:1.3.3-1+b2
ii  libxss1  1:1.2.3-1
ii  lightdm  1.26.0-4

light-locker recommends no packages.

light-locker suggests no packages.

-- no debconf information

Bug#929292: autofs: lsstat errors on automounted NFS4.1 share

[Matt Weatherford]

Package: autofs
Version: 5.1.2-4
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***


I am seeing the following in the logs for autofs:


root@libra:~# cd /var/log
root@libra:/var/log# grep DESCRIP  *.log
daemon.log:May 20 14:32:47 libra automount[1399]: rmdir_path: lstat of 
/homes/DESCRIPTION failed

why is automount looking for this file?  It is quite frequent on Debian9 
systems.
I just updated everything on this debian 10 system to see if the issue is here 
also... apparently it is




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

Kernel: Linux 4.19.0-5-amd64 (SMP w/16 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autofs depends on:
ii  libc62.28-10
ii  libxml2  2.9.4+dfsg1-7+b3
ii  ucf  3.0038+nmu1

Versions of packages autofs recommends:
ii  e2fsprogs   1.44.5-1
ii  kmod26-1
ii  nfs-common  1:1.3.4-2.5

autofs suggests no packages.

-- no debconf information