Bug 111813 - Ubuntu 18.04.3 + Mesa 19.3 = Login Loop
Summary: Ubuntu 18.04.3 + Mesa 19.3 = Login Loop
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: not set normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-25 09:09 UTC by Dirk Toewe
Modified: 2019-09-25 18:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Dirk Toewe 2019-09-25 09:09:34 UTC
Description
-----------
As of today with Oibaf's latest PPA update (19.3~git1909250730.88f909~oibaf~b), Ubuntu 18.04.3 is stuck in a login loop, i.e. after entering the password the desktop background is displayed for a second and then Gnome goes back to the login screen. According to /var/log/syslog, there are segementation faults happening when Gnome tries to access GLX.

Sep 25 09:07:58 kernel: [   10.405287] gnome-shell[1073]: segfault at 50 ip 00007f1d58939291 sp 00007ffe73daced0 error 4 in libGLX_mesa.so.0.0.0[7f1d588f0000+73000]
Sep 25 09:07:59 kernel: [   12.097378] gnome-shell[1323]: segfault at 50 ip 00007f3c427b1291 sp 00007ffef7af4e50 error 4 in libGLX_mesa.so.0.0.0[7f3c42768000+73000]

After reverting to the official Ubuntu repositories using PPA-Purge, the login works just fine. My experience with (debugging) native binaries let alone drivers is quite limited. Please let me know what else I can do to provide more info if needed.

Hardware
--------
AMD A10-7850K APU (Kaveri)
Comment 1 GitLab Migration User 2019-09-25 18:50:59 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1434.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.