Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#50268 - [chromium] 52.x slow on startup

Attached to Project: Arch Linux
Opened by GH (stafuz) - Friday, 05 August 2016, 13:47 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 18 August 2016, 13:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Bartłomiej Piotrowski (Barthalion)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Chromium takes long time to start in a gnome desktop enviroment after relogging in.


Additional info:
* package version(s)
gnome 3.20.x
chromium 51.x to 52.x
* config and/or log files etc.


Steps to reproduce:
login to gnome
start chromium (start works fine)
restart chromium (shows up in seconds)
logout from gnome
login as a different user
restart chromium (very slow to show up) takes more than 60 sec
afterwards system is unstable (sometimes freezes)
have to killall Xorg to restore system stable state

This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 18 August 2016, 13:38 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Configuration issue
Comment by Doug Newgard (Scimmia) - Saturday, 06 August 2016, 06:34 GMT
Anything in the log for that time?
Comment by GH (stafuz) - Saturday, 06 August 2016, 06:52 GMT
here is log of that time seems gnome-session related!

08:55:55 kernel: snd_hda_intel 0000:01:00.1: CORB reset timeout#2, CORBRP = 65535
08:55:35 kernel: snd_hda_intel 0000:01:00.1: CORB reset timeout#2, CORBRP = 65535
08:55:34 kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
08:55:34 kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
08:54:52 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:52 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:52 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:52 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:45 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:45 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:45 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:54:45 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:52:21 python: backintime (betty/1): ERROR: Back In Time is not configured!
08:52:15 kernel: snd_hda_intel 0000:01:00.1: CORB reset timeout#2, CORBRP = 65535
08:51:43 kernel: snd_hda_intel 0000:01:00.1: CORB reset timeout#2, CORBRP = 65535
08:51:41 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:41 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:41 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:41 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:40 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:40 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:40 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:51:40 gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
08:50:49 kernel: snd_hda_codec_hdmi hdaudioC1D0: Unable to sync register 0x2f0d00. -5
Comment by Jan de Groot (JGC) - Sunday, 07 August 2016, 09:18 GMT
I see timeouts on snd-hda, looks like something is hanging on sound card access.
Comment by GH (stafuz) - Monday, 08 August 2016, 07:35 GMT
Yes, i confirm snd-hda device is lost after logging in and out of gnome with lightdm service.
NO idea what causes this! Only after restarting Xorg sound device is active and working.
Comment by GH (stafuz) - Monday, 08 August 2016, 11:21 GMT
Deleted monitors.xml file in the ~/.config dir.
Now it seems working. Do more testing.
Thanks!
Comment by GH (stafuz) - Monday, 08 August 2016, 16:09 GMT
Nothing. Soundcard comes and goes. I surrender!!!
Comment by Bartłomiej Piotrowski (Barthalion) - Monday, 08 August 2016, 19:44 GMT
Did you check if the same happens with GDM?
Comment by GH (stafuz) - Monday, 08 August 2016, 20:10 GMT
with gdm even worse. user login kills soundcard.
Comment by Bartłomiej Piotrowski (Barthalion) - Monday, 08 August 2016, 20:19 GMT
Anyway, it doesn't look like it's packaging issue. There are threads describing similar issue (google for these with "snd_hda_intel 0000:01:00.1: CORB reset timeout#2, CORBRP = 65535"). The best thing now would be opening thread on Arch forums so we can continue there with debugging.
Comment by GH (stafuz) - Thursday, 18 August 2016, 11:33 GMT
after playing around with pulsaudio settings problem seems solved! bug can be closed.
thanks

Loading...