Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux.mint > #46930 > unrolled thread
| Started by | yossarian <<nomail@gmail.com>> |
|---|---|
| First post | 2026-02-28 12:33 +0100 |
| Last post | 2026-03-03 05:18 +0000 |
| Articles | 20 on this page of 140 — 11 participants |
Back to article view | Back to alt.os.linux.mint
Very good rant about our loving linux yossarian <<nomail@gmail.com>> - 2026-02-28 12:33 +0100
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-02-28 10:23 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-01 01:40 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-01 15:15 -0500
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-28 22:08 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-02-28 14:25 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-01 01:33 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-01 07:24 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-01 08:27 -0800
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-03 02:54 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-02 22:21 -0500
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-03 04:52 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-03 05:31 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-03 09:17 -0800
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-03 21:17 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-03 13:44 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-03 14:03 -0800
Re: Very good rant about our loving linux yossarian <<nomail@gmail.com>> - 2026-03-04 10:35 +0100
Re: Very good rant about our loving linux "Alan K." <alan@invalid.com> - 2026-02-28 17:34 -0500
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-02-28 14:44 -0800
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-01 07:27 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-01 08:37 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-01 19:52 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-01 12:04 +1100
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-01 01:29 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-01 10:52 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-02 00:20 +1100
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-01 15:01 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-02 07:45 +1100
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-01 21:22 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-02 15:06 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-02 21:18 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-03 17:58 +1100
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-03 07:57 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-03 23:10 +1100
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-03 14:20 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-03 20:19 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-04 10:54 +1100
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-04 10:58 +1100
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-03 20:18 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-03 12:50 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-03 13:02 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-03 13:10 -0800
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-03 22:39 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-04 15:48 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-04 20:42 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-04 21:08 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-04 19:16 -0500
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-05 16:10 +1100
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-05 16:17 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-05 08:29 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-05 08:42 -0800
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-03 17:51 -0500
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-04 15:50 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-04 20:46 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-04 21:12 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-05 16:11 +1100
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-05 11:15 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-05 23:35 +1100
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-05 20:33 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-06 10:49 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-06 10:48 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-06 20:01 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-07 02:46 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-07 06:29 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-07 10:37 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-07 08:41 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-07 21:06 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-07 13:18 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-07 14:47 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-08 00:33 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-08 00:26 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-08 03:59 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-08 10:09 -0700
Re: Very good rant about our loving linux yossarian <<nomail@gmail.com>> - 2026-03-08 21:55 +0100
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-08 14:34 -0700
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-08 15:03 -0700
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-09 06:42 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-07 11:52 -0500
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-07 12:51 -0800
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-08 03:58 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-08 10:28 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-08 10:15 -0700
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-07 21:16 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-08 09:57 +0000
Re: Very good rant about our loving linux yossarian <<nomail@gmail.com>> - 2026-03-08 14:19 +0100
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-07 20:59 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-08 10:24 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-08 12:53 -0400
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-08 10:21 -0700
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-09 02:40 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-09 06:39 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-09 23:46 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-10 04:47 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-10 10:13 -0700
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-09 10:43 -0700
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-09 23:50 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-09 06:37 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-09 06:33 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-05 08:06 -0800
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-05 13:08 -0500
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-06 11:07 +0000
Re: Very good rant about our loving linux Axel <none@not.here> - 2026-03-07 00:18 +1100
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-06 19:52 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-06 09:38 -0500
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-06 18:13 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-05 20:01 +0000
Re: Very good rant about our loving linux "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-03-06 10:08 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-06 10:30 -0500
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-06 08:36 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-06 09:13 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-06 09:21 -0800
Re: Very good rant about our loving linux "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-03-06 18:18 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-06 11:14 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-06 20:13 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-07 00:09 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-06 20:09 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-06 10:52 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-06 19:55 +0000
Re: Very good rant about our loving linux RonB <ronb02NOSPAM@gmail.com> - 2026-03-07 02:43 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-03 08:00 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-03 22:38 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-03 21:30 -0500
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-04 11:56 +0000
Re: Very good rant about our loving linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-04 20:47 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-01 18:09 -0500
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-02 15:04 +0000
Re: Very good rant about our loving linux Paul <nospam@needed.invalid> - 2026-03-02 16:21 -0500
Re: Very good rant about our loving linux vallor <vallor@vallor.earth> - 2026-03-02 03:27 +0000
Re: Very good rant about our loving linux Handsome Jack <jack@handsome.com> - 2026-03-02 15:01 +0000
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-01 19:51 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-01 13:12 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-02 01:19 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-02 08:41 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-02 08:59 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-02 09:08 -0800
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-02 09:20 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-02 18:21 +0000
Re: Very good rant about our loving linux Mike Easter <MikeE@ster.invalid> - 2026-03-02 11:58 -0800
Re: Very good rant about our loving linux rbowman <bowman@montana.com> - 2026-03-03 05:18 +0000
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
| From | Handsome Jack <jack@handsome.com> |
|---|---|
| Date | 2026-03-03 08:00 +0000 |
| Message-ID | <10o64ec$1r9k6$2@dont-email.me> |
| In reply to | #46972 |
On Tue, 3 Mar 2026 17:58:07 +1100, Axel wrote: > Handsome Jack wrote: >> On Sun, 1 Mar 2026 21:22:49 -0000 (UTC), Lawrence D’Oliveiro wrote: >> >>> On Sun, 1 Mar 2026 15:01:00 -0000 (UTC), Handsome Jack wrote: >>> >>>> On Mon, 2 Mar 2026 00:20:44 +1100, Axel wrote: >>>> >>>>> Handsome Jack wrote: >>>>>> The main limitation of Linux (specifically LM) for me is that some >>>>>> minor things - matters of practical importance - do not work >>>>>> properly and there seems no prospect that they will get fixed. >>>>> what things? >>>> Just as one example, that Thunar regularly crashes. >>> Have you tried getting more info on the bug and sending in a report? >> No, but if I did that wouldn't change the fact that Thunar regularly >> crashes, and that that is not a satisfactory state of affairs. > > why not use some other file manager? I use LM22.3 and Thunar is not the > default manager > > I should have added: And this Thunar thing is only one of many small but annoying problems that don't look as they will ever get fixed. I can live with most of them - and Lord knows LM is still far preferable to Windows - but they are still problems.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-03-03 22:38 +0000 |
| Message-ID | <10o7nta$2eqop$1@dont-email.me> |
| In reply to | #46974 |
On Tue, 3 Mar 2026 08:00:12 -0000 (UTC), Handsome Jack wrote: > And this Thunar thing is only one of many small but annoying > problems that don't look as they will ever get fixed. Problems only get fixed if somebody fixes them. The code doesn’t write itself, you know.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2026-03-03 21:30 -0500 |
| Message-ID | <10o85fb$2ir0u$1@dont-email.me> |
| In reply to | #46974 |
On Tue, 3/3/2026 3:00 AM, Handsome Jack wrote: > On Tue, 3 Mar 2026 17:58:07 +1100, Axel wrote: > >> Handsome Jack wrote: >>> On Sun, 1 Mar 2026 21:22:49 -0000 (UTC), Lawrence D’Oliveiro wrote: >>> >>>> On Sun, 1 Mar 2026 15:01:00 -0000 (UTC), Handsome Jack wrote: >>>> >>>>> On Mon, 2 Mar 2026 00:20:44 +1100, Axel wrote: >>>>> >>>>>> Handsome Jack wrote: >>>>>>> The main limitation of Linux (specifically LM) for me is that some >>>>>>> minor things - matters of practical importance - do not work >>>>>>> properly and there seems no prospect that they will get fixed. >>>>>> what things? >>>>> Just as one example, that Thunar regularly crashes. >>>> Have you tried getting more info on the bug and sending in a report? >>> No, but if I did that wouldn't change the fact that Thunar regularly >>> crashes, and that that is not a satisfactory state of affairs. >> >> why not use some other file manager? I use LM22.3 and Thunar is not the >> default manager >> >> > > I should have added: And this Thunar thing is only one of many small but > annoying problems that don't look as they will ever get fixed. I can live > with most of them - and Lord knows LM is still far preferable to Windows - > but they are still problems. > At this point, we don't know much about your Thunar problem. "Regularly crashes" are the best kind of crashes, because you are claiming the crashes are reproducible on demand. You can then learn how to collect traces, and provide as much useful info as possible about the problem. Paul
[toc] | [prev] | [next] | [standalone]
| From | Handsome Jack <jack@handsome.com> |
|---|---|
| Date | 2026-03-04 11:56 +0000 |
| Message-ID | <10o96l0$2s91l$2@dont-email.me> |
| In reply to | #46991 |
On Tue, 3 Mar 2026 21:30:05 -0500, Paul wrote: > At this point, we don't know much about your Thunar problem. It just vanishes! No clue as to why. > "Regularly crashes" are the best kind of crashes, because you are > claiming the crashes are reproducible on demand. You can then learn how > to collect traces, and provide as much useful info as possible about the > problem. In demotic English, "regularly" also means "often" and that's the meaning I had in mind.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-03-04 20:47 +0000 |
| Message-ID | <10oa5p2$3856b$5@dont-email.me> |
| In reply to | #46993 |
On Wed, 4 Mar 2026 11:56:16 -0000 (UTC), Handsome Jack wrote: > On Tue, 3 Mar 2026 21:30:05 -0500, Paul wrote: > >> "Regularly crashes" are the best kind of crashes, because you are >> claiming the crashes are reproducible on demand. You can then learn >> how to collect traces, and provide as much useful info as possible >> about the problem. > > In demotic English, "regularly" also means "often" and that's the > meaning I had in mind. Still, if you can make it crash so easily, collecting the information that Paul mentioned shouldn’t be hard.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2026-03-01 18:09 -0500 |
| Message-ID | <10o2gut$lee6$1@dont-email.me> |
| In reply to | #46944 |
On Sun, 3/1/2026 10:01 AM, Handsome Jack wrote: > On Mon, 2 Mar 2026 00:20:44 +1100, Axel wrote: > >> Handsome Jack wrote: > >>> The main limitation of Linux (specifically LM) for me is that some >>> minor things - matters of practical importance - do not work properly >>> and there seems no prospect that they will get fixed. >> >> what things? > > Just as one example, that Thunar regularly crashes. > >> >>> The developers appear to be more interested in grand long-term projects >>> to replace things that already do work. >>> >>> >> the only thing that annoys me is the super small window controls- >> minimize, expand, close. I can't think of any good reason for making >> them that small. > > A presumably related one is that none of the window themes provide thick > enough borders that you can easily grab to resize the window. Here, have one of my scroll bars. They're free (if you can find one). OK, now let's adjust some columns in a File Manager, to our liking. What's that, you've given up already ? :-) Now, if my Thunar won't crash, what do you recommend I do ? When things like this happen, the very first question I ask, is what generation of RAM does the machine have ? Is it DDR2 for example, running faster than DDR2-533 ? DDR2 can be very stable... if you run it slow enough. DDR3/4/5 can be a bit better. Paul
[toc] | [prev] | [next] | [standalone]
| From | Handsome Jack <jack@handsome.com> |
|---|---|
| Date | 2026-03-02 15:04 +0000 |
| Message-ID | <10o48u6$17v3l$3@dont-email.me> |
| In reply to | #46953 |
On Sun, 1 Mar 2026 18:09:19 -0500, Paul wrote: > On Sun, 3/1/2026 10:01 AM, Handsome Jack wrote: >> On Mon, 2 Mar 2026 00:20:44 +1100, Axel wrote: >> >>> Handsome Jack wrote: >> >>>> The main limitation of Linux (specifically LM) for me is that some >>>> minor things - matters of practical importance - do not work properly >>>> and there seems no prospect that they will get fixed. >>> >>> what things? >> >> Just as one example, that Thunar regularly crashes. >> >> [snip] > When things like this happen, the very first question I ask, is what > generation of RAM does the machine have ? > Is it DDR2 for example, running faster than DDR2-533 ? > DDR2 can be very stable... if you run it slow enough. > DDR3/4/5 can be a bit better. I have no idea. Is it really a good idea to supply a file manager - one of the most vital tools of any OS - that crashes if you're using a specific type of RAM? None of my other applications do that.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2026-03-02 16:21 -0500 |
| Message-ID | <10o4v1h$1glo9$1@dont-email.me> |
| In reply to | #46957 |
On Mon, 3/2/2026 10:04 AM, Handsome Jack wrote:
> On Sun, 1 Mar 2026 18:09:19 -0500, Paul wrote:
>
>> On Sun, 3/1/2026 10:01 AM, Handsome Jack wrote:
>>> On Mon, 2 Mar 2026 00:20:44 +1100, Axel wrote:
>>>
>>>> Handsome Jack wrote:
>>>
>>>>> The main limitation of Linux (specifically LM) for me is that some
>>>>> minor things - matters of practical importance - do not work properly
>>>>> and there seems no prospect that they will get fixed.
>>>>
>>>> what things?
>>>
>>> Just as one example, that Thunar regularly crashes.
>>>
>>>
> [snip]
>> When things like this happen, the very first question I ask, is what
>> generation of RAM does the machine have ?
>> Is it DDR2 for example, running faster than DDR2-533 ?
>> DDR2 can be very stable... if you run it slow enough.
>> DDR3/4/5 can be a bit better.
>
>
> I have no idea. Is it really a good idea to supply a file manager - one of
> the most vital tools of any OS - that crashes if you're using a specific
> type of RAM? None of my other applications do that.
>
I'm explaining a typical root cause.
Even when you get a Dell or an HP, when you receive it, you should be
using "memtest" in the GRUB menu and test that the RAM is stable. A good memory
tester, tests from "0..Max" of the RAM. The BIOS has reserved locations
that must not be tested by non-BIOS activity, and memtest asks the BIOS
for the reservation list, before it tests. If you have four RAM slots, you
can put two sticks on one channel, test them, if they pass, turn off the
power and swap the two sticks (so the high stick takes the low stick role,
and the low stick takes the high stick role), and that comes the closest
to constructing a test to thoroughly test RAM. If you don't want to do
two RAM tests like that, just run one memtest with the sticks left in
their slots, and that's "close enough" for Thunar to not be crashing.
*******
On both Windows and Linux, setting up to capture crashes is a
pain in the ass. The easiest thing to do, is attach gdb to a
running application, and wait for a crash. Tools like this one,
may be able to do the stack trace for you and print it out.
https://wiki.ubuntu.com/Apport
Since that looked painful, we can compare the complexity to this one.
This one tells you how to "make a program with a bug in it". And
then the gdb result shows the stack trace for the bug. We run our
buggy program, and see if the stack trace points at the defective line.
Real programs can be "stripped" of line numbers, so then we have to be
content with just getting the "type of crash" as our evidence.
https://www.cs.toronto.edu/~krueger/csc209h/tut/gdb_tutorial.html
gdb is used for Ring3 programs (Thunar). kdb is used for kernel debugging.
Any time an executable has multiple processes or threads, this
greatly increases the brainpower you need to run the tools. For example,
if you do "ps" and see seven Firefox thingies running, which one
do you attach to ? That's part of the fun. On Firefox, the movie
player is the most likely one to crash, and maybe there is a good
reason to attach gdb to that PID when we figure out which Firefox
is the movie one.
Thunar can have great complexity inside, but attaching it shouldn't
be any worse than attaching to that sample program.
gdb /usr/bin/thunar /home/jack/Downloads
> run
... Thunar crashes
> backtrace
... Copy the screen info and put in a text file
> quit
Since Thunar deals with file systems at the virtual level,
it is "insulated" by doing things like stat() on files and
getting the "standard information" for them. Thunar is
a middle-man.
Using a program like "strace", you can watch what files Thunar was looking
at when it crashed. This would be as a second test run,
to collect some "behavioral" information up to the crash point.
https://man7.org/linux/man-pages/man1/strace.1.html
strace /usr/bin/thunar /home/jack/Downloads
and one of the things you see at first, is it "poking" the
Downloads folder and collecting information. Then, when you
start mousing around where that crash thing happens, the
last lines out of the strace in the terminal console,
hint at what file was helping that crash along. Thunar
does not have to crash on a "file reason" -- if it is
a RAM stability problem, the gdb result and the strace
result will be random and no discernible pattern will be
there. That's one of the reasons we might run the "memtest"
first, to assure ourselves how sweet the computer is and
it would never cause us problems like this :-) That's
why I memtest -- "trust, but verify" :-)
When using strace, set the scrollback on the terminal to
a high number of lines, as strace can produce a large amount
of output. While you can redirect the output to a text file,
I'd have to go look up whether the output is on stderr or not,
to make a tee and some redirects to make that work. For a first
run, you can just let it puke into the terminal. That's so you can
see how it works.
Paul
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2026-03-02 03:27 +0000 |
| Message-ID | <10o302o$pu0g$1@dont-email.me> |
| In reply to | #46944 |
At Sun, 1 Mar 2026 15:01:00 -0000 (UTC), Handsome Jack <jack@handsome.com> wrote: > On Mon, 2 Mar 2026 00:20:44 +1100, Axel wrote: > > > Handsome Jack wrote: > > >> The main limitation of Linux (specifically LM) for me is that some > >> minor things - matters of practical importance - do not work > >> properly and there seems no prospect that they will get fixed. > > > > what things? > > Just as one example, that Thunar regularly crashes. > > > > >> The developers appear to be more interested in grand long-term > >> projects to replace things that already do work. > >> > >> > > the only thing that annoys me is the super small window controls- > > minimize, expand, close. I can't think of any good reason for making > > them that small. > > A presumably related one is that none of the window themes provide > thick enough borders that you can easily grab to resize the window. > > I had that trouble before, but switched to one of the HiDPI themes. -- -v System76 Thelio Mega v1.1 x86_64 Mem: 258G OS: Linux 6.19.5 D: Mint 22.3 DE: Xfce 4.18 (X11) NVIDIA GeForce RTX 3090Ti (24G) (580.126.18) "...and on the seventh day, He exited from append mode."
[toc] | [prev] | [next] | [standalone]
| From | Handsome Jack <jack@handsome.com> |
|---|---|
| Date | 2026-03-02 15:01 +0000 |
| Message-ID | <10o48o3$17v3l$2@dont-email.me> |
| In reply to | #46955 |
On Mon, 02 Mar 2026 03:27:20 +0000, vallor wrote: > At Sun, 1 Mar 2026 15:01:00 -0000 (UTC), Handsome Jack > <jack@handsome.com> wrote: >> >> A presumably related one is that none of the window themes provide >> thick enough borders that you can easily grab to resize the window. >> >> >> > I had that trouble before, but switched to one of the HiDPI themes. Doesn't seem to make any difference on mine.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-03-01 19:51 +0000 |
| Message-ID | <n0jjl7Fpe4tU1@mid.individual.net> |
| In reply to | #46942 |
On Sun, 1 Mar 2026 10:52:45 -0000 (UTC), Handsome Jack wrote: > Neither inxi nor neofetch tell you. I don't even know what Wayland or > X11 are, or how they relate to XFCE or XFWM4 or any of the other > alphabet soups. I expect I could learn, but I don't know what good it > would do me. > I read the Wayland entry in Wikipedia and I couldn't make head or tail > of it. Neofetch does if you know what you're looking at. On the Ubuntu box WM: Mutter (Wayland) I have Cinnamon on the Mint box WM: Mutter (muffin) Muffin is a X11 windows manager. For Xfce you will probably see xfwm4, another X11 window manager.
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2026-03-01 13:12 -0800 |
| Message-ID | <n0jodeFq1diU1@mid.individual.net> |
| In reply to | #46942 |
Handsome Jack wrote: > Alan K. wrote: > >> If the machine runs, it's good. Oh I can get in the background and >> fix/adjust a few things but I couldn't tell you if I had Wayland or X11 >> (actually I could in LM). >> >> I also have a KDE OS and I don't know, easily, if it's KDE 5 or 6, >> Wayland or X11, systemd or other. To me, it works. I'd have to run >> inxi or neofetch to get a hint. > > Neither inxi nor neofetch tell you. > That is not quite correct; inxi has enough power to tell you about wayland, x11, KDE 5/6, and even systemd if you use -Ix. Neofetch is all about its 'appearance' so its help just tells you more ways to display it. Well, a little more than that, but not like inxi. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-03-02 01:19 +0000 |
| Message-ID | <n0k6s7Fs68eU1@mid.individual.net> |
| In reply to | #46951 |
On Sun, 1 Mar 2026 13:12:14 -0800, Mike Easter wrote: > Neofetch is all about its 'appearance' so its help just tells you more > ways to display it. Well, a little more than that, but not like inxi. The neofetch github was archived 2 years ago and it hadn't been touched for several years prior to that. Fastfetch is the replacement and on my Cinnamon laptop shows 'Muffin (X11)' for the WM. fastfetch --gen-config-full will create a JSON file in .config/fastfetch if you want to tweak it. There is a .config/neofetch configuration file but it doesn't have many options.
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2026-03-02 08:41 -0800 |
| Message-ID | <n0lst0F5g96U2@mid.individual.net> |
| In reply to | #46954 |
rbowman wrote: > Mike Easter wrote: > >> Neofetch is all about its 'appearance' so its help just tells you >> more ways to display it. Well, a little more than that, but not >> like inxi. > > The neofetch github was archived 2 years ago and it hadn't been > touched for several years prior to that. Fastfetch is the > replacement and on my Cinnamon laptop shows 'Muffin (X11)' for the > WM. > > fastfetch --gen-config-full will create a JSON file in .config/ > fastfetch if you want to tweak it. There is a .config/neofetch > configuration file but it doesn't have many options. > Well, I have no experience w/ fastfetch, but I LUV inxi. So I asked gglAIov: 'compare fastfetch and inxi' > Fastfetch and inxi are both command-line utilities used for > displaying system information on Linux, but they serve different > primary purposes: > Fastfetch is a modern, ultra-fast alternative to Neofetch designed > for visual, stylized output (often used in desktop screenshots), > while inxi is a comprehensive, deep-dive diagnostic tool designed > for system troubleshooting and hardware analysis. I'm not interested in neo- or fast-'s 'visual stylized output'. I want inxi's comprehensive deep-dive or a choice of an 'overview' or a verbose/detailed of only one section of its many parameters. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2026-03-02 08:59 -0800 |
| Message-ID | <n0ltvuF5g96U3@mid.individual.net> |
| In reply to | #46959 |
Mike Easter wrote: >> > Well, I have no experience w/ fastfetch, but I LUV inxi. So I asked > gglAIov: 'compare fastfetch and inxi' > >> Fastfetch and inxi are both command-line utilities used for >> displaying system information on Linux, but they serve different >> primary purposes: >> Fastfetch is a modern, ultra-fast alternative to Neofetch designed >> for visual, stylized output (often used in desktop screenshots), >> while inxi is a comprehensive, deep-dive diagnostic tool designed >> for system troubleshooting and hardware analysis. > > I'm not interested in neo- or fast-'s 'visual stylized output'. I want > inxi's comprehensive deep-dive or a choice of an 'overview' or a > verbose/detailed of only one section of its many parameters. > Well, rather than pay too much attention to some LLM, I installed fastfetch from a .ppa and ran it. I definitely like it better than neofetch, but it also definitely isn't inxi. I like to be able to 'focus' on a parameter, or not, depending; and to dive deeply or not, depending. inxi is great at that. -fast's dev/s are a little crazy for .json, which is like a foreign language to me. > Here is the documentation. It is generated from the JSON schema, but you might not find it very user-friendly. https://github.com/fastfetch-cli/fastfetch/wiki/Json-Schema?tab=readme-ov-file -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2026-03-02 09:08 -0800 |
| Message-ID | <n0lufvF5g96U4@mid.individual.net> |
| In reply to | #46960 |
Mike Easter cited: > >> Here is the documentation. It is generated from the JSON schema, but >> you might not find it very user-friendly. > OTOH, there's a very large man, 588 pp which tells me fast- has more power than I realized, in terms of isolating modules. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2026-03-02 09:20 -0800 |
| Message-ID | <n0lv7eF5g96U5@mid.individual.net> |
| In reply to | #46961 |
Mike Easter wrote: > OTOH, there's a very large man, 588 pp which tells me fast- has more > power than I realized, in terms of isolating modules. Oops; nevermind. It doesn't isolate (as a command option); but it has a lot of modules. I actually don't like it that much better than neofetch, which it surpasses; but it doesn't come up to inxi's ankles for me. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-03-02 18:21 +0000 |
| Message-ID | <n0m2ofF6gbeU2@mid.individual.net> |
| In reply to | #46962 |
On Mon, 2 Mar 2026 09:20:46 -0800, Mike Easter wrote:
> I actually don't like it that much better than neofetch, which it
> surpasses; but it doesn't come up to inxi's ankles for me.
Horse for courses.
$ inxi -w
Weather:
Report: temperature: 16.81 C (62 F) conditions: overcast clouds
Locale: None, CO, Unknown current time: Mon 02 Mar 2026 11:00:51 AM MST
(America/Denver) Source: OpenWeatherMap.org
Nice feature but the problem is I'm 900 miles from Denver. The problem
with inxi is unless I use -F, which is deprecated in favor of -e if you
ask it, you're dealing with
"You can use these options alone or together, # to show or add the item(s)
you want to see: A, B, C, d, D, E, f, G, i, I, j, J, l, L, m, M, n, N, o,
p, P, r, R, s, S, t, u, w, --edid, --mm, --ms, --slots. If you use them
with -b, -e, or -v [level], inxi will add the requested lines to the
report. "
Of course if you go digging fastfetch isn't much better.
You can have fun with fastfetch. For some reason if you go on subreddits
like r/linuxmint people love to show screen shots with fastfetch. The 'I
use Arch btw' gets sniffy. I actually use EndeavourOS on one box but I
hacked the config so it swears it's Arch Linux x86_64. You don't even
have to mess with the config. -l specifies the logo and there are 497
built in.
fastfetch --list-logos
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2026-03-02 11:58 -0800 |
| Message-ID | <n0m8eiF7mjjU1@mid.individual.net> |
| In reply to | #46963 |
rbowman wrote: > Horse for courses. > > $ inxi -w That isn't the way I use inxi's weather. I use my zip code, because my city (and county) have LOTS of different climates. In fact, I often use the zip code next to the west of me, because almost all the time there is a prevailing breeze from the west that comes thru' and around my house, and I feel that the weather report and forecast for that area is more like my weather than my own zip. Oops, wait; I lied :-/ (was mistaken about inxi) I don't use inxi for weather, I use wttr.in and my zip or my next W zip. curl wttr.in 'yourzip-noquote' The accuracy problem in an area like mine which has such a diverse bunch of microclimates, is how the system is 'rigged' to using particular /station/ databanks. There are little home reporters which may be closer than official jurisdictional weather reporting. Fortunately I have a NWS national weather service station not far to my west. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-03-03 05:18 +0000 |
| Message-ID | <n0n98vFcmsuU1@mid.individual.net> |
| In reply to | #46964 |
On Mon, 2 Mar 2026 11:58:09 -0800, Mike Easter wrote:
> There are little home reporters which may be closer than official
> jurisdictional weather reporting. Fortunately I have a NWS national
> weather service station not far to my west.
I just stumbled on inxi's weather report. emacs developers must have had a
hand in it. At least it doesn't tell fortunes afaik.
I wrote a Python program to pull down the weather from
https://api.weather.gov/points/{latitude},{longitude}
where I pass in the coordinates. That gives me the grid and I can get the
latest observations. The points query also returns the forecast url so I
can print out the next week like
Tuesday
Mostly sunny, with a high near 57. South wind 1 to 5 mph.
temperature: 57
wind 1 to 5 mph S
Tuesday Night
Rain likely after 11pm. Mostly cloudy, with a low around 34. South wind
around 5 mph. Chance of precipitation is 60%.
temperature: 34
wind 5 mph S
The return is JSON but is easily parsed in Python. I've got a program
running on the Raspberry Pi that reads the inside temp/humidity from a
DHT11 sensor that I'll expand to also get the current conditions. Output
it to a LCD for a little at a glance info.
[toc] | [prev] | [standalone]
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
Back to top | Article view | alt.os.linux.mint
csiph-web