konqueror crashed on startup the first time after I upgraded it

Bug #324680 reported by Zooko Wilcox-O'Hearn
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

$ konqueror &
[3] 25287
MAIN yukyuk:~$ konqueror(25287) KToolInvocation::klauncher: klauncher not running... launching kdeinit
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
kdeinit4: preparing to launch /usr/bin/kded4
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
kbuildsycoca4(25298) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/ooo-startcenter.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(25298) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/ooo-startcenter.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(25298) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/speedcrunch.desktop" is not compliant with XDG standard (missing trailing semicolon).
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
kdeinit4: preparing to launch
konqueror(25287) KonqHistoryManager::loadHistory: The history version doesn't match, aborting loading
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
KCrash: Application 'konqueror' crashing...
sock_file=/home/zooko/.kde/socket-yukyuk/kdeinit4__2
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi

When I restarted it, it didn't crash and worked normally.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

So this happened only once after upgrade, correct? To properly handle this bug we'd need a backtrace of the crash. (https://wiki.ubuntu.com/Backtrace)
I don't know how likely is it that we'll be able to get one, though, if it was just a one-time occurrence... :(

Changed in kdebase:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.