Can't modify a file with Kate, getting "unknown error code 177"

Hello everyone, total Linux Noob here. In my quest to actually use the full potential of my DAC, I want to modify the alsa.conf file. I opened it with Kate as an administrator, edited it, but when I want to save, I get “Unknown Error Code 177”.

Has anyone had this problem before or can tell me, what the code means? When I searched for it online, I only found some weird medical insurance stuff.

alsa.conf is in / and needs root permissions.

From a Konsole, you can type sudo vi /usr/share/alsa/alsa.conf and modify the file and save (first read about how edit with vi).

Insert to begin to type, you can move with arrows, when you finish the edition press Esc, and after type : wq to save and exit of the file.

Regards

hi welcome,

what do you mean when you say you “opened with kate as administrator”?

if want to edit a file owned by root, i just open it in kate and make my changes.

it’s when i go to save that i get prompted for the admin password.

i’m not aware of kate having any kind of administrator mode.

you don’t say what system you are on, but you should be able to see if you have a package called kio-admin installed or not… that might matter.

1 Like

@Lith7ium, I see this in the File Picker and dolphin-25.12.0-1.fc43, when I attempt to name a file “�̵͚̺̘͎̳̲̳̌̿̒́̄͐͆̑̀̾͝�̶̙̬͙̍̄表̵̡̙̞̫͔̞́͗̌̀̀̕̚ポ̵̧̧̑̉あ̶̢̻̤̰͖͔̠̦̝̦̖̜͈͉̓͊̏̑͑̓̊̂̔̅̋̑͘A̵̛̘͉̪̬͙̘̪͌̓̔͌͌͑̈́̉̑̔́͜鷗̵̨͎͉̤̮̊͛͒̂͆͋̎͜Œ̵̹͔̤̫͚̦͖̠̲̩̼͕̘̺̯̝͆̉̔̈̊̅̇̌̍̚̚̚ͅé̵̡͍͚̬̥̙̲̱͔̝̘͍͚̣͜͝B̸̺͓̼̫̑̚逍”, [1] so it appears to relate to a subsystem rejecting the action requested by the user.

In future search for "Unknown error code 177", because that’ll solely return exact results, like thecadforums.com/threads/tableprint8-exe-problem.27857/#post-105360.


  1. Unknown error code 177
    /home/RokeJulianLockhart/.config/qterminal.org/�̵͚̺̘͎̳̲̳̌̿̒́̄͐͆̑̀̾͝�̶̙̬͙̍̄表̵̡̙̞̫͔̞́͗̌̀̀̕̚ポ̵̧̧̑̉あ̶̢̻̤̰͖͔̠̦̝̦̖̜͈͉̓͊̏̑͑̓̊̂̔̅̋̑͘A̵̛̘͉̪̬͙̘̪͌̓̔͌͌͑̈́̉̑̔́͜鷗̵̨͎͉̤̮̊͛͒̂͆͋̎͜Œ̵̹͔̤̫͚̦͖̠̲̩̼͕̘̺̯̝͆̉̔̈̊̅̇̌̍̚̚̚ͅé̵̡͍͚̬̥̙̲̱͔̝̘͍͚̣͜͝B̸̺͓̼̫̑̚逍.part
    Please send a full bug report at https://bugs.kde.org.

    ↩︎