Screen Goes black after Login After Update

I am new to linux and recently shifted to Manjaro Os and having a great experience.

But after updating some days before Two strange things happened with me.

  1. I automatically got signed out from all of my gmail accounts from chromium though there was nothing done in settings and it was working fine before update
    But I solved that by logging in all again.

  2. Today when I started my Pc, I saw the login screen as before But After typing password and pressing enter the entire screen goes black with only cursor present. However, I tried rebooting multiple times but still same thing happens everytime.

Can I know why before updates everything runs smoothly and after updates everytime something happens that spoils my overall experience ??

Is there an easy way of solving this?
Any kind of help or advice will help me.

Make sure you log in in X11 Session and not the Wayland one as your system might not be compatible and somehow was set as default.
In your left, corner screen, dropdown menu

image

select it first to make sure

image

then log in

I was trying to login with plasma x11 session only.
Also I have only one session that is plasma x11
I also tried running startx but the result came the same.

From TTy use startplasma-x11 instead and provide what error you get.
Also, to make sure there was no partial update, run this:
sudo pacman-mirrors -f5 && sudo pacman -Syyu

When I write startplasma-x11
It is showing

“DISPLAY is not set or cannot connect to the X Server”

And after running an update it shows nothing to do.

We should know more about your system in order to get an idea what is happening

See what you can gather and share with us. Someone will help you out for sure.

There is no green link here


Click here :slightly_smiling_face:

I am new to linux and manjaro Os
I can see my login screen as it was before But when I Enter My Password and press Enter then screen goes black with only cursor present

After getting into terminal when i type
startplasma-x11
Then error comes
DISPLAY not set or cannot connect to x-server.

System info
Processor i3 7th gen
GPU nvidia Gt 710
RAM 4 GB
120 GB SSD
1TB HDD

WHEN I STARTED A NEW TOPIC IN FORUM THEN THE PERSON GAVE ME THIS LINK.

IS THERE ANY WAY TO SOLVE THIS ERROR OR DO I NEED TO REINSTALL MY OS ??

It’s only to get the information that we need.
And post it on the other forum post.

1 Like

