Bug 783703

Summary:	long delay at login, libgobject-2.0.so.0: undefined symbol: g_bytes_unref
Product:	[openSUSE] openSUSE 12.1	Reporter:	Rihards Olups <richlv>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P4 - Low	CC:	forgotten_SxCIMBZqeN
Version:	Final
Target Milestone:	---
Hardware:	32bit
OS:	openSUSE 12.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Rihards Olups 2012-10-05 12:24:17 UTC

User-Agent:       Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.289 Version/12.02

opensuse 12.1 appliance, built today.

there is a long delay when logging in the console, after entering the password. sometimes it's some 10 seconds, sometimes it completely times out after 15 seconds and i have to log in again. after that logins are instant.

/var/log/messages seems to contain relevant information :

Oct  5 15:09:33 linux-77jr systemd-logind[436]: New user root logged in.
Oct  5 15:09:33 linux-77jr systemd-logind[436]: New session 1 of user root.
Oct  5 15:09:33 linux-77jr dbus-daemon[544]: dbus[544]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Oct  5 15:09:33 linux-77jr dbus[544]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Oct  5 15:09:33 linux-77jr console-kit-daemon[2431]: /usr/sbin/console-kit-daemon: symbol lookup error: /usr/lib/libgobject-2.0.so.0: undefined symbol: g_bytes_unref
Oct  5 15:09:33 linux-77jr systemd[1]: console-kit-daemon.service: main process exited, code=exited, status=127
Oct  5 15:09:33 linux-77jr systemd[1]: Unit console-kit-daemon.service entered failed state.
Oct  5 15:09:58 linux-77jr dbus-daemon[544]: dbus[544]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
Oct  5 15:09:58 linux-77jr dbus[544]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out


if i have an ssh session open and attempt a login, i can see that the slowdown is specifically between these two lines:

Oct  5 15:23:02 linux-77jr systemd[1]: Unit console-kit-daemon.service entered failed state.
<pause is here>
Oct  5 15:23:27 linux-77jr dbus[544]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 2 Forgotten User SxCIMBZqeN 2013-02-23 07:00:41 UTC

I have an X_64 Processor wt Quad core and 4Gig or RAM taking more than 5 mins to load the default KDE windowing manager - OMG! Its worse than Windoze 8. Any other instabilities in the windowing Manager create an issue where the PC cannot be restarted or stopped via default kickoff Launcher. It appears that after any early forced termination of any Window/app the kickoff menu freezes on first click...Not only can you not shut the PC down - you cannot access any application after a forced closure of a process...Only way is to perform CTRL+DEL+Backspace x 2 and shutdown from shell ...please tell me what logs may help you.

Comment 3 Rihards Olups 2013-02-23 11:44:22 UTC

it is likely that this was caused by messed up upgrade state in suse studio, closing

Comment 4 Forgotten User SxCIMBZqeN 2013-02-23 11:53:21 UTC

(In reply to comment #3)
> it is likely that this was caused by messed up upgrade state in suse studio,
> closing

The install was based on a NEW Install and not an upgrade.
It is NOT acceptable that 11.4 loads in 90 seconds and a more advanced 12.1 takes 5 minutes.

Waat an outrageous cop-out

If you know the cause ...then fix it..otherwise what are we all doing here.

QA. Define acceptable closer as wontfix

Comment 5 Rihards Olups 2013-02-23 12:07:20 UTC

please do not piggyback on unrelated bugreports. this was my report about a specific issue on console login about library version incompatibility.
on a system without x11 even installed.

Comment 6 Forgotten User SxCIMBZqeN 2013-02-24 02:24:04 UTC

My Apologies I should have perhaps voted or spoken to you offline