I have a locally-recorded video at http://www.zefox.net/~bp/ampinvt/2nd_inverter/browser_viewable_2nd_inverter.mp4
When you start Firefox from a terminal does it complain about any
missing libraries?
On 8 Dec 2025 10:29:08 +1000, Computer Nerd Kev wrote:
When you start Firefox from a terminal does it complain about any
missing libraries?
When you run a GUI app in the regular GUI way, it used to write its error messages to the file ~/.xsession-errors. Trouble is, lines in that file never had any timestamps or any other identifying information about where they came from. Under Wayland+systemd, you can now monitor those errors a bit more cleanly with journalctl --user.
On Mon, 8 Dec 2025 22:28:53 -0000 (UTC), bp wrote:
Copying a YouTube URL into vlc media player causes an error, which starts with
Your input can't be opened:
VLC is unable to open the MRL 'https://rr2---sn-nvopjoxu-25ve.googlevideo.com/videoplayback?expire=1765254131&ei=k083aZHbLNaMlu8PvrCu0As&ip=50.1.20.31&id=o-AJ-TWnr5nbiu1saDbbnTkT--M44S09bXDdhPGEg1........
but I suppose that some deliberate access control by Youtube.
Could just be that VLC?s attempt at extracting media URLs from YouTube
isn?t as up-to-date as that in a dedicated downloader like youtube-dl,
yt-dlp etc al.
You could get the media URL from one of those, and then see if VLC
will play it.
On 8 Dec 2025 10:29:08 +1000, Computer Nerd Kev wrote:
When you start Firefox from a terminal does it complain about any
missing libraries?
When you run a GUI app in the regular GUI way, it used to write its error messages to the file ~/.xsession-errors.
Trouble is, lines in that file
never had any timestamps or any other identifying information about where they came from. Under Wayland+systemd, you can now monitor those errors a bit more cleanly with journalctl --user.
I find journalctl unclean in all the most important respects ...
On 20 Dec 2025 17:38:15 +1000, Computer Nerd Kev wrote:
I find journalctl unclean in all the most important respects ...
If that's what your system is using to record its per-user log files,
then your choices are either a) learn to use it, or b) switch to a
different distro.
On 22 Dec 2025 10:50:06 +1000, Computer Nerd Kev wrote:
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On 20 Dec 2025 17:38:15 +1000, Computer Nerd Kev wrote:
I find journalctl unclean in all the most important respects ...
If that's what your system is using to record its per-user log
files, then your choices are either a) learn to use it, or b)
switch to a different distro.
Already done b), and in fact on Raspberry Pi I have the
(non-Systemd) syslog daemon started manually only for debugging, so
normally there are no such logs at all.
So what happens to the diagnostic messages from GUI apps that you run?
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On 20 Dec 2025 17:38:15 +1000, Computer Nerd Kev wrote:
I find journalctl unclean in all the most important respects ...
If that's what your system is using to record its per-user log
files, then your choices are either a) learn to use it, or b)
switch to a different distro.
Already done b), and in fact on Raspberry Pi I have the
(non-Systemd) syslog daemon started manually only for debugging, so
normally there are no such logs at all.
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
So what happens to the diagnostic messages from GUI apps that you
run?
They go to the framebuffer console X is started from (Ctrl-Alt-F1),
unless they were started from a terminal window. But those messages
aren't sent to syslog by the GUI applications, maybe your systems
have something extra which does that when GUI programs are started?
| Sysop: | Drillsar |
|---|---|
| Location: | Livingston, NJ |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 111:47:14 |
| Calls: | 16 |
| Messages: | 15,287 |