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: AssumeDefaul
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 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
>
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
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
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 corresp
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. [
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
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-ope
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,
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
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
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
@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 p
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
** 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-bu
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
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
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 determin
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
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
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 rece
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.
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 regresse
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://b
@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?
** 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 ma
** 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
u
** 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-bug
** 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.
--
** 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
** 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
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
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
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
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/6
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-o
>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.
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
Stat
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
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 rece
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 contr
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-
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:
packa
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/
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: ErrorMess
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] pac
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://bu
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 ve
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 m
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 resul
** 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 receiv
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
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_G
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 subsc
55 matches
Mail list logo
