Launchpad itself

Does "Unassigned" on a bug report mean no developer is looking into it?

Asked by Kupfer

There is a bug report concerning a problem with gnome-settings-daemon, namely that on some machines the Ubuntu themes often revert to Gnome default: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/588155
It is a pretty severe problem for a whole lot of people, as the Ubuntu Forums thread on this issue signals - it is currently 17 pages long (and growing): http://ubuntuforums.org/showthread.php?t=1575703&page=17

The bug report is currently set to "Confirmed", yet "Unassigned". It took considerable effort to get even this far, as the bug report seemed abandoned for a very long time. There was confusion whether this is a Gnome bug or an Ubuntu bug. I opened a bug report on bugzilla.gnome.org. The Gnome developers determined, that it is not a Gnome issue. Quote:
"GNOME cannot fix bugs in Ubuntu. Closing as NOTGNOME."
Users reporting in the Ubuntu Forums Thread also confirmed that this is indeed an Ubuntu bug as no other Gnome distro shows signs of it (I can confirmed that too, as I'm using Fedora because of this bug).

Now, a user even confirms that the bug shows up in Natty Alpha 2 + Updates, so the problem won't go away by itself.

So my Question is: Does the fact, that the bug report is set to "Unassigned" mean, that no developers is actively looking into the problem?

There was some communication on the issue, that a backtrace has to be provided in order to have the developers look into it. That backtrace was finally provided by a user too:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/588155/comments/36

Yet the bug is still Unassigned.
Could this mean that the bug is still not being looked by anyone at despite the provided backtrace and is still orphaned. Or does that mean that someone is working on it and the "Assigned to" status will be changed later, for example after the bug is finally fixed?

Thanks for any information regarding the problem. A lot of people are anxious to have the bug resolved (I'm for example are skipping Maverick because of this and don't want it spilling over into Natty) and there seems to be no sign of any active effort by the devs to do something about it.

I hope I'm interpreting the signs wrong :)

Thanks again.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Curtis Hovey (sinzui) said : 		#1

Unassigned does means no developer is working on it. Confirmed means users recongnise the bug. Triaged means the engineers understand the bug. Confirmed bugs are often duped to a triaged bug or later marked triaged when engineers know what the underlying issue in the code is.

Can you help with this problem?

Provide an answer of your own, or ask Kupfer for more information if necessary.

To post a message you must log in.