Hello all,
thank you for manjaro!
I have the following error message in the above situation:
~ gedit .zshenv .zshrc & ✔
[2] 5910
(gedit:5910): Gtk-WARNING **: 06:53:21.007: cannot open display: :0.0
[2] + exit 1 gedit .zshenv .zshrc
After all I cannot run a gui app from command line, when I do not use auto login at startup.
When I perform auto login at bootup everything works out fine!
Best regards
Check your gdm configuration files and local .X* configs which may be relevant.
using Xorg or Wayland?
which GPU?
hybrid system?
which driver is active?
Please include information about your system which will answer the above listed questions
inxi -Fxxxc0
You didn’t actually describe your situation.
Why would you want to edit ~/.zshenv and ~/.zshrc at once?
And why would you want to use gedit to do it when you are (pretty clearly) not in a graphical environment?
Use another editor - like nano. It is present by default in every installation.
nano ~/.zshenvnano ~/.zshrc
2 Likes
X11
nVidia 4090
dedicated GPU
~ nvidia-smi ✔
Fri Jan 3 10:31:06 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.135 Driver Version: 550.135 CUDA Version: 12.4 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 4090 Off | 00000000:0C:00.0 On | Off |
| 0% 52C P8 34W / 450W | 1841MiB / 24564MiB | 1% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 1288 G /usr/lib/Xorg 882MiB |
| 0 N/A N/A 1384 G /usr/bin/gnome-shell 84MiB |
| 0 N/A N/A 2138 G kitty 10MiB |
| 0 N/A N/A 2453 G ...54,262144 --variations-seed-version 107MiB |
| 0 N/A N/A 3088 G ...78,262144 --variations-seed-version 457MiB |
| 0 N/A N/A 3401 G /usr/lib/thunderbird/thunderbird 208MiB |
| 0 N/A N/A 7586 G ...erProcess --variations-seed-version 59MiB |
+-----------------------------------------------------------------------------------------+
linux-aarhus:
inxi -Fxxxc0
~ inxi -Fxxxc0 ✔
System:
Host: gerrit-systemproductname Kernel: 6.11.11-1-MANJARO arch: x86_64
bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc
Desktop: GNOME v: 47.2 tk: GTK v: 3.24.43 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 47.0 Distro: Manjaro
base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG CROSSHAIR VIII DARK HERO v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 4805 date: 03/18/2024
CPU:
Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP smt: enabled
arch: Zen 3+ rev: 0 cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
Speed (MHz): avg: 1743 min/max: 550/5084 boost: enabled cores: 1: 1743
2: 1743 3: 1743 4: 1743 5: 1743 6: 1743 7: 1743 8: 1743 9: 1743 10: 1743
11: 1743 12: 1743 13: 1743 14: 1743 15: 1743 16: 1743 17: 1743 18: 1743
19: 1743 20: 1743 21: 1743 22: 1743 23: 1743 24: 1743 25: 1743 26: 1743
27: 1743 28: 1743 29: 1743 30: 1743 31: 1743 32: 1743 bogomips: 217720
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA AD102 [GeForce RTX 4090] vendor: ZOTAC driver: nvidia
v: 550.135 arch: Lovelace pcie: speed: 2.5 GT/s lanes: 16 ports:
active: none off: DP-1,DP-2,DP-3 empty: HDMI-A-1 bus-ID: 0c:00.0
chip-ID: 10de:2684 class-ID: 0300
Device-2: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-3.1:8 chip-ID: 046d:0843
class-ID: 0102 serial: 198DAAAE
Display: x11 server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: gnome-shell driver: X: loaded: nvidia
gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 11520x2160 s-size: <missing: xdpyinfo>
Monitor-1: DP-1 mapped: DP-0 note: disabled pos: right
model: Philips PHL 329P1 serial: AU82216001247 res: 3840x2160 hz: 60
dpi: 140 size: 697x392mm (27.44x15.43") diag: 800mm (31.5") modes:
max: 3840x2160 min: 640x480
Monitor-2: DP-2 note: disabled pos: center model: Gigabyte AORUS FO32U2P
serial: 24320B001198 res: 3840x2160 hz: 60 dpi: 140
size: 699x395mm (27.52x15.55") diag: 793mm (31.2") modes: max: 3840x2160
min: 640x480
Monitor-3: DP-3 mapped: DP-4 note: disabled pos: primary,left
model: Acer XV322QK KV serial: 52131EE4F4200 res: 3840x2160 hz: 60 dpi: 140
size: 697x392mm (27.44x15.43") diag: 800mm (31.5") modes: max: 3840x2160
min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.135
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
Audio:
Device-1: NVIDIA AD102 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 0c:00.1 chip-ID: 10de:22ba class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 5-3.1:8 chip-ID: 046d:0843
class-ID: 0102 serial: 198DAAAE
API: ALSA v: k6.11.11-1-MANJARO status: kernel-api with: aoss
type: oss-emulator
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Aquantia AQtion AQC107 NBase-T/IEEE 802.3an Ethernet [Atlantic
10G] vendor: ASUSTeK driver: atlantic v: kernel pcie: speed: 8 GT/s
lanes: 4 port: N/A bus-ID: 05:00.0 chip-ID: 1d6a:07b1 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: 3c:7c:3f:41:1c:6e
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0 chip-ID: 10ec:8125
class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: 3c:7c:3f:d6:04:b7
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 07:00.0 chip-ID: 8086:1539
class-ID: 0200
IF: enp7s0 state: down mac: 3c:7c:3f:d6:04:b6
Device-4: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
speed: 5 GT/s lanes: 1 bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: 3c:9c:0f:8e:96:e9
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-6:9 chip-ID: 8087:0029 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: 3C:9C:0F:8E:96:ED
bt-v: 5.2 lmp-v: 11 class-ID: 6c0104
Drives:
Local Storage: total: 4.89 TiB used: 2.89 TiB (59.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 1TB size: 953.87 GiB
speed: 31.6 Gb/s lanes: 4 tech: SSD serial: S3EVNX0K301947N fw-rev: 2B6QCXP7
temp: 35.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Lexar model: SSD NM790 4TB size: 3.73 TiB
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: NHG456R005541P2202 fw-rev: 12237
temp: 55.9 C scheme: GPT
ID-3: /dev/sda vendor: OCZ model: VERTEX4 size: 238.47 GiB speed: 6.0 Gb/s
tech: SSD serial: OCZ-MED154408D785HBK fw-rev: 1.5 scheme: GPT
Partition:
ID-1: / size: 3.6 TiB used: 1.83 TiB (50.7%) fs: ext4 dev: /dev/nvme1n1p2
ID-2: /boot/efi size: 299.4 MiB used: 296 KiB (0.1%) fs: vfat
dev: /dev/nvme1n1p1
Swap:
ID-1: swap-1 type: partition size: 68.98 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme1n1p3
Sensors:
System Temperatures: cpu: 39.0 C mobo: 39.0 C gpu: nvidia temp: 52 C
Fan Speeds (rpm): cpu: 0 gpu: nvidia fan: 0%
Info:
Memory: total: 64 GiB note: est. available: 62.7 GiB used: 12.34 GiB (19.7%)
Processes: 582 Power: uptime: 3h 32m states: freeze,mem,disk suspend: deep
wakeups: 0 hibernate: platform Init: systemd v: 256 default: graphical
Packages: 2110 pm: pacman pkgs: 2071 pm: flatpak pkgs: 39 Compilers:
clang: 18.1.8 gcc: 14.2.1 alt: 13 Shell: Zsh v: 5.9 running-in: terminator
inxi: 3.3.36
it is just any GUI app that is not running from Terminal b/c of display :0.0 error.
It appears there is a language barrier here.
Let us clarify your use by asking a simple yes /no question
gedit when outside the Gnome desktop - known as plain console or TTY? (without the graphical desktop)
If you can answer yes to above question, then you are correct - it is not possible to run gedit outside the graphical desktop - and the error is expected.
Outside the graphical desktop, you must use a console editor like vi , nano or micro .
1 Like
Are you in a graphical session at all?
Gnome defaults to a Wayland session - X applications won’t work.
NO!
You are mistaken: I can run any GUI app from gnome terminal and it outputs the GUI on X11.
leder11011:
You are mistaken:
I am not mistaken - I asked a question to clarify the usecase - you answered no to my question
I know that
You will have to look at your configuration files
Autologin is something invented to please former Windows users and it is creating more issues than it solves.
That said - I have tested with a virtual machine - GNOME Shell 47.2 - with and without autologin - no issues
thank you for your message!
I can assure you: gnome login screen is definitively broken - I have three monitor setup and they are misaligned on gnome login screen, but not on gnome desktop. That’s an additional bug to the one with the disabled auto login.
leder11011:
the disabled auto login.
I cannot reproduce that issue - GNOME Shell 47.2 - whether I use wayland or xorg and enable autologin or not.
Not a bug - likely some local configuration issue.
As I don’t use Gnome on my workstation - I cannot verify if you are correct.
I am telling the truth. I give you my word!
That’s not the point.
An issue needs to be reproduced (by others) before it can be potentially considered a bug .
It is indeed more likely to be a configuration issue.
I don’t use Gnome.
I do, however, have Gnome installed on a VM (fully updated) and it does not exhibit the issue you’re describing as a bug. Of course, the VM does not use Nvidia or multiple monitors, either.
I notice you’re using X11.
Perhaps using Wayland may help produce more favourable results; otherwise, I have nothing useful to suggest at this time.
Regards.
1 Like
Thank you for your input!
I use X11 indeed as it is forced by manjaro when proprietary nvidia drivers are installed:
stop disabling wayland on nvidia machines.
It forces users to go through a whole bunch of shady forums dabbling in config files that may or may not work . It forces them into a dangerous position.
Allow them to have the option to boot into wayland and when they see how “buggy” you say it is, they will opt into x11 on their own .
You are making them attempt shady installs of it and they will be flooding the forum with this subject.
Just enable it in its best case scenario and let the users c…
When I login into wayland I get funny things happening…
I understood that the Nvidia/Wayland situation on Gnome had improved a little since I last read anything substantial about the combination. As I use AMD graphics exclusively, there’s been no pressing need to follow it often.
However, contrary to your interpretation of the 2023 topic you referenced (which appears to be a rant on the subject by another Member) X11 is not forced ; though in Gnome, specifically, it seems Wayland was disabled at some point.
The choice to run Wayland remains, if desired.
Difficulty: ★★★☆☆
Wayland does not play well with proprietary drivers. Currently the biggest issue is that NVIDIA does currently not support Xwayland properly, so apps that require it get software rendering. This includes most games, which are the most common use case for proprietary NVIDIA drivers. This is why GNOME automatically disables Wayland if you have NVIDIA.
However, if this does not deter you, you can use Wayland with NVIDIA drivers. Here is how to do it:
That tutorial was also from 2023.
Success or failure will be greatly influenced by the specific Nvidia hardware used in conjunction with Wayland.
It appears even now that some Members still experience difficulties with this combination.
With respect your current issue, I’m afraid it seems to need further clarification. I note that others have tried to extract information from you to better understand your problem, but without success.
It may be that:
The only person who can help overcome that is you.
Another possibility is to create a new topic in your native language category , which might ultimately be more effective.
Eine weitere Möglichkeit wäre, ein neues Thema in der Kategorie deiner Muttersprache zu erstellen , was letztlich effektiver sein könnte.
Please let us know if you decide to do that.
I hope you find a solution.
Regards.
It is fairly simple to enable / disable wayland.
When funny things happen - switch to testing or unstable branch.
Open Manjaro Hello - click the Layouts button - click the Settings tab
Of course you need to restart user-space
systemctl soft-reboot
1 Like
for your problem in the forum ? (Wisdom lies in asking → listening → reading 
Are you launching gedit when outside the Gnome desktop - known as plain console or TTY? (without the graphical desktop)