On 04/02/2016 04:16 PM, Gordan Bobic wrote: > On 02/04/16 00:37, Jacco Ligthart wrote: >> Hi all, >> >> I finally got to the source of the gnome bug in 7.2 >> It was indeed, as I previously mentioned, llvm related. I made a package >> for a newer version of mesa-private-llvm (3.7.1 vs 3.6.2) and rebuild >> mesa-10.6 to build against the new llvm version. Both sets of packages >> can be found in the extra repo of 7.2 >> (http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7-devel/el7/7.2/extra/) >> > > Awesome. How did you pin it down to broken llvm? This kind of bug that > is one step removed can be really hard to get to the bottom of.
slowly updating, until I had a set of updates left which would trigger the bug. At this point I noticed that just updating mesa-dri-drivers/mesa-private-llvm would also trigger the bug. Which made mesa suspect. After some googling I found this rhel 7.2 for arm release notes: https://access.redhat.com/sites/default/files/attachments/red_hat_enterprise_linux_server_for_arm-7.2_beta-release_notes-en-us.pdf with this text: 15.1. OpenGL applications fail to start Any program which requires OpenGL, including GNOME Shell, will fail to work due to a bug in the mesa-private-llvm package. The only way to run a graphical interface (GNOME) on the 64-bit ARM architecture is currently to connect to the system remotely using a VNC client. >From here on I did test the new gnome over VNC, which worked. I could not find a specific bug report or patch for the issue we were seeing, so I just tried the next version of llvm. I guess the work around is short-lived as I saw requests for gnome 3.18 and llvm 3.8 on redhat's bugzilla. Jacco _______________________________________________ users mailing list [email protected] https://lists.redsleeve.org/mailman/listinfo/users
