I've been following this bug pretty much forever now, and I have to say I
think touristguy is not being rude or disruptive, but is bang on the mark.
The discussion was wondering off track and needed pulled back to the point.
Talk of admins granting permission to users, choice of file systems etc
Public bug reported:
Binary package hint: gdm
Problem:
Network upgrade from Intrepid to Jaunty with Xubuntu. On reboot after upgrade,
normal bootup, but error message:
'No exec in session file: .xfce4' (Can't remember the exact words -
this is close).
Then gdm defaults to a failsafe X mode
To add my voice to this bug, I installed 13.04 today, on my work
computer (previously Windows 7 only), to enable me to use a variety of
bash scripts to process a large number of files on an external ext3
drive. At home I have 12.10 installed.
The files are images, several thousand per folder,
Seems to be related to KDE bug #324438
(https://bugs.kde.org/show_bug.cgi?id=324438) which was fixed in KDE bug
#329112 (https://bugs.kde.org/show_bug.cgi?id=329112).
There is a patch and reference to a git commit in #329112 which claims
to have fixed the problem.
** Bug watch added: KDE Bug
There is a fundamental difference between search (what you do when you
don't know where something is) and navigate (what you do when you know
exactly where something is, and want to go there). Why the gnome team
have chosen to conflate them, and their mental state while doing so, is
anyone's
It's a shame there is no way to vote for things here, and instead weight
seems given to bugs with a large number of comments / activity.
The current version of nautilus, which is the very core of Ubuntu, is
broken. Search is not the same as navigation. I do not want to search my
files when I know
> Oh I see why: most of us cannot change back the status of the bug once
it has been changed to "fix released" (which is stupid, too).
If that is genuinely the reason (and this bug has been marked as "Fix
Released" since Jan 2014, so it seems correct), then is it not time to
raise a new bug?
--
