Bug 207549 - Sometimes ~/.kde/share/apps/ksysguard/ProcessTable.sgrd might be corrupted.
Summary: Sometimes ~/.kde/share/apps/ksysguard/ProcessTable.sgrd might be corrupted.
Status: RESOLVED DUPLICATE of bug 218796
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: 4.7 and older
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-16 10:37 UTC by Torsten
Modified: 2019-03-12 19:50 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Torsten 2009-09-16 10:37:36 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    SuSE RPMs

If I start the process monitor (Systemmonitor Version 4 Unter KDE 4.2.4 (KDE 4.2.4) "release 2") a error message appears: Die Datei /home/torsten/.kde4/share/apps/ksysguard/ProcessTable.sgrd enthält kein gültiges XML.
Comment 1 Dario Andres 2009-09-16 15:22:06 UTC
- Does KSysguard starts anyways? (you see the window)
- If it starts, is some tab/graph missing?
- What is the message output you get if you launch it as "LANG=C ksysguard" ?
Thanks
Comment 2 Torsten 2009-09-16 17:42:50 UTC
Yes if I quit the message KSysguard starts. But only with a empty sheet. I  
send a picture with this message.
Only the line under the sheet show current data.

Torsten




Am 16.09.2009, 15:22 Uhr, schrieb Dario Andres
<andresbajotierra@gmail.com>:

> https://bugs.kde.org/show_bug.cgi?id=207549
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                             
> |andresbajotierra@gmail.com
>          Resolution|                            |WAITINGFORINFO
>
>
>
>
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>   
> 2009-09-16 15:22:06 ---
> - Does KSysguard starts anyways? (you see the window)
> - If it starts, is some tab/graph missing?
> - What is the message output you get if you launch it as "LANG=C  
> ksysguard" ?
> Thanks
>
Comment 3 Dario Andres 2009-09-16 20:11:06 UTC
I guess the message is saying something like that sheet file is invalid and therefore it can't be loaded properly; so the sheet/page is missing.
Comment 4 Roger Pixley 2012-09-01 23:05:29 UTC
I've gotten this error message as well. The only thing that I can submit as help was that my ~/.xsession-errors filled up the disk just prior to this. I deleted the offending error file and logged out and back in which gave me the error and no process table in ksysguard. Invoking the process table from krunner (or pressing ctrl+esc) works. The file ~/.kde/share/apps/ksysguard/ProcessTable.sgrd is size 0. Moving it returns the system monitor to normal. 

As an inquiry is that state indicative of any issues? If not perhaps recover by moving the invalid XML file to a backup and notifying the user something was wrong but fixed?
Comment 5 Andrew Crouthamel 2018-11-09 00:55:41 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-18 03:22:34 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Richard Llom 2019-03-12 19:50:46 UTC

*** This bug has been marked as a duplicate of bug 218796 ***