Re: [Bug 112749] Re: gedit open files as "Unsaved Document", unable to correctly open text files

2007-05-06 Thread Genes
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

[Bug 112749] gedit open files as "Unsaved Document", unable to correctly open text files

2007-05-05 Thread Genes
Public bug reported: Binary package hint: gedit Any text files is open as "Unsaved Document" check luancher = gedit %U ProblemType: Bug Architecture: i386 Date: Sun May 6 13:30:20 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gedit Package: gedit 2.18.1-0ubuntu1 PackageArchitecture:

[Bug 112749] Re: gedit open files as "Unsaved Document", unable to correctly open text files

2007-05-05 Thread Genes
** 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

[Bug 63090] Re: do not eject all USB/Firewire devices

2007-04-29 Thread Genes
I've also got the same prob when I've upgrade to Feisty Some work around with nautilus-scripts. $ gedit .gnome2/nautilus-scripts/Eject -Paste for uri in $NAUTILUS_SCRIPT_SELECTED_URIS; do device=`echo $uri | sed 's/file:\/\///g'`