Bug 19505 - Gnome linuxconf generates "/etc/sysconfig/mouse has a revision date in the future" message after saving NIC-parameters in basic host information
Summary: Gnome linuxconf generates "/etc/sysconfig/mouse has a revision date in the fu...
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-linuxconf   
(Show other bugs)
Version: 7.0
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Jay Turner
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-21 08:27 UTC by Need Real Name
Modified: 2015-01-07 23:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-18 09:56:04 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 Need Real Name 2000-10-21 08:27:26 UTC 
Every time when I try to set the parameters (IP-address, NIC module, 
netmask etc) to work with the 3Com 3C509 NIC with Gnome linuxconf I get 
the following message two times in a row:

"The file /etc/sysconfig/mouse has a revision date in the future. This 
probably means that your system time is wrong or has been wrong at some 
point."
After selecting OK on both fault messages the Gnome session manager 
crashes due to a fatal error (segmentation fault) and I've to reboot the 
system or login again. After rebooting the NIC isn't recognized.
BTW the error message text contains faults: "as a revision date" and "as 
been wrong at some"
Comment 1 Need Real Name 2000-10-21 08:31:42 UTC 
The mouse hangs after the two messages are generated and if I've selected them 
with an "OK" confirmation.
Comment 2 Kjartan Maraas 2004-03-29 20:29:59 UTC 
guess it's time to close these old reports off now?
Note You need to log in before you can comment on or make changes to this bug.