Gnome Error Log File
Contents |
if you have a problem using GDM, you can submit a bug or send an email to the gdm-list mailing list. Information about how to do this is in the Introduction section of the document. If GDM is failing to work gnome log file properly, it is always a good idea to include debug information. To enable debugging, set the gnome log viewer debug/Enable key to "true" in the
Gnome Shell Extension Log
information and not the entire file since it can be large. If you do not see any GDM syslog output, you may need to configure syslog (refer to the syslog man page). 7.1. GDM Will Not Start 7.1. GDM Will Not Start There are a many problems that can cause GDM to fail to start, but this section will discuss a few common problems and how to approach tracking down a problem with GDM starting. Some problems will gdm log cause GDM to respond with an error message or dialog when it tries to start, but it can be difficult to track down problems when GDM fails silently. First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system. Also make sure that the /tmp directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start. GDM Commands License About Copyrights Copyright © 1998, 1999 Martin K. Petersen Copyright © 2001, 2003, 2004 George Lebl Copyright © 2003, 2007, 2008 Red Hat, Inc. Copyright © 2003, 2011 Oracle and/or its affiliates. All rights reserved. Legal Notice Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover
gnome-shell in Fedora 19? fedora19 gnome-shell logs asked 2014-04-26 11:24:03 +0000 bnsmb 21 ●1 ●1 ●3 updated gnome oh no something went wrong 2014-09-30 11:52:07 +0000 mether 7023 ●41 ●67 ●111 https://fedoraproject.org... My installed
Gnome-session-check-accelerated: Helper Exited With Code 256
gnome-shell extensions do crash very often but I do not know why e.g. sometimes after resume or even after the lock screen starts all extension do not work anymore. After ALT-F2 "r" everything is fine again. To find the reason for this error https://help.gnome.org/admin/gdm/stable/troubleshooting.html.en I need to take a look at the logfile from the gnome-shell I think. But there is neither ~/.xsession-errors nor ~/.cache/gdm/session.log in my user home directory. So: Where is the gnome-shell logfile in Fedora 19 for x86_64? regards Bernd edit retag flag offensive close merge delete 1 answer Sort by » oldest newest most https://ask.fedoraproject.org/en/question/45921/where-are-the-logs-from-the-gnome-shell-in-fedora-19/ voted 2 answered 2014-04-26 12:04:47 +0000 remjg 810 ●17 ●29 ●45 updated 2014-04-26 12:45:02 +0000 You need to use journalctl to retrieve the logs, use man journactl for more information since I don't know much about it. One of these commands might be useful for you: journalctl -b _SYSTEMD_UNIT=session-1.scope # log from current boot journalctl -b -1 _SYSTEMD_UNIT=session-1.scope # log from previous boot journalctl -b -2 _SYSTEMD_UNIT=session-1.scope # log from the boot before the previous boot... You could also try one of these (use the -b option to specify a specific boot): journalctl /usr/bin/gnome-shell journalctl /usr/bin/gnome-session edit flag offensive delete link more Your Answer Please start posting anonymously - your entry will be published after you log in or create a new account. Add Answer [hide preview] community wiki (karma is not awarded & many others can edit wiki post) Use your votes! Use the 30 daily voting points that you get! Up-vote well framed questions that provide enough information
1 #1 2013-04-11 12:05:31 mythus Member From: MS Gulf Coast Registered: 2008-05-15 Posts: 509 Website [Gnome 3.8] Can't log in, get the "Oh No Something Is Wrong" screen Greetings, My appologies if the thread title isn't sufficient, I really do not know how https://bbs.archlinux.org/viewtopic.php?id=161310 to title this.Anyway, seeing as Gnome 3.8 has hit testing, I decided to give it http://stackoverflow.com/questions/15608817/how-to-debug-on-gnome-shell-3-6-3-8-or-newer a try like a good little archer. I updated my computer and just to make sure I got everything, I ran pacman -S testing/gnome testing/gnome-extras, which install more things for gnome 3.8.I then rebooted and tried to log in to the newly updated gnome, but no dice. Instead, after a 2-4 minute wait I get the grey screen with the sad computer log file telling me " Oh no, Something is Wrong" and the only option is to log out.I tried clearing out gnome related files in /home, from /config and /local, and still no dice. I should mention that:1.) this is the 64 bit version2.) gnome 3.6 functioned fine3.) as KDE has been my main desktop for a while, I used KDM as my display managerAny ideas, suggestions, or demands for certain logs? Legends of Nor'Ova - role playing community gnome error log devoted to quality forum-based and table-top role play, home of the Legends of Nor'Ova Core Rule Book and Legends of Nor'Ova: Saga of Ablution steam punk like forum based RPG Offline #2 2013-04-11 12:11:22 HalosGhost Member From: Twin Cities, MN Registered: 2012-06-22 Posts: 1,486 Website Re: [Gnome 3.8] Can't log in, get the "Oh No Something Is Wrong" screen What errors do you see in `dmesg` and `journalctl -b`?All the best,-HG "All errors are ᴘᴇʙᴋᴀᴄ errors—It's just a matter of narrowing down which keyboard and chair." -Trilby\ldots Offline #3 2013-04-11 12:32:18 felipense Member Registered: 2013-04-05 Posts: 62 Re: [Gnome 3.8] Can't log in, get the "Oh No Something Is Wrong" screen I had the same issue with my old archlinux, have you installed systemd ? Or is a fresh install of archlinux? Try removing kde, kdm and using gdm. systemctl disable kdm.service pacman -Rsc kde pacman -S gnome gnome-extras gdm systemctl enable gdm.service restartif that not work try with xinit instead gdm see the wiki to know how configure. Last edited by felipense (2013-04-11 12:32:45) Offline #4 2013-04-11 12:36:13 mythus Member From: MS Gulf Coast Registered: 2008-05-15 Posts: 509 Website Re: [Gnome 3.8] Can't log in, get the "Oh No Something Is Wrong" screen Greetings,dmesg shows me a segfault with nepomukserver[579], error 4 in lbQtCore.so.4.8.4and....systemd-journald[109]: Failed to write entry, ignoring: Argument list too longjournalctl - b shows:WARNING: App 'gno
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to debug on GNOME Shell 3.6, 3.8 or newer up vote 2 down vote favorite I developed my own gnome-shell extension that worked on GNOME Shell 3.4 and GNOME Shell 3.6. It's not working on GNOME Shell 3.8 and I can't find out why because I don't know where to access to any logs. On GNOME Shell 3.4, using Looking Glass, there was a 'Error' tab that was removed on the 3.6 and 3.8 version, and I can't see any errors. On the extensions tab, clicking on 'show the errors' says 'no errors'. Launching the gnome-shell --replace for terminal doesn't show any errors either. But my extension is not displayed (the code is the same and works on GNOME 3.4 and 3.6). How can I debug this in order to find what's wrong with my code? Thanks! The extension: https://github.com/Softcatala/TraductorGnomeShell gnome-shell-extensions share|improve this question asked Mar 25 '13 at 6:20 PauGNU 4442926 add a comment| 3 Answers 3 active oldest votes up vote 5 down vote accepted All output is redirected to stout/stderr this is captured in .cache/gdm/session.log or .xsession-errors share|improve this answer answered Mar 25 '13 at 6:26 Guido Günther 1311 Thanks Guido. May I ask something else: how do I add my own logs to this file from my code? (something like global.log(xx)?, but this doesn't seem to work) –PauGNU Mar 29 '13 at 16:25 add a comment| up vote 1 down vote Since Gnome 3.6+ the error message tab was removed from Looking Glass. On a Gnome 3.6+ system open a console and issue the command: tail -f .xsession-errors In your extension use the new logging syntax: log('my message'); In your console you will then see: JS LOG: my message share|improve this answer edited Jun 2 '13 at 21:42 answered Jun 2 '13 at 21:31 mbokil 1,5891212 add a comment| up vote 1 down vote If you are using Fedora 19 log function mentioned in @mbokil answer writes to /var/log/m