Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 13
stuck at boot screen journalctl -b output : failed to open private bus cnnection:failed to connect to socket /run/user/1000/dbus/user_bus_socket:no such file and systemctl --user: failed to get D-bus connection:unable to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Apr 2014
    Posts
    8

    fedora 20 freezes at logo


    stuck at boot screen

    journalctl -b output :

    failed to open private bus cnnection:failed to connect to socket /run/user/1000/dbus/user_bus_socket:no such file
    and systemctl --user:

    failed to get D-bus connection:unable to autolaunch a dbus-daemon without a $display fo X11
    what do i do?

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,655
    Has this been working in the past? If not, then reinstall the OS AFTER running a check sum on the image to be sure that it was not corrupted, although Fedora/RedHat/CentOS and such systems usually have a "scan and validate installation media" option that will do that for you. If it has been working, then think back on what you did just before you rebooted and this occurred. In such a case, you may be able to recover the system, or at least backup your user data with a Live CD/DVD/USB drive.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Apr 2014
    Posts
    8
    yes,it worked in the past.Before I rebooted I tried to run 'nautilus .' ,this gave me some error something related to dbus.I tried to fix it with the help of some instructions on forums ,in that process i believe I set the environment variable DISPLAY to '0'.Realizing that could be the mistake I unsetted it later .

    UPDATE

    after setting the display variable again ,systemctl --user gave :
    failed to issue method call : process /bin/false exited with status 1
    Last edited by prudhvi09; 04-04-2014 at 04:05 AM.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,655
    So, what did you change your DISPLAY environment variable to? Normally it should be :0.0
    Also, how did you set/reset the variable? Finally, have you tried booting into text mode, logging in (under your normal user account), and run the startx command? If so, please post the errors here.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  6. #5
    Just Joined!
    Join Date
    Apr 2014
    Posts
    8
    I tried booting in text mode as you said and ran startx command.It booted normally (i see my workspace),I dont see any errors .Is there a way to check errors?
    I dont think there is anything to do with the DISPLAY variable ,I checked it by printenv its value is ':0'
    Last edited by prudhvi09; 04-04-2014 at 06:11 PM.

  7. #6
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,655
    Well, this is good news. It means that your system is mostly intact. Try booting again into GUI mode (runlevel 5). A DISPLAY variable of :0 is more or less the same as :0.0
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  8. #7
    Just Joined!
    Join Date
    Apr 2014
    Posts
    8
    I tried init 5, just got a black screen

  9. #8
    Just Joined!
    Join Date
    Apr 2014
    Posts
    8
    Is it possible that startup services are causing this?or corrupt drivers?
    Is reinstallation of OS only option now?

  10. #9
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,655
    Since you can start the GUI from a text command-line, then the OS and the drivers are correct. There is a problem with the GUI boot process. Until you figure out how to fix that, I would recommend booting into runlevel 3, logging in, and then running startx. At least with those little extra steps (none, really), you can work as normal. You just won't get that nice GUI login page!

    IE, never let stupid sh!t interfere with getting your work done!
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  11. #10
    Just Joined!
    Join Date
    Apr 2014
    Posts
    8
    I wouldn't mind working in text mode,the problem is my browser is not opening in here .I get this error-

    Glib-Critical **: g_slice_set_config: assertion 'sys_page_size=0' failed
    error: Platform version '27.0' is not compatible with
    minVersion >=25.0
    maxVersion <= 25.0
    Has this got anything to do with graphics?

    After little time of trying to open firefox I get this alert -
    SELinux Alert Browser
    the source process: /usr/bin/systemd-tmpfiles
    Attempted this access:net_admin
    details window says
    selinux is preventing /usr/sbin/systemd-tmpfiles from using the net_admin capability

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •