Your message dated Mon, 26 Feb 2007 14:33:17 -0500 with message-id <9f694b820702261133n2c3e3ccdg9797de85cfeb649b@mail.gmail.com> and subject line Bug#292597: Very old bug, do you still have this problem ? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: noatun crashes remote artsd
- From: Ryan Nowakowski <ryan@britestream.com>
- Date: Thu, 27 Jan 2005 22:04:36 -0600
- Message-id: <E1CuNN7-0005xq-00@mango.layern.com>
Package: arts Version: 1.3.2-2 Severity: normal Running noatun on a client system with ARTS_SERVER=remoteserver:41533 causes artsd on remoteserver to crash. Kaffeine and other programs don't cause the artsd crash. The remote server's sound system is configured with custom options "-p 41533 -u". Here's a backtrace: Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208815488 (LWP 22714)] [KCrash handler] #38 0xb7d5f92a in Noatun::StereoVolumeControlSSE_impl::calculateBlock () from /usr/lib/libnoatunarts.so #39 0x42212146 in Arts::StdScheduleNode::gslProcess () from /usr/lib/libartsflow.so.1 #40 0x4228ad19 in _gsl_init_engine_utils () from /usr/lib/libartsflow.so.1 #41 0x4228b0dc in _gsl_init_engine_utils () from /usr/lib/libartsflow.so.1 #42 0x42287e2f in gsl_engine_dispatch () from /usr/lib/libartsflow.so.1 #43 0x42232fe6 in GslMainLoop::run () from /usr/lib/libartsflow.so.1 #44 0x422144c0 in Arts::StdScheduleNode::requireFlow () from /usr/lib/libartsflow.so.1 #45 0x4223f01e in Arts::Synth_PLAY_impl::needMore () from /usr/lib/libartsflow.so.1 #46 0x422183eb in Arts::AudioSubSystem::handleIO () from /usr/lib/libartsflow.so.1 #47 0x42227e8a in Arts::AudioIOALSA::notifyIO () from /usr/lib/libartsflow.so.1 #48 0x424333be in Arts::StdIOManager::processOneEvent () from /usr/lib/libmcop.so.1 #49 0x42433831 in Arts::StdIOManager::run () from /usr/lib/libmcop.so.1 #50 0x424319d7 in Arts::Dispatcher::run () from /usr/lib/libmcop.so.1 #51 0x0805f680 in ?? () #52 0xbffff980 in ?? () #53 0x08066b98 in _IO_stdin_used () #54 0x00000000 in ?? () #55 0x463776fb in _dl_unload_cache () from /lib/ld-linux.so.2 #56 0x4639e7f8 in __libc_start_main () from /lib/tls/libc.so.6 #57 0x464c0edc in ?? () from /lib/tls/libc.so.6 -- System Information: Debian Release: unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages arts depends on: ii libarts1 1.3.2-2 aRts Sound system ii libartsc0 1.3.2-2 aRts Sound system C support librar -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 292597-done@bugs.debian.org
- Subject: Re: Bug#292597: Very old bug, do you still have this problem ?
- From: "Olivier Vitrat" <ovit.debian@gmail.com>
- Date: Mon, 26 Feb 2007 14:33:17 -0500
- Message-id: <9f694b820702261133n2c3e3ccdg9797de85cfeb649b@mail.gmail.com>
- In-reply-to: <20070226185304.GE25073@polishwonder.fattuba.com>
- References: <[🔎] 9f694b820702261029p11482adavfcc4cde560d449e8@mail.gmail.com> <20070226185304.GE25073@polishwonder.fattuba.com>
2007/2/26, Ryan Nowakowski <tubaman@fattuba.com>:On Mon, Feb 26, 2007 at 01:29:02PM -0500, Olivier Vitrat wrote: > the bug you've reported is ~2 years old. > Can you still reproduce this bug? If yes please give us a short note, if > not, this bug will be closed in a few weeks (but you are of course > free to reopen it). I don't have 2 debian machines to test with anymore. Sorry.
--- End Message ---