You are not logged in.

#1 2023-12-02 18:39:06

juanbits
Member
Registered: 2023-12-02
Posts: 5

dotted/pixelated windows on xfce4

Hi there,

I'm having some problems with my arch and xfce4.

At start when i run startxfce4 I'm getting a white screen and sometimes looks pixelated or dotted. I fix that every time running:
rm ~/.cache/xfce4

but yesterday after a power off due to electricity issues, when i try to enter I'm getting the same white screen and not works even i run the above command.

Then i see i need to run:
rm ~/.cache/
and
rm ~/.config/xfce4

and then startxffce4 and I'm was able to enter. Im configure the display settings but now when i try to enter to the pamac-aur, chrome or chromium i get a white-pixelated-dotted window, like you can look in the image
68b6fbf4-d601-4e79-b892-ef7c1a2900a0.jpg

im able to open the firefox, writter, calc, etc, windows

i need your help to:
1. how to fix the white windows (pamac-aur, chrome, windows)
2.- avoid run every time rm the directories and configs

thanks in advance

Offline

#2 2023-12-02 20:17:33

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 8,842
Website

Re: dotted/pixelated windows on xfce4

Try disabling the compositor.


Jin, Jîyan, Azadî

Offline

#3 2023-12-02 20:55:22

juanbits
Member
Registered: 2023-12-02
Posts: 5

Re: dotted/pixelated windows on xfce4

thanks, I disabled the compositor. Now i poweroff and reboot and when i run startxfce4 i dont need rm cache or config.

But when i try to open chrome or pamac-aur i continue getting the white or pixelated window

pamac-aur window
xxsjdhfdj1.png

chromium window
xxsdf2.png

Offline

#4 2023-12-02 21:08:03

seth
Member
Registered: 2012-09-03
Posts: 63,354

Re: dotted/pixelated windows on xfce4

Please replace the oversized images w/ links (the board has a 250x250 px max rule) and post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Offline

#5 2023-12-06 01:44:17

juanbits
Member
Registered: 2023-12-02
Posts: 5

Re: dotted/pixelated windows on xfce4

when i start the pamac-manager via the terminal, i see the next:

kernel rejected pushbuf: Invalid argument

and if i run the command

journalctl --boot --catalog --priority=err
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
Dec 02 14:51:17 myuser systemd-coredump[1043]: [] Process 990 (pamac-manager>
                                                 
                                                 Stack trace of thread 990:
                                                 #0  0x00007f1691b2083c n/a (li>
                                                 #1  0x00007f1691ad0668 raise (>
                                                 #2  0x00007f1691ab84b8 abort (>
                                                 #3  0x00007f1691ab83dc n/a (li>
                                                 #4  0x00007f1691ac8d26 __asser>
                                                 #5  0x00007f168c011c28 nouveau>
                                                 #6  0x00007f168c011b87 nouveau>
                                                 #7  0x00007f168c011cad n/a (li>
                                                 #8  0x00007f168c011f27 n/a (li>
                                                 #9  0x00007f168c012a79 n/a (li>
                                                 #10 0x00007f1662338ac8 n/a (no>
                                                 #11 0x00007f16623548bc n/a (no>
                                                 #12 0x00007f166236cf04 n/a (no>
                                                 #13 0x00007f16623b9a4d n/a (no>
                                                 #14 0x00007f168c011c9e n/a (li>
                                                 #15 0x00007f168c011f27 n/a (li>
                                                 #16 0x00007f168c012a79 n/a (li>
                                                 #17 0x00007f1662e4d25f n/a (no>
                                                 #18 0x00007f16623d7ec9 n/a (no>
                                                 #19 0x00007f16623e939e n/a (no>
lines 1-23...skipping...
Dec 02 14:51:17 myuser systemd-coredump[1043]: [] Process 990 (pamac-manager) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 990:
                                                 #0  0x00007f1691b2083c n/a (libc.so.6 + 0x8e83c)
                                                 #1  0x00007f1691ad0668 raise (libc.so.6 + 0x3e668)
                                                 #2  0x00007f1691ab84b8 abort (libc.so.6 + 0x264b8)
                                                 #3  0x00007f1691ab83dc n/a (libc.so.6 + 0x263dc)
                                                 #4  0x00007f1691ac8d26 __assert_fail (libc.so.6 + 0x36d26)
                                                 #5  0x00007f168c011c28 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4c28)
                                                 #6  0x00007f168c011b87 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4b87)
                                                 #7  0x00007f168c011cad n/a (libdrm_nouveau.so.2 + 0x4cad)
                                                 #8  0x00007f168c011f27 n/a (libdrm_nouveau.so.2 + 0x4f27)
                                                 #9  0x00007f168c012a79 n/a (libdrm_nouveau.so.2 + 0x5a79)
                                                 #10 0x00007f1662338ac8 n/a (nouveau_dri.so + 0x938ac8)
                                                 #11 0x00007f16623548bc n/a (nouveau_dri.so + 0x9548bc)
                                                 #12 0x00007f166236cf04 n/a (nouveau_dri.so + 0x96cf04)
                                                 #13 0x00007f16623b9a4d n/a (nouveau_dri.so + 0x9b9a4d)
                                                 #14 0x00007f168c011c9e n/a (libdrm_nouveau.so.2 + 0x4c9e)
                                                 #15 0x00007f168c011f27 n/a (libdrm_nouveau.so.2 + 0x4f27)
                                                 #16 0x00007f168c012a79 n/a (libdrm_nouveau.so.2 + 0x5a79)
                                                 #17 0x00007f1662e4d25f n/a (nouveau_dri.so + 0x144d25f)
                                                 #18 0x00007f16623d7ec9 n/a (nouveau_dri.so + 0x9d7ec9)
                                                 #19 0x00007f16623e939e n/a (nouveau_dri.so + 0x9e939e)
                                                 #20 0x00007f16623e97d7 n/a (nouveau_dri.so + 0x9e97d7)
                                                 #21 0x00007f1661d03c42 n/a (nouveau_dri.so + 0x303c42)
                                                 #22 0x00007f1692676c18 n/a (libgtk-4.so.1 + 0x476c18)
                                                 #23 0x00007f169267bbc2 n/a (libgtk-4.so.1 + 0x47bbc2)
                                                 #24 0x00007f16926591a5 gsk_renderer_render (libgtk-4.so.1 + 0x4591a5)
                                                 #25 0x00007f1692474af2 n/a (libgtk-4.so.1 + 0x274af2)
                                                 #26 0x00007f1692475a39 n/a (libgtk-4.so.1 + 0x275a39)
                                                 #27 0x00007f16925daf89 n/a (libgtk-4.so.1 + 0x3daf89)
                                                 #28 0x00007f1692a9fb73 n/a (libgobject-2.0.so.0 + 0x33b73)
                                                 #29 0x00007f1692a9fc77 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33c77)
                                                 #30 0x00007f1692a9fd34 g_signal_emit (libgobject-2.0.so.0 + 0x33d34)
                                                 #31 0x00007f1692647c9c n/a (libgtk-4.so.1 + 0x447c9c)
                                                 #32 0x00007f1692a9fb73 n/a (libgobject-2.0.so.0 + 0x33b73)
                                                 #33 0x00007f1692a9fc77 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33c77)
                                                 #34 0x00007f1692a9fd34 g_signal_emit (libgobject-2.0.so.0 + 0x33d34)
                                                 #35 0x00007f169263493a n/a (libgtk-4.so.1 + 0x43493a)
                                                 #36 0x00007f1691f363ee n/a (libglib-2.0.so.0 + 0x5b3ee)
                                                 #37 0x00007f1691f34f69 n/a (libglib-2.0.so.0 + 0x59f69)
                                                 #38 0x00007f1691f93327 n/a (libglib-2.0.so.0 + 0xb8327)
                                                 #39 0x00007f1691f33162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
                                                 #40 0x00007f1692106b16 g_application_run (libgio-2.0.so.0 + 0xdfb16)
                                                 #41 0x000055ab6af4d100 main (pamac-manager + 0xd100)
                                                 #42 0x00007f1691ab9cd0 n/a (libc.so.6 + 0x27cd0)
                                                 #43 0x00007f1691ab9d8a __libc_start_main (libc.so.6 + 0x27d8a)
                                                 #44 0x000055ab6af4d175 _start (pamac-manager + 0xd175)
                                                 
                                                 Stack trace of thread 995:
                                                 #0  0x00007f1691b2c894 n/a (libc.so.6 + 0x9a894)

Last edited by juanbits (2023-12-06 01:47:30)

Offline

#6 2023-12-06 07:17:32

seth
Member
Registered: 2012-09-03
Posts: 63,354

Re: dotted/pixelated windows on xfce4

seth wrote:

Please replace the oversized images w/ links (the board has a 250x250 px max rule) and post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Also don't copypaste out of the pager, it trunc>
And you've to run "sudo journalctl" to see more than your session log.

I can already tell that the problem is nouveau, though.

Offline

#7 2023-12-07 04:26:21

juanbits
Member
Registered: 2023-12-02
Posts: 5

Re: dotted/pixelated windows on xfce4

seth wrote:
seth wrote:

Please replace the oversized images w/ links (the board has a 250x250 px max rule) and post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Also don't copypaste out of the pager, it trunc>
And you've to run "sudo journalctl" to see more than your session log.

I can already tell that the problem is nouveau, though.

this is the output

Dec 05 19:54:02 myuser kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Dec 05 19:54:02 myuser kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000038800000-0x000000003cffffff], contact BIOS vendor for fixes
Dec 05 19:54:02 myuser kernel: x86/cpu: SGX disabled by BIOS.
Dec 05 19:54:02 myuser kernel: RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
Dec 05 19:54:02 myuser kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Dec 05 19:54:02 myuser kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
Dec 05 19:54:02 myuser kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 022554 [ PRIVRING ]
Dec 05 19:54:04 myuser bluetoothd[411]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to clear UUIDs: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to set mode: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:04 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:19 myuser kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ PRIVRING ]
Dec 05 19:54:21 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:21 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:21 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:21 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:22 myuser bluetoothd[411]: Failed to add UUID: Failed (0x03)
Dec 05 19:54:30 myuser kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ PRIVRING ]
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validating bo list
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: validate: -22
Dec 05 19:54:31 myuser kernel: nouveau 0000:01:00.0: Xorg[545]: fail ttm_validate

and the next is another output

spci -k | grep -A 2 -E "(VGA|3D)"

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
	Subsystem: ASUSTeK Computer Inc. HD Graphics 530
	Kernel driver in use: i915
--
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)
	Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M]
	Kernel driver in use: nouveau

Offline

#8 2023-12-07 07:11:04

juanbits
Member
Registered: 2023-12-02
Posts: 5

Re: dotted/pixelated windows on xfce4

I see i dont has installed the nouveau package, so I install the nvidia drivers and config them. Then i reboot and my grub crashed. then i recover the boot and now all work ok, i dont see the pixelated windows

thanks

Offline

#9 2023-12-07 07:32:32

seth
Member
Registered: 2012-09-03
Posts: 63,354

Re: dotted/pixelated windows on xfce4

That's still not your journal, but oh, well.
nouveau_dri.so and libdrm_nouveau.so.2 are part of mesa and libdrm, you've likely been using the modesetting driver on top of the nouveau kernel module, xf86-video-nouveau is irrelevant itr.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB