From: "Sebastian H." <vand2@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: Alsamixer-Qt4 0.4.0 released
Date: Thu, 05 Aug 2010 13:22:02 +0200 [thread overview]
Message-ID: <4C5A9EDA.10509@gmx.de> (raw)
In-Reply-To: <20100804233309.GB6629@00110101.home>
Am 05.08.2010 01:33, schrieb errordeveloper@gmail.com:
> it crashes on my machine with one USB soundcard,
> and an RME Hammerfall ..i think RME causes it -
> i get a `Floating exception` ..hm, not a segfault this time :)
This looks like a bug in the slider/painter code.
Maybe some ranges are screwed, like 0 to 0 or so and the slider
can't handle it.
A gdb backtrace would be helpful.
Could you compile with:
cmake -DCMAKE_BUILD_TYPE=Debug
make
and then create a backtrace with gdb:
echo -e "run\nwhere\nquit" > gdb_com.txt
gdb src/alsamixer-qt4 -batch -x gdb_com.txt > gdb.txt
and send me the gdb.txt file?
> ..i can do some tests ..have you got an svn or git?
Right now I only have a mercurial repository on my local machine.
I think sourceforge support mercurial now, I'll check on this later.
> basically RME alsa driver is different from all other drivers,
> so far i only see one mixer that presented snd-hdsp options
> in correct way ..it's mostly just tick boxes..
> i'd say that you can just try to set up a condition
> that if the card is RME, then just ignore that card :)
> ..otherwise check hdspmixer and hdspconf in alsa-tools.
I would like to avoid keeping a blacklist in the mixer application.
It's meant to be a general purpose mixer but it should'n crash on high
end hardware.
Sebastian
next prev parent reply other threads:[~2010-08-05 11:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 12:17 Alsamixer-Qt4 0.4.0 released Sebastian H.
2010-08-04 23:33 ` errordeveloper
2010-08-05 11:22 ` Sebastian H. [this message]
2010-08-08 12:12 ` Sebastian H.
2010-08-05 7:20 ` Raymond Yau
2010-08-05 12:48 ` Sebastian H.
2010-08-06 0:26 ` Raymond Yau
2010-08-06 14:34 ` Sebastian H.
2010-08-12 1:38 ` Raymond Yau
2010-08-12 9:27 ` Sebastian H.
2010-08-05 8:46 ` The Source
2010-08-08 20:54 ` Niels Mayer
2010-08-09 14:08 ` Sebastian H.
2010-08-12 14:20 ` Niels Mayer
2010-08-15 13:14 ` Sebastian H.
2010-09-25 1:25 ` Raymond Yau
2010-09-25 10:42 ` Sebastian H.
2010-09-25 23:56 ` Raymond Yau
2010-09-26 10:36 ` Sebastian H.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C5A9EDA.10509@gmx.de \
--to=vand2@gmx.de \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).