Hi!
I have a strange problem with my installation.
When I use Wlan I can't open any program anymore. If I try to open a program in the terminal I get the following output:
No Protocol specified
Unable to init server: Connection failed: Connection setup rejected
Error: connato open display: :0
What is this and how can I solve this problem?
I use OpenRC if this is important. I tried it with KDE and XFCE but both have the same behaviour (both with a fresh installation).
Hello,
Have you configured wlan correctly?
I suppose so.
Yes, and it worked for four days (after a fresh installation with a weekly ISO, all others won't work). I don't know what this failure caused.
Maybe this could help you :
https://bbs.archlinux.org/viewtopic.php?id=250965
I changed the hostname to another one and now it works. I haven't used localhost or any other system relevant hostname so I still don't understand why my hostname didn't worked. In any other Distro I used the same and had no problems.
Anyway, thanks for your help and the link! Now I know what caused this failure.
I do not know the answer to your problem, and I will let the specialists answer you.
But I had read that the hostname could be a problem :
https://forum.artixlinux.org/index.php/topic,2700.msg17826.html#msg17826
With pleasure 8-)
https://man.archlinux.org/man/hostname.7
https://datatracker.ietf.org/doc/html/rfc1178
@strajder What do you want me to say with your links? I know what a hostname is and how it should be named.
So, then tell me what was wrong with my hostname "grid"?
With "grid" as hostname and wlan activated no programs can be opened. I changed it to "thegrid" and now it works.
And I have to say that this behaviour is only in Artix, on all other Distris I can use "grid" as hostname without a problem.
Just tried setting my hostname to "grid" without any errors. Proof:
https://i.imgur.com/ofB1TlP.png
Notes:
1. I'm using 66.
2. When setting the hostname with hostname grid as root, X programs will from that point on refuse to start in the currently running X session, which is expected (this isn't related to the name "grid" itself). I had to do 66-env boot@system as root and set the hostname there, followed by 66-enable -F -t boot boot@system and reboot to be able to properly set the hostname to "grid" and test the rename.
Without more details about your problem (https://forum.artixlinux.org/index.php/topic,1923.0.html), it's hard to say. For example, you only mentioned what was the actual hostname which was failing now. Maybe someone could help you more if you described the steps you did when setting the hostname to "grid" more thoroughly and gave the links to relevant configuration files (using paste.artixlinux.org for larger files).
Which steps? As I mentioned I did a fresh install and set the hostname with the installer, nothing else.
And I can't describe more because there's nothing more to say except what I said.
I got the same problem, with the wlan that, casually, locked or not the execution of every program if the notebook is connected. You disconnect it from the wlan and all start regularly, despite the connection to the lan, obviously.
It happen to me with 2 different notebook of Tuxedo (the GEN1 model). It work correctly when I'm in office, don't work with the lan of Customer A, work with Customer B, but not always and so on.
Sometime simply disconnecting and connecting to the lan, via WIFI, is sufficient to have all work correctly. Its an error that is a lot less frequent, at least for me, from 2 months, more or less.
The hostname in not localhost.
I thought about a problem with connman, I'm using networkmanager, but I'm not sure. Anyway I removed connman from the program started automatically.
That is a description as well. But you didn't include the "nothing else" part in the OP. Every bit of information is important, because it helps narrow down the problem.
Your init is important, because in addition to narrowing down the problem, the exact commands in the solution will differ if it involves dealing with services.
So far we have determined that the problem doesn't depend on the particular hostname that is given to the computer - "grid" is not special in any way.
This is just a speculation, but I'd say that the problem could be in not activating the dhcpcd service. In OpenRC:
$ su
# rc-service dhcpcd start
The hostname service in OpenRC just reads /etc/hostname and runs the command
hostname with whatever it read from that file as the argument (check with
less /etc/init.d/hostname).
Without logs, we can't be sure what's wrong with your system.I happen to have a laptop with a built-in wifi adapter, but unfortunately I cannot reinstall Artix on it just for the sake of testing this. Wifi works perfectly on it under Artix base with 66 init, and there are no problems with starting X programs.
Check /var/log/rc.log (perhaps paste it to pastebin or similar after redacting it with sed or similar if there was any sensitive info in it) and if the hostname setting worked you might see something like this:
Setting hostname to grid from /etc/hostname ...
[ ok ]
not:
Failed to set the hostname
Testing this on 2 Artix OpenRC laptops, one with the internal wifi card and the other with a PCMCIA card (also on the PCI bus) I had no problems using grid or nf220 which I think was the name that gave me problems on another laptop. But these 2 had a base install and lack a regular network manager app, whereas the one I had problems with was a fairly default Mate (iirc) iso install.
In the first post I wrote that I use OpenRC and tried with XFCE and KDE (now I'm on KDE), both fresh installs.
I will give the logs if this issue happens again.
I think it's the wrong driver for this Wlan card because sometimes the connection get lost and it takes sometime to connect again. I will have a look which hardware the laptop has.
I was so annoyed by the problem that I first installed another distribution.
Actually, I am still interested in the error, so I just installed Artix again.
Even before I did the first update (I used the same weekly Iso from 30.08. like the last time, and the exact settings), Wlan was activated, nothing worked again.
I have therefore made two screenshots where you can see the error message in the terminal.
Can it be that this is a bug of KDE with the combination of Wayland? Or isn't the KDE ISO well configured?
AFAIK, all Artix ISOs are tested. Even so, you can always use the base ISO and go from there.
Again, post
logs (preferably using paste.artixlinux.org) so we can try to find the cause of the problem. See here:
how to ask correctly to get the right answer (https://forum.artixlinux.org/index.php/topic,1923.0.html)
I don't think so because otherwise there wouldn't be both gpu drivers are active.
inxi:
https://paste.artixlinux.org/b971b5bb
lsmod:
https://paste.artixlinux.org/66455e8f
After the initial update after fresh install it didn't happen again, so I have to wait.
EDIT:
The two screenshots from my last post were from the live iso.
The first thing you do after installation and reboot from hard disk is pacman -Syyu, provided you have a working network connection.
You have two video cards installed in your system?
If not, you shouldn't use nouveau (independent driver for NVIDIA cards) with an AMD ATI card. If the kernel still somehow loads nouveau on your system, you should blacklist (https://wiki.archlinux.org/title/Kernel_module#Blacklisting) nouveau module.
Post other logs, most importantly /var/log/dmesg.log and /var/log/everything.log.
Yes, there are two video cards in the system, one from the cpu and a dedicated nVidia. Nowadays many notebooks have two video cards.
Both drivers are loaded by default from the ISO. But why?
dmesg.log is empty and everything.log is too long atm and there's nothing special in the log to see the problem, because like I said there wasn't any problem since reboot and update.
Since there is no problem, I guess this doesn't apply then?
Running
pacman -Syyu after installing and rebooting the system from disk is standard procedure. Artix is a rolling release distro and it is user's fault if he doesn't update the system. There is nothing wrong with the ISO. If you disagree, provide the everything.log and dmesg output (or log) from when there is a problem.
Didn't you read what I wrote? I said dmesg.log is empty and in the everything.log can't be found what I'm looking for because it happened during the live session!
And of course the iso has issues and the installation too because it happened there, some packages aren't loaded (xcb for example) as you can see in the two screenshots, and last but not least, two gpu drivers are loaded at the same time.
I know what a rolling release distro is and I know what to do after an installation, but these problems were in the live iso session.
And it's not my job to blacklist a gpu driver because I didn't install them on my own.
Your descriptions are very vague, I hope not on purpose.
You didn't write the issue happened during the "live session" (meaning the initial session from installation media, not the one from the installed system). You instead wrote this:
So, it's a fresh installed system that has problems.
So, now it's a fresh install from both XFCE and KDE, and both installs work without problems ("if this issue happens again")?
So, again, it is the installed system that has problems, and not the session from installation media?
If your issue happens during the session from the installation media, I can test that on my laptop. Installed system should be updated immediately on first boot.
If you have two graphics cards, see here:
https://wiki.archlinux.org/title/Hybrid_graphics
https://wiki.archlinux.org/title/NVIDIA_Optimus
I am having the same issue. It happens in both XFCE and Cinnamon. If I log out of the desktop environment and log back in again, I can then open new windows normally with WIFI enabled. This happens consistently on my home network that have WEP security credentials saved by network manager. It does not happen right now on an open wifi network. I have run "pacman -Syyu" and it does not correct the problem as of a few hours ago.
My computer is using network manager and openrc. My video driver is amdgpu.
Here is dmesg:
https://paste.artixlinux.org/7cd6ef81
For some reason, I can't paste everything.log. The pastebin gives an error that it contains blocked words.
A word list was recently introduced to block pornographic material from being posted. One of them was "children", but I guess in UNIX processes spawn lots of them and tell syslog about it. You can re-try now.
I am so glad that someone else is having this problem, I missed this thread in September and thought that it must be only me that was having the problem!
I too have an amdgpu in this new laptop and I am wondering if that is the problem?
My system is:
System: Host: mc-NL5xNU Kernel: 5.14.16-artix1-1 x86_64 bits: 64 Desktop: LXQt Distro: Artix Linux
Machine: Type: Laptop System: Notebook product: NL5xNU v: N/A serial: N/A
Mobo: Notebook model: NL5xNU serial: N/A UEFI: INSYDE v: 1.07.07 date: 10/15/2020
Battery: ID-1: BAT0 charge: 48.1 Wh (100.0%) condition: 48.1/49.4 Wh (97.3%)
CPU: Info: 8-Core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP cache: L2: 4 MiB
Speed: 1862 MHz min/max: 1400/1800 MHz Core speeds (MHz): 1: 1862 2: 1397 3: 1397 4: 1397 5: 1396 6: 1397 7: 1397
8: 1406 9: 1397 10: 1397 11: 1397 12: 1397 13: 1418 14: 1397 15: 1397 16: 1397
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Lucienne driver: amdgpu v: kernel
Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo
Display: x11 server: X.org 1.21.1.1 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa
resolution: <missing: xdpyinfo>
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A
Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.14.16-artix1-1 running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eth0 state: down mac: 80:fa:5b:9d:3b:e1
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
IF: wlan0 state: up mac: 48:51:c5:9d:94:be
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Drives: Local Storage: total: 298.1 GiB used: 4.89 GiB (1.6%)
ID-1: /dev/nvme0n1 model: 256GB PCS PCIe M.2 SSD size: 238.47 GiB
ID-2: /dev/sda type: USB vendor: Lexar model: USB Flash Drive size: 59.62 GiB
Partition: ID-1: / size: 57.21 GiB used: 4.89 GiB (8.5%) fs: ext4 dev: /dev/sda2
ID-2: /boot/efi size: 1.19 GiB used: 296 KiB (0.0%) fs: vfat dev: /dev/sda1
Swap: Alert: No swap data was found.
Sensors: System Temperatures: cpu: 36.2 C mobo: N/A gpu: amdgpu temp: 33.0 C
Fan Speeds (RPM): N/A
Info: Processes: 326 Uptime: 24m Memory: 14.99 GiB used: 1.45 GiB (9.7%) Shell: Bash inxi: 3.3.08
I can post logs if necessary to help.
EDIT: This happens with both openrc and dinit versions of LXQT.
None of you have posted any relevant logs, except from that one inxi log. Post /var/log/everything.log and /var/log/dmesg.log. Of course not in the body of the post, use paste.artixlinux.org and put the URLs of the pastes here.
It would also be helpful to open a terminal and start an X program from that terminal, to see the error messages. For example, for XFCE:
$ atril >atril-output.log 2>&1
and then post atril-output.log. Substitute atril above with the name of the X program's executable. In the case of LXQt, you can use:
$ pcmanfm-qt >pcmanfm-output.log 2>&1
If you can't open a terminal, log out and then back in (as per
@matt_'s post above) to temporarily clear the issue, then (
if testing XFCE) create a file ~/atril-test:
#!/bin/sh
atril >~/atril-output.log 2>&1
execute:
$ chmod 755 ~/atril-test
and create a launcher in XFCE. Next to "Command:" field, open browser and navigate to the file atril-test in your home directory. Save, then reboot and activate the said launcher. Press "Launch Anyway" and then post atril-output.log from your home directory (if it is nonempty).
Similar method could be used on LXQt, just instead of atril, use for example pcmanfm-qt.
@STRADJER
https://paste.artixlinux.org/view/6672226c
https://paste.artixlinux.org/view/c10fb50c
https://paste.artixlinux.org/view/1c5a1159
https://paste.artixlinux.org/view/2e6a86ac
https://paste.artixlinux.org/view/70cd8b6e
https://paste.artixlinux.org/view/37ff2118
https://paste.artixlinux.org/view/9efb3b1a
Apologies for the delay in replying, I have been very busy at work.
Those are the logs you requested, the plain everything.log and dmesg are from the live LXQT Openrc, the 'no_wifi' and 'with_wifi' are from the subsequent installed version.
In my case, I cannot launch any programs or login or out with wifi running, the application menu will open but all items are unresponsive. As soon as I disconnect the wifi, everything returns to normal.
The pcmanfm-qt text is copied from the terminal and shows the result of the commands when connected to wifi and disconnected from wifi.
I hope this is of use in locating the problem.
This seems to be a problem with NetworkManager managing hostname. This is a post from 2010 from Arch forum which describes the problem:
https://bbs.archlinux.org/viewtopic.php?pid=684936#p684936
The configuration file name and format have since changed, but NetworkManager still wants to be too smart for its own good. You can try to set the parameter
hostname-mode to
none instead, as per this answer:
https://unix.stackexchange.com/a/513413
This is one of the reasons why "user friendly" programs are bad: you might not know exactly what they are programmed to do in certain situations. The more "user friendly" a program is, the less control a user has over it. Personally, I use only wpa_supplicant for WiFi.
Proposed solution: Edit /etc/NetworkManager/NetworkManager.conf by adding/changing:
[main]
plugins=keyfile
hostname-mode=none
For more information:
man 5 NetworkManager.conf
Thank you so much @STRAJDER, your proposed solution has worked perfectly!
And I take your point about 'user friendly' programs, they can be too clever.
Thank you! I can confirm this solved the problem for me as well.