Bug 196405 - KDE battery monitor doesn't stay in notification area
Summary: KDE battery monitor doesn't stay in notification area
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-23 00:26 UTC by Donald Straney
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: FC5
Clone Of:
Environment:
Last Closed: 2006-06-23 12:37:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Donald Straney 2006-06-23 00:26:07 UTC
(I'm sorry if this is assigned to the wrong component, this is the closest as
far as I know)

I'm using KDE 3.5 with FC5 on a laptop, and I've noticed that the battery
monitor in the notification area disappears after first use.  When I started FC5
for the first time or logged into a new account, it appeared, but disappeared
after the next reboot.  Enabling or disabling the 'Restore last session' option
doesn't change anything, and pressing the 'Start battery monitor' button in the
'Laptop Battery' section of the KDE control center doesn't help either.  What
does work, however, is disabling the battery monitor (with a checkbox in the
same section of the control center, I'm not in FC5 right now and don't remember
the name), pressing 'Apply', re-enabling it, and pressing 'Apply' again.  The
battery monitor appears, but it's gone again after the next reboot.

I'm using kdelibs-3.5.1-2.3 and kdebase-3.5.1-5.  GNOME's battery monitor works
fine, so I think it's a problem with the specific program instead of the kernel
or HAL.  Any information I left out?

Comment 1 Than Ngo 2006-06-23 12:37:43 UTC
there's new KDE-3.5.3 in FC5-update since 1 week. The new version includes 
several fixes and the fix for this problem, too.

You should update to new KDE version please. Thanks


Note You need to log in before you can comment on or make changes to this bug.