I just reinstalled Maverick and applied all updates. Problem was only
corrected when I performed comment #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669279
Title:
[ICH4 - Intel ICH6] Dell Lati
Alroger is right. Just noticed I was bit by this same bug after using
Alt installer for Maverick laptop running on LUKS LVM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/438520
Title:
Right Alt key
Here's a link to the Proxmox sources for their deb packages.
ftp://download.proxmox.com/sources/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669818
Title:
Update to 10.04 2.6.32-25 as KVM Guest n
We have also run into the problem on our AMD Opteron KVM hosts and I'm
the author of the Proxmox post. The problem seems related to SMP.
Setting the guest to run with only one core works.
I see that there was a SMP kernel update in the 2.6.32-25 revision.
Could this have caused a regression?
http
Any update on Pasi's question about release to lucid-updates?
--
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-bug
All,
Looks like the fix is in testing. I received a reply on the Likewise
Open forum covering the same bug.
http://www.likewise.com/community/index.php/forums/viewthread/697/
--
CacheEntryExpire setting ignored & default value of 4 hours is too low
https://bugs.launchpad.net/bugs/572271
You rec
Thank you Marc for posting your PPA. I restarted the lsassd service
after upgrading to the ppa6 version and now the "Cache entry expiry"
shows the hex changes I've made using lw-edit-reg.
-- Before --
Event Record ID. 155
Event Table Category System
Event Type.. Information
Gerald, any update on the PPA release with the fix?
Thanks.
--
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
This is a long-shot. Have you checked the time sync between your Lucid
machines and the AD server? I recall seeing this odd error but it went
away after I installed NTP and reboot the workstation. Note, I was
troubleshooting something else and didn't investigate the TRUST error.
--
Lucid: domainj
Hi Gerald,
Any update on the progress being made on this bug. We can't upgrade our
laptop users to Lucid until this enterprise show-stopper gets fixed.
Thanks for your time and effort. It is appreciated.
--
CacheEntryExpire setting ignored & default value of 4 hours is too low
https://bugs.laun
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
I see what appears to be a similar bug posted in the Debian tracker with
an upstream fix.
01ifupdown errs out on vpn connection change events
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518530
--
[8.10] Error: Failed to set IPv4 route
https://bugs.launchpad.net/bugs/294394
You received this
I am seeing the same nm-dispatcher ifupdown error in Lucid when I try to
connect to my university's VPN. It is able to connect and receives all
of the routes but no traffic passes to the remove network.
May 12 10:12:07 sps31-728-ckr1 NetworkManager: Policy set 'Auto eth0'
(eth0) as default for
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:
I'm now testing with Carter's PPA builds. I've set my cache entry expiry
to 90 days. That should be long enough for any of our laptops or less
used workstations.
$ aptitude show likewise-open
Package: likewise-open
New: yes
State: installed
Automatically installed: no
Version: 5.4.0.42111-3~ppa5~l
Public bug reported:
Binary package hint: likewise-open
Attempting to troubleshoot likewise-open bug 572271, I discovered a
problem with using sql_filter arguments with lw-eventlog-cli.
$ sudo lw-eventlog-cli -c "(EventRecordId < 1000) AND (EventType = 'Warning')"
127.0.0.1
Error: An invalid ev
Some more testing but no success.
I stopped the lsasd service, made a backup of the registry.db file and
then tried manually inserting 2592000 (30 days) into the
CacheEntryExpiry value.
Restarted the service and ran lw-eventlog-cli -s - localhost to see
there was any change. There wasn't.
Event
I was looking around in the /var/lib/likewise-open/db/registry.db file
and see what appears to be null entries in the regvalues1 table. Is this
correct? I'm wondering if there is a problem with the values getting
stored for the CacheEntryExpiry and the lsasd service is just running on
magic number
This is a show stopper and will prevent deployment of Lucid laptop at
our organization. I recommend increasing the default cache expiration as
suggested by Pasi. Four hours is way to short and doesn't work for
enterprise.
--
CacheEntryExpire setting ignored & default value of 4 hours is too low
h
I am seeing this bug in the 10.4 official release. It started for me
after I added network-manager-openvpn-gnome. Why this OpenVPN package is
affecting VPNC tunnels, I can only guess.
--
network-manager-vpnc does not recognize group secrets from cisco .pcf
https://bugs.launchpad.net/bugs/363027
Y
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
Forgot to include my package version in my previous post:
Package: likewise-open
New: yes
State: installed
Automatically installed: no
Version: 5.4.0.42111-2
--
likewise package on lucid : Can no longer login to Windows domain
https://bugs.launchpad.net/bugs/543963
You received this bug notifica
I just found this bug track after encountering the same
CENTERROR_DOMAINJOIN_LSASS_ERROR error message. My problem resulted
after I joined a new Lucid machines to our domain for our Lucid pre-
release testing. It worked and I then ran the domainjoin-cli leave
command. That worked as well.
The pro
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/44168067/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44168068/Dependencies.txt
** Attachment added: "Df.txt"
http://launchpadlibrarian.net/44168069/Df.txt
** Attachment added:
Public bug reported:
Binary package hint: likewise-open
I got this error after removing likewise-open with apt-get remove
--purge and then trying to reinstall.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: likewise-open 5.4.0.42111-2
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic
Public bug reported:
Binary package hint: ubuntu-docs
Please add a few lines of instruction describing how to use kpasswd to
change Windows user account password from Ubuntu on the official
Likewise Open online documentation. This will help new users.
https://help.ubuntu.com/9.10/serverguide/C/l
Tom: Your private key password conversion tip rocks. Saved me a bunch of
troubleshooting headaches and nudged me to be more secure with my keys.
Thanks!
--
VPN connection fails: "unable to find valid VPN secrets" (auth dialog crash
when secrets exist)
https://bugs.launchpad.net/bugs/284212
You r
27 matches
Mail list logo
