Bug 39364 - Crash trying to connect to aRtsd
Summary: Crash trying to connect to aRtsd
Status: RESOLVED FIXED
Alias: None
Product: arts
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports All
: NOR crash
Target Milestone: ---
Assignee: Stefan Westerfeld
URL:
Keywords:
: 40759 43806 44259 51169 52607 52613 56994 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-03-14 08:18 UTC by michael
Modified: 2008-01-22 03:49 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2002-03-14 08:04:01 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           knotify
Version:           KDE 2.2.2 
Severity:          normal
Installed from:    FreeBSD Ports
Compiler:          Not Specified
OS:                FreeBSD
OS/Compiler notes: Not Specified

I have a home network consisting of an X server and an X terminal.  I have the esound sound daemon running on each to provide remote sound to machines in a similar manner to remote X.

I switched to KDE as my default desktop environment last week and all was working well except I hadn't configured KDE to use artsd or esd so I was living without sound in KDE.

I decided I would start configuring sound for the network and enabled the "network transparency" option (and the related "X11 security" option) in my user profile.

Since doing this it is most common for me to get a KNotify crash dialog box (KNotify crashed and caused a SIGABRT) when logging into KDE (I also have the "start artsd soundserver on KDE startup" option enabled) and it seems that this happens whenever KDE is trying to use sound.

I don't think arts is currently working as I still have esd running and I doubt that they can both use the sound (dsp) at the same time.  Nonetheless I wouldn't expect KNotify to crash in such situations.

Since it seems I can't attach files at this point I'll paste the crash backtrace... (the no debugging symbols found message is repeated about 20 times in the original)
-----
(no debugging symbols found)...
0x28d55cb0 in wait4 () from /usr/lib/libc.so.4
#0  0x28d55cb0 in wait4 () from /usr/lib/libc.so.4
#1  0x28d46e47 in waitpid () from /usr/lib/libc.so.4
#2  0x28602405 in KCrash::defaultCrashHandler ()
   from /usr/local/lib/libkdecore.so.4
#3  0xbfbfffac in ?? ()
#4  0x286a22a0 in FAMDebugLevel () from /usr/local/lib/libfam.so.0
#5  0x286a22bd in FAMDebugLevel () from /usr/local/lib/libfam.so.0
#6  0x28a5277f in __pure_virtual () from /usr/X11R6/lib/libqt2.so.4
#7  0x28fa9df2 in Arts::Dispatcher::connectUrl ()
   from /usr/local/lib/libmcop.so.0
#8  0x28fa9bc2 in Arts::Dispatcher::connectObjectRemote ()
   from /usr/local/lib/libmcop.so.0
#9  0x28eaedea in Arts::SoundServerV2_base::_fromReference ()
   from /usr/local/lib/libsoundserver_idl.so.0
#10 0x28eaebe6 in Arts::SoundServerV2_base::_fromString ()
   from /usr/local/lib/libsoundserver_idl.so.0

#11 0x28e90b95 in KNotify::connectSoundServer () from /usr/local/lib/knotify.so

#12 0x28e8ea04 in KNotify::notifyBySound () from /usr/local/lib/knotify.so
#13 0x28e8e7e3 in KNotify::notify () from /usr/local/lib/knotify.so
#14 0x28e91791 in KNotify::process () from /usr/local/lib/knotify.so
#15 0x28084abd in DCOPClient::receive () from /usr/local/lib/libDCOP.so.4
#16 0x28077e20 in DCOPProcessInternal () from /usr/local/lib/libDCOP.so.4
#17 0x28077963 in DCOPProcessMessage () from /usr/local/lib/libDCOP.so.4
#18 0x2808f1ac in KDE_IceProcessMessages () from /usr/local/lib/libDCOP.so.4
#19 0x2808566e in DCOPClient::processSocketData ()
   from /usr/local/lib/libDCOP.so.4
#20 0x2885bfb4 in QObject::activate_signal () from /usr/X11R6/lib/libqt2.so.4

#21 0x288b0b00 in QSocketNotifier::activated () from /usr/X11R6/lib/libqt2.so.4

#22 0x28890cc4 in QSocketNotifier::event () from /usr/X11R6/lib/libqt2.so.4
#23 0x2880bffa in QApplication::notify () from /usr/X11R6/lib/libqt2.so.4
#24 0x28567953 in KApplication::notify () from /usr/local/lib/libkdecore.so.4
#25 0x287da8c1 in qt_set_socket_handler () from /usr/X11R6/lib/libqt2.so.4
#26 0x287db023 in QApplication::processNextEvent ()
   from /usr/X11R6/lib/libqt2.so.4
#27 0x2880ddb7 in QApplication::enter_loop () from /usr/X11R6/lib/libqt2.so.4
#28 0x287da93b in QApplication::exec () from /usr/X11R6/lib/libqt2.so.4
#29 0x28e8b62b in main () from /usr/local/lib/knotify.so
#30 0x804caba in QCollection::newItem ()
#31 0x804eb3e in QCollection::newItem ()
#32 0x804adf9 in QCollection::newItem ()
-----
Since I notice that FAM is mentioned in the debug output I'l mention that I don't think it's correctly configured on my box at the moment.

I guess this could easily be a bug in artsd KNotify FAM or some other part of KDE.


(Submitted via bugs.kde.org)
Comment 1 Stephan Kulow 2002-09-20 18:19:47 UTC
*** Bug 44259 has been marked as a duplicate of this bug. ***
Comment 2 ddoerflinger 2003-03-06 14:34:47 UTC
Can you reproduce this using an upgraded Port?
What Version of FreeBSD did/do you use?

