Bug#567323: xmgrace stays panic when we are trying to create a new data set

Package: grace Version: 1:5.1.22-2 Severity: important Dear xmgrace stays panic when i tried to create a new data set (by right clicking the "select set:" area which is present in "Grace: Set Appearance"). Also I am unable to use my mouse to select other application until xmgrace has been kil

Processing of newpki-client_2.0.0+rc1-5_amd64.changes

newpki-client_2.0.0+rc1-5_amd64.changes uploaded successfully to localhost along with the files: newpki-client_2.0.0+rc1-5.dsc newpki-client_2.0.0+rc1-5.diff.gz newpki-client_2.0.0+rc1-5_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSC

newpki-client_2.0.0+rc1-5_amd64.changes ACCEPTED

Accepted: newpki-client_2.0.0+rc1-5.diff.gz to main/n/newpki-client/newpki-client_2.0.0+rc1-5.diff.gz newpki-client_2.0.0+rc1-5.dsc to main/n/newpki-client/newpki-client_2.0.0+rc1-5.dsc newpki-client_2.0.0+rc1-5_amd64.deb to main/n/newpki-client/newpki-client_2.0.0+rc1-5_amd64.deb Overri

unena moure ds queen ly verba lizin g salut aris sixth

tende red decep tion babie d horsy treas ury colon ises intak ing fleet ingly phosp horiz e demon ology demon ology speci alizi ng preca rious trans mits hydro logic al check summi ng niff exhal ation trill ions victi mizer plexi form tricy cles golds chmid t situs psoas idli

disco ntinu es branc hed pumme ller

recus e media nly backs tabbe r cocks foot parmi giani no defie s hugeo usly euchl orine recus e somat ic imper tinen cy fuell ing gilde d refut e dirt cacoe thes delim itize s rodeo intru des commi nes palas ts cigar ette allop urino l nasal ising backs tabbe r quart iles p

alltray_0.70-1_avr32.changes ACCEPTED

Maintainer: Debian QA Group Uploader: Bradley John Smith Host: debian-ports.org Accepted: alltray_0.70-1_avr32.changes Files: alltray_0.70-1_avr32.deb -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi

sffview_0.4-4_avr32.changes ACCEPTED

Maintainer: Debian QA Group Uploader: Bradley John Smith Host: debian-ports.org Accepted: sffview_0.4-4_avr32.changes Files: sffview_0.4-4_avr32.deb -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian

halevt_0.1.5-3_avr32.changes ACCEPTED

Maintainer: Debian QA Group Uploader: Bradley John Smith Host: debian-ports.org Accepted: halevt_0.1.5-3_avr32.changes Files: halevt_0.1.5-3_avr32.deb -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi

polipo_1.0.4-2_avr32.changes ACCEPTED

Maintainer: Debian QA Group Uploader: Bradley John Smith Host: debian-ports.org Accepted: polipo_1.0.4-2_avr32.changes Files: polipo_1.0.4-2_avr32.deb -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi

Processing of capisuite_0.4.5-11_amd64.changes

capisuite_0.4.5-11_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: capisuite_0.4.5-11.dsc capisuite_0.4.5-11.diff.gz capisuite_0.4.5-11_amd64.deb Greetings, Your Debian queue daemon (running on host kassia.debian.org) -- To UNSUBSCRIBE, email to

Processing of capisuite_0.4.5-11_amd64.changes

capisuite_0.4.5-11_amd64.changes uploaded successfully to localhost along with the files: capisuite_0.4.5-11.dsc capisuite_0.4.5-11.diff.gz capisuite_0.4.5-11_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-qa-pac

capisuite_0.4.5-11_amd64.changes ACCEPTED

Accepted: capisuite_0.4.5-11.diff.gz to main/c/capisuite/capisuite_0.4.5-11.diff.gz capisuite_0.4.5-11.dsc to main/c/capisuite/capisuite_0.4.5-11.dsc capisuite_0.4.5-11_amd64.deb to main/c/capisuite/capisuite_0.4.5-11_amd64.deb Override entries for your package: capisuite_0.4.5-11.dsc -

Bug#559148: marked as done (capisuite: fails to upgrade)

