Feedback: "Authorization Dialog" bug in Samba for 11.2

caprus · April 12, 2010, 8:51pm

In response to the sticky at Fixing “Authorization Dialog” bug in Samba for 11.2 - openSUSE Forums

I have the greatest regard for Swerdna, his advice has saved me countless hours over the past few years, but…

When I updated as suggested I got the following results, some sorta good, some horrible and not easy to resolve.

Good:

The immediate problem dissappeared and I was now able to browse the LAN again (using Dolphin)… sort of… well it worked 90& of the time, sometimes the bogus authenication window still came up (still unresponsive too), but I could browse by hitting the back button and retrying.

Bad:

Browsing the LAN is now very, very slow.

I’m completely unable to browse this PC’s shares from the LAN or from itself. The icon for the PC shows up, but when I click on it I get no response for 30 - 60 seconds then sometimes a list of shared folders, none of which can be accessed, and sometimes the bogus authentication window.

Unable to use pdbedit. For example:# pdbedit -L -w
Unknown parameter encountered: “pasdb backend”
Ignoring unknown parameter “pasdb backend”
Whenever the PC boots now I get a warning that “Either another instance of OpenOffice is accessing your personal settings or your personal settings are locked. Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure user ‘myusername’ closes OpenOfice.org on host ‘this-pc’.”
(No OpenOffice app has even been opened on this PC for several days.)

So I decided to roll back to the old versions of the Samba files (from the install DVD). All of the anomilies listed above still occur.

Note: This PC has not been in use for any other purpose (ex, browsing the web in Firefox to find info on this issue) during the period I’ve been working on this problem so I suspect that this “solution” has caused more problems than it solved.

PS, I’m using the same smb.conf, firewall settings, etc that worked fine for several months prior to the recent update.

caprus · April 12, 2010, 9:13pm

The OpenOffice error was resolved by going into the options in OpenOffice and clicking on “save changes” even though I’d made no changes. I’m not convinced this problem was related to the “Authorization Dialog” bug issues, but the timing sure is suspicious.

swerdna · April 14, 2010, 11:45pm

Just noticed this thread.

Sounds to me a bit like there were mixed library files updated. If the slowness and the occasional appearance of the bogus authentication window persists (probably it does), then please check and post here the samba file and library versions with this command (maybe use copy & paste for this code):

caprus · April 16, 2010, 1:34pm

(Sorry to be so slow to reply, tied up on a project yesterday)

Happy to report that I haven’t seen the bogus Authentication window for 48 hours.

Here’s the data you requested:
~> rpm -qa | egrep “cifs-mount|libldb0|libsmbclient0|libtalloc2|libtdb1|libtevent0|libwbclient0|samba|samba-client”
libtdb1-32bit-3.4.2-1.1.3.1.x86_64
libsmbclient0-32bit-3.4.2-1.1.3.1.x86_64
cifs-mount-3.5.2-1.1.x86_64
yast2-samba-client-2.18.3-2.2.noarch
libwbclient0-3.4.2-1.1.3.1.x86_64
samba-doc-3.4.2-1.1.3.1.noarch
libtdb1-3.4.2-1.1.3.1.x86_64
libwbclient0-32bit-3.4.2-1.1.3.1.x86_64
libsmbclient0-3.4.2-1.1.3.1.x86_64
samba-3.4.2-1.1.3.1.x86_64
samba-client-32bit-3.4.2-1.1.3.1.x86_64
samba-client-3.4.2-1.1.3.1.x86_64
samba-32bit-3.4.2-1.1.3.1.x86_64
yast2-samba-server-2.18.2-2.1.noarch

Thanks again for your time and attention.

swerdna · April 16, 2010, 3:38pm

I can see only these discrepancies:

libtalloc2-3.4.2-1.1.3.1.x86_64 has been removed in the update/rollback process
samba-32bit-3.4.2-1.1.3.1.x86_64 has been added but shouldn’t be installed
cifs-mount didn’t get rolled back to 3.4.2-1.1.3.1 with the other RPMs

So if you install RPM 1 and uninstall RPM 2 and roll back cifs-mount, that might change things for the better.

Also, this line is concerning: Unknown parameter encountered: “pasdb backend”
It’s possible you have changed (somehow) the [global] stanza of the file /etc/samba/smb.conf. Can you run this command:

cat /etc/samba/smb.conf

and make sure this line is in the [global] stanza:

passdb backend = tdbsam

notice the spelling is “passdb”.

caprus · April 17, 2010, 4:48pm

libtalloc2-3.4.2-1.1.3.1.x86_64 has been removed in the update/rollback process
I can’t find this file anywhere. I’ve only been only to find it as libtalloc2-3.5.2-1.1.x86_64, not as libtalloc2-2.3.4.2-1.1.3.1.x86. Any suggestions?

samba-32bit-3.4.2-1.1.3.1.x86_64 has been added but shouldn’t be installed
removed

