[Bug 251469] Re: samba nightmare

2008-11-20 Thread codeslinger
I am disappointed by the lack of response to this bug. But I am happy to report that after several months of automatic updates, I happened to notice that samba had finally and mysteriously started to work... with no changes on my part. So somebody somewhere fixed something. And for that I am

[Bug 251469] Re: samba nightmare

2008-07-24 Thread codeslinger
** Attachment added: currently installed synaptic packages -- broken system http://launchpadlibrarian.net/16279541/synaptic_pkgs_final_total_disaster.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/16279542/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt

[Bug 251469] Re: samba nightmare

2008-07-24 Thread codeslinger
attached is the synaptic package list after installing the additional packages that broke the printer config system. ** Attachment added: synaptic package - broken printing http://launchpadlibrarian.net/16279605/printer-krap-very-broken.txt -- samba nightmare

[Bug 251469] Re: samba nightmare

2008-07-24 Thread codeslinger
for comparison, attached is my synaptic config when everything still basically worked, this was after a successful install (by hand) of vmware. of course at this point, file and printer sharing is *NOT* working... and I have not yet attempted to install samba in order to get it to work. **

[Bug 251469] Re: samba nightmare

2008-07-24 Thread codeslinger
by the way, I am a computer consultant / sysadmin for several different companies. I would like nothing better than to convert those companies to using ubuntu and to avoid Vista altogether. My samba nightmare is that in one of those companies, their main computer died and I foolishly decided to

[Bug 251469] Re: samba nightmare

2008-07-24 Thread mcas
Thank you for reporting this bug. Can you please describe how you reinstall samba and cups? Have you deleted some files manually? ** Changed in: samba (Ubuntu) Status: New = Incomplete -- samba nightmare https://bugs.launchpad.net/bugs/251469 You received this bug notification because