Bug#767625: avahi-daemon leaks MAC address

2014-11-01 Thread Blue Beret
Package: avahi-daemon Version: 0.6.31-4 Severity: important Tags: ipv6 Dear Maintainer, I noticed that when I use NetworkManager to connect to a wired Ethernet network using a custom (or cloned) MAC address, avahi-daemon has access to both MAC addresses and uses them inconsistently in MDNS

Bug#468572: libpurple0: OSCAR group names wrong encoding

2008-02-29 Thread Blue Beret
Package: libpurple0 Version: 2.3.1-2 Severity: normal Tags: patch During server-side buddylist import over OSCAR, libpurple converts all group names from the local encoding (CP1250 in my case) to UTF-8. However, all ICQ clients - Pidgin included! - save those names in UTF-8. I am sending a patch

Bug#458262: pre-removal fails when gkrellmd not running

2007-12-29 Thread Blue Beret
Package: gkrellmd Version: 2.2.10-2 Severity: important When upgrading or removing, gkrellmd pre-removal script tries to stop the daemon. If it's not running, the whole removal process fails. This probably applies to version 2.3.1-1, too. -- System Information: Debian Release: lenny/sid APT

Bug#416149: icedove: no reload after downloading message

2007-03-25 Thread Blue Beret
Package: icedove Version: 1.5.0.10.dfsg1-2 Severity: normal When configured not do display previews in the main window and not to download the message bodies automagically, the following happens: I open an unread message, a new window asks me to retrieve the message from the server, I confirm,

Bug#391798: gaim: fails to receive messages ending with acute wovel

2006-10-09 Thread Blue Beret
Hi, I set UTF-8 in Account Settings / Advanced / Encoding. The error is (An error occured when receiving this message. The buddy you are talking to has probably a buggy client.) being displayed instead of the message. Setting locale to cs_CZ.UTF8 makes things no better. Hi, Where are you

Bug#391798: gaim: fails to receive messages ending with acute wovel

2006-10-09 Thread Blue Beret
I do not think this is the problem. I apologize if I haven't said it yet, but using the UTF-8 encoding works absolutely right except for the last character error. All other messages appear correctly. Using another encoding, e.g. cp1250 for Czech Windows environments, results in screwing the

Bug#391798: gaim: fails to receive messages ending with acute wovel

2006-10-08 Thread Blue Beret
Package: gaim Version: 1:2.0.0+beta3.1-4 Severity: normal Tags: l10n Having UTF-8 set as the ICQ encoding, all messages are transferred well, except for those ending with an acute wovel (eg. á, é, í, ó, ú, ý) - though they make no harm inside a message, an error is reported if one of these

Bug#390511: mpd: please add pause/resume/stop fades

2006-10-01 Thread Blue Beret
Package: mpd Version: 0.12.0-1 Severity: wishlist I did use XMMS with Crossfade plugin before switching to mpd. There was a feature to make a quick fadeout on pause/stop and a quick fadein on resume. Could this be added to mpd? -- System Information: Debian Release: testing/unstable APT

Bug#385444: dosbox: openGL support dropped in version 0.65-1?

2006-08-31 Thread Blue Beret
Package: dosbox Version: 0.63-2.2 Severity: important I was previously using dosbox 0.63-2.2, configured to use an OpenGL output. After upgrading to 0.65, it seemed to use 'surface' output again - the image dithering was lost, and an audible performance drop was present. I was forced to