From: Catonano <catonano@gmail.com>
To: ng0 <contact.ng0@cryptolab.net>
Cc: 25689@debbugs.gnu.org
Subject: bug#25689: gnome-shell segfaults
Date: Fri, 3 Mar 2017 10:02:52 +0100 [thread overview]
Message-ID: <CAJ98PDwD0q+9HeNWJNfJiukvVuQobou0q4pg9qvS3F0QLpWTcA@mail.gmail.com> (raw)
In-Reply-To: <20170211143110.6wmqw5iqm6stykhn@wasp>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2086 bytes --]
next prev parent reply other threads:[~2017-03-03 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 14:31 bug#25689: gnome-shell segfaults ng0
2017-03-03 9:02 ` Catonano [this message]
2017-03-03 11:20 ` ng0
2018-03-12 13:53 ` Ludovic Courtès
2020-09-19 4:47 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDwD0q+9HeNWJNfJiukvVuQobou0q4pg9qvS3F0QLpWTcA@mail.gmail.com \
--to=catonano@gmail.com \
--cc=25689@debbugs.gnu.org \
--cc=contact.ng0@cryptolab.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).