6:17 p.m.
That's pretty much it. After upgrading to F20, launching gnome terminal
starts a shell with its current directory of / instead of $HOME. Very
annoying.
gnome-terminal appears to inherit the parent process's home directory. If I
launch gnome-terminal from another terminal window, the new shell's initial
directory is the parent's. Curiously, the shell's parent process is gnome-
terminal-server, whose current directory is $HOME.
going on.
The likely explanation is that I'm launching new gnome-terminal session from
a desktop icon (since Gnome 3's brain damaged "Activities" screen always
moronically activates one of the existing terminal windows, instead of
creating new terminal session), and I see that the nautilus process's home
directory is /, I guess that's what's going on, but I still just want to
have my new shells come up in $HOME by default.
6:27 p.m.
On Thu, 26 Dec 2013 19:17:04 -0500, Sam Varshavchik wrote:
That's pretty much it. After upgrading to F20, launching gnome
terminal
starts a shell with its current directory of / instead of $HOME. Very
annoying.
gnome-terminal appears to inherit the parent process's home directory. If I
launch gnome-terminal from another terminal window, the new shell's initial
directory is the parent's. Curiously, the shell's parent process is gnome-
terminal-server, whose current directory is $HOME.
going on.
The likely explanation is that I'm launching new gnome-terminal session from
a desktop icon (since Gnome 3's brain damaged "Activities" screen always
moronically activates one of the existing terminal windows, instead of
creating new terminal session), and I see that the nautilus process's home
directory is /, I guess that's what's going on, but I still just want to
have my new shells come up in $HOME by default.
Some people start new gnome-terminal windows either via "right-click ->
New Window" or via "Ctrl + left-click". Assuming you refer to the
Favourites
bar at the left.
9:02 p.m.
Michael Schwendt writes:
On Thu, 26 Dec 2013 19:17:04 -0500, Sam Varshavchik wrote:
> That's pretty much it. After upgrading to F20, launching gnome terminal
> starts a shell with its current directory of / instead of $HOME. Very
> annoying.
>
> gnome-terminal appears to inherit the parent process's home directory. If I
> launch gnome-terminal from another terminal window, the new shell's initial
> directory is the parent's. Curiously, the shell's parent process is gnome-
> terminal-server, whose current directory is $HOME.
> going on.
>
> The likely explanation is that I'm launching new gnome-terminal session
from
> a desktop icon (since Gnome 3's brain damaged "Activities" screen
always
> moronically activates one of the existing terminal windows, instead of
> creating new terminal session), and I see that the nautilus process's home
> directory is /, I guess that's what's going on, but I still just want to
> have my new shells come up in $HOME by default.
Some people start new gnome-terminal windows either via "right-click ->
New Window" or via "Ctrl + left-click". Assuming you refer to the
Favourites
bar at the left.
Well, I prefer to double-click on an icon on my desktop. Not the funny-
looking "Favorites" bar that I have to play finger gymnastics to open. I
prefer to have simple, ordinary icons that are always available on my
desktop to double-click on. They always worked just fine. Or, at least,
until F20.
So, I just tried it, just for kicks and giggles. So, the "recommended" way:
* Hit the top right corner with the pointer. Doesn't work. Hit it again. The
favourites bar slides in from the right. Yay.
* Move the pointer again. Rearrange your fingers to execute a ctrl-left
click.
* A new minituarized window appears somewhere else on the screen.
* Rearrange the fingers again, to position the pointer to the new miniatured
window.
* Click it to move the input focus there.
Versus:
* Move the pointer to an icon on the desktop. Double click on it.
WTF is wrong with Gnome? Don't answer that. It's a rhetorical question.
6:42 a.m.
On Thu, 26 Dec 2013 22:02:29 -0500, Sam Varshavchik wrote:
* Hit the top right corner with the pointer. Doesn't work. Hit it
again. The
favourites bar slides in from the right. Yay.
Pressing the Meta-key (aka "Super"-key or "Windows"-key) is a more
convenient way, also just to get to the Activities overview screen.
Much better than moving the mouse long ways over the entire screen.
(Guess what I thought when during F20 development for a short time I had
to open the screenlock with a mouse gesture because no key would do it.)
Alt+TAB for switching through active windows as well as Ctrl+Alt+Up/Down
for switching virtual desktops still works, too.
* A new minituarized window appears somewhere else on the screen.
Where should it appear instead? If there's enough free space on the screen
(not the Activities overview), at least the window doesn't overlap with
other windows. And it becomes the active window, too, when returning to
the screen (e.g. by pressing Meta-key).
* Click it to move the input focus there.
A matter of taste. I'm still a fan of "focus follows mouse", so I don't
need to click windows to activate them.
Versus:
* Move the pointer to an icon on the desktop. Double click on it.
Works only if no windows hide those icons. Or else you need to unhide the
desktop first.
WTF is wrong with Gnome? Don't answer that. It's a rhetorical
question.
FWIW, I'm not here to defend it. I just use it (or more precisely, the
programs on the screen), and I'm glad the default GNOME Shell screen is
not overloaded with lots of applets and distraction anymore.
7:44 a.m.
Michael Schwendt writes:
On Thu, 26 Dec 2013 22:02:29 -0500, Sam Varshavchik wrote:
> * Hit the top right corner with the pointer. Doesn't work. Hit it again.
The
> favourites bar slides in from the right. Yay.
Pressing the Meta-key (aka "Super"-key or "Windows"-key) is a more
convenient way, also just to get to the Activities overview screen.
Much better than moving the mouse long ways over the entire screen.
(Guess what I thought when during F20 development for a short time I had
to open the screenlock with a mouse gesture because no key would do it.)
Alt+TAB for switching through active windows as well as Ctrl+Alt+Up/Down
for switching virtual desktops still works, too.
> * A new minituarized window appears somewhere else on the screen.
Where should it appear instead? If there's enough free space on the screen
The point is that by this time I've already done more work than I do with a
simple double-click.
> * Click it to move the input focus there.
A matter of taste. I'm still a fan of "focus follows mouse", so I
don't
need to click windows to activate them.
I use focus follows mouse too. But when I did my little experiment, the
"favorites" bar was still slid out after the new gnome-terminal window
appeared, and I had to click on the new window in order to return to the
desktop, and the new window.
> Versus:
>
> * Move the pointer to an icon on the desktop. Double click on it.
Works only if no windows hide those icons. Or else you need to unhide the
desktop first.
Except that when I'm working, I make sure that the small part of the screen
where my important icons live remains unobstructed, and accessible.
The point is that a traditional desktop paradigm is infinitely more
flexible, and results in faster, more optimum workflow. I can open new
terminal windows without letting go of the mouse. The Gnome way takes
longer, involves more steps, and requires keyboard action.
And now, in F20, Gnome found more ways to break traditional desktops, by
finding a way to have gnome-terminal open in / instead of the home
directory, when it gets launched from a desktop icon.
> WTF is wrong with Gnome? Don't answer that. It's a
rhetorical question.
FWIW, I'm not here to defend it. I just use it (or more precisely, the
programs on the screen), and I'm glad the default GNOME Shell screen is
not overloaded with lots of applets and distraction anymore.
Good for you.
8:39 a.m.
On Fri, 27 Dec 2013 08:44:47 -0500, Sam Varshavchik wrote:
And now, in F20, Gnome found more ways to break traditional desktops,
by
finding a way to have gnome-terminal open in / instead of the home
directory, when it gets launched from a desktop icon.
It doesn't do that here.
I used gnome-tweak-tool to enable desktop icons, then copied a
gnome-terminal.desktop file from another account, had to mark it as
trusted, and double-clicking it starts a new terminal with default path
being $HOME.
9:01 a.m.
Michael Schwendt writes:
On Fri, 27 Dec 2013 08:44:47 -0500, Sam Varshavchik wrote:
> And now, in F20, Gnome found more ways to break traditional desktops, by
> finding a way to have gnome-terminal open in / instead of the home
> directory, when it gets launched from a desktop icon.
It doesn't do that here.
I used gnome-tweak-tool to enable desktop icons, then copied a
gnome-terminal.desktop file from another account, had to mark it as
trusted, and double-clicking it starts a new terminal with default path
being $HOME.
Well, my gnome-terminal.desktop file was last modified in 2011. It always
started gnome-terminal in the home directory, until F20. Now, it launched
gnome-terminal from /.
10:24 a.m.
On Fri, 27 Dec 2013 10:01:25 -0500, Sam Varshavchik wrote:
> I used gnome-tweak-tool to enable desktop icons, then copied a
> gnome-terminal.desktop file from another account, had to mark it as
> trusted, and double-clicking it starts a new terminal with default path
> being $HOME.
Well, my gnome-terminal.desktop file was last modified in 2011.
$ stat gnome-terminal.desktop |grep ^M
Modify: 2011-07-20 21:47:18.000000000 +0200
Originally it had been dragged onto the desktop in 2011 and has not been
modified since then.
It always started gnome-terminal in the home directory,
Here it does.
until F20. Now, it launched gnome-terminal from /.
What makes you so sure that _this_ behaviour is intentional and not only
a bug (or side-effect) specific to your setup? Even Nautilus not starting
in $HOME sounds unusual.
11:02 a.m.
Michael Schwendt writes:
On Fri, 27 Dec 2013 10:01:25 -0500, Sam Varshavchik wrote:
> > I used gnome-tweak-tool to enable desktop icons, then copied a
> > gnome-terminal.desktop file from another account, had to mark it as
> > trusted, and double-clicking it starts a new terminal with default path
> > being $HOME.
>
> Well, my gnome-terminal.desktop file was last modified in 2011.
$ stat gnome-terminal.desktop |grep ^M
Modify: 2011-07-20 21:47:18.000000000 +0200
Originally it had been dragged onto the desktop in 2011 and has not been
modified since then.
> It always started gnome-terminal in the home directory,
Here it does.
> until F20. Now, it launched gnome-terminal from /.
What makes you so sure that _this_ behaviour is intentional and not only
a bug (or side-effect) specific to your setup? Even Nautilus not starting
in $HOME sounds unusual.
Because it's par for the course. Evidence is replete with examples of
hostility from Gnome UI to anything other than the Official Way – to the
point that one needs to use something laughably called a "Tweak Tool", an
add-on, to control various mundane things like the date display format, or
input focus behavior. Something that, until Gnome 3, was offered as an
integrated configuration setting of the primary desktop configuration tool.
I could go on, of course. Suffice it to say that if, in order to customize
one's desktop, one more often will use the tweak tool add-on, instead of the
readily available "settings" applications, then someone's priorities are
definitely wrong.
1:23 p.m.
Rahul Sundaram writes:
Hi
On Fri, Dec 27, 2013 at 12:02 PM, Sam Varshavchik wrote:
Because it's par for the course
Not in this case. You have specific behavior which doesn't match anyone
else. You should create a new user and check. If you can still reproduce
it, file a bug report.
Creating a new user made no difference, of course. Same behavior –
launching via gnome3's activities or search starts the shell in the new
account's home directory. Copying gnome-terminal.desktop into ~/Desktop, and
launching it from the icon, launches the shell in /.
But I feel a little silly for overlooking the obvious fix: changing the
icon to execute:
sh -c "cd $HOME; gnome-terminal &"
Now, on to finding an explanation for systemd spinning its wheels, doing
absolutely nothing, for two minutes, on every boot…
2:30 p.m.
HI
On Fri, Dec 27, 2013 at 2:23 PM, Sam Varshavchik wrote:
Rahul Sundaram writes:
Hi
>
> On Fri, Dec 27, 2013 at 12:02 PM, Sam Varshavchik wrote:
> Because it's par for the course
>
> Not in this case. You have specific behavior which doesn't match anyone
> else. You should create a new user and check. If you can still reproduce
> it, file a bug report.
>
Creating a new user made no difference, of course. Same behavior –
launching via gnome3's activities or search starts the shell in the new
account's home directory. Copying gnome-terminal.desktop into ~/Desktop,
and launching it from the icon, launches the shell in /.
Bug report #?
Rahul
3:35 p.m.
Rahul Sundaram writes:
« HTML content follows »
HI
On Fri, Dec 27, 2013 at 2:23 PM, Sam Varshavchik wrote:
Rahul Sundaram writes:
Hi
On Fri, Dec 27, 2013 at 12:02 PM, Sam Varshavchik wrote:
Because it's par for the course
Not in this case. You have specific behavior which doesn't match anyone
else. You should create a new user and check. If you can still
reproduce it, file a bug report.
Creating a new user made no difference, of course. Same behavior –
launching via gnome3's activities or search starts the shell in the new
account's home directory. Copying gnome-terminal.desktop into ~/Desktop,
and launching it from the icon, launches the shell in /.
Bug report #?
1046980.
8:47 p.m.
Michael Schwendt writes:
On Fri, 27 Dec 2013 16:35:27 -0500, Sam Varshavchik wrote:
> > Bug report #?
>
> 1046980.
Is that with or without SELinux enforcing mode?
If with SELinux, is it reproducible also with SELinux permissive mode?
Some programs enter fs root, if something is wrong with /home.
selinux is permissive.
Previously, experimentation showed that gnome-terminal spawns a shell with
the current directory inherited from the parent process, and nautilus now
appears to run with its current directory as /. I'm guessing that in F19
nautilus 3.8 ran with $HOME for its current directory, and F20's nautilus
3.10 runs from /. Just guessing that this is really nautilus's bug. I think
a good argument can be made for nautilus to reset to $HOME after forking off
a child process for a launched application, if it's running from /.
mrsam 3394 1 0 13:05 ? 00:00:07 /usr/bin/nautilus --no-default-window
mrsam 10597 10240 0 21:46 pts/1 00:00:00 grep --color=auto nautilus
[mrsam@monster ~]$ ls -al /proc/3394/cwd
lrwxrwxrwx. 1 mrsam mrsam 0 Dec 27 21:46 /proc/3394/cwd -> /
5:23 a.m.
On Fri, 27 Dec 2013 21:47:56 -0500, Sam Varshavchik wrote:
Previously, experimentation showed that gnome-terminal spawns a shell
with
the current directory inherited from the parent process, and nautilus now
appears to run with its current directory as /.
It doesn't do that here. It's specific to your machine.
I'm guessing that in F19
nautilus 3.8 ran with $HOME for its current directory, and F20's nautilus
3.10 runs from /. Just guessing that this is really nautilus's bug. I think
a good argument can be made for nautilus to reset to $HOME after forking off
a child process for a launched application, if it's running from /.
Too much speculation. It's good that you can show that it does that for
your machine, but more interesting would be to find out why/when it does
that.
8:28 a.m.
Michael Schwendt writes:
On Fri, 27 Dec 2013 21:47:56 -0500, Sam Varshavchik wrote:
> Previously, experimentation showed that gnome-terminal spawns a shell with
> the current directory inherited from the parent process, and nautilus now
> appears to run with its current directory as /.
It doesn't do that here. It's specific to your machine.
> I'm guessing that in F19
> nautilus 3.8 ran with $HOME for its current directory, and F20's nautilus
> 3.10 runs from /. Just guessing that this is really nautilus's bug. I think
> a good argument can be made for nautilus to reset to $HOME after forking
off
> a child process for a launched application, if it's running from /.
Too much speculation. It's good that you can show that it does that for
your machine, but more interesting would be to find out why/when it does
that.
It is not user-specific configuration. This occurs for newly-created users
too. I have not done anything to nautilus, I don't even know where its
configuration settings are.
8:41 a.m.
On 12/28/13 22:28, Sam Varshavchik wrote:
Michael Schwendt writes:
> On Fri, 27 Dec 2013 21:47:56 -0500, Sam Varshavchik wrote:
>
> > Previously, experimentation showed that gnome-terminal spawns a shell with
> > the current directory inherited from the parent process, and nautilus now
> > appears to run with its current directory as /.
>
> It doesn't do that here. It's specific to your machine.
>
> > I'm guessing that in F19
> > nautilus 3.8 ran with $HOME for its current directory, and F20's nautilus
> > 3.10 runs from /. Just guessing that this is really nautilus's bug. I think
> > a good argument can be made for nautilus to reset to $HOME after forking off
> > a child process for a launched application, if it's running from /.
>
> Too much speculation. It's good that you can show that it does that for
> your machine, but more interesting would be to find out why/when it does
> that.
It is not user-specific configuration. This occurs for newly-created users too. I have
not done anything to nautilus, I don't even know where its configuration settings
are.
Whatever it is, it certainly seems unique to your system. I have a newly installed F20
system and nautilus starts with the user's home directory and when I create a desktop
icon for gnome-terminal it starts in the user's home directory.
The one thing I've not seen is anyone posting the contents of the desktop file. Mine
is....
[egreshko@f20f Desktop]$ cat gnome-terminal.desktop
[Desktop Entry]
Comment[en_US]=
Comment=
Exec=/usr/bin/gnome-terminal
GenericName[en_US]=Gnome Terminal
GenericName=Gnome Terminal
Icon=utilities-terminal
MimeType=
Name[en_US]=gnome-terminal
Name=gnome-terminal
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=
--
Getting tired of non-Fedora discussions and self-serving posts
8:42 a.m.
On Sat, 28 Dec 2013 09:28:43 -0500, Sam Varshavchik wrote:
> > 3.10 runs from /. Just guessing that this is really
nautilus's bug. I think
> > a good argument can be made for nautilus to reset to $HOME after forking
> off
> > a child process for a launched application, if it's running from /.
>
> Too much speculation. It's good that you can show that it does that for
> your machine, but more interesting would be to find out why/when it does
> that.
It is not user-specific configuration. This occurs for newly-created users
too. I have not done anything to nautilus, I don't even know where its
configuration settings are.
It doesn't need to be a change in a config file. The machine setup
(partitioning, permissions of /home, for instance) could influence runtime
behaviour, too.
It may not even be a bug in Nautilus either, since other components take
care of stopping/starting it (e.g. gnome-tweak-tool and gnome-shell).
What happens if you kill all "nautilus" processes, then start a terminal
(e.g. gnome-terminal) in a way that it starts in $HOME, then run
"nautilus --no-default-window" manually? Does it also cwd to /? Or does
it stay in $HOME? (you can also run it without options just in case)
9:32 a.m.
Michael Schwendt writes:
It may not even be a bug in Nautilus either, since other components take
care of stopping/starting it (e.g. gnome-tweak-tool and gnome-shell).
What happens if you kill all "nautilus" processes, then start a terminal
(e.g. gnome-terminal) in a way that it starts in $HOME, then run
"nautilus --no-default-window" manually? Does it also cwd to /? Or does
it stay in $HOME? (you can also run it without options just in case)
It stays in $HOME, and gnome-terminal will come up in $HOME. So, this is
really an issue with nautilus getting started in /.
nautilus's parent process is init, no finger pointing as to what normally
starts it, but both the gnome-shell's and gnome-session's processes' current
directories are $HOME.
lrwxrwxrwx. 1 mrsam mrsam 0 Dec 29 10:15 /proc/32380/cwd → /home/mrsam
lrwxrwxrwx. 1 mrsam mrsam 0 Dec 29 10:10 /proc/32380/exe → /usr/bin/gnome-
session
lrwxrwxrwx. 1 mrsam mrsam 0 Dec 29 10:23 /proc/32601/cwd → /home/mrsam
lrwxrwxrwx. 1 mrsam mrsam 0 Dec 29 10:10 /proc/32601/exe → /usr/bin/gnome-
shell
I don't have anything custom in /etc/X11/xinit/xinitrc.d, just the stock
stuff that's installed by a couple of packages. Xclients.d is empty.
The only thing that was odd was that nautilus's full command line is
/usr/bin/nautilus --no-default-window, however gnome-session-properties had
an entry for "nautilus -n" only. Something else must really be kicking off
nautilus, and the gnome-session entry must've been inherited from earlier
fedora releases (so it wouldn't be there for new user accounts) when
nautilus was getting started from gnome-session, and now the second process
is a no-op. Verified this from the command line, removed the entry for
Nautilus from gnome-session-properties, logged out and back in, nautilus
still gets started from /.
So, I'm guessing that gnome-shell currently starts nautilus. But I don't see
anything that the gnome-shell rpm installs in /etc
3795
days inactive
3797
days old
19 comments
4 participants
participants (4)
-
Ed Greshko -
Michael Schwendt -
Rahul Sundaram -
Sam Varshavchik