earth tech

Apparenlty the prooblem with Konqueror dying trying to load the Blogger.com Dashboard was temporary. This post is made using Konqueror 3.5.2 (KDE 3.5.2). It appears that the problem may have had somewhat to do with the Spell Checker problems I was trying to post about earlier (at the time the Konqueor crash occurred.

The problem then was that Konqueror as configured by default under Knoppix 5.0.1 was still using the German language dictionary for spell-checking, even though I had changed the KDE language preference to US English (US-EN) using the KDE Kicker panel [I.E. "toolbar"] widget.

I have since restarted KDE (due to some problems that seemed to have been caused by my moving the system /tmp directory to an internal drive partition while KDE was still running) and Konqueror starts up and runs and has not [yet] crashed on the Blogger Dashboard interface.

The earlier crash which killed Konqueror for the duration of that KDE session occurred after the problems with the spell checker manifested, and after I clicked the Save Now button to save the post. The Save Now button did not "depress" at that time, and no draft of the message was saved. Immediately after the save operation failed is when I clicked the Dashboard link, which is what caused Konqueror to crash.

Note that at this time, the spell checker does not seem to be working at all in Konqueror (the Auto Spell Check option is checked, and the Check Spelling context menu command does nothing), and that

1. There is no "typeahead" pattern matching in the tags field of the blogger.com Posting interface as there is with Firefox v2.x
2. The layout of the blogger.com Posting interface in Konqueror is munged - there is a large whitespace block below the text entry area, between the bottom edge of the HTML textarea element and the the bottom edge of the boarder which encloses the HTML element. (above the Post Options link, the Labels (sic) [tags] entry field, Publish Post and Save Now buttons, etc.

Labels: blogger, crash, kde, konqueror, linux, v3.5.2

posted by pd wilson   #   06:42

Another problem that has shown up recently with blogger.com recently is some strange behavior under Firefox v2.0.0.4 and v2.0.0.5 - specifically, the Posting interface, when certain buttons are clicked, does not behave as expected.

For instance, the "Link&qut; button [supposed to add an HTML anchor (A) element in the text box where the blog post is entered and/or edited:

When the link button is clicked, Firefox apparently initiates a "Drag and Drop" operation for the button image. The URL entry box pops up as expected, but the pointer cursor is changed to indicate that a drag/drop is in progress, and if the user clicks within the URL entry field on the popup, the URL of the button image [at blogger.com] is pasted into the URL entry field. If the user clicks outside the text entry field on the popup, the "drop" part of the drag/drop operation fails silently and text can be entered.

For some reason the drag operation does not provide the "NO" symbol cursor on screen areas which will not accept the dragged image.

This is almost certainly a Firefox issue, rather than Blogger issue, but it is possible that it is something funky w/ the Javascript Blogger uses. I have not examined the Javascript source or tried to replicate this error on other sites or with other browsers (although the same issue does exist with Iceweasel under Debian).

Labels: blogger, bug, firefox, iceweasel

posted by pd wilson   #   04:51

Well, the Dashboard page at blogger.com seems to have killed Konqueror web browser under KNOPPIX. Konqueror crashed first while I was trying to post about the spell-checker problems that exist in Konqueror under the KNOPPIX LiveCD distro - at that point I was logged in to blogger.com - then it crashed again when I re-ran Konqueror and tried to log in to the blogger.com dashboard. Both times it gave the DrKonqi crash-handler screen.

Now, after I created a persistent installation of Firefox 2.0.0.5 and ran it to make this post, I find (while trying to run Konqueror to get the version number to use in this post) that Konqueror won't run at all [from the toolbar button, at least - haven't tried any other approaches, yet]; it shows the bouncing "wait" cursor for about 15 or so seconds, then just dies silently.

This is Knoppix 5.0.x - I don't have the version number to-hand, but I may be able to post it later. I see that Knoppix 5.2 is released, so the problem may be solved by burning a new LiveCD. Note, however, that the version of K3B that shipped with this version of KNOPPIX does not work - or at least, it doesn't work on this computer, so the burning of a new CD is problematic, right now.

Labels: blogger, crash, knoppix, konqueror

posted by pd wilson   #   09:37

Konqueror is :

1. Hanging while waiting for blogger.com to "Publish" a blog post.
2. Crashing; Konqueror will crash if - while the "publish" operation is in its infinite refresh loop, loading and reloading the "Please wait while your page is published" message page - the user
   1. opens another Konqueror window
   2. goes to view the blog in the new window [note that the post which initiated the publish operation has been posted - the post has uploaded and the blog has been updated, despite the braindead infinite loop the first window of Kongqueror is stuck in]
   3. goes back to the first window [where the ininfinite refresh loop is going on]
   4. clicks on the Blogger Dashboard link there, in the first window, while the infinite refresh loop is going on

Other info from the Crash Handler:

• Konqueror [crashed and] threw SIGILL.
• "The application was asked to save its documents"

Default browser indentification string for this version of Konqueror [note that I have broken the line below at the backslash]:

Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.17; X11; i686; en_US)\
 KHTML/3.5.2 (like Gecko) (Debian package 4:3.5.2-2+b1)

Here is the backtrace data from the crash handler:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231935808 (LWP 4267)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x08f95edc in ?? ()
#6  0xb62d57ae in DOM::checkChild () from /usr/lib/libkhtml.so.4
#7  0xb629e96c in DOM::XMLAttributeReader::~XMLAttributeReader ()
   from /usr/lib/libkhtml.so.4
#8  0xb6268f9e in KHTMLPart::saveState () from /usr/lib/libkhtml.so.4
#9  0xb62289fe in KHTMLPartBrowserExtension::saveState ()
   from /usr/lib/libkhtml.so.4
#10 0xb6875b5f in KonqView::updateHistoryEntry ()
   from /usr/lib/libkdeinit_konqueror.so
#11 0xb6893a11 in KonqView::slotCompleted ()
   from /usr/lib/libkdeinit_konqueror.so
#12 0xb6893c23 in KonqView::slotCompleted ()
   from /usr/lib/libkdeinit_konqueror.so
#13 0xb689987d in KonqView::qt_invoke () from /usr/lib/libkdeinit_konqueror.so
#14 0xb72b8678 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb72b8fdc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb7f85e0a in KParts::ReadOnlyPart::completed ()
   from /usr/lib/libkparts.so.2
#17 0xb62581c0 in KHTMLView::timerEvent () from /usr/lib/libkhtml.so.4
#18 0xb72b5786 in QObject::event () from /usr/lib/libqt-mt.so.3
#19 0xb72f2b9a in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb724e87a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb724f5f5 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb792502e in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb71e0001 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#24 0xb7240305 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#25 0xb71f3d2a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb7267255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb726717a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb724d38d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0xb68be17c in kdemain () from /usr/lib/libkdeinit_konqueror.so
#30 0xb7fb1524 in kdeinitmain () from /usr/lib/kde3/konqueror.so
#31 0x0804e1d6 in ?? ()
#32 0x00000004 in ?? ()
#33 0x080cff68 in ?? ()
#34 0x00000001 in ?? ()
#35 0x00000000 in ?? ()

Labels: blogger, crash, kde, knoppix, konqueror, linux, v3.5.2

posted by pd wilson   #   09:47

Here are [links to] templates used for the earth blogs pages. These templates are HTML encoded, so they should be copied and pasted rather than directly downloaded, since the HTML elements and blogger tags will show up as HTML entities in the HTML source code.

These templates is specific to blogger.com and probably won't work with other blogging services.

These templates are moving towards being XHTML and CSS standards compliant, but probably aren't there, yet. That is: the goal here is to write the template in such a way that the resulting blog pages will validate using the W3C validation services.

The blogger template for the ain't it strange blog: aint_it_strange.html

The template for blog null: blog_null-v3.html

The template for this [earth tech] blog is derived from the template for earth food: earth_tech-blog-template.html. Additionally, the stylesheet for earth tech is available: earth_tech.css

Labels: blog, blogger, css, template

posted by pd wilson   #   04:20

Checking out the JavaScript drawing program example called Doodle at the webreference.com section on JavaScript Programming, I found this bit of CSS that does syntax highlighting: SyntaxHighlighter.css [http://www.webreference.com/css/SyntaxHighlighter.css]

See also the Doodle Javascript programming example provided by WebReference for use of these style classes. Nice bit of work.

Here is a trivial example of the HTML to use of some of SyntaxHighlighter.css classes [from the example article, page 3]:

<div style="width: 700px;">
<textarea name="code" class="javascript" cols="60" rows="10"> 

<P class=code>&lt;script src="core.js" 
type=text/javascript&gt;&lt;/script&gt;<BR>&lt;script src="graphics.js" 
type=text/javascript&gt;&lt;/script&gt;<BR>&lt;script src="canvas.js" 
type=text/javascript&gt;&lt;/script&gt;<BR>&lt;script 
type=text/javascript&gt;<BR>var canvas = null;<BR>function initCanvas() 
{<BR>&nbsp;&nbsp;&nbsp;canvas = new 
Canvas($('theCanvas'));<BR>}<BR>window.setTimeout(initCanvas, 
10);<BR>&lt;/script&gt;<BR>&nbsp;&nbsp;&nbsp;&lt;div id="theFrame" 
class="CanvasFrame"&gt;&lt;/div&gt;<BR>&nbsp;&nbsp;&nbsp;&lt;div id="theCanvas" 
class="Canvas"&gt;&lt;/div&gt;<BR>&lt;/div&gt;</P>

</textarea>
</div>

Other examples occur in the article.

This CSS seems to make a nice complement to the PHP syntax highlighter blogged about elsewhere.

Labels: blog, blogger, code, css, html, javascript, php, source, syntax highlighter, web

posted by pd wilson   #   05:10