summaryrefslogtreecommitdiffstats
path: root/doc/doxy/fixed_bugs.dox
blob: e478b96f39abb1b90fdbef0ace0b6d97ce0b104a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
/*!
* \page fixed_bugs Fixed Bugs 
*
* You will find the newest bugs at the top of this list. If there is no comment, the bugnumbers are
* from the SUSE/Novell bugzilla (https://bugzilla.novell.com) \n
*
* Note: This list only contain reported and fixed bugs. The list is maybe not up-to-date.
*
* \section fixed_bugs_sec_0_7_x All fixed bugs for the 0.7.x tree
*
* \li   Bug \b #245081 - TDEPowersave does not set (ondemand) governor on startup \n
* \li   Bug \b #244052 - Close lid of a laptop and suspend to ram cause TDEPowersave 100% CPU \n \n
*	Needed to uncouple Action calls (as e.g. suspend on lidclose) which include blocking dialogs
*	from the related events. This is needed because otherwise the D-Bus QT3 bindings run amok
*	if the dialog block the filterfunction, since signals in QT are not really independent 
*	(they are more function calls). Used QTimer:SingleShot() for this since they go into the 
*	QT event loop and don't follow the workflow of the rest of the program. \n \n
* \li   Bug \b #229960 - CPUFREQ_DYNAMIC_PERFORMANCE seems to be ignored during boot and scheme change \n
* \li   Bug \b #230686 - TDEPowersave need to be restarted to set changed DPMS settings \n
* \li   Bug \b #230965 - puzzling battery state info \n
* \li   Bug \b #231709 - tdepowersave-0.7.1-12: comparison with string literal \n
* \li   Bug \b #231184 - TDEPowersave crashes due to uninitalized LibHalContext \n
* \li   Bug \b #229234 - TDEPowersave does not fall back to userspace governor \n
* \li   Bug \b #215262 - Suspend to disk with attached usb storage not working \n \n
*	Depending on a KDE feature TDEPowersave umount all external media before suspend and display
*	an error message if the umount fail. This need a special patch for the KDE mediamanager.\n \n
* \li   Bug \b #223164 - After suspend, second core has performance governor set \n
* \li   Bug \b #223517 - Powersave: CPU scheme "dynamic" reduces speed if only nice -19 processes run \n
* \li   Bug \b #223637 - tdepowersave crashes in first login \n
* \li   Bug \b #225212 - TDEPowersave crash on ThinkPad X60s \n
* \li   Bug \b #221715 - Functionality for configuring lid close event etc. to trigger suspend not in YaST 
*       any more, but tdepowersave doesn't have them either \n \n
*	Needed changes in TDEPowersave to adapt the new powermanagement structur and allow the user 
*	to configure options we had former in the powersave daemon. This include also changes in
*	the configure dialog to provide a way to change settings as user. \n \n
* \li   Bug \b #223922 - System not shuting down on pressing power button \n \n 
*	Changes due to new powermanagement infrastructure. (see also #221715) \n \n
* \li   Bug \b #220289 - tdepowersave 0.7.0 gives battery level notifications while charging \n
* \li   Bug \b #220271 - CPU Frequency Policy setting not possible with tdepowersave \n \n
*	Changes due to new powermanagement infrastructure. \n \n
* \li   Bug \b #220222 - Restarting D-Bus makes TDEPowersave unusable \n
* \li   Bug \b #220212 - TDEPowersave: Changing brightness does not work reliably \n
* \li   Bug \b #220553 - suspend2disk doesn't lock the screen in KDE \n
* \li   Bug \b #167919 - DPMS energy settings are ignored / lost in new kde session \n \n
*	Added DCOP interface to allow KDE to check if TDEPowersave set special DPMS settings. \n \n
*
* \section fixed_bugs_sec_0_6_x All fixed bugs for the 0.6.x tree
*
* \li   Bug \b #198237 - message: DBUS daemon not running appears (part 1/2) \n \n
*	For easier bugreporting and assign of warning messages about powersave/HAL/DBUS state added
*	string "TDEPowersave" to window caption. \n \n
* \li   Bug \b #184076 - TDEPowersave: display wrong command to start dbus daemon in errormessages \n \n
*	If the dbus daemon is not running TDEPowersave popup a errormessage. This message contains the 
*	command to restart/start dbus. This is the wrong command on SUSE/Debian/Ubuntu and other. \n \n
* \li	Bug \b #183745 - TDEPowersave: open on SLES/SLED the wrong bugzilla site \n \n
*	If the user clock on "Report a bug ..." in the tdepowersave help menu on SLES/SLED, the wrong bugzilla
*	website is used. Instead of opensuse.org we should open bugzilla.novell.com. \n \n
*	\b Fix-comment: Added new configure option (--enable-suse-sles) to force SLES/SLED as detected 
*			distribution and changed detection if SUSE Linux to detect SLES/SLED. Changed 
*			the bugzilla site for the SUSE Enterprise products. (NOTE: the bug isn't public) \n \n
* \li	Bug \b #176782 - TDEPowersave: Changing display brightness is to long winded \n \n
*	If you like to change the display brightness with TDEPowersave (temporary), you have to perform five
*	clicks, going through all the menus and the configuration dialog settings until reaching the 
*	brightness settings [...]. \n \n
*	\b Fix-comment:	Added slightly adopted patch from Timo Hoenig <thoenig@suse.de> to allow change
*			brightness if supported by hardware and enabled in the scheme via mouse wheel. \n \n
* \li	Bug \b #182515 - TDEPowersave: configure dialog allow set invalid dpms settings\n \n
*	The TDEPowersave config dialog allow to not valid DPMS setting, wich result in not set DPMS timeouts.
*	TDEPowersave does not follow the rules for the X-Server from www.xfree86.org/current/DPMSLib.pdf. \n \n
* \li	Bug \b #168619 - Access to devices from remote session. \n \n
*	If you start a remote desktop session, e.g. via VNC, TDEPowersave display "Powersave is not running ..."
*	message also if the powersave daemon is running, but the remote user has not the rights to 
*	access the DBUS interface of powersave. \n \n
*	\b Fix-comment: Reworked detection if DBUS, HAL and powersave is not running and if the user has the 
*			needed rights. Added new error messages and translations. \n \n
* \li	Bug \b #177792 - TDEPowersave: changes via dcop are not set to applet menu, some dcop functions missing \n \n
*	If autosuspend is disabled via the DCOP interface, the change is not set back to the 
*	applet menu (enable applet entry). There is already a dcop function to get current scheme and 
*	CPUFreq policy, but there is no function to change them.\n \n
*	\b Fix-comment: fixed  disableAutosuspend(), added missing functions. This bug partly effect 
*			sf.net bug #1483392. \n \n
* \li   Bug \b #177788 - TDEPowersave: autosuspend does not suspend after set time if dpms is on 
*			(also: (partial) sf.net bug #1483392) \n \n
*	If the timeout for autosuspend is longer than a timeout for a dpms state (standb/suspend/off) 
*	TDEPowersave suspend first if the user was as long as timout for current dpms state plus timout
*	for autosuspend was idle. If dpms state changed befor reached autosuspend timout all start
*	again from zero. The problem is: idleTime from XScreenSaver extension does not give (as descriped
*	in the code comment in the header) the complete user idle time but minus the timeout for the current
*	dpms state. \n \n
*	\b Fix-comment: Added a function to workaround this. This was also effected by \b bug \b #180000 (dpms
*			timeouts are additive, but they shouldn't)  \n \n
* \li   Bug \b #168838 - TDEPowersave: event for resumeFromSuspendToDisk displayed twice in knotify dialog \n \n
*       Fixed typo for resumeFromSuspendToRAM and corrected translations. \n \n
* \li   Bug \b #167296 - TDEPowersave: always show the last known remaining time in tooltip on APM if charge \n \n
*	Remove no longer needed (useless) checks from pdaemon. With this the time is set to -1 if charging and
*	if the powersave daemon reports UNKNOW for remaining time. \n \n
* \li   Bug \b #165462 - tdepowersave: knotify messages have a strange source \n \n
*	Fixed bad UTF in eventsrc from translation. \n \n
*
*
* \section fixed_bugs_sec_old All fixed bugs since tdepowersave-0.3.9-1 release until v0.6.0
*
* \li   Bug \b #134683 - TDEPowersave: Disables CPUs show as "Processor 2: 100% 734017 MHz" \n \n
*	Fixed update processor info on machines with more than one CPU/Core and/or no CPUFreq support.
*	Check now every two seconds for updates/changes in /sys and /proc. \n \n
* \li   Bug \b #121965 - TDEPowersave should not complain about missing powersaved \n \n
	Added new errormessage with checkbox to disable the message. \n \n
* \li   Bug \b #116440 - TDEPowersave: missing space in minute field in several languages [de,fr,it,pt_BR] \n
* \li   Bug \b #116439 - TDEPowersave: not update translation files [sv, tr, uk, sk, ru] \n
* \li   Bug \b #116438 - TDEPowersave: missing Polish translation file \n
* \li   Bug \b #116353 - TDEPowersave: ooopps, my desktop comp is "Charging" [KDE; Hungarian]. \n
* \li   Bug \b #116079 - TDEPowersave: missing translation in the suspend progress dialog \n \n
*	If machine suspend TDEPowersave display a suspend progress dialog. The messages in the dialog are 
*	not translated, also if there are translations in the po files. \n
*	Fix: The related messages come from powersave scripts and only start with the translated strings 
*	from the po files. Added function to parse and replace them against translated messages. \n \n
* \li   Bug \b #116079 - TDEPowersave: missing translation in the suspend progress dialog \n
* \li   Bug \b #115903 - TDEPowersave: menu entry "set active scheme" visible if powersave is stopped \n
* \li   Bug \b #115914 - TDEPowersave: problems with edit blacklist dialog with bigger fonts \n \n
*	The dialog for edit blacklist is not correct resized for bigger fonts. There are also some overlays
*	of some widgets in the dialog. \n \n
* \li   Bug \b #115584 - TDEPowersave displays warning twice when powersave shuts down \n
* \li   Bug \b #78953 - TDEPowersave: does not start at all (beta1, NLD9)\n \n
*	Added new option --force-acpi-check to dektop file and added a new file for autostart, to force
*	start and recheck for acpi on a machine where acpi ckeck failed at the first time. \n \n
* \li   Bug \b #95250 - TDEPowersave has no online help. \n
* \li   Bug \b #106177 - TDEPowersave: Show again the cpuinfo_cur_freq in tooltip. \n \n
*	TDEPowersave currently does not display the cpu freqency in the tooltip. \n \n
* \li   Bug \b #113559 - TDEPowersave: only one autosuspend. \n \n
*	TDEPowersave make only one autosuspend. After resume you must restart TDEPowersave for the next autosuspend. \n \n
* \li   Bug \b #105555 - TDEPowersave: Patch against ugly disabled icons. \n \n
*	Attached patch is against ugly (=all grey) icons on disabled buttons within TDEPowerSave dialogs. \n \n
* \li   Bug \b #104382 - SIGSEGV in TDEPowersave. \n \n
*	When starting YaST Powermanagement module from the context menu of TDEPowersave's tray, the application exits 
*	with a SEGV. (fixed also some file descriptor leaks) \n \n
* \li   Bug \b #104603 - tdepowersave says "Battery is chargin" - even if I run on battery. \n
* \li   Bug \b #104445 - tdepowersave: Suspend only possible if power is connected. \n \n
*	As long as power is connected, could suspend via tdepowersave but as soon as plug oput the cable, the menu 
*	entries are greyed out. \n \n
* \li   Bug \b #95279 -  tdepowersave progress bar popup does not handle "close" event. \n \n
*	If the progressbar popup does not get closed by a "101%"-event, it does never
*	close. If you close it via the window manager, tdepowersave never opens a popup again.
*	Fix: Now the suspend/progress dialog is Qt::WDestructiveClose and TDEPowersave connect to the 
*	destroyed() signal of the dialog \n \n
* \li	Bug \b #82880 - KDE: KMessageBox::error not on top since KDE 3.4 \n \n
*	All TDEPowersave error messages are not on the top, and popup in the background. \n \n
* \li	Bug \b #81681 - tdepowersave: progress shown below active window \n \n
*	If you suspend with powersave (e.g. powersave -U or Fn-keys) the suspend dialog is not on top level. \n \n
* \li	Bug \b #73805 - TDEPowersave files descriptor leak \n \n
*	Bug in tdepowersave: If tdepowersave can't access /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed the
*	open filedescriptor is never closed. \n \n
*	And: The update_info_cpufreq_speed_changed isn't set in all cases of the function. So could it happen that 
*	tdepowersave display wrong CPU Freq. \n \n
* \li	Bug \b #73810 - TDEPowersave ignore screensaver/dpms settings under gnome/xscreensaver \n \n
*	If you use GNOME and have a scheme setting where 'Enable specific screensaver settings' or 'Enable specific 
*	display power management' is not enabled and you change from a scheme where it is, the settings are ignored 
*	and not set back to user default. Same Problem on exit (selected by the user): tdepowersave don't set 
*	back to usersettings. \n \n
* \li   Bug \b #72939 - tdepowersave should set the KDE screensaver and dpms settings back if quit \n \n
*	At the moment TDEPowersave don't set the KDE screensaver and dpms settings back on exit if changed trough 
*	the scheme settings. This should be fixed. I think its enough to reset the settings in _quit() and not in 
*	the destructor, because them need only to reset if the user exit tdepowersave and not if the user logoff from 
*	KDE. \n \n
*	\b Comment: Problem also: tdepowersave try to set KDE settings if scheme changed also if KDE isn't runnig 
*	(e.g. GNOME). \n \n
* \li	Bug \b #72846 - passive-popups are not sufficient for tdepowersave \n \n
*	Almost everything that is signalled through tdepowersave popups now is important, so passive popups that 
*	disappear after a short time are nut sufficient for this task. \n \n
*	\b FIX-Comment:  Now the user can choose between KPassivPopup and KMessageBox be change configure variable 
*	in tdepowersaverc by hand. Default is KBessageBox. \n \n
* \li	Bug \b #71955 - not set the schemesettings if user changed them via configure dialog \n \n
*	If the user change the scheme or/and general settings of tdepowersave trough the configure dialog tdepowersave 
*	set this settings first if there is a scheme change. \n \n
* \li 	Bug \b #71192 - wrong enabled items in configure dialog if DPMS diabled \n \n
*	If you disable in the tdepowersave configure dialog DPMS, all work correct and the textlabel and spinboxes 
*	for the DPMS settings get disabled. But if you change a scheme or restart the configure dialog them are 
*	enabled also if DPMS is diabled. \n \n
* \li	Bug \b #71016 - tdepowersave never update the menu if powersaved not running on start \n \n
*	If you start tdepowersave (v0.3.10-6) without a running powersaved the user get no warning message. If you 
*	start powersaved later tdepowersave don't register that and never update the menu. \n  \n
* \li	Bug \b #66662 - kde screensaver disable problem  \n \n
*	TDEpowersave overwrite the settings of the KDE Controlcenter. If the user select there 'disable screensaver'
*	tdepowersave ignore this settings on start or if a scheme is changed depending on the global settings of 
*	powersave. The screensaver settings should be configurable by the user and should not depending on 'root' 
*	settings. \n \n
*	For more informations about the solution take a look at the \ref changelog . \n \n
* \li   Bugs \b #66502 and \b #66652 -  tdepowersave icon shows empty batteries on non-laptop \n \n
*	" ... The tools panel in kde contains a tdepowersave icon. For my workstation, which is 
*	definitly to heavy to be a laptop, it shows empty batteries, next to a mains 
*	connector. The connector is fine, but the batteries symbol should not be there. ..." \n \n
*	\b Comment: Also a problem with the tooltip. The problem: powersave have the right status of AC-Adapter 
*	within powersave (tested on commandline) but send a wrong value to the clients/over the libary. \n \n
*
* From now we use bugnumbers from the Novell Bugzilla, since the SuSE Bugzilla is moved and merged to the 
* Novell Bugzilla.
*
* \li	Bugzilla \b #49845 - xscreensaver under KDE ignored [from screen.cpp] \n \n
*	If we use Xscreensaver under KDE we don't get any information about this.
*	The Problem is the function \ref screen::checkScreenSaverStatus() . We don't check
*	for the XScreensaver, because we jump out of the KScreensaver-block. \n \n
* \li   Bugzilla \b #49844 - 'disable screensaver' - 'overwritten' by scheme if AC removed  [from tdepowersave.cpp] \n \n
*	Interaction between mplayer and tdepowersave if AC removed during the enterprise.
*	This is the same problem, if 'disable screensaver' in the menu is activated and AC removed 
*	or powersave change the scheme to 'powersave'. It's better to ignore the 'AC off' for the
*	screensaver if user set 'disable screensaver'. \n \n
* \li	Bugzilla \b #49632 - wrong path in message if powersaved not running [from tdepowersave.cpp] \n \n
*	There is an error in the message, which pop-up if powersave is stopped: \n
*	"The powersave daemon is not running. Starting it will improve performance: /usr/sbin/rcpowersave 
*	start". \n This is the wrong path. It must mean: /usr/sbin/rcpowersaved . Must be fix in the code and 
*	the translation-files. \n \n
* \li	Bugzilla \b #49445 - tdepowersave: empty cs-translation-file  \n \n
*	The czech translation don't work (no translation, tdepowersave only with english text) because of empty 
*	cs.po-file in the source. The file is empty in the cvs-tree since SUSE 9.2 final, the reason is unknown.  \n \n
*
*/