gnome-shell segfaults with @updates-testing/F18

[Onuralp SEZER]

Did you report the redhat.bugzilla.com. ? Also why did you enable "test"
repository ? Is there any reason for to do that ?


On 24 February 2013 19:47, Ozan Çağlayan <ozancag at gmail.com> wrote:

> Hi,
>
> Yesterday I did an update of my x86_64 F18 through updates-testing
> repository. Upon reboot, I got a blue background after gdm startup saying
> that things are going wrong, contact an administrator.
>
> In dmesg, there is segfaults for gnome-shell:
> gnome-shell[1229]: segfault at 88 ip 000000383f63f134 sp
> 00007fff5866c750 error 4 in libcogl.so.11.0.3[383f600000+8e000]
> I downgraded gnome-shell, cairo, xorg-* related updates but nothing fixed
> the situation.
>
> I'm using nouveau drm driver but today it happened also on my laptop with
> i915.
>
> I now distro-sync'ed to updates repository after disabling
> updates-testing and everything is OK.
>
> i googled but found nothing so this is really interesting that nobody
> encountered this.
>
> One more thing is that upon updating, the logged-in gnome3 desktop starts
> to show weird symptoms. icons disappear, evince can't open pdf files, gtk
> theme is rendered wrongly, etc.
>
> Attached is the yum transaction that causes the problem.
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>



-- 





----------------------
Onuralp SEZER
Fedora Ambassadors <http://fedoraproject.org/wiki/Ambassadors>
EMEA<http://fedoraproject.org/wiki/Ambassadors/EMEA> Member
/ Turkey
Fedora Translations Turkish Team
Member<https://fedora.transifex.net/projects/p/fedora/team/tr/>
Fedora Design Member <http://fedoraproject.org/wiki/Design>
---- Monster.inc Notebook ----
Fedora 18 Gnome-shell MONSTER Notebook
Nvidia GeForce GTX 680M with Optimus and Intel Ivy Bridge
Intel® Core™ i7-3720QM CPU @ 2.60GHz × 8
4x4 GB Kingston HyperX KIT CL11 1866 MHZ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130224/cc6304f2/attachment.html>