[Bug 300542] [NEW] ltsp-build-client fails on Ubuntu 8.10 when can't configure hal

2008-11-20 Thread lipinski
Public bug reported: After upgrading a Ubuntu system from 8.04 to 8.10; ltsp-build-client cannot be completed successfully. Have attempted to entirely remove /opt/ltsp; and run sudo ltsp-build-client, however: Errors were encountered while processing: hal ltsp-client E: Sub-process /usr/bin/dp

[Bug 300542] Re: ltsp-build-client fails on Ubuntu 8.10 when can't configure hal

2008-12-01 Thread lipinski
Let me know if there is more data I can provide for this bug. I need to rebuild some LTSP images, and am stuck right now because the server is on 8.10, and I can't build a new client image with 8.10. I assume people are not having this problem with fresh installs of 8.10, or else LTSP wouldn't wo

[Bug 300542] Re: ltsp-build-client fails on Ubuntu 8.10 when can't configure hal

2008-12-04 Thread lipinski
Found the cause of my problem. Seems that ltsp-build-client will not work if /opt is a symlink. In my case /opt -> /usr/local/opt Once I made /opt a directory, ltsp-build-client worked fine. ** Summary changed: - ltsp-build-client fails on Ubuntu 8.10 when can't configure hal + ltsp-build-clie

[Bug 1644428] Re: Unable to log in with AD account after update

2017-05-05 Thread Mario Lipinski
Since this bug was marked as "fixed" for the earlier release, I opened #1677329. Since I am not familiar with launchpad I failed to setup proper relationships for Zesty. So far I would say that libpam-winbind is completely broken on Zesty. -- You received this bug notification because you are a m

[Bug 1677329] [NEW] libpam-winbind: unable to dlopen

2017-03-29 Thread Mario Lipinski
Public bug reported: The pam winbind module seems to be broken on current 17.04 beta2. Mar 29 18:28:21 daw0 lightdm: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory Mar 29 18:28:21 daw0 lightdm: PAM adding faulty modu

[Bug 997004] Re: Kile complains about "too long lines"

2012-05-22 Thread Doug Lipinski
Same problem here. I wonder who decided this was a nice "feature" to include. Apparently the files that have been opened as read only due to the line length restriction are logged somewhere in ~/.kde/ and are opened as read only in all future instances without a warning. A quick and dirty fix: 1)

[Bug 816750] Re: mpich2 library needs recompile with gfortran 4.5

2011-07-26 Thread Doug Lipinski
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816750 Title: mpich2 library needs recompile with gfortran 4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/m

[Bug 816750] [NEW] mpich2 library needs recompile with gfortran 4.5

2011-07-26 Thread Doug Lipinski
Public bug reported: Ubuntu 11.04 mpich2 1.3.1-1 gfortran 4.5.2 When attempting to compile fortran programs using the mpich2 libraries, the following message is received: Fatal Error: Wrong module version '0' (expected '4') for file 'mpi.mod' This bug has previously been discussed here: http://

[Bug 816750] Re: mpich2 library needs recompile with gfortran 4.5

2011-07-27 Thread Doug Lipinski
Attached a minimal test program to reproduce the error. Attempting to compile gives: $ mpif90 mpich2_bug.f90 -o mpich2_bug mpich2_bug.f90:3.7: use mpi 1 Fatal Error: Wrong module version '0' (expected '4') for file 'mpi.mod' opened at (1) ** Attachment added: "test program to reproduce e

[Bug 816750] Re: mpich2 library needs recompile with gfortran 4.5

2011-07-29 Thread Doug Lipinski
I've verified this bug on 3 different systems, an 2010 Macbook Pro, a Dell PowerEdge T410 server, and a custom built core i7 desktop. On all systems, uninstalling MPICH2 and then compiling from source with gfortran 4.5 solved the problem. -- You received this bug notification because you are a me