Window Selection Issue, Electrical or Other Issue?

I am having certain problems when using my current system.

I do not know whether they are hardware based on software based.

This is currently happening in qubes. While typing, my system will jump from one window to another. For example, I was using the terminal for sys-whonix and the system jumped to my Tor browser window and suddenly I was tying in that.

Also, while typing in this, my cursor (in this text field) jumps over to similar topics.

I am also having this problem while using my other operating system, which is a linux system on the same machine that uses gnome. It happens a lot, sometimes with random programs opening up that I have not even requested to open.

Please do not move this to the “help I think I’ve been hacked” section. This seems more likely electrical in nature, like damaged chips or something.

I have a possibly damaged touchscreen and may need to get that replaced. (There are some parts of the screen that look slightly damaged.) But even if the touchscreen had a problem, I wouldn’t expect programs to run on their own. I am also having unusual keyboard issues, like things turn into CAPITAL LETTERS suddenly.

I am wondering if I shorted something out when I cleaned a fan inside the machine. I tried to be careful, but this seems like an electrical issue.

At first, when this started happening, I did think i was being hacked.

The only huge risk in Qubes is that I use a github utility to control the WinMax2 fans, win-max-2-fan-control and I have that in dom0. (That’s probably a huge mistake, and I can use a VM PVH Qube with the fans attached and the utility.) But the code is public, I doubt that code is what is doing this. (Sorry Joanna! and everyone else at Qubes. They’d be so upset. It was lazy and stupid. But the code is available and doubt that this particular piece of software is what is causing all this.)

Also, strangely, these errors seems to happen a lot less when I turn the internet off. They were happening all the time while writing this, then I turned my Internet off, and suddenly the problems have stopped. I also did replace my router firmware, and it hasn’t stopped any of this.

It’s also possible that the machine I got had compromised firmware or was compromised by a USB driver. I am not running the latest bios firmware because of concerns that it’s not compatible with Qubes, but perhaps that’s the problem. I’ve heard of multiple people complain online that the bios upgrade bricked their winmax or made things less usable. I have a hard time believing this is a driver issue.

This is also happening so much, it’s hard to believe it’s just a regular hacker because I don’t think a regular hacker would have that much time to target me. I think this is much more likely to be hardware. Then again, I can’t rule out a skilled hacker is doing this. I have made enemies on occasion. I don’t think they are after me, however, and it would be hard for them to be after me by hacking qubes. Some of the people I’ve met in my life are very sophisticated with computers and would be able to attack a hardened system. I have also shared controversial views online of a political nature in a very outspoken way that could be upsetting to some. I don’t really do anything that important enough to be targeted by a nation-state, likely, although I sometimes wonder if this is something automatic happening and somehow some system keeps finding me. I have enough somewhat unique network characteristics that a sophisticated adversary with access to the network infrastructure could possibly guess that it’s me over and over, despite using certain techniques to try to protect myself.

I’m not sure what to think of all of this. I am considering moving to a RISC system with Debian so I am least am less concerned about chip-level exploits.

Am I over-reacting to this? The sys-whonix terminal was open and the Tor browser window was open when it kept switching from the sys-whionix terminal to the tor browser window and then it kept making it hard for me to type this until I disconnected the Internet, then none of the jumping mouse pointer and changes in windows kept happening. I am going to reconnect to post this.

I wish I knew what all of this was. I am not a wealthy person and buying another machine to try to figure this out may be a mistake if it’s a firmware issue. I also have another hardened device that may have had some similar issues.

This seemed to happen more sometime after I got the device and installed other upgraded components. This may not be a hack.

I also don’t know the smartest way to proceed. If I do nothing, I may be a deer waiting in the headlights, and this could be a real hack with the hacker waiting to do something harmful to me somehow, such as commit a financial crime against me. This could also be something where some country thinks statements I’ve said online are bad and I’m at risk in an even worse way, although so many people say controversial stuff online or political views, it seems like very improbable.

1 Like

Does it also happen if you unplug all peripherals and especially the power supply (assuming that it’s ungrounded), and run on battery? Or maybe there could be another cause for static electricity buildup, e.g. from a carpet? If you have an anti-static mat + wristband you could rule that out.

1 Like

Yes, it does happen with no peripherals and on battery.

I am wondering if it could be a damaged touchscreen and the touchscreen being damaged is leading to the system thinking there are presses that aren’t there.

If it’s not that, then someone is hacking me remotely through my router, but it seems so unlikely.

I even thought it could be PSP in the chipset being controlled with a different router (like PSP staying connected to an open WiFi) and so I reduce the power to the WiFi by remove the power lines to the WiFi internally, but it still happens. So I’ve ruled that out.

It’s like a hidden mouse is being moved around and occasionally selecting part of the screen.

The only thing that doesn’t fit with this is that programs are opening up on their own too. The problems happen both in Qubes and the other gnome-based linux I have on the system, but programs have not opened on their own in Qubes.

I run Waydroid on the Gnome-linux system and one of the strange thing that happened was the camera for that opened, and there’s not even an icon for that.

I have also seen another device on my network have issues too, but I’m not sure what it is. I’ve even thought that it could be malicious packet injection someone injection into the vpn I’m using.

The problems tends to not happen when I am not connect to the Internet.

I could backup all my data and reinstall everything, but that takes so long to do.

I don’t think it’s static.

1 Like

I doubt that it will help but I have seen phantom mouse movement/clicks
from a damaged touchscreen. Your descriptions sound very familiar.
I doubt that reinstalling on the same machine will help.
Obviously you should have full backups of your data in any case -
whether from the Qubes Backup, or some other (better) backup tool. Dont
neglect this.

2 Likes

Okay, then replace your hardware.

1 Like

Have you tried deactivating the broken touchscreen? The “touch” part, not the “screen” part :wink:

I’ve never had to do that but I guess I’d look for (in this order):

  • a separate digitizer cable to disconnect
  • a BIOS option to disable
  • a kernel module to blacklist
  • a udev device to make libinput ignore
3 Likes

oh that’s a great idea. i could find a way to disable to touch option and just see if that’s what’s causing this.

1 Like

sorry, i didn’t mean it like that. i don’t know what this is.

1 Like

I tried this using a command line in terminal, just disabling it based on xinput and then evtest

most of the weirdness stopped and i thought i was fine. but then the monitor brightness level suddenly went from 100% to 50% and I didn’t do anything, nothing changed, and I wasn’t touching the system.

not sure what to think of that

1 Like

i hope you are right. i used evtest to shut off the touchscreen part and the cursor mostly stopped going all over, but then the screen brightness suddenly changed when i didn’t touch it

if it was a hacker, they would be able to see everything i typed, including evtest, so they might have just temporarily stopped. i had thought the problem had stopped before weeks ago… but then it started again suddenly prior to posting about it. could just be another “don’t worry, the problem is over” while a hacker lurks. still thinking it’s more likely electrical, but i don’t know.

it may just be more screen related stuff or not

1 Like

Sounds like (at least) the “screen” part of the touch screen is broken too. If you have an external monitor, you could try using that and fully disconnecting the internal screen+digitizer cable. Maybe the rest of the hardware is still okay.

1 Like

so i am currently dual booting (i know, stupid choices), and this is on the non-qubes distro.

how would a broken screen lead the operating system to turn the brightness/contrast way down?

oh, i’ve looked at this more. i have a power saver mode that dims the screen. this is probably what happened.

i think this issue is resolved. it is electrical almost certainly, not a hack, caused by a screen issue

1 Like

This was really helpful and I didn’t know whether to mark you as the solution or unman. I ended up marking unman as the solution since his response led to me investigate it more, but your suggestion really helped. I ended up using xinput and then evtest to send the touchscreen to null and then the problem stopped.

2 Likes

what was marked as a solution is no longer the solution

so the problem happened again while I was not connected to the Internet, and my wifi router was off

my cursor started blinking, it would be really hard to enter text, it opened up “cheese” and then would select unusual areas

