Bug 17308

Summary:	[6-sta1] LiveDVD "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)"
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	Release (media or process)	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, marja11, pkg-bugs, sysadmin-bugs
Version:	Cauldron	Keywords:	6sta1, NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Ben McMonagle 2015-12-07 22:06:46 CET

Description of problem: Write Mageia-6-dev1-LiveDVD-PLASMA5-x86_64-DVD.iso
DATE.txt: Sun Dec  6 13:30:00 CET 2015 to either USB or optical media. boot  and select "Boot Mageia" or "Install Mageia". a few minutes later several lines of "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)" are displayed.


Version-Release number of selected component (if applicable):


How reproducible:every time


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Ben McMonagle 2015-12-12 03:47:35 CET

Whiteboard: (none) => Mga6dev1

Florian Hubold 2015-12-13 16:06:02 CET

CC: (none) => doktor5000

Samuel Verschelde 2015-12-14 10:52:03 CET

CC: (none) => pkg-bugs
Assignee: bugsquad => tmb

Samuel Verschelde 2015-12-14 10:52:20 CET

CC: (none) => sysadmin-bugs
Component: Installer => Release (media or process)
Summary: Mga6dev1 "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)" => Mga6dev1 LiveDVD "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)"

Comment 1 Ben McMonagle 2016-01-20 07:04:13 CET

valid for both live plasma5 dvd i586 and x86 dated 17 Jan 2016

to continue installation: tty2 => login as root => systemctl stop sddm.service,=> run drakx11, => tty2 again => systemctl start sddm.service

Comment 2 Ben McMonagle 2016-01-28 08:22:51 CET

a simpler work-a-round

ctrl+alt+F2 [tty2?]
login as "root"
at the prompt: "drakx11", set up x-server, monitor and resolution, then "ok"
at the prompt: "systemctl restart sddm"

output from lspcidrake -v | grep Card

$  lspcidrake -v | grep Card
Card:Intel 810 and later: Intel Corporation|Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0152 subv:1043 subd:84ca) (rev: 09)

integrated graphics asus mobo; P8B75M-LX

Summary: Mga6dev1 LiveDVD "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)" => [Mga6-dev1] LiveDVD "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)"

Comment 3 Marja Van Waes 2016-04-05 19:33:44 CEST

Is this bug still valid for the released 6dev1 isos?

Keywords: (none) => 6dev1, NEEDINFO
CC: (none) => marja11
Whiteboard: Mga6dev1 => (none)

Comment 4 Ben McMonagle 2016-04-05 22:12:22 CEST

its for a live dvd, and no new ones yet.
will keep an eye on it

Comment 5 Ben McMonagle 2016-05-10 08:42:23 CEST

(In reply to Marja van Waes from comment #3)
> Is this bug still valid for the released 6dev1 isos?

sorry for the long delay - been testing the Classicals.

improvements: now eventually does get to the desktop with no user intervention.

However, the 1/2 page of recurring : "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)"  is still displayed part way through the boot up. 

so,  still valid for, from DVD:

Mageia-6-sta1-LiveDVD-PLASMA5-i586-DVD.iso
DATE.txt: Mon May  2 08:30:00 CEST 2016

Keywords: 6dev1 => 6sta1
Summary: [Mga6-dev1] LiveDVD "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)" => [6-sta1] LiveDVD "Error getting authority: error initializing authority:Could not connect: No such file or directory (g-io-error-quark, 1)"

Comment 6 Ben McMonagle 2017-03-22 04:06:47 CET

no longer a problem

Status: NEW => RESOLVED
Resolution: (none) => FIXED