Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 311465 - Nepomuk crashes producing jre crash log
Summary: Nepomuk crashes producing jre crash log
Status: RESOLVED DUPLICATE of bug 260147
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Java (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-26 15:55 UTC by dan blum
Modified: 2010-03-28 16:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
error log (hs_err_pid3445.log,23.52 KB, text/plain)
2010-03-26 15:57 UTC, dan blum 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dan blum 2010-03-26 15:55:34 UTC 
An error log is created in the home folder. Not sure what is affected, the kde system I use freezes up very infrequently.


Why cannot I attach a file with bug, or am I missing something?

Reproducible: Always

Steps to Reproduce:
1.Run system
2.
3.
Comment 1 dan blum 2010-03-26 15:57:17 UTC 
Created attachment 225339 [details]
error log
Comment 2 Andreas K. Hüttel archtester gentoo-dev 2010-03-27 08:20:27 UTC 
What's your kde version? Does the error still happen with 4.3.5?
Comment 3 dan blum 2010-03-27 15:58:02 UTC 
4.4.1. The error log directs one to the Debian site, not Gentoo. Akonadi is not working either. Is that tied in?(In reply to comment #2)
> What's your kde version? Does the error still happen with 4.3.5?
>
Comment 4 dan blum 2010-03-27 23:51:22 UTC 
It may be 4.3.3 or 4.4.1 as indicated(In reply to comment #3)
> 4.4.1. The error log directs one to the Debian site, not Gentoo. Akonadi is not
> working either. Is that tied in?(In reply to comment #2)
> > What's your kde version? Does the error still happen with 4.3.5?
> > 
>
Comment 5 Andreas K. Hüttel archtester gentoo-dev 2010-03-28 16:19:33 UTC 

*** This bug has been marked as a duplicate of bug 260147 ***