Comment 24 for bug 106060

Ted,

I'm sorry, but I did not understand your message. I'm a retired programmer
of over 20 years, but never worked with Unix or Linux, so some of your terms
are obscure to me. In particular, your use of the term "hack" is unclear to me.

I understand your message to say you have changed the source package
name from gnome-screensaver to xscreensaver, and you have removed
yourself as the person assigned to work on it. Is this correct?

The fact that this bug, along with the difficulties in rendering several other
screensaver modules, showed up with the arrival of Feisty last April, and
given the severity of its effects, I would have thought it would have been
reasonably easy to identify and correct, but that was apparently not true.

This is only about the second communication I have received in almost a
year that is directly related to bug 106060. Apparently it was not deemed
serious enough to merit fixing right away, based on the severity alone.
That tells me the people who would work on it must have more important
things to work on, or to much to work on, or there are too few workers.

Anyway, if you could confirm my interpretation, or correct it, I'd appreciate it.

Jerry

 -------------- Original message ----------------------
From: Ted Gould <email address hidden>
> X Screensaver is the source of all the hacks, and this seems to be hack
> specific.
>
> ** Changed in: xscreensaver (Ubuntu)
> Sourcepackagename: gnome-screensaver => xscreensaver
> Assignee: Ted Gould (ted-gould) => (unassigned)
>
> --
> Selecting the Molecule screensaver makes the PC freeze. It is completely
> unresponsive.
> https://bugs.launchpad.net/bugs/106060
> You received this bug notification because you are a direct subscriber
> of the bug.