[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#444081: marked as done (totem: jackd stuff is awefully talkative)



Your message dated Fri, 24 Oct 2008 00:30:53 -0400
with message-id <8e2a98be0810232130x784657afwe7393bd5237a577e@mail.gmail.com>
and subject line re: Tries to start jackd although JackNoStartServer is given
has caused the Debian Bug report #436666,
regarding totem: jackd stuff is awefully talkative
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
436666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436666
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: totem
Version: 2.20.0-1
Severity: normal

if jackd is not installed when totem is run, there will be an error
message "sh: jackd: command not found".  and even if jackd is installed
the message "JACK tmpdir identified as [/dev/shm]" is presented during
gnome start up.  none of this information is really useful to the user
and should be supressed.

mike

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages totem depends on:
ii  totem-gstreamer               2.20.0-1   A simple media player for the Gnom

totem recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
i just tested the sample code in the previous post with the latest
version of jack in sid (0.109.2-4), and this problem appears to have
been resolved.

please reopen the bug if you encounter the problem with this version or newer.


--- End Message ---

Reply to: