Mailinglist Archive: opensuse (714 mails)

< Previous Next >
[opensuse] help forum no help getting printer to print
On 2011/10/06 17:34 (GMT) Jim Henderson composed:

On Wed, 05 Oct 2011 23:09:39 -0400, Felix Miata wrote:

After seeing "unable to open listen socket for address ::1:631 - Address
family not supported by protocol" in /var/log/cups/error_log, Google
told me goto
and to figure out why I can't
print with my Canon GDI, but instead of help I just see the incompetent
results of incompetent site styles:

That screenshot is now available at

Can someone please fix the openSUSE web sites to use browser defaults
instead of mousetype so that this kind of mess doesn't keep happening?

If you can give us steps to reproduce, we'll look at it. It's not
helpful to use charged words like "incompetent", BTW. Nobody has ever
reported seeing something like this (that I can recall), and we have
thousands of users who use the site without issues.

On 2011/10/06 22:13 (GMT) Jim Henderson composed:

Screenshot was yesterday on 12.1B1, but general behavior is longstanding
<>. Details to follow
when time permits, as so much has been lost trying to make print work in
order that other projects can escape logjam.

I don't have access to that bug, but just to be clear, I'm talking about
the display issue you saw in the forums, not the printing issue. Since

That's why I opened this thread in the opensuse-web mailing list as well, but no one has replied there as yet.

I'm staff on the forums, I can try to get that addressed if I can
reproduce the issue.

Those two bugs are web site bugs. If you have power to alter the site, then whoever has the power to give you access to those two bugs needs to do so. They contain the foundation of my complaint.

Incompetence was a word choice that applies to the web generally, not specifically to Competently designed web sites don't induce users to use heroic measures to compensate for stupid and rude site styles, such as those described in those two bugs and in which contains the entirety of the highly burdensome 155k+ of CSS saved to disk as web page complete with Gecko from shows what 408396-cups-deamon-not-accessable.html looks like on one of my systems without any rudeness countermeasures applied. The dominant text size is a small fraction of the UA's UI text size, which is a smaller size than the UA's default size, for a net result of painful to use, if not totally illegible.

My need to return to various pages on a recurring basis makes temporary defenses like minimum text size and zoom worse than sub-optimal. So, I use site specific user styles as a long term defense mechanism. The current version of user CSS applied specifically to the site consists of and, in conjunction with my generic user CSS at, and are necessary to have a chance to reproduce. Reproduction should not be necessary to correction, as no user defenses would be necessary at all if both those two bugs and the broader problem they describe were fixed and remained so across site facelifts.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata ***
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >