good enough, closing the report for now then, it should be re open if
someone else is able to reproduce it. thanks.
** Changed in: gnome-session (Ubuntu)
Status: Incomplete = Invalid
--
gnome-session-save scew up session file
https://bugs.launchpad.net/bugs/157780
You received this bug
Yes, i guess this impact only users playing with WM so maybe we can
safely consider than someone playing with WM is able to fix WM related
issues even though it would have been better to autodetect the WM while
generating the session file.
Anyway we can still re-open the bug latter if some users
Still an issue? nobody else has confirmed this since your call for
testing, otherwise i'll close this report. thanks.
--
gnome-session-save scew up session file
https://bugs.launchpad.net/bugs/157780
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ok please someone at least confirm this on another computer so we can
set this report as confirmed and not incomplete
I edited the description explaining how to reproduce the bug, i can
reproduce this as much as i want and i located the problem. Updating by
hand the Gconf key to /etc/bin/metacity
** Description changed:
Binary package hint: gnome-session
+ gnome-session-save command don't look at the WM your are using but at the
desktop gnome application window_manager current Gcong key which may
not be up to date.
+ In my case the current key was wrongly set to /usr/bin/xfwm4
Ok here some more informations.
I discovered some strange behaviour about gnome-session-save. YOu can
see in the gutsy generated session file that xfwm4 is set as default
manager with no reason. However for an odd reason the desktop gnome
application window_manager current Gcong key was set
One more thing i would like to add and which is really weird to me is
the presence of these lines in my gutsy generated session file (the one
who don't work ) :
,Program=xfwm4
13,CurrentDirectory=/home/frodon
13,CloneCommand=/usr/bin/xfwm4 --display :0.0
13,RestartCommand=/usr/bin/xfwm4
Unfortunatly my old feisty session file is really different than the one
created under gutsy so it is hard for me to catch what could be wrong, in
addition i tried to delete my session file then start a new session and run the
gnome-session-save command with no apps opened and it results also
Could you attach the gutsy new session? Looks like you are the only one
to have the issue which makes it likely the issue come from something
you are running
--
gnome-session-save scew up session file
https://bugs.launchpad.net/bugs/157780
You received this bug notification because you are a
Sorry i wasn't clear in my previous comment, the file i posted in my
previous comment (wrongly called Feisty session file which is working
correctly) is the one i'm using now under gutsy.
--
gnome-session-save scew up session file
https://bugs.launchpad.net/bugs/157780
You received this bug
Here is an ubuntuforum thread were users are reporting long login time,
so this might be also describing the same issue where the session file
is written in a way where the login time is really long. In my case i
never waited more than 2 minutes.
http://ubuntuforums.org/showthread.php?t=585635
Here is an example of a broken file generated by the gnome-session-save
command on my computer.
** Attachment added: Broken session file
http://launchpadlibrarian.net/10186561/session_old
--
gnome-session-save scew up session file
https://bugs.launchpad.net/bugs/157780
You received this bug
Thank you for your bug. That's likely to due to one of the applications
stored in your session. What is the difference between the working and
broken version of your session?
** Changed in: gnome-session (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
13 matches
Mail list logo
