Cannot save file linux

Thread: [SOLVED] can’t save file

Thread Tools

Display

[SOLVED] can’t save file

See my final post in thread for how I fixed it.

Odd problem. I have typed up a document in OpenOffice and now can’t save it anywhere, including the desktop, fat32 and ext3 partitions.

Here is the ‘Permissions’ window message from Properties->Permissions from fat32 and ext3 partitions (both same):

and when I try to save the file .

/disk is not in my /media directory but my other two partitions are. Throws the same error regardless of where I try and save (including a dongle which automounted and appears on desktop). Everything seemed to be working okay before.

Here is result of /etc/fstab:

Any other info happily provided.

Desperate as this uni stuff. About to fall asleep but appreciate any help as this is first cab off the rank when I get up (it has to be — uni work and I am going to have to print and re-type for now). Eeek! Probably simple I imagine . (hope). Thanks in advance .

Last edited by Bucky Ball; August 10th, 2008 at 10:33 AM .

Re: can’t save file

Can you open the file? If so just copy and paste its contents in to an empty document on your desktop.

Re: can’t save file

Hey dude. I can’t close it! Booted up open office, created document, now can’t save it. Can’t close it to open it, if you follow me .

If I create an empty document and copy/paste, I will then have two identical documents, neither of which I can save anywhere! Double eek! ;(

Re: can’t save file

Re: can’t save file

Wondering if you could explain the /fstab entries you’ve suggested a little more. Don’t mean to be a pain, but just wondering why things were working fine before and not now. Machine been on all day and hardly touched it (or tweaked rather!).

I get the vfat changes, but could you explain the 0 2 at the end of the ext3 drive instead of what I have?

They exist, that is the thing.

And this set up was working fine. Got me a bit bamboozled and wondering why .

* Hey, I just remembered something. I did do one thing and that was install cronky. That could be the culprit perhaps ?? I go to Synaptics to uninstall and guess what? No ‘cronky’ to mark for uninstall. Weird . I have Compiz-Switch installed also and that switched so Compiz is off. Possible conflict or up the garden path with that one?

Last edited by Bucky Ball; August 9th, 2008 at 09:59 PM .

Re: can’t save file

When I try to save the file, it is telling me;

/media directory contains nothing like this. I run the ‘locate’ command and this is the result;

Ah ha. I get closer. I am using gnome and this is trying to save to somewhere I don’t even know about (don’t use kde although it is installed). This path has suddenly changed, cos as I say, fine before and saving to /media/bigboy; /media/fatso etc .

I test saving in AbiWord:

A different issue me thinks as the path is correct. Maybe OpenOffice problem with the path change.
Suggestions? Anyone?

Last edited by Bucky Ball; August 9th, 2008 at 10:10 PM .

Re: can’t save file

For EXT3 (bigboy) partition I used ‘gksudo nautilus’ and changed the file permissions. I had been trying ‘sudo nautilus’ before that.

For FAT32, (fatso) I replaced the /etc/fstab line for that partition with the one suggested by sisco311 above.

I also found this helpful:

Back to some uni work at last!

Last edited by Bucky Ball; August 10th, 2008 at 08:06 AM .

Re: can’t save file

Cool!
If your thread is solved, please mark it solved by selecting
Mark this thread as solved from the Thead Tools.

Re: can’t save file

Hey, cool sisco311. How did that happen? I was looking for that option on another problem I had that got solved but wasn’t there.

Just one thing though, not urgent but curious.

Now I can move things freely I’ve moved the Music folder. Rhythmbox Music Player is working fine, except when I go to import anything, it is checking the old path to my Music folder, naturally throwing an error, even though I have been to preferences and changed the path.

Tried uninstalling and reinstalling Rhythmbox but no different. When I click ok and close the error window, it then lets me import what I want from where I want.

Any ideas or should I post this in a separate thread when I have the time? Update Rhythmbox in a terminal or am I right off the money with a wild guess?

Cheers

Last edited by Bucky Ball; August 10th, 2008 at 10:36 AM .

Источник

Thread: [SOLVED] Can’t save gedit file

Thread Tools

Display

[SOLVED] Can’t save gedit file

I add lines into the file but the save option is greyed out. I choose save as and this error comes up:

Re: Can’t save gedit file

Re: Can’t save gedit file

You need to use vi to edit that file (Ubuntu may use Nano, I can’t remember).

Open a terminal and type

but be warned that if you do something even slightly wrong in that file, and you won’t be able to use sudo

Re: Can’t save gedit file

I add lines into the file but the save option is greyed out. I choose save as and this error comes up:

Re: Can’t save gedit file

Make changes so that visudo starts with nano rather than vi:

/.bashrc and add this line somewhere:

Now in terminal:

so that the change in .bashrc takes place. Now

starts visudo in nano rather than vi.

Re: Can’t save gedit file

You need to use vi to edit that file (Ubuntu may use Nano, I can’t remember).

Open a terminal and type

nano was the default
they changed it to vi in hardy

Re: Can’t save gedit file

This work perfectly.

Thanks guys

Re: Can’t save gedit file

in my experience visudo doesn’t play nice with the GUI editors

Last edited by sisco311; July 20th, 2008 at 11:03 PM .

Re: Can’t save gedit file

What kind of problems? I think I’ve used gedit a half dozen times to edit sudoers without any troubles.

I’m certainly open to changing to nano or vi if it would be better. I recommended gedit just because most ubuntu newbies are probably more familiar with that editor and you certainly don’t want to be making mistakes with sudoers.

Re: Can’t save gedit file

What kind of problems? I think I’ve used gedit a half dozen times to edit sudoers without any troubles.

I’m certainly open to changing to nano or vi if it would be better. I recommended gedit just because most ubuntu newbies are probably more familiar with that editor and you certainly don’t want to be making mistakes with sudoers.

Did you try to save the file with syntax error?
The (e)dit option doesn’t worked for me.

I don’t have any GUI editors installed, so I can’t test it now.
(I’m out of space on my 1gb «hard disk»=mp3 player; damn bad sectors)

Источник

Debian Bug report logs — #673252
[mc] mcedit cannot save file

Package: mc; Maintainer for mc is Dmitry Smirnov ; Source for mc is src:mc (PTS, buildd, popcon).

Date: Thu, 17 May 2012 10:12:02 UTC

Tags: confirmed, upstream

Found in version mc/3:4.8.3-2

Fixed in version mc/3:4.8.3-6

Done: Dmitry Smirnov

Bug is archived. No further changes may be made.

Report forwarded to debian-bugs-dist@lists.debian.org, Debian MC Packaging Group

:
Bug#673252 ; Package mc . (Thu, 17 May 2012 10:12:05 GMT) (full text, mbox, link).

—> Acknowledgement sent to Petr Voralek :
New Bug report received and forwarded. Copy sent to Debian MC Packaging Group

Information forwarded to debian-bugs-dist@lists.debian.org, Debian MC Packaging Group

:
Bug#673252 ; Package mc . (Fri, 18 May 2012 02:39:03 GMT) (full text, mbox, link).

Acknowledgement sent to onlyjob@member.fsf.org :
Extra info received and forwarded to list. Copy sent to Debian MC Packaging Group

Information forwarded to debian-bugs-dist@lists.debian.org, Debian MC Packaging Group

:
Bug#673252 ; Package mc . (Mon, 21 May 2012 04:45:06 GMT) (full text, mbox, link).

Acknowledgement sent to onlyjob@member.fsf.org :
Extra info received and forwarded to list. Copy sent to Debian MC Packaging Group

—> ‘upstream confirmed’ >; —> » >; —> Added tag(s) upstream and confirmed. Request was from Dmitry Smirnov to control@bugs.debian.org . (Mon, 18 Jun 2012 09:18:35 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Debian MC Packaging Group

:
Bug#673252 ; Package mc . (Mon, 16 Jul 2012 15:51:09 GMT) (full text, mbox, link).

—> Acknowledgement sent to Göran Weinholt :
Extra info received and forwarded to list. Copy sent to Debian MC Packaging Group

—> ‘upstream confirmed pending’ >; —> ‘upstream confirmed’ >; —> Added tag(s) pending. Request was from Dmitry Smirnov to control@bugs.debian.org . (Fri, 24 Aug 2012 14:15:13 GMT) (full text, mbox, link).

—> Reply sent to Dmitry Smirnov :
You have taken responsibility. (Sat, 25 Aug 2012 04:21:05 GMT) (full text, mbox, link).

—> Notification sent to Petr Voralek :
Bug acknowledged by developer. (Sat, 25 Aug 2012 04:21:05 GMT) (full text, mbox, link).

—> Bug archived. Request was from Debbugs Internal Request to internal_control@bugs.debian.org . (Thu, 04 Oct 2012 07:26:52 GMT) (full text, mbox, link).

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.

Источник

How To Save a File in Vi / Vim Text Editor

How to save a file in Vi / Vim editor in Linux

The procedure is as follows:

1. Open vim in Linux. For example, type: vim test.c
2. Write code or programe
3. Save file in vim by pressing ESC and ZZ
4. This will save and exit in vim or vi text editor running on Unix or Linux

Let us see some more examples.

Save a File in Vim Text Editor

The vi or vim is a text editor who has three modes: command mode, input mode, and ex mode. When starting, vim or vi begins in command mode. One can press Esc key to return to command mode and issue various commands. To create a new file, open a terminal and then type:
$ vi demo.txt

vi / vim always begins in command mode. You can press [Esc] key anytime to return to command mode. Press i to insert text. To save and exit from vi / vim, press [Esc] key and type ZZ:
ZZ
To see list of your saved file use the cat command. Run:
$ ls
$ cat demo.txt
To just save file and not to exit to shell prompt, press [Esc] key and type w
w

vi ex Mode File Saving Commands

To get into the ex mode, press [Esc] key and then : (the colon). For example, to exit from vi saving changes, press [Esc], : (colon) and type wq:
:wq

Fig.01: vi / vim write and quit command in action

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

Common Vi / Vim File Savings Related Commands (ex mode)

You need to press [Esc] key followed by the colon (:) before typing the following commands:

Command	Description
q	Quit
q!	Quit without saving changes i.e. discard changes and quit file
r fileName	Read data from file called fileName
w	Save file and continue editing
wq	Write and quit (save and exit)
x	Same as wq command i.e. write and quit (save and exit)
w fileName	Write to file called fileName (save as)
w! fileName	Overwrite to file called fileName (save as forcefully)

See Vi editor command keys wiki page for more information.

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Источник