RE: [Bug 534629] Re: AssumeDefaultDomain does not work
The registry editor is lwregshell. It should be in /usr/bin. > -Original Message- > From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of > Gene > Sent: Monday, March 29, 2010 1:22 PM > To: likewise-open-b...@lists.likewiseopen.org > Subject: [Bug 534629] Re: AssumeDefaultDomain does not work > > In a mailing list post I saw reference to a reg editor that was in the > likewise/bin/ folder... that folder does not exist in Ubuntu nor can I > find the program... maybe adding that to the Ubuntu package would help > with this? > > -- > AssumeDefaultDomain does not work > https://bugs.launchpad.net/bugs/534629 > You received this bug notification because you are a member of Likewise > Open Developers, which is subscribed to likewise-open in ubuntu. > > Status in “likewise-open” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: likewise-open > > Setting "AssumeDefaultDomain"=dword:0001 does not work with > likewise-open 5.4.0.39949-3 on Ubuntu 10.04 (development branch) 64 > bit. > > Steps to reproduce: > 1. Install likewise-open, join domain. > 2. Check likewise behavior: getent passwd domain\\testuser returns > information, getent passwd testuser does not. > 2. Change AssumeDefaultDomain to dword:0001 in /etc/likewise- > open/lsassd.reg > 3. Run lwregshell import /etc/likewise-open/lsassd.reg > 4. Run lw-refresh-configuration > 5. Check behavior again: getent passwd testuser does not return > information while it now should... > -- AssumeDefaultDomain does not work https://bugs.launchpad.net/bugs/534629 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568422] Re: Upgrading from likewise-open5 changes home directory locations
I could not reproduce this problem with 'update-manager -d': On Ubuntu 9.10 Desktop amd64, I installed likewise-open5 and joined a domain. I verified the home directory template settings in the configuration (lassd.conf) and logged in as a domain user -- the home directory corresponded to %H/%D/%U. I then upgraded using 'update-manager -d'. At the end of installation and subsequent reboot, I was still able to log in as a domain user to the proper home directory (%H/%D/%U). I checked the registry with lwregshell it reported %H/%D/%U for the HomeDirTemplate. -- Upgrading from likewise-open5 changes home directory locations https://bugs.launchpad.net/bugs/568422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 568422] Re: Upgrading from likewise-open5 changes home directorylocations
I think the package update would explain things. The update overwrote all the existing settings that were present in the registry, ignoring the upgrade. I'll see about fixing that. > -Original Message- > From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of > David Leon > Sent: Monday, May 03, 2010 2:28 PM > To: likewise-open-b...@lists.likewiseopen.org > Subject: [Bug 568422] Re: Upgrading from likewise-open5 changes home > directorylocations > > Scott: > > When I upgraded I could login correctly at first. It took a few days > before I was redirected to the new home directory. There was also a > package update in the meantime. > > Could you check if the configuration files in /etc/likewise-open/ point > to %H/%D/%U after the upgrade too? Could it confuse a subsequent update > if they don't match the registry?. > > -- > Upgrading from likewise-open5 changes home directory locations > https://bugs.launchpad.net/bugs/568422 > You received this bug notification because you are a member of Likewise > Open Developers, which is subscribed to likewise-open in ubuntu. > > Status in “likewise-open” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: likewise-open > > On a machine correctly joined to a domain with likewise-open5: > > The homedir template variable in /etc/likewise-open5/lsassd.conf was > set to its default: > [auth provider:lsa-activedirectory-provider] > ... > homedir-template = %H/%D/%U > > After upgrading to likewise-open on Mon 2010-04-12, package likewise- > open 5.4.0.42111-2 > > /etc/likewise-open/lsassd.conf.reg > [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory] > ... > "HomeDirTemplate"="%H/%D/%U" > ... > [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\Local] > ... > "HomeDirTemplate"="%H/%U" > > /etc/likewise-open/lsassd.reg > [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\ActiveDirectory] > ... > "HomeDirTemplate"="%H/likewise-open/%D/%U" > ... > [HKEY_THIS_MACHINE\Services\lsass\Parameters\Providers\Local] > ... > "HomeDirTemplate"="%H/likewise-open/%D/%U" > ... > [HKEY_THIS_MACHINE\Services\lsass\Parameters\RPCServers\samr] > ... > "HomeDirTemplate"="%H/likewise-open/%D/%U" > > lw-edit-reg showed the same configuration as lsassd.reg > > The change didn't become apparent right away after the upgrade. I could > login normally and get all my files, but a few days later, when I > logged in, I got a new home directory in the new location, looking like > all my files were lost. > > etckeeper recorded a single change, during the upgrade after the apt > run. The files didn't exist previously. > > After a few tries editing the configuration files, changing the > configuration with lw-edit-reg, clearing the ad cache and rebooting I > could finally login and get the old home directory back. > -- Upgrading from likewise-open5 changes home directory locations https://bugs.launchpad.net/bugs/568422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509988] Re: Likewise-open not working in Ubuntu 10.04 alpha 2
The sudoers files needs the format to be this (the ^ becomes an escaped space): %MYDOMAIN\\domain\ users ALL=(ALL) ALL When you log in through gdm, use mydomain\myuser. -- Likewise-open not working in Ubuntu 10.04 alpha 2 https://bugs.launchpad.net/bugs/509988 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 551901] [NEW] likewise-open fails to join domain (lucid)
Can you give us details about the domain? For example, are the DCs running Windows 2000, 2003, or 2008? > -Original Message- > From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of > Matt > Sent: Tuesday, March 30, 2010 10:26 AM > To: likewise-open-b...@lists.likewiseopen.org > Subject: [Bug 551901] [NEW] likewise-open fails to join domain (lucid) > > Public bug reported: > > Binary package hint: likewise-open > > Package: likewise-open > Architecture: amd64 > Version: 5.4.0.42111-1 > uname: Linux 2.6.32-18-generic #27-Ubuntu SMP > > I am unable to join an AD domain. This machine was upgraded from 9.04 > to 9.10, after that update, I was able to join the domain and things > worked fine. I upgraded to 10.04, and the likewise-open upgrade > failed. > I cleaned the old likewise-open install, reinstalled likewise-open and > was unable to join the domain. I also tried using the suggestions > offered in Bug #543963, but that resulted in the same outcome which > follows: > > sudo domainjoin-cli --loglevel verbose join mydomain.com adminuser > Joining to AD Domain: mydomain.com > With Computer DNS Name: mycomputer.mydomain.com > > adminu...@mydomain.com's password: > > (at this point the program pauses for 30 seconds to a minute) > > Error: Lsass Error [code 0x00080047] > > 59 (0x3B) ERROR_UNEXP_NET_ERR - Unknown error > > The last few syslog entries: > > Mar 30 10:19:07 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 589824 (Invalid token was supplied) > Mar 30 10:19:07 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 13 () > Mar 30 10:19:11 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 589824 (Invalid token was supplied) > Mar 30 10:19:11 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 13 () > Mar 30 10:19:12 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 589824 (Invalid token was supplied) > Mar 30 10:19:12 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 13 () > Mar 30 10:19:17 mycomputer lsassd[17901]: 0x7fee6ae8a710:Failed to run > provider specific request (request code = 8, provider = 'lsa- > activedirectory-provider') -> error = 59, symbol = ERROR_UNEXP_NET_ERR, > client pid = 17933 > > ** Affects: likewise-open (Ubuntu) > Importance: Undecided > Status: New > > -- > likewise-open fails to join domain (lucid) > https://bugs.launchpad.net/bugs/551901 > You received this bug notification because you are a member of Likewise > Open Developers, which is subscribed to likewise-open in ubuntu. > > Status in “likewise-open” package in Ubuntu: New > > Bug description: > Binary package hint: likewise-open > > Package: likewise-open > Architecture: amd64 > Version: 5.4.0.42111-1 > uname: Linux 2.6.32-18-generic #27-Ubuntu SMP > > I am unable to join an AD domain. This machine was upgraded from 9.04 > to 9.10, after that update, I was able to join the domain and things > worked fine. I upgraded to 10.04, and the likewise-open upgrade > failed. I cleaned the old likewise-open install, reinstalled likewise- > open and was unable to join the domain. I also tried using the > suggestions offered in Bug #543963, but that resulted in the same > outcome which follows: > > sudo domainjoin-cli --loglevel verbose join mydomain.com adminuser > Joining to AD Domain: mydomain.com > With Computer DNS Name: mycomputer.mydomain.com > > adminu...@mydomain.com's password: > > (at this point the program pauses for 30 seconds to a minute) > > Error: Lsass Error [code 0x00080047] > > 59 (0x3B) ERROR_UNEXP_NET_ERR - Unknown error > > The last few syslog entries: > > Mar 30 10:19:07 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 589824 (Invalid token was supplied) > Mar 30 10:19:07 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 13 () > Mar 30 10:19:11 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 589824 (Invalid token was supplied) > Mar 30 10:19:11 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 13 () > Mar 30 10:19:12 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 589824 (Invalid token was supplied) > Mar 30 10:19:12 mycomputer lwiod[17879]: GSS-API error calling > gss_init_sec_context: 13 () > Mar 30 10:19:17 mycomputer lsassd[17901]: 0x7fee6ae8a710:Failed to run > provider specific request (request code = 8, provider = 'lsa- > activedirectory-provider') -> error = 59, symbol = ERROR_UNEXP_NET_ERR, > client pid = 17933 > -- likewise-open fails to join domain (lucid) https://bugs.launchpad.net/bugs/551901 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568422] Re: Upgrading from likewise-open5 changes home directory locations
I could not reproduce this problem upgrading from Ubuntu 9.10 Desktop amd64. On Ubuntu 9.10 Desktop amd64, I installed likewise-open5 and joined a domain. I verified the home directory template settings in the configuration (lassd.conf) and logged in as a domain user -- the home directory corresponded to %H/%D/%U. I then upgraded using the alternate CD (ubuntu-10.04-rc-alternate- amd64.iso). At the end of installation and subsequent reboot, I was still able to log in as a domain user to the proper home directory (%H/%D/%U). I checked the registry with lwregshell and lw-edit-reg and they reported %H/%D/%U for the HomeDirTemplate. -- Upgrading from likewise-open5 changes home directory locations https://bugs.launchpad.net/bugs/568422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 531812] Re: package likewise-open 5.4.0.39949-3 failed to install/upgrade:
The tool to convert and preserve the configuration is crashing while processing the likewise-open5 configuration files. Could someone attach the likewise-open5 configuration files? They are /etc/likewise-open5/*.conf before upgrading and /etc/likewise- open/5_0_upgrade/*.conf during the upgrade. [Note the path differences.] -- package likewise-open 5.4.0.39949-3 failed to install/upgrade: https://bugs.launchpad.net/bugs/531812 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684579] Re: package likewise-open 6.0.0.53010-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
If you still have this system around, could you send me the file /var/log/likewise-open-install.log so I have some additional detail? Look through it first to make sure it doesn't include anything you don't want to expose online -- though I think it only contains results from commands specific to likewise-open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684579 Title: package likewise-open 6.0.0.53010-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684579] Re: package likewise-open 6.0.0.53010-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Thanks for the log, but it will be a while before I have a solution as I'm going to be away from keyboard for a week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684579 Title: package likewise-open 6.0.0.53010-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845477] Re: /usr/libexec/likewise-open/init-base.sh: 1: [init]: not found
I wasn't aware that it was working -- I thought it was completely broken right now. I'm in the middle of an office split/move and cannot really contribute to fixes. Also, after the move I will not have any real time to work on the likewise-open packaging. Since I thought the package was broken, it seemed like a good idea to remove it rather than have users install it and be disappointed with their Ubuntu experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845477 Title: /usr/libexec/likewise-open/init-base.sh: 1: [init]: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/845477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 854971] Re: likewise-open package missing libnpfs
The npfs component is no longer a component of likewise-open. The product likewise-open 6.1 from BeyondTrust already has a fix in it to remove the dependency on upgrades. I'm attaching a patch, but I haven't/won't be able to test it for some time. ** Patch added: "Remove npfs dependencies in lwio and lsass during the postinstall step." https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/854971/+attachment/2475379/+files/remove-npfs-dependency.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/854971 Title: likewise-open package missing libnpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/854971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969343] Re: Unable to connect to WPA enterprise wireless
Diane Trout's wpa_supplicant fixed things for me with these wireless settings: WPA & WPA2 Enterprise Protected EAP (PEAP) CA certificate PEAP version: Automatic MSCHAPv2 username/password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969343 Title: Unable to connect to WPA enterprise wireless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/969343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845477] Re: /usr/libexec/likewise-open/init-base.sh: 1: [init]: not found
Several scripts are being polluted with logging from 'make'. I'm doing some private builds to create a patch. The bug is because some of the scripts were being edited by sed in the old build system. The new build system, which needed to keep some compatibility with the old build system, continued to use sed but the redirection from sed and verbose logging from make collide to produce a bad file. debian/rules was recently modified to add 'V=1' to the make command line and that's what triggered the bug. I'm modifying the process to use the more correct input-file.in -> input-file transform used in autoconf/MakeKit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845477 Title: /usr/libexec/likewise-open/init-base.sh: 1: [init]: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/845477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655533] Re: [master] package likewise-open 5.4.0.42111-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
@Dave, I'm not sure if likewise-open (6.0.0.53010-4ubuntu5) fixes LP#655533. The logs that this bug was submitted with suggests the problem may be because pam-auth-update couldn't arrange for likewise- open in the PAM stack because of changes made by winbind. I have since marked the likewise-open package as conflicting with winbind. But I don't remember if I tested that scenario at the time and I certainly have not done so in likewise-open (6.0.0.53010-4ubuntu5). My previous reply (#9) was to Michael Vogt (#8) and the particular problem he brought up and I thought we were in a bug about the natty release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655533 Title: [master] package likewise-open 5.4.0.42111-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 766014] Re: likewise-open version 6.0.0.53010-4ubuntu5 failed to build on i386
I'm working on a new version based on Likewise Open 6.1. All versions of Likewise Open have problems compiling with gcc 4.6 because of new warnings. Rather than turn off the warnings, we are modifying the code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/766014 Title: likewise-open version 6.0.0.53010-4ubuntu5 failed to build on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/766014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693704] Re: lwsmd fails to start: undefined symbol: LwIoGetPid
** Changed in: likewise-open (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693704 Title: lwsmd fails to start: undefined symbol: LwIoGetPid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737362] Re: package likewise-open-gui (not installed) failed to install/upgrade: problemy z zależnościami - pozostawiony nieskonfigurowany
Thank you, Chris. It looks like the bug originates with likewise-open -- it's post configuration didn't complete. I'm going to be doing some upgrade testing today to see if I can get this to reproduce. But, could you send me the file '/var/log/likewise-open-install.log'? It may have a clue. And were you (or anyone else) logged in as a domain user while doing the upgrade -- I've never tried that scenario but I doubt it is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737362 Title: package likewise-open-gui (not installed) failed to install/upgrade: problemy z zależnościami - pozostawiony nieskonfigurowany -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737362] Re: package likewise-open-gui (not installed) failed to install/upgrade: problemy z zależnościami - pozostawiony nieskonfigurowany
I think I've got it figured out and it explains so many upgrade problems. Some of the daemon's don't manage their pid files very well and stale pid files are being left around. I'll check in a fix that makes lwregd and netlogond remove their pid files on successful exit and modify the installer to detect stale pid files and remove them. Note that we're already addressing this upstream by completely changing the way daemons are managed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737362 Title: package likewise-open-gui (not installed) failed to install/upgrade: problemy z zależnościami - pozostawiony nieskonfigurowany -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661547] Re: Existing patch gssapi.diff makes guess_service_principal produce garbage
RustyNail: I suggest going to http://www.likewise.com/community/index.php/forums and writing of your problem there. Likewise has support engineers that work with the Open community and they are pretty responsive. The issues you describe sound like environmental problems and they can help determine the cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661547 Title: Existing patch gssapi.diff makes guess_service_principal produce garbage -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 732758] Re: package likewise-open 6.0.0.53010-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Could you attach the log file '/var/log/likewise-open-install.log' ? Note that it may contain a process listing from 'ps', so please scrub it for confidential information before attaching. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/732758 Title: package likewise-open 6.0.0.53010-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 831604] Re: likewise-open users don’t get ecryptfs home directory
I know very little about about ecryptfs. What feature does likewise-open need to support this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/831604 Title: likewise-open users don’t get ecryptfs home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/831604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823717] Re: likewise-open version 6.1.0.406-0ubuntu2 failed to build on armel
PowerBroker Identity Services (Likewise Open) is using a new build system that needs to be taught about ARM. Unfortunately, I have not succeeded in setting up an ARM environment that looks like the build systems used by launchpad. Until I have that, I don't think this will get fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823717 Title: likewise-open version 6.1.0.406-0ubuntu2 failed to build on armel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/823717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572271] Re: CacheEntryExpire setting ignored & default value of 4 hours is too low
I'll look into this -- we call it the 'laptop scenario' we did test it at various points in the development cycle, but perhaps something broke it. But the CacheEntryExpire setting should not determine whether you can log in when offline. It is to determine whether we try to update values from AD. Many APIs request information about a user -- just doing an 'ls' will cause user lookups. If we did a network traversal each time you would suffer horrendous performance. So we cache the values and update them every so often. I think newer releases may have lowered the expiry to a handful of minutes. If you are offline, then expired cache entries are just supposed to be used since there is nothing better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572271 Title: CacheEntryExpire setting ignored & default value of 4 hours is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/572271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572271] Re: CacheEntryExpire setting ignored & default value of 4 hours is too low
About 24 hours ago, I installed likewise-open on Natty, joined a domain, logged in as a domain user through ssh, logged out, and then disconnected the network cable. A few minutes ago, I successfully logged into the box as the same domain user. The 'laptop' scenario does not seem to have regressed in Natty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572271 Title: CacheEntryExpire setting ignored & default value of 4 hours is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/572271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845477] Re: /usr/libexec/likewise-open/init-base.sh: 1: [init]: not found
Should likewise-open be withdrawn from the distribution? I'm not going to be able to offer up any more patches and the current version was broken with the last accepted change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845477 Title: /usr/libexec/likewise-open/init-base.sh: 1: [init]: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/845477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661547] Re: Existing patch gssapi.diff makes guess_service_principal produce garbage
@Thierry: I have installed the openldap package in -proposed and installed likewise-open and successfully joined a domain and logged in [on amd64] and did a few other tests that indicate likewise-open is in the same state of health as in 10.04. Could you give me some guidance as to what to do now? Is there a place to log this success? A series of tests to run? [I looked at qa.ubuntu.com for openldap tests but didn't find anything]. -- Existing patch gssapi.diff makes guess_service_principal produce garbage https://bugs.launchpad.net/bugs/661547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605326] Re: Likewise open 5 or 6 conflicts with winbind
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise- open.fix627272 -- Likewise open 5 or 6 conflicts with winbind https://bugs.launchpad.net/bugs/605326 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591893] Re: likewise-open depends on psmisc
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise- open.fix627272 -- likewise-open depends on psmisc https://bugs.launchpad.net/bugs/591893 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575152] Re: Likewise-Open RequireMembershipOf Does Not Work
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise- open.fix627272 -- Likewise-Open RequireMembershipOf Does Not Work https://bugs.launchpad.net/bugs/575152 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574443] Re: likewise-open5 upgrade mangles RequireMembershipOf settings
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise- open.fix627272 -- likewise-open5 upgrade mangles RequireMembershipOf settings https://bugs.launchpad.net/bugs/574443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572271] Re: CacheEntryExpire setting ignored & default value of 4 hours is too low
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise- open.fix627272 -- CacheEntryExpire setting ignored & default value of 4 hours is too low https://bugs.launchpad.net/bugs/572271 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534629] Re: AssumeDefaultDomain does not work
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise- open.fix627272 -- AssumeDefaultDomain does not work https://bugs.launchpad.net/bugs/534629 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655533] Re: [master] package likewise-open 5.4.0.42111-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I think this *may* be a duplicate of lp: #605326. I think that because DpkgTerminalLog shows winbind installed not long before likewise-open. -- [master] package likewise-open 5.4.0.42111-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/655533 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 647026] Re: package likewise-open 5.4.0.42111-2ubuntu1.2 failed to install/upgrade:
The mixture of version numbers is very confusing. I think there may have been packages created from the upstream git repository in addition to the likewise-open5 package and everything got munged together. ** Description changed: Binary package hint: likewise-open failed under update from 9.10 to 10.04 LTS ProblemType: Package DistroRelease: Ubuntu 10.04 Package: likewise-open 5.4.0.42111-2ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.31-22.63-generic Uname: Linux 2.6.31-22-generic i686 Architecture: i386 Date: Fri Sep 24 17:58:04 2010 ErrorMessage: - ErrorMessage: underproces installed post-installation script returnerede afslutningsstatus 1 + ErrorMessage: underproces installed post-installation script returnerede afslutningsstatus 1 SourcePackage: likewise-open Title: package likewise-open 5.4.0.42111-2ubuntu1.2 failed to install/upgrade: -- package likewise-open 5.4.0.42111-2ubuntu1.2 failed to install/upgrade: https://bugs.launchpad.net/bugs/647026 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661547] Re: Existing patch gssapi.diff makes guess_service_principal produce garbage
Drop the patch in the openldap-xxx/debian/patches directory and edit the 'series' file in the same directory, replacing gssapi.diff with gssapi-2.diff and then build. If this is unfamiliar for you, I could download the latest openldap sources, apply the patch, and upload the sources to my ppa where launchpad will build it and then you could download it. -- Existing patch gssapi.diff makes guess_service_principal produce garbage https://bugs.launchpad.net/bugs/661547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661547] Re: Existing patch gssapi.diff makes guess_service_principal produce garbage
I've added the patched version to my ppa (https://launchpad.net/~ssalley/+archive/ppa/+packages). I suggest rebooting after installing to make sure all processes pick up the new version. -- Existing patch gssapi.diff makes guess_service_principal produce garbage https://bugs.launchpad.net/bugs/661547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605326] Re: Likewise open 5 or 6 conflicts with winbind
likewise-open and winbind both edit configuration files that are present on the system. Most of these files have no defined method for automatically updating them and the algorithms that likewise-open and winbind use come into conflict. The problem is resolved in my branch by having the likewise-open package declare a conflict with the winbind package so that users don't try to use both. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605326 Title: Likewise open 5 or 6 conflicts with winbind -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625105] Re: package likewise-open (not installed) failed to install/upgrade:
>From VarLogDistupgradeTermlog.gz, preparing to replace likewise-open 4.0.5-0ubuntu3.1 (using .../likewise-open_5.4.0.42111-2ubuntu1.2_i386.deb) ... * Stopping the Likewise-open auth daemon ...done. /var/lib/dpkg/tmp.ci/preinst: 75: pam-auth-update: not found >From >http://bazaar.launchpad.net/~ssalley/ubuntu/maverick/likewise-open/likewise-open.fix627272 > revision 19 * Added missing dependencies that prevent distribution and package upgrades from succeeding: - debian/control: Added libpam-runtime (LP BUG 627272, LP BUG 625105) Summary: likewise-open did not declare a dependency on libpam-runtime for pam-auth-update and now it does (in that branch) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625105 Title: package likewise-open (not installed) failed to install/upgrade: -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716615] [NEW] likewise-open 6.0.0.53010-2 fails to build
Public bug reported: Binary package hint: likewise-open The currently checked in version of likewise-open 6.0.0.533010-2 fails to build. Build logs indicate a missing library (or libraries) needs to be added to the link. ** Affects: likewise-open (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716615 Title: likewise-open 6.0.0.53010-2 fails to build -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 567473] Re: Can't login with domain account via ssh in Lucid
I'm the packager for likewise-open and I suggest going to the Likewise forums at http://www.likewise.com/community/index.php/forums and posting of your problem there. They have been very responsive and are pretty good at figuring these issues out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/567473 Title: Can't login with domain account via ssh in Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741335] Re: package likewise-open 6.0.0.53010-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The error I see is that likewise-open failed to complete its configuration and this means likewise-open-gui cannot install. I've checked in a fix ( https://code.launchpad.net/~ssalley/ubuntu/natty /likewise-open/likewise-open-fix-737362/+merge/54272 ) that I'm now waiting for review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741335 Title: package likewise-open 6.0.0.53010-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771773] Re: package likewise-open failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Kayvee: What is '/bin/sh' linked to? I just did a quick test and discovered that 'dash' doesn't have a problem with 'return' at the top level but that 'bash' does have a problem. [POSIX says I should use 'return' at the top level.] I just want to make sure that '/bin/sh' not being dash is a contributing factor before I submit a patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771773 Title: package likewise-open failed to install/upgrade: subprocess new pre- installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771773] Re: package likewise-open failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Correction: POSIX says I should *not* use return at the top level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771773 Title: package likewise-open failed to install/upgrade: subprocess new pre- installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771773] Re: package likewise-open failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Kayvee: ls -al /bin/sh On my system I see that /bin/sh is linked to dash: lrwxrwxrwx 1 root root 4 2009-07-06 13:09 /bin/sh -> dash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771773 Title: package likewise-open failed to install/upgrade: subprocess new pre- installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771773] Re: package likewise-open failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Kayvee: It is a bug in likewise-open that is hidden by the default dash shell. It will be a while before a new package is available, because I need to verify I don't break anything and then need to get it reviewed and approved. It also sounds like your system is set up quite oddly. Normally, /bin/sh is linked to 'dash'. If you have '/bin/dash', you may want to reset it to be your default shell. If you don't have /bin/dash, you may want to install it. Install dash: sudo apt-get install dash Set dash as shell: sudo ln -f -s /bin/dash /bin/sh After doing this, you should be able to complete the likewise-open installation: sudo apt-get install likewise-open -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771773 Title: package likewise-open failed to install/upgrade: subprocess new pre- installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712640] Re: package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: ErrorMessage: installing xserver-xorg-core would break existing software
For what it's worth, I believe this bug to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712640 Title: package xserver-xorg-core 2:1.9.0.902-1ubuntu4 failed to install/upgrade: ErrorMessage: installing xserver-xorg-core would break existing software -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655533] Re: [master] package likewise-open 5.4.0.42111-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
A newer version of likewise-open (6.0.0.53010-4ubuntu5) which fixed upgrade issues in my test environment has been committed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655533 Title: [master] package likewise-open 5.4.0.42111-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 517300] Re: [armel] likewise-open needs porting to ARM
Just FYI: I don't know the entire reason why we (Likewise) didn't take the ARM patch, but I do know we will be supporting ARM, so I don't expect a patch to be needed for 11.11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/517300 Title: [armel] likewise-open needs porting to ARM -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 707195] [NEW] debian/control has spelling errors and wrong versions
Public bug reported: Binary package hint: likewise-open likewise-open 6.0.0.53010-1 has spelling errors and wrong/improper versions in debian/control. These changes in the package descriptions should be made: s/savely/safely/ s/5.4/6.0 And package dependency versions do not match the minimum versions document upstream ** Affects: likewise-open (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/707195 Title: debian/control has spelling errors and wrong versions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724038] [NEW] the tool lwconfig is missing, making it hard to configure likewise-open
Public bug reported: Binary package hint: likewise-open The tool /usr/bin/lwconfig and related configuration file are missing from likewise-open. Likewise uses subversion internally for code management and then mirrors selected portions to an external git repository. The lwconfig directory was mistakenly left out of this mirroring process (since corrected) and I'm now attempting to get it checked in before the freeze. This tools greatly simplifies configuring many common settings and the documentation is leveraging this tool when possible. ** Affects: likewise-open (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724038 Title: the tool lwconfig is missing, making it hard to configure likewise- open -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661547] [NEW] Existing patch gssapi.diff makes guess_service_principal produce garbage
Public bug reported: openldap 2.4.23-0ubuntu3 in Ubuntu 10.10 likewise-open users reported severe failures and I investigated and determined that the patch gssapi.diff (in openldap) contains modifications to guess_service_principal() that are incompatible with recent changes in OpenLDAP and results in random service principal strings. Attached is a replacement patch for gssapi.diff (named gssapi-2.diff) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- Existing patch gssapi.diff makes guess_service_principal produce garbage https://bugs.launchpad.net/bugs/661547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661547] Re: Existing patch gssapi.diff makes guess_service_principal produce garbage
** Patch added: "The same as gssapi.diff without changes to guess_service_principal." https://bugs.launchpad.net/bugs/661547/+attachment/1695785/+files/gssapi-2.diff -- Existing patch gssapi.diff makes guess_service_principal produce garbage https://bugs.launchpad.net/bugs/661547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658799] Re: likewise-open will not join domain: "Error: Lsass Error [code 0x00080047]"
This bug will be fixed when this is fixed: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/661547 -- likewise-open will not join domain: "Error: Lsass Error [code 0x00080047]" https://bugs.launchpad.net/bugs/658799 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640558] Re: Unable to join domain: lsassd[12426]: 0x7fa0f4130710:Failed to run provider specific request (request code = 8, provider = 'lsa-activedirectory-provider') -> error = 31, symbol = ERRO
This bug will be fixed when this is fixed: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/661547 -- Unable to join domain: lsassd[12426]: 0x7fa0f4130710:Failed to run provider specific request (request code = 8, provider = 'lsa-activedirectory-provider') -> error = 31, symbol = ERROR_GEN_FAILURE, https://bugs.launchpad.net/bugs/640558 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575070] Re: Lucid: domainjoin-cli fails error LW_ERROR_ENUM_DOMAIN_TRUSTS_FAILED
I am getting Likewise 6.0 ready for Natty. I don't know how far back we will try to back port. -- Lucid: domainjoin-cli fails error LW_ERROR_ENUM_DOMAIN_TRUSTS_FAILED https://bugs.launchpad.net/bugs/575070 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
