Im using Arch Linux and have a problem with Konqueror crashing especially on sites using java (ebay and Arduino site). BUT if I start Konqueror from Konsole, Konqueror does not crash. What is the difference between starting Konqueror from the icon and starting Konqueror from command line? Thanks for your help.

Are other sites which use plugins (such as Flash) also affected by this issue, or is it just Java based sites?

bcooksley wrote:Are other sites which use plugins (such as Flash) also affected by this issue, or is it just Java based sites?

I have no problems with flash at all. I just really need to know the difference between what I asked in the op because it works fine every time from konsole.

The only difference I can think of in this case is that when launched from Konsole, Konqueror and the Java it embeds would have an active terminal to print messages. When it crashes, does the crash assistant launch, and if so, can you get a backtrace?

Only place I can find an error is .xsession-errors which is

konqueror: Fatal IO error: client killed

Hmm - that message isn't helpful unfortunately, it usually means that X has suddenly quit on Konqueror.
When Konqueror crashes, does it simply suddenly disappear or does the crash assistant launch?

bcooksley wrote:Hmm - that message isn't helpful unfortunately, it usually means that X has suddenly quit on Konqueror.
When Konqueror crashes, does it simply suddenly disappear or does the crash assistant launch?

It just disappears no crash assistant. Just *poof* I really like KDE though after close to 10 years as a Gnome guy. I could probably install firefox and have no issues but I really want this to work. Arch is very fast with updates and I'm always hoping that "this is the one" that will fix it but not yet.

I just figured out that this only happens after the laptop comes back from sleep. I rebooted visited all the sites that usually crash Konqueror and no crash. So in a way this will most likely be even harder to solve.

Ouch. Okay, can you run "kdebugdialog" and enable all areas? Then tail ~/.xsession-errors and launch Konqueror as you normally would and attempt to reproduce the crash.

Please then post the output given in Konsole here. Make sure to check any references to kio_http in the log - as they may leak sensitive details (such as the URL of the site you are visiting).

I just tried rekonq it crashed also. Here is the crash log. I installed Firefox and it does not crash and runs as expected.

[user@archlaptop ~]$ tail -30 .xsession-errors
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5000012
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5000012
plasma-desktop(322)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
QGridLayoutEngine::addItem: Cell (0, 1) already taken
plasma-desktop(322)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
akonadi_pop3_resource_0(440)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://com@pop.secureserver.net:995/index") data size = 0
akonadi_pop3_resource_0(440)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://com@pop.secureserver.net:995/uidl") data size = 0
akonadi_pop3_resource_0(440)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("pop3s://com@pop.secureserver.net:995/download/") data size = 0
akonadi_pop3_resource_0(440)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QGridLayoutEngine::addItem: Cell (0, 1) already taken
plasma-desktop(322)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application
KCrash: Application 'konqueror' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
drkonqi(5620) KCrashBackend::constructCrashedApplication: Using /proc to determine executable path
drkonqi(5620) KCrashBackend::constructCrashedApplication: Executable is: "/usr/bin/kdeinit4"
drkonqi(5620) KCrashBackend::constructCrashedApplication: Executable exists: true
drkonqi(5620): Unable to find an internal debugger that can work with the KCrash backend
drkonqi(5620) DrKonqi::init: Enabling drkonqi crash catching
drkonqi(5620)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::instance: instance(): ... initialised
drkonqi(5620)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::readConfig: readConfig(): local zone= "America/Phoenix"
drkonqi(5620)/kdecore (K*TimeZone*) KSystemTimeZonesPrivate::readZoneTab: readZoneTab( "/usr/share/zoneinfo/zone.tab" )
drkonqi(5620) KCrashBackend::stopAttachedProcess: Sending SIGSTOP to process
drkonqi(5620) KCrashBackend::continueAttachedProcess: Sending SIGCONT to process
drkonqi(5620) KCrashBackend::stopAttachedProcess: Sending SIGSTOP to process
drkonqi(5620) KCrashBackend::continueAttachedProcess: Sending SIGCONT to process
[user@archlaptop ~]$

Hmm, unfortunate - it seems any reason for the crash wasn't included - but it seems that the crash assistant (Dr Konqi) was able to catch that crash. Do you have a debugger installed on your system? It's output seems to indicate you might not.

No debugger installed. Unless one came with the kde-meta Arch package.

It is necessary to have a debugger such as gdb installed in order to generate the necessary Developer Information to debug this i'm afraid.
Please install one and try to reproduce the Konqueror crash.