[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-ports
Subject:    Re: Gnome 3 (gnome-shell) crash on initialization on an x61s with Intel 965 x3100 display
From:       Justin Haynes <justin () justinhaynes ! com>
Date:       2016-07-29 8:31:53
Message-ID: CANSK4GDkxkh=wu9gN6BEnAs0JVFK9KBLBjHULeOsSTyNa95SHQ () mail ! gmail ! com
[Download RAW message or body]

I may need to start following current.  I'm seeing a theme in development
where mesa has to be replaced and patched to address various problems...  I
wanted to fire up gnome3 so I can try using google drive as a filesystem.
I may put this on hold and try it later.

I'm pretty thrilled with the new WindowMaker..

On Fri, Jul 29, 2016 at 3:29 AM, Justin Haynes <justin@justinhaynes.com>
wrote:

> I consolidated /usr/local onto /usr becuase of a sizing issue.  Actually,
> in liu of resizing, I moved files, deleted slices and then created a larger
> /usr and smaller /home to accomodate more programs.  So I just checked and
> /usr doesn't have suid:
> 
> ff18b54934f6a0f8.f /usr ffs rw,nodev 1 2
> 
> And speaking of permissions, I did check /etc/fbtab to amd made sure
> /dev/drm0 was being owned by me so that drm would work in X:
> 
> /dev/ttyC0      0600
> /dev/console:/dev/wskbd:/dev/wskbd0:/dev/wsmouse:/dev/wsmouse0:/dev/ttyCcfg:/dev/drm0:/dev/drm1:/dev/drm2:/dev/drm3
>  
> and i confirmed with glxgears and other programs that demand 3d graphics
> as well. During on one of my previous tests, I must not have started from
> the first virtual terminal, so I was getting permissions errors on drm, and
> graphics were running very slowly.  This was why.
> 
> -Justin
> 
> On Fri, Jul 29, 2016 at 2:25 AM, David Dahlberg <
> david.dahlberg@fkie.fraunhofer.de> wrote:
> 
> > Am Freitag, den 29.07.2016, 00:26 -0500 schrieb Justin Haynes:
> > 
> > > The problem is that when i attempt ot start Gnome using gdm, I get
> > > nothing
> > > but X Windows with a black background and the X mouse cursor.
> > 
> > Had a similar problem lately.
> > 
> > Please check fstab(5), whether you have nosuid configured to /usr/local.
> > Seems something changed recently, such that slock, gnome-settings-daemon
> > and (gnome|gdm)-session-something need suid.
> 
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread]