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
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
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
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
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
Jorrit,
On Tue, Jan 20, 2009 at 09:23:48PM -, Jorrit Kronjee wrote:
I ran into the same issue just yesterday. sudo started segfaulting right
after installing a few samba-related packages. I've been able to make a
backtrace (see attachment).
Thanks very much! I don't know why the
Steve:
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
corruption triggering a similar segfault.
--
silent login/gdm
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
Steve,
I ran into the same issue just yesterday. sudo started segfaulting right
after installing a few samba-related packages. I've been able to make a
backtrace (see attachment).
Commenting out the line with pam_smbpass.so in /etc/pam.d/common-auth
has fixed the problem for me.
** Attachment
Steve,
I did a little thinking and some poking about on my 8.10 partition.
I looked at auth.log and noticed several of the following:
Jan 2 20:32:37 2kbox gdm[5340]: pam_unix(gdm:auth): auth could not
identify password for [WEB]
WEB is my 98box user name. The 2kbox (8.10) should be web (lower
Michael, yes, apt-get install libpam-smbpass should be enough to try to
reproduce the problem again, and apt-get remove libpam-smbpass should be
sufficient to restore your 8.10 system to working order so you can make
productive use of it in between debugging sessions.
--
silent login/gdm
Walter,
This recipe should permit reproducing the crashes from your intrepid
system; if you can confirm this to be the case, we can go from there on
trying to get debugging information out of it.
$ sudo chroot /media/disk su username
$ sudo -s
where username is the name of your admin user on
Hi Steve,
Note that there is an icon on my desktop for 9.6 GB Media. It also shows
under PlacesComputer.
It is my /media/disk folder.
I opened terminal and got this:
w...@2kbox:~$ sudo chroot /media/disk su web
[sudo] password for web:
bash: /dev/null: Permission denied
bash: /dev/null:
Hmm ... just found out that these comments can't be edited in any
obvious way ...
I also found the following folder:
/media/disk/usr/share/doc/libpam-smbpass/
which contains a readme, a to-do, a copyright, several .gz files and an
examples folder.
There are no libpam-smbpass files on the Hardy
When I had the same problem before, libpam-smbpass was installed. Removing
samba completely removed that package. Libpam-smbpass was installed when I
shared a folder (which prompted me to have samba installed automatically).
The problem started when I tried stopping a shared printer with ongoing
Steve it seems I did have libpam-smbpass installed. Will it be
sufficient for me to apt-get install that package again and try to
reproduce or do I need to configure in some particular way?
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
Michael, did you have the libpam-smbpass package installed previously?
This failure is still not reproducible for me here; are you in a
position to reinstall libpam-smbpass to see if the problem reappears for
you?
Walter, do you have libpam-smbpass installed on your inaccessible
intrepid install?
Steve, I have the following files and locations on my 8.10 inaccessible
drive:
/media/disk/etc/logcheck/ignore.d.server/libpam-smbpass
/media/disk/var/lib/dpkg/info/libpam-smbpass.conffiles
/media/disk/var/lib/dpkg/info/libpam-smbpass.list
/media/disk/var/lib/dpkg/info/libpam-smbpass.md5sums
I can confirm that I have the same unable to log in issue with Intrepid 8.10.
First, a little history ...
Several months ago I burned an ISO of Hardy Heron 8.04.
Two weeks ago I finally got around to trying it and decided to install it.
I installed the recommended upgrades and used it for a day or
On more thing on the residual problem I had with session unlock: I found
the solution. It's another bug:
https://bugs.launchpad.net/bugs/279560
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification
I would like to add, I also experienced this bug today. Everything was
working nicely and I tried to change the halftoning setting for my
printer via the CUPS HTTP admin interface. CUPS crashed, and I was
unable to access any samba shares. When I attempted to login via SSH, I
got prompted for my
Sorry I should add that I'm using ubuntu server 8.10 and have not
installed any exotic/non standard packages.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks! That worked out well. I also removed samba and samba-client, then
reinstalled them, and everything worked well again.
2008/12/25 Luca A luca.azzal...@gmail.com
To mangwills:
you have to reboot, choose safe mode. You get into a text-mode menu.
Choose open root session (or similar. I
To mangwills:
you have to reboot, choose safe mode. You get into a text-mode menu.
Choose open root session (or similar. I can't remember exactly). From
there you can modify the files. You must use a terminal-based editor
like vi, nano or emacs. I suggest to use nano, it's the simplest one.
When
I've encountered the same problem twice already. If the user that can't
login due to the problem is the admin account, how can I edit the
common-auto and common-password files?
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You
Yes it's safe to remove ubuntu-desktop but it's better to reinstall to
avoid errors with upgrading.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I went on removing all the mentioned packages and the reinstall.
I'm still having the problem with lock session in gnome. However login works
properly with the common-auth and common-password set to their original states.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
I confirm this problem. For about two weeks I was unable to login. I
don't know if I did any changes to the system.
- Local login always displayed the login-promt again
- ssh closed connection
- authentication for root-permissions within gdm was not possible, it reacted
as if the cancel-button
Thnak you guys for your info.
When I try to mark for complete removal samba-common from synaptics, it tell
me that it will remove also ubuntu-desktop (amongh others packages). Is it safe
to continue?
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
Luca A (and all).
I had the same original problem of the looping login / segfaults and
then samba problems (post 14 here). I had followed all the suggestions
here and ran into the same issue that Luca A has.
After some help from jrib and marcelkoopman on #ubuntu
(irc.freenode.net) I got
ok, thanks for trying anyway!
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Soldberg, ariel.darkserver
are you having the same problem as I have? I mean I cannot use anymore the
lock session functionality, in gnome. If I do, I cannot log back in, it
refuses my password.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
Luca A,
since I have changed the common-auth and common-password, I don't have any
login problems. lock session in gnome and login in again works fine.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug
** Summary changed:
- login impossible, no error message
+ silent login/gdm failures and sudo segfaults with smbpasswd enabled
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a
54 matches
Mail list logo
