Bug 16835

Summary:	chromium-browser takes a long time to start from a terminal in XFCE and GNOME in a new user
Product:	Mageia	Reporter:	Shlomi Fish <shlomif>
Component:	RPM Packages	Assignee:	Nicolas Lécureuil <mageia>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cjw, gnome, joequant
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	chromium-browser-stable-45.0.2454.99-1.mga6.src.rpm	CVE:
Status comment:	Related to gnome-keyring apparently.

Description Shlomi Fish 2015-09-26 19:12:32 CEST

Description of problem:

When using XFCE and GNOME in a new UNIX user account, or in my default one, and starting them using startx, then chromium-browser takes a long time to spring its windows from the terminal (xterm/etc.). It starts out extremely quickly on LXQT and JWM.

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

Cauldron.

How reproducible:

Always

Steps to Reproduce:
1. Create a new UNIX user account.
2. Log in to it using the virtual console.
3. Put startxfce4 in your ~/.xinitrc.
4. startx.
5. Start a new terminal.
6. Type "chromium-browser".
7. Wait.

Reproducible: 

Steps to Reproduce:

Comment 1 Shlomi Fish 2015-09-26 19:46:24 CEST

Just a note - I checked now and it does not happen when I start the XFCE or GNOME sessions by logging in using lightdm.

Comment 2 Samuel Verschelde 2015-09-28 11:36:12 CEST

Do you see anything meaningful in logs?

No maintainer for now for chromium-browser (well, officially dmorgan but he's inactive and unresponding). Adding some packagers in CC, notably cjw who looks like the de-facto maintainer.

Please assign to yourself if working on it.

CC: (none) => cjw, joequant

Comment 3 Shlomi Fish 2015-09-28 12:08:54 CEST

Hi Samuel,

(In reply to Samuel VERSCHELDE from comment #2)
> Do you see anything meaningful in logs?
> 

Which logs? How do I generate or view them? I can also provide the output of strace -f -ttt of chromium-browser.

Comment 4 Christiaan Welvaart 2015-09-28 12:16:43 CEST

This sounds like a problem connecting to dbus or something similar. If you look at what chrome is doing (ps -elf, strace) it's probably waiting on some socket. You may need to ltrace chromium to see what it's trying to do, but I haven't had much luck with that tool the last time I used it.

Comment 5 Shlomi Fish 2015-09-28 14:40:18 CEST

(In reply to Christiaan Welvaart from comment #4)
> This sounds like a problem connecting to dbus or something similar. If you
> look at what chrome is doing (ps -elf, strace) it's probably waiting on some
> socket. You may need to ltrace chromium to see what it's trying to do, but I
> haven't had much luck with that tool the last time I used it.

Thanks for the lead . After some investigation, I found a workaround:

1. Run "pkill -9 gnome-keyring" as root.

2. Run â/usr/bin/gnome-keyring-daemon --start --foreground --components=secretsâ in a terminal window as the user that ran startx.

3. Now chromium-browser starts normally from the terminal.

I also found out that the problem does not happen in an x86-64 Debian Testing VM.

Samuel Verschelde 2016-11-03 11:37:33 CET

Status comment: (none) => Related to gnome-keyring apparently.
CC: (none) => gnome
Assignee: bugsquad => mageia

Comment 6 Shlomi Fish 2019-06-07 21:56:54 CEST

This no longer happens on my system. Can we close it?