|
Bugzilla – Full Text Bug Listing |
| Summary: | kded crash | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Forgotten User E4aj6OYf6m <forgotten_E4aj6OYf6m> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | VERIFIED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | gchristensen |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | kded crash report by kde crashmanager | ||
|
Description
Forgotten User E4aj6OYf6m
2005-10-29 01:12:59 UTC
*** Bug 887 has been marked as a duplicate of this bug. *** we still haven't found someone to reproduce it. It seems x86_64 specific and I blame krdc - but unreproducible ;( Created attachment 70330 [details]
kded crash report by kde crashmanager
Messages when starting kded in terminal window:
QLayout "unnamed" added to CatalogStatusItem "CatalogStatus", which alre ady has a layout
KWrited überwacht Gerät /dev/pts/0
*** glibc detected *** malloc(): memory corruption (fast): 0x00002aaab15ad49f ***
Last DCOP call before KDED crash was from application 'kcontrol'
to object 'kded', function 'loadedModules()'.
KCrash: Application 'kded' crashing...
QLayout "unnamed" added to CatalogStatusItem "CatalogStatus", which already has a layout
KWrited überwacht Gerät /dev/pts/0
*** glibc detected *** malloc(): memory corruption (fast): 0x00002aaab10b141f ***
QSocketNotifier: invalid socket 3 and type 'Read', disabling...
Last DCOP call before KDED crash was from application 'DCOPServer'
to object '', function 'applicationRemoved(QCString)'.
KCrash: Application 'kded' crashing...
kded: Fatal IO error: client killed
QLayout "unnamed" added to CatalogStatusItem "CatalogStatus", which already has a layout
KWrited überwacht Gerät /dev/pts/0
Stefan: Thats a totally different issue. We've fixed that. as a workaround, deinstall kat. without a way to reproduce it, I close the bug ;( |