Re: Extension problem with lockscreen

On Sat, Jun 7, 2014 at 8:07 AM, Norman L. Smith <nls1729 gmail com> wrote:
On Sat, 2014-06-07 at 08:48 +0100, Neil Bird wrote:
Around about 06/06/14 17:18, Thiago Bellini Ribeiro scribbled ...
I was crazy those days because I could not find the reason. Also, I
can't find where the log is those days.

   Seconded:  I'm on F20 / GNOME 3.10 and I've not a clue where
gnome-shell & extension errors/output are now going.  Is it even hitting
a file?


I think debian jessie went to journalctl and systemd for logs and init.

Yes, it really did. I'm actually using systemd even before the migration.

Didn't know that even user logs (not only system services logs) would
be managed by it too though.


F20 uses journalctl and systemd for sure.  The following script is handy
for viewing Gnome Shell logging.  It displays the log entries for the
current session.  You can use alacate to put it in the overview menu
apps and make it a favorite.

#!/usr/bin/env bash
pid=`ps -ef | grep $USER | grep "[0-9] gnome-session" | grep -v grep |
cut -c 10-14 | sed "s/ //g"`
/usr/bin/gnome-terminal --window --full-screen
sleep 1
xdotool type "journalctl --user --no-pager --full _PID=$pid "
xdotool key Return

hrm, the only problem is that ps doesn't show gnome-session. I can see
gnome-shell, but it's PID doesn't have anything on the log.

But well, typying "journalctl" directly provided me the full log and I
can grep or search inside less for it. But probably the problem is
because although most of the system was migrated to 3.12 (some
packages I got from experimental), some are still on 3.8 (debian is in
the middle of the transition, as you can see here:

Anyway, thank you so much for the hint! I would never figured this
alone, and I couldn't find anything on google =P

Thiago Bellini Ribeiro

“Real knowledge is to know the extent of one's ignorance.” - Confucius

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]