Comment 3 for bug 672013

First update was pure cups and was the only change on the system since posting
this entry on November 5.

http://logikalblog.com/2010/11/05/end-the-recession-in-18-months-without-
spending-taxpayer-money/

After posting it I applied the cups updates which had been sitting there in
the notification thing for several days. I wrote a few other things, then
attempted to upload a new post. Upload failed. I re-installed the plug-in
just in case, still failed. I saw there were many more cups updates suddenly
released and assumed this was the typical break-it:fix-it:break-it:fix-it patch
history I've become used to, so applied this round of updates. Still broken.

Since I haven't done what most do to get around problems, forced the
installation of Sun Java, I assume it is some kind of tweak the visciously
fragile Java package we are now forced to endure.

My internet connection for this machine is an actual hard wire, not wireless
or USB, but my keyboard and mouse are connected via USB KVM switch which long
ago had a "patch" to networking for usb based network devices which
completely waxed its ability to switch between systems.

What perplexes me is that the plug-in can connect when a new blog is added AND
pull down the list of blog entry categories the site has to work with. The
update simply waxed the ability to post to a WordPress (don't know about other
types) based blogs. No, it's not the hose site, They haven't updated
anything in the blog side of business in roughly two years.

Is there a log somewhere which shows which updates were applied on which day?
If there is, and a simply command line method of backing each one out one at a
time, I can spend today backing out the updates until my new blog entry posts.
Then we will know which entry was the primary culprit, though it may have had
assistance from another patch.

On Sunday, November 07, 2010 06:22:37 am you wrote:
> How do you come to the conclusion that CUPS is the culprit here?
>
> Did you up[date only CUPS and nothing else? Usually there come many more
> packages with the system updates.
>
> The functionality which failed for you has nothing to do with printing.
> Did you see any evidence that CUPS is blocking it?
>
> Try the following:
>
> Run in a terminal window
>
> sudo stop cups
>
> This turns off CUPS. Can you post now?
>
> Now run
>
> sudo start cups
>
> Does posting stop working again?
>
> If you downgrade CUPS, are you able to post again?
>
> ** Changed in: cups (Ubuntu)
> Status: New => Incomplete

--
Roland Hughes, President
Logikal Solutions

http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net

No U.S. troops have ever lost their lives defending our ethanol reserves.