Not seeing all journalctl output:
Hi, I am receiving this message when passing:journalctl -b -1 -r Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. The issue is that I am in the "systemd-journal" group. Thinkcentre-M57p:/usr/bin> groups paul paul : paul audio cdrom systemd-journal Thinkcentre-M57p:/usr/bin> What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show id -a output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio) Thinkcentre-M57p:/> Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 .drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 .drwxr-xr-x 1 root root 1.4K Jan 31 00:25 ..drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3Thinkcentre-M57p:/var/log/journal> Thinkcentre-M57p:/> ls -lah total 16K drwxr-xr-x 1 root root 142 Jun 3 2021 .drwxr-xr-x 1 root root 142 Jun 3 2021 ..lrwxrwxrwx 1 root root 7 Dec 10 12:49 bin-> usr/bindr-xr-xr-x 1 root root 1.3K Jan 30 17:22 bootdrwxr-xr-x 21 root root 4.3K Jan 31 09:41 devdrwxr-xr-x 1 root root 4.6K Jan 31 00:15 etcdr-xr-xr-x 1 root root 14 Jan 21 18:18 homelrwxrwxrwx 1 root root 7 Dec 10 12:49 lib-> usr/liblrwxrwxrwx 1 root root 9 Dec 10 12:49 lib64-> usr/lib64dr-xr-xr-x 1 root root 0 Jun 9 2021 mntdr-xr-xr-x 1 root root 14 Jan 6 01:12 optdr-xr-xr-x 317 root root 0 Jan 31 00:24 procdrwx------ 1 root root 796 Jan 31 00:15 rootdrwxr-xr-x 45 root root 1.2K Jan 31 09:41 runlrwxrwxrwx 1 root root 8 Dec 10 12:49 sbin-> usr/sbindrwxr-x--- 1 root root 316 Jan 31 03:32 .snapshotsdr-xr-xr-x 1 root root 22 Jun 9 2021 srvdr-xr-xr-x 13 root root 0 Jan 31 00:24 sysdrwxrwxrwt 14 root root 400 Jan 31 09:51 tmpdrwxr-xr-x 1 root root 124 Dec 10 12:49 usrdrwxr-xr-x 1 root root 148 Dec 11 21:44 varThinkcentre-M57p:/> What is the 's' in group for /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for?
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On 31.01.2024 19:34, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Thinkcentre-M57p:/> id -a
uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/> Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 .drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 .drwxr-xr-x 1 root root 1.4K Jan 31 00:25 ..drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3Thinkcentre-M57p:/var/log/journal> Thinkcentre-M57p:/> ls -lah total 16K drwxr-xr-x 1 root root 142 Jun 3 2021 .drwxr-xr-x 1 root root 142 Jun 3 2021 ..lrwxrwxrwx 1 root root 7 Dec 10 12:49 bin-> usr/bindr-xr-xr-x 1 root root 1.3K Jan 30 17:22 bootdrwxr-xr-x 21 root root 4.3K Jan 31 09:41 devdrwxr-xr-x 1 root root 4.6K Jan 31 00:15 etcdr-xr-xr-x 1 root root 14 Jan 21 18:18 homelrwxrwxrwx 1 root root 7 Dec 10 12:49 lib-> usr/liblrwxrwxrwx 1 root root 9 Dec 10 12:49 lib64-> usr/lib64dr-xr-xr-x 1 root root 0 Jun 9 2021 mntdr-xr-xr-x 1 root root 14 Jan 6 01:12 optdr-xr-xr-x 317 root root 0 Jan 31 00:24 procdrwx------ 1 root root 796 Jan 31 00:15 rootdrwxr-xr-x 45 root root 1.2K Jan 31 09:41 runlrwxrwxrwx 1 root root 8 Dec 10 12:49 sbin-> usr/sbindrwxr-x--- 1 root root 316 Jan 31 03:32 .snapshotsdr-xr-xr-x 1 root root 22 Jun 9 2021 srvdr-xr-xr-x 13 root root 0 Jan 31 00:24 sysdrwxrwxrwt 14 root root 400 Jan 31 09:51 tmpdrwxr-xr-x 1 root root 124 Dec 10 12:49 usrdrwxr-xr-x 1 root root 148 Dec 11 21:44 varThinkcentre-M57p:/> What is the 's' in group for /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for?
This is unreadable.
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2024-01-31 a las 20:35 +0300, Andrei Borzenkov escribió:
On 31.01.2024 19:34, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
...
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Thinkcentre-M57p:/> id -a
uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/> Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 .drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcentre-M57p:/var/log/journal> ls
...
This is unreadable.
TB bug. I paste for you (the html version is perfectly readable): Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio) Thinkcentre-M57p:/> Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal> Thinkcentre-M57p:/> ls -lah total 16K drwxr-xr-x 1 root root 142 Jun 3 2021 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. lrwxrwxrwx 1 root root 7 Dec 10 12:49 bin -> usr/bin dr-xr-xr-x 1 root root 1.3K Jan 30 17:22 boot drwxr-xr-x 21 root root 4.3K Jan 31 09:41 dev drwxr-xr-x 1 root root 4.6K Jan 31 00:15 etc dr-xr-xr-x 1 root root 14 Jan 21 18:18 home lrwxrwxrwx 1 root root 7 Dec 10 12:49 lib -> usr/lib lrwxrwxrwx 1 root root 9 Dec 10 12:49 lib64 -> usr/lib64 dr-xr-xr-x 1 root root 0 Jun 9 2021 mnt dr-xr-xr-x 1 root root 14 Jan 6 01:12 opt dr-xr-xr-x 317 root root 0 Jan 31 00:24 proc drwx------ 1 root root 796 Jan 31 00:15 root drwxr-xr-x 45 root root 1.2K Jan 31 09:41 run lrwxrwxrwx 1 root root 8 Dec 10 12:49 sbin -> usr/sbin drwxr-x--- 1 root root 316 Jan 31 03:32 .snapshots dr-xr-xr-x 1 root root 22 Jun 9 2021 srv dr-xr-xr-x 13 root root 0 Jan 31 00:24 sys drwxrwxrwt 14 root root 400 Jan 31 09:51 tmp drwxr-xr-x 1 root root 124 Dec 10 12:49 usr drwxr-xr-x 1 root root 148 Dec 11 21:44 var Thinkcentre-M57p:/> What is the 's' in group for /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for? - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZbqLQxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVtgUAniBdxwg+5kCQinxRAM4L cnqsYKyRAJ9wlkufJcFDHn4FA2QShHKhDQ+Erw== =qVMT -----END PGP SIGNATURE-----
On 31.01.2024 21:02, Carlos E. R. wrote:
El 2024-01-31 a las 20:35 +0300, Andrei Borzenkov escribió:
On 31.01.2024 19:34, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
...
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Thinkcentre-M57p:/> id -a
uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/> Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 .drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcentre-M57p:/var/log/journal> ls
...
This is unreadable.
TB bug.
If you imply that it is a bug on my side - no, it is not. This is exactly how plain text alternative part looks like.
(the html version is perfectly readable):
I disable HTML display.
On 2024-01-31 19:28, Andrei Borzenkov wrote:
On 31.01.2024 21:02, Carlos E. R. wrote:
El 2024-01-31 a las 20:35 +0300, Andrei Borzenkov escribió:
On 31.01.2024 19:34, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
...
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Thinkcentre-M57p:/> id -a
uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/> Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 .drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcentre-M57p:/var/log/journal> ls
...
This is unreadable.
TB bug.
If you imply that it is a bug on my side - no, it is not. This is exactly how plain text alternative part looks like.
I did not. It's a bug, IMO, in how TB generated the plain text part when -pj posted.
(the html version is perfectly readable):
I disable HTML display.
I guessed, so I did the work of converting to plain text for you to see. I was trying to help. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now. Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio) Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal> Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal> What is the 's' in group for in /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for?
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3 Also strace -o /tmp/strace.log journalctl -b and upload /tmp/strace.log to https://paste.opensuse.org/
What is the 's' in group for in /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for?
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On 2024-01-31 20:37, Andrei Borzenkov wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Maybe this is not needed. I think you missed the posts in which he said he had added the systemd-journal group, but not restarted the session; thus after a reboot it worked. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 01-31-2024 02:11PM, Carlos E. R. wrote:
On 2024-01-31 20:37, Andrei Borzenkov wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Maybe this is not needed. I think you missed the posts in which he said he had added the systemd-journal group, but not restarted the session; thus after a reboot it worked.
Yes, please this is needed. I had wished to have the strace.log reviewed if at all possible for this machine. -Thanks
On 01-31-2024 01:37PM, Andrei Borzenkov wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Also
strace -o /tmp/strace.log journalctl -b
and upload /tmp/strace.log to https://paste.opensuse.org/
Thinkcentre-M57p:~> ls -ld /var/log/journal drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 /var/log/journal Thinkcentre-M57p:~> ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3/ total 479464 -rw-r----- 1 root systemd-journal 8388608 Jan 24 17:22 system@00060fb99fdc25b8-a95abe5acd7cbe13.journal~ -rw-r----- 1 root systemd-journal 4807752 Jan 26 20:28 system@085a4cb3cbf540ef87948b95a8dbf3c4-0000000000232421-00060fe4263f3b1b.journal -rw-r----- 1 root systemd-journal 4705864 Jan 27 11:28 system@085a4cb3cbf540ef87948b95a8dbf3c4-0000000000232b22-00060fe429dba9b0.journal -rw-r----- 1 root systemd-journal 4789328 Jan 22 00:47 system@13690fff054e4b729bc86c9423bfe0ef-000000000022092c-00060f832ee077ed.journal -rw-r----- 1 root systemd-journal 5283880 Jan 23 02:40 system@13690fff054e4b729bc86c9423bfe0ef-000000000022101f-00060f83329d3efc.journal -rw-r----- 1 root systemd-journal 4813064 Jan 30 17:22 system@1a1e1ad3d2de4ffdbed7d9508668b2da-000000000023db0b-000610320663ea2d.journal -rw-r----- 1 root systemd-journal 4340728 Jan 30 20:38 system@1a1e1ad3d2de4ffdbed7d9508668b2da-000000000023e235-0006103209f011ff.journal -rw-r----- 1 root systemd-journal 4804488 Jan 27 13:05 system@1b6f2fef9d114af893c0df919dd0f768-00000000002360d7-00060ff217d9cc77.journal -rw-r----- 1 root systemd-journal 4113360 Jan 27 13:11 system@1b6f2fef9d114af893c0df919dd0f768-00000000002367d8-00060ff21a39d3b1.journal -rw-r----- 1 root systemd-journal 4803920 Jan 27 12:37 system@24890fa7f0b54a449f9f9c62839f621e-0000000000235028-00060ff1b22958ab.journal -rw-r----- 1 root systemd-journal 5050160 Jan 27 13:05 system@24890fa7f0b54a449f9f9c62839f621e-0000000000235727-00060ff1b4c05cfe.journal -rw-r----- 1 root systemd-journal 4815624 Jan 27 22:36 system@3a66db62d9574007a3f632299a8458e9-0000000000238efc-00060ffa04e9822b.journal -rw-r----- 1 root systemd-journal 4209312 Jan 27 23:50 system@3a66db62d9574007a3f632299a8458e9-000000000023960d-00060ffa12c5424f.journal -rw-r----- 1 root systemd-journal 4804840 Jan 25 01:34 system@548a7574aca14b4e95f0943b1b4c45f0-000000000022959b-00060fc03386b825.journal -rw-r----- 1 root systemd-journal 4876072 Jan 25 11:01 system@548a7574aca14b4e95f0943b1b4c45f0-0000000000229cbf-00060fc03608f669.journal -rw-r----- 1 root systemd-journal 4812592 Jan 25 13:02 system@563e4f9169844739ab4e8c78a24b0d26-000000000022d0eb-00060fc9ce28c7bc.journal -rw-r----- 1 root systemd-journal 4111856 Jan 25 13:07 system@563e4f9169844739ab4e8c78a24b0d26-000000000022d803-00060fc9d0bb99db.journal -rw-r----- 1 root systemd-journal 4809304 Jan 22 00:14 system@679132c6cf37473fa1644f9081814492-000000000021f145-00060f82ba878b69.journal -rw-r----- 1 root systemd-journal 4110816 Jan 22 00:20 system@679132c6cf37473fa1644f9081814492-000000000021f86d-00060f82bcdc2123.journal -rw-r----- 1 root systemd-journal 4806016 Jan 27 23:50 system@6dde52db5f5a455d9fd0fdf01c9699cd-0000000000239b39-00060ffb1a036954.journal -rw-r----- 1 root systemd-journal 6340592 Jan 29 23:36 system@6dde52db5f5a455d9fd0fdf01c9699cd-000000000023a235-00060ffb1c9a249d.journal -rw-r----- 1 root systemd-journal 4817328 Jan 23 02:41 system@7c58c76161e54f318185b901f4413011-0000000000222764-00060f98e55e5a8a.journal -rw-r----- 1 root systemd-journal 5050984 Jan 23 13:29 system@7c58c76161e54f318185b901f4413011-0000000000222e94-00060f98e964da8a.journal -rw-r----- 1 root systemd-journal 4808448 Jan 26 19:55 system@7e612b5537f04d52b142f3abe8365dcf-0000000000230cae-00060fe3b1d6af15.journal -rw-r----- 1 root systemd-journal 4114528 Jan 26 20:01 system@7e612b5537f04d52b142f3abe8365dcf-00000000002313ae-00060fe3b46c23a3.journal -rw-r----- 1 root systemd-journal 4786168 Jan 23 13:30 system@802970651bf64c5888e9f35dab432038-0000000000223b82-00060fa1f7627cb6.journal -rw-r----- 1 root systemd-journal 5353296 Jan 24 14:05 system@802970651bf64c5888e9f35dab432038-000000000022426c-00060fa1fae04e7a.journal -rw-r----- 1 root systemd-journal 4807520 Jan 25 11:58 system@8f1b4a6e819d4481aba25562c2339b27-000000000022c0ff-00060fc8ecbc7961.journal -rw-r----- 1 root systemd-journal 4491520 Jan 25 13:01 system@8f1b4a6e819d4481aba25562c2339b27-000000000022c7ff-00060fc8ef168097.journal -rw-r----- 1 root systemd-journal 5788416 Jan 25 01:34 system@909368fb8a0745a28e188ddadfe1b52e-0000000000228022-00060fb99efb156c.journal -rw-r----- 1 root systemd-journal 4807776 Jan 21 15:02 system@9e75637229b54e538ad7a7c6059b3986-0000000000219115-00060f7b045d5a8e.journal -rw-r----- 1 root systemd-journal 4676976 Jan 21 17:49 system@9e75637229b54e538ad7a7c6059b3986-0000000000219837-00060f7b06f68d99.journal -rw-r----- 1 root systemd-journal 4810008 Jan 21 17:49 system@a03023b3aba547c184e8a6fc31af0e5d-000000000021a517-00060f7d5a9de79c.journal -rw-r----- 1 root systemd-journal 4182280 Jan 21 18:14 system@a03023b3aba547c184e8a6fc31af0e5d-000000000021ac57-00060f7d5d3751d0.journal -rw-r----- 1 root systemd-journal 4838008 Jan 21 21:52 system@a3983e73d1454bbc9a70879613b5a666-000000000021d091-00060f80be3a0ea1.journal -rw-r----- 1 root systemd-journal 4263576 Jan 21 23:55 system@a3983e73d1454bbc9a70879613b5a666-000000000021d7db-00060f80c0885ed4.journal -rw-r----- 1 root systemd-journal 4816888 Jan 22 00:20 system@ac3bfb12c4254a22a714ffa9f9ef0705-000000000021fcbd-00060f82d189d1c2.journal -rw-r----- 1 root systemd-journal 4191000 Jan 22 00:46 system@ac3bfb12c4254a22a714ffa9f9ef0705-00000000002203e2-00060f82d3a5bcbe.journal -rw-r----- 1 root systemd-journal 4821840 Jan 31 00:25 system@b0397650061e486b858b75a7e852719a-000000000023fc1c-00061037eebd06ff.journal -rw-r----- 1 root systemd-journal 4810808 Jan 21 18:14 system@b280d534007e48718dcf916f36e4c823-000000000021b177-00060f7db5927157.journal -rw-r----- 1 root systemd-journal 4271816 Jan 21 20:20 system@b280d534007e48718dcf916f36e4c823-000000000021b88d-00060f7db7ad434c.journal -rw-r----- 1 root systemd-journal 4830184 Jan 21 23:55 system@b96a7d1dbc5544628a7a50011f013237-000000000021df00-00060f8277e54f46.journal -rw-r----- 1 root systemd-journal 4467608 Jan 22 00:13 system@b96a7d1dbc5544628a7a50011f013237-000000000021e643-00060f827a36f2b3.journal -rw-r----- 1 root systemd-journal 4802904 Jan 26 02:26 system@bca8e0c98e1c4decbc4b36d7a7750fca-000000000022f029-00060fd5094eed23.journal -rw-r----- 1 root systemd-journal 5150984 Jan 26 19:54 system@bca8e0c98e1c4decbc4b36d7a7750fca-000000000022f727-00060fd50bdd22b0.journal -rw-r----- 1 root systemd-journal 4814600 Jan 27 13:11 system@c8001fcaf7f940ba8f23173d779ee6bf-0000000000236c1b-00060ff22ce39188.journal -rw-r----- 1 root systemd-journal 4127176 Jan 27 13:19 system@c8001fcaf7f940ba8f23173d779ee6bf-0000000000237328-00060ff22f25bc6f.journal -rw-r----- 1 root systemd-journal 4793736 Jan 27 11:28 system@cd6b42a5cf6340c4b525882d44b373bf-0000000000233d63-00060ff0bbe0b2c2.journal -rw-r----- 1 root systemd-journal 5152936 Jan 27 12:37 system@cd6b42a5cf6340c4b525882d44b373bf-000000000023445f-00060ff0bec77a18.journal -rw-r----- 1 root systemd-journal 4803320 Jan 30 20:38 system@cec3e46d52c24626a194b871836c0a48-000000000023eaac-00061034c3ff9e3d.journal -rw-r----- 1 root systemd-journal 4509728 Jan 31 00:24 system@cec3e46d52c24626a194b871836c0a48-000000000023f1a8-00061034c6518466.journal -rw-r----- 1 root systemd-journal 4804048 Jan 25 13:08 system@d48121f10e4f4a03adccd1f447b55647-000000000022dc48-00060fc9e473fdbf.journal -rw-r----- 1 root systemd-journal 4822520 Jan 26 02:25 system@d48121f10e4f4a03adccd1f447b55647-000000000022e34a-00060fc9e70dbebd.journal -rw-r----- 1 root systemd-journal 4782128 Jan 24 14:05 system@d9d0b54db94241049c51ead00284ca7f-0000000000225ee0-00060fb6943ed646.journal -rw-r----- 1 root systemd-journal 4816416 Jan 25 11:10 system@df2cfec52ec2419e9e40f95984f48d7f-000000000022b4c1-00060fc820598c0c.journal -rw-r----- 1 root systemd-journal 4177384 Jan 25 11:58 system@df2cfec52ec2419e9e40f95984f48d7f-000000000022bbdd-00060fc843302750.journal -rw-r----- 1 root systemd-journal 4807944 Jan 21 20:21 system@e924ed3848764a2ba927b27cecce997d-000000000021bf3f-00060f7f79e9a6b4.journal -rw-r----- 1 root systemd-journal 4432456 Jan 21 21:51 system@e924ed3848764a2ba927b27cecce997d-000000000021c660-00060f7f7c1baf82.journal -rw-r----- 1 root systemd-journal 4808144 Jan 26 20:02 system@efb396d14f2346bdbe4cf4c65675292d-00000000002318a1-00060fe3ca560dd1.journal -rw-r----- 1 root systemd-journal 4131176 Jan 26 20:27 system@efb396d14f2346bdbe4cf4c65675292d-0000000000231fa2-00060fe3cd9603fa.journal -rw-r----- 1 root systemd-journal 4814936 Jan 29 23:37 system@f739aca90d954da699172d6e2467ab4d-000000000023c550-00061023235452aa.journal -rw-r----- 1 root systemd-journal 5147344 Jan 30 17:21 system@f739aca90d954da699172d6e2467ab4d-000000000023cc5e-0006102326f6eef6.journal -rw-r----- 1 root systemd-journal 4805128 Jan 27 13:19 system@ff07da056c0948679378dd98792f1174-00000000002377f6-00060ff249f9b41b.journal -rw-r----- 1 root systemd-journal 5117128 Jan 27 22:32 system@ff07da056c0948679378dd98792f1174-0000000000237ef1-00060ff24c3ed302.journal -rw-r----- 1 root systemd-journal 8388608 Jan 31 13:45 system.journal -rw-r-----+ 1 root systemd-journal 8388608 Jan 24 17:21 user-1000@00060fb9a1aae370-6a41269ceebcbfbd.journal~ -rw-r-----+ 1 root systemd-journal 5896464 Jan 27 11:28 user-1000@085a4cb3cbf540ef87948b95a8dbf3c4-0000000000232b21-00060fe429d8aef7.journal -rw-r-----+ 1 root systemd-journal 6422528 Jan 23 02:41 user-1000@13690fff054e4b729bc86c9423bfe0ef-000000000022101e-00060f83329a5d9c.journal -rw-r-----+ 1 root systemd-journal 4768424 Jan 30 20:38 user-1000@1a1e1ad3d2de4ffdbed7d9508668b2da-000000000023e234-0006103209ecba7e.journal -rw-r-----+ 1 root systemd-journal 4241104 Jan 27 13:11 user-1000@1b6f2fef9d114af893c0df919dd0f768-00000000002367d7-00060ff21a3616af.journal -rw-r-----+ 1 root systemd-journal 4353216 Jan 27 13:05 user-1000@24890fa7f0b54a449f9f9c62839f621e-0000000000235726-00060ff1b4bcec28.journal -rw-r-----+ 1 root systemd-journal 4305440 Jan 27 23:50 user-1000@3a66db62d9574007a3f632299a8458e9-000000000023960c-00060ffa12c21f00.journal -rw-r-----+ 1 root systemd-journal 6409048 Jan 25 11:10 user-1000@548a7574aca14b4e95f0943b1b4c45f0-0000000000229cbe-00060fc036066189.journal -rw-r-----+ 1 root systemd-journal 4242072 Jan 25 13:08 user-1000@563e4f9169844739ab4e8c78a24b0d26-000000000022d802-00060fc9d0b7f528.journal -rw-r-----+ 1 root systemd-journal 4254256 Jan 22 00:20 user-1000@679132c6cf37473fa1644f9081814492-000000000021f86c-00060f82bcd78dd8.journal -rw-r-----+ 1 root systemd-journal 6732512 Jan 29 23:37 user-1000@6dde52db5f5a455d9fd0fdf01c9699cd-000000000023a234-00060ffb1c96a29b.journal -rw-r-----+ 1 root systemd-journal 4825808 Jan 23 13:30 user-1000@7c58c76161e54f318185b901f4413011-0000000000222e93-00060f98e961ea7a.journal -rw-r-----+ 1 root systemd-journal 4347216 Jan 26 20:02 user-1000@7e612b5537f04d52b142f3abe8365dcf-00000000002313ad-00060fe3b4687372.journal -rw-r-----+ 1 root systemd-journal 6830688 Jan 24 14:05 user-1000@802970651bf64c5888e9f35dab432038-000000000022426b-00060fa1faddc5a0.journal -rw-r-----+ 1 root systemd-journal 4671840 Jan 25 13:02 user-1000@8f1b4a6e819d4481aba25562c2339b27-000000000022c7fe-00060fc8ef12c31d.journal -rw-r-----+ 1 root systemd-journal 5101448 Jan 25 01:34 user-1000@909368fb8a0745a28e188ddadfe1b52e-000000000022873d-00060fb9a1aa6f97.journal -rw-r-----+ 1 root systemd-journal 4879872 Jan 21 17:49 user-1000@9e75637229b54e538ad7a7c6059b3986-0000000000219836-00060f7b06f16bf6.journal -rw-r-----+ 1 root systemd-journal 4322304 Jan 21 18:14 user-1000@a03023b3aba547c184e8a6fc31af0e5d-000000000021ac56-00060f7d5d33ffce.journal -rw-r-----+ 1 root systemd-journal 4637472 Jan 21 23:55 user-1000@a3983e73d1454bbc9a70879613b5a666-000000000021d7da-00060f80c0853c0d.journal -rw-r-----+ 1 root systemd-journal 4340968 Jan 22 00:47 user-1000@ac3bfb12c4254a22a714ffa9f9ef0705-00000000002203e1-00060f82d3a33573.journal -rw-r-----+ 1 root systemd-journal 4444664 Jan 21 20:21 user-1000@b280d534007e48718dcf916f36e4c823-000000000021b88c-00060f7db7aa4892.journal -rw-r-----+ 1 root systemd-journal 4735440 Jan 22 00:14 user-1000@b96a7d1dbc5544628a7a50011f013237-000000000021e642-00060f827a330999.journal -rw-r-----+ 1 root systemd-journal 6015728 Jan 26 19:55 user-1000@bca8e0c98e1c4decbc4b36d7a7750fca-000000000022f726-00060fd50bd9170f.journal -rw-r-----+ 1 root systemd-journal 4321672 Jan 27 13:19 user-1000@c8001fcaf7f940ba8f23173d779ee6bf-0000000000237327-00060ff22f215047.journal -rw-r-----+ 1 root systemd-journal 4639296 Jan 27 12:37 user-1000@cd6b42a5cf6340c4b525882d44b373bf-000000000023445e-00060ff0bec39325.journal -rw-r-----+ 1 root systemd-journal 4903376 Jan 31 00:25 user-1000@cec3e46d52c24626a194b871836c0a48-000000000023f1a7-00061034c64daf7e.journal -rw-r-----+ 1 root systemd-journal 4939160 Jan 26 02:26 user-1000@d48121f10e4f4a03adccd1f447b55647-000000000022e349-00060fc9e70a3557.journal -rw-r-----+ 1 root systemd-journal 4333496 Jan 25 11:58 user-1000@df2cfec52ec2419e9e40f95984f48d7f-000000000022bbdc-00060fc8432df1e0.journal -rw-r-----+ 1 root systemd-journal 4917240 Jan 21 21:52 user-1000@e924ed3848764a2ba927b27cecce997d-000000000021c65f-00060f7f7c191969.journal -rw-r-----+ 1 root systemd-journal 4268744 Jan 26 20:28 user-1000@efb396d14f2346bdbe4cf4c65675292d-0000000000231fa1-00060fe3cd923146.journal -rw-r-----+ 1 root systemd-journal 4841096 Jan 30 17:22 user-1000@f739aca90d954da699172d6e2467ab4d-000000000023cc5d-0006102326f211b0.journal -rw-r-----+ 1 root systemd-journal 5184648 Jan 27 22:36 user-1000@ff07da056c0948679378dd98792f1174-0000000000237ef0-00060ff24c3b059f.journal -rw-r-----+ 1 root systemd-journal 8388608 Jan 31 13:45 user-1000.journal -rw-r-----+ 1 root systemd-journal 4125840 Jan 21 17:49 user-1001@9e75637229b54e538ad7a7c6059b3986-0000000000219ca2-00060f7b2b66669a.journal -rw-r-----+ 1 root systemd-journal 4143072 Jan 22 00:14 user-1001@b96a7d1dbc5544628a7a50011f013237-000000000021e9ff-00060f8292d1bacf.journal Thinkcentre-M57p:~> I am unable to upload the /tmp/strace.log file to https://paste.opensuse.org/ . It simply will not take, even after logging in (suse paste) then retrying and then creating a new paste non private, selecting the /tmp/strace.log file. nothing is displayed but the ability to create a new paste page. Why is this and what am I doing wrong when trying to upload this strace.log file?
What is the 's' in group for in /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for?
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On Wed, 31 Jan 2024 22:37:01 +0300 Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
Well it does actually show the permissions of /var/log/journal and /var/log for that matter, since he used a -a option. But I agree he didn't show the sub-directories :( And pj that 'file' is not a file, but a sub-directory! Most people have the -F option turned on so they can see it easily. The s means setgid.
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Also
strace -o /tmp/strace.log journalctl -b
and upload /tmp/strace.log to https://paste.opensuse.org/
On 01-31-2024 02:43PM, Dave Howorth wrote:
On Wed, 31 Jan 2024 22:37:01 +0300 Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
Well it does actually show the permissions of /var/log/journal and /var/log for that matter, since he used a -a option. But I agree he didn't show the sub-directories :(
And pj that 'file' is not a file, but a sub-directory! Most people have the -F option turned on so they can see it easily. The s means setgid.
Thanks for clearing that up for me I could see directory but now using 'ls -Flah' instead of 'ls -lah' I see more clearly. Yes I see that that 'd' means directory. suse paste appears to be completely non-functional for the moment now (at least from this location).
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Also
strace -o /tmp/strace.log journalctl -b
and upload /tmp/strace.log to https://paste.opensuse.org/
-pj composed on 2024-01-31 14:57 (UTC-0600):
suse paste appears to be completely non-functional for the moment now (at least from this location).
I gave up long ago trying to use the susepaste website other than to view existing pastes. Similarly, I found the susepaste command to be cantankerous and picky going back for years, making me think its host's upload functionality simply doesn't run on a 24/7 basis. More recently I have found it fairly reliable, as long as the upload size and/or expires are not too large, and quotes are used for *all* cmdline option strings, exactly as demonstrated in its man page examples. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 01-31-2024 03:32PM, Felix Miata wrote:
-pj composed on 2024-01-31 14:57 (UTC-0600):
suse paste appears to be completely non-functional for the moment now (at least from this location).
I gave up long ago trying to use the susepaste website other than to view existing pastes. Similarly, I found the susepaste command to be cantankerous and picky going back for years, making me think its host's upload functionality simply doesn't run on a 24/7 basis. More recently I have found it fairly reliable, as long as the upload size and/or expires are not too large, and quotes are used for *all* cmdline option strings, exactly as demonstrated in its man page examples.
Ok, thanks for your insight into this. I have been confused about this for some time actually. Is it acceptable to attach the strace.log file to a message in Thunderbird or is that not a good way? What do you think I should do about this situation?
-pj composed on 2024-01-31 16:06 (UTC-0600):
Felix Miata wrote:
I gave up long ago trying to use the susepaste website other than to view existing pastes. Similarly, I found the susepaste command to be cantankerous and picky going back for years, making me think its host's upload functionality simply doesn't run on a 24/7 basis. More recently I have found it fairly reliable, as long as the upload size and/or expires are not too large, and quotes are used for *all* cmdline option strings, exactly as demonstrated in its man page examples.
Ok, thanks for your insight into this. I have been confused about this for some time actually. Is it acceptable to attach the strace.log file to a message in Thunderbird or is that not a good way? What do you think I should do about this situation?
First, strip .log out of the file name if that's how it ends. Instead of its original name, change its end to log.txt or just .txt. Then try the susepaste command again strictly using the bottom of man page examples, using at least a week long expires. If it fails again, double check your quoting and try again. If it still fails, wait 10 hours and try again, and if that too fails, try compressing the log into an archive, and attach the archive to a list reply mail. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
* Felix Miata <mrmazda@earthlink.net> [01-31-24 17:26]:
-pj composed on 2024-01-31 16:06 (UTC-0600):
Felix Miata wrote:
I gave up long ago trying to use the susepaste website other than to view existing pastes. Similarly, I found the susepaste command to be cantankerous and picky going back for years, making me think its host's upload functionality simply doesn't run on a 24/7 basis. More recently I have found it fairly reliable, as long as the upload size and/or expires are not too large, and quotes are used for *all* cmdline option strings, exactly as demonstrated in its man page examples.
Ok, thanks for your insight into this. I have been confused about this for some time actually. Is it acceptable to attach the strace.log file to a message in Thunderbird or is that not a good way? What do you think I should do about this situation?
First, strip .log out of the file name if that's how it ends. Instead of its original name, change its end to log.txt or just .txt. Then try the susepaste command again strictly using the bottom of man page examples, using at least a week long expires. If it fails again, double check your quoting and try again. If it still fails, wait 10 hours and try again, and if that too fails, try compressing the log into an archive, and attach the archive to a list reply mail.
rather than "attaching" to mail which sends it to *everybody* on the list, upload it to a file sharing location such as google drive, .... where only those interested will be affected. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 01-31-2024 04:25PM, Felix Miata wrote:
-pj composed on 2024-01-31 16:06 (UTC-0600):
Felix Miata wrote:
I gave up long ago trying to use the susepaste website other than to view existing pastes. Similarly, I found the susepaste command to be cantankerous and picky going back for years, making me think its host's upload functionality simply doesn't run on a 24/7 basis. More recently I have found it fairly reliable, as long as the upload size and/or expires are not too large, and quotes are used for *all* cmdline option strings, exactly as demonstrated in its man page examples.
Ok, thanks for your insight into this. I have been confused about this for some time actually. Is it acceptable to attach the strace.log file to a message in Thunderbird or is that not a good way? What do you think I should do about this situation?
First, strip .log out of the file name if that's how it ends. Instead of its original name, change its end to log.txt or just .txt. Then try the susepaste command again strictly using the bottom of man page examples, using at least a week long expires. If it fails again, double check your quoting and try again. If it still fails, wait 10 hours and try again, and if that too fails, try compressing the log into an archive, and attach the archive to a list reply mail.
Hi, that looks like great advice although I am receiving no joy from following it yet here. I understand that 10 hours has not passed yet. Please see below for my most likely incorrect susepaste command passings: Thinkcentre-M57p:/tmp> ls -lah total 23M drwxrwxrwt 14 root root 460 Jan 31 17:05 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. drwxrwxrwt 2 root root 40 Jan 31 00:24 .font-unix drwxrwxrwt 2 root root 60 Jan 31 00:25 .ICE-unix -rw-r--r-- 1 paul paul 108 Jan 31 14:40 keepassxc-paul.lock srwx------ 1 paul paul 0 Jan 31 14:40 keepassxc-paul.socket drwx------ 2 paul paul 40 Jan 31 00:25 plasma-csd-generator.pqVjDO -rw-r----- 1 paul paul 0 Jan 31 00:25 qipc_sharedmemory_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a -rw-r----- 1 paul paul 0 Jan 31 00:25 qipc_systemsem_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a srwx------ 1 paul paul 0 Jan 31 00:25 Qsynth:paul@paul-Thinkcentre-M57p srwx------ 1 sddm sddm 0 Jan 31 00:25 sddm-:0-NrqKTx srwxr-xr-x 1 root root 0 Jan 31 00:25 sddm-auth-d52d421d-dd11-4f62-b549-9ee0c84be0be -rw-r--r-- 1 paul paul 23M Jan 31 14:30 strace..txt drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-chronyd.service-ZHg9nZ drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-ModemManager.service-EseIuy drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-polkit.service-6kPzLI drwx------ 3 root root 60 Jan 31 00:25 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-power-profiles-daemon.service-ciy43Q drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-systemd-logind.service-WqYU8O drwx------ 3 root root 60 Jan 31 00:25 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-upower.service-KsIIQu drwx------ 2 paul paul 40 Jan 31 00:25 Temp-b9ec1e10-03dc-4b05-b5e2-0f9259ab2ad4 drwxrwxrwt 2 root root 60 Jan 31 00:25 .X11-unix -rw------- 1 paul paul 111 Jan 31 00:25 xauth_YgTfbj drwxrwxrwt 2 root root 40 Jan 31 00:24 .XIM-unix strace.txt is 23M size. Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘ usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] -Regards
PJ, et al -- ...and then OpenSuSE users said... % ... % % Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" % ‘strace.txt‘ [snip] What character are you using in front of the 't', 'e', 'f' arg flags? They should be a hyphen (dash, minus sign, ...) just like your -pj moniker. HTH & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
-pj composed on 2024-01-31 17:18 (UTC-0600):
strace.txt is 23M size.
Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
I believe there is an unpublished size limit that 23M exceeds - by a /lot/. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 01-31-2024 06:15PM, Felix Miata wrote:
-pj composed on 2024-01-31 17:18 (UTC-0600):
strace.txt is 23M size.
Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
I believe there is an unpublished size limit that 23M exceeds - by a /lot/.
My question for you is, what could my next alternative be before compressing and then attaching to the list? I do not use file sharing services typically.
On 2024-02-01 01:39, -pj via openSUSE Users wrote:
On 01-31-2024 06:15PM, Felix Miata wrote:
-pj composed on 2024-01-31 17:18 (UTC-0600):
strace.txt is 23M size.
Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
You do not need "-f text", leave that to automatics. And you can add a "-n yourname".
I believe there is an unpublished size limit that 23M exceeds - by a /lot/.
My question for you is, what could my next alternative be before compressing and then attaching to the list? I do not use file sharing services typically.
Compress the file, obviously. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 01-31-2024 07:20PM, Carlos E. R. wrote:
susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
Thinkcentre-M57p:/tmp # ls -lah total 23M drwxrwxrwt 15 root root 500 Jan 31 19:37 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. drwxrwxrwt 2 root root 40 Jan 31 00:24 .font-unix drwxrwxrwt 2 root root 60 Jan 31 00:25 .ICE-unix -rw-r--r-- 1 paul paul 108 Jan 31 14:40 keepassxc-paul.lock srwx------ 1 paul paul 0 Jan 31 14:40 keepassxc-paul.socket drwx------ 2 paul paul 40 Jan 31 00:25 plasma-csd-generator.pqVjDO -rw-r----- 1 paul paul 0 Jan 31 00:25 qipc_sharedmemory_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a -rw-r----- 1 paul paul 0 Jan 31 00:25 qipc_systemsem_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a srwx------ 1 paul paul 0 Jan 31 00:25 Qsynth:paul@paul-Thinkcentre-M57p drwx------ 2 root root 40 Jan 31 19:27 runtime-root srwx------ 1 sddm sddm 0 Jan 31 00:25 sddm-:0-NrqKTx srwxr-xr-x 1 root root 0 Jan 31 00:25 sddm-auth-d52d421d-dd11-4f62-b549-9ee0c84be0be -rw-r--r-- 1 paul paul 23M Jan 31 14:30 strace.txt drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-chronyd.service-ZHg9nZ drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-ModemManager.service-EseIuy drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-polkit.service-6kPzLI drwx------ 3 root root 60 Jan 31 00:25 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-power-profiles-daemon.service-ciy43Q drwx------ 3 root root 60 Jan 31 00:24 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-systemd-logind.service-WqYU8O drwx------ 3 root root 60 Jan 31 00:25 systemd-private-4d5bbf9c425b492b82d34750a40f5b0b-upower.service-KsIIQu drwx------ 2 paul paul 40 Jan 31 00:25 Temp-b9ec1e10-03dc-4b05-b5e2-0f9259ab2ad4 -rw-r--r-- 1 paul paul 0 Jan 31 19:25 test-0.txt drwxrwxrwt 2 root root 60 Jan 31 00:25 .X11-unix -rw------- 1 paul paul 111 Jan 31 00:25 xauth_YgTfbj drwxrwxrwt 2 root root 40 Jan 31 00:24 .XIM-unix paul-Thinkcentre-M57p:/tmp # susepaste ‐t "-pj strace.txt" ‐e "1080" -n "pj" 'strace.txt' openSUSE Paste script usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] Thinkcentre-M57p:/tmp # Which application do you use for file compression typically? Should strace.txt be changed back to strace.log before compression?
On 2024-02-01 02:39, -pj via openSUSE Users wrote:
On 01-31-2024 07:20PM, Carlos E. R. wrote:
susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
Thinkcentre-M57p:/tmp # ls -lah total 23M
....
paul-Thinkcentre-M57p:/tmp # susepaste ‐t "-pj strace.txt" ‐e "1080" -n "pj" 'strace.txt' openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file]
Perhaps doesn't like: ‐t "-pj strace.txt" Try with: ‐t "\-pj strace.txt" or ‐t "pj strace.txt"
Thinkcentre-M57p:/tmp #
Which application do you use for file compression typically? Should strace.txt be changed back to strace.log before compression?
xz, probably. The name of the file is irrelevant. Yes, the person downloading it has to decompress it, but a program like "less strace.log.xz" will do it transparently. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 01-31-2024 08:17PM, Carlos E. R. wrote:
On 2024-02-01 02:39, -pj via openSUSE Users wrote:
On 01-31-2024 07:20PM, Carlos E. R. wrote:
susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
Thinkcentre-M57p:/tmp # ls -lah total 23M
....
paul-Thinkcentre-M57p:/tmp # susepaste ‐t "-pj strace.txt" ‐e "1080" -n "pj" 'strace.txt' openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file]
Perhaps doesn't like:
‐t "-pj strace.txt"
Try with:
‐t "\-pj strace.txt"
or
‐t "pj strace.txt"
Thinkcentre-M57p:/tmp # susepaste ‐t "\-pj strace.txt" ‐e "1080" -n "pj" 'strace.txt' openSUSE Paste script usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] Thinkcentre-M57p:/tmp # susepaste ‐t "-pj strace.txt" ‐e "1080" -n "pj" 'strace.txt' openSUSE Paste script usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] Thinkcentre-M57p:/tmp #
Carlos & PJ, et al -- ...and then Carlos E. R. said... % On 2024-02-01 02:39, -pj via openSUSE Users wrote: % % > paul-Thinkcentre-M57p:/tmp # susepaste ?t "-pj strace.txt" ?e "1080" -n % > "pj" 'strace.txt' % > openSUSE Paste script % > % > usage: % > susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] % > [file] % % Perhaps doesn't like: % % ?t "-pj strace.txt" % % Try with: % % ?t "\-pj strace.txt" % % or % % ?t "pj strace.txt" Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)? davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-( Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign. Good luck ... :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al --
...and then Carlos E. R. said... % On 2024-02-01 02:39, -pj via openSUSE Users wrote: % % > paul-Thinkcentre-M57p:/tmp # susepaste ?t "-pj strace.txt" ?e "1080" -n % > "pj" 'strace.txt' % > openSUSE Paste script % > % > usage: % > susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] % > [file] % % Perhaps doesn't like: % % ?t "-pj strace.txt" % % Try with: % % ?t "\-pj strace.txt" % % or % % ?t "pj strace.txt"
Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)?
davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file]
davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-(
Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign.
Good luck ...
:-D This below is the "Examples" (end of the man page) I have been reviewing.
EXAMPLES How to post list of your usb devices: lsusb ‐v | TITLE="My usb devices" NICK="Geeko" susepaste lsusb ‐v | susepaste ‐t "My usb devices" ‐n "Geeko" How to post susepaste that will last six hours: susepaste ‐t "openSUSE paste" ‐e "360" ‐f "bash" ‘which susepaste‘ How to post an image that will last three hours: susepaste ‐t "openSUSE image" ‐e "180" ‐f "image" example.png COPYRIGHT Copyright (C) 2010 by Michal Hrusecky <Michal@Hrusecky.net> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. AUTHORS Michal Hrusecky <Michal@Hrusecky.net> SUSEpaste 0.5 April 2011 SUSEPASTE(1)
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al --
...and then Carlos E. R. said... % On 2024-02-01 02:39, -pj via openSUSE Users wrote: % % > paul-Thinkcentre-M57p:/tmp # susepaste ?t "-pj strace.txt" ?e "1080" -n % > "pj" 'strace.txt' % > openSUSE Paste script % > % > usage: % > susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] % > [file] % % Perhaps doesn't like: % % ?t "-pj strace.txt" % % Try with: % % ?t "\-pj strace.txt" % % or % % ?t "pj strace.txt"
Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)?
davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-(
Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign.
I'm surprised nobody has confirmed what David is saying. He's right. For whatever reason it seems pj isn't using a normal hyphen character to introduce some of the arguments. Fix that and the commands should work.
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al -- [...]
Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)? davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-(
Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign.
I'm surprised nobody has confirmed what David is saying. He's right. For whatever reason it seems pj isn't using a normal hyphen character to introduce some of the arguments. Fix that and the commands should work.
For purposes of discussion, we need to have common terminology. The character used to introduce command-line options is what Wikipedia calls "Hyphen-minus". [1] Other characters that look like it are the Hyphen, Non-breaking hyphen, Minus sign, En dash, and Em dash. If PJ is using something that isn't the proper hyphen-minus character, then maybe it is because he copy-pasted it right from the f'ed-up susepaste man page. Some of you will see that none of the "hyphen-whatevers" shown for the option descriptions and the examples in the man page are the actual hyphen-minus. Others won't. It depends on your locale settings. What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1 Yes, there is just one hyphen-minus in the whole man page. It is in the title line. For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= [1] https://en.wikipedia.org/wiki/Hyphen-minus -- Robert Webb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2024-02-01 at 11:16 -0000, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al -- [...]
Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)? davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-(
Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign.
I'm surprised nobody has confirmed what David is saying. He's right. For whatever reason it seems pj isn't using a normal hyphen character to introduce some of the arguments. Fix that and the commands should work.
Sorry, no, I don't see it. You must have very good eyesight. But you are right. Good catch. cer@Telcontar:~> hexdump -C Downloads/Thunderbird_downloads/Re\:\ susepasting\ -\ -pj\ via\ openSUSE\ Users\ \<users@lists.opensuse.org\>\ -\ 2024-02-01\ 0239.eml | less 00002820 74 6d 70 20 23 20 73 75 73 65 70 61 73 74 65 20 |tmp # susepaste | 00002830 3d 45 32 3d 38 30 3d 39 30 74 20 22 2d 70 6a 20 |=E2=80=90t "-pj | 00002840 73 74 72 61 63 65 2e 74 78 74 22 20 3d 45 32 3d |strace.txt" =E2=| 00002850 38 30 3d 0d 0a 3d 39 30 65 20 22 31 30 38 30 22 |80=..=90e "1080"| 00002860 20 2d 6e 0d 0a 22 70 6a 22 20 27 73 74 72 61 63 | -n.."pj" 'strac| 00002870 65 2e 74 78 74 27 0d 0a 6f 70 65 6e 53 55 53 45 |e.txt'..openSUSE| 00002880 20 50 61 73 74 65 20 73 63 72 69 70 74 0d 0a 0d | Paste script...|
For purposes of discussion, we need to have common terminology. The character used to introduce command-line options is what Wikipedia calls "Hyphen-minus". [1] Other characters that look like it are the Hyphen, Non-breaking hyphen, Minus sign, En dash, and Em dash.
I know that it is the ascii-7 "hyphen", char(0x2d) :-) cer@Telcontar:~> echo "-" | hexdump -C 00000000 2d 0a |-.| 00000002 cer@Telcontar:~>
If PJ is using something that isn't the proper hyphen-minus character, then maybe it is because he copy-pasted it right from the f'ed-up susepaste man page.
Some of you will see that none of the "hyphen-whatevers" shown for the option descriptions and the examples in the man page are the actual hyphen-minus. Others won't. It depends on your locale settings.
cer@Telcontar:~> man susepaste | hexdump -C | less 000002e0 20 20 20 2d 6e 20 4e 49 43 4b 0a 20 20 20 20 20 | -n NICK. | 00000320 20 20 20 20 20 2d 74 20 54 49 54 4c 45 0a 20 20 | -t TITLE. | 00002310 0a 0a 20 20 20 20 20 20 20 2d 65 20 45 58 50 49 |.. -e EXPI| 00002580 65 72 0a 0a 20 20 20 20 20 20 20 2d 73 20 53 43 |er.. -s SC| I don't see the error in "my" man page, sorry.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
cer@Telcontar:~> locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES.utf8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES.utf8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=es_ES.utf8 LC_NAME=es_ES.utf8 LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE=es_ES.utf8 LC_MEASUREMENT=es_ES.utf8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= cer@Telcontar:~>
- -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZbuC/Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV630An1LfZRDexZwq/5Q/b5HV wDEhqw3DAKCZI471w15U4DHVWrbBPNXLOLrNog== =dfXT -----END PGP SIGNATURE-----
On Thu, 1 Feb 2024 12:39:40 +0100 (CET), "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Thursday, 2024-02-01 at 11:16 -0000, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al -- [...]
Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)? davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-(
Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign.
I'm surprised nobody has confirmed what David is saying. He's right. For whatever reason it seems pj isn't using a normal hyphen character to introduce some of the arguments. Fix that and the commands should work.
Sorry, no, I don't see it. You must have very good eyesight.
But you are right. Good catch.
cer@Telcontar:~> hexdump -C Downloads/Thunderbird_downloads/Re\:\ susepasting\ -\ -pj\ via\ openSUSE\ Users\ \<users@lists.opensuse.org\>\ -\ 2024-02-01\ 0239.eml | less
00002820 74 6d 70 20 23 20 73 75 73 65 70 61 73 74 65 20 |tmp # susepaste | 00002830 3d 45 32 3d 38 30 3d 39 30 74 20 22 2d 70 6a 20 |=E2=80=90t "-pj | 00002840 73 74 72 61 63 65 2e 74 78 74 22 20 3d 45 32 3d |strace.txt" =E2=| 00002850 38 30 3d 0d 0a 3d 39 30 65 20 22 31 30 38 30 22 |80=..=90e "1080"| 00002860 20 2d 6e 0d 0a 22 70 6a 22 20 27 73 74 72 61 63 | -n.."pj" 'strac| 00002870 65 2e 74 78 74 27 0d 0a 6f 70 65 6e 53 55 53 45 |e.txt'..openSUSE| 00002880 20 50 61 73 74 65 20 73 63 72 69 70 74 0d 0a 0d | Paste script...|
For purposes of discussion, we need to have common terminology. The character used to introduce command-line options is what Wikipedia calls "Hyphen-minus". [1] Other characters that look like it are the Hyphen, Non-breaking hyphen, Minus sign, En dash, and Em dash.
I know that it is the ascii-7 "hyphen", char(0x2d) :-)
cer@Telcontar:~> echo "-" | hexdump -C 00000000 2d 0a |-.| 00000002 cer@Telcontar:~>
If PJ is using something that isn't the proper hyphen-minus character, then maybe it is because he copy-pasted it right from the f'ed-up susepaste man page.
Some of you will see that none of the "hyphen-whatevers" shown for the option descriptions and the examples in the man page are the actual hyphen-minus. Others won't. It depends on your locale settings.
cer@Telcontar:~> man susepaste | hexdump -C | less
000002e0 20 20 20 2d 6e 20 4e 49 43 4b 0a 20 20 20 20 20 | -n NICK. |
00000320 20 20 20 20 20 2d 74 20 54 49 54 4c 45 0a 20 20 | -t TITLE. |
00002310 0a 0a 20 20 20 20 20 20 20 2d 65 20 45 58 50 49 |.. -e EXPI|
00002580 65 72 0a 0a 20 20 20 20 20 20 20 2d 73 20 53 43 |er.. -s SC|
I don't see the error in "my" man page, sorry.
Right. Instead of hex "2d", as you properly have, I see the UTF-8 sequence "e2 80 90" (Unicode U+2010 Hyphen) in "my" man page.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
cer@Telcontar:~> locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES.utf8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES.utf8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=es_ES.utf8 LC_NAME=es_ES.utf8 LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE=es_ES.utf8 LC_MEASUREMENT=es_ES.utf8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= cer@Telcontar:~>
I'm surprised that your LC_CTYPE value is the same as mine. Isn't that the one that should determine character encodings? When I tried setting LC_ALL=C, the man page was OK (using hex 2d). OK also with LC_CTYPE=C . I only noticed the problem recently, with not just the susepaste man page BTW, so maybe there is a difference between Leap and Tumbleweed (which I am using). Some man pages are OK, though, and some use mixed hyphen-minus characters in some places, and then semi-randomly other "hyphens" elsewhere (man rsync).
-- Robert Webb
On 2024-02-01 13:52, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 12:39:40 +0100 (CET), "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Thursday, 2024-02-01 at 11:16 -0000, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al -- [...]
...
I don't see the error in "my" man page, sorry.
Right. Instead of hex "2d", as you properly have, I see the UTF-8 sequence "e2 80 90" (Unicode U+2010 Hyphen) in "my" man page.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
cer@Telcontar:~> locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES.utf8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES.utf8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=es_ES.utf8 LC_NAME=es_ES.utf8 LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE=es_ES.utf8 LC_MEASUREMENT=es_ES.utf8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= cer@Telcontar:~>
I'm surprised that your LC_CTYPE value is the same as mine. Isn't that the one that should determine character encodings?
It must be something else. I am using Leap 15.4 on this machine. Oh, and some of us may have installed susepaste from a different repo. I know I have tried several versions. Telcontar:~ # zypper info susepaste Loading repository data... Reading installed packages... Information for package susepaste: ---------------------------------- Repository : Update repository of openSUSE Backports Name : susepaste Version : 0.6-bp154.3.3.1 Arch : noarch Vendor : openSUSE Installed Size : 41.8 KiB Installed : Yes Status : up-to-date Source package : susepaste-0.6-bp154.3.3.1.src Upstream URL : https://susepaste.org Summary : Script for using openSUSE paste Description : A script for using the openSUSE paste service. You can paste either the file or input from stdin. Telcontar:~ # I think that is current the official version.
When I tried setting LC_ALL=C, the man page was OK (using hex 2d). OK also with LC_CTYPE=C .
I only noticed the problem recently, with not just the susepaste man page BTW, so maybe there is a difference between Leap and Tumbleweed (which I am using). Some man pages are OK, though, and some use mixed hyphen-minus characters in some places, and then semi-randomly other "hyphens" elsewhere (man rsync).
Maybe you should write a bugzilla. My guess is that the source of the manpage does have the "wrong" hyphen, but depending on something there is a conversion to the correct hyphen. # zcat /usr/share/man/man1/susepaste.1.gz | hexdump -C | less I see the 2d character there. I don't think the above does any conversion, but troff/groff maybe does. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 02-01-2024 07:17AM, Carlos E. R. wrote:
On 2024-02-01 13:52, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 12:39:40 +0100 (CET), "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Thursday, 2024-02-01 at 11:16 -0000, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote: > Carlos & PJ, et al -- > [...]
...
I don't see the error in "my" man page, sorry.
Right. Instead of hex "2d", as you properly have, I see the UTF-8 sequence "e2 80 90" (Unicode U+2010 Hyphen) in "my" man page.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
cer@Telcontar:~> locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES.utf8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES.utf8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=es_ES.utf8 LC_NAME=es_ES.utf8 LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE=es_ES.utf8 LC_MEASUREMENT=es_ES.utf8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= cer@Telcontar:~>
I'm surprised that your LC_CTYPE value is the same as mine. Isn't that the one that should determine character encodings?
It must be something else. I am using Leap 15.4 on this machine.
Oh, and some of us may have installed susepaste from a different repo. I know I have tried several versions.
Telcontar:~ # zypper info susepaste Loading repository data... Reading installed packages...
Information for package susepaste: ---------------------------------- Repository : Update repository of openSUSE Backports Name : susepaste Version : 0.6-bp154.3.3.1 Arch : noarch Vendor : openSUSE Installed Size : 41.8 KiB Installed : Yes Status : up-to-date Source package : susepaste-0.6-bp154.3.3.1.src Upstream URL : https://susepaste.org Summary : Script for using openSUSE paste Description : A script for using the openSUSE paste service. You can paste either the file or input from stdin.
Telcontar:~ #
I think that is current the official version.
This is the current susepaste version installed on this machine here: Thinkcentre-M57p:~ # zypper info susepaste Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... Information for package susepaste: ---------------------------------- Repository : repo-oss Name : susepaste Version : 0.6-7.1 Arch : noarch Vendor : openSUSE Installed Size : 41.8 KiB Installed : Yes (automatically) Status : up-to-date Source package : susepaste-0.6-7.1.src Upstream URL : https://github.com/openSUSE/paste Summary : Script for using openSUSE paste Description : A script for using the openSUSE paste service. You can paste either the file or input from stdin. Thinkcentre-M57p:~ #
When I tried setting LC_ALL=C, the man page was OK (using hex 2d). OK also with LC_CTYPE=C .
I only noticed the problem recently, with not just the susepaste man page BTW, so maybe there is a difference between Leap and Tumbleweed (which I am using). Some man pages are OK, though, and some use mixed hyphen-minus characters in some places, and then semi-randomly other "hyphens" elsewhere (man rsync).
Maybe you should write a bugzilla. My guess is that the source of the manpage does have the "wrong" hyphen, but depending on something there is a conversion to the correct hyphen.
# zcat /usr/share/man/man1/susepaste.1.gz | hexdump -C | less
I see the 2d character there. I don't think the above does any conversion, but troff/groff maybe does.
On 02-01-2024 07:17AM, Carlos E. R. wrote:
On 2024-02-01 13:52, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 12:39:40 +0100 (CET), "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Thursday, 2024-02-01 at 11:16 -0000, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote: > Carlos & PJ, et al -- > [...]
...
I don't see the error in "my" man page, sorry.
Right. Instead of hex "2d", as you properly have, I see the UTF-8 sequence "e2 80 90" (Unicode U+2010 Hyphen) in "my" man page.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
cer@Telcontar:~> locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES.utf8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES.utf8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=es_ES.utf8 LC_NAME=es_ES.utf8 LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE=es_ES.utf8 LC_MEASUREMENT=es_ES.utf8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= cer@Telcontar:~>
I'm surprised that your LC_CTYPE value is the same as mine. Isn't that the one that should determine character encodings?
It must be something else. I am using Leap 15.4 on this machine.
Oh, and some of us may have installed susepaste from a different repo. I know I have tried several versions.
Telcontar:~ # zypper info susepaste Loading repository data... Reading installed packages...
Information for package susepaste: ---------------------------------- Repository : Update repository of openSUSE Backports Name : susepaste Version : 0.6-bp154.3.3.1 Arch : noarch Vendor : openSUSE Installed Size : 41.8 KiB Installed : Yes Status : up-to-date Source package : susepaste-0.6-bp154.3.3.1.src Upstream URL : https://susepaste.org Summary : Script for using openSUSE paste Description : A script for using the openSUSE paste service. You can paste either the file or input from stdin.
Telcontar:~ #
I think that is current the official version.
When I tried setting LC_ALL=C, the man page was OK (using hex 2d). OK also with LC_CTYPE=C .
I only noticed the problem recently, with not just the susepaste man page BTW, so maybe there is a difference between Leap and Tumbleweed (which I am using). Some man pages are OK, though, and some use mixed hyphen-minus characters in some places, and then semi-randomly other "hyphens" elsewhere (man rsync).
Maybe you should write a bugzilla. My guess is that the source of the manpage does have the "wrong" hyphen, but depending on something there is a conversion to the correct hyphen.
# zcat /usr/share/man/man1/susepaste.1.gz | hexdump -C | less
I see the 2d character there. I don't think the above does any conversion, but troff/groff maybe does.
Also must have " not ' i.e. "which susepaste" *not* 'which susepaste' in [FILE] SYNOPSIS field. Syntax like this works: susepaste -t "susepaste Test File" -n "pj" -e "40320" "susepaste-test-0.txt" Link: https://paste.opensuse.org/pastes/5b6928cee0a4
On Thu, 1 Feb 2024 14:17:10 +0100, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-02-01 13:52, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 12:39:40 +0100 (CET), "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Thursday, 2024-02-01 at 11:16 -0000, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote: > Carlos & PJ, et al -- > [...]
...
I don't see the error in "my" man page, sorry.
Right. Instead of hex "2d", as you properly have, I see the UTF-8 sequence "e2 80 90" (Unicode U+2010 Hyphen) in "my" man page.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
cer@Telcontar:~> locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES.utf8 LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES.utf8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=es_ES.utf8 LC_NAME=es_ES.utf8 LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE=es_ES.utf8 LC_MEASUREMENT=es_ES.utf8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= cer@Telcontar:~>
I'm surprised that your LC_CTYPE value is the same as mine. Isn't that the one that should determine character encodings?
It must be something else. I am using Leap 15.4 on this machine.
Oh, and some of us may have installed susepaste from a different repo. I know I have tried several versions.
Telcontar:~ # zypper info susepaste Loading repository data... Reading installed packages...
Information for package susepaste: ---------------------------------- Repository : Update repository of openSUSE Backports Name : susepaste Version : 0.6-bp154.3.3.1 Arch : noarch Vendor : openSUSE Installed Size : 41.8 KiB Installed : Yes Status : up-to-date Source package : susepaste-0.6-bp154.3.3.1.src Upstream URL : https://susepaste.org Summary : Script for using openSUSE paste Description : A script for using the openSUSE paste service. You can paste either the file or input from stdin.
Telcontar:~ #
I think that is current the official version.
And mine on Tumbleweed: $ zypper if susepaste [...] Information for package susepaste: ---------------------------------- Repository : Main Repository (OSS) Name : susepaste Version : 0.6-7.1 Arch : noarch Vendor : openSUSE Installed Size : 41.8 KiB Installed : Yes (automatically) Status : up-to-date Source package : susepaste-0.6-7.1.src Upstream URL : https://github.com/openSUSE/paste Summary : Script for using openSUSE paste Description : A script for using the openSUSE paste service. You can paste either the file or input from stdin.
When I tried setting LC_ALL=C, the man page was OK (using hex 2d). OK also with LC_CTYPE=C .
I only noticed the problem recently, with not just the susepaste man page BTW, so maybe there is a difference between Leap and Tumbleweed (which I am using). Some man pages are OK, though, and some use mixed hyphen-minus characters in some places, and then semi-randomly other "hyphens" elsewhere (man rsync).
Maybe you should write a bugzilla. My guess is that the source of the manpage does have the "wrong" hyphen, but depending on something there is a conversion to the correct hyphen.
# zcat /usr/share/man/man1/susepaste.1.gz | hexdump -C | less
I see the 2d character there. I don't think the above does any conversion, but troff/groff maybe does.
The same. I only see the hyphen-minus character ('-' U+002D) and no hyphens ('‐' U+2010) in the source nroff file. $ for UCODE in 002D 2010 ;do eval "CHAR=$'\\u$UCODE'" ;printf '=== U+%s: %s: ' "$UCODE" "$CHAR" zcat /usr/share/man/man1/susepaste.1.gz |grep -o -e "$CHAR" |wc -l done === U+002D: -: 26 === U+2010: ‐: 0 -- Robert Webb
On Thu, 1 Feb 2024 12:39:40 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> wrote:
Sorry, no, I don't see it. You must have very good eyesight.
It's nothing to do with my eyesight. I simply cut-and-pasted pj's command and saw the same problem he did.
But you are right. Good catch.
I didn't catch it. David T-G did. It definitely needs a bug report. Who's writing it?
On 2024-02-01 21:42, Dave Howorth wrote:
On Thu, 1 Feb 2024 12:39:40 +0100 (CET) "Carlos E. R." <robin.listas@telefonica.net> wrote:
Sorry, no, I don't see it. You must have very good eyesight.
It's nothing to do with my eyesight. I simply cut-and-pasted pj's command and saw the same problem he did.
But you are right. Good catch.
I didn't catch it. David T-G did.
It definitely needs a bug report. Who's writing it?
I can not reproduce the error in the man page. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 02-01-2024 05:39AM, Carlos E. R. wrote:
echo "-" | hexdump -C
This is the output for the command above here below: # echo "-" | hexdump -C 00000000 2d 0a |-.| 00000002 When I pass the following command here there is 703 lines of output in Konsole so if it's still relevant let me know how to send the output back. # man susepaste | hexdump -C | less Carlos said: Why are you listing files, what is your intention with that? Just to try to explain that I am in the correct directory with the correct filename in it. 'pwd' would show directory. I'll start cutting out more lines before I paste. I just wanted to report back the best I can at what the output in Konsole is for me. Some of this is difficult for me to grasp but I felt compelled to send this message.
On 02-01-2024 05:16AM, Robert Webb via openSUSE Users wrote:
On Thu, 1 Feb 2024 09:12:45 +0000, Dave Howorth <dave@howorth.org.uk> wrote:
On Thu, 1 Feb 2024 00:53:24 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-01-2024 12:31AM, David T-G wrote:
Carlos & PJ, et al -- [...]
Why is this still a question??!? Does nobody else, really, see that PJ is using the wrong arg flag (something like an underscore but it's an extended char that I don't know what it is)?
davidtg@jpo:~> date | susepaste _t "with underscore" openSUSE Paste script
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] davidtg@jpo:~> date | susepaste -t "with hyphen" Paste failed :-(
Ignore the "failed" error for the moment; it doesn't matter. The important thing is that the script doesn't barf on the illegal character. Note that it takes a hyphen to indicate an argument. I don't know what kind of man page y'all are reading, but mine shows a minus sign.
I'm surprised nobody has confirmed what David is saying. He's right. For whatever reason it seems pj isn't using a normal hyphen character to introduce some of the arguments. Fix that and the commands should work.
For purposes of discussion, we need to have common terminology. The character used to introduce command-line options is what Wikipedia calls "Hyphen-minus". [1] Other characters that look like it are the Hyphen, Non-breaking hyphen, Minus sign, En dash, and Em dash.
If PJ is using something that isn't the proper hyphen-minus character, then maybe it is because he copy-pasted it right from the f'ed-up susepaste man page.
Some of you will see that none of the "hyphen-whatevers" shown for the option descriptions and the examples in the man page are the actual hyphen-minus. Others won't. It depends on your locale settings.
What do you think of this?: $ man susepaste |col -bx |grep -o -e '-' |wc -l 1
Yes, there is just one hyphen-minus in the whole man page. It is in the title line.
For me: $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
[1] https://en.wikipedia.org/wiki/Hyphen-minus
-- Robert Webb
Hi, this is the local output here: Thinkcentre-M57p:~> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" <- *NOT* LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Thinkcentre-M57p:~> I assume this above is the default locale.
On Thu, 1 Feb 2024 12:50:34 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote: [snip]
Hi, this is the local output here:
Thinkcentre-M57p:~> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" <- *NOT* LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Thinkcentre-M57p:~>
I assume this above is the default locale.
Can we take it that you now understand the problem and are able to correct your command line and run it OK, or do you still need some explanation?
On 02-01-2024 02:42PM, Dave Howorth wrote:
On Thu, 1 Feb 2024 12:50:34 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
[snip]
Hi, this is the local output here:
Thinkcentre-M57p:~> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" <- *NOT* LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Thinkcentre-M57p:~>
I assume this above is the default locale.
Can we take it that you now understand the problem and are able to correct your command line and run it OK, or do you still need some explanation? Things seem better now. See my latest post please. Thanks for your help with this.
On 2024-02-01 21:45, -pj via openSUSE Users wrote:
On 02-01-2024 02:42PM, Dave Howorth wrote:
On Thu, 1 Feb 2024 12:50:34 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
[snip]
Hi, this is the local output here:
Thinkcentre-M57p:~> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" <- *NOT* LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Thinkcentre-M57p:~>
I assume this above is the default locale.
Can we take it that you now understand the problem and are able to correct your command line and run it OK, or do you still need some explanation? Things seem better now. See my latest post please. Thanks for your help with this.
The question is if you can correct the wrong susepaste command you used: Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘ usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] There is an error there, which I intentionally left intact. Can you correct it and issue the correct command? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 02-01-2024 03:27PM, Carlos E. R. wrote:
On 2024-02-01 21:45, -pj via openSUSE Users wrote:
On 02-01-2024 02:42PM, Dave Howorth wrote:
On Thu, 1 Feb 2024 12:50:34 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
[snip]
Hi, this is the local output here:
Thinkcentre-M57p:~> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" <- *NOT* LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Thinkcentre-M57p:~>
I assume this above is the default locale.
Can we take it that you now understand the problem and are able to correct your command line and run it OK, or do you still need some explanation? Things seem better now. See my latest post please. Thanks for your help with this.
The question is if you can correct the wrong susepaste command you used:
Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file]
There is an error there, which I intentionally left intact. Can you correct it and issue the correct command?
Yes, with very limited success as shown from terminal below: Thinkcentre-M57p:/tmp # ls -lah total 4.8M drwxrwxrwt 16 root root 600 Feb 1 15:56 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. drwxrwxrwt 2 root root 60 Feb 1 12:35 .ICE-unix drwxrwxrwt 2 root root 60 Feb 1 12:35 .X11-unix drwxrwxrwt 2 root root 40 Feb 1 12:35 .XIM-unix drwxrwxrwt 2 root root 40 Feb 1 12:35 .font-unix srwx------ 1 paul paul 0 Feb 1 12:35 Qsynth:paul@paul-Thinkcentre-M57p drwx------ 2 paul paul 40 Feb 1 12:36 Temp-b9ec1e10-03dc-4b05-b5e2-0f9259ab2ad4 drwx------ 2 root root 100 Feb 1 15:15 YaST2-25975-LcR3p4 srwxrwxrwx 1 root root 0 Feb 1 15:10 dbus-uHDGSDWuyd -rw-r--r-- 1 paul paul 108 Feb 1 12:52 keepassxc-paul.lock srwx------ 1 paul paul 0 Feb 1 12:52 keepassxc-paul.socket drwx------ 2 paul paul 40 Feb 1 12:35 plasma-csd-generator.mSDvkw -rw-r----- 1 paul paul 0 Feb 1 12:35 qipc_sharedmemory_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a -rw-r----- 1 paul paul 0 Feb 1 12:35 qipc_systemsem_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a drwx------ 2 root root 40 Feb 1 15:10 runtime-root srwx------ 1 sddm sddm 0 Feb 1 12:35 sddm-:0-RaCFRZ srwxr-xr-x 1 root root 0 Feb 1 12:35 sddm-auth-9fda41f0-11c5-4814-b993-6ff2df47a56e -rw-r--r-- 1 paul paul 2.4M Feb 1 15:48 strace.log -rw-r--r-- 1 paul paul 45K Feb 1 15:42 strace.log.gz -rw-r--r-- 1 root root 2.4M Feb 1 15:48 strace.txt -rw-r--r-- 1 root root 28 Feb 1 15:56 susepaste-test-0.txt drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-ModemManager.service-2M2URv drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-chronyd.service-iZ82cu drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-polkit.service-EPffUY drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-power-profiles-daemon.service-t5x68k drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-systemd-logind.service-6hxk4q drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-upower.service-ROq8zK -rw------- 1 root root 66 Feb 1 15:10 xauth.XXXXkNVj3q -rw------- 1 paul paul 111 Feb 1 12:35 xauth_apDOSS Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "susepaste-test-0.txt" Pasted as: https://susepaste.org/851aaae82c4d https://paste.opensuse.org/851aaae82c4d Link is also in your clipboard. Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log.gz" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.txt" Paste failed :-( Thinkcentre-M57p:/tmp # The small text file was able to uploaded to susepaste and the other files were not. The man page has ' *not* " in [file] SYNOPSIS usage. Is that the error you left intact?
On 2024-02-01 23:06, -pj via openSUSE Users wrote:
On 02-01-2024 03:27PM, Carlos E. R. wrote:
...
The question is if you can correct the wrong susepaste command you used:
Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file]
There is an error there, which I intentionally left intact. Can you correct it and issue the correct command?
Yes, with very limited success as shown from terminal below: Thinkcentre-M57p:/tmp # ls -lah total 4.8M drwxrwxrwt 16 root root 600 Feb 1 15:56 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. drwxrwxrwt 2 root root 60 Feb 1 12:35 .ICE-unix drwxrwxrwt 2 root root 60 Feb 1 12:35 .X11-unix drwxrwxrwt 2 root root 40 Feb 1 12:35 .XIM-unix drwxrwxrwt 2 root root 40 Feb 1 12:35 .font-unix srwx------ 1 paul paul 0 Feb 1 12:35 Qsynth:paul@paul-Thinkcentre-M57p drwx------ 2 paul paul 40 Feb 1 12:36 Temp-b9ec1e10-03dc-4b05-b5e2-0f9259ab2ad4
Why are you listing files, what is your intention with that?
drwx------ 2 root root 100 Feb 1 15:15 YaST2-25975-LcR3p4 srwxrwxrwx 1 root root 0 Feb 1 15:10 dbus-uHDGSDWuyd -rw-r--r-- 1 paul paul 108 Feb 1 12:52 keepassxc-paul.lock srwx------ 1 paul paul 0 Feb 1 12:52 keepassxc-paul.socket drwx------ 2 paul paul 40 Feb 1 12:35 plasma-csd-generator.mSDvkw -rw-r----- 1 paul paul 0 Feb 1 12:35 qipc_sharedmemory_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a -rw-r----- 1 paul paul 0 Feb 1 12:35 qipc_systemsem_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a drwx------ 2 root root 40 Feb 1 15:10 runtime-root srwx------ 1 sddm sddm 0 Feb 1 12:35 sddm-:0-RaCFRZ srwxr-xr-x 1 root root 0 Feb 1 12:35 sddm-auth-9fda41f0-11c5-4814-b993-6ff2df47a56e -rw-r--r-- 1 paul paul 2.4M Feb 1 15:48 strace.log -rw-r--r-- 1 paul paul 45K Feb 1 15:42 strace.log.gz -rw-r--r-- 1 root root 2.4M Feb 1 15:48 strace.txt -rw-r--r-- 1 root root 28 Feb 1 15:56 susepaste-test-0.txt drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-ModemManager.service-2M2URv drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-chronyd.service-iZ82cu drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-polkit.service-EPffUY drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-power-profiles-daemon.service-t5x68k drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-systemd-logind.service-6hxk4q drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-upower.service-ROq8zK -rw------- 1 root root 66 Feb 1 15:10 xauth.XXXXkNVj3q -rw------- 1 paul paul 111 Feb 1 12:35 xauth_apDOSS
All that listing serves no purpose.
Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "susepaste-test-0.txt" Pasted as: https://susepaste.org/851aaae82c4d https://paste.opensuse.org/851aaae82c4d Link is also in your clipboard.
Ok, good.
Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log.gz" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.txt" Paste failed :-( Thinkcentre-M57p:/tmp #
The small text file was able to uploaded to susepaste and the other files were not.
The man page has ' *not* " in [file] SYNOPSIS usage. Is that the error you left intact?
No, the hyphen. That 23 MB trace file fails for me also. cer@Telcontar:~/Downloads/Thunderbird_downloads> susepaste -n "Carlos E.R." -t "test" -e 60 strace.txt Paste failed :-( cer@Telcontar:~/Downloads/Thunderbird_downloads> -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 02-02-2024 12:00noon, Carlos E. R. wrote:
On 2024-02-01 23:06, -pj via openSUSE Users wrote:
On 02-01-2024 03:27PM, Carlos E. R. wrote:
...
The question is if you can correct the wrong susepaste command you used:
Thinkcentre-M57p:/tmp> susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘
usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file]
There is an error there, which I intentionally left intact. Can you correct it and issue the correct command?
Yes, with very limited success as shown from terminal below: Thinkcentre-M57p:/tmp # ls -lah total 4.8M drwxrwxrwt 16 root root 600 Feb 1 15:56 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. drwxrwxrwt 2 root root 60 Feb 1 12:35 .ICE-unix drwxrwxrwt 2 root root 60 Feb 1 12:35 .X11-unix drwxrwxrwt 2 root root 40 Feb 1 12:35 .XIM-unix drwxrwxrwt 2 root root 40 Feb 1 12:35 .font-unix srwx------ 1 paul paul 0 Feb 1 12:35 Qsynth:paul@paul-Thinkcentre-M57p drwx------ 2 paul paul 40 Feb 1 12:36 Temp-b9ec1e10-03dc-4b05-b5e2-0f9259ab2ad4
Why are you listing files, what is your intention with that?
drwx------ 2 root root 100 Feb 1 15:15 YaST2-25975-LcR3p4 srwxrwxrwx 1 root root 0 Feb 1 15:10 dbus-uHDGSDWuyd -rw-r--r-- 1 paul paul 108 Feb 1 12:52 keepassxc-paul.lock srwx------ 1 paul paul 0 Feb 1 12:52 keepassxc-paul.socket drwx------ 2 paul paul 40 Feb 1 12:35 plasma-csd-generator.mSDvkw -rw-r----- 1 paul paul 0 Feb 1 12:35 qipc_sharedmemory_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a -rw-r----- 1 paul paul 0 Feb 1 12:35 qipc_systemsem_QsynthpaulpaulThinkcentreMpd29f10059f45e91e7d7e0499ae5d69f4aaf3d93a drwx------ 2 root root 40 Feb 1 15:10 runtime-root srwx------ 1 sddm sddm 0 Feb 1 12:35 sddm-:0-RaCFRZ srwxr-xr-x 1 root root 0 Feb 1 12:35 sddm-auth-9fda41f0-11c5-4814-b993-6ff2df47a56e -rw-r--r-- 1 paul paul 2.4M Feb 1 15:48 strace.log -rw-r--r-- 1 paul paul 45K Feb 1 15:42 strace.log.gz -rw-r--r-- 1 root root 2.4M Feb 1 15:48 strace.txt -rw-r--r-- 1 root root 28 Feb 1 15:56 susepaste-test-0.txt drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-ModemManager.service-2M2URv drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-chronyd.service-iZ82cu drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-polkit.service-EPffUY drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-power-profiles-daemon.service-t5x68k drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-systemd-logind.service-6hxk4q drwx------ 3 root root 60 Feb 1 12:35 systemd-private-f57c726f1c934386a35f2e6379fc96b5-upower.service-ROq8zK -rw------- 1 root root 66 Feb 1 15:10 xauth.XXXXkNVj3q -rw------- 1 paul paul 111 Feb 1 12:35 xauth_apDOSS
All that listing serves no purpose.
Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "susepaste-test-0.txt" Pasted as: https://susepaste.org/851aaae82c4d https://paste.opensuse.org/851aaae82c4d Link is also in your clipboard.
Ok, good.
Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log.gz" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.txt" Paste failed :-( Thinkcentre-M57p:/tmp #
The small text file was able to uploaded to susepaste and the other files were not.
The man page has ' *not* " in [file] SYNOPSIS usage. Is that the error you left intact?
No, the hyphen.🙁
So, the manpage is using hypen-minus in it's example and there is only one minus used (in the title of the manpage). So don't try to copy/paste the command example in for any sort of template is the motto here. Must issue the - from your own machine not from manpage copy (which is actually a hyphen minus). I have had success with a small test file and a small screenshot so far. I do not know what the data cap on uploading to susepaste is.
That 23 MB trace file fails for me also.
cer@Telcontar:~/Downloads/Thunderbird_downloads> susepaste -n "Carlos E.R." -t "test" -e 60 strace.txt Paste failed :-( cer@Telcontar:~/Downloads/Thunderbird_downloads>
Try using the command you issued above with quotes also around "strace.txt" *not* strace.txt without quotes. See this example below.Also probably create a small text file for testing because, susepaste does not want even 4 MB files uploaded it seems. Let alone 24 MB files. Thinkcentre-M57p:~/Desktop> susepaste -n "-pj" -t "test" -e 3600 "susepaste-test-0.txt" Pasted as: https://susepaste.org/91d5fe146ef0 https://paste.opensuse.org/91d5fe146ef0 Link is also in your clipboard. 🙁
On Fri, 2 Feb 2024 12:29:04 -0600, -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-02-2024 12:00noon, Carlos E. R. wrote:
On 2024-02-01 23:06, -pj via openSUSE Users wrote:
Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.log.gz" Paste failed :-( Thinkcentre-M57p:/tmp # susepaste -t "-pj susepaste-test-0.txt" -e "1080" -n "-pj" "strace.txt" Paste failed :-( Thinkcentre-M57p:/tmp #
The small text file was able to uploaded to susepaste and the other files were not.
The man page has ' *not* " in [file] SYNOPSIS usage. Is that the error you left intact?
No, the hyphen.🙁
So, the manpage is using hypen-minus in it's example and there is only one minus used (in the title of the manpage). So don't try to copy/paste the command example in for any sort of template is the motto here. Must issue the - from your own machine not from manpage copy (which is actually a hyphen minus). I have had success with a small test file and a small screenshot so far. I do not know what the data cap on uploading to susepaste is.
You took away the right message, but to correct a couple of details - You mixed up where the different hyphens are in the susepaste man page (as displayed to me, but not to Carlos. You never said what you saw there, BTW). The Unicode Hyphen-minus, alternately known as the ASCII (hex 2D) hyphen, is used for command-line options. It is NOT the same as the Unicode Hyphen, and the Unicode Minus is unique from those two. For me, all of the "hyphens" in the man page, except the first one, show as *Unicode Hyphen*, not "hyphen-minus". That is, of course, wrong, and to copy and paste those from the man page would not work. You're correct about that. As a work-around, 'LC_CTYPE=C man susepaste' will display all the "hyphens" as the hex '2d' version.
That 23 MB trace file fails for me also.
cer@Telcontar:~/Downloads/Thunderbird_downloads> susepaste -n "Carlos E.R." -t "test" -e 60 strace.txt Paste failed :-( cer@Telcontar:~/Downloads/Thunderbird_downloads>
Try using the command you issued above with quotes also around "strace.txt" *not* strace.txt without quotes. See this example below.Also probably create a small text file for testing because, susepaste does not want even 4 MB files uploaded it seems. Let alone 24 MB files.
It would be helpful to see the errors. I modified the susepaste script to write a log file from the paste operation done by the 'curl' command: susepaste-curl_log.sh pasted to: https://paste.opensuse.org/9dd778c3c9d2 (expire: 1 month) Specify a path for a log file to be written as the first argument. usage: susepaste-curl_log.sh <curl_log> [options] [FILE] To run it, you still need susepaste installed to get this sed script called by the susepaste script: /usr/share/susepaste/lang-mappings.sed I have attached a diff of the changes to the script: susepaste-curl_log.diff When pasting the script, I was getting "Paste failed" whenever I set an expire time greater than one month. In the log were the messages: "We are completely uploaded and fine" but then later: "We're sorry, but something went wrong." "If you are the application owner check the logs for more information." 'curl' then exited without an error. The script, though, didn't get the URL location info from the curl output, and so failed. -- Robert Webb
On 02-01-2024 05:16AM, Robert Webb via openSUSE Users wrote:
man susepaste |col -bx |grep -o -e '-' |wc -l
Seen here as follows: > man susepaste |col -bx |grep -o -e '-' |wc -l 1 /usr/share/susepaste> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" <---Different LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
-pj composed on 2024-01-31 19:39 (UTC-0600):
Which application do you use for file compression typically?
When I need more compression than average: tar -cvjf targetfile source When it shouldn't matter, I use either tar -cfzf, or create a .zip. Try all three and check the different resulting sizes FYOI.
Should strace.txt be changed back to strace.log before compression?
Not necessary. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 01-31-2024 08:19PM, Felix Miata wrote:
-pj composed on 2024-01-31 19:39 (UTC-0600):
Which application do you use for file compression typically?
When I need more compression than average:
tar -cvjf targetfile source
When it shouldn't matter, I use either tar -cfzf, or create a .zip. Try all three and check the different resulting sizes FYOI.
Should strace.txt be changed back to strace.log before compression?
Not necessary. Thanks again for this excellent insight. There is now a tarball named strace.tar.gz and it is only 77k in size now after compression.
On 2024-02-01 03:45, -pj via openSUSE Users wrote:
On 01-31-2024 08:19PM, Felix Miata wrote:
-pj composed on 2024-01-31 19:39 (UTC-0600):
Which application do you use for file compression typically?
When I need more compression than average:
tar -cvjf targetfile source
When it shouldn't matter, I use either tar -cfzf, or create a .zip. Try all three and check the different resulting sizes FYOI.
Should strace.txt be changed back to strace.log before compression?
Not necessary. Thanks again for this excellent insight. There is now a tarball named strace.tar.gz and it is only 77k in size now after compression.
Notice that using "tar" is an extra step that is not necessary when compressing a single file, and complicates reading at the other end. Simply use "gzip strace.txt" which will convert the file to "strace.txt.gz". The file can be read directly with commands like "less strace.txt.gz". -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 02-01-2024 05:43AM, Carlos E. R. wrote:
Notice that using "tar" is an extra step that is not necessary when compressing a single file, and complicates reading at the other end.
Simply use "gzip strace.txt" which will convert the file to "strace.txt.gz". The file can be read directly with commands like "less strace.txt.gz".
Thank you for that insight.
PJ, et al -- ...and then OpenSuSE users said... % % Ok, thanks for your insight into this. I have been confused about this % for some time actually. Is it acceptable to attach the strace.log file % to a message in Thunderbird or is that not a good way? What do you think % I should do about this situation? Can't be any worse than all of that HTML email bloat, right? ;-) HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
On 01-31-2024 05:57PM, David T-G wrote:
PJ, et al --
...and then OpenSuSE users said... % % Ok, thanks for your insight into this. I have been confused about this % for some time actually. Is it acceptable to attach the strace.log file % to a message in Thunderbird or is that not a good way? What do you think % I should do about this situation?
Can't be any worse than all of that HTML email bloat, right? ;-)
HAND
:-D -rw-r--r-- 1 paul paul 23M Jan 31 14:30 strace..txt
EXAMPLES How to post list of your usb devices: lsusb ‐v | TITLE="My usb devices" NICK="Geeko" susepaste lsusb ‐v | susepaste ‐t "My usb devices" ‐n "Geeko" How to post susepaste that will last six hours: susepaste ‐t "openSUSE paste" ‐e "360" ‐f "bash" ‘which susepaste‘ How to post an image that will last three hours: susepaste ‐t "openSUSE image" ‐e "180" ‐f "image" example.png - susepaste ‐t "-pj strace.txt" ‐e "1080" ‐f "text" ‘strace.txt‘ openSUSE Paste script usage: susepaste [-f format] [-n nick] [-t title] [-e expire] [-s schema] [file] I'm still trying to get this to work but maybe strace.txt is to large.
On 01-31-2024 01:37PM, Andrei Borzenkov wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Also
strace -o /tmp/strace.log journalctl -b
and upload /tmp/strace.log to https://paste.opensuse.org/
Hi, I was unable to upload the strace file to https://paste.opensuse.org/ I was able to commress the file into tarball form named strace.tar.gz (76k), and attached it to this message for review. Thanks again for your help with this.
What is the 's' in group for in /run/log/journal/systemd-journal and /var/log/journal/systemd-journal (stickybit)? What is the file d27ebfd1ed87479da329ef76152c4dc3 used for?
What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
On 01.02.2024 06:03, -pj via openSUSE Users wrote:
On 01-31-2024 01:37PM, Andrei Borzenkov wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Also
strace -o /tmp/strace.log journalctl -b
and upload /tmp/strace.log to https://paste.opensuse.org/
Hi, I was unable to upload the strace file to https://paste.opensuse.org/ I was able to commress the file into tarball form named strace.tar.gz (76k), and attached it to this message for review. Thanks again for your help with this.
Did you receive the warning from journalctl? Because I do not see anything in this strace, it run normally as expected.
On 01-31-2024 10:01PM, Andrei Borzenkov wrote:
On 01.02.2024 06:03, -pj via openSUSE Users wrote:
On 01-31-2024 01:37PM, Andrei Borzenkov wrote:
On 31.01.2024 21:54, -pj via openSUSE Users wrote:
On 01-31-2024 12:37AM, Andrei Borzenkov wrote:
On Wed, Jan 31, 2024 at 9:33 AM -pj via openSUSE Users <users@lists.opensuse.org> wrote:
Hi, I am receiving this message when passing: journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin>
Show
id -a
output. Also check permissions on journal (sub-)directories - /run/log/journal and /var/log/journal (and of course on the parent path).
Is this readable? Composition & Addressing > Composition > Compose messages in HTML format is toggled *off* in Thunderbird now.
Thinkcentre-M57p:/> id -a uid=1000(paul) gid=1000(paul) groups=1000(paul),474(systemd-journal),488(cdrom),489(audio)
Thinkcentre-M57p:/run/log/journal> ls -lah total 0 drwxr-sr-x 2 root systemd-journal 40 Jan 31 00:24 . drwxr-xr-x 3 root root 60 Jan 31 00:24 .. Thinkcenter-M57p:/run/log/journal>
Thinkcentre-M57p:/var/log/journal> ls -lah total 4.0K drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 . drwxr-xr-x 1 root root 1.4K Jan 31 00:25 .. drwxr-sr-x 1 root systemd-journal 16K Jan 31 00:25 d27ebfd1ed87479da329ef76152c4dc3 Thinkcentre-M57p:/var/log/journal>
This shows permissions of the content of /var/log/journal, not the /var/log/journal itself nor the permissions of individual journal files. Show
ls -ld /var/log/journal ls -l /var/log/journal/d27ebfd1ed87479da329ef76152c4dc3
Also
strace -o /tmp/strace.log journalctl -b
and upload /tmp/strace.log to https://paste.opensuse.org/
Hi, I was unable to upload the strace file to https://paste.opensuse.org/ I was able to commress the file into tarball form named strace.tar.gz (76k), and attached it to this message for review. Thanks again for your help with this.
Did you receive the warning from journalctl? Because I do not see anything in this strace, it run normally as expected.
Thanks for reviewing the strace file. What had made me concerned is the amount of yellow and red entries shown here when reviewing the output. Initially yes I was receiving the following: Hint: You are currently not seeing messages from other users and the
system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
The issue is that I am in the "systemd-journal" group. Since adding the user to systemd-journal group that issue is gone. Do you think working with 'Valgrind' could have some positive effect on the machine here?
On 2024-01-31 07:32, -pj via openSUSE Users wrote:
Hi, I am receiving this message when passing:journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice. The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin> What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
Powercycling fixed the issue? Had you added yourself to the "systemd-journal" group just in this session? Modifications to groups do not work till you restart the session. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 01-31-2024 05:47AM, Carlos E. R. wrote:
On 2024-01-31 07:32, -pj via openSUSE Users wrote:
Hi, I am receiving this message when passing:journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice. The issue is that I am in the "systemd-journal" group.
Thinkcentre-M57p:/usr/bin> groups paul
paul : paul audio cdrom systemd-journal
Thinkcentre-M57p:/usr/bin> What is going on here? What am I doing wrong and not understanding about this "Hint" above? Ok, powercycling fixed the issue. Do you recommend adding admin user to "systemd-journal" group typically?
Powercycling fixed the issue?
Had you added yourself to the "systemd-journal" group just in this session? Modifications to groups do not work till you restart the session.
Yes, in that session I added myself to the "systemd-journal" then I powercycled the machine. So you say that I could have just logged out and then back in.
participants (8)
-
-pj -
Andrei Borzenkov -
Carlos E. R. -
Dave Howorth -
David T-G -
Felix Miata -
Patrick Shanahan -
Robert Webb