Linked by Thom Holwerda on Wed 20th Feb 2008 00:08 UTC, submitted by Philipp Esselbach
KDE KDE 3.5.9 has been released. "The KDE Community today announced the immediate availability of KDE 3.5.9, a maintenance release for the latest generation of the most advanced and powerful free desktop for GNU/Linux and other UNIXes. The most important changes have been made to the KDE-PIM applications, including the KMail email client, KOrganizer, a planning application and other components."
Thread beginning with comment 301528
To read all comments associated with this story, please click here.
Closing bugs
by jjmckay on Wed 20th Feb 2008 00:53 UTC
jjmckay
Member since:
2005-11-11

Wow, well they are patching kde 3.5 which is nice but that didn't stop them from closing my bug report with no reason given.

http://bugs.kde.org/show_bug.cgi?id=140530

" What |Removed |Added
---------------------------------------------------------------------- ------
AssignedTo|kwin kde org |kwin-bugs-null kde org"

I presume kwin-bugs-null is a way to drop the bug into a black hole.

RE: Closing bugs
by halfmanhalfamazing on Wed 20th Feb 2008 01:46 in reply to "Closing bugs"
halfmanhalfamazing Member since:
2005-07-23

The bug still shows as open, unconfirmed.

FWIW, I think I've seen this myself. I keep my kicker panel located at the top, with auto hide enabled, at 93% length.

I usually see this bug a lot more often when I have a lot of browser windows open.

Sometimes, the panel just relocates back to the bottom, but I can't unhide it. I'll have to fix it by opening up a term and re assigning the panel via Kcontrol.

I've seen it on SuSE and PCLoS.

I added to your bug report over there.

Edited 2008-02-20 02:03 UTC

Reply Parent Bookmark Score: 2

RE: Closing bugs
by cyrilleberger on Wed 20th Feb 2008 09:20 in reply to "Closing bugs"
cyrilleberger Member since:
2006-02-01

No you are misleaded "kwin-bugs-null kde org" doesn't mean the bug is assigned to a black hole. This is a work around some limitations of bugzilla (or at least the version runned by KDE), when bugs are created for a "product", they are assigned to a default person (usually the maintainer), but if there is a team working on the "product", other members of the team might want to be warned that a new bug has been entered. The only solution to do that is to follow the activity of the "default person", the problem is that you will receive a mail for all of his bugzilla activity. That's why there is those "PRODUCE-bugs-null kde org" addresses. Now I guess the change from "kwin kde org" to "kwin-bugs-null kde org" was probably made to avoid sending bugs mail to the mailing list, but still have the possibility to easily follow activity on the kwin bugs reports.

Reply Parent Bookmark Score: 5