Process Table blinks all the time, showing the content only occasionally, and thus is unusable.
...
Steps to reproduce
Launch ksysguard.
Switch to the Process Table worksheet.
Screenshots
<!--
This is a comment.
Please fill in the required fields below.
The comments provide instructions on how to do so.
Note: You do not need to remove comments.
-->
## Basic information
- TDE version: R14.1.0
- Distribution: Debian GNU/Linux bookworm/sid
- Hardware: amd64
<!--
Use SL/* labels to set the severity level.
Please do not set a milestone.
-->
## Description
Process Table blinks all the time, showing the content only occasionally, and thus is unusable.
...
## Steps to reproduce
1. Launch ksysguard.
2. Switch to the Process Table worksheet.
## Screenshots
Uhm... works fine here, and it has done so for years.
What is the refresh rate of the worksheet for info? Have you tried removing the worksheet, add a new one and see if there is any difference?
Have you tried from a new user?
Uhm... works fine here, and it has done so for years.
What is the refresh rate of the worksheet for info? Have you tried removing the worksheet, add a new one and see if there is any difference?
Have you tried from a new user?
What is the refresh rate of the worksheet for info?
All the defaults (2 seconds, I suppose?)
Tried to enlarge to 10 seconds, still the same (actually, it obviously blinks several times per a second, much more frequent than the refresh rate).
I also checked if compositing is the culprit (I use Compiz), but it's the same under Openbox.
Have you tried removing the worksheet, add a new one and see if there is any difference?
Same in a new worksheet.
Have you tried from a new user?
Yes, added a test user to video and input groups, launched pure X with ksysguard, still blinks the same way.
> What is the refresh rate of the worksheet for info?
All the defaults (2 seconds, I suppose?)
Tried to enlarge to 10 seconds, still the same (actually, it obviously blinks several times per a second, much more frequent than the refresh rate).
I also checked if compositing is the culprit (I use Compiz), but it's the same under Openbox.
> Have you tried removing the worksheet, add a new one and see if there is any difference?
Same in a new worksheet.
> Have you tried from a new user?
Yes, added a test user to `video` and `input` groups, launched pure X with ksysguard, still blinks the same way.
This is definitely a weird one. I also use Debian bookworm and don't have anything like that.
Do you have an nvidia graphic card? Some users reported strange behaviors with old (legacy?) drivers.
Also it may be a good idea to ask on the user mailing lists if anyone has experienced something similar.
This is definitely a weird one. I also use Debian bookworm and don't have anything like that.
Do you have an nvidia graphic card? Some users reported strange behaviors with old (legacy?) drivers.
Also it may be a good idea to ask on the user mailing lists if anyone has experienced something similar.
Not sure what the cause of the issue could be, honestly.
Did it happened also with R14.0.13?
Does it happen both in Tree View mode and List Mode?
Does it happen also if you select a different entry in the top right combobox?
As I said, it may be good dropping an email to the user mailing list and see if anyone has any suggestion.
Not sure what the cause of the issue could be, honestly.
Did it happened also with R14.0.13?
Does it happen both in Tree View mode and List Mode?
Does it happen also if you select a different entry in the top right combobox?
As I said, it may be good dropping an email to the user [mailing list](https://www.trinitydesktop.org/mailinglist.php) and see if anyone has any suggestion.
Does it happen both in Tree View mode and List Mode?
Yes.
Does it happen also if you select a different entry in the top right combobox?
Yes, the frequency may change, but it still blinks.
As I said, it may be good dropping an email to the user mailing list and see if anyone has any suggestion.
I already did, but the message did not appear in the archive yet (is it pre-moderated?)
> Did it happened also with R14.0.13?
Don't know, I installed it just recently.
> Does it happen both in Tree View mode and List Mode?
Yes.
> Does it happen also if you select a different entry in the top right combobox?
Yes, the frequency may change, but it still blinks.
> As I said, it may be good dropping an email to the user mailing list and see if anyone has any suggestion.
I already did, but the message did not appear in the archive yet (is it pre-moderated?)
I already did, but the message did not appear in the archive yet (is it pre-moderated?)
New members are moderated, to reduce spams. Once a member is proven "genuine", then he will be set as non-moderated. But I didn't see any request for message approval in recent days. Did you send your message to this address? users@trinitydesktop.org
Thanks for the feedback.
> I already did, but the message did not appear in the archive yet (is it pre-moderated?)
New members are moderated, to reduce spams. Once a member is proven "genuine", then he will be set as non-moderated. But I didn't see any request for message approval in recent days. Did you send your message to this address? users@trinitydesktop.org
Uhm, no request for message approval has shown up.
Will check with @SlavekB later when he is awake to see if the message was discarded by the mail server for some reasons and let you know
Uhm, no request for message approval has shown up.
Will check with @SlavekB later when he is awake to see if the message was discarded by the mail server for some reasons and let you know
I suppose it may be related to MESA somehow. I already have another graphical glitch in dated software (compiz-reloaded) reproduced only on this hardware, and the developer suggested it may be related to MESA, but didn't dive any further as they're focused on Wayfire now.
I'll watch if upgrades would change anything when Bookworm is finally released and I transition to Trixie.
I suppose it may be related to MESA somehow. I already have another graphical glitch in dated software (compiz-reloaded) reproduced only on this hardware, and the developer suggested it may be related to MESA, but didn't dive any further as they're focused on Wayfire now.
I'll watch if upgrades would change anything when Bookworm is finally released and I transition to Trixie.
You could try removing the MESA lib and see if the problem goes away, at least it would give some more indication of whether the problem comes from there or not.
Btw, does it happen only with the listview in ksysguard or also with other listview (say konqueror in detail mode for example)? Trying to understand if it is a problem with the graphical widget or the application.
You could try removing the MESA lib and see if the problem goes away, at least it would give some more indication of whether the problem comes from there or not.
Btw, does it happen only with the listview in ksysguard or also with other listview (say konqueror in detail mode for example)? Trying to understand if it is a problem with the graphical widget or the application.
It would bring too much of a dependency breakage; anyway, MESA does not seem to be used by Qt3 at all, nothing is printed with LIBGL_DEBUG=verbose.
say konqueror in detail mode for example
Installed konqueror, no such problem there.
> You could try removing the MESA lib
It would bring too much of a dependency breakage; anyway, MESA does not seem to be used by Qt3 at all, nothing is printed with `LIBGL_DEBUG=verbose`.
> say konqueror in detail mode for example
Installed konqueror, no such problem there.
are you running a full TDE session or specific applications within a different DE?
EDIT: as I was surprised you had to install Konqueror, which is one of the base components and would always be there even in a minimal installation (tdebase only)
are you running a full TDE session or specific applications within a different DE?
EDIT: as I was surprised you had to install Konqueror, which is one of the base components and would always be there even in a minimal installation (tdebase only)
oh interesting setup. So plain bookworm or sid + X server + selected applications?
If you give me some basic info of your setup, I could try setting up a VM in the same way and see if I can reproduce the issue.
oh interesting setup. So plain bookworm or sid + X server + selected applications?
If you give me some basic info of your setup, I could try setting up a VM in the same way and see if I can reproduce the issue.
Just checked, it also happens with Xwayland, Xnest and Xephyr too, so it's barely related to video driver issues, I suppose.
I mentioned above a minimal setup on which this issue happens (X.Org + Openbox). Ran like this:
```
X -seat seat0 vt8 :2 &
DISPLAY=:2 openbox &
DISPLAY=:2 /opt/trinity/bin/ksysguard &
```
Just checked, it also happens with Xwayland, Xnest and Xephyr too, so it's barely related to video driver issues, I suppose.
Hi @bodqhrohro,
I have done a bullseye netinstall on a new VM, without any DE on it. Then installed xserver-xorg, openbox and ksysguard (plus required dependencies but excluding recommended ones).
After running
I see ksysguard running but continuously complaining that it lost connection to the host. Not sure if you did some other setup that I didn't.
Note that we are not running the starttde scripts, which does some required init.
which starts a full TDE session. Everything seems to work fine and ksysguard works fine without any flashing.
As a next step, I would recommend you to try doing the same and see if you still see the flashing in ksysguard or not.
Hi @bodqhrohro,
I have done a bullseye netinstall on a new VM, without any DE on it. Then installed xserver-xorg, openbox and ksysguard (plus required dependencies but excluding recommended ones).
After running
```
X -seat seat0 vt8 :2 &
DISPLAY=:2 openbox &
DISPLAY=:2 /opt/trinity/bin/ksysguard &
```
I see ksysguard running but continuously complaining that it lost connection to the host. Not sure if you did some other setup that I didn't.
Note that we are not running the `starttde` scripts, which does some required init.
I then install tdebase-trinity and run
```
X -seat seat0 vt8 :2 &
DISPLAY=:2 openbox &
DISPLAY=:2 /opt/trinity/bin/starttde &
```
which starts a full TDE session. Everything seems to work fine and ksysguard works fine without any flashing.
As a next step, I would recommend you to try doing the same and see if you still see the flashing in ksysguard or not.
Yes, it does not blink in a full TDE session, though it took a long time to display anything in the widget, around 10 seconds. The status bar also had placeholders like "88888 processes" during this time.
So it's intentionally dependent on TDE runtime?
Yes, it does not blink in a full TDE session, though it took a long time to display anything in the widget, around 10 seconds. The status bar also had placeholders like "88888 processes" during this time.
So it's intentionally dependent on TDE runtime?
Haven't checked the inner code of ksysguard, but I guess it may depends on DCOP server having been started, possibly some environment variable being properly set and perhaps more.
Btw, I saw the same 888888 in the status bar when I ran ksysguard on its own, out of a session. I reckon that happens when a connection with the backend is not established yet.
So where should we go from here with this issue? Leave open for (possibly) further investigation or simply close since ksysguard works fine within a proper session?
Haven't checked the inner code of ksysguard, but I guess it may depends on DCOP server having been started, possibly some environment variable being properly set and perhaps more.
Btw, I saw the same 888888 in the status bar when I ran ksysguard on its own, out of a session. I reckon that happens when a connection with the backend is not established yet.
So where should we go from here with this issue? Leave open for (possibly) further investigation or simply close since ksysguard works fine within a proper session?
I believe any DE applications should be able to be run outside of their alma mater (yup, including the components of GNOME Shell and Plasma Shell which I contempt for non-modularity since their very existence), so you know the answer ×D
I've seen the connection failures since the very beginning too, and it's really my bad to ignore them. I'll try to determine what does it require then, maybe it's a relatively easy fit to launch some daemons manually.
I believe any DE applications should be able to be run outside of their alma mater (yup, including the components of GNOME Shell and Plasma Shell which I contempt for non-modularity since their very existence), so you know the answer ×D
I've seen the connection failures since the very beginning too, and it's really my bad to ignore them. I'll try to determine what does it require then, maybe it's a relatively easy fit to launch some daemons manually.
Basic information
Description
Process Table blinks all the time, showing the content only occasionally, and thus is unusable.
...
Steps to reproduce
Screenshots
Uhm... works fine here, and it has done so for years.
What is the refresh rate of the worksheet for info? Have you tried removing the worksheet, add a new one and see if there is any difference?
Have you tried from a new user?
All the defaults (2 seconds, I suppose?)
Tried to enlarge to 10 seconds, still the same (actually, it obviously blinks several times per a second, much more frequent than the refresh rate).
I also checked if compositing is the culprit (I use Compiz), but it's the same under Openbox.
Same in a new worksheet.
Yes, added a test user to
videoandinputgroups, launched pure X with ksysguard, still blinks the same way.This is definitely a weird one. I also use Debian bookworm and don't have anything like that.
Do you have an nvidia graphic card? Some users reported strange behaviors with old (legacy?) drivers.
Also it may be a good idea to ask on the user mailing lists if anyone has experienced something similar.
Nope, amdgpu.
Not sure what the cause of the issue could be, honestly.
Did it happened also with R14.0.13?
Does it happen both in Tree View mode and List Mode?
Does it happen also if you select a different entry in the top right combobox?
As I said, it may be good dropping an email to the user mailing list and see if anyone has any suggestion.
Don't know, I installed it just recently.
Yes.
Yes, the frequency may change, but it still blinks.
I already did, but the message did not appear in the archive yet (is it pre-moderated?)
Thanks for the feedback.
New members are moderated, to reduce spams. Once a member is proven "genuine", then he will be set as non-moderated. But I didn't see any request for message approval in recent days. Did you send your message to this address? users@trinitydesktop.org
Yes.
Maybe try to send one more time, I can check whether there is a message being hold back
Done.
Uhm, no request for message approval has shown up.
Will check with @SlavekB later when he is awake to see if the message was discarded by the mail server for some reasons and let you know
I suppose it may be related to MESA somehow. I already have another graphical glitch in dated software (compiz-reloaded) reproduced only on this hardware, and the developer suggested it may be related to MESA, but didn't dive any further as they're focused on Wayfire now.
I'll watch if upgrades would change anything when Bookworm is finally released and I transition to Trixie.
You could try removing the MESA lib and see if the problem goes away, at least it would give some more indication of whether the problem comes from there or not.
Btw, does it happen only with the listview in ksysguard or also with other listview (say konqueror in detail mode for example)? Trying to understand if it is a problem with the graphical widget or the application.
Haven't got hold of Slavek yet
It would bring too much of a dependency breakage; anyway, MESA does not seem to be used by Qt3 at all, nothing is printed with
LIBGL_DEBUG=verbose.Installed konqueror, no such problem there.
are you running a full TDE session or specific applications within a different DE?
EDIT: as I was surprised you had to install Konqueror, which is one of the base components and would always be there even in a minimal installation (tdebase only)
I only installed ksysguard to try it, and I don't use a DE.
oh interesting setup. So plain bookworm or sid + X server + selected applications?
If you give me some basic info of your setup, I could try setting up a VM in the same way and see if I can reproduce the issue.
I mentioned above a minimal setup on which this issue happens (X.Org + Openbox). Ran like this:
Just checked, it also happens with Xwayland, Xnest and Xephyr too, so it's barely related to video driver issues, I suppose.
great thanks. I will try to find some time this weekend or next week to setup a VM like that and test
Hi @bodqhrohro,
I have done a bullseye netinstall on a new VM, without any DE on it. Then installed xserver-xorg, openbox and ksysguard (plus required dependencies but excluding recommended ones).
After running
I see ksysguard running but continuously complaining that it lost connection to the host. Not sure if you did some other setup that I didn't.
Note that we are not running the
starttdescripts, which does some required init.I then install tdebase-trinity and run
which starts a full TDE session. Everything seems to work fine and ksysguard works fine without any flashing.
As a next step, I would recommend you to try doing the same and see if you still see the flashing in ksysguard or not.
Yes, it does not blink in a full TDE session, though it took a long time to display anything in the widget, around 10 seconds. The status bar also had placeholders like "88888 processes" during this time.
So it's intentionally dependent on TDE runtime?
Haven't checked the inner code of ksysguard, but I guess it may depends on DCOP server having been started, possibly some environment variable being properly set and perhaps more.
Btw, I saw the same 888888 in the status bar when I ran ksysguard on its own, out of a session. I reckon that happens when a connection with the backend is not established yet.
So where should we go from here with this issue? Leave open for (possibly) further investigation or simply close since ksysguard works fine within a proper session?
I believe any DE applications should be able to be run outside of their alma mater (yup, including the components of GNOME Shell and Plasma Shell which I contempt for non-modularity since their very existence), so you know the answer ×D
I've seen the connection failures since the very beginning too, and it's really my bad to ignore them. I'll try to determine what does it require then, maybe it's a relatively easy fit to launch some daemons manually.
I agree, so let's keep the issue open.
If you figure out what is wrong/required to do, please update here and we take it from there.