We're planning on sticking with Lucid until the next LTS. Given that
this is a very basic issue that affects every desktop user I would have
to request for this to be backported. Is there any specific place to
request this?
--
Open with Other Application remember feature does not work
FWIW, my ssh stopped working again, even after fixing the home directory
and upgrading to the latest PPA deb. I don't know if it involves some
sort of timeout and that's why I could login at first.
Interestingly I can scp and sftp to that machine without problem. It's only the
interactive login
Same thing happens to us, upgrading from karmic with likewise-open5
It couldn't reload the service manager configuration, and later when apt
retries, it fails because lwsmd was already running from the first try
(but apparently everything worked?). No actual error messages are
written out.
** Changed in: evolution (Ubuntu)
Status: New = Confirmed
--
cannot turn on alarm for meeting received via email
https://bugs.launchpad.net/bugs/528557
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Upstream bug comments this was tested on Ubuntu Lucid. Any chance of
getting this added to a Lucid update and/or PPA?
This is a showstopper for migrating desktops in our exchange-based
environment.
--
cannot turn on alarm for meeting received via email
https://bugs.launchpad.net/bugs/528557
You
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
As a workaround, just remove command-not-found-data and things work
fine.
For some reason it's marked as installed manually so it's not removed
when you remove command-not-found.
--
[lucid] command-not-found can't be removed properly using apt
https://bugs.launchpad.net/bugs/561046
You received
Public bug reported:
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
Actually, It seems to be working now.
I don't know if this is related, but today when I logged in, I noticed
my home directory changed to /home/likewise-open/DOMAIN/myusername, when
it used to be /home/DOMAIN/myusername. Apparently, one of the upgrades
(karmic-lucid, partial upgrade) changed
Public bug reported:
Binary package hint: likewise-open
Can't login with domain account with likewise-open via ssh
When connecting via ssh to Ubuntu Lucid running likewise-open and
correctly joined to a domain:
domain\myusern...@server:~$ ssh localhost
Password:
Connection to localhost closed
** Attachment added: sshd log
http://launchpadlibrarian.net/44919293/logsshlucid1.txt
--
Can't login with domain account via ssh in Lucid
https://bugs.launchpad.net/bugs/567473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: sshd log without PrintLastLog
http://launchpadlibrarian.net/44919371/logsshlucid2.txt
--
Can't login with domain account via ssh in Lucid
https://bugs.launchpad.net/bugs/567473
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: sshd log - Succesful connection to Karmic
http://launchpadlibrarian.net/44919437/logsshkarmic.txt
--
Can't login with domain account via ssh in Lucid
https://bugs.launchpad.net/bugs/567473
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: lucid
--
Can't login with domain account via ssh in Lucid
https://bugs.launchpad.net/bugs/567473
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
More information: On Karmic, SSH doesn't seem to understand the ipv6
prefix of the display, unless the display number is 0.
server1: echo $DISPLAY
:::10.50.50.129:4.0
server1:~$ xauth list
##3a3a3a31302e35302e35302e313239#:4 MIT-MAGIC-COOKIE-1
88d9f68e0648ff171df763364d5e9439
More information: On Karmic, SSH doesn't seem to understand the ipv6
prefix of the display, unless the display number is 0.
server1: echo $DISPLAY
:::10.50.50.129:4.0
server1:~$ xauth list
##3a3a3a31302e35302e35302e313239#:4 MIT-MAGIC-COOKIE-1
88d9f68e0648ff171df763364d5e9439
This bug still exists in Jaunty. Are there plans to include the fix in
Jaunty or Karmic?
--
javascript script support through rhino should not be on bootclasspath
https://bugs.launchpad.net/bugs/255149
You received this bug notification because you are a member of Ubuntu
Bugs, which is
17 matches
Mail list logo
