Arch Linux

ArcticStag

Member

Registered: 2020-09-14

Posts: 46

[SOLVED] New install unable to StartX

Hi All,

I am having an issue with my new install. When I attempt to run startx

With the following .xinitrc

exec awesome

Linked here is my dmesg and my Xorg.1.log

dmesg
http://ix.io/3w48

Xorg Log
http://is.io/3w49

I am running AMD for the CPU so I installed the AMD-code and a GTX graphics card so I also installed the NVIDIA drivers
Not sure what I am missing in the logs that is causing the crash

TIA!

Last edited by ArcticStag (2021-08-15 12:12:28)

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: [SOLVED] New install unable to StartX

If that is your entire ~/.xinitrc then it is incorrect. Read the wiki page...
https://wiki.archlinux.org/title/Xinit#xinitrc

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

ArcticStag

Member

Registered: 2020-09-14

Posts: 46

Re: [SOLVED] New install unable to StartX

If that is your entire ~/.xinitrc then it is incorrect. Read the wiki page...

First, This is not helpful. All this backhanded comment about reading the wiki does is give the Arch Community a bad reputation. In this instance I have already read the wiki. I understand that I may not be using the most efficient xinitrc, however what I have used is not

incorrect.

as you so bluntly put it.

In this case, what would have been helpful was a second set of eyes to see that the call to Awesome was failing. I have resolved this issue. It seems i pressed N during the install of the awesome window manager during install after install my .xinitrc works perfectly without issue.

Thanks.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,088

Re: [SOLVED] New install unable to StartX

It isn't a backhanded comment, the xinitrc without doing the sourcing of the proper scripts can lead to  subtle errors even if you've  managed to start awesome now. To prevent future threads that wonder why some session tooling breaks it's better to make sure that your .xinitrc follows the proper common practice if you've made us aware that you currently doing it "unoptimally".