I'm pretty sure this is avoided in Jaunty through the apparmor fix in bug
357581.
Closing as Fix Released, please reopen if you can reproduce it on Jaunty.
The apparmor patch was nominated for an Intrepid SRU.
** Changed in: samba (Ubuntu)
Status: Confirmed = Fix Released
--
silent
Hello! At first i've started having segfaults when trying to sudo, then
i've restarted my machine and could not login at all. To solve this i've
entered recovery mode, opened the root prompt and used this command
apt-get purge -y samba samba-common samba-client libpam-smbpass apt-
get install -y
Hey All,
Has there been any resolution to this. I had the same problems mentioned
in the initial post, changed my 2 pam files, and was able to log back
in. However, now my samba server doesn't start and cups still doesn't
work properly. I had just installed a fresh Ubuntu 8.10 server 2 days
ago
the fix in bug 260687 is making sure /var/lib/samba is created by moving
directory creation to the appropriate package.
It's not solving the segfault that happens if it's not there.
Yes, I'm aware.
However here the problem is different, as it happens with an existing
/var/lib/samba
On 1/22/2009 3:36 AM, Steve Langasek wrote:
Jorrit, you showed a test involving 'mv /var/lib/samba/
/var/lib/samba.bak/' - did you have a /var/lib/samba directory on your
system when the original crash happened that you were reporting?
Steve,
Yes, moving or not moving the directory doesn't
On Wed, Jan 21, 2009 at 01:18:53PM -, Thierry Carrez wrote:
It looks related to bug 303458 (and his evil duplicate bug 302092)
The problem we solved was bug 260687 (libpam-smbpass segfault caused by
missing /var/lib/samba), but there seem to be a case of /var/lib/samba/
contents
By corruption I didn't mean a corrupted bits in a specific file, but
rather a corrupted state for the global /var/lib/samba directory
contents... The basis for this is that in the mentionned bugs clearing
the directory (and especially the existing secrets.tdb file) made
everything working again.
Thierry Carrez wrote:
By corruption I didn't mean a corrupted bits in a specific file, but
rather a corrupted state for the global /var/lib/samba directory
contents... The basis for this is that in the mentionned bugs clearing
the directory (and especially the existing secrets.tdb file) made
Jorrit: it will indeed segfault if there is no /var/lib/samba directory
anymore. But an existing (empty) /var/lib/samba should work (files will
be recreated). That is, if this bug is the same as the other two I
mentionned.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
Thierry Carrez wrote:
Jorrit: it will indeed segfault if there is no /var/lib/samba directory
anymore. But an existing (empty) /var/lib/samba should work (files will
be recreated). That is, if this bug is the same as the other two I
mentionned.
Thierry,
I guess you are right. Creating an
The missing /var/lib/samba dir bug, bug #260687, is purported to be
fixed in version 2:3.2.3-1ubuntu3 - earlier than the version Jorrit
reports is installed.
Walter and Martin, can you tell me whether you have a /var/lib/samba
directory on your affected systems?
Jorrit, you showed a test
Walter and Martin, can you tell me whether you have a /var/lib/samba
directory on your affected systems?
Yes ... I do have that directory.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you
Steve: the fix in bug 260687 is making sure /var/lib/samba is created by
moving directory creation to the appropriate package. It's not solving
the segfault that happens if it's not there.
However here the problem is different, as it happens with an existing
/var/lib/samba directory. Emptying the
13 matches
Mail list logo
