Bug 67844 - xscreensaver has version and build date in titlebar
Summary: xscreensaver has version and build date in titlebar
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: xscreensaver   
(Show other bugs)
Version: 1.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 67218
TreeView+ depends on / blocked
 
Reported: 2002-07-02 21:14 UTC by Havoc Pennington
Modified: 2014-03-17 02:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-07-03 20:13:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Havoc Pennington 2002-07-02 21:14:19 UTC 
Titlebar should just say "Screensaver Properties", no "xscreensaver", 
or version number, or build date.
Comment 1 Havoc Pennington 2002-07-02 22:20:53 UTC 
Correction, the other dialogs seem to say "preferences" not "properties", so
"screensaver preferences"
Comment 2 Alexei Podtelezhnikov 2002-07-03 18:51:19 UTC 
Is this a customization (seemless integration) into GNOME?
If so, please split xscreensaver according to bug 59891.

Xscreensavers could be a perfect part of KDE too. 
It does not require much effort, see bug 59891.
Comment 3 Havoc Pennington 2002-07-03 20:12:11 UTC 
I'd love to see KDE use xscreensaver instead of their own cut-and-paste fork
thing, yes. I'd really _prefer_ if upstream KDE did this, though. It would make
a lot more sense.
Comment 4 Havoc Pennington 2002-07-03 20:13:02 UTC 
(I don't see a reason to split the package though - we pretty much require 
GTK to be installed for any X install. I don't think xscreensaver does/should
require libgnomeui anymore, just GTK.)
Comment 5 Bill Nottingham 2002-08-13 02:29:35 UTC 
Fixed in 4.05-4.
Note You need to log in before you can comment on or make changes to this bug.