Re: gnome-shell segfault

Alexander Tsoy <alexander-EP/[email protected]>
Newsgroups gmane.linux.gentoo.hardened
Message-ID <[email protected]>
В Sun, 12 May 2013 21:14:29 -0600
Stan Sander <[email protected]> пишет:

> I doubt this is specifically a hardened issue, but this is the only list
> I'm currently subscribed to and I know there are some very savvy folks
> who hang out here.  I've been poking at this issue off and on for a
> couple of months (kind of hoping that an update would take care of the
> problem), but it hasn't so here are the details. 
> 
> I decided to give gnome a try (I've never used anything other than KDE
> on this system) on my ~amd64 desktop so I emerged the meta package with
> the USE flags of my liking, enabled the gnome USE flag globally and let
> the system build away.   My problem is gnome-shell segfaults.  I get a
> blue background with vertical stripes that sort of reminds me of a
> curtain.  After a few seconds I see the message that something has gone
> wrong and I have to log out.  I've done some google searches and tried
> all sorts of things that have worked for others with similar symptoms
> but none have helped here.  Also many emerge -auvND and revdep-rebuilds
> have been done since I first attempted to run gnome.  Mesa has gallium
> enabled and eselected since I'm using an ATI video card.  I've toyed
> around with the idea of a bug report, but decided to try here first. 
> 
> backtrace is attached
> 
> Log files of the most recent attempt show the following:
> 
> May 12 20:35:08 siren dbus[1897]: [system] Rejected send message, 2
> matched rules; type="method_call", sender=":1.226" (uid=500 pid=15249
> comm="/usr/bin/gnome-shell ")
> interface="org.freedesktop.DBus.Properties" member="GetAll" error
> name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=1912
> comm="/usr/sbin/console-kit-daemon ")
> May 12 20:35:08 siren polkitd[1991]: Registered Authentication Agent for
> unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name
> :1.226 [/usr/bin/gnome-shell], object path
> /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
> May 12 20:35:08 siren dbus[1897]: [system] Rejected send message, 2
> matched rules; type="method_call", sender=":1.226" (uid=500 pid=15249
> comm="/usr/bin/gnome-shell ")
> interface="org.freedesktop.DBus.Properties" member="GetAll" error
> name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=1912
> comm="/usr/sbin/console-kit-daemon ")
> May 12 20:35:09 siren gnome-session[15161]: WARNING: Application
> 'gnome-shell.desktop' killed by signal 11
> May 12 20:35:10 siren dbus[1897]: [system] Rejected send message, 2
> matched rules; type="method_call", sender=":1.230" (uid=500 pid=15358
> comm="/usr/bin/gnome-shell ")
> interface="org.freedesktop.DBus.Properties" member="GetAll" error
> name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=1912
> comm="/usr/sbin/console-kit-daemon ")
> May 12 20:35:11 siren polkitd[1991]: Registered Authentication Agent for
> unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name
> :1.230 [/usr/bin/gnome-shell], object path
> /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
> May 12 20:35:11 siren dbus[1897]: [system] Rejected send message, 2
> matched rules; type="method_call", sender=":1.230" (uid=500 pid=15358
> comm="/usr/bin/gnome-shell ")
> interface="org.freedesktop.DBus.Properties" member="GetAll" error
> name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=1912
> comm="/usr/sbin/console-kit-daemon ")
> May 12 20:35:11 siren gnome-session[15161]: WARNING: Application
> 'gnome-shell.desktop' killed by signal 11
> May 12 20:35:11 siren gnome-session[15161]: WARNING: App
> 'gnome-shell.desktop' respawning too quickly
> 

Hello!

Do you have errors like 'grsec: denied RWX mprotect of ...' in dmesg or
journal?

Also see this bug report:
https://bugs.gentoo.org/show_bug.cgi?id=455938

-- 
Alexander Tsoy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.