#586174 evolution: printing appointment from calendar puts date and time in white

Package:
evolution
Source:
evolution
Description:
groupware suite with mail client and organizer
Submitter:
Daniel Kahn Gillmor
Date:
2010-07-31 14:39:03 UTC
Severity:
normal
#586174#5
Date:
2010-06-17 05:13:01 UTC
From:
To:
when i print an appointment from the Calendar, the most critical information
(date and time of the appointment) are "printed" in white, even though the rest
of the text is black.  On white paper, this makes it so the date and time are
invisible.

I'm attaching a PDF example, gathered from the webcal feed at
https://penta.debconf.org/dc10_schedule/schedule.en.ics

#586174#10
Date:
2010-06-17 05:40:00 UTC
From:
To:
Thanks, but please submit upstream issues directly upstream on
http://bugzilla.gnome.org.

Cheers,

#586174#15
Date:
2010-06-17 05:53:11 UTC
From:
To:
Feel free to forward this upstream (and cc me if you like) if you feel
confident this is not a debian-specific issue.  I haven't had a chance
(and won't, in the forseeable future) to try it on a non-debian distro.

I also don't know enough about the interrelationships between gnome,
evolution, and the printing subsystem to be confident that it is an
upstream issue myself.

Thanks for maintaining evolution for debian!

#586174#20
Date:
2010-06-17 06:11:03 UTC
From:
To:
I don't have time to handle most serious issues, not to mention more
minor one. So no, I can't do it myself. I'm fairly confident it's an
upstream issue, and have even less way to reproduce on another distro.

Sorry, but reporting directly is your best chance to have it fixed (for
that particular bug but also for others).

Cheers,

#586174#25
Date:
2010-07-31 13:43:59 UTC
From:
To:
Hi Yves-Alexis,

I draw your attention to:

http://www.debian.org/doc/developers-reference/developer-duties.html#upstream-coordination

Specifically the second sentence of the first paragraph, which you
appear to have forgotten, where it says:

  You have to forward these bug reports to the upstream developers...

I note that the construction "have to" should probably read as "MUST"
instead, as per RFC usage, but it is reasonably definite even as it is.

If we start discouraging bugs on the basis that we're rather busy, then
the knowledge contained in the bugs will be lost, and will be
unavailable to others who find the same bug.  Since you are confident
that it's an upstream issue, it is to your advantage to have it recorded
in the BTS and marked as forwarded upstream, as that should prevent the
next person to find it from bothering you, and you never know, it might
even get fixed.

Cheers, Phil.

#586174#30
Date:
2010-07-31 14:36:11 UTC
From:
To:
No I don't, I simply don't have time. So I'm maintaining evolution the
better I can. If it's not enough, then you're gladly welcome to help,
really.

I'm not discouraging but reports. I ask people to file relevant bugs
upstream because that's where they belong. If they file it in Debian
too, that's even better (and bonus points for filing them with the
according “forwarded-to”). But upstream is where the (upstream) bugs
will be fixed, not here, so it's faster to file issues upstream than to
wait for me to do it.

And you know what, that's exactly what I do.

Cheers,