Summary: | gnome-base/nautilus-2.32.2.1-r1 can't open a samba share (samba-3.6.0_rc3-r1) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/var/log/samba/log.smbd on grizzly
.xsession-errors_after_opening_gnometerminal /home/test_samba/.xsession-errors_after_trying_to_access_samba_share |
Description
Juergen Rose
2011-08-08 08:19:03 UTC
Created attachment 282533 [details]
/var/log/samba/log.smbd on grizzly
On grizzly I find during my try to acces the samba share with nautilus from impala in /var/log/samba/log.smbd the output in the attached file
Can you reproduce this on a new created user account? In that case please attach ~/.xsession-errors just after reproducing. Is this a regression over older samba versions? At first I masked samba > 3.5.9. Then I reemerged samba. Now I have again samba-3.5.9: root@grizzly:/root(20)# genlop -t samba | tail Thu Jun 30 04:45:20 2011 >>> net-fs/samba-3.5.9 merge time: 19 minutes and 31 seconds. Fri Aug 5 04:44:07 2011 >>> net-fs/samba-3.6.0_rc3-r1 merge time: 15 minutes and 29 seconds. Mon Aug 8 13:33:42 2011 >>> net-fs/samba-3.5.9 merge time: 19 minutes and 48 seconds. I tried to access from three different computer with nautilus as user rose the public share on grizzly. I will not asked for a password, bu I could not access the public share and I see the hourglass. Then I created a new user test_samba at "condor" with the new home directory test_samba. I added the groups audio, plugdev, pulse and pulse-access to user test_samba. I opened a gnome terminal and did 'cat .xsession-errors > .xsession-errors_after_opening_gnometerminal' Then I tried: Places Network GRIZZLY Windows Network (I click on GRIZZLY) public (I click on public) And I see the hourglass, I click "Back", and see again the normal mousepointer. I save .xsession-errors: cat .xsession-errors > .xsession-errors_after_trying_to_access_samba_share The additional lines in .xsession-errors_after_trying_to_access_samba_share are only multiple WARNINGSs that connection to volume-control-applet and to gnome-settings-daemon failed. The gnome-settings-daemon is running: root@condor:/etc/local.d(55)# ps -ef | grep gnome-sett | grep -v grep 1205 5653 1 0 15:42 ? 00:00:00 /usr/libexec/gnome-settings-daemon I hoped, that adding user test_samba to the udio, plugdev, pulse and pulse-access groups remove these volume-control-applet messages. But id did not. As the next step after finishing 'emerge sys-devel/gcc' I will reboot "grizzly", and see what happens. So it seems me that the issue is not a regression from samba-3.5.9 to samba-3.6.0_rc3-r1, but in generall it is a regression. But I can not say, when it was working last time. I trying to access this samba share only once in a month or less and I am not shure, if I accessed it one month ago as a samba share or simply via the filesystem. Created attachment 282567 [details]
.xsession-errors_after_opening_gnometerminal
Created attachment 282569 [details]
/home/test_samba/.xsession-errors_after_trying_to_access_samba_share
Browsing of samba shares works again. The only change, I see, is the downgrade of samba to samba-3.5.11 on the client side. (In reply to comment #6) > Browsing of samba shares works again. The only change, I see, is the downgrade > of samba to samba-3.5.11 on the client side. Looks like a regression caused by samba-3.6.x upgrade then, would be interesting to test with different 3.6.x RC releases to try to isolate the problematic version and know what changed in it There was also a minor upgrade of gnome-desktop to gnome-desktop-2.32.1-r1 in the last days. Perhaps this upgrade had also some influence of the samba browsing in nautilus. (In reply to comment #8) > There was also a minor upgrade of gnome-desktop to gnome-desktop-2.32.1-r1 in > the last days. Perhaps this upgrade had also some influence of the samba > browsing in nautilus. That minor upgrade has completely irrelevant changes. (In reply to comment #7) > (In reply to comment #6) > > Browsing of samba shares works again. The only change, I see, is the downgrade > > of samba to samba-3.5.11 on the client side. > > Looks like a regression caused by samba-3.6.x upgrade then, would be > interesting to test with different 3.6.x RC releases to try to isolate the > problematic version and know what changed in it Were you finally able to test that? (In reply to comment #10) > (In reply to comment #7) > > (In reply to comment #6) > > > Browsing of samba shares works again. The only change, I see, is the downgrade > > > of samba to samba-3.5.11 on the client side. > > > > Looks like a regression caused by samba-3.6.x upgrade then, would be > > interesting to test with different 3.6.x RC releases to try to isolate the > > problematic version and know what changed in it > > Were you finally able to test that? |