I have a duel boot laptop. if i boot it into f12, using kde, and pull out the power cord, i get a popup message telling me i've done so and the battery monitor icon changes. If i boot into f13, also kde, i get no indication at all when i pull out the cable. The home directory is shared between the two boots, so the configuration is the same.
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
Has anyone else seen this? Can anyone suggest how I can debug it?
Thanks,
Chris
Chris Rouch <chris.rouch <at> gmail.com> writes:
The home directory is shared between the two boots, so the configuration is the same.
Well, that may be the problem ... Unless you really have a specific reason to have a common home dir, I think you are asking for more or less unpredictability with both installations (even if they are f12 and f13 distros). You are going backwards and forwards (f12, f13) with your home configuration files.
Your distro installation and updates put a lot of config files in your home dir ( the dot files) and unless you install exactly the same version of every program there might be conflicts. Every time something changes in the behaviour of your machine, your ability to understand and debug it is diminished (newly downloaded packages ?, new/changed config files ?, forgot about .rpmsave, .rpmnew ?, etc).
Fedora is a fast moving dev environment. You yourself should not introduce additional uncertainty - you want to do some useful work with your machine on a daily basis, right ? JB
JB wrote:
The home directory is shared between the two boots, so the configuration is the same.
Well, that may be the problem ... Unless you really have a specific reason to have a common home dir, I think you are asking for more or less unpredictability with both installations (even if they are f12 and f13 distros). You are going backwards and forwards (f12, f13) with your home configuration files.
I completely disagree. It is far more sensible to have /home on a separate partition. It is up to Fedora to make sure that any config files that it (she?) places in /home are properly updated during installation of a new distribution.
I must say I have had no problem of this kind with recent Fedora distributions.
On Thu, 2010-07-29 at 12:47 +0200, Timothy Murphy wrote:
It is up to Fedora to make sure that any config files that it (she?) places in /home are properly updated during installation of a new distribution.
While I think it's fair to ask that Fedora 13 (and its apps) can read the configuration left behind by Fedora 12, and update it where needed. You can't really expect Fedora 12 (when someone is dual-booting) to be able to handle Fedora 13 configurations.
The prior messages certainly suggest that they're dual-booting, between releases, and not just updating.
For cases like that, I'd second the motion that you keep separate homespaces, so the two release's configuration are independent. Keep your own files in just one place, and provide a link to that directory, or directories, in the second.
On 07/29/2010 07:16 PM, Tim wrote:
While I think it's fair to ask that Fedora 13 (and its apps) can read the configuration left behind by Fedora 12, and update it where needed. You can't really expect Fedora 12 (when someone is dual-booting) to be able to handle Fedora 13 configurations.
The prior messages certainly suggest that they're dual-booting, between releases, and not just updating.
For cases like that, I'd second the motion that you keep separate homespaces, so the two release's configuration are independent. Keep your own files in just one place, and provide a link to that directory, or directories, in the second.
While I do agree with what you've said.... The one thing that hasn't been determined is if indeed the issue is the differences in settings between F12 and F13 and jumping between the 2 versions. The OP "thinks" it was working before the last update.
I suppose the first thing I would do is to create a new user on F13 and test under a clean F13 environment. I feel to do otherwise is jumping to conclusions.
On 29 July 2010 13:28, Ed Greshko Ed.Greshko@greshko.com wrote:
While I do agree with what you've said.... The one thing that hasn't been determined is if indeed the issue is the differences in settings between F12 and F13 and jumping between the 2 versions. The OP "thinks" it was working before the last update.
I suppose the first thing I would do is to create a new user on F13 and test under a clean F13 environment. I feel to do otherwise is jumping to conclusions.
Good idea. I created a new user, selected a kde session and logged in as that user. I did not change any configuration. The battery charge icon had a yellow lightning bolt indication mains power. I pulled the power lead, and nothing changed - no popup dialog, no change of icon.
Regards,
Chris
On 07/29/2010 07:41 PM, Chris Rouch wrote:
Good idea. I created a new user, selected a kde session and logged in as that user. I did not change any configuration. The battery charge icon had a yellow lightning bolt indication mains power. I pulled the power lead, and nothing changed - no popup dialog, no change of icon.
So, this would mean that it is a pure F13 problem. Since I don't have laptop running F13, or any other version of Fedora, I don't think I'll be of much help. :-(
But, I think that the acpid is used for this. So, I would check to make sure that it is indeed started and that no errors have been reported by it.
Other than that....I leave it to those more experienced in that area.
On Thu, 2010-07-29 at 19:28 +0800, Ed Greshko wrote:
On 07/29/2010 07:16 PM, Tim wrote:
While I think it's fair to ask that Fedora 13 (and its apps) can read the configuration left behind by Fedora 12, and update it where needed. You can't really expect Fedora 12 (when someone is dual-booting) to be able to handle Fedora 13 configurations.
The prior messages certainly suggest that they're dual-booting, between releases, and not just updating.
For cases like that, I'd second the motion that you keep separate homespaces, so the two release's configuration are independent. Keep your own files in just one place, and provide a link to that directory, or directories, in the second.
While I do agree with what you've said.... The one thing that hasn't been determined is if indeed the issue is the differences in settings between F12 and F13 and jumping between the 2 versions. The OP "thinks" it was working before the last update.
I suppose the first thing I would do is to create a new user on F13 and test under a clean F13 environment. I feel to do otherwise is jumping to conclusions.
It is generally true that different verions of Fedoraq have different versions of the configuration files. If not developers would be somewhat limited in what they can do. I would doubt that two versions of Fedora would have exactly the sam configuration files.
On 29 July 2010 12:27, JB jb.123abc@yahoo.com wrote:
Chris Rouch <chris.rouch <at> gmail.com> writes:
The home directory is shared between the two boots, so the configuration is the same.
Well, that may be the problem ... Unless you really have a specific reason to have a common home dir, I think you are asking for more or less unpredictability with both installations (even if they are f12 and f13 distros). You are going backwards and forwards (f12, f13) with your home configuration files.
Yes, but...
I was only intending to go forward, and not worry about backing up and restoring /home. I appreciate that upgrades from f13 may alter config files in such a way that f12 apps no longer understand them. In fact I only booted to f12 to confirm that it was an f13 problem (and not a problem with the laptop). And it still works under f12, but not under f13.
Your distro installation and updates put a lot of config files in your home dir ( the dot files) and unless you install exactly the same version of every program there might be conflicts. Every time something changes in the behaviour of your machine, your ability to understand and debug it is diminished (newly downloaded packages ?, new/changed config files ?, forgot about .rpmsave, .rpmnew ?, etc).
Fedora is a fast moving dev environment. You yourself should not introduce additional uncertainty - you want to do some useful work with your machine on a daily basis, right ? JB
i'd love to. unfortunately i have an nvidia card which doesn't work properly in f13 (neither with nouveau or proprietary drivers). and now power management has also failed for me. I really don't want to have to go back to f12, but right now I still need that option.
Regards,
Chris
Chris Rouch <chris.rouch <at> gmail.com> writes:
I have a duel boot laptop. if i boot it into f12, using kde, and pull out the power cord, i get a popup message telling me i've done so and the battery monitor icon changes. If i boot into f13, also kde, i get no indication at all when i pull out the cable. The home directory is shared between the two boots, so the configuration is the same.
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
Has anyone else seen this? Can anyone suggest how I can debug it?
Thanks,
Chris
Hi, I am on a Gnome desktop and so can not help you with KDE. But I think you should try Gnome as well (they can co-exist). You will get to know it (I am a convert from KDE myself) and at the same time see if your power and battery work correctly. Try it: # [root@localhost jb]# yum grouplist |grep -i gnome # yum groupinstall "GNOME Desktop Environment" JB
JB <jb.123abc <at> yahoo.com> writes:
Chris Rouch <chris.rouch <at> gmail.com> writes:
I have a duel boot laptop. if i boot it into f12, using kde, and pull out the power cord, i get a popup message telling me i've done so and the battery monitor icon changes. If i boot into f13, also kde, i get no indication at all when i pull out the cable. The home directory is shared between the two boots, so the configuration is the same.
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
Has anyone else seen this? Can anyone suggest how I can debug it?
Thanks,
Chris
Hi, I am on a Gnome desktop and so can not help you with KDE. But I think you should try Gnome as well (they can co-exist). You will get to know it (I am a convert from KDE myself) and at the same time see if your power and battery work correctly. Try it: # [root <at> localhost jb]# yum grouplist |grep -i gnome # yum groupinstall "GNOME Desktop Environment" JB
Hi, I have installed a fresh KDE desktop environment and without any changes in settings can confirm that power cord pull out and plug in change battery icon and display a popup message about the corresponding event. So it is about your machine and KDE.
Look at Applications-Settings-System Settings-Advanced tab-Power Management .
I repeat my invitation to a Gnome desktop - you will be glad you did it :-) . System-Preferences-Power Management .
JB
On 29 July 2010 16:32, JB jb.123abc@yahoo.com wrote:
JB <jb.123abc <at> yahoo.com> writes:
Chris Rouch <chris.rouch <at> gmail.com> writes:
I have a duel boot laptop. if i boot it into f12, using kde, and pull out the power cord, i get a popup message telling me i've done so and the battery monitor icon changes. If i boot into f13, also kde, i get no indication at all when i pull out the cable. The home directory is shared between the two boots, so the configuration is the same.
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
Has anyone else seen this? Can anyone suggest how I can debug it?
Thanks,
Chris
Hi, I am on a Gnome desktop and so can not help you with KDE. But I think you should try Gnome as well (they can co-exist). You will get to know it (I am a convert from KDE myself) and at the same time see if your power and battery work correctly. Try it: # [root <at> localhost jb]# yum grouplist |grep -i gnome # yum groupinstall "GNOME Desktop Environment" JB
Hi, I have installed a fresh KDE desktop environment and without any changes in settings can confirm that power cord pull out and plug in change battery icon and display a popup message about the corresponding event. So it is about your machine and KDE.
Look at Applications-Settings-System Settings-Advanced tab-Power Management .
Thanks for trying that. I'd already noticed that the laptop would not do anything when the lid was closed (i've raised a kacpi bug for this), so it's possible i mis-remembered seeing the power management ever working
I repeat my invitation to a Gnome desktop - you will be glad you did it :-) .
I'm going to try it, just to rule out the kde components. But i've used gnome before and was forced to junk it for fvwm when it became too bloated for my (old) laptop. i've never been tempted to try it again :-)
Regards,
Chris
On 08/01/2010 11:15 AM, Chris Rouch wrote:
.....snip ..... I'm going to try it, just to rule out the kde components. But i've used gnome before and was forced to junk it for fvwm when it became too bloated for my (old) laptop. i've never been tempted to try it again :-)
Regards,
Chris
Hi, Others have posted here that XFCE is a very lightwight window manager. You might try it to see if you gain any performance benefits from it.
On 1 August 2010 20:24, JD jd1008@gmail.com wrote:
On 08/01/2010 11:15 AM, Chris Rouch wrote:
.....snip ..... I'm going to try it, just to rule out the kde components. But i've used gnome before and was forced to junk it for fvwm when it became too bloated for my (old) laptop. i've never been tempted to try it again :-)
Regards,
Chris
Hi, Others have posted here that XFCE is a very lightwight window manager. You might try it to see if you gain any performance benefits from it.
I have xfce on my netbook - it works well enough there. But my current laptop has the resources for kde or gnome, so i'd prefer to stay put for the moment.
In any case, i installed gnome as suggested, created a new user and logged into a gnome session. Hey presto, the power management works as it should. so i logged out and logged in again as the new user but with kde and the power management failed. Logged out and in again to the gnome session and it worked again. By "worked" i mean the icon changed after a short time and an information dialog was displayed.
So I think this is a kde problem.
Regards,
Chris
Chris Rouch <chris.rouch <at> gmail.com> writes:
So I think this is a kde problem.
Hi, have you looked into these in KDE: computer-system settings-general-notifications-system notifications-applications event source selection -> scroll to PowerDevil select item e.g. AC adaptor plugged in check off below e.g. Show a message in a popup etc Apply button to save
The same is under: computer-system settings-advanced-power management- general settings- configure notifications
Now look into: computer-system settings-advanced-service manager-startup services check off PowerDevil Apply button to save
Finally: restart desktop to make sure that all services become available.
Other: [jb@localhost ~]$ ps aux |grep -i power root 1439 0.0 0.3 6028 2364 ? S Aug01 0:04 /usr/libexec/upowerd jb 6983 0.0 0.0 4312 736 pts/3 S+ 17:29 0:00 grep -i power
[jb@localhost ~]$ ps aux |grep -i pm root 11 0.0 0.0 0 0 ? S Aug01 0:00 [pm] jb 7012 0.0 0.1 4312 764 pts/4 S+ 17:31 0:00 grep -i pm
[jb@localhost ~]$ ps aux |grep -i acpi root 16 0.0 0.0 0 0 ? S Aug01 0:00 [kacpid] root 17 0.0 0.0 0 0 ? S Aug01 0:00 [kacpi_notify] root 18 0.0 0.0 0 0 ? S Aug01 0:00 [kacpi_hotplug] root 990 0.0 0.0 1972 556 ? Ss Aug01 0:00 /usr/sbin/acpid 68 1107 0.0 0.0 3908 740 ? S Aug01 0:00 /usr/libexec/hald-addon-acpi jb 7038 0.0 0.0 4312 736 pts/4 S+ 17:34 0:00 grep -i acpi
JB
On 07/29/2010 01:17 AM, Chris Rouch wrote:
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
The first thing you should try is probably to boot the oldest F13 kernel that you've got and see if the system's behavior is any different.
On both the older kernel and the new one, check the state of your batteries:
$ cat /proc/acpi/battery/BAT*/state
Record the results while you are on AC power and on battery power. There may be an ACPI bug in your system. You might also want to update the BIOS to see if that corrects the problem.
On Thu, 2010-07-29 at 15:16 -0700, Gordon Messmer wrote:
On 07/29/2010 01:17 AM, Chris Rouch wrote:
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
The first thing you should try is probably to boot the oldest F13 kernel that you've got and see if the system's behavior is any different.
On both the older kernel and the new one, check the state of your batteries:
$ cat /proc/acpi/battery/BAT*/state
Record the results while you are on AC power and on battery power. There may be an ACPI bug in your system. You might also want to update the BIOS to see if that corrects the problem.
Anyone looked at:
yet?
On 30 July 2010 00:16, Gordon Messmer yinyang@eburg.com wrote:
On 07/29/2010 01:17 AM, Chris Rouch wrote:
I think this was working for f13 too until the last time i applied updates, though it may just be that i didn't test it.
The first thing you should try is probably to boot the oldest F13 kernel that you've got and see if the system's behavior is any different.
On both the older kernel and the new one, check the state of your batteries:
$ cat /proc/acpi/battery/BAT*/state
Record the results while you are on AC power and on battery power. There may be an ACPI bug in your system. You might also want to update the BIOS to see if that corrects the problem.
That part seems to be working:
% cat /proc/acpi/battery/BAT*/state present: yes capacity state: ok charging state: charging present rate: 0 mA remaining capacity: 4318 mAh present voltage: 12533 mV
% cat /proc/acpi/battery/BAT*/state present: yes capacity state: ok charging state: discharging present rate: 0 mA remaining capacity: 4319 mAh present voltage: 12533 mV
Regards,
Chris
-
Aaron Konstam -
Ankur Sinha -
Chris Rouch -
Ed Greshko -
Gordon Messmer -
JB -
JD -
Tim -
Timothy Murphy