Bug 316251 - ProcessTable.sgrd contains invalid XML code
Summary: ProcessTable.sgrd contains invalid XML code
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (show other bugs)
Version: 4.9.4
Platform: Ubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
: 324740 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-06 21:35 UTC by fava
Modified: 2023-02-07 03:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
the empty window (32.70 KB, image/jpeg)
2013-03-06 21:36 UTC, fava
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fava 2013-03-06 21:35:33 UTC
Hi to all.

It's a couple of days since I always get the following error message each time I try to open Ksysguard, no matters whether I try to launch it as normal or super user:

"Il file /home/superman/.kde/share/apps/ksysguard/ProcessTable.sgrd non contiene codice XML valido."
"Il file /home/superman/.kde/share/apps/ksysguard/SystemLoad2.sgrd non contiene codice XML valido."

then the Ksysguard window appears but the CPU, RAM and Disk sensors are not visible. Only the menu items are visible.
What can I do?
Thanks

Reproducible: Always

Steps to Reproduce:
1.just open ksysguard
2.
3.



A couple of days ago I've been following some instructions in order to clean the system. Those are the related links:
http://mauriziosiagri.wordpress.com/2012/10/24/clean-and-optimize-ubuntu-12-10-quantal-quetzal/

http://mauriziosiagri.wordpress.com/ubuntu/programmi-essenziali-per-ubuntu-12-04/
Comment 1 fava 2013-03-06 21:36:24 UTC
Created attachment 77815 [details]
the empty window
Comment 2 fava 2013-03-07 07:51:40 UTC
The problem persists also after updating the desktop environment to KDE 4.9.5
Comment 3 fava 2013-03-12 14:29:14 UTC
Still no feedback?
Comment 4 John Tapsell 2013-03-12 14:47:40 UTC
Please attach the two mentioned .sgrd files, then delete them on your system.  That should fix it for you.
Comment 5 Christoph Feck 2014-04-20 23:19:12 UTC
*** Bug 324740 has been marked as a duplicate of this bug. ***
Comment 6 Andrew Crouthamel 2018-11-11 04:32:15 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 7 Andrew Crouthamel 2018-11-21 04:33:28 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 8 Justin Zobel 2023-01-08 22:44:43 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 9 Bug Janitor Service 2023-01-23 05:04:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-02-07 03:55:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!