From mboxrd@z Thu Jan  1 00:00:00 1970
From: Catonano <catonano@gmail.com>
Subject: bug#25689: gnome-shell segfaults
Date: Fri, 3 Mar 2017 10:02:52 +0100
Message-ID: <CAJ98PDwD0q+9HeNWJNfJiukvVuQobou0q4pg9qvS3F0QLpWTcA@mail.gmail.com>
References: <20170211143110.6wmqw5iqm6stykhn@wasp>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary=f4030438914096fd0a0549cfcf0d
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48090)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1cjj7B-0004yo-8s
	for bug-guix@gnu.org; Fri, 03 Mar 2017 04:03:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1cjj78-0006Q2-3g
	for bug-guix@gnu.org; Fri, 03 Mar 2017 04:03:05 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:39189)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1cjj77-0006Ps-Vm
	for bug-guix@gnu.org; Fri, 03 Mar 2017 04:03:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1cjj77-0005f8-OS
	for bug-guix@gnu.org; Fri, 03 Mar 2017 04:03:01 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.25689.B25689.148853178021758@debbugs.gnu.org>
In-Reply-To: <20170211143110.6wmqw5iqm6stykhn@wasp>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: ng0 <contact.ng0@cryptolab.net>
Cc: 25689@debbugs.gnu.org

--f4030438914096fd0a0549cfcf0d
Content-Type: text/plain; charset=UTF-8

2017-02-11 15:31 GMT+01:00 ng0 <contact.ng0@cryptolab.net>:

> So, I am not 100% sure if I encouter hardware failures or software
> failures here. But I need to solve wether this is a GNOME bug to exclude
> or include the hardware failure.
>
> The following is the log output of a session with SSDM where I
> succesfully log into "GNOME with Xorg" and launch the GNOME-Terminal
> after I logged into GNOME.
>
> The visual side of the log can be described like this: I can see how
> the terminal application opens, but just a milisecond after it's ready I
> see the window decoration disappearing, content of the application
> stays, GNOME session crashes, on a dark scree I see for a moment:
>
> vmunix: [  226.579414] nouveau 0000:01:00.0: DRM: 0xD4A7: Parsing digital
> output script table
>
> and I get thrown back to the log in screen of SDDM.
>
> Occasionally gnome-terminal or some other gnome part would crash my
> gnome session when I still used SLIM.
>
> This is on commit 883aab6462c49d4f4846a6f22168325e70227663
> but has been happening for a very long time before this commit.
>

I use the Gnome terminal all the time and I can't confirm your
experience

CAVEATS:

1) I don't know whether I'm using SSDM or SLIM. I just took the basic
desktop conf file when I installed

2) this is my video card

~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)

~$ egrep -i " connected|card detect|primary dev|Setting driver"
/var/log/Xorg.0.log
[     7.760] (II) intel(0): Using Kernel Mode Setting driver: i915, version
1.6.0 20160919

--f4030438914096fd0a0549cfcf0d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">2017-02-11 15:31 GMT+01:00 ng0 <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:contact.ng0@cryptolab.net" target=3D"_blank">contact.ng0@crypt=
olab.net</a>&gt;</span>:<br><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">So, I am not 100% sure if I encouter =
hardware failures or software<br>
failures here. But I need to solve wether this is a GNOME bug to exclude<br=
>
or include the hardware failure.<br>
<br>
The following is the log output of a session with SSDM where I<br>
succesfully log into &quot;GNOME with Xorg&quot; and launch the GNOME-Termi=
nal<br>
after I logged into GNOME.<br>
<br>
The visual side of the log can be described like this: I can see how<br>
the terminal application opens, but just a milisecond after it&#39;s ready =
I<br>
see the window decoration disappearing, content of the application<br>
stays, GNOME session crashes, on a dark scree I see for a moment:<br>
<br>
vmunix: [=C2=A0 226.579414] nouveau 0000:01:00.0: DRM: 0xD4A7: Parsing digi=
tal output script table<br>
<br>
and I get thrown back to the log in screen of SDDM.<br>
<br>
Occasionally gnome-terminal or some other gnome part would crash my<br>
gnome session when I still used SLIM.<br>
<br>
This is on commit 883aab6462c49d4f4846a6f2216832<wbr>5e70227663<br>
but has been happening for a very long time before this commit.<br></blockq=
uote><div><br>I use the Gnome terminal all the time and I can&#39;t confirm=
 your<br>experience<br><br>CAVEATS:<br><br>1) I don&#39;t know whether I&#3=
9;m using SSDM or SLIM. I just took the basic<br>desktop conf file when I i=
nstalled<br><br>2) this is my video card<br><br>~$ lspci | grep VGA<br>00:0=
2.0 VGA compatible controller: Intel Corporation 3rd Gen Core<br>processor =
Graphics Controller (rev 09)<br><br>~$ egrep -i &quot; connected|card detec=
t|primary dev|Setting driver&quot; /var/log/Xorg.0.log<br>[=C2=A0=C2=A0=C2=
=A0=C2=A0 7.760] (II) intel(0): Using Kernel Mode Setting driver: i915, ver=
sion 1.6.0 20160919<br><br><br></div></div></div></div>

--f4030438914096fd0a0549cfcf0d--