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:
Just a note - I checked now and it does not happen when I start the XFCE or GNOME sessions by logging in using lightdm.
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
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.
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.
(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.
Status comment: (none) => Related to gnome-keyring apparently.CC: (none) => gnomeAssignee: bugsquad => mageia
This no longer happens on my system. Can we close it?