Regards,

Dirk Doerflinger
Comment 3 Arnold Krille 2003-03-10 15:19:24 UTC
Should be resolved in CVS since esd support is now there... 
 
Perhaps try CVS-HEAD of aRts? 
 
Arnold 
Comment 4 Stephan Kulow 2003-04-08 13:38:14 UTC
*** Bug 56994 has been marked as a duplicate of this bug. ***
Comment 5 George Staikos 2003-06-19 04:50:38 UTC
*** Bug 52613 has been marked as a duplicate of this bug. ***
Comment 6 George Staikos 2003-06-19 04:51:29 UTC
*** Bug 52607 has been marked as a duplicate of this bug. ***
Comment 7 George Staikos 2003-06-19 04:52:54 UTC
*** Bug 51169 has been marked as a duplicate of this bug. ***
Comment 8 George Staikos 2003-06-19 04:54:05 UTC
*** Bug 43806 has been marked as a duplicate of this bug. ***
Comment 9 George Staikos 2003-06-19 04:54:30 UTC
*** Bug 40759 has been marked as a duplicate of this bug. ***
Comment 10 Stefan Gehn 2004-04-29 09:51:03 UTC
Can this still be reproduced by somebody? Otherwise I'd be tempted to close such an old bugreport with so many possible problematic parts (fam, esd, network transparency which I haven't tried myself).
Comment 11 Rick Stevens 2004-05-20 07:13:17 UTC
Still happens with a fresh install of Fedora Core 2 on an Athlon 64.  Can I give you any more data to help sort it out?
Comment 12 deivis 2004-07-02 20:41:03 UTC
aRtsd crashes on Linux. KDE version 3.2.3. Kernel 2.4.27-pre2 on i586
Running MandrakeLinux development version. KDE version 3.2.3. I have C-Media sound card.

Crash report:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 1130)]
0x40663b78 in waitpid () from /lib/libpthread.so.0
#0  0x40663b78 in waitpid () from /lib/libpthread.so.0
#1  0x00000400 in ?? ()
#2  0x0805b955 in Arts::CrashHandler::defaultCrashHandler (sig=-512)
    at crashhandler.cc:215
#3  0x40662902 in __pthread_sighandler () from /lib/libpthread.so.0
#4  0x407e13c8 in killpg () from /lib/libc.so.6
#5  0x4016cdcf in Arts::AudioIOALSA::open (this=0xbfffed40)
    at audioioalsa9.cc:185
#6  0x40165509 in Arts::AudioSubSystem::open (this=0x80802f0)
    at audiosubsys.cc:361
#7  0x401656c2 in Arts::AudioSubSystem::check (this=0x80802f0)
    at audiosubsys.cc:341
#8  0x0805c8dd in main (argc=-1073745504, argv=0x0) at artsd.cc:295
Comment 13 Rijk van Wel 2004-07-30 17:45:39 UTC
At my system (SuSE Linux 9.1, KDE 3.2.1) aRtsd / Knotify also crashed. It crashes everytime I start KDE. I don't know much about software or debugging, but this was the backtrace:

(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(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)...[Thread debugging using libthread_db enabled]
[New Thread 1081247456 (LWP 4303)]
(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)...0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbfffea8c in ?? ()
#2  0x00000000 in ?? ()
#3  0x00000000 in ?? ()
#4  0x40526e63 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#5  0x08055fba in Arts::CrashHandler::defaultCrashHandler ()
#6  <signal handler called>
#7  0x40280847 in Arts::Synth_WAVE_SIN_skel::_interfaceNameSkel ()
   from /opt/kde3/lib/libartsflow_idl.so.1
#8  0x40171302 in Arts::Synth_WAVE_SIN_impl_Factory::interfaceName ()
   from /opt/kde3/lib/libartsflow.so.1
#9  0x403fa6eb in Arts::ObjectManager::create ()
   from /opt/kde3/lib/libmcop.so.1
#10 0x40079bf6 in Arts::SoundServerStartup_base::_create ()
   from /opt/kde3/lib/libsoundserver_idl.so.1
#11 0x40079c60 in Arts::SoundServerStartup::_Creator ()
   from /opt/kde3/lib/libsoundserver_idl.so.1
#12 0x0805754e in main ()
Comment 14 riaanho 2004-11-26 22:01:36 UTC
I am using Gentoo with KDE 3.3.1 and if I change anything in the Control Center - Sound system and click the apply button then the same window pops up and informed me :      
The application Knotify (knotify) crashed and
caused signal 11 (SIGSEGV).
There is no valid backtrace to post as this is the message in the backtrace window : This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

But everything is working for me. I have sound etc.

So I is really anoying.
Comment 15 riaanho 2004-11-26 22:25:48 UTC
*** This bug has been confirmed by popular vote. ***
Comment 16 Stefan Gehn 2004-11-26 22:30:34 UTC
Still no valid backtrace of artsd crashing with debug-symbols, therefore unconfirming again.
Comment 17 Alexander Rødseth 2005-01-18 15:22:07 UTC
*** This bug has been confirmed by popular vote. ***
Comment 18 George Goldberg 2007-12-17 05:46:46 UTC
Is this bug still present in a recent version of KDE, such as 3.5.8? Further, aRTS is dead and is replaced in KDE 4 by phonon.
Comment 19 George Goldberg 2008-01-22 03:49:46 UTC
Closing due to no response by reporter. Please reopen if this bug is still present in a current version of KDE (at time of writing, 3.5.8).