On Sat, Nov 8, 2014 at 1:10 PM, Alberts Muktupāvels
No, but I figured out the problem with logging. :)<alberts muktupavels gmail com> wrote:
>
>
> On Sat, Nov 8, 2014 at 7:12 PM, Michael DePaulo <mikedep333 gmail com>
> wrote:
>>
>> On Sat, Nov 8, 2014 at 10:10 AM, Alberts Muktupāvels
>> <alberts muktupavels gmail com> wrote:
>> >
>> >
>> > On Sat, Nov 8, 2014 at 4:48 PM, Mike DePaulo <mikedep333 gmail com>
>> > wrote:
>> >>
>> >> Hi, see inline responses,
>> >>
>> >> On 11/07/14 08:56, Alberts Muktupāvels wrote:
>> >> > Hi,
>> >> >
>> >> > 1. can you try changing last line in script files to this?
>> >> > exec ${GNOME}/bin/gnome-session
>> >> > --session=gnome-flashback-[compiz/metacity]
>> >> >
>> >> > 2. also I have this before export:
>> >> > unset DBUS_SESSION_BUS_ADDRESS
>> >>
>> >> I made both changes. I still have the grey screen for metacity and the
>> >> fail
>> >> whale for compiz. And I do not see any logging.
>> >
>> >
>> > Did you add --debug (if you just made copy & paste)? Otherwise I have no
>> > idea why you don't get any debug messages, it should be in
>> > ~/.xsession-errors.
>>
>> Yeah, that is what I was expecting. The file did not exist. I created
>> it manually, yet it is still empty, even after rebooting the VM and
>> starting a session again.
>>
>> Maybe Fedora 21 prevents output to this file by default? I will look into
>> it.
>
>
> $XDG_CACHE_HOME/gdm/session.log
>
> Does this file exist?
These logs are now handled by journald. I need to run journalctl commands.
I've attached my user log for a metacity session with and without
gnome-session having been passed "--debug".
I've also attached the entire system + user log since I last booted
("system journalctl --boot.txt"). You should be able to grep it easily
for gdm log entries.
>
>>
>> >>
>> >> > Grey screen probably means that required components are not started.
>> >> > What
>> >> > DM you use for testing?
>> >>
>> >> I am using gdm from Fedora 21.
>> >>
>> >> When I start a metacity session as the user "batmin", these are the
>> >> processes I see running. It appears that not all the components
>> >> specified in
>> >> ${GNOME}/share/gnome-session/sessions/gnome-flashback-metacity.session
>> >> are running.
>> >
>> >
>> > Show output of:
>> > echo $XDG_CURRENT_DESKTOP
>>
>> I cannot launch gnome-terminal under the session because there is no
>> applications menu. However, I viewed /proc/2366/environ (PID 2365 is
>> gnome-settings-daemon) and this is set:
>>
>> XDG_CURRENT_DESKTOP=GNOME
>
>
> What GDM version do you have? It should work with 3.12.1 or newer.
"yum info gdm" says:
Version : 3.14.1
Release : 1.fc21
>
> Are you sure that you start correct session? Maybe update
> gnome-jhbuild-session-flashback-metacity script to add extra environment
> variable (if there is some way to see it later), for example:
> export MY_TEST_VARIABLE="test..."
That test works. I put it before the exec line.
> Or just make that script to create empty file in your home dir.
That test also works. I put it before the exec line.
> --
>> > it should be - GNOME-Flashback:GNOME. If it is not then this is problem.
>> > GDM
>> > should set this from DesktopNames if version is 3.14. You can workaround
>> > this by removing ShowOnlyIn=GNOME-Flashback from gnome-panel,
>> > gnome-flashback-init, gnome-flashback .desktop files.
>>
>> We're making progress! I removed that line from those 3 files. Now
>> when I launch a metacity session, I see the desktop wallpaper and
>> gnome-panel for a split second. Then I get the fail whale.
>>
>> Still no .xsession-errors output though.
>
>
> You need to find file where errors are logged to see why session crash.
>
>>
>> -Mike
>>
>> >> mike fedora-21:~ :( [8] $ ps -ef | grep -i 'gnome\|metacity'
>> >> batmin 1632 1 0 09:35 ? 00:00:00
>> >> /usr/bin/gnome-keyring-daemon --daemonize --login
>> >> batmin 1667 1606 0 09:35 ? 00:00:00
>> >> /home/batmin/jhbuild/install/bin/gnome-session
>> >> --session=gnome-flashback-metacity
>> >> batmin 1692 1667 0 09:35 ? 00:00:00 /usr/bin/ssh-agent
>> >> /bin/sh
>> >> -c exec -l /bin/bash -c
>> >> "/usr/local/bin/gnome-jhbuild-session-flashback-metacity"
>> >> batmin 1709 1 0 09:35 ? 00:00:00 dbus-launch
>> >> --exit-with-session /home/batmin/jhbuild/install/bin/gnome-session
>> >> --session=gnome-flashback-metacity
>> >> batmin 1722 1 0 09:35 ? 00:00:00
>> >> /home/batmin/jhbuild/install/libexec/at-spi2-registryd
>> >> --use-gnome-session
>> >> batmin 1733 1667 0 09:35 ? 00:00:00
>> >> /home/batmin/jhbuild/install/libexec/gnome-settings-daemon
>> >> batmin 1756 1667 0 09:35 ? 00:00:00 metacity
>> >> mike 1962 1533 0 09:38 pts/0 00:00:00 grep --color=auto -i
>> >> gnome\|metacity
>> >>
>> >> -Mike
>> >>
>> >> >
>> >> > On Fri, Nov 7, 2014 at 3:40 PM, Michael DePaulo
>> >> > <mikedep333 gmail com>
>> >> > wrote:
>> >> >
>> >> >> Hi, after successfully building GNOME Flashback's 3.16 branch with
>> >> >> jhbuild on Fedora 21 64-bit, I am now able to launch a GNOME jhbuild
>> >> >> session. However, I am unable to launch a GNOME Flashback Compiz
>> >> >> jhbuild sesion or a GNOME Flashback Metacity jhbuild session.
>> >> >>
>> >> >> A Metacity session is just a grey screen.
>> >> >> A Compiz session is the fail whale.
>> >> >>
>> >> >> I've attached my .desktop files from /usr/share/xsessions/ and my
>> >> >> scripts from /usr/local/bin/ (no file extensions.) However, despite
>> >> >> passing --debug to gnome-session, I do not see the debug output
>> >> >> anywhere. Is there a way for me to collect it?
>> >> >>
>> >> >> -Mike
>> >> [...]
>> > Alberts Muktupāvels
>> > [...]
> Alberts Muktupāvels
[...]
_______________________________________________
gnome-flashback-list mailing list
gnome-flashback-list gnome org
https://mail.gnome.org/mailman/listinfo/gnome-flashback-list