i then did manage to run sudo evtest --grab /dev/input/event16 >> /dev/null to block the touchscreen

but it kept happening

this command, which normally blocked the touchscreen, also didn’t seem totally block it for whatever reason. when i pressed workspaces or applications, it would show a toolbar at the bottom with a list of running applications (i don’t normally use a toolbar at the bottom).

it also continues even after I put it in the microwave would i think would block radio frequencies at least partially even if this were a firmware backdoor allowing wireless connections despite the software turning it off (like if i were being hacked through firmware from another router that was on nearby). so most likely this occurred without an internet connection on at the time.

i did manage to run system monitor

so this happened while running Pop! OS instead of Qubes. I am still dual-booting for now. But a similar problem as happened in Qubes.

So I ran system monitor in Pop! OS, then was somehow able to video capture the screen.

the main things that is going on that is strange is something called

“gjs” is taking up about 130 MB of RAM and also taking up about 5-10% of my system processes, which is much higher than usual (there are normally 3 copies of gjs and they take up 0% of system processes)

this is weird because: 1) i was not doing anything when the error started. i woke up my computer and it immediately started happening

  1. there was almost nothing running except background programs i normally run

  2. nothing was connected to the internet and so most likely this is either persistent malware or some other technical problem rather than an internet based intrusion

  3. once again it seemed to open up an app and the app it opened was Cheese

I am running a Win Max 2. The only things I put in both dom0 and Pop! OS are RyzenAdj and win-max-2-fan-control, both build from github after cloning

I had commented out win-max-2-fan-control after this has started to happen.

I put both of those in dom0 because the system runs too hot without them and xenpm isn’t good enough at lowering processing and increasing the fan to keep temperatures at acceptable levels.

i recorded for about 10 minutes, getting a somewhat better understanding of the problem. i was unable to resize the system monitor window during this time, so i can see disk read, but not disk write. when my system gets like this, it seems like someone is pressing keys constantly and it’s doing something to make it harder for me to type, almost like an invisible buffer overflow attack, but probably not that.

i’m not a hacker and only know vague terms, not how things actually work.

i am not sure if i should share the system-monitor video in this forum, as it does show a lot about the programs i use. (in other words, if someone is actually trying to attack me, like if this is a targeted attack, which seems incredibly unlikely, then i’d be showing them a lot of attack surfaces)

if anyone trusted on qubes wants me to share it (it’s just a webm video of the desktop) i’d send it, or if multiple people here think i am over-reacting about being concerned about sharing lots of attack surface in a forum, then perhaps i should just post it

i have git cloned a lot of stuff and compiled it, including stuff that could be questionable. i know github has been an attack vector for some malware with fake starts and things like that.

it’s also possible this is still an electrical issue and the electrical issue is causing gjs to go into hyperdrive.

also, i have multiple copies of gjs running and know the process id of the one that started using huge amounts of resources. but i don’t know what it’s linked with or really how gjs works.

i also should add that there have been multiple times when this problem has resulted in the camera being opened.

i am starting to think it’s more likely it’s malware. i have been running rkhunter and chkrootkit without bad results, but that may not matter.

@rustybird do you also think this is still a screen issue or is it more likely to be malware?

I also found this github issue (High gjs CPU usage since upgrade to 22.04 related to DING · Issue #2358 · pop-os/pop · GitHub) which is open, but i don’t think it’s related.

1 Like

Had to look that up, okay it’s GNOME’s camera app. Maybe it’s assigned a hotkey by default or there’s some other way it could be launched by stray input events?

My money would still be on a hardware issue. Maybe it’s not the touchscreen itself that’s broken but the mainboard? Which could affect touchscreen or keyboard input.

In general, to me this kind of thing always feels like an implausible mismatch between what would be very high skilled intrusions affecting dom0, or firmware, … but looking undisciplined and extremely noisy, spamming key presses and mouse movements and all that.

Also on a statistical level the base rate of being hacked individually is low enough, and computer hardware and the software stack behaving oddly in some unspecific way is so common it’s a miracle anything ever works at all - that if the latter is used to diagnose the former, this test must have a false positive rate close to 100%.

But I’m not a hardware or malware or incident recovery expert. I’m just saying in your situation, I’d probably go ugh, there’s another expensive paperweight. Now if the same thing happened again (especially with a different notebook model), and faulty electrical wiring in my home frying my electronics one after the other had been ruled out, it would start to look interesting.

1 Like

are there are tools I can use to test if the board is performing correctly?

AI thinks it could be an extension because of the logs.

Jul 13 16:01:14 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not act>
Jul 13 16:01:13 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not act>
Jul 13 16:01:13 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:13 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:13 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not act>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to size/format constraints
Jul 13 16:01:12 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not a
Jul 13 16:01:14 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusEr>
Jul 13 16:01:13 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusEr>
Jul 13 16:01:13 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:13 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:13 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusEr>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Failed to create offscreen effect framebuffer: Failed to create texture 2d due to siz>
Jul 13 16:01:12 localhost gnome-shell[4207]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.DBusEr>
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Failed with result 'timeout'.
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Killing process 1873 (alsa-midi-seq) with signal SIGKILL.
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Main process exited, code=killed, status=9/KILL
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Killing process 1873 (alsa-midi-seq) with signal SIGKILL.
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Killing process 1796 (fluidsynth) with signal SIGKILL.
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Killing process 1805 (dbus-broker) with signal SIGKILL.
Jul 13 15:55:54 localhost systemd[1]: user@111.service: Killing process 1803 (dbus-broker-lau) with signal SIGKILL.
Jul 13 15:55:58 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c153a0 StWidget:insensitive last-child] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c143a0 StBin.popup-menu-item-expander:insensitive] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c13500 StLabel:insensitive ("Balanced")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c13080 StIcon.popup-menu-icon:insensitive] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11bd0 StLabel.popup-menu-ornament:insensitive first-child ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c153a0 StWidget:insensitive last-child] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c143a0 StBin.popup-menu-item-expander:insensitive] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c13500 StLabel:insensitive ("Balanced")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c13080 StIcon.popup-menu-icon:insensitive] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11bd0 StLabel.popup-menu-ornament:insensitive first-child ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c11400 Gjs_ui_popupMenu_PopupSubMenuMenuItem.popup-menu-item popup-submenu-menu-item:first-child last-child (>
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:57 localhost gnome-shell[4207]: st_widget_get_theme_node called on the widget [0x58a101c0ecb0 StBoxLayout.popup-menu-section:insensitive ("")] which is not in the stage.
Jul 13 15:55:39 localhost gsd-color[4351]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Japan_Display_Inc__GPD1001H_1_gdm_111
Jul 13 15:55:39 localhost gdm-launch-environment][1736]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

i’d say it was a pop! problem, but it happened in Qubes too.

is there a comprehensive hardware test i get from apt?

1 Like

Not that I know of. I think it would be a laborious manual process, hooking up probes to various parts of the board, things like that.

If the problems are more likely to occur under load, the mprime “torture test” should be able to trigger them.

Looks like normal logspam to me tbh. It may or may not point to a misconfiguration, which could be related to the gjs process using a lot of CPU, but I don’t see how that would cause stuff like stray input events.

But why not try to disable this “DING extension” thing anyway, like in the ticket you linked to.

2 Likes

When loading models and using a large amount of RAM, I am now getting unusual graphics errors.

This is sometimes affecting the fonts and shading of windows too.

I continue to not know whether this is likely a firmware hack issue, motherboard/chipset damage issue, an OS or bios issue, and whether this represents a security risk.

This happened when I used a large amount of the RAM, over half of the RAM on this machine. When I use more than that, the machine just crashes.

I have also seen unusual font disturbances, where some of the letters are missing, in other programs. Although this is occurring in the non-Qubes OS, I am also having problems in Qubes OS and don’t know what to make of this problem.

Also, I have seen under “Networks” in my file system an unusual network listed that I never created. I do some virtualization and I am not sure if the network was just picking up on some network between visualized areas. When I select the virtual network, it does not open to anything.

1 Like

No one even has a guess?