Hi, For quite a while in my testing of OpenSUSE 10.2 (possibly ever since I started with alpha5, but I'm not sure), I've been seeing a KDE Crash alert for KPowersave every time I log in. I'm not sure what role this application plays in normal system operation. Nothing is overtly malfunctioning as far as I can tell. The system is an always-on desktop. % rpm -qa |egrep -i powersave kpowersave-0.7.1-6 powersave-0.15.10-3 powersave-libs-0.15.10-3 How should I deal with this? Should the application be running? If not, how do I get KDE to stop launching it when I log in? If it is important, how might I diagnose and repair the problem? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 10 December 2006 19:44, Randall R Schulz wrote:
Hi,
For quite a while in my testing of OpenSUSE 10.2 (possibly ever since I started with alpha5, but I'm not sure), I've been seeing a KDE Crash alert for KPowersave every time I log in.
I'm not sure what role this application plays in normal system operation. Nothing is overtly malfunctioning as far as I can tell.
I use it to "hibernate" my desktop system (suspend to disk). Takes about 30 s to shut down, and 45 s to startup. Very nice!
The system is an always-on desktop.
% rpm -qa |egrep -i powersave kpowersave-0.7.1-6 powersave-0.15.10-3 powersave-libs-0.15.10-3
Yup, have those too.
How should I deal with this? Should the application be running? If not, how do I get KDE to stop launching it when I log in? If it is important, how might I diagnose and repair the problem?
Hmm, might be an error in it's config file? Try logging out, renaming ~/.kde/share/config/kpowersaverc, and logging in again. KPowerSave's autostart is an option in its settings dialog. Right click on the plug in the system tray, choose Configure KPowersave, choose the "General Settings"-tab, "Autostart"-panel. You might want to try disable the autostart, quitting KPowersve, and starting it from a terminal. Maybe you get some useful messages. Cheers, Leen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Leen, On Sunday 10 December 2006 11:01, Leendert Meyer wrote:
On Sunday 10 December 2006 19:44, Randall R Schulz wrote:
Hi,
For quite a while in my testing of OpenSUSE 10.2 (possibly ever since I started with alpha5, but I'm not sure), I've been seeing a KDE Crash alert for KPowersave every time I log in.
I'm not sure what role this application plays in normal system operation. Nothing is overtly malfunctioning as far as I can tell.
I use it to "hibernate" my desktop system (suspend to disk). Takes about 30 s to shut down, and 45 s to startup. Very nice!
Since this system will be (in part) a server, it will remain an always-on system. It is by far the slowest system I've ever used as measured by the time from power-on (or reset) to KDE prompt. Which is ironic, since it's by far the most high-performing system I've ever owned.
The system is an always-on desktop.
% rpm -qa |egrep -i powersave kpowersave-0.7.1-6 powersave-0.15.10-3 powersave-libs-0.15.10-3
Yup, have those too.
How should I deal with this? Should the application be running? If not, how do I get KDE to stop launching it when I log in? If it is important, how might I diagnose and repair the problem?
Hmm, might be an error in it's config file? Try logging out, renaming ~/.kde/share/config/kpowersaverc, and logging in again.
The current contents (as I'm logged in) are pretty simple: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- [General] AlreadyStarted=true [infoDialog] dbusNotRunning=false -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
KPowerSave's autostart is an option in its settings dialog. Right click on the plug in the system tray, choose Configure KPowersave, choose the "General Settings"-tab, "Autostart"-panel.
Of course, since it crashes upon start-up, that tray icon and generally all KPowersave functionality presented via its GUI is unavailable! Attempting to start it via the KDE menu produces the same crash, instantaneously. I then removed ~/.kde/share/config/kpowersaverc and launched KPowersave again, but the results were the same. In fact, it did not get far enough to re-create the kpowersaverc file.
You might want to try disable the autostart, quitting KPowersve, and starting it from a terminal. Maybe you get some useful messages.
As above, nothing that requires KPowersave to be running is an option, as things stand.
Cheers,
Leen
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 10 December 2006 10:17, Randall R Schulz wrote:
Since this system will be (in part) a server, it will remain an always-on system. It is by far the slowest system I've ever used as measured by the time from power-on (or reset) to KDE prompt. Which is ironic, since it's by far the most high-performing system I've ever owned.
There are time when KDE boots that it takes forever. I've tracked these down to it trying to restart tasks that were running as of the last shutdown. You can often see these in top with the "c" command running with big fuzzy command tails: kalarm -session 1070656e0000115825652900000040960012_1165738664_883947 Some times you will see dozens of these try to restart because they don't always get cleared properly and hang around forever, trying to restart at each boot, sometimes failing silently, other times running doing nothing but in any case taking a lot of time on bootup. Sometimes you can cure this by manually shutting down every task you don't need and then checking top again to make sure there is nothing in there you can't explain. Then log out of the kde session. (Be sure to log out, not shutdown or anything else). You can then log back in again and look for more of these. Other times, you just have to look in /home/<user>/.kde/share/config/session and delete anything you don't want running on next boot. Also maker sure there are not suspended KDE sessions for other users (resulting from switching users). I know this part is not helpful: Why would you run kde on a server? Why not just runlevel 3? -- _____________________________________ John Andersen
Randall R Schulz wrote:
Hi,
For quite a while in my testing of OpenSUSE 10.2 (possibly ever since I started with alpha5, but I'm not sure), I've been seeing a KDE Crash alert for KPowersave every time I log in.
I'm not sure what role this application plays in normal system operation. Nothing is overtly malfunctioning as far as I can tell.
Its help says: "KPowersave is a utility used to set power consumption and conservation options." It is essential for mobile users, I usually disable it for desktop computers.
The system is an always-on desktop.
% rpm -qa |egrep -i powersave kpowersave-0.7.1-6 powersave-0.15.10-3 powersave-libs-0.15.10-3
How should I deal with this? Should the application be running? If not, how do I get KDE to stop launching it when I log in?
Edit ~/.kde/share/config/kpowersaverc and set Autostart to "false"
If it is important, how might I diagnose and repair the problem?
Try to get a coredump. -- Adi Pircalabu -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 10 December 2006 11:14, Adi Pircalabu wrote:
Randall R Schulz wrote:
Hi,
For quite a while in my testing of OpenSUSE 10.2 (possibly ever since I started with alpha5, but I'm not sure), I've been seeing a KDE Crash alert for KPowersave every time I log in.
I'm not sure what role this application plays in normal system operation. Nothing is overtly malfunctioning as far as I can tell.
Its help says: "KPowersave is a utility used to set power consumption and conservation options." It is essential for mobile users, I usually disable it for desktop computers.
The system is an always-on desktop.
% rpm -qa |egrep -i powersave kpowersave-0.7.1-6 powersave-0.15.10-3 powersave-libs-0.15.10-3
How should I deal with this? Should the application be running? If not, how do I get KDE to stop launching it when I log in?
Edit ~/.kde/share/config/kpowersaverc and set Autostart to "false"
That setting was not present, and as I said in my reply to Leen Meyer, KPowersave doesn't appear to get as far as reading its rc file before crashing. Something else is starting it and that's where I'm going to have effect a change. The only file anywhere in the ~/.kde hierarchy that mentions KPowersave in any form (besides its own rc file) is .../share/config/kickerrc. This file contains two seemingly relevant entries: 1) The string "kde-kpowersave" appears among a large comma-separated list in the setting FirstSeenApps from section [menus]. 2) The string "/opt/kde3/share/applications/kde/kpowersave.desktop" appears in the setting RecentAppsStat, also in the [menus] section.
If it is important, how might I diagnose and repair the problem?
Try to get a coredump.
I have the stack back-trace from the KDE Crash Handler, but since this is not a debug version of the program, there are no symbols, just addresses: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- System configuration startup check disabled. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231242752 (LWP 4978)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #9 0xb673c197 in dbus_threads_init () from /usr/lib/libdbus-1.so.3 #10 0xb6729622 in dbus_connection_send_with_reply () from /usr/lib/libdbus-1.so.3 #11 0xb67298ea in dbus_connection_send_with_reply_and_block () from /usr/lib/libdbus-1.so.3 #12 0xb6763163 in libhal_device_property_exists () from /usr/lib/libhal.so.1 #13 0xb679f5a0 in dbusHAL::halGetPropertyString () from /opt/kde3/lib/libkdeinit_kpowersave.so #14 0xb67ab4dc in HardwareInfo::checkPowermanagement () from /opt/kde3/lib/libkdeinit_kpowersave.so #15 0xb67aed90 in HardwareInfo::HardwareInfo () from /opt/kde3/lib/libkdeinit_kpowersave.so #16 0xb67c095f in kpowersave::kpowersave () from /opt/kde3/lib/libkdeinit_kpowersave.so #17 0xb67c3c9b in kdemain () from /opt/kde3/lib/libkdeinit_kpowersave.so #18 0xb7f47764 in kdeinitmain () from /opt/kde3/lib/kde3/kpowersave.so #19 0x0804e33f in QGList::~QGList () #20 0x00000001 in ?? () #21 0x0807e5b0 in ?? () #22 0x00000001 in ?? () #23 0x00000000 in ?? () -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
--
Adi Pircalabu
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Sunday 10 December 2006 11:14, Adi Pircalabu wrote:
Randall R Schulz wrote:
Hi,
For quite a while in my testing of OpenSUSE 10.2 (possibly ever since I started with alpha5, but I'm not sure), I've been seeing a KDE Crash alert for KPowersave every time I log in.
I'm not sure what role this application plays in normal system operation. Nothing is overtly malfunctioning as far as I can tell. Its help says: "KPowersave is a utility used to set power consumption and conservation options." It is essential for mobile users, I usually disable it for desktop computers.
The system is an always-on desktop.
% rpm -qa |egrep -i powersave kpowersave-0.7.1-6 powersave-0.15.10-3 powersave-libs-0.15.10-3
How should I deal with this? Should the application be running? If not, how do I get KDE to stop launching it when I log in? Edit ~/.kde/share/config/kpowersaverc and set Autostart to "false"
That setting was not present, and as I said in my reply to Leen Meyer, KPowersave doesn't appear to get as far as reading its rc file before crashing. Something else is starting it and that's where I'm going to have effect a change.
The only file anywhere in the ~/.kde hierarchy that mentions KPowersave in any form (besides its own rc file) is .../share/config/kickerrc. This file contains two seemingly relevant entries:
I have the stack back-trace from the KDE Crash Handler, but since this is not a debug version of the program, there are no symbols, just addresses: [...] (no debugging symbols found) [KCrash handler] #9 0xb673c197 in dbus_threads_init () from /usr/lib/libdbus-1.so.3 #10 0xb6729622 in dbus_connection_send_with_reply () from /usr/lib/libdbus-1.so.3 #11 0xb67298ea in dbus_connection_send_with_reply_and_block () from /usr/lib/libdbus-1.so.3 #12 0xb6763163 in libhal_device_property_exists () from /usr/lib/libhal.so.1 #13 0xb679f5a0 in dbusHAL::halGetPropertyString () from /opt/kde3/lib/libkdeinit_kpowersave.so #14 0xb67ab4dc in HardwareInfo::checkPowermanagement () from /opt/kde3/lib/libkdeinit_kpowersave.so #15 0xb67aed90 in HardwareInfo::HardwareInfo () from /opt/kde3/lib/libkdeinit_kpowersave.so #16 0xb67c095f in kpowersave::kpowersave () from /opt/kde3/lib/libkdeinit_kpowersave.so #17 0xb67c3c9b in kdemain () from /opt/kde3/lib/libkdeinit_kpowersave.so #18 0xb7f47764 in kdeinitmain () from /opt/kde3/lib/kde3/kpowersave.so #19 0x0804e33f in QGList::~QGList () #20 0x00000001 in ?? () #21 0x0807e5b0 in ?? () #22 0x00000001 in ?? () #23 0x00000000 in ?? ()
Create a new user and log in as that user. Does it still crash? What versions of hal/dbus packages do you have? Did you install updated versions of these packages from 3rd-party repos? The interface may change between versions major versions. Can you post the output from "rpm -qa \*hal\* \*dbus\*"? You can also consider posting to Novell's Bugzilla, at least for tracking purposes. -- Adi Pircalabu -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Adi Pircalabu
-
John Andersen
-
Leendert Meyer
-
Randall R Schulz