We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: gedit (Ubuntu)
does it depend of the directory name you are using? Does it works if you
use one without special char?
--
gedit open files as "Unsaved Document", unable to correctly open text files
https://bugs.launchpad.net/bugs/112749
You received this bug notification because you are a member of Ubuntu
Bugs,
marking unconfirmed, gedit works fine for me and you are the only one
who opened a bug about that, likely to some local configuration but I'm
not sure of what you changed
** Changed in: gedit (Ubuntu)
Status: Needs Info => Unconfirmed
--
gedit open files as "Unsaved Document", unable to c
I double clicked the text file, e.g readme.txt
It happens all the time
Sebastien Bacher wrote:
> Thank you for your bug. How do you open the file? Does it happen if the
> directory name has no space character?
>
> ** Changed in: gedit (Ubuntu)
>Importance: Undecided => Low
> Assignee: (un
Thank you for your bug. How do you open the file? Does it happen if the
directory name has no space character?
** Changed in: gedit (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
gedit open files as "Unsaved
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7565871/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/7565872/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/7565873/ProcStatus.txt
--
gedit
