lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: likewise-open (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as "Won't Fix".
** Changed in: likewise-open (Ubuntu Maverick)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bu
Hello,
I tried to use the version from their official site (beyondtrust.com)
just like you suggested, but unfortunately it did not work for me.
The problems:
1 - The gui below did not come up. So I still had to add the computer to
the domain using the CLI.
2 - After the computer was added to th
Hi Peter,
I wrote the above a bit before I saw your answer (and I guess you wrote
me before you saw my second post). Anyways, I still need help, hope you
see my previous post and can help with it?
Thanks again,
linux.girl
--
You received this bug notification because you are a member of Ubuntu
To complete the picture above, the procedure I used to install and add
the computer to the domain is this one:
https://help.ubuntu.com/10.04/serverguide/C/likewise-open.html
But I am reading now on likewise.com several things that I should have
that I simply dont. For example:
the /opt is empty,
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of
linux.girl
Sent: Wednesday, February 08, 2012 10:41 AM
To: pet...@xley.com
Subject: [Bug 534629] Re: AssumeDefaultDomain does not work
Hello,
I am using oneiric oncelot 64 bit with likewise version 6.1.0.406 and
assumedefaultdoma
Hello,
I am using oneiric oncelot 64 bit with likewise version 6.1.0.406 and
assumedefaultdomain is not working for me.
Is there a fix for this?
Thanks in advance,
linux.girl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: likewise-open (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: likewise-open (Ubuntu Maverick)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Branch linked: lp:~zulcss/ubuntu/lucid/likewise-open/likewise-open-
sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/534629
Title:
AssumeDefaultDomain does not work
--
ubuntu-bugs mailing list
** Also affects: likewise-open (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: likewise-open (Ubuntu Maverick)
Assignee: (unassigned) => Chuck Short (zulcss)
** Changed in: likewise-open (Ubuntu Maverick)
Milestone: None => maverick-updates
--
You received
** Changed in: likewise-open (Ubuntu Lucid)
Assignee: (unassigned) => Chuck Short (zulcss)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/534629
Title:
AssumeDefaultDomain does not work
--
ubu
** Description changed:
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.
+ IMPACT STATEMENT
+
+
+ Many Likewise Open prefer to set AssumeDefaultD
** Changed in: likewise-open (Ubuntu Lucid)
Milestone: None => lucid-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/534629
Title:
AssumeDefaultDomain does not work
--
ubuntu-bugs mailin
: Joshua McClintock
Subject: [Bug 534629] Re: AssumeDefaultDomain does not work
I downloaded and installed likewise-open_5.4.0.42111-3~ppa9_amd64.deb
After doing this, my default domain works and login's seem to go pretty
smoothy. It would be if this could be added to 10.10, or at least
subm
I downloaded and installed likewise-open_5.4.0.42111-3~ppa9_amd64.deb
After doing this, my default domain works and login's seem to go pretty
smoothy. It would be if this could be added to 10.10, or at least
submit it.
--
You received this bug notification because you are a member of Ubuntu
Bug
I can confirm this is still broken in likewise-open 5.4.0.42111-2ubuntu2
lw-event-cli -s - localhost | grep Assume show "Assume default domain:
true" and i still need to use us\%username% to login
I was unable to get LikewiseOpen 6 to be able to let me log in setting
Assume Default Domain either.
** Branch linked: lp:~ssalley/ubuntu/lucid/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
ub
** Branch linked: lp:~ssalley/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@list
Hmm.. it would be best if lucid would be upgraded to likewise-open
version 6.
As it seems that 5.4 is totally broken with Maverick and version 6
should work with it:
--cut--
With the release of Ubuntu 10.10 (Maverick) changes in the distribution have
caused the version of Likewise-Open available
So...again we're "Fix Committed"...? What, where, and how? Lucid still
says "undecided"...?
--
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 mai
** Branch linked: lp:~ssalley/ubuntu/maverick/likewise-open/likewise-
open.fix62727
--
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
** 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
At my company we simply chose to give up on likewise. We've migrated to
Samba / winbind instead.
--
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
I, sadly, have to echo Jimmy's thoughts on this because a long, sad,
unfunny joke. :(
I've been trying to move our infrastructure towards Ubuntu and off of
SuSE - our other option being Red Hat. This bug is killer - because I'm
basically having to baby the situation along by hand behind the scene
I've also applied the upgrade hoping this issue had been fixed in the
maintstream packages and AssumeDefaultDomian still doesn't work! Running
32-bit on amd64 and intel.
I'm surprised at this, as I had been running the ppa7 version which
fixed the problem but resulted in painfully slow login times
I did an upgrade today that updated my likewise version to likewise-open
5.4.0.42111-3. Not only did this update not fix the assume default
domain issue but also introduced the same issue with home folder
redirection. My home folder is now set to %H/likewise-open/%D/%U. I
had to do a sym link to
Has a fix been rolled out for Ubuntu (Lucid) 10.04 yet? Or do anyone have a
clue about a date?
I'm currently running Likewise-open 5.4.0.42111-2ubuntu1.2 and the bug is still
present.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification
I'll second that. If fix *was* released, what was the fix? Have we
rolled to build 8046 upstream?
--
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-bu
** Also affects: likewise-open (Ubuntu Lucid)
Importance: Undecided
Status: New
--
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
Could we get some info about when this issue is to be "Fix released" and
available in the repos?
--
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
What version was the ppa for likewise when this fix was committed and
verified. Currently the ~ppa7 version fails to start lsassd on an amd64
system and ~ppa6 lsassd only will run when exeucted by hand (lsassd
--start-as-daemon --syslog). lwsm does not start the service correctly
and reports dead
Have we started the SRU (Lucid) process for this as well as (LP:
#575152)?
--
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-bu
Be aware that although build 8046 resolves this bug, the following bug
is still present:
https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/575152
I'm not entirely clear on how they test this stuff, but I'm pretty sure
these are two of the most commonly sought after features, and yet th
Bug *is* resolved in build 8046. Don't let the name throw you either,
this is in fact the right installer.
--
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.
--
u
Those links have compulsory registration. :( That's why I posted the
links I did.
Would be good to know whether the newer builds have this fixed or not.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a member of Ub
Works fine for me using 5.4.0.42111-3~ppa7
$ ssh gcar...@192.168.1.150
Password:
Last login: Fri Jul 30 12:43:28 2010 from hickory.local
gcar...@hickory:~$ pwd
/home/likewise-open/AD/gcarter
gcar...@hickory:~$ id
uid=181931072(gcarter) gid=181928449(Domain^Users)
groups=1544(BUILTIN\Administra
8046 can be had here:
http://www.likewise.com/bits/likewise_cifs/8046/
I'll test this build now.
--
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-bug
I'm investigating. ./sigh
--
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/mai
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2010-0833
--
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-bu
Folks, versions prior to 8046 have a security flaw - Get something
newer, if you can find it see the advisory below:
Likewise Software has posted a security advisor on our Likewise Open
forum announcements
http://cts.vresp.com/c/?LikewiseSoftware/a4f78d058f/1b43a64120/5eac187271.
This n
Well - looks like the bug *did* reappear in 8040.
Wow. So 7985 it is fixed, by 8040 it is busted again.
--
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.
--
ubu
Bug is still present on this other build.
- - - - - - - - - - - - - - - - - - - - - -
Marcos Saraiva
On Tue, Aug 3, 2010 at 15:44, Tony Shadwick wrote:
> Going to give this a shot:
>
>
> http://www.likewise.com/bits/summer09/8040/LikewiseIdentityServiceOpen-5.4.0.8040-linux-x86_64
> -deb-insta
Going to give this a shot:
http://www.likewise.com/bits/summer09/8040/LikewiseIdentityServiceOpen-5.4.0.8040-linux-x86_64
-deb-installer
I'll report how it goes - this is the most recent build available after
7985. One would hope the problem did not spring back up in the later
build...
--
Assu
If it weren't already common knowledge, builds can be quickly obtained
here:
http://www.likewise.com/bits/
--
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.
--
u
Just as an FYI, I first started experiencing this issue on Oracle
Enterprise Linux prior to this release of likewise-open.
On OEL, I went to this version:
LikewiseIdentityServiceOpen-5.4.0.7985-linux-x86_64-rpm
That version works fully as expected upstream, and was downloaded
directly from likew
I also installed the latest Ubuntu patch for this package and the
AssumeDefaultDomain setting is not working. When can we expect this
item to be resolved "in production".
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you ar
The bug appears to be back in ~ppa7-lucid.
I had 'default domain' logins working fine, I did an 'apt-get upgrade'
which fetched a newer version of the PPA and now default domain doesn't
work. Domain logins work - if I put {DOMAIN\\} in front of the login
name, authentication against the AD works.
Does anyone else have an issue after reboot with lsassd not starting
after the first reboot with likewise-open=5.4.0.42111-3~ppa6~lucid? It
runs fine when started manually.
r...@lasras02:~# lwsm list
lwreg running (standalone: 724)
dcerpc running (standalone: 907)
eventlogrunning (s
I can also confirm that the https://launchpad.net/~mgariepy/+archive/ppa
package works. What is the timeframe on getting this fix released? It
is preventing upgrading our servers from hardy to lucid.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this b
Matthew: have you flushed the cache? It will not work on users which
have user account active in the cache before you flush it.
--
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 subscrib
The PPA works for me as well, however "HomeDirTemplate"="%H/%D/%U"
doesn't seem to work, the home dir seems to be always /hone/likewise-
open/%D/%U
But the 'default domain' works now.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification
I can confirm by using that
https://launchpad.net/~mgariepy/+archive/ppa, likewise once again works
as expected on my 32bit laptop (cache creds) and 64 server instance
(cloud). Will we see this soon in a SRU?
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You receive
I had this problem using 32Bit version of 10.04.
I also had the problem with short cached credentials and solved both problems
by using 5.4.0.42111-3~ppa6~lucid from
https://launchpad.net/~mgariepy/+archive/ppa
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You rece
Hi sydenis,
I am not sure why you marked this bug as Fix Released/Commited - it's
not.
Can you please explain or undo your status-change?
Claus
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: likewise-open (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: likewise-open (Ubuntu)
Status: Fix Released => Fix Committed
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a m
This bug is still present for me, using 5.4.0.42111-3~ppa5~lucid and I
also have problems with the following services never running at boot and
I have to start them manually (I added /etc/init.d/service_name start &
in rc.local and this fails too, so I have to start the services manually
after ever
This bug is still present upstream (5.4 build 8040). What upstream build
does the Ubuntu package represents?
--
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.
--
Vide: i386.
I am running the 5.4.0.42111-3~ppa5~lucid build from the PPA,
virtualized under ESXi 4.0:
Linux edge 2.6.32-22-generic-pae #33-Ubuntu SMP Wed Apr 28 14:57:29 UTC 2010
i686 GNU/Linux
Ubuntu 10.04 LTS
Cheers,
Victor
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bu
I am using AMD64 systems.
--
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/mail
It seems that it works OK on amd64 but it doesn't work on i386. I've
added the same repo on both machines and the version is the same a part
from the architecture
Marcos, Alexander, Ninjix, are you using i386 or amd64?
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
Y
Now that is strange.. I've got a machine where the fix works (mine) and
another on a colleague's PC with the same exact configuration (copied
from my machine), the same exact likewise-open build (from your PPA) and
there it still doesn't work. It accepts logins only with
DOMAIN\username, not userna
Yeah, I saw this too. There's a patch for that but it seems that was
ignored.
http://www.mail-archive.com/screen-de...@gnu.org/msg00186.html
I'll open a wish in Ubuntu Launchpad so Ubuntu could apply this patch.
If this is the new and definitive likewise behavior, more people are
going to see thi
I see. I wonder what the actual length limitation is. The name
"AD\gcarter" works fine, but "ATLANTIS\Administrator" fails. Looks like
a bug in screen filed upstream. http://savannah.gnu.org/bugs/?21653
** Bug watch added: GNU Savannah Bug Tracker #21653
http://savannah.gnu.org/bugs/?21653
Gerald: I simply try to execute screen with "screen" :)
My unix name is now 8 (domain name) + 1 (slash) + 14 (username) so it sums 23.
And I can't change anything in my scenario.
Any suggestion?
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug no
The current behaviour is by design. I run screen with AD usernames and
don't see that error log. What are you doing to get the error msg?
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a member of Ubuntu
Bugs, which
It works for me too but there is still a problem/different behaviour
respect to 9.10. Now when I login I've always get "DOMAIN\username" as
my unix username while before it was simply "username". This poses
problems with, for example, "screen" which complain about "LoginName too
long". Is this a bu
I confirm the fix in PPA build.
Thanks, Gerald!
--
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:
Can confirm the fix works also for me.
However I do see a change in how username checks are handled. Before the
AssumeDefaultDomain setting worked I could match 'domain\username' in
group and sudo checks without problems. It didn't matter how the
username was actually registered in AD (i.e. 'DOMAI
It was an upstream bug that was fixed and backported to the Ubuntu
packages. Will take one week minimum to get it into Lucid from what I
understand. We'll put new 5.4 packages on likewise.com some time next
week.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You re
Thanks, the fix works for me too. But i have to ask...will this be fixed
upstream, or is it Ubuntu specific? It also affects 5.4.7985 (unstable),
which made me roll back to 7939 for the linux workstations that do not
run Ubuntu.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs
5.4.0.42111-3~ppa5~lucid
Seems to be working for me as well.
How long do these typically take to get into the official repository?
--
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 su
Thanks for the feedback. Once I get verification on a couple of other
fixes in that package, I'll submit the upload request.
** Changed in: likewise-open (Ubuntu)
Status: In Progress => Fix Committed
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received
Hello,
just to say that i've update to likewise-open_5.4.0.42111-3~ppa4~lucid_i386.deb
and now the "AssumeDefaultDomain" setting works!
Thanks!
Best Regards
NBA
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a membe
We have a fix in testing. I will generate new packages for the likewise
open PPA in the next 24 hours hopefully and let you know.
** Changed in: likewise-open (Ubuntu)
Status: Confirmed => In Progress
** Changed in: likewise-open (Ubuntu)
Assignee: (unassigned) => Gerald Carter (coff
As with many of the other posters here, we have placed our plans to
upgrade to 10.04 on hold, pending the resolution of this bug and bug
572271 which Pasi refers to above.
I would also like to note that some of the configuration settings stored
in the registry, such as HomeDirTemplate, are honored
@Juergen,Neskie: The 5.4 documentation says: "Note: With Likewise
Enterprise, you can manage this setting by using a Likewise group
policy; see Set the Cache Expiration Time in the Likewise Enterprise
guide."
However this means that you can use Windows Active Directory Group
Policies to modify the
@Juergen if that's true, then that doesn't seem like a thing to be
promoting as the Ubuntu solution for joining machines to Active
Directory.
@Christian
I did the same following
https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
--
AssumeDefaultDomain does not work
https://bugs.launch
Same for me. My installation depends on a smooth integration into my
Windows Domain, and without a fix for this bug I'm not going to upgrade
and stay with 9.10
If I read the Likewise 5.4 documentation correctly, they evaluate the
AssumeDefaultDomain flag only in the enterprise version, so I specul
lw-eventlog-cli -s - 127.0.0.1
lists following:
...
Assume default domain: true
...
but default domain is not used.
This breaks many things, so we stopped 10.04 Upgrade project.
maybe possible workaround:
* uninstall OpenLikewise
* install Samba / winbindd
* set up pam_winbin
Based on feedback from this (http://www.mail-archive.com/likewise-open-
disc...@lists.likewiseopen.org/msg00142.html) post, I have tried using
the lwregshell command to get the AssumeDefaultDomain setting to change
in the "registry". So far, I haven't been totally successful. Okay, I
haven't even b
This is not the worst bug in the current release of likewise in lucid..
but would definitely stop me upgrading.
The worst is that you are not able to login on to your computer after 4
hours when offline (https://bugs.launchpad.net/ubuntu/+source/likewise-
open/+bug/572271). ;)
--
AssumeDefaultDo
Confirmed also in 10.04 LTS, Likewise open version 5.4.0.42111-2ubuntu1.
--
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
** Changed in: likewise-open (Ubuntu)
Importance: Undecided => Medium
--
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
Confirmed here as well. Ouch!
This will slow my 9.10 -> 10.4 upgrade plans for my user workstations.
This is one of those "paper cuts" that will annoy users. Hopefully it
gets corrected soon considering Canonical is advertising improved
Likewise-Open 5.4 Active Directory integration as a leading f
Some investigation leads me to believe this might be due to a change
that transitioned lsassd away from using the system krb5.conf which
contains the default realm. Just an update. No solution at this time.
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received
I confirm this bug in 10.04 beta 2.
--
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.ubunt
I believe I have seen this bug also in 10.04 beta 2
--
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
ht
t: [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?
>
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/5346
AssumeDefaultDomain works for me when using 5.4.7939 (5.4.0
build/release 7939 from upstream) from ~2009-12-09.
I'm out of my element here, but I'm hitting two issues.
First, AD_FindObjectByAliasNoCache in online.c:3465 is returning 'Error
code 40081 (LW_ERROR_NOT_SUPPORTED).'
Overriding that, '
>From what I can gather, 42111 appears to be an svn revision that is
roughly matchable in the git log in the upstream repository [1]. The
5.4.0.7985 upstream release from 2010-01-28 also has this bug, but I
would speculate that likewise-open=5.4.0.42111-1 currently in lucid is
from approximately 20
Confirmed in likewise-open_5.4.0.42111-1~ppa1~lucid from the likewise-
open-development PPA
** Changed in: likewise-open (Ubuntu)
Status: New => Confirmed
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a membe
I confirm this bug, in ubuntu 10.04, likewise open version 5.4.0.39949-3
Moreover in my opinion , a GUI would be needed to configure the .reg file.
Regards
--
AssumeDefaultDomain does not work
https://bugs.launchpad.net/bugs/534629
You received this bug notification because you are a member of U
** Tags removed: kernel-series-unknown
--
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.ub
** Tags added: kernel-series-unknown
--
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.ubun
95 matches
Mail list logo
