On Apr 4, 2008, at 5:09 PM, Moritz Muehlenhoff wrote:
But is there point in keeping it, now that mpg123 is free software?
Yes, because mpg321 uses libmad, which is a) very high quality and b)
fixed-point, so it works efficiently on machines without an FPU (like
many ARM machines).
What a
On Mar 19, 2008, at 9:03 PM, Peter Eisentraut wrote:
Obviously, this package is not being maintained anymore, so unless
someone objects, I'm going to orphan this package in about a week's
time.
I'm also the upstream developer for mpg321, and there's been no
upstream development either. :)
Michel Dänzer wrote:
> As it seems threading related: Does XInitThreads() get called and finish
> before any other libX11 function is called?
Yes. (And yes, it's definitely threading-related.)
reassign 463159 libxcb1 1.1-1
forwarded 463159 http://bugs.freedesktop.org/show_bug.cgi?id=9528
thanks
This bug is actually in libxcb1, not libx11-6. (Although I'm willing to
be proven wrong, and that it's some *interaction* between libx11 and
libxcb that's causing it.)
--
To UNSUBSCRIBE, emai
Package: libx11-6
Version: 2:1.1.3-1
Severity: critical
This is only 'critical' because it causes unrelated software (e.g., Side
Effects Software's Houdini) to break by causing hangs. Feel free to
downgrade, but this is a very important bug to me, at least.
This is also reported upstream:
http://
reassign 461119 libao2
done
Frederik Eaton wrote:
> Changing to 'alsa' allows me to play things with mpg321, but when
> another program is using the device, the error from mpg321 is still
> "can't create mcop directory". That's a bit confusing, perhaps mpg321
> should say something more helpful su
Frederik Eaton wrote:
> $ cat /etc/libao.conf
> default_driver=esd
>
> What should I change this to?
default_driver=alsa
And check your home directory for a .ao.conf or something along those
lines too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
Frederik Eaton wrote:
> I am currently unable to use mpg123, it dies with the error "can't
> create mcop directory". This is strange because (1) it is not trying
> to create a directory, according to strace; and (2) it seems to be
> using kde, which I never told it to do (I don't even use KDE). I t
Package: colorgcc
Version: 1.3.2.0-5
Severity: important
As of the latest version of colorgcc, my configuration file (attached)
gives the following error:
Invalid attribute name /usr/bin/ccache at /home/joe/bin/gcc-4.1 line 164
(where /home/joe/bin/gcc-4.1 is a link to colorgcc)
All compiles su
Package: fontconfig
Version: 2.4.2-1.2
Severity: normal
When starting any GTK application, I now get the following
warnings/errors:
Fontconfig error: "/etc/fonts/conf.d/30-defoma.conf", line 11: invalid
doctype "busconfig"
Fontconfig warning: "/etc/fonts/conf.d/30-defoma.conf", line 12: unknown
e
I can also reproduce this bug. Here's the info you requested:
$ dpkg -S setkeycodes
console-tools: /usr/share/man/man8/setkeycodes.8.gz
console-tools: /usr/bin/setkeycodes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: libpango1.0-common
Version: 1.16.4-1
Severity: serious
dpkg: error processing
/var/cache/apt/archives/libpango1.0-common_1.16.4-3_all.deb (--unpack):
trying to overwrite `/etc/defoma/config', which is also in package gs-common
This has been the case for a few days now. I don't see the bu
Package: icedove
Version: 2.0.0.0-1
Severity: grave
$ icedove --debug
/usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-bin
MOZILLA_FIVE_HOME=/usr/lib/icedove
LD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove/plugins:/usr/lib/mre/mre-2.0.0.0:.:/home/joe/dev/hfs/dsolib:/home/joe/dev/hf
Joachim Reichel wrote:
this notice is to announce my NMU intention. I'll prepare and upload an
NMU if I see no action from your side concerning these bugs in the next
week. Not attaching any patch as they are already in the bug logs.
Hi Joachim,
Go ahead -- NMU at will.
Thanks!
Joe
--
To U
reopen 419225
found 419225 2.5-3
thanks
This bug was fixed in libc6 2.5-2, but it regressed in 2.5-3. Maybe
this test case should be made part of the libc6 regression tests?
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: nvidia-glx-dev
Version: 1.0.8762-1
Severity: important
nvidia-glx-dev now conflicts with libgl1-mesa-dev. Unfortunately, it
doesn't totally replace libgl1-mesa-dev, since it doesn't include the
OpenGL manpages. (libgl1-mesa-dev currently has a bug, #363014, in which
it's also missing the
Package: hddtemp
Version: 0.3-beta15-3
Severity: normal
By changing /etc/hddtemp.db line 377 to:
"WDC WD740GD-([05]0FL[AC][01]|75FLA1)" 194 C
"Western Digital SATA Raptor 74GB 8MB"
(the difference being the [01] after the [AC]
you can support my drive, and stop me from h
Package: libstdc++6
Version: 4.1.0-1+b1
Severity: normal
I came across a strange bug which I'm utterly unable to reproduce on
anything but Debian unstable (including testing on Fedora Core 5).
Basically, I've worked out (through using valgrind and gdb) that calling
ifstream::read() causes a crash
Philipp Frauenfelder wrote:
> Hi Joe
>
> Am Fri, Apr 28, 2006 at 10:21:49AM -0400 hat Joe Drew getippert:
>> Valgrind works; callgrind doesn't.
>>
>> This happens for both me and a co-worker of mine.
>
> Would you mind trying the behaviour of callgrind i
Philipp Frauenfelder wrote:
> [EMAIL PROTECTED]:/# callgrind
> valgrind: no program specified
> valgrind: Use --help for more information.
>
> Btw, it is the same as I get, when I run valgrind without
> program:
>
> [EMAIL PROTECTED]:/# valgrind
> valgrind: no program specified
> valgrind: Use --
The 'unable to load usable ISO8859 font' problem is not isolated to
xmessage; programs such as xfontsel can't find fonts either.
The funny part is that there are lots of iso8559 fonts available:
$ xlsfonts -fn '-*-*-*-*-*-*-*-*-*-*-*-*-iso8859-*' | wc -l
2918
$ xfontsel -pattern '-*-*-*-*-*-*-*-*
Package: valgrind-callgrind
Version: 0.10.1-1
Severity: grave
Callgrind always quits immediately on me, no matter what I do.
[EMAIL PROTECTED]:~$ callgrind
Killed
[EMAIL PROTECTED]:~$ strace callgrind
[ ... bunch of stuff ... ]
open("/usr/lib/debug/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1
Package: xbase-clients
Version: 1:7.0.0-4
Severity: important
When I run xmag, then click somewhere to magnify, I get the following error:
$ xmag
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Warning: Cannot convert string "8x13bold" to type
Package: locales
Version: 2.3.6-5
Severity: serious
Setting up locales (2.3.6-5) ...
Generating locales (this might take a while)...
en_CA.ISO-8859-1... done
ja_JP.UTF-8... done
ja_JP.EUC-JP... done
Generation complete.
*** update-locale: Error: LANGUAGE ("en_CA:en_US:en_GB:en") is not
compa
In fact, it seems that metacity 2.14 is pretty horribly broken w.r.t.
focus right now. For example, most windows opened via the command
line open *behind* the gnome-terminal window I opened them from. I am
not sure if this has to do with the "don't raise windows on click"
feature, but I wou
severity 360786 normal
thanks
I inflated the severity of this bug.
This bug has been reproduced by a colleague of mine. He discovered that
a workaround was to resize the gnome-terminal window, then resize it
back to its original size. After that, vi draws properly.
Joe
--
To UNSUBSCRIBE, ema
Package: metacity
Version: 1:2.14.1-1
Severity: normal
Metacity 2.14, with "don't raise windows on click" gconf key set,
doesn't raise windows when I click on their entry in the window list. I
consider clicking on the window list equivalent to clicking on the title
bar, which seems to be the only
Package: gnome-terminal
Version: 2.14.0-1
Severity: grave
Since I updated gnome-terminal today, I've had intermittent but
repeatable problems with curses programs not drawing properly. I
generally work with very tall terminal windows, 80x63 or so. If I create
a terminal window of that height, then
Luk Claes wrote:
Attached the patch for the version I intend to upload. Please respond if
you don't want this NMU to happen, if you are working yourself on a
patch or if you think that the attached patch won't work.
Looks good, Luk. Please go ahead with my thanks and blessing.
Joe
--
To UNSU
Package: inkscape
Version: 0.43-2
Severity: normal
In the export bitmap entry of the File menu, the default is to have an
image with an extension (and format) of png. However, if I change this
to file.jpg, inkscape silently decides that it'll still export a png,
but with the *extension* jpg.
Inst
Package: cupsys
Version: 1.1.23-13
Severity: normal
>From the debconf manual:
lowVery trivial questions that have defaults that will work in the
vast majority of cases.
medium Normal questions that have reasonable defaults.
high Questions that don't have
adrian wrote:
I've applied Wolfgang's fix and added a "uniq" hack onto the temporary
files function, hopefully this will sort it finally. I've tested with
two files, file + CVS, CVS + CVS and it all looks like it works now.
With the patch you provided, it works for SVN too. Looks good!
--
To
Package: tkdiff
Version: 1:4.0.2-3
Severity: grave
I'm sad to report that tkdiff still seems broken. This is on a diff of a
subversion file.
Error in startup script: can't read "errorCode": no such variable
while executing
"error "Failed creating temporary file: $errorCode""
(procedure "t
My mistake - sorry. I didn't realize this was already assigned to tcsh,
and I thought I was reopening another bug on the same issue.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reopen 339406
severity 339406 normal
thanks
tcsh should not rely on dircolors not being set, and it should
especially not barf on something it doesn't recognize.
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: tkdiff
Version: 1:4.0.2-2
Severity: grave
For every subversion file I try to tkdiff, I get the following error:
Error in startup script: can not find channel named "fid"
while executing
"close fid"
(procedure "tmpfile" line 11)
invoked from within
"tmpfile $index"
(proced
Ari Pollak wrote:
Joe: Do you mind if I take over maintainership of this package, at least
until you're able to do regular updates again?
At least add yourself to Uploaders, please. :)
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
Frank Küster wrote:
Joe, did you install from a system without any tex-common on it, or with
tex-common in rc state, or was it an upgrade (from which version)?
It was an upgrade, and I believe it was from 0.8 to 0.9. (There's no
good reason for it to be otherwise; the bug first occurred on Mon
Package: tex-common
Version: 0.9
Severity: grave
tex-common fails to install because it can't chmod an ls-R file.
/var/lib/texmf exists on my system, but the ls-R file doesn't.
Setting up tex-common (0.9) ...
chmod: cannot access `/var/lib/texmf/ls-R': No such file or directory
dpkg: error proces
Package: distcc
Version: 2.18.3-3
Severity: normal
distcc's init.d file sets LISTENER to 127.0.0.1 by default, and sets it
again in /etc/default. This means that simply removing the LISTENER
definition from the default file doesn't actually disable it. The
correct thing to do is likely to remove t
Luk Claes wrote:
Attached the patch for the version I intend to upload. Please respond if
you don't want this NMU to happen, if you are working yourself on a
patch or if you think that the attached patch won't work.
Please do, Luk. I am without a working Debian machine for some time now.
--
T
Dalibor Topic's latest mail states that kaffe should be fixed. Can this
subversion bug be closed?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: valgrind-callgrind
Version: 0.9.12-1
Severity: grave
valgrind-callgrind isn't installable since it conflicts with valgrind >
2.6, and valgrind 3.0 is the only verison available in unstable.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500,
ibsmpeg0 should exist. My problem is that I don't have an
operational Debian machine with my private key on it. I'll see if I can
rectify that today, and revert the NMU.
--
Joe Drew <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
If you use Internet Explorer, your computer isn'
Package: zlib1g
Version: 1:1.2.3-1
Severity: normal
In trying to compile zlib in a debug way, I defined and exported
DEB_BUILD_OPTIONS="nostrip,noopt", but for some reason the zlib rules
file ignored it. I can't see why that would be happening, but it happens
all the same.
-- System Information:
Package: xlibs
Version: 6.8.2.dfsg.1-2
Severity: important
Ever since I upgraded to xorg, after a certain amount of time (a few
days), I get the following error every time I try to open another
program:
Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached
It's pos
Package: g++-4.0
Version: 4.0.1-2
Severity: normal
See PR 22132, just fixed upstream. I'd very much appreciate if this fix
could be integrated to the Debian packages, especially if 4.0.2 will be
a long time in coming.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
Package: x11-common
Version: 6.8.2.dfsg.1-2
Severity: normal
When I installed x11-common, even though xfree86-common was removed, the
files /etc/X11/Xsession.d/*xfree86-common* files (whose contents, I
assume, are duplicated in *x11-common*) were left lying around. This
resulted in the very strang
Package: mozilla
Severity: serious
Justification: no longer builds from source
Building Mozilla on an up-to-date unstable machine results in the below
build failure:
g++ -o nsFreeType.o -c -DOSTYPE=\"Linux2.6\" -DOSARCH=\"Linux\" -I../..
-I../../../dist/include/xpcom -I../../../dist/include/stri
sean finney wrote:
could you throw a "set -x" in the top of the postinst script and
send us the output?
Sure can!
[EMAIL PROTECTED]:~# /var/lib/dpkg/info/mysql-server-4.1.postinst configure
+ export
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/sbin:/usr/sbin:/bin
Package: mysql-server-4.1
Severity: serious
It looks as though the postinst is trying to stop mysql instead of
starting it. I had a working mysql installation previous to this, and
I haven't seen this problem before.
Relevant portions of the upgrade log are below.
Preparing to replace mysql-serv
51 matches
Mail list logo
