Konqueror crashing

  • Thread starter Thread starter Deleted member 9563
  • Start date Start date
D

Deleted member 9563

Guest
Konquerer crashes. Sorry, I don't use this computer myself so I didn't see the exact quote but the message is something like
Code:
XID collision, trouble ahead
This time it happened after saving a .jpg and then opening it again. The crashing is severe, the screen goes black and the machine locks hard. This is the second installation on which this is happening. It is also a fresh install so I am extremely worried about the implications. How can I investigate, and hopefully fix this?

Edit: Doing some more searching I see this error happens in Linux with high CPU load. I don't think this is happening here. However, in case it matters, the machine is:
- Intel DH55TC board
- Intel Pentium Dual Core G6950 2.8GHz processor
- 8 GB DDR3 memory
- Radeon HD 4350 512MB Graphics
 
I see this has been moved to KDE. That gives me a hint as to where the problem may lie. I am not running a KDE desktop environment. Should I be?

The desktop environment is Fluxbox and there is the kdebase3 port installed. From what I understand installing kdebase is the only way to get Konqueror and some other KDE programs to run, but I am not aware of anything else that should be installed for this purpose.
 
Well, you didn't mention your WM, but I'll usually move K-related issues to the K-related forum ;)
 
It's all good. :) It does make sense that it would be KDE related regardless of the WM.

That said, I solved the problem. Or should I say, "it went away" after I did a reinstall of textproc/p5-XML-Parser.

I came to that after I checked for upgrades and found a couple which needed it. The upgrade didn't fix anything, but did result in discovering the following line:


Code:
Stale dependency: evince-2.32.0_2 --> nautilus-2.32.1 -- manually run 'pkgdb
-F' to fix, or specify -O to force.


Leading to:
Code:
# pkgdb -F
-snip-
checking for XML::Parser... configure: error: XML::Parser perl module is
required for intltool
===>  Script "configure" failed unexpectedly.

A search led to a thread here which gave the solution which was to deinstall and reinstall textproc/p5-XML-Parser. After that Konqueror worked properly.
 
Konqueror has been good all day and I thought it was fixed. It just now crashed. It crashes fluxbox and puts the user back to a terminal prompt. At that point, typing startx results in a black screen and the computer locked up with no access to other terminals. I installed Konqueror by just making the kdebase3 port. Is there another way? If anyone has any idea of how to install this program, or can point me to a how-to, I would be grateful.

All ports are up-to-date. All ports were installed from the ports collection (which is also up-to-date) and not from packages. I am only using portupgrade and not mixing it with portmaster. I have done very little other than follow the handbook. No experimenting. No wild commands. Nothing that would seem risky. I accept all defaults. What am I missing, other than more experience and expertise?
 
I installed KDE from the port hoping that it would add something which perhaps was missing from kdebase. It just completed with no errors.

Although I was not specifically interested in KDE as a desktop environment I couldn't resist starting it nevertheless. Unfortunately it fails. I guess that's how it goes. It's now 5am and I've wasted way too much time with this. I honestly don't think there is any hope for me being able to install a FreeBSD desktop system. Although I am not especially talented nor a professional, I thought that over 25 years of playing with computers would have prepared me for FreeBSD. I was wrong. I give up.
 
The "xorg dies with a black screen" sounds more like a video card driver or general xorg problem. And there's always PC-BSD, which would at least let you see if the problem was in your hardware or not.
 
wblock said:
The "xorg dies with a black screen" sounds more like a video card driver or general xorg problem. And there's always PC-BSD, which would at least let you see if the problem was in your hardware or not.

I does sound like a video card problem. However, since the above disappointment with KDE I found that it will actually run without error if started with exec. So, everything in KDE appears to work as before, and there are a number of extra KDE things too. This computer is actually my wife's so I have to go with her choices. She prefers fluxbox, but nevertheless has been testing KDE all day and using different browsers, viewing photos, pdf, and djview files as well as setting up a spreadsheet. Videos play fine too. One would think that by now an xorg or video card problem would have shown up. So far it is only Konqueror which crashes. Just like with fluxbox, so there's no advantage to KDE in that regard. I've been doing a lot of searching and it certainly is odd that there is not a lot of similar experience.

Perhaps it has to do with some of the other little problems which haven't been sorted out yet. For example, there are no drives visible in Konqueror. The /usr/ports/CHANGES file says to remove the cdrom entry from the /etc/fstab file. I'm still confused about that, since that would imply that KDE would be taking care of it, but it isn't.

I'm going to try a couple of live Linux CDs to check the hardware, but I'm reluctant to drop all the work and learning I've gone through with FreeBSD so far. Regarding PC-BSD, I'm aware of it, but was really trying to avoid a pre-packaged environment. Also, we're old folks here and don't really enjoy the whole KDE (especially 4) "computer fashion" thing which is probably better suited for younger folk. PC-BSD does look like it has a lot of merit so I won't reject it out of hand, but will wait to see if I can't get this to work first. It's a trial though. :) Anyway, we have a house full of computers and I plan to migrate them to BSD over time.
 
Back
Top