|
Bugzilla – Full Text Bug Listing |
| Summary: | Knode crashed when deleting an account | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Joe Harmon <jharmon> |
| Component: | KDE | Assignee: | Lubos Lunak <llunak> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dmueller, kde-maintainers |
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
back trace
xsession-errors back trace of crash requested log from valgrind debugger valgrind log Another crash |
||
|
Description
Joe Harmon
2005-10-14 22:04:35 UTC
Created attachment 54184 [details]
back trace
it crashes somewhere inside alsa client libs. there must have been an error message on the console output that refers to an undefined symbol or similiar. can you retrieve that please? are you sure you have a clean installation? (In reply to comment #2) > it crashes somewhere inside alsa client libs. there must have been an error > message on the console output that refers to an undefined symbol or similiar. I don't see any message that refers to an undefined symbol. I looked in the syslog and on the CNTL ALT F10 window. > are you sure you have a clean installation? As far as I know. It is also important to note that this isn't always reproducable. In fact I have only run into this issue twice on SUSE 10.0. However, since I don't delete accounts very often (maybe a handful of times so far) then I think that is somewhat significant. *** Bug 130563 has been marked as a duplicate of this bug. *** X applications don't log to syslog, the output is usually in ~/.xsession-errors, please check there. And it indeed looks like some problem with the instalation. Created attachment 59945 [details] xsession-errors Since you mentioned that https://bugzilla.novell.com/show_bug.cgi?id=130563 was the same crash and this one, I reproduced the crash from bug #130563 because I can reproduce it every time. Here is the xsession-errors that you requested. I will also attach a new back trace from this latest crash. Created attachment 59946 [details]
back trace of crash
Please kill knotify and run it in valgrind[*] and attach the log. [*] valgrind --tool=memcheck --num-callers=20 knotify --nofork Created attachment 63677 [details]
requested log from valgrind debugger
There's no sign of a crash in the log. Yeah, I just attached what was there, but it appared to me that knotify never fully launched. I tried it several times, but it would always hang at that point. It's not hung, knotify is a notification daemon. Backtraces from both comment #1 and comment #7 are from knotify. You need to reproduce the crash. I got it to crash once but it didn't seem to put anything across the terminal. I still have it running though. But here is my log from yesterday in case you see anything different. Created attachment 64298 [details]
valgrind log
This log contains the crash, it's those "Invalid read of size 4" in do_lookup_x (in /lib/ld-2.3.5.so). Since those first two warnings about uninitialized data are harmless and the remaining ones are(?) probably too, let's say this is a glibc and not KDE problem. I can only see that KDE is messing up with signal handlers, this is serious. And using uninitializes buffers, too. I'm not sure if valgrind is right here, valgrind has a very long history of not working correct inside glibc routines. Neverless, glibc 2.3.5 is dead and I think KDE is broken here. I am sorry but I don't agree with this. A more serious problem occurs, that is a duplicate to this bug, where Kontact crashes when displaying groupwise appointments. How can we say we won't fix this issue? nonsense. first of all the SIGKILL crap comes from glibc and second, those interaction issues with glibc are long fixed. glibc never blocks SIGKILL itself. it does, anyway, the issue is the access of deleted memory after dlclose() here. glibc has no code for this, I looked at it. by 0x1C986E39: dlclose (in /lib/libdl-2.3.5.so) this is getting nowhere, perhaps Lubos has a minute of looking at it. You're using KDE3.5 from supplementary, right? Update to the latest akode packages and try if you can still reproduce the problem. (In reply to comment #24) > You're using KDE3.5 from supplementary, right? Update to the latest akode > packages and try if you can still reproduce the problem. No, I have been using the standard KDE packages that come with SUSE Linux 10.0, although I have been keeping up to date with Yast Online Update. It is also important to note that I am running the KDE applications (Kontact) though GNOME. But I will update to the latest and see if I can duplicate the issue. That could be crucial point - knotify isn't unloading itself that often when not being run under GNOME. Created attachment 66207 [details]
Another crash
It is happening on KDE 3.5 as well. I updated using the supplementary directory. I even used the latest packages out under the kirk.provo.novell.com/dist/full/full-10.0-i386 directlry stucture and it still crashes
What does rpm -qa | grep akode give you? (In reply to comment #28) > What does rpm -qa | grep akode give you? > libakode-2.0.0-5 I am no longer having any crashes with knode running in NLD 10 beta6. |