Bug#602753: cdtool: everything seems to work as expected, but no sound :(

2010-11-07 Thread Cristian Ionescu-Idbohrn
Package: cdtool Version: 2.1.8-release-2 Severity: important Renders package unusable :( (audacious will play this cd though; with sound) Like: $ cdctrl Opened /dev/cdrom as device 3 i CMD info no-status 0 53:36.19 2:19.72 END d 1-14 1 00:02.00 A 2 01:06.65 A 3 07:41.00 A 4 12:52.40 A 5 1

Bug#602752: cdcd: everything seems to work as expected, but no sound :(

2010-11-07 Thread Cristian Ionescu-Idbohrn
Package: cdcd Version: 0.6.6-11 Severity: important Renders package unusable :( (audacious will play this cd though, with sound) Like: c...@caesar> cdcd info Album name: Back On The Block Album artist: Quincy Jones Total tracks: 14 Disc length:57:56 Stopped c...@caesar> cdcd tra

Bug#232029: snooper: segfault when resizing the terminal window

2010-02-16 Thread Cristian Ionescu-Idbohrn
On Tue, 16 Feb 2010, Stefan Bauer wrote: > Christian, > > this report is more than 6 years old but could you please try if the problem > still persists with the latest snooper package from unstable? There have been > many changes in the past. > > I was trying to reproduce your problem but it works

Bug#294523: mimedecode: decoding subject headers

2009-05-24 Thread Cristian Ionescu-Idbohrn
Package: mimedecode Version: 1.9-4 Severity: normal It took just somewhat over 4 years for someone to look into this bug :( I suppose noone's interested in fixing it :( Michele, as you already discovered, the expression you used: SUB=`formail -zx Subject: | mimedecode` won't be useful.

Bug#385011: decode_header_line assertion

2009-05-24 Thread Cristian Ionescu-Idbohrn
Using formail to extract the Subject will remove the 'header' part. Use grep instead of formail and it will work. -- Cristian Ionescu-Idbohrn Sun, 24 May 2009 12:06:31 +0200 --- mimedecode.c.original 2009-05-22 12:12:51.0 +0200 +++ mimedecode.c2

Bug#510273: wmtop: segfault

2008-12-30 Thread Cristian Ionescu-Idbohrn
Package: wmtop Version: 0.84-9 Severity: normal I've seen this occasionaly, during the year(s). Don't know what's causing it nor how to reproduce. _Seems_ to be triggered by suddenly high cpu activity. dmesg shows: [789110.5ê91676] wmtop[6544]: segfault at 0 ip 0804a5de sp bfba6250 error 4 in