Bug 165963 - Weird krunner crash (can't even provide backtrace)
Summary: Weird krunner crash (can't even provide backtrace)
Status: RESOLVED WORKSFORME
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-07 20:01 UTC by Bernhard Friedreich
Modified: 2008-07-09 10:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot describing problem (219.45 KB, image/jpeg)
2008-07-07 20:02 UTC, Bernhard Friedreich
Details
krunnerrc (1.35 KB, application/octet-stream)
2008-07-07 20:03 UTC, Bernhard Friedreich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Friedreich 2008-07-07 20:01:50 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          g++ (SUSE Linux) 4.3.2 20080613 (prerelease) [gcc-4_3-branch revision 136744] 
OS:                Linux

Well... what did I do?

I enabled nepomuk and strigi, logged out, logged in, emmidiately after login I pressed alt+f2 and was greated with a nice crashhandler window and when I pressed on details a message popped up that the backtrace can't be created. (normally backtrace creating works wonderfully) (yes I have debugging symbols installed ^^)

I'll attach a screenshot and my krunner conf
Comment 1 Bernhard Friedreich 2008-07-07 20:02:20 UTC
Created attachment 25906 [details]
Screenshot describing problem
Comment 2 Bernhard Friedreich 2008-07-07 20:03:00 UTC
Created attachment 25907 [details]
krunnerrc
Comment 3 Aaron J. Seigo 2008-07-07 22:53:28 UTC
does this happen every time you press Alt-F2 now? (e.g. it reproducably crashes on showing)

this would be very odd, and point to some rather fundamental packaging problem perhaps, since the runners aren't even loaded until you start typing a search phrase into the text box.
Comment 4 Bernhard Friedreich 2008-07-08 08:52:42 UTC
nope.. this problem happened just once..
any idea what it could be related to?
Comment 5 Aaron J. Seigo 2008-07-08 12:03:28 UTC
no idea what it could be related to. and unless this can be repeated in some manner, there's no hope in identifying the cause of such a bug.
Comment 6 Sebastian Sauer 2008-07-09 05:58:51 UTC
Bernhard: also it may the case that the crash got already reported. But since without future details we are unlikely to address this report, would you like to close the report again? For sure you can reopen just any time if you are able to reproduce it somehow or if you are even able to catch a backtrace :) Thanks in advance.
Comment 7 Bernhard Friedreich 2008-07-09 10:09:32 UTC
Ok.. I'll close the bug and if I get any useful information or can reproduce the bug I'll reopen it.