John Lindgren on Mon, 12 Apr 2010 16:45:24 -0400 wrote:
> severity 569109 wishlist
> thanks
Sounds reasonable.
> For what it's worth, 2.3 will sort the tracks in "1, 2, ... 9, 10, 11"
> order anyway.
Good to hear. That was the main reason I noticed the missing functionality
anyway.
-Ross
Package: audacious
Version: 1.5.1-4
Severity: minor
I'm using audacious because xmms isn't packaged anymore.
One feature I used was the custom playlist string, and I was
happy to find that audacious has something similar.
But I wasn't able to implement my normal format:
Artist - Album - [TrackN
Package: audacious
Version: 1.5.1-4
Severity: normal
This is the first time I'm using audacious (previously I used xmms
but it doesn't seem to be packaged anymore) and I'm running into a
few problems. This bug report is about two problems with the
playlist window event handling. I'm running it
Package: videogen
Version: 0.32-3
Severity: normal
Tags: patch
This script doesn't seem to be updated very frequently. There are a few
issues which are fixed in the attached patch:
* a reference to XF86Config(-4)
* it fails silently when dialog, whiptail, and gdialog aren't installed
* the DEF_M
Package: network-manager
Version: 0.6.4-6
I just did my first fresh install of etch, and everything
looked really good until I rebooted and tried to use the
network.
I could ping things by IP, but name resolution was out.
I thought, must be an installer bug, so I checked the
resolv.conf, and it o
The message wasn't requesting a response so I didn't realize you were waiting
for one. I have not tried upstream, but I guess I can attempt to compile it
and see what happens.
-Ross
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED
Brice Goglin <[EMAIL PROTECTED]> wrote:
> Last year, you reported a bug to the Debian BTS regarding a Geforce PCX
> 5300 board not being supported. Do you still have problems running X on
> this board nowadays? If not, I will close this bug in the next weeks.
Hi Brice.
I'm still having the same
Brice Goglin <[EMAIL PROTECTED]> wrote:
> About 2 years ago, you reported (or replied to) a bug in the Debian BTS
> regarding a crash of the Xfree86 4.3 server on a Rendition Verite 2100
> chipset. Did any of you guys reproduce this problem recently? If not, I
> will close this bug in the next wee
Package: libx11-dev
Version: 4.3.0.dfsg.1-14sarge1
Severity: normal
Tags: patch
This man page does not discuss the actual return values of the
function, but says they are of type "Status". One might assume
that this means you could compare it with the "Success" macro.
One would be wrong.
The X
"Adam D. Barratt" <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-08-09 at 00:19 -0500, Ross Combs wrote:
> > "Adam D. Barratt" <[EMAIL PROTECTED]> wrote:
> >
> > > This is not the case - see
> > > http://lists.debian.org/debian-devel-a
Package: www.debian.org
Version: n/a
The security support for the AMD64 port is still (apparently) not
in place. However the only information on www.debian.org says that
it is. Following the instructions provided on the site is dangerous
because no security updates will be applied.
Specifically
I am having the exact same problem (and so are several other
people according to Google). I just upgraded the X server on
my wife's computer from version 3.3.x to 4.3.x, and now X is
crashing on startup. I have commented out all the modules
which caused error messages, but the signal 4 (illegal
i
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Yes, the new flex is no longer lex/POSIX compatible. It does,
> however, work with modern C/C++ compilers a lot better, is
> reenterant, and one can have multiple lex scanners in a program.
> Because of that, and the fact we have flex-old,
Package: flex
Version: 2.5.31-26
The version of flex in Debian testing no longer works with a
large number of packages which depend on traditional lex
compatibility or POSIX lex compliance. The biggest problem
I have had is that yywrap() now takes an argument of some
type.
Because of this I don'
14 matches
Mail list logo