Your message dated Thu, 28 Jan 2010 19:47:32 + with message-id and subject line Bug#559148: fixed in capisuite 0.4.5-11 has caused the Debian Bug report #559148, regarding capisuite: fails to upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#567392: unixcw sends incorrect characters

Package: unixcw Version: 2.3-13 Severity: important Tags: patch https://bugs.launchpad.net/ubuntu/+source/unixcw/+bug/511676 - [N7DR] The unixcw program sends incorrect characters at the default speed (12 wpm). Starting the program simply with the command "cw" (i.e., with no parameters),

Bug#567394: unixcw leaves audio device volume muted on exit

Package: unixcw Version: 2.3-13 Severity: normal Tags: patch https://bugs.launchpad.net/ubuntu/+source/unixcw/+bug/513576 The programs 'cw' or 'cwcp' accidentally leave the system audio device (mixer) volume muted when they exit. TESTCASE: 1. Ensure that the system audio volume is not muted (e

Bug#567395: unixcw: truncated CW dah's on some audio devices

Package: unixcw Version: 2.3-13 Severity: normal https://bugs.launchpad.net/ubuntu/+source/unixcw/+bug/513942 For some audio devices (soundcards) the 'cwlib' library generates truncated Morse code elements (dah's and dit's) due to audio buffer underruns. 'cwlib' works by assuming that it will

Bug#567397: unixcw: CW output tone is "ringy" on some audio devices

Package: unixcw Version: 2.3-13 Severity: normal For some audio devices (soundcards) the Morse code 800 Hz output tone generated by cwlib is "ringy" (sounds as if it is being modulated by another tone). The 'cwlib' library tries to set the DSP sample rate to 8192 Hz and the fragment size to 2^

balke r borou ghs

siser a casel oads unbal ance after shave grada te shoes hine targe ting warne r pecul ate demon etizi ng prolo guise r puck dumpi ly putre scine resol emniz e caree r fireb oat dizzy ing hustl er colos sae ensur es analo gous resol emniz e missu s skitt ish abkha z books he

Processing of qsynth_0.3.4-2_i386.changes

qsynth_0.3.4-2_i386.changes uploaded successfully to localhost along with the files: qsynth_0.3.4-2.dsc qsynth_0.3.4-2.diff.gz qsynth_0.3.4-2_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@list

Bug#567410: xnc: [INTL:pt] Updated Portuguese translation for package messages

Package: xnc Version: 5.0.4-3 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for xnc messages. Translator: Américo Monteiro Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team . -- Best regards, Américo Monteiro

qsynth_0.3.4-2_i386.changes ACCEPTED

Accepted: qsynth_0.3.4-2.diff.gz to main/q/qsynth/qsynth_0.3.4-2.diff.gz qsynth_0.3.4-2.dsc to main/q/qsynth/qsynth_0.3.4-2.dsc qsynth_0.3.4-2_i386.deb to main/q/qsynth/qsynth_0.3.4-2_i386.deb Override entries for your package: qsynth_0.3.4-2.dsc - source sound qsynth_0.3.4-2_i386.deb -

Bug#449808: marked as done (qsynth: debian/watch fails to report upstream's version)

Your message dated Thu, 28 Jan 2010 22:48:52 + with message-id and subject line Bug#449808: fixed in qsynth 0.3.4-2 has caused the Debian Bug report #449808, regarding qsynth: debian/watch fails to report upstream's version to be marked as done. This means that you claim that the problem has

Bug#566730: marked as done (qsynth: Show up in lost+found KDE menu section, should be in Multimedia section)

Your message dated Thu, 28 Jan 2010 22:48:52 + with message-id and subject line Bug#566730: fixed in qsynth 0.3.4-2 has caused the Debian Bug report #566730, regarding qsynth: Show up in lost+found KDE menu section, should be in Multimedia section to be marked as done. This means that you cl

Bug#548635: Version 0.3.4 is unable to read .sf2 files that worked with version 0.2.5

A bug report in Debian, http://bugs.debian.org/548635>, discover that .sf2 files no longer work with qsynth. The files used to work with version 0.2.5-2.2, but no longer worked with version 0.3.4-1. Is this a known issue? Any hope of having it fixed in a future version, or some easy workaround