G-io-error-quark
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more error initializing authority could not connect no such file or directory (g-io-error-quark 1) about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask error getting authority centos 7 Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up ubuntu error getting authority g-io-error-quark Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1) error getting authority error initializing authority centos 7 up vote 13 down vote favorite 4 I just got this error from Kubuntu 15.x when starting up after restart to upgrade kernel. Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1) PS. Please note this is not a duplicate of: 'starting version 219' bug after the 15.04 update while the error message is similar, the root cause is different (which is example of terrible design if you ask me). kubuntu systemd share|improve
G-io-error-quark 1 Centos 7
this question edited Oct 8 '15 at 13:09 asked Jun 2 '15 at 14:48 Marcin Raczkowski 439148 add a comment| 4 Answers 4 active oldest votes up vote 27 down vote accepted The reason for this error was entry in /etc/fstab that pointed to partition UUID that was no longer existing (after i reformated one of the hard drives). The solution was to remove the fstab entry. NOTHING AT ALL in the error message indicates what might be the cause of the error, neither does calling journalctl as systemd suggest. Browsing the internet revealed that the exact same error can be produced in several different situations. Take a look at 'starting version 219' bug after the 15.04 update for other causes. Googling for the phrase returns few other possible causes. Hope it helps anyone who stumbles upon this cryptic error. share|improve this answer answered Jun 2 '15 at 14:48 Marcin Raczkowski 439148 2 I also encountered this with Fedora 22. –John Schmitt Aug 20 '15 at 21:34 Happened on Antergos(Archlinux) Thank you –Sam Sep 23 '15 at 3:37 Thank you for the info, got it from dual boot windows 10 (reboot) and Ubuntu 15.10 –TungstenX Jan 8 at 11:34 1 Just wanted to add my two cents, that it can be caused by not shutting down Windows 8, 8.1 or 10 without the new fast-boot feature. –HackerFinn Feb 24 a
to Milestone Light Display Manager Edit New Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: Light Display Manager
Error Getting Authority Error Initializing Authority Could Not Connect
Filed here by: Joolz When: 2015-06-08 Target Distribution Baltix BOSS Juju error getting authority error initializing authority g-io-error-quark Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build g-io-error-quark, 24 Ubuntu RTM Package (Find…) Project (Find…) Status Importance New Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project http://askubuntu.com/questions/631362/error-getting-authority-error-initializing-authority-could-not-connect-no-suc (?) Also affects distribution/package Nominate for series Bug Description On a complete clean install of 15.04 32bits on an Asus eee which used to work allright for a few days, I now have an issue. The system will not start the GUI, I land in emergency mode which says "Error getting authority: Error initializing authority: Could not connect: No such https://bugs.launchpad.net/bugs/1463116 file or directory (g-io-error-quark, 1)" and suggests to ^D to attempt to boot into default mode When I do this, GUI login is possible and the system works fine. However, shutting down brings me back to the emergency shell and I have to power down with the hardware button. I tried `sudo systemctl enable lightdm` but that gives me: Synchronizing state for lightdm.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d lightdm defaults Executing /usr/sbin/update-rc.d lightdm enable The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). So I tried `sudo dpkg-reconfigure lightdm` (as suggested by https://askubuntu.com/questions/614198/starting-version-219-bug-after-the-15-04-update and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607) which runs without errors but doesn't chang
zabrielza Member Registered: 2015-03-02 Posts: 125 [Solved]Error on boot, Emergency mode available only Hello, Yesterday I tried to configure Slim as my display manager. I changed only /etc/slim.conf and .xinitrc files. So, in the /etc/slim file https://bbs.archlinux.org/viewtopic.php?id=200772 I changed my username, and hashed out the line sessiondir# Set directory that http://forums.fedoraforum.org/showthread.php?t=307557 contains the xsessions. # slim reads xsesion from this directory, and be able to select. # sessiondir /usr/share/xsessions/.xinitrc file before changing it, contained this lineexec startfluxboxto start my fluxbox session and worked perfectlyafter changing it I placed this line[]exec $1[/]without knowing what it is :-$ So, After that I rebooted and then I am error getting getting try again to boot into default mode. Give root password for maintenance (or press Control-D to continue):Also I am getting this ErrorError getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)journalctl -p 3 -b givesfsck failed with error code 4 Failed to start File System Check on /dev/disk/by-uuid/2f5b7f54-cad1-4f7d-8290-2e50ae9f7382 emergency.service: Failed at step EXEC spawning /bin/plymouth: No such file or directory error getting authority fsck failed with error code 4.What is going on? I have two Drives one Hard Drive and one SSD. On the SSD I have / partition mainly and on the Hard Drive I have data etc. Is my SSD dead or something? How can I fix this prolem?Thanks in advance Last edited by zabrielza (2015-08-07 12:29:18) Offline #2 2015-08-07 07:33:53 esdaniel Member From: Paris Registered: 2010-02-01 Posts: 57 Website Re: [Solved]Error on boot, Emergency mode available only Seems you've had some bad luck and some data on the disk got corrupted. This can happen if cached data in memory hasn't been flushed to a disk and written before you turn off the computer.The fsck error pertains to "4 - File system errors left uncorrected".In maintenance mode, you should run fsck on the *unmounted* volume throwing the error:# fsck -AR -yWould be wise to read up on fsck before you actually run that though so you know what it's doing, in the example above it checks all filesystems except root filesystem and attempts to fix any errors discovered.If all is well and good then you can reboot and things should be back to normal. Offline #3 2015-08-07 12:28:18 zabrielza Member Registered
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Installation, Upgrades and Live Media F21 to F23 upgrade -> broken system FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Installation, Upgrades and Live Media Help with Installation, FedUp & Live Media (Live CD, USB, DVD) problems. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 11th November 2015, 11:28 PM njackson Offline Registered User Join Date: Nov 2015 Location: Canada Posts: 3 F21 to F23 upgrade -> broken system I attempted to upgrade my system today from Fedora 21 to Fedora 23 using the instructions at https://fedoraproject.org/wiki/DNF_system_upgrade. The upgrade seemed to go well. After it it wrote the message "Complete" (or words to that effect) it rebooted. Startup seemed normal up until the white pulsing shape of the Fedora logo turned blue. Then I immediately got the error message: "Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1) Welcome to emergency mode! ... ... (or press Control-D to continue):" Control-D takes me back to the usual white pulsing background to the Fedora logo, and as soon as it turns blue, I get the same error message again. I can authenticate at the emergency mode prompt, but I haven't tried anything there yet, other than shutting the system down. Where do I go from here? Any suggestions or pointers would be much appreciated. Do I file a bug report at this point even though I have no idea what's going on or do I have to isolate the problem first? Thank you in advance for any assistance. P.S. I perhaps should note that the "emergency mode ... Control-D" prompt is normal on my system at this stage of system start up. [I've been plagued by it ever since an update that came down soon after I upgraded to Fedora 21.] It follows