Discussion:
xfce install
(too old to reply)
steef van duin
2 years ago
Permalink
hi folks
i am wrestling with a fresh 11.6-black-screen installation to get a xfce-desktop going.

allthough I think I used from the commandline the most appropriate commands by apt i keep gretting the response 'cannot find xfce4'   when i
do btw sudo apt-get install xfce4.
anhybody a solution for this?

kind regarfs and thanks,

steef

groningen
Peter Ehlert
2 years ago
Permalink
Post by steef van duin
hi folks
i am wrestling with a fresh 11.6-black-screen installation to get  a
xfce-desktop going.
allthough I think I used from the commandline the most appropriate
commands by apt i keep gretting the response 'cannot find xfce4'  
when i do btw sudo apt-get install xfce4.
I do not have Sudo enabled, however when I run as root (su -)

apt install xfce4

works for me
Post by steef van duin
anhybody a solution for this?
kind regarfs and thanks,
steef
groningen
Nicolas George
2 years ago
Permalink
Post by steef van duin
i am wrestling with a fresh 11.6-black-screen installation to get a xfce-desktop going.
allthough I think I used from the commandline the most appropriate commands
by apt i keep gretting the response 'cannot find xfce4'   when i do btw sudo
apt-get install xfce4.
anhybody a solution for this?
When you ask for help about a command that failed, you do not make a
sentence to explain, you copy-paste the command (including the shell
prompt) and its output.

Regards,
--
Nicolas George
Greg Wooledge
2 years ago
Permalink
Post by Nicolas George
Post by steef van duin
i am wrestling with a fresh 11.6-black-screen installation to get a xfce-desktop going.
allthough I think I used from the commandline the most appropriate commands
by apt i keep gretting the response 'cannot find xfce4'   when i do btw sudo
apt-get install xfce4.
anhybody a solution for this?
When you ask for help about a command that failed, you do not make a
sentence to explain, you copy-paste the command (including the shell
prompt) and its output.
This is especially true when the quoted error text is *clearly* made up.

unicorn:~$ sudo apt-get install sdfhskdf
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package sdfhskdf

unicorn:~$ sdfhskdf
bash: sdfhskdf: command not found

Neither of these cases matches the OP's error text, so it's entirely
unclear what command the OP actually ran, or what it did, or failed to do.

However, I agree with the earlier suggestion that the sources.list file
is the best starting point.
Nicolas George
2 years ago
Permalink
Post by Greg Wooledge
Neither of these cases matches the OP's error text, so it's entirely
unclear what command the OP actually ran, or what it did, or failed to do.
It could be a translation back to English. Which brings me to another
piece of advice:

Before asking for help about a command-line, type:

unset LC_ALL
export LC_MESSAGES=C


 and re-run the command.
Post by Greg Wooledge
However, I agree with the earlier suggestion that the sources.list file
is the best starting point.
Always when asking for help about anything related to apt, of course,
you are right.

Maybe material for the FAQ?

Regards,
--
Nicolas George
r***@gmail.com
2 years ago
Permalink
Post by Nicolas George
unset LC_ALL
export LC_MESSAGES=C
… and re-run the command.
That sounds like good advice, but then the "user" (the person asking for help)
needs to know how to restore his system, so instructions should be included to
do that. (So if that is put in an FAQ, it should include the instructions to
save and later restore his original settings.

Presumably before the unset LC-ALL, a command should be run to find out the
current "LC" settings, save them, and then restore them.
--
rhk

(sig revised 20221206)

If you reply: snip, snip, and snip again; leave attributions; avoid HTML;
avoid top posting; and keep it "on list". (Oxford comma (and semi-colon)
included at no charge.) If you revise the topic, change the Subject: line.
If you change the topic, start a new thread.

Writing is often meant for others to read and understand (legal documents
excepted?) -- make it easier for your reader by various means, including
liberal use of whitespace (short paragraphs, separated by whitespace / blank
lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and
references.

If someone has already responded to a question, decide whether any response
you add will be helpful or not ...

A picture is worth a thousand words. A video (or "audio"): not so much --
divide by 10 for each minute of video (or audio) or create a transcript and
edit it to 10% of the original.

A speaker who uses ahhs, ums, or such may have a real physical or mental
disability, or may be showing disrespect for his listeners by not properly
preparing in advance and thinking before speaking. (Remember Cicero who did
not have enough time to write a short missive.) (That speaker might have been
"trained" to do this by being interrupted often if he pauses.)

A radio (or TV) station which broadcasts speakers with high pitched voices (or
very low pitched / gravelly voices) (which older people might not be able to
hear properly) disrespects its listeners. Likewise if it broadcasts
extraneous or disturbing sounds (like gunfire or crying), or broadcasts
speakers using their native language (with or without an overdubbed
translation).

A person who writes a sig this long probably has issues and disrespects (and
offends) a large number of readers. ;-)
'
Greg Wooledge
2 years ago
Permalink
Post by r***@gmail.com
Post by Nicolas George
unset LC_ALL
export LC_MESSAGES=C
… and re-run the command.
That sounds like good advice, but then the "user" (the person asking for help)
needs to know how to restore his system, so instructions should be included to
do that.
"Afterward, simply exit from this terminal." None of these changes are
permanent.

An even simpler set of instructions would be:

1) Open a new terminal, or run a new instance of your shell.

2) export LC_ALL=C

3) Run your comands. Paste the commands and their results into the body
of your email.

4) Exit from this shell/terminal.
steef van duin
2 years ago
Permalink
...
Thank you greg and others for your expert answers. as a kind of christmas present i got xfce4 going again! going this morning!

steef
Nicolas George
2 years ago
Permalink
Post by Greg Wooledge
2) export LC_ALL=C
I have considered suggesting this, but some locales are required for
programs to work correctly (LC_CTYPE), and some other locales might be
the cause for the issue and disabling them would make debugging harder.

Regards,
--
Nicolas George
Loading...