Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

startx: d-bus connection refused but xinit command issued by startx works

I am running fedora 28 with gnome. Rather than letting the system enter a gui-based login by default, I have set the systemd default target at "runlevel 3". From there, I normally launch the gui using "startx". Earlier this week I ran a dnf update, and either this update (or an earlier one prior to rebooting) has broken startx.

However, I wrote in an echo statement into /usr/bin/startx that tells me exactly what xinit command is being issued after the startx script determines things like $DISPLAY/xserver/xauth stuff to contruct the xinit command to be issued at the end of the startx script.

Manually typing in the xinit command (exactly as constructed within startx) starts things off perfectly.

I looked up the issue online, and there were suggestions that xinit needed to be setuid, which I discovered is _not_ the problem. Setting it setuid didn't solve the problem, I removed the permission after testing.

The rwx permissions on startx and xinit in /usr/bin are the same.

I have "semi solved" my problem in that I can get into gnome, however, I'd like to do it using startx instead of directly issuing the command that startx would have for me.

Does anyone have any ideas what could be causing this, or how to troubleshoot further?

I will try to update the exact error with startx unless someone happens to know what is going on and can help before I can :)

startx: d-bus connection refused but xinit command issued by startx works

I am running fedora 28 with gnome. Rather than letting the system enter a gui-based login by default, I have set the systemd default target at "runlevel 3". From there, I normally launch the gui using "startx". Earlier this week I ran a dnf update, and either this update (or an earlier one prior to rebooting) has broken startx.

However, I wrote in an echo statement into /usr/bin/startx that tells me exactly what xinit command is being issued after the startx script determines things like $DISPLAY/xserver/xauth stuff to contruct the xinit command to be issued at the end of the startx script.

Manually typing in the xinit command (exactly as constructed within startx) starts things off perfectly.

I looked up the issue online, and there were suggestions that xinit needed to be setuid, which I discovered is _not_ the problem. Setting it setuid didn't solve the problem, I removed the permission after testing.

The rwx permissions on startx and xinit in /usr/bin are the same.

I have "semi solved" my problem in that I can get into gnome, however, I'd like to do it using startx instead of directly issuing the command that startx would have for me.

Does anyone have any ideas what could be causing this, or how to troubleshoot further?

I Here is the error after launching startx:

xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /tmp/dbus-mizrpQmgcO: Connection refused GLib-GIO-Message: 21:26:51.283: Using the 'memory' GSettings backend. Your sett ings will try to update the exact error not be saved or shared with startx unless someone happens to know what is going on and can help before I can :)other applications.

* (process:2421): WARNING *: 21:26:51.490: Could not make bus activated client s aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Co nnection refused xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closi ng log file.

startx: d-bus connection refused but xinit command issued by startx works

I am running fedora 28 with gnome. Rather than letting the system enter a gui-based login by default, I have set the systemd default target at "runlevel 3". From there, I normally launch the gui using "startx". Earlier this week I ran a dnf update, and either this update (or an earlier one prior to rebooting) has broken startx.

However, I wrote in an echo statement into /usr/bin/startx that tells me exactly what xinit command is being issued after the startx script determines things like $DISPLAY/xserver/xauth stuff to contruct the xinit command to be issued at the end of the startx script.

Manually typing in the xinit command (exactly as constructed within startx) starts things off perfectly.

I looked up the issue online, and there were suggestions that xinit needed to be setuid, which I discovered is _not_ the problem. Setting it setuid didn't solve the problem, I removed the permission after testing.

The rwx permissions on startx and xinit in /usr/bin are the same.

I have "semi solved" my problem in that I can get into gnome, however, I'd like to do it using startx instead of directly issuing the command that startx would have for me.

Does anyone have any ideas what could be causing this, or how to troubleshoot further?

Here is the error after launching startx:

startx:
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

dbus-update-activation-environment: permitteddbus-update-activation-environment: error: unable to connect to D-Bus: Failed to to connect to socket /tmp/dbus-mizrpQmgcO: Connection refused refused GLib-GIO-Message: 21:26:51.283: Using the 'memory' GSettings backend. Your sett ings settings will not be saved or shared with other applications.

applications. * (process:2421): WARNING *: 21:26:51.490: Could not make bus activated client s clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Co nnection Connection refused xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closi ng Closng log file.file.