cifs-mount didn’t get rolled back to 3.4.2-1.1.3.1 with the other RPMs
rolled back to 3.4.2-1.1.3.1

Also, this line is concerning: Unknown parameter encountered: “pasdb backend”
It’s possible you have changed (somehow) the [global] stanza of the file /etc/samba/smb.conf. Can you run this command:
cat /etc/samba/smb.conf 
and make sure this line is in the [global] stanza:
passdb backend = tdbsam
notice the spelling is “passdb”.
“pasdb backend = tdbsam” changed back to “passdb backend = tdbsam” (no idea how or when that error happened:.… )

I can now see and browse this PC again from the LAN, although it’s almost unbelievably slow.

Reran

pdbedit -L -w

Now I no longer get any error message,and I can see the users. I was also able to add a user, So we’re certainly making progress.

swerdna · April 17, 2010, 9:59pm

Think about upgrading to the version in the Samba repo. Once you add the repo it’s a one-click process (for KDE users) like so:

KDE users can use the GUI one-click link to “switch system packages to versions in the Samba Repo”.

While you’re deciding, can you post your smb.conf file? If “pasdb” got changed, maybe something else is wrong too.

caprus · April 17, 2010, 10:42pm

~> cat /etc/samba/smb.conf

smb.conf is the main Samba configuration file. You find a full commented

version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the

samba-doc package is installed.

Date: 2008-12-03

[global]
workgroup = XXXX
netbios name = XXXX
server string = greyshark-XXXX
name resolve order = bcast host lmhosts wins
passdb backend = tdbsam
printcap name = cups
cups options = raw
map to guest = Bad User
#include = /etc/samba/dhcp.conf
#logon path = \%L\profiles.msprofile
#logon home = \%L%U.9xprofile
#logon drive = P:
usershare allow guests = Yes
hosts allow = 192.168.0.0/255.255.255.0, 127.0.0.1
local master = yes
os level = 33

[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes

[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700

[users]
comment = All users
path = /home/
inherit acls = yes
veto files = /aquota.user/groups/shares/

[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

[PUBLIC]
path = /home/greyshark/Public/
guest ok = yes
read only = no

swerdna · April 17, 2010, 11:20pm

That smb.conf looks OK to me. The issue seems to have flowed from the buggy files triggered by the update repository. All I can suggest it to update using the one-click link in the KDE version of Yast, and then check the file list against this one:

john@suse112:~> rpm -qa | egrep “cifs-mount|libldb0|libsmbclient0|libtalloc2|libtdb1|libtevent0|libwbclient0|samba|samba-client”
libtalloc2-3.5.2-1.1.x86_64
libldb0-3.5.2-1.1.x86_64
libwbclient0-3.5.2-1.1.x86_64
yast2-samba-client-2.18.3-2.2.noarch
libsmbclient0-3.5.2-1.1.x86_64
samba-3.5.2-1.1.x86_64
cifs-mount-3.5.2-1.1.x86_64
libwbclient0-32bit-3.5.2-1.1.x86_64
libtevent0-3.5.2-1.1.x86_64
libtdb1-32bit-3.5.2-1.1.x86_64
samba-client-32bit-3.5.2-1.1.x86_64
yast2-samba-server-2.18.2-2.1.noarch
samba-client-3.5.2-1.1.x86_64
libtdb1-3.5.2-1.1.x86_64

caprus · April 17, 2010, 11:20pm

~> rpm -qa | egrep "cifs-mount|libldb0|libsmbclient0|libtalloc2|libtdb1|libtevent0|libwbclient0|samba|samba-client"
libtdb1-32bit-3.5.2-1.1.x86_64
cifs-mount-3.5.2-1.1.x86_64
yast2-samba-client-2.18.3-2.2.noarch
libsmbclient0-32bit-3.5.2-1.1.x86_64
libtdb1-3.5.2-1.1.x86_64
samba-client-3.5.2-1.1.x86_64
libtalloc2-3.5.2-1.1.x86_64
libsmbclient0-3.5.2-1.1.x86_64
samba-3.5.2-1.1.x86_64
libwbclient0-32bit-3.5.2-1.1.x86_64
samba-client-32bit-3.5.2-1.1.x86_64
libwbclient0-3.5.2-1.1.x86_64
libldb0-3.5.2-1.1.x86_64
yast2-samba-server-2.18.2-2.1.noarch
samba-doc-3.5.2-1.1.noarch
libtevent0-3.5.2-1.1.x86_64

So far, so good. This time the update appears to have been more successful… none of the problems noted above.

swerdna · April 18, 2010, 5:02am

That’s a good result – another satisfied Suser I hope

caprus · April 18, 2010, 1:40pm

Very satisfied with the resolution, Thanks again!

(However, I must say that I’m rather disappointed that the buggy update got published in the first place.)

swerdna · April 18, 2010, 1:58pm

Yes, it’s caused quite a lot of bother, and the bug is so very pronounced that the update maybe was tested only superficially.