:+1: Welcome to Manjaro! :+1:

  1. What bogdancovaciu was trying to tell you was, please read this!
    Don’t post there! :grin:
    After reading the above, press the three dots below your original post and give us more information so we can see what’s really going on.
    Because now we know [the symptom of the disease, but we need some more probing to know where the origin lies… :grin:
  2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
    Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

:+1:

Will You Please Guide Me How To Do It because i am only able to access the terminal and nothing else so how to copy paste?

  • Execute:

    inxi --admin --verbosity=7 --filter --no-host --width > /tmp/myini.txt
    
  • Execute:

    cp /tmp/myinxi.txt /Wherever/Your/USB/is
    

    where, obviously /Wherever/Your/USB/is is the path to your USB stick (I don’t know where you mounted it)

  • upload the file from your USB stick here.

:crossed_fingers:

System:
  Kernel: 5.10.56-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=5bcb4106-7b5a-4636-a5a8-a42872f901c6 rw quiet udev.log_priority=3 
  Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
  Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Desktop System: Gigabyte product: H110M-S2 v: N/A serial: <filter> 
  Mobo: Gigabyte model: H110M-S2-CF v: x.x serial: <filter> 
  UEFI: American Megatrends v: F23 date: 12/14/2017 
Battery:
  Message: No system battery data found. Is one present? 
Memory:
  RAM: total: 3.73 GiB used: 1.97 GiB (52.9%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 9E (158) stepping: 9 microcode: EA 
  cache: L2: 3 MiB bogomips: 31211 
  Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 
  4: 800 
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon art 
  avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid 
  cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts ept ept_ad erms est f16c 
  flexpriority flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window hwp_epp 
  hwp_notify ibpb ibrs intel_pt invpcid invpcid_single lahf_lm lm mca mce 
  md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid 
  pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand 
  rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 
  ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme 
  vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel 
  bus-ID: 00:02.0 chip-ID: 8086:5912 class-ID: 0380 
  Device-2: NVIDIA GK208B [GeForce GT 710] vendor: Gigabyte driver: nvidia 
  v: 470.57.02 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 
  chip-ID: 10de:128b class-ID: 0300 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: nvidia display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.0x10.7") 
  s-diag: 554mm (21.8") 
  OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 470.57.02 
  direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 
  class-ID: 0403 
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus-ID: 01:00.1 chip-ID: 10de:0e0f class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.56-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 15.0 running: yes 
  Sound Server-4: PipeWire v: 0.3.33 running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: d000 bus-ID: 02:00.0 
  chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  WAN IP: <filter> 
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB 
  driver: btusb v: 0.8 bus-ID: 1-3:2 chip-ID: 0a12:0001 class-ID: e001 
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends 
Logical:
  Message: No logical block device data found. 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 1.05 TiB used: 81.47 GiB (7.6%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SQ500S37 120G 
  size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  type: SSD serial: <filter> rev: 1102 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM010-2EP102 
  size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  type: HDD rpm: 7200 serial: <filter> rev: CC43 scheme: GPT 
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Ultra Fit 
  size: 28.64 GiB block-size: physical: 512 B logical: 512 B type: N/A 
  serial: <filter> rev: 1.00 scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / raw-size: 111.49 GiB size: 109.18 GiB (97.93%) 
  used: 24.92 GiB (22.8%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: N/A 
  uuid: 5bcb4106-7b5a-4636-a5a8-a42872f901c6 
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) 
  used: 288 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: NO_LABEL 
  uuid: FC8B-94C4 
  ID-3: /run/media/omi/HDD raw-size: 931.51 GiB size: 915.82 GiB (98.31%) 
  used: 31.4 GiB (3.4%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: HDD 
  uuid: 8092c9c5-f927-4980-ac5a-4a90e81b1f29 
  ID-4: /run/media/omi/OM raw-size: 28.64 GiB size: 28.62 GiB (99.95%) 
  used: 25.15 GiB (87.9%) fs: vfat dev: /dev/sdc1 maj-min: 8:33 label: OM 
  uuid: F8A2-68B3 
Swap:
  Alert: No swap data was found. 
Unmounted:
  Message: No unmounted partitions found. 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-3:2 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) 
  type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s 
  power: 100mA chip-ID: 0a12:0001 class-ID: e001 
  Device-2: 1-4:3 info: MosArt 2 4Ghz Wireless Transceiver [for Delux M618 
  Plus Wireless Vertical Mouse] 
  type: Keyboard,Mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1 
  speed: 12 Mb/s power: 100mA chip-ID: 062a:4c01 class-ID: 0301 
  Device-3: 1-9:4 info: SanDisk Ultra Fit type: Mass Storage 
  driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 224mA 
  chip-ID: 0781:5583 class-ID: 0806 serial: <filter> 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 47 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 35% 
Info:
  Processes: 211 Uptime: 27m wakeups: 0 Init: systemd v: 248 tool: systemctl 
  Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1341 lib: 339 
  Shell: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06 

So you have an issue in your user profile and finding out which exact setting you changed is going to take weeks if not months, therefore, we’re going to do the following:

  • Log into TTY2

  • Create a new user (E.G. if your current user is twitty, create twitty2)

    useradd twitty2
    
  • Verify that the new user has access to the same groups as your old one by executing groups and comparing the output of both users.

     groups twitty
     groups twitty2
    

    (Where obviously, twitty is your old user and twitty2 is your new one.)
    E.G. if twitty is a member of operator and twitty2 isn’t, execute:

    usermod --append --groups operator twitty2
    
  • Copy all data files from your old profile into your new one

    cp --verbose --recursive --preserve=timestamps /home/twitty/Documents/* /home/twitty2/Documents/
    

    If that worked and you had no errors, remove the documents from your old user:

    rm --recursive /home/twitty/Documents/*
    

    repeat for:

    • Pictures
    • Videos
    • Music
    • .thunderbird
    • .mozilla/firefox/
    • Templates, and everything else that is important to you.
    • Linux games like Battle of Wesnoth have their game data stored under ~/.local/share/ E.G. ~/.local/share/wesnoth/
  • After everything has been copied over, disable the old user so you cannot accidentally log on to it any more:

    usermod --lock twitty
    
  • If you would have theming or other customisations going on, don’t do everything in one day but do this at the rate of 1 application / theme / … per day and if the same issue crops up again, roll back your last change and thus you’ve now pinpointed the exact setting that made your old user misbehave. :thinking:

  • in 1 month delete the entire home directory of your old user, but don’t delete the user itself so that in 6 months time files still owned by that user will still show up under its username.

  • If you ever migrate to a new machine, just don’t migrate the old user: only the new one.


Now log in as your new user and we’re going to take care of the root cause of your issue:

Please read this and adapt


And from now on, start making backups so you can roll back and never have to do this again:

1 Like