LinuxQuestions.org - Overlapping screens with x error in Debian

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Overlapping screens with x error in Debian (https://www.linuxquestions.org/questions/linux-software-2/overlapping-screens-with-x-error-in-debian-4175718634/)

Overlapping screens with x error in Debian

Difficult to explain :

unable to switch in Debian 11 from one to other program (page). (Now I am writing on Ubuntu, same computer,different partition).

Mostly I note an X trying to change, close pages.

Pls. see screenshot

Many thanks everybody.

That's a bizarre looking desktop. :p

Your window decorations are missing; no titlebars or frames or min/max/close buttons that I can make out.

What you need to explain is how you got your Debian, whether it ever worked right, if you just upgraded from 11.4 to latest, if it's a VM, if it's a fresh installation, things like that. All you've done is show us something is wildly wrong.

Try doing inxi -Faz > somefile.txt and pasting somefile.txt here using code tags, so that we know something about your hardware and setup.

Many thanks for your kind answer.

Debian version is 11, but upgrade was confused (in root I still read @debian -10 ).

Full booting is still impossible (no way to write in terminal); however if I log out to other user, Debian 11 is loaded and works regularly (only first user is disabled ? ):

Quote:

username@debian-10:~$ su -
Password:
root@debian-10:~# inxi -GSCaZ
System:
Host: debian-10 Kernel: 5.10.0-19-amd64 x86_64 bits: 64 compiler: gcc
v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64
root=UUID=a53812cd-eaf3-480e-a77c-358b3439806d ro quiet
Console: tty 0 DM: GDM3 3.38.2.1 Distro: Debian GNU/Linux 11 (bullseye)
CPU:
Info: Quad Core model: Intel Core i5-8269U socket: BGA1528 (U3E1)
note: check bits: 64 type: MT MCP arch: Kaby Lake note: check family: 6
model-id: 8E (142) stepping: A (10) microcode: 9E L1 cache: 256 KiB
L2 cache: 6 MiB L3 cache: 5.9 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 41599
Speed: 400 MHz min/max: 400/4200 MHz base/boost: 2475/8300 volts: 0.8 V
ext-clock: 100 MHz Core speeds (MHz): 1: 400 2: 400 3: 400 4: 400 5: 400
6: 400 7: 400 8: 400
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no
microcode; SMT vulnerable
Type: retbleed mitigation: IBRS
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Vulnerable: No microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CoffeeLake-U GT3e [Iris Plus Graphics 655] driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:3ea5 class ID: 0300
Device-2: Realtek Integrated_Webcam_FHD type: USB driver: uvcvideo
bus ID: 1-8.1:6 chip ID: 0bda:5760 class ID: 0e02 serial: 200901010001
Display: server: X.org 1.20.11 driver: loaded: modesetting
unloaded: fbdev,vesa tty: 80x24
Message: Advanced graphics data unavailable in console for root.
root@debian-10:~#

Please edit post #3 to change the quote tags to code tags so as to preserve the original formatting and thus command output readability. Also at most only -GSCaz is needed from inxi for graphics issues. inxi -Faz is mostly noise.

If the screen is messed up for one user and good for the other user then it would indicate that something in the user configs in their home directory is causing the problem. It becomes an exercise in identifying and removing the problem config for that user.

Quote:

Originally Posted by computersavvy (Post 6392413)

Thanks, but .. if I log out to second user , how to modify first user configs ? (First user has troubles).

(On recovery mode I read following :
audit: type=1400 ..apparmor = "Denied" ..
If I log out (to second user),one warning message is : "low disk space on Filesystem root" )

Quote:

Originally Posted by AngeloU (Post 6393780)

warning message is : "low disk space on Filesystem root" )

This can cause all kinds of trouble. Fix it before doing anything else. The simplest cure for this in most cases is probably apt clean, which will remove downloaded updates from the cache. First run df -h / to see just how much freespace remains, then run it again after to see how much more results. If you have a persistent journal, it will consume a good deal of space if not configured to be limited to a date range and/or size range and/or file quantity range in /etc/systemd/journal.conf.

Quote:

Originally Posted by mrmazda (Post 6393827)

Apt clean reduced disk usage to 90 % (previous was 98 %)

Since problems for first user persist, should I now modify /home (not second user home) ?

Here some attempts to open /root :

Quote:

Quote:

Originally Posted by AngeloU (Post 6394046)

I have no idea what you were trying to do.

Code:

# duf /home

-bash: duf: command not found

# du -s /home

783212  /home

# du -f /home

du: invalid option -- 'f'

Try 'du --help' for more information.

Quote:

Originally Posted by AngeloU (Post 6394046)

Apt clean reduced disk usage to 90 % (previous was 98 %)

A system that is that close to full should be modified to allow more space or have software/logs/etc. cleaned up to allow more space.

Running a file system at 90% or more on a consistent basis may result in fragmentation of files or other issues as well as potential inability to even boot & log in.

If you have free disk space I would recommend expanding the partition holding / . If no available space exists then remove unnecessary data/software to free up additional space in the existing file system/partition.

I feel two solution has been provided :

1.

Code:

... exercise in identifying and removing the problem config for that user....

Code:

....I would recommend expanding the partition holding / . If no available ....

Therefore I think to mark this post as s o l v e d .

Starting again (on next days) with new posts for each point ( 1 and 2 ).