Sorry, been crazy busy the past few days and hadn't had the time to
respond to this. Yes you can set it back to fixed.
I will also mention that Ubuntu's updates today fixed the issue, I was
able to double check after I rescinded follow symlinks back to NO. So no
extra bug report is needed by me,
Sorry I must have had some miscommunication here. I did apply those fix
patches for it, and it did indeed fix everything. I swapped it back to
follow symlinks = no and everything was just fine until last week
sometime. The problem was SIMILAR in nature after the updates from
sometime during the
Sorry to drag this up again, but I thought it fit as the symptoms were
similar and the fix was the same.
After another samba upgrade the other day - I'm not quite sure when it
initially hit, I hadn't upgraded my system in a week and a half or so - but
upon the upgrade when I went to load a
Okay, I removed the 'hold' flag on the needed packages and upgraded
(again) and can confirm that it DOES work now - at least at first
appearance. I'll be doing some stuff on the server tonight and will keep
you apprised of any problems.
In the duplicate bug I saw someone implied that the remedy
Damn I don't know how I missed that bug, I did a ton of searching.
Apologies. However, as I needed access to the server back immediately I
downgraded to v5. As soon as I get a free moment I'll remove the "hold
back" flag and upgrade again and try the workaround. I'll let you know
what the results
Okay, to give a little update on this, it is something in the "new"
version (2:4.4.5+dfsg-2ubuntu5.4 - I'll now refer to this as v5.4 for
simplicity's sake) - of what I don't exactly know. After about 12 more
full hours of searching and talking with another user who is having
similar issues I
Public bug reported:
I hadn't noticed it immediately after samba package upgrade, but in an
attempt to sign into my samba shares once I get the share mounted and I
try and open a folder it appears empty where it worked flawlessly
before. I hoped that reinstalling the samba package would give me a
Something else i was thinking about last night
Does anyone run compiz? it seemed to speed up the problem if Compiz was
running
And See if you guys can reproduce the error by opening xfce4-terminal
and the gnome one. Not xterm, but the other two.
There were times it seemed as though as soon as I
Did a dist-upgrade a few days ago, getting all these issues. Tried
browsing ubuntuforums and here to no avail. tried removing
xfce4-sessions, .config/, uh quite a few other things as well. Can't
wait to get it fixed as XFCE is the only GUI that lets me use 3 monitors
on my desktop in *nix
I finally gave up on it today and installed Kali-Linux. Although it uses
an old version of XFCE I don't like.
Considering going to BT since its built on Ubuntu to see if the version of XFCE
is better. If its not maybe I can get the Xubuntu version I'm wanting to use or
build it from source. If
10 matches
Mail list logo
