Well, to open the issues upstream I have to be sure it is not SUSE-specific. I do not have other distro installed currently, so I can only guess. That's why I preferred to open them in novel bugzilla in hope that developers will forward it usptream, if necessary.
Sometimes it is obvious, such as no meta-data in Konqueror (KDE) or a Yast issue (Suse). Sometimes not :)
BTW, it sounds a bit strange to me that when the bug is identified as upstream, it is now marked as "resolved" in Novell bugzilla. I would expect some kind of "monitoring" state. Otherwise how will Open SUSE developers know when the upstream bug is fixed and they can pick the fix up?
That is the norm, as the changes will be picked up the next time the KDE sources are pulled. As there is no need for further attention from Suse devs, it is marked Resolved. Sometimes it gets pushed from Suse -> KDE -> Qt and although it is "resolved" in Suse and KDE, the bug rots for years in the Qt issue tracker! (jaded)
It was in KDE for many years. It was initially called kwintv, but at some stage was included in KDE and renamed to kdetv. It is in the process of porting and is in KDE "playground", so I hope in some short time it will be back.
Ah, it's in playground?! Great! -- Dotan Cohen http://what-is-what.com http://gibberish.co.il -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org