Gdk-WARNING **: XID collision, trouble ahead
The Internet is awash with reports of this. I can reproduce it, start seamonkey from a terminal window, go to here:
...or any advertised property on domain.com.au, then click the scrollbar to scroll down. SeaMonkey spits out this error message.
I am running Wary, which has GTK 2.20.1 -- so I thought the more recent version than earlier puppies is the problem. Quirky for example has GTK 2.16.6. But no...
I was using SeaMonkey 2.0.13. I tried SM 2.0.11, same problem. Then I tried SM 1.1.18 -- problem gone!
An observation: both SM and Firefox are going downhill. SM 1.1.x is fast and low resources, 2.0 has rendering/scrolling slowness and uses more resources (plus the above bug), 2.1beta is a real resource hog.
I don't care about the critics who say that I should go for the latest SM, I think that I will put 1.1.18 or 1.1.19 into the next Wary, along with adblock and a couple of other plugins.
Comments:Posted on 26 Apr 2011, 20:29 by xman
Opera, rising Star
SM is stranger for me but I think you have right feeling about FF. Combination FF 3.6.13 & FP 10.2rxxx behaves, but combination FF 4.0 & FP 10.2r153 is totally horrible, and combination FF 4.0 & FP 10.2r159 is just horrible. Can even Adobe do something to elevate crashy FF 4.0 on her feet?
Browser industry isn't totally in deep depression. There are better news to tell from Norway. Opera is going better. Opera 11.10.2092 is remarkably stable, and debian package installs to Quirky or Wary without any missing libraries.
Posted on 26 Apr 2011, 22:43 by John Biles
It's what works that counts
Hello Barry K, No point having the latest and greatest Web Browser if it doesn't give a user an enjoyable experience. Go with the older working version.
Posted on 26 Apr 2011, 23:18 by Enhas
I also like Opera
I've tried the Opera 11.10 .deb package in Wary Puppy, and it installed and worked just fine (except for some reason, a few of the icons were corrupted and didn't display correctly, but that wasn't that bad).
Opera also has Opera Turbo which works pretty well on most sites for slow connections (at the cost of image quality). Dial-up on my old computer only works at about half-speed in Puppy compared to Windows, so this would help regain some of the loss as well.
Posted on 26 Apr 2011, 23:26 by ttuuxxx
Hi Barry 2.14X has Wary's GlibC and I compiled the same Gcc as in Wary and a few others, Its around 80% Binary compatible with Wary, I still have to add a few minor updates to make it 100%. Anyways 2.14X comes with the latest Firefox 4.0 downloaded from mozilla and it autoupdates. It runs perfect, no jumpy scrolling, pages load quick etc. The only other puppy to run Firefox almost as smooth is Dpup.
Seamonkey 2.0 is slow on Wary I find also. If you are going to compile Seamonkey 1 could you maybe pm me a link to it and If you like I could give it a make over, People really dislike the look and feel of Seamonkey 1, I can retheme the original theme like I've done in the past and make it look a lot nicer without adding much to package if anything.
Posted on 26 Apr 2011, 23:28 by DaveS
Oprera.. Maybe not
Opera provides a good browsing experience (posting from it now actually), but it cannot print properly. This means it is only half useful. SM 1* is ok.
Posted on 26 Apr 2011, 23:51 by gjuhasz
Based on http://www.seamonkey-project.org/news, "SeaMonkey 1.x series no longer receives security updates, due to resource constraints, the SeaMonkey team strongly urges users of that series to upgrade".
I am afraid that the lack of HTML5 support will urge users to drop Seamonkey 1.x
I visited the link Barry mentions without any problem (VirtualBox, Wary 5.1.1, SM 2.0.11, Flash 10.2.152.27
Posted on 27 Apr 2011, 5:44 by joec.
I tested the web site with 3 old puppies that are on my computer.
puppy 4.1.2 & Quirky 002 using seamonky 2.0.1 no problem,no error message.
Wary 1.0.4 using seamonky 2.0.11 no error message but scrolling was very slow but that i believe is because wary is much slower on my old computer than the other 2.
Maybe they fixed something on the web site?
I had to upgrade to seamonky 2.0.1 on 412 and Quirky because my isp (verizon ) "upgraded" their webmail site and seamonky 1 will not work, also some department store web sites would no longer
work with seamonky 1
Posted on 27 Apr 2011, 6:55 by Jemimah
If you haven't played with Midori lately, you should. The latest development versions of webkit-gtk are pretty stable with a simple patch and work perfectly with like 98% of websites.
(I don't consider webkitgtk stable enough for my primary browser yet, it segfaults maybe once or twice a week, but hopefully all that will be sorted out soon).
Static Midori is between 2 and 3 MB in size leaving plenty of space for whatever browser the user wants - plus it runs very nearly as fast as Dillo.
Webkit can use gsteamer for html5 video so it's possible to build the whole puplet with only gstreamer-based multimedia (Puppeee and Fluppy have been like this for a while). The best light gstreamer media player is Parole - not perfect, but it's passable. Other small gstreamer projects of interest are Eina, Xnoise, Gnac, and Thoggen.
This is absolutely the way to go if you're looking for a fully functional system in as small of footprint as possible.
Posted on 27 Apr 2011, 7:37 by KJ
I agree with Jemimah. Latest Midori is greatly improved and is worth consideration. Parole works well for me also.
Posted on 27 Apr 2011, 7:42 by ozsouth
sm 2 errors
Folks, all browsers will show the site, but the terminal shows the XID error. (I tested SM 2.0.9 & 2.0.3 - error shows in terminal). I'm finding an increasing number of sites needing the IE8 user agent setting. Ffox 3.6x don't have that problem. I've tried Midori - mostly pretty good, & flash works. I always struggled with Opera. SM 1.1.18 works, but what to do about HTML5 / Security / IPV6 etc?
Posted on 27 Apr 2011, 8:12 by session
Can't reproduce error
Wary's retro Xorg runs faster on my kit, however in SM herky-jerky sites like these often scroll better under newer Xorg. I have no error message for this site under any circumstance in Wary.
Posted on 27 Apr 2011, 8:38 by session
CAN reproduce after hosts edit
I had no error message because I was using Scottman's Pup-Advert-Blocker. It seems the error is generated from some ad...
Posted on 27 Apr 2011, 8:53 by BarryK
Re HTML5, etc
Yeah, I agree that using SM 1.1.x is probably not a suitable long-term solution. Though, I am wondering if there could be an addon hack to pickup and display HTML5 video content.
I feel constrained to stay with SM as it is a suite, a lot of people including me use the WYSIWYG web page editor.
With Midori, if you include gnutls with https (SSL) support, that bulks it out considerably. Plus of course it is not a suite.
Regarding security, that is a very debatable issue. There may be security holes that are very specific to SM 1.1.x, but if no one else is using 1.1.x then predaters are much less likely to be targeting us (is that logic reasonable?). Plus, just what are these vulnerabilities? -- we would need to know what they are -- for example if one of them enables alteration of the Windows registry, then we couldn't care less.
Note, I am thinking of including 01micko's PET to optionally run SM as a non-root user -- that's next on my to-do list.
Posted on 27 Apr 2011, 8:03 by BarryK
With the user agent switcher addon, SM 1.1.x can pretend it is IE8, so many sites, for example a bank that Sage uses, will be happy.
Posted on 27 Apr 2011, 8:41 by ozsouth
Appears to me that SM 1.1.9 's main issues are with older plugins, etc than we use, so HTML5 is the main issue (but not such a big one yet). See:
My 'geri' users also prefer Seamonkey to other combos - it's just easier.
Posted on 27 Apr 2011, 10:27 by ozsouth
no script & SM 118
Posted on 27 Apr 2011, 22:46 by f00-
for nicer sm skins, I like the ones at http://vectorlinux.osuosl.org/incognu/
three more add-ons of note
(think these were from www.seamonkey.be)
.. much more and it starts that FF-bloat cycle
Posted on 29 Apr 2011, 4:48 by GCMartin
Seamonkey vs XID collision ...
For as long as I’ve been a forum follower-member, there has been consistent concerns about Seamonkey that I find contradictory.
Yes, I am a user of SEamonkey, but I am NOT a fan. I have and continure to use it because of all the features it affords me and the support community that exist. It is system complete and secure. To me, its the perfect browser package.
In the last week, several members in the forum and here has posted that Adblock seemingly is addressing issue that have give unwarrented behavior. Seems to be working, as, the one problem I had is not annoying me anymore.
Here’s the 2 discussions currently of all things WARY:
Memory use. When I joined the forum years ago, there was a lot of focus on issues. Many of us has low-RAM PCs, I haven’t seen a handful of memory use complaints in the last 6 months. What happened? ..... upgrades! Where the Puppy was confined to his cage, he now has a whole room to run around in. And, many of us now have “Stadiums” size PCs for 1000s of Puppies to run in. SeaMonkey isn’t a hog that its played out to be.
Slowness: Frankly, this is an objective discussion. Yes, Google Chrome is fastest...and I would expect it to be! But Seamonkey is fast too, so are all the other browsers....and each one delivers it own set of features....but none/NONE are full featured.
I think whatever SeaMonkey is selected should be consistent with WARY’s future direction....whatever that might be. In fact, I often wondered if the Puppy community would should be suited with 2 browsers: Fully featured SM and something called “Fast”. Thus allowing the community to choose whatever browser they consider to be fast to the Menu.
I hope I stayed on the topic of a full featured browser & "XID collision ..."
Hope this helps