According to Desktop::Notify::Notification developer Stephen Cavilia
this bug should have been fixed in 0.03. Unstable (sid) still has 0.01.
Quote from Stephen:
"Hmm, I think i fixed that in the 0.03 release (not by initializing id
to 0, which allows the close method to potentially send useless messages
to the daemon, but by defaulting to 0 in the Notify dbus call)."
The related suggested fix to Notification.pm was:
sub new {
my ($class, $server, %params) = @_;
my $self = \%params;
$self->{server} = $server;
# original
# $self->{id} = undef;
# changed
$self->{id} = 0;
bless $self, $class;
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
