Bug 64935 - k-jofol interface crashes when noatun is closed
Summary: k-jofol interface crashes when noatun is closed
Status: RESOLVED WORKSFORME
Alias: None
Product: noatun
Classification: Unmaintained
Component: general (show other bugs)
Version: 2.2.1
Platform: Mandrake RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-25 19:08 UTC by Erich Vinson
Modified: 2003-10-21 20:05 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erich Vinson 2003-09-25 19:08:18 UTC
Version:           2.2.1 (using KDE 3.1.0)
Installed from:    Mandrake Linux Cooker i586 - Cooker
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
OS:          Linux (i686) release 2.4.21-0.13mdk

When the J-Jofol interface is loaded and the application is closed, noatun crashes. Not a big deal since I am closing it anyway I guess, but it is reproducible (at least on my Mandrake 9.1 system)

Backtrace:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 16025)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40f12677 in waitpid () from /lib/i686/libpthread.so.0
#0  0x40f12677 in waitpid () from /lib/i686/libpthread.so.0
#1  0x40639e7b in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#2  0x4107f3b8 in __libc_sigaction () from /lib/i686/libc.so.6
Comment 1 Stefan Gehn 2003-09-25 19:31:55 UTC
That backtrace contains no information about the crash, to find the cause of this 
problem the binary needs to be compiled with debug information. 
Comment 2 Eray Ozkural 2003-10-21 15:08:35 UTC
I can't even load k-jofol right now. Seems broken to some as of yet undetermined extent. ;)

Comment 3 Stefan Gehn 2003-10-21 20:05:55 UTC
No information, no bugfix, as easy as that.
I'm using kj
Comment 4 Erich Vinson 2003-10-21 20:14:13 UTC
Subject: Re:  k-jofol interface crashes when noatun is closed

Sorry, I am just an average end-user and thought I might try to help. I
included all the info I know how to get, I wouldn't know how to get an
accurate backtrace or anything. All I know is that default installation
on my Mandrake 9.1 box makes it crash when using kjofol. Maybe if I
could get a link to a HOWTO on how to get the info you need I can help
more. Otherwise you may as well close the bug report because I don't
know how to get the info you requested. Thanks! :-)

On Tue, 2003-10-21 at 12:05, Stefan Gehn wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>      
> http://bugs.kde.org/show_bug.cgi?id=64935     
> mETz81@web.de changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |WORKSFORME
> 
> 
> 
> ------- Additional Comments From mETz81@web.de  2003-10-21 20:05 -------
> No information, no bugfix, as easy as that.
> I'm using kj