[lubuntu-users] Forum continues to have problems loading or accessing

[Fritz Hudnut]

Folks:

Have a thread running on the forum, and from day to day sometimes it's
working and today, it isn't.  Forum won't load from "visit topic" link
in the email sent out when there are replies.

Several days ago I tried to use the "or reply from this email" to
provide a reply . . . days went by with "failed delivery" messages,
ending yesterday with:

[QUOTE] The response was:

The recipient server did not accept our requests to connect. Learn
more at https://support.google.com/mail/answer/7720
[discourse.lubuntu.me 15.204.140.176: FAILED_PRECONDITION: connect
error (113): No route to host]  [/QUOTE]

Usually the forum will not work when actually running Lubuntu . . .
today I'm in Manjaro and clicking on "Forum" link from the lubuntu.me
web site . . . fails to load the forum.

"Personal problem" or . . . "problem"???  Who knows.

F

-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Discourse forum seems broken (Mateusz Konieczny) (Nio W)

[Fritz Hudnut]

Had a moment to check the forum while in Pop!_OS .  . . and strange
dysfunctions, like I couldn't scroll up and down in a thread, but I
could change threads . . . and I could "reply" within the thread to
what I could see, but not scroll . . . .  Also in Firefox as I usually
am . . . but not in Lubuntu . .  . .

On Wed, Oct 26, 2022 at 7:25 AM Fritz Hudnut  wrote:
>
> >
> > Message: 2
> > Date: Wed, 26 Oct 2022 11:34:21 +0200
> > From: Nio Wiklund 
> > To: Mateusz Konieczny ,
> > lubuntu-users@lists.ubuntu.com
> > Subject: Re: [lubuntu-users] Discourse forum seems broken
> > Message-ID: <5e2cb8c8-639e-8230-bdf2-b57d16578...@gmail.com>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > Den 2022-10-26 kl. 11:26, skrev Mateusz Konieczny:
> > > If I enter say my
> > > https://discourse.lubuntu.me/t/how-can-i-change-which-software-is-used-to-open-folders/3716
> > >  
> > > <https://discourse.lubuntu.me/t/how-can-i-change-which-software-is-used-to-open-folders/3716>
> > > thread nothing on page is clickable or scrollable
> > >
> > > Console log has
> > > "Content Security Policy: The page's settings blocked the loading of a
> > > resource
> > > at inline ("script-src"). Source: // This script is inlined in
> > > `_discourse_splash.html.erb"
> > >
> > > Is it just me or general breakage?
> > >
> > > https://discourse.lubuntu.me/ <https://discourse.lubuntu.me/> seems to
> > > have no recent postings
> > >
> >
> > Hi Mateusz,
> >
> > It seems broken for me too. I cannot scroll down (so I cannot see the
> > bottom alias end) of a thread (I tested more one thread).
> >
> > So I hope someone with enough privileges on the website can fix the problem.
> >
> > Best regards
> > Nio
> >
> >
>
> Gents:
>
> This is a problem that does also "happen" to me . . . most often
> specifically if I'm running Lubuntu, links from digests won't work or
> forum opens to blank page.  But, if I flip over to another distro,
> then sometimes it will work . . . "ironic" no?
>
> There is a gent who is in charge . . . might have his name in the
> rolodex if he doesn't pick up the phone in a bit . . . can't recall
> right now.  He often thinks it relates to something in the browser . .
> . but the problem does recur . . . .  Maybe try flipping to another
> browser???
>
> F

-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Discourse forum seems broken (Mateusz Konieczny) (Nio W)

[Fritz Hudnut]

>
> Message: 2
> Date: Wed, 26 Oct 2022 11:34:21 +0200
> From: Nio Wiklund 
> To: Mateusz Konieczny ,
> lubuntu-users@lists.ubuntu.com
> Subject: Re: [lubuntu-users] Discourse forum seems broken
> Message-ID: <5e2cb8c8-639e-8230-bdf2-b57d16578...@gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Den 2022-10-26 kl. 11:26, skrev Mateusz Konieczny:
> > If I enter say my
> > https://discourse.lubuntu.me/t/how-can-i-change-which-software-is-used-to-open-folders/3716
> >  
> > 
> > thread nothing on page is clickable or scrollable
> >
> > Console log has
> > "Content Security Policy: The page's settings blocked the loading of a
> > resource
> > at inline ("script-src"). Source: // This script is inlined in
> > `_discourse_splash.html.erb"
> >
> > Is it just me or general breakage?
> >
> > https://discourse.lubuntu.me/  seems to
> > have no recent postings
> >
>
> Hi Mateusz,
>
> It seems broken for me too. I cannot scroll down (so I cannot see the
> bottom alias end) of a thread (I tested more one thread).
>
> So I hope someone with enough privileges on the website can fix the problem.
>
> Best regards
> Nio
>
>

Gents:

This is a problem that does also "happen" to me . . . most often
specifically if I'm running Lubuntu, links from digests won't work or
forum opens to blank page.  But, if I flip over to another distro,
then sometimes it will work . . . "ironic" no?

There is a gent who is in charge . . . might have his name in the
rolodex if he doesn't pick up the phone in a bit . . . can't recall
right now.  He often thinks it relates to something in the browser . .
. but the problem does recur . . . .  Maybe try flipping to another
browser???

F

-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

@Is:

Yes.  I did both, reinstalled grub and then "mkconfig'd" it and on cold
boot, selecting Lubuntu now brings verbose log in/dmesg, or it shows up . .
. in the fairly slow boot process . . . but got there!!  And uname -r shows
5.19xxx kernel . . . 

It takes a village . . . in my case.  I guess the thing was, after erasing
the 5.13 kernel I edited the individual grub item data, but didn't run
another "grub2-mkconfig" to solidify the edits??  Or, in this case, find
the newer kernel and register it, etc.

I started a new thread on Discourse, but since I'm now running Lubuntu I
can't post an update there . . . ?  : - 0

On Wed, Sep 21, 2022 at 10:00 AM Fritz Hudnut  wrote:

> Is:
>
> Thanks for the reply . . . I do "know" which distro is handling grub . . .
> the TW install, but they don't do the same "update-grub" command in SUSE,
> as I recall from past exploits trying to get grub tidied up . . . .  They
> do a command like "grub2-mkconfig xxx" which I did run yesterday.  They
> do offer reinstall with "grub2-install" . . . .
>
> I guess it wouldn't hurt to run that to see if it picks up the newer
> kernel in Lu . . . now that 5.13 is gone there should be a more clear
> "choice" . . . .
>
>
>
> On Wed, Sep 21, 2022 at 9:33 AM Israel Dahl  wrote:
>
>> Hey Fritz,
>>
>> The best way to update grub is using the `update-grub` CLI utility.
>> But you have to do it from the distro you installed grub with.  If you
>> can remember which one you installed grub with, simply run that command
>> using `sudo` and it should automatically detect the most recent kernel and
>> do it for you.
>>
>> If you cannot figure out which one you installed it with, reinstall grub
>> from the distro you use the most.
>>
>> On 9/21/22 11:06, Fritz Hudnut wrote:
>>
>> et al:
>>
>> Spoke too soon . . . not out of the woods on this one yet.  Seems like
>> the edits made in the grub "EFI" menu are not maintained on reboot??
>> Doesn't seem to be any hints on how to "save" the edits . . . just make
>> them and then boot them???  But, then it appears that the edits are lost
>> and it's back to the previous version??
>>
>> After I got 5.19 to boot I used the GUI mainline kernel app to remove the
>> old 5.13 kernel, to try to get the system to default to 5.19, but on trying
>> today it said, "5.13 not found, hit any key to continue" and back into Grub
>> menu we went.
>>
>> Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 5.19
>> and it booted up.
>>
>> Question is, why doesn't it hold the data??  I've changed both line
>> items, the "Lubuntu" and the "advanced options" data and I can boot it, one
>> time . . . .  I tried "ctrl o" but that didn't do anything . . . .  Do I
>> need to take it to "command line" and then try to "ctrl o" it to save it??
>>
>> F
>>
>> On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut 
>> wrote:
>>
>>> Top posting, with impunity!!
>>>
>>> So, I got a hint over on Discourse to "check the grub EFI menu" . . .
>>> and once I figured out how to do that, indeed, Lubuntu was listing itself
>>> as "19.10" and set to be booting 5.13 . . . took some more time to figure
>>> out how to edit that data, to the correct wording for the kernel . . . and
>>> that did seem to boot Lubuntu to 5.19!!!
>>>
>>> Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
>>> site loads as a white page . . . of whiteness.  I'll have to reboot into a
>>> non-Lu system to get it to load . . . .
>>>
>>> So far now it seems like the solution has been invoked . . . .
>>>
>>> F
>>>
>>>
>>> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund 
>>>> wrote:
>>>>
>>>>> Hi again Fritz,
>>>>>
>>>>> Is the problematic system your main system or 'only' a test system? If
>>>>> a
>>>>> test system you might just reinstall it to get rid of the problem.
>>>>>
>>>>> Best regards
>>>>> Nio
>>>>>
>>>>>
>>>>>
>>>>>
>> --
>> 
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Is:

Thanks for the reply . . . I do "know" which distro is handling grub . . .
the TW install, but they don't do the same "update-grub" command in SUSE,
as I recall from past exploits trying to get grub tidied up . . . .  They
do a command like "grub2-mkconfig xxx" which I did run yesterday.  They
do offer reinstall with "grub2-install" . . . .

I guess it wouldn't hurt to run that to see if it picks up the newer kernel
in Lu . . . now that 5.13 is gone there should be a more clear "choice" . .
. .



On Wed, Sep 21, 2022 at 9:33 AM Israel Dahl  wrote:

> Hey Fritz,
>
> The best way to update grub is using the `update-grub` CLI utility.
> But you have to do it from the distro you installed grub with.  If you can
> remember which one you installed grub with, simply run that command using
> `sudo` and it should automatically detect the most recent kernel and do it
> for you.
>
> If you cannot figure out which one you installed it with, reinstall grub
> from the distro you use the most.
>
> On 9/21/22 11:06, Fritz Hudnut wrote:
>
> et al:
>
> Spoke too soon . . . not out of the woods on this one yet.  Seems like the
> edits made in the grub "EFI" menu are not maintained on reboot??  Doesn't
> seem to be any hints on how to "save" the edits . . . just make them and
> then boot them???  But, then it appears that the edits are lost and it's
> back to the previous version??
>
> After I got 5.19 to boot I used the GUI mainline kernel app to remove the
> old 5.13 kernel, to try to get the system to default to 5.19, but on trying
> today it said, "5.13 not found, hit any key to continue" and back into Grub
> menu we went.
>
> Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 5.19
> and it booted up.
>
> Question is, why doesn't it hold the data??  I've changed both line items,
> the "Lubuntu" and the "advanced options" data and I can boot it, one time .
> . . .  I tried "ctrl o" but that didn't do anything . . . .  Do I need to
> take it to "command line" and then try to "ctrl o" it to save it??
>
> F
>
> On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut 
> wrote:
>
>> Top posting, with impunity!!
>>
>> So, I got a hint over on Discourse to "check the grub EFI menu" . . . and
>> once I figured out how to do that, indeed, Lubuntu was listing itself as
>> "19.10" and set to be booting 5.13 . . . took some more time to figure out
>> how to edit that data, to the correct wording for the kernel . . . and that
>> did seem to boot Lubuntu to 5.19!!!
>>
>> Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
>> site loads as a white page . . . of whiteness.  I'll have to reboot into a
>> non-Lu system to get it to load . . . .
>>
>> So far now it seems like the solution has been invoked . . . .
>>
>> F
>>
>>
>> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund 
>>> wrote:
>>>
>>>> Hi again Fritz,
>>>>
>>>> Is the problematic system your main system or 'only' a test system? If
>>>> a
>>>> test system you might just reinstall it to get rid of the problem.
>>>>
>>>> Best regards
>>>> Nio
>>>>
>>>>
>>>>
>>>>
> --
> 
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

et al:

Spoke too soon . . . not out of the woods on this one yet.  Seems like the
edits made in the grub "EFI" menu are not maintained on reboot??  Doesn't
seem to be any hints on how to "save" the edits . . . just make them and
then boot them???  But, then it appears that the edits are lost and it's
back to the previous version??

After I got 5.19 to boot I used the GUI mainline kernel app to remove the
old 5.13 kernel, to try to get the system to default to 5.19, but on trying
today it said, "5.13 not found, hit any key to continue" and back into Grub
menu we went.

Arrowed down to Lubuntu, pressed "e" and changed the kernel data to 5.19
and it booted up.

Question is, why doesn't it hold the data??  I've changed both line items,
the "Lubuntu" and the "advanced options" data and I can boot it, one time .
. . .  I tried "ctrl o" but that didn't do anything . . . .  Do I need to
take it to "command line" and then try to "ctrl o" it to save it??

F

On Tue, Sep 20, 2022 at 9:53 AM Fritz Hudnut  wrote:

> Top posting, with impunity!!
>
> So, I got a hint over on Discourse to "check the grub EFI menu" . . . and
> once I figured out how to do that, indeed, Lubuntu was listing itself as
> "19.10" and set to be booting 5.13 . . . took some more time to figure out
> how to edit that data, to the correct wording for the kernel . . . and that
> did seem to boot Lubuntu to 5.19!!!
>
> Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
> site loads as a white page . . . of whiteness.  I'll have to reboot into a
> non-Lu system to get it to load . . . .
>
> So far now it seems like the solution has been invoked . . . .
>
> F
>
>
> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund  wrote:
>>
>>> Hi again Fritz,
>>>
>>> Is the problematic system your main system or 'only' a test system? If a
>>> test system you might just reinstall it to get rid of the problem.
>>>
>>> Best regards
>>> Nio
>>>
>>>
>>>
>>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Top posting, with impunity!!

So, I got a hint over on Discourse to "check the grub EFI menu" . . . and
once I figured out how to do that, indeed, Lubuntu was listing itself as
"19.10" and set to be booting 5.13 . . . took some more time to figure out
how to edit that data, to the correct wording for the kernel . . . and that
did seem to boot Lubuntu to 5.19!!!

Only "problem" seems to be that when I'm booted in Lubuntu the Discourse
site loads as a white page . . . of whiteness.  I'll have to reboot into a
non-Lu system to get it to load . . . .

So far now it seems like the solution has been invoked . . . .

F

On Fri, Sep 16, 2022 at 5:58 PM Fritz Hudnut  wrote:

> Nio:
>
> Well, good question . . . based upon which system is the "problematic"
> one.  The Lubuntu install is one of the first that went on this machine . .
> . on the OEM HDD.  The grub handler is TW, and that also is fairly "old" .
> . . neither one of them is "test" per se . . . or ALL of them are.  Way
> back before I understood that I shouldn't let each install have a grub
> file, when I had a problem I would just do a fresh install, which would
> then freshen grub list and I'd be "OK" until the next fresh "bootloader"
> install, etc.
>
> Then I figured out (with the help of a forum slap upside the head) that
> only one system should handle grub.  The "wild card" in this is that ubuntu
> seems to have decided that it doesn't want to relinquish grub control, it
> keeps some strings attached . . . and I have two ubuntu based systems
> installed now, Lu & LM . . . .
>
> So, based upon knowing what has happened in the recent past when
> installing ubuntu, I'd somewhat like to avoid installing Lubuntu again . .
> . .  But, I have been considering a fresh install of TW into an SSD for "/"
> and that might tidy everybody else up in the process . . . ???
>
> On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund  wrote:
>
>> Hi again Fritz,
>>
>> Is the problematic system your main system or 'only' a test system? If a
>> test system you might just reinstall it to get rid of the problem.
>>
>> Best regards
>> Nio
>>
>>
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Nio:

Well, good question . . . based upon which system is the "problematic"
one.  The Lubuntu install is one of the first that went on this machine . .
. on the OEM HDD.  The grub handler is TW, and that also is fairly "old" .
. . neither one of them is "test" per se . . . or ALL of them are.  Way
back before I understood that I shouldn't let each install have a grub
file, when I had a problem I would just do a fresh install, which would
then freshen grub list and I'd be "OK" until the next fresh "bootloader"
install, etc.

Then I figured out (with the help of a forum slap upside the head) that
only one system should handle grub.  The "wild card" in this is that ubuntu
seems to have decided that it doesn't want to relinquish grub control, it
keeps some strings attached . . . and I have two ubuntu based systems
installed now, Lu & LM . . . .

So, based upon knowing what has happened in the recent past when installing
ubuntu, I'd somewhat like to avoid installing Lubuntu again . . . .  But, I
have been considering a fresh install of TW into an SSD for "/" and that
might tidy everybody else up in the process . . . ???

On Fri, Sep 16, 2022 at 3:45 PM Nio Wiklund  wrote:

> Hi again Fritz,
>
> Is the problematic system your main system or 'only' a test system? If a
> test system you might just reinstall it to get rid of the problem.
>
> Best regards
> Nio
>
> Den 2022-09-16 kl. 21:17, skrev Fritz Hudnut:
> > Nio:
> >
> > Thanks for getting back to me about it . . . .  I haven't had the time
> > to mess with it just yet.  I was thinking that that UUID number didn't
> > match anything in, what, "blkid" . . . ???  I couldn't find in my notes
> > how to see what my master grub in TW is using to identify the UUID
> > numbers of each of the 8 systems "/" filesystem to know where to boot
> it??
> >
> > And, then I wasn't sure if I needed to fix that "resume from swap"
> > issue, or if that is correct and what should be resumed from???  I have
> > had this issue show up over the years, learned how to fix it, fixed it .
> > . . but then time passes and I forget the way to fix it . . . .
> >
> > It's not the end of the world, it's just that kinetic is now stuck in
> > 5.13 . . . instead of 5.19 . . . .  The question is, whether the problem
> > is something in Lubuntu that "messed with itself" OR as "historically,"
> > something in "ubuntu" grub cut across into the master grub file data in
> > TW and created a problem for Lubuntu
> >
> > On Fri, Sep 16, 2022 at 11:55 AM Nio Wiklund  > <mailto:nio.wikl...@gmail.com>> wrote:
> >
> > Hi Fritz,
> >
> > I think (but am not sure) that 'resume' means resume from hibernation
> > using the swap space at the specified target. Please check if that
> UUID
> > matches a swap partition.
> >
> > Best regards
> > Nio
> >
> > Den 2022-09-11 kl. 20:45, skrev Fritz Hudnut:
> >  > Top posting:
> >  >
> >  > This is the current data from Lubuntu, and that UUID number
> > doesn't show
> >  > up anywhere in "sudo blkid" from in the Lu system.  But I did
> > write that
> >  > number down from some "error" reports showing in the console
> > during the
> >  > last apt dist-upgrade that I ran yesterday in Lu.  Somehow
> > perhaps apt
> >  > did something to  mess itself up??
> >  >
> >  > [CODE] sudo cat /etc/default/grub
> >  > # If you change this file, run 'update-grub' afterwards to update
> >  > # /boot/grub/grub.cfg.
> >  > # For full documentation of the options in this file, see:
> >  > #   info -f grub -n 'Simple configuration'
> >  >
> >  > GRUB_DEFAULT=0
> >  > GRUB_TIMEOUT=0
> >  > GRUB_DISTRIBUTOR='lubuntu1910'
> >  > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
> >  > resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0"
> >  > GRUB_CMDLINE_LINUX="" [/CODE]
> >  >
> >  > Do I want to edit that "quiet splash resume" data to match the
> > /dev/sdc7
> >  > location of the Lubuntu "/" UUID??
> >  >
> >  > [CODE] /dev/sdc7: UUID="17bcb813-d05e-4cc3-bcdf-16d283156780"
> > [/CODE]
> >  >
> >  > And, then try to again run the grub bootloader to get it to find
> > a newer
> >  > loca

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Nio:

Thanks for getting back to me about it . . . .  I haven't had the time to
mess with it just yet.  I was thinking that that UUID number didn't match
anything in, what, "blkid" . . . ???  I couldn't find in my notes how to
see what my master grub in TW is using to identify the UUID numbers of each
of the 8 systems "/" filesystem to know where to boot it??

And, then I wasn't sure if I needed to fix that "resume from swap" issue,
or if that is correct and what should be resumed from???  I have had this
issue show up over the years, learned how to fix it, fixed it . . . but
then time passes and I forget the way to fix it . . . .

It's not the end of the world, it's just that kinetic is now stuck in 5.13
. . . instead of 5.19 . . . .  The question is, whether the problem is
something in Lubuntu that "messed with itself" OR as "historically,"
something in "ubuntu" grub cut across into the master grub file data in TW
and created a problem for Lubuntu

On Fri, Sep 16, 2022 at 11:55 AM Nio Wiklund  wrote:

> Hi Fritz,
>
> I think (but am not sure) that 'resume' means resume from hibernation
> using the swap space at the specified target. Please check if that UUID
> matches a swap partition.
>
> Best regards
> Nio
>
> Den 2022-09-11 kl. 20:45, skrev Fritz Hudnut:
> > Top posting:
> >
> > This is the current data from Lubuntu, and that UUID number doesn't show
> > up anywhere in "sudo blkid" from in the Lu system.  But I did write that
> > number down from some "error" reports showing in the console during the
> > last apt dist-upgrade that I ran yesterday in Lu.  Somehow perhaps apt
> > did something to  mess itself up??
> >
> > [CODE] sudo cat /etc/default/grub
> > # If you change this file, run 'update-grub' afterwards to update
> > # /boot/grub/grub.cfg.
> > # For full documentation of the options in this file, see:
> > #   info -f grub -n 'Simple configuration'
> >
> > GRUB_DEFAULT=0
> > GRUB_TIMEOUT=0
> > GRUB_DISTRIBUTOR='lubuntu1910'
> > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
> > resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0"
> > GRUB_CMDLINE_LINUX="" [/CODE]
> >
> > Do I want to edit that "quiet splash resume" data to match the /dev/sdc7
> > location of the Lubuntu "/" UUID??
> >
> > [CODE] /dev/sdc7: UUID="17bcb813-d05e-4cc3-bcdf-16d283156780"  [/CODE]
> >
> > And, then try to again run the grub bootloader to get it to find a newer
> > location of Lu that would then allow upgrading to 5.19 xx kernel???
> >
> > F
> >
> > F
> >
> > On Sat, Sep 10, 2022 at 5:05 PM Fritz Hudnut  > <mailto:este.el@gmail.com>> wrote:
> >
> > Welp . . . not getting it . . . .  I ran mainline to
> > --install-latest   and it installed 5.19.5 kernel.  It said on the
> > console, "reboot to select new kernel."  Rebooted over to TW and ran
> > "grub2-mkconfig xxx" to get it to run os-prober and make a new
> > grub . . . .  Shut down.  Cold booted to grub and selected Lu . . .
> > and still running kernel is 5.13 . . . ???
> >
> > I tried to uninstall oldest kernel but mainline said, "error: can't
> > find running kernel."  Ssked mainline to list the kernels and then
> > it showed 5.13 as "running" . . . and there are two 5.19 kernel
> > options showing as installed in the list???
> >
> > I had a similar type of problem with Pop_OS! at one point, where
> > they use the /efi/boot partition to install the kernel . . . and it
> > over-filled the directory with kernels . . . and couldn't get grub
> > to select the newer kernel . . . .  Turned out there, there was
> > hardware issues . . . it all got rather "complicated" after a lot of
> > messing around.  Here I saw somewhere in apt it was saying "trying
> > to boot from /dev/sdc9" . . . and that is a swap partition . . . .
> >
> > Couldn't find my notes on how to show uuid  in efibootmgr to see
> > what is showing up there.  Perhaps I'll use mainline to remove the
> > 5.19 kernels and see then the next time if apt dist-upgrade will
> > upgrade the kernel???
> >
> > F
> >
> >
> > On Sat, Sep 10, 2022 at 11:55 AM Nio Wiklund
> > mailto:nio.wikl...@gmail.com>> wrote:
> >
> > Hi Fritz,
> >
> > This is what I think:
> >
> > If the active grub is controlled by some other distr

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Top posting:

This is the current data from Lubuntu, and that UUID number doesn't show up
anywhere in "sudo blkid" from in the Lu system.  But I did write that
number down from some "error" reports showing in the console during the
last apt dist-upgrade that I ran yesterday in Lu.  Somehow perhaps apt did
something to  mess itself up??

[CODE] sudo cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR='lubuntu1910'
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0"
GRUB_CMDLINE_LINUX="" [/CODE]

Do I want to edit that "quiet splash resume" data to match the /dev/sdc7
location of the Lubuntu "/" UUID??

[CODE] /dev/sdc7: UUID="17bcb813-d05e-4cc3-bcdf-16d283156780"  [/CODE]

And, then try to again run the grub bootloader to get it to find a newer
location of Lu that would then allow upgrading to 5.19 xx kernel???

F

F

On Sat, Sep 10, 2022 at 5:05 PM Fritz Hudnut  wrote:

> Welp . . . not getting it . . . .  I ran mainline to --install-latest
> and it installed 5.19.5 kernel.  It said on the console, "reboot to select
> new kernel."  Rebooted over to TW and ran "grub2-mkconfig xxx" to get
> it to run os-prober and make a new grub . . . .  Shut down.  Cold booted to
> grub and selected Lu . . . and still running kernel is 5.13 . . . ???
>
> I tried to uninstall oldest kernel but mainline said, "error: can't find
> running kernel."  Ssked mainline to list the kernels and then it showed
> 5.13 as "running" . . . and there are two 5.19 kernel options showing as
> installed in the list???
>
> I had a similar type of problem with Pop_OS! at one point, where they use
> the /efi/boot partition to install the kernel . . . and it over-filled the
> directory with kernels . . . and couldn't get grub to select the newer
> kernel . . . .  Turned out there, there was hardware issues . . . it all
> got rather "complicated" after a lot of messing around.  Here I saw
> somewhere in apt it was saying "trying to boot from /dev/sdc9" . . . and
> that is a swap partition . . . .
>
> Couldn't find my notes on how to show uuid  in efibootmgr to see what is
> showing up there.  Perhaps I'll use mainline to remove the 5.19 kernels and
> see then the next time if apt dist-upgrade will upgrade the kernel???
>
> F
>
>
>>

> On Sat, Sep 10, 2022 at 11:55 AM Nio Wiklund 
>> wrote:
>>
>>> Hi Fritz,
>>>
>>> This is what I think:
>>>
>>> If the active grub is controlled by some other distro in a dual-boot or
>>> multi-boot setup,
>>>
>>> sudo update-grub
>>>
>>> of Lubuntu will not upgrade which kernel it points to. You should boot
>>> into the system that controls the active grub and run
>>>
>>> sudo update-grub
>>>
>>> or some corresponding command. Chances are that it will make Lubuntu
>>> boot into the 5.19 kernel.
>>>
>>> Best regards
>>> Nio
>>>
>>>
>>>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? kernel not upgrading during dist-upgrade in kinetic??

[Fritz Hudnut]

Welp . . . not getting it . . . .  I ran mainline to --install-latest   and
it installed 5.19.5 kernel.  It said on the console, "reboot to select new
kernel."  Rebooted over to TW and ran "grub2-mkconfig xxx" to get it to
run os-prober and make a new grub . . . .  Shut down.  Cold booted to grub
and selected Lu . . . and still running kernel is 5.13 . . . ???

I tried to uninstall oldest kernel but mainline said, "error: can't find
running kernel."  Ssked mainline to list the kernels and then it showed
5.13 as "running" . . . and there are two 5.19 kernel options showing as
installed in the list???

I had a similar type of problem with Pop_OS! at one point, where they use
the /efi/boot partition to install the kernel . . . and it over-filled the
directory with kernels . . . and couldn't get grub to select the newer
kernel . . . .  Turned out there, there was hardware issues . . . it all
got rather "complicated" after a lot of messing around.  Here I saw
somewhere in apt it was saying "trying to boot from /dev/sdc9" . . . and
that is a swap partition . . . .

Couldn't find my notes on how to show uuid  in efibootmgr to see what is
showing up there.  Perhaps I'll use mainline to remove the 5.19 kernels and
see then the next time if apt dist-upgrade will upgrade the kernel???

F

On Sat, Sep 10, 2022 at 12:45 PM Fritz Hudnut  wrote:

> Nio:
>
> Right you are . . . there is something that "grub" is missing . . . .
> **Ordinarily** I can just refresh the bootloader in TW, which is the master
> controller and that picks up the weekly kernel changes . . . .  But,
> sometimes possibly something happens that messes up something like the
> UUID's for the partitions and then I have to run a command to make the new
> grub listing . . . .
>
> I've tried to disable grub in the non-controller systems, but seems like
> in ubuntu they don't want to relinquish control over grub???  I and others
> had a bug report going on it . . . possibly this is why at times grub
> "loses track" of the kernel options . . . ???
>
> And, then combined with old guy memory of what was done to fix stuff . . .
> .  Historically I have had to "chroot" into the TW install to update grub
> due to these "conflicts" over who gets to run grub . . . .
>
> But, thanks for the reminder on it . . . .  : - 0  "What day is this???"
> [senior question that older folks used to ask when I was do acu treatment
> in hospitals]  Seize the day and update-grub!!
>
> F
>
> On Sat, Sep 10, 2022 at 11:55 AM Nio Wiklund 
> wrote:
>
>> Hi Fritz,
>>
>> This is what I think:
>>
>> If the active grub is controlled by some other distro in a dual-boot or
>> multi-boot setup,
>>
>> sudo update-grub
>>
>> of Lubuntu will not upgrade which kernel it points to. You should boot
>> into the system that controls the active grub and run
>>
>> sudo update-grub
>>
>> or some corresponding command. Chances are that it will make Lubuntu
>> boot into the 5.19 kernel.
>>
>> Best regards
>> Nio
>>
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

Nio:

Right you are . . . there is something that "grub" is missing . . . .
**Ordinarily** I can just refresh the bootloader in TW, which is the master
controller and that picks up the weekly kernel changes . . . .  But,
sometimes possibly something happens that messes up something like the
UUID's for the partitions and then I have to run a command to make the new
grub listing . . . .

I've tried to disable grub in the non-controller systems, but seems like in
ubuntu they don't want to relinquish control over grub???  I and others had
a bug report going on it . . . possibly this is why at times grub "loses
track" of the kernel options . . . ???

And, then combined with old guy memory of what was done to fix stuff . . .
.  Historically I have had to "chroot" into the TW install to update grub
due to these "conflicts" over who gets to run grub . . . .

But, thanks for the reminder on it . . . .  : - 0  "What day is this???"
[senior question that older folks used to ask when I was do acu treatment
in hospitals]  Seize the day and update-grub!!

F

On Sat, Sep 10, 2022 at 11:55 AM Nio Wiklund  wrote:

> Hi Fritz,
>
> This is what I think:
>
> If the active grub is controlled by some other distro in a dual-boot or
> multi-boot setup,
>
> sudo update-grub
>
> of Lubuntu will not upgrade which kernel it points to. You should boot
> into the system that controls the active grub and run
>
> sudo update-grub
>
> or some corresponding command. Chances are that it will make Lubuntu
> boot into the 5.19 kernel.
>
> Best regards
> Nio
>
> Den 2022-09-10 kl. 20:27, skrev Fritz Hudnut:
> > So, following up on my investigations . . . synaptic "kernels" does show
> > "5.19" as "installed" . . . but uname -r still shows that 5.13 is being
> > selected???
> >
> > I installed "mainline" some time back, but forgot how to use it . . .
> > until I found the github page tabbed in FF.  I ran a couple commands and
> > it shows:  [CODE] $ mainline --list-installed
> > mainline 1.0.16
> > Distribution: Ubuntu Kinetic Kudu (development branch)
> > Architecture: amd64
> > Running kernel: 5.13.0-16-generic
> > --
> > Found installed: 5.19.0-15.15
> > Found installed: 5.19.0.15.15
> > Found installed: 5.13.0-16.16
> > --
> > --
> > [/CODE]
> >
> > I forget how to get it to switch the kernel . . . 5.19 is "installed"
> > but grub is still selecting 5.13 . . . do I run "mainline
> > --install-latest" to "reinstall" . . . or is this a grub error of some
> > type???
> >
> > I went into grub's "advanced options" and it's only showing three
> > options for 5.13 . . . I selected recovery and ran fsck which did
> > nothing, and then dpkg . . . which also found nothing . . . .  In the
> > sense that the system is not finding anything "broken" . . . but it
> > isn't sliding up to select 5.19 options . . . .
> >
> > F
> >
> > On Sat, Sep 10, 2022 at 8:35 AM Fritz Hudnut  > <mailto:este.el@gmail.com>> wrote:
> >
> > I jumped the queue and booted Lu this morning . . . it was still
> > showing 5.13 as the kernel . . . ran a 93 package upgrade . . . no
> > mention of a kernel in the list . . . went through w/o error . . . .
> >
> > Booted over into master grub control system . . . updated the grub
> > bootloader . . . then back into Lu . . . ran another apt . . .
> > couple packages to upgrade . . . nothing on the kernel.
> >
> > Uname -r still showing "5.13.0-16" . . .   I guess the question
> > is, if Sid is running 5.10 why would kinetic be running 5.19???
> >
> > And, then, other interesting question, why did apt show something
> > like 5.15 the last time I was in Lu . . . but then "hang" and lose
> > track of it???
> >
> > These are somewhat "moot" . . . in that Lu boots and runs OK . . .
> > but, something "happened" last week . . .
> >
> > F
> >
> > On Tue, Sep 6, 2022 at 12:51 PM Fritz Hudnut  > <mailto:este.el@gmail.com>> wrote:
> >
> > Nio:
> >
> > I guess there was a post on the list that I didn't get, as I'm
> > on digest . . . .  But, thanks guys for checking on the "5.19" .
> > . . I'm doing &q

Re: [lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

So, following up on my investigations . . . synaptic "kernels" does show
"5.19" as "installed" . . . but uname -r still shows that 5.13 is being
selected???

I installed "mainline" some time back, but forgot how to use it . . . until
I found the github page tabbed in FF.  I ran a couple commands and it
shows:  [CODE] $ mainline --list-installed
mainline 1.0.16
Distribution: Ubuntu Kinetic Kudu (development branch)
Architecture: amd64
Running kernel: 5.13.0-16-generic
--
Found installed: 5.19.0-15.15
Found installed: 5.19.0.15.15
Found installed: 5.13.0-16.16
--
--
[/CODE]

I forget how to get it to switch the kernel . . . 5.19 is "installed" but
grub is still selecting 5.13 . . . do I run "mainline --install-latest" to
"reinstall" . . . or is this a grub error of some type???

I went into grub's "advanced options" and it's only showing three options
for 5.13 . . . I selected recovery and ran fsck which did nothing, and then
dpkg . . . which also found nothing . . . .  In the sense that the system
is not finding anything "broken" . . . but it isn't sliding up to select
5.19 options . . . .

F

On Sat, Sep 10, 2022 at 8:35 AM Fritz Hudnut  wrote:

> I jumped the queue and booted Lu this morning . . . it was still showing
> 5.13 as the kernel . . . ran a 93 package upgrade . . . no mention of a
> kernel in the list . . . went through w/o error . . . .
>
> Booted over into master grub control system . . . updated the grub
> bootloader . . . then back into Lu . . . ran another apt . . . couple
> packages to upgrade . . . nothing on the kernel.
>
> Uname -r still showing "5.13.0-16" . . .   I guess the question is, if
> Sid is running 5.10 why would kinetic be running 5.19???
>
> And, then, other interesting question, why did apt show something like
> 5.15 the last time I was in Lu . . . but then "hang" and lose track of it???
>
> These are somewhat "moot" . . . in that Lu boots and runs OK . . . but,
> something "happened" last week . . .
>
> F
>
> On Tue, Sep 6, 2022 at 12:51 PM Fritz Hudnut 
> wrote:
>
>> Nio:
>>
>> I guess there was a post on the list that I didn't get, as I'm on digest
>> . . . .  But, thanks guys for checking on the "5.19" . . . I'm doing
>> "weekly" apt update/upgrade and pretty sure I saw it was attempting to
>> install 5.15??? (something less than 5.19)  and then now seems to have
>> selected 5.13 . . . ???
>>
>> I ran the master grub bootloader this morning, which should select the
>> newest kernel in Lu . . . next time I boot into it . . . .  And I did run
>> "apt -f install" and that brought back "nothing to do" . . . it didn't show
>> anything "broken" and so forth.
>>
>> I will also check synaptic to see if it shows anything broken . . .
>> sometimes it can actually "fix broken"  and sometimes it "blinks its eyes"
>> and nothing happens . . . .  I was looking through my cheat sheet notes for
>> how to fix problems, but I didn't see anything on "dpkg" and/or how to use
>> it to find and fix any issues . . . ???
>>
>> Anyway . . . I'll get back to it in a bit and see if grub found the 5.19
>> kernel option to boot up . . . .
>>
>>
>> On Tue, Sep 6, 2022 at 12:05 PM Nio Wiklund 
>> wrote:
>>
>>> Den 2022-09-06 kl. 20:57, skrev Israel Dahl:
>>> > On 9/6/22 09:31, Fritz Hudnut wrote:
>>> >> > . . . .  On cold boot FF came back.
>>> >>
>>> >> >
>>> >> > But, the question of what happened with apt was the more
>>> important
>>> >> > question . . . was it trying to install a too new kernel and
>>> then
>>> >> > tried to back out of it?  It was an odd episode . . . .
>>> >> >
>>> >> > F
>>> >> >
>>> >> Hey Fritz,
>>> >>
>>> >> You could search for the available kernels to see which ones are
>>> >> available, and which ones are installed.
>>> >>
>>> >> You can also look in the /var/log/dpkg.log something like:
>>> >>
>>> >> grep "upgrade " /var/log/dpkg.log
>>> >>
>>> >> That might give you a starting point.
>>> >>
>>> >>  

Re: [lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

I jumped the queue and booted Lu this morning . . . it was still showing
5.13 as the kernel . . . ran a 93 package upgrade . . . no mention of a
kernel in the list . . . went through w/o error . . . .

Booted over into master grub control system . . . updated the grub
bootloader . . . then back into Lu . . . ran another apt . . . couple
packages to upgrade . . . nothing on the kernel.

Uname -r still showing "5.13.0-16" . . .   I guess the question is, if
Sid is running 5.10 why would kinetic be running 5.19???

And, then, other interesting question, why did apt show something like 5.15
the last time I was in Lu . . . but then "hang" and lose track of it???

These are somewhat "moot" . . . in that Lu boots and runs OK . . . but,
something "happened" last week . . .????

F

On Tue, Sep 6, 2022 at 12:51 PM Fritz Hudnut  wrote:

> Nio:
>
> I guess there was a post on the list that I didn't get, as I'm on digest .
> . . .  But, thanks guys for checking on the "5.19" . . . I'm doing "weekly"
> apt update/upgrade and pretty sure I saw it was attempting to install
> 5.15??? (something less than 5.19)  and then now seems to have selected
> 5.13 . . . ???
>
> I ran the master grub bootloader this morning, which should select the
> newest kernel in Lu . . . next time I boot into it . . . .  And I did run
> "apt -f install" and that brought back "nothing to do" . . . it didn't show
> anything "broken" and so forth.
>
> I will also check synaptic to see if it shows anything broken . . .
> sometimes it can actually "fix broken"  and sometimes it "blinks its eyes"
> and nothing happens . . . .  I was looking through my cheat sheet notes for
> how to fix problems, but I didn't see anything on "dpkg" and/or how to use
> it to find and fix any issues . . . ???
>
> Anyway . . . I'll get back to it in a bit and see if grub found the 5.19
> kernel option to boot up . . . .
>
>
> On Tue, Sep 6, 2022 at 12:05 PM Nio Wiklund  wrote:
>
>> Den 2022-09-06 kl. 20:57, skrev Israel Dahl:
>> > On 9/6/22 09:31, Fritz Hudnut wrote:
>> >> > . . . .  On cold boot FF came back.
>> >>
>> >> >
>> >> > But, the question of what happened with apt was the more
>> important
>> >> > question . . . was it trying to install a too new kernel and then
>> >> > tried to back out of it?  It was an odd episode . . . .
>> >> >
>> >> > F
>> >> >
>> >> Hey Fritz,
>> >>
>> >> You could search for the available kernels to see which ones are
>> >> available, and which ones are installed.
>> >>
>> >> You can also look in the /var/log/dpkg.log something like:
>> >>
>> >> grep "upgrade " /var/log/dpkg.log
>> >>
>> >> That might give you a starting point.
>> >>
>> >> As for the disappearance of firefox, I think snap/flatpak packages
>> >> don't
>> >> always show up after install, there may be a way to force it to
>> >> update
>> >> the menus but I don't really like to use either of those unless I
>> >> *really* have to, so I don't know off the top of my head/
>> >>
>> >> --
>> >> 
>> >>
>> >>
>> >>
>> >> Israel:
>> >>
>> >> Thanks for the suggestions . . . I'll check into them when I get back
>> >> to Lu in a few days.  One of my problems is that since I'm rotating
>> >> OSs each day, I don't know where each system is vis the kernel.
>> >> Possibly kinetic is a "5.13" base system, but I did see "5.15" in the
>> >> upgrade list. Yesterday I was in Tumbleweed, which is 5.19 . . . and
>> >> then today I'm in Deb Sid, which I thought would be like 5.20??? but,
>> >> nope, uname -r shows "5.10" . . . .
>> >>
>> >> The good news is that whatever blew up in the middle or end of the
>> >> apt, the kinetic system rebooted into the GUI . . . .  It was just a
>> >> rare instance of a "hang" in the apt dist-upgrade.
>> >>
>> >> F
>> >>
>> > It looks like Kinetic has a 5.19 now, so you should try to update again.
>> >
>> > You should check to see that everything was unpacked in that last
>> > upgrade as well.  You might need to use dpkg to fix things if not.
>> >
>> > --
>> > 
>>
>> Hi Fritz and Israel,
>>
>> I can confirm that Kinetic is a 5.19 now. Today I installed Lubuntu via
>>
>> kinetic-preinstalled-server-amd64.img.xz
>>
>> and lubuntu-desktop, installed into it when running in an external SSD
>> according to
>>
>> "Ubuntu Server amd64 compressed image (when extracted) boots in UEFI and
>> BIOS mode",
>>
>> https://ubuntuforums.org/showthread.php?t=2474692
>>
>> Best regards
>> Nio
>>
>>
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

Nio:

I guess there was a post on the list that I didn't get, as I'm on digest .
. . .  But, thanks guys for checking on the "5.19" . . . I'm doing "weekly"
apt update/upgrade and pretty sure I saw it was attempting to install
5.15??? (something less than 5.19)  and then now seems to have selected
5.13 . . . ???

I ran the master grub bootloader this morning, which should select the
newest kernel in Lu . . . next time I boot into it . . . .  And I did run
"apt -f install" and that brought back "nothing to do" . . . it didn't show
anything "broken" and so forth.

I will also check synaptic to see if it shows anything broken . . .
sometimes it can actually "fix broken"  and sometimes it "blinks its eyes"
and nothing happens . . . .  I was looking through my cheat sheet notes for
how to fix problems, but I didn't see anything on "dpkg" and/or how to use
it to find and fix any issues . . . ???

Anyway . . . I'll get back to it in a bit and see if grub found the 5.19
kernel option to boot up . . . .


On Tue, Sep 6, 2022 at 12:05 PM Nio Wiklund  wrote:

> Den 2022-09-06 kl. 20:57, skrev Israel Dahl:
> > On 9/6/22 09:31, Fritz Hudnut wrote:
> >> > . . . .  On cold boot FF came back.
> >>
> >> >
> >> > But, the question of what happened with apt was the more important
> >> > question . . . was it trying to install a too new kernel and then
> >> > tried to back out of it?  It was an odd episode . . . .
> >> >
> >> > F
> >> >
> >> Hey Fritz,
> >>
> >> You could search for the available kernels to see which ones are
> >> available, and which ones are installed.
> >>
> >> You can also look in the /var/log/dpkg.log something like:
> >>
> >> grep "upgrade " /var/log/dpkg.log
> >>
> >> That might give you a starting point.
> >>
> >> As for the disappearance of firefox, I think snap/flatpak packages
> >> don't
> >> always show up after install, there may be a way to force it to
> >> update
> >> the menus but I don't really like to use either of those unless I
> >> *really* have to, so I don't know off the top of my head/
> >>
> >> --
> >> 
> >>
> >>
> >>
> >> Israel:
> >>
> >> Thanks for the suggestions . . . I'll check into them when I get back
> >> to Lu in a few days.  One of my problems is that since I'm rotating
> >> OSs each day, I don't know where each system is vis the kernel.
> >> Possibly kinetic is a "5.13" base system, but I did see "5.15" in the
> >> upgrade list. Yesterday I was in Tumbleweed, which is 5.19 . . . and
> >> then today I'm in Deb Sid, which I thought would be like 5.20??? but,
> >> nope, uname -r shows "5.10" . . . .
> >>
> >> The good news is that whatever blew up in the middle or end of the
> >> apt, the kinetic system rebooted into the GUI . . . .  It was just a
> >> rare instance of a "hang" in the apt dist-upgrade.
> >>
> >> F
> >>
> > It looks like Kinetic has a 5.19 now, so you should try to update again.
> >
> > You should check to see that everything was unpacked in that last
> > upgrade as well.  You might need to use dpkg to fix things if not.
> >
> > --
> > 
>
> Hi Fritz and Israel,
>
> I can confirm that Kinetic is a 5.19 now. Today I installed Lubuntu via
>
> kinetic-preinstalled-server-amd64.img.xz
>
> and lubuntu-desktop, installed into it when running in an external SSD
> according to
>
> "Ubuntu Server amd64 compressed image (when extracted) boots in UEFI and
> BIOS mode",
>
> https://ubuntuforums.org/showthread.php?t=2474692
>
> Best regards
> Nio
>
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

> . . . .  On cold boot FF came back.

> >
> > But, the question of what happened with apt was the more important
> > question . . . was it trying to install a too new kernel and then
> > tried to back out of it?  It was an odd episode . . . .
> >
> > F
> >
> Hey Fritz,
>
> You could search for the available kernels to see which ones are
> available, and which ones are installed.
>
> You can also look in the /var/log/dpkg.log something like:
>
> grep "upgrade " /var/log/dpkg.log
>
> That might give you a starting point.
>
> As for the disappearance of firefox, I think snap/flatpak packages don't
> always show up after install, there may be a way to force it to update
> the menus but I don't really like to use either of those unless I
> *really* have to, so I don't know off the top of my head/
>
> --
> 
>
>
>
Israel:

Thanks for the suggestions . . . I'll check into them when I get back to Lu
in a few days.  One of my problems is that since I'm rotating OSs each day,
I don't know where each system is vis the kernel.  Possibly kinetic is a
"5.13" base system, but I did see "5.15" in the upgrade list.  Yesterday I
was in Tumbleweed, which is 5.19 . . . and then today I'm in Deb Sid, which
I thought would be like 5.20???  but, nope, uname -r shows "5.10" . . . .

The good news is that whatever blew up in the middle or end of the apt, the
kinetic system rebooted into the GUI . . . .  It was just a rare instance
of a "hang" in the apt dist-upgrade.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

On Sun, 2022-09-04 at 10:38 -0700, Fritz Hudnut wrote:
> > [snip] running kinetic this morning and executed "apt update && apt
> > dist-upgrade" [snip]
> > FireFox disappeared from the internet menu [snip]
>
> Hi,
>
> Firefox is not provided by the apt repositories.
>
> It's a "Transitional package - firefox -> firefox snap", see
> https://packages.ubuntu.com/kinetic/firefox , IOW the snap related
> upgrade process is providing Firefox.
>
> The "bin" provided by this package actually is a script, at least the
> jammy package's Firefox script starts with:
>
> "#!/bin/sh
> if ! [ -x /snap/bin/firefox ]; then
> echo "" >&2
> echo "Command '$0' requires the firefox snap to be installed." >&2
> echo "Please install it with:" >&2
> echo "" >&2
> echo "snap install firefox" >&2
> echo "" >&2
> exit 1
> fi"
>
> IMO the snap enforcement is the beginning of the end of Ubuntu flavours.
> Fortunately my everyday Linux is the rolling release Arch Linux. Ubuntu
> flavours were my long term support emergency Linux installs, but now I
> try to find a long term support replacement for Ubuntu flavours.
>
> Snaps are an Ubuntu only thingy. Other distros provide the snap
> infrastructure, but they are not supporting it. I also dislike
> alternatives, such as flatpak, but those at least enjoy a minimum of
> acceptance, while there's absolutely no acceptance for snaps outside of
> Ubuntu flavours.
>
> Regards,
> Ralf
>
>
>
Ralf:

Alrighty, thanks for the reply . . . the "disappearing Firefox" thing only
was a problem as far as wanting a browser to search for answers to the
problem of apt "hanging" in the process of updating the system . . . .  On
cold boot FF came back.

But, the question of what happened with apt was the more important question
. . . was it trying to install a too new kernel and then tried to back out
of it?  It was an odd episode . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??

[Fritz Hudnut]

Folks:

Once again in Lu can't access Discourse, so posting here . . . running
kinetic this morning and executed "apt update && apt dist-upgrade" . . .
showed a few hundred packages to install . . . midway through on #52???
there was a "hang" on what might have been "initrd - 5.15x"  and there
was an "error" showing in the update applet . . . something about "package
number count"???  Concurrently FireFox disappeared from the internet menu .
. . .

I couldn't "ctrl-c" out of the hang in the console . . . couldn't launch
synaptic because "apt" was locking access . . . didn't know the precise
command to "force quit apt" . . . I also tried "apt -f install" but that
wouldn't override apt's lock on the system.  Finally just shut down out of
it.

On cold boot in spite of hanging "halfway" . . . now it showed only one
package left to upgrade . . . a language package??  But it showed "5.15
xxx" to be removed in "autoremove"??  so it was previously trying to
install it and then changed its mind??

uname -r right now shows 5.13.0-16-generic . . . I didn't update grub via
the master grub controller in another OS . . . to see if that would get the
kernel closer to 6.15???  Running a multi-boot grub situation . . . .  But
there hasn't been this kind of "hang" in running apt in Lu in quite some
time . . . ?  something got sideways in the dist-upgrade in kinetic . .
. .
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] "Update pending for Firefox snap"???

[Fritz Hudnut]

Folks:

Booted up in Lubuntu kinetic today and I once again get an error message
about "update for Firefox snap, close app in the next 13 days"

I have "closed the app" numerous times over the last month or so and still
getting this error message . . . what's up with that message??

I run weekly apt updates on the system, with autoremove, etc . . . system
isn't clearing this error.
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Testing Jammy on old hardware???

[Fritz Hudnut]

Bottom posting . . .

I think it's all the little ads, permeating almost every web-page you visit
nowadays, that saps away the power of our machines. Slower

> machines are more affected.
>
>
>
>
> Last time I experienced almost-no-ADs was in socialism in Yugoslavia.
> I doubt Lubuntu (even 26.04 LTS) could get me that ;-P
> but advocating for sustainability by Lubuntu would be useful.
>
>
> > Of course, if you don't browse the Internet on them, older,
> > less-powerful machines, work well.
> >
>
> I am not convinced this is only the issue of web pages,
> but would love to have more clarity as I can not test myself.
>
> Other than that - I do appreciate your individual efforts.
>
> Thank you!
>


So, what are you saying, "you can not test yourself" . . . ???  Can you not
download an iso and use mkusb to burn it to a flash drive and boot it up
and test it to see how the machine handles the OS??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu-users Digest, Vol 115, Issue 2

[Fritz Hudnut]

> >
> Thank you for your hard work on this release.
>
> I've been testing it, and got some pleasant surprises.
>
> The color-customization I so enjoyed on LXDE, now works on LXQT too.
> And it now supports the SD-card reader in my Mac Mini.
>
> It appears to upgrade reliably from Lubuntu 20.04, and it successfully
> runs all my music tests.  I am quite happy with this release, so far.
>
> --
> Sincerely,
> Aere
>

@Aere:

Nice to also see yr name again on the list after these several very
difficult years . . . glad to see you are still testing the systems, etc.

F

>
>
>
>
>
> --
>
> Subject: Digest Footer
>
> --
> Lubuntu-users mailing list
> Lubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
>
>
> --
>
> End of Lubuntu-users Digest, Vol 115, Issue 2
> *
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu-users Digest, Vol 115, Issue 1

[Fritz Hudnut]

> >
> Hi,
>
> I gotta say I tried it out a few days ago and it looks great!
> Congratulations on the style and all the hard work you put into it!
>
> --
> 
>
>
>
>
> @Israel:
>

Haven't seen yr name on this list for quite awhile, since . . . ??  the
days of PPC linux???  : - ))

F

>
> End of Lubuntu-users Digest, Vol 115, Issue 1
> *
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] problem accessing the forum in lubuntu.me

[Fritz Hudnut]

@et al:

I've had this problem, mainly when trying to access the forum by way of the
digests, and just the other day I checked it again and the problem was
still happening.  I supplied material to one of the folks with a ubuntu
address . . . and then I believe I followed up on it . . . to wit . . .
nada . . . .

Problem remains.  Possibly I can directly access the web site, but linking
through the digests doesn't work . . . .  I checked after I moved up to
Impish.

F



> Message: 2
> Date: Tue, 18 May 2021 10:20:03 +1000
> From: Chris Guiver 
> To: Juan Manuel Carrillo Campos 
> Cc: lubuntu-users@lists.ubuntu.com
> Subject: Re: [lubuntu-users] problem accessing the forum in lubuntu.me
> Message-ID:
>  bn-4ardoeyk8q1x...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> I would try again.
>
> I just tested both links you provided, and they worked for me.   Your
> issue may be local network related (on a campus or corporate network
> which restricts traffic to specific domains etc) and not site related,
> or you were just unlucky.
>
> Chris
>
> On 5/18/21, Juan Manuel Carrillo Campos  wrote:
> > Hello,
> > I may access the main page of lubuntu.me
> > There I may access the links but no https://discourse.lubuntu.me/
> > (the forums link) Because there I just see a blank page without
> > anything on it.
> > My distro is *DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"* and is "up to
> > date" with all the "upgrades" proposed:
> > Linux Pinky 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC
> > 2020 x86_64 x86_64 x86_64 GNU/Linux
> > (and I have a screen resolution of 1366x768).
> > Please help me to fix this issue or let me know an alternative to rich
> > the forums.
> > Thanks in advance for your support.
> > Best regards.
> > Juan Manuel
> >
> >
> >
> > --
> > Lubuntu-users mailing list
> > Lubuntu-users@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
> >
>
>
>
> --
>
> Subject: Digest Footer
>
> --
> Lubuntu-users mailing list
> Lubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
>
>
> --
>
> End of Lubuntu-users Digest, Vol 111, Issue 2
> *
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Blank page for forum

[Fritz Hudnut]

JM:

Yes, I can confirm this issue.  My edition of it is through the email
digests from the forum, clicking on the links goes to blankness.  But,
yesterday via search engine I logged in via Github and was able to post on
the forum . . . to little fanfare.

I was in Gecko yesterday, also using Firefox, and today I'm in Leap 15.3
and search engine took me to the site . . . in full color.

There is a gentleman from ubuntu who was supposed to be in charge of fixing
this issue, seems like maybe that hasn't happened yet.  This link below was
working for me minutes ago.

https://discourse.lubuntu.me/

 F

> From: Juan Manuel Carrillo Campos 
> To: lubuntu-users@lists.ubuntu.com
> Subject: [lubuntu-users] Problem to access the FORUM page
> Message-ID: <14eb48eab66b555d5a6dee77e8d19cb09c172f7e.ca...@gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hello,
> When I try to access the FORUM page of Lubuntu (
> https://discourse.lubuntu.me/), all that I get is a blank page, all the
> other links/pages open without any problem.
> (I have Lubuntu 20.04, my browser is Firefox 87.0 (64 bits))
> How may i debug and fix this issue?
> Thanks in advance for your kind answer.
> Best regards.
> Juan Manuel
>
>
>
>
>
> -
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Apart from this I'm using syslinux instead of grub2.

[Fritz Hudnut]

>
>
> From: Ralf Mardorf 
> To: lubuntu user list 
> Subject: Re: [lubuntu-users] Apart from this I'm using syslinux
> instead of  grub2.
> Message-ID: <20200730022816.0dfa7ea2@archlinux>
> Content-Type: text/plain; charset=US-ASCII
>
> On Wed, 29 Jul 2020 16:03:51 -0700, Fritz Hudnut wrote:
> >On Wed, Jul 29, 2020 at 3:51 PM Ralf Mardorf 
> >wrote:
> >
> >> On Wed, 29 Jul 2020 15:34:54 -0700, Fritz Hudnut wrote:
> >> >got a good laugh out of the "Hal 9000" line . . . classic geek humor
> >> >there
> >>
> >> Using a computer without a sense of dark humour is really dangerous!
> >>
> >
> >Indeed it is . . . and the reference to Hal 9000 is "the stuff of the
> >dark web" . . . i.e., extra dark stuff . . . .  : - 
>
> The relativity of real-time.
>
> The shooter sees the target by speed of light.
>
> The target hears the shot by speed of sound, if the shooter (even by a
> ricochet) did miss the target.
>
> Even if the projectile should be slower than the speed of
> sound, the speed of the awareness of the sound, is way slower than the
> projectile.
>
> If the shooter didn't miss the target, then the target did not hear the
> shot.
>
> Many people believe in noticing computers becoming dangerous,
> before computers could harm. This guess is as infantil.
>
> Hiding behind a car door, as shelter against a projectile, gains
> nothing. At best it blocks the view, but not the bullet.
>
> We also could hide behind car doors trying to ensure privacy and
> security of data.
>
>
>

>
> A starting point: https://wiki.archlinux.org/index.php/Syslinux
>
>
>  @Ralf:

Thanks for that link to the wiki . . . .  On the previous allegorical data
. . . well stated, it looks like something I myself could have written . .
. to the usual "?" response.

A couple weeks back I did a short keynote presentation to a group of mental
health acupuncturists on the topic of "Connecting with Our Nature in nature
for higher understanding" . . . I thought it was pretty "clear" what I was
saying . . . .  But after the talk the facilitator said, "Thanks for the
presentation, of course for the most part not many people will understand
what you were saying . . . but, thanks for saying it."

So, Ralf, thanks for saying it . . . I still think "Hal 9000" is an apt
metaphor for today's society . . . but mostly "self-inflicted" or "pilot
error" on the part of the "carbon units" who don't understand their great
blessings . . . and they let the synth units "run the show" . . . .  We
"didn't hear the shot" . . . etc. etc.  : - 

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.

[Fritz Hudnut]

Ralf:

I just did a quick search on the googly and it seems like syslinux is for
"MS/DOS" or "BIOS" and/or possibly "FAT32" systems??  It didn't seem to
mention Macs, although it did show something on "UEFI" . . . but then one
item was saying, "It won't boot ext2 systems"???  So it seems like syslinux
is also "going back" in the history of linux in the time before apple was
considered "adequate" . . . .

But, I think sometime in the next year or so I will be trying to find a PC
laptop, or a  "built for linux" laptop . . . and that would likely have the
"BIOS" and "MBR" items that might be friendlier to syslinux

Seems like what I might have seen in OpenSUSE was some "syslinux" package
or app, which might not be the same as the "syslinux bootloader" that is
BIOS friendly and only boots "MS/DOS" and/or Fat32 formatted systems???

I know that in Mac the EFI boot partition is formatted as FAT32 . . . so
question is . . . is that meeting the requirements for booting via
syslinux, or nope it don't do Macintoshes . . . ???

On Wed, Jul 29, 2020 at 3:40 PM Ralf Mardorf 
wrote:

> PPS:
>
> For my Xenial install I'm using links, I have to manually update, so
> that I don't need to fix my syslinux.cfg:
>
> [rocketmouse@archlinux ~]$ /usr/bin/ls -hl /.boot/ubuntu_moonstudio/boot/
> total 114M
> -rw--- 1 root root 3.8M Jul  1 09:30 System.map-4.4.0-186-lowlatency
> -rw-r--r-- 1 root root 3.2M Nov 15  2019
> System.map-5.3.0-11.2-liquorix-amd64
> -rw-r--r-- 1 root root 187K Jul  1 09:30 config-4.4.0-186-lowlatency
> -rw-r--r-- 1 root root 213K Nov 15  2019 config-5.3.0-11.2-liquorix-amd64
> drwxr-xr-x 2 root root 4.0K May  7 06:09 grub
> -rw-r--r-- 1 root root  37M Jul 21 04:50 initrd.img-4.4.0-186-lowlatency
> -rw-r--r-- 1 root root  54M Jun 13 18:23
> initrd.img-5.3.0-11.2-liquorix-amd64
> lrwxrwxrwx 1 root root   36 Nov 26  2019 initrd.img-liquorix ->
> initrd.img-5.3.0-11.2-liquorix-amd64
> lrwxrwxrwx 1 root root   31 Jul 21 04:58 initrd.img-lowlatency ->
> initrd.img-4.4.0-186-lowlatency
> -rw-r--r-- 1 root root 179K Jan 28  2016 memtest86+.bin
> -rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+.elf
> -rw-r--r-- 1 root root 181K Jan 28  2016 memtest86+_multiboot.bin
> -rw-r--r-- 1 root root0 Aug  6  2018 s3.archlinux
> -rw--- 1 root root 7.0M Jul  6 11:18 vmlinuz-4.4.0-186-lowlatency
> -rw-r--r-- 1 root root 9.0M Nov 15  2019 vmlinuz-5.3.0-11.2-liquorix-amd64
> lrwxrwxrwx 1 root root   33 Nov 26  2019 vmlinuz-liquorix ->
> vmlinuz-5.3.0-11.2-liquorix-amd64
> lrwxrwxrwx 1 root root   28 Jul 21 04:58 vmlinuz-lowlatency ->
> vmlinuz-4.4.0-186-lowlatency
>
> --
> /usr/bin/ls since 'ls' is an alias on my install:
> [rocketmouse@archlinux ~]$ alias ls
> alias ls='lsd'
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.

[Fritz Hudnut]

On Wed, Jul 29, 2020 at 3:51 PM Ralf Mardorf  wrote:

> On Wed, 29 Jul 2020 15:34:54 -0700, Fritz Hudnut wrote:
> >got a good laugh out of the "Hal 9000" line . . . classic geek humor
> >there
>
> Using a computer without a sense of dark humour is really dangerous!
>

Indeed it is . . . and the reference to Hal 9000 is "the stuff of the dark
web" . . . i.e., extra dark stuff . . . .  : - 
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.

[Fritz Hudnut]

Ralf:

Thanks for sharing that data . . . it looks like "French" right now to this
redneck hippie 'merican . . . so I'll have to study it for awhile . . . .
But, got a good laugh out of the "Hal 9000" line . . . classic geek humor
there . . . .  Somewhere recently I used the "Dave . . . stop . . . stop .
. . Dave . . . please stop . . . stop." line, but it didn't seem to be
"recognized" for the high value humor that it should have provided . . . .
: - 0

F

On Wed, Jul 29, 2020 at 3:25 PM Ralf Mardorf 
wrote:

> PS:
>
> I've got experiences with chainloading FreeBSD and Windows when using
> grub legacy and grub2, but not with syslinux.
>
> My syslinux multi-boot PC is a Linux only multi-boot _and_ I never
> used, neither with grub, nor with syslinux, anything secure boot/(U)EFI
> related.
>
> That's my current syslinux.cfg:
>
> [rocketmouse@archlinux ~]$ cat /boot/syslinux/syslinux.cfg
> # Syslinux
> #   http://syslinux.zytor.com/wiki/index.php/Doc/menu
> #
> # Mitigations linux >= 5.1.13
> #
> https://linuxreviews.org/HOWTO_make_Linux_run_blazing_fast_(again)_on_Intel_CPUs
> #   mitigations=off
> #
> # Misc
> #   grep . /sys/devices/system/cpu/vulnerabilities/* | cut -d/ -f7
> #   audit=off
>
> PROMPT 0
> TIMEOUT 600
> UI menu.c32
> MENU HIDDEN
> MENU CLEAR
> MENU COLOR screen  0;30;40
> MENU COLOR border  0;30;40
> MENU COLOR title   1;37;44
> MENU COLOR unsel   0;37;40
> MENU COLOR hotkey  1;37;40
> MENU COLOR hotsel  7;37;40
> MENU COLOR sel 7;37;40
> MENU COLOR disabled1;37;40
> MENU COLOR scrollbar   0;30;40
> MENU COLOR tabmsg  0;30;40
> MENU COLOR cmdmark 0;31;40
> MENU COLOR cmdline 0;37;40
> MENU COLOR timeout_msg 0;37;40
> MENU COLOR timeout 1;37;40
>
> # Used hotkeys: ^8 ^A ^C ^e ^f ^g ^H ^i (^l) ^M ^n ^o ^P ^Q ^R ^S ^t ^V
> (^X) ^y
> KBDMAP  de.ktl
> DEFAULT Securityink
>
> MENU TITLE HAL 9000-s3
> LABEL Toolbox
> MENU LABEL Toolbox
> MENU DISABLE
> MENU SEPARATOR
>
>
> LABEL Hardware
> MENU LABEL ^Hardware Detection
> COM32 hdt.c32
>
> LABEL Memtest
> MENU LABEL Memtest^86+
> LINUX /.boot/ubuntu_moonstudio/boot/memtest86+.bin
>
> LABEL Reset
> MENU LABEL R^eset
> COM32 reboot.c32
>
>
> MENU SEPARATOR
> MENU SEPARATOR
> LABEL Arch Menu
> MENU LABEL Arch Linux
> MENU DISABLE
> MENU SEPARATOR
>
>
> LABEL Threadirqs
> MENU LABEL Arch Linux ^threadirqs
> LINUX ../vmlinuz-linux
> APPEND root=LABEL=s3.archlinux ro threadirqs
> INITRD ../intel-ucode.img,../initramfs-linux.img
>
> LABEL Threadirqs_no_mitigations
> MENU LABEL Arch Linux threadirqs  ^no mitigations
> LINUX ../vmlinuz-linux
> APPEND root=LABEL=s3.archlinux ro threadirqs mitigations=off audit=off
> INITRD ../intel-ucode.img,../initramfs-linux.img
>
> LABEL Securityink
> MENU LABEL Arch Linux Rt ^Securityink
> LINUX ../vmlinuz-linux-rt-securityink
> APPEND root=LABEL=s3.archlinux ro
> INITRD ../intel-ucode.img,../initramfs-linux-rt-securityink.img
>
> LABEL Securityink_no_mitigations
> MENU LABEL Arch Linux Rt Securityink  no m^itigations
> LINUX ../vmlinuz-linux-rt-securityink
> APPEND root=LABEL=s3.archlinux ro noibrs noibpb nopti nospectre_v2
> nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off
> mitigations=off
> INITRD ../intel-ucode.img,../initramfs-linux-rt-securityink.img
>
> LABEL Pussytoes
> MENU LABEL Arch Linux Rt ^Pussytoes
> LINUX ../vmlinuz-linux-rt-pussytoes
> APPEND root=LABEL=s3.archlinux ro
> INITRD ../intel-ucode.img,../initramfs-linux-rt-pussytoes.img
>
> LABEL Pussytoes_no_mitigations
> MENU LABEL Arch Linux Rt Puss^ytoesno mitigations
> LINUX ../vmlinuz-linux-rt-pussytoes
> #APPEND root=LABEL=s3.archlinux ro mitigations=off
> APPEND root=LABEL=s3.archlinux ro noibrs noibpb nopti nospectre_v2
> nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off
> mitigations=off
> INITRD ../intel-ucode.img,../initramfs-linux-rt-pussytoes.img
>
> LABEL Cornflower
> MENU LABEL Arch Linux Rt ^Cornflower
> LINUX ../vmlinuz-linux-rt-cornflower
> APPEND root=LABEL=s3.archlinux ro
> INITRD ../intel-ucode.img,../initramfs-linux-rt-cornflower.img
>
> LABEL Cornflower_no_mitigations
> MENU LABEL Arch Linux Rt Corn^flower   no mitigations
> LINUX ../vmlinuz-linux-rt-cornflower
> #APPEND root=LABEL=s3.archlinux ro mitigations=off audit=off
> APPEND root=LABEL=s3.archlinux ro mitigations=off
> INITRD ../intel-ucode.img,../initramfs-linux-rt-cornflower.img
>
> LABEL Rt
> MENU LABEL Arch Linux ^Rt
> LINUX ../vmlinuz-linux-rt
> APPEND root=LABEL=s3.archlinux ro
> INITRD ../intel-ucode.img,../initramfs-linux-rt.img
>
> LABEL Rt_no_mitigations
> MENU LABEL Arch Linux Rt  n^o mitigations
> LINUX ../vmlinuz-linux-rt
> APPEND root=LABEL=s3.archlinux ro mitigations=off
> INITRD ../intel-ucode.img,../initramfs-linux-rt.img
>
> LABEL 

Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.

[Fritz Hudnut]

On Wed, Jul 29, 2020 at 3:03 PM Ralf Mardorf 
wrote:

> Hi Fritz,
>
> it comes with a learning curve ;).
>
> On Wed, 29 Jul 2020 14:20:18 -0700, Fritz Hudnut wrote:
> >Any pointers on why you choose syslinux over grub2??
>
> For me the pros of syslinux are
>
> - I do not need to disable insane automation, as I had to do (depending
>   on the distro providing it) for grub2
> - I do not need to tidy up a default config, to get rid of clutter
>
> For me the con of syslinux is
>
> - I'm either forced to use chainloading or as I do, to use one
>   partition for the kernels of all installs and (not necessarily) to
>   bind mount [1]
>
> In my case 2 pros vs one con.
>
> Actually there are a lot of more pros and cons for both, syslinux as
> well as grub2, depending on the users needs. For me just the mentioned
> matter.
>
> On 'apt' based distros, such as the Ubuntu flavour Lubuntu, you can
> 'dpkg-divert' [2] 'grub-mkconfig' and 'update-grub' to get rid of the
> insane automation and usage of configs, to generate cluttered configs.
> Instead manually edit a clean grub.cfg and don't worry about any
> automation that could mess up anything.
>
> FWIW I'm using syslinux of my Arch Linux install, not from my Ubuntu
> Xenial install.
>
> Regards,
> Ralf
>
> [1]
> [weremouse@moonstudio src]$ grep bind /etc/fstab
> /mnt/archlinux/.boot/ubuntu_moonstudio/boot /boot  none   bind
>   0 0
>
> [2]
> http://manpages.ubuntu.com/manpages/xenial/man1/dpkg-divert.1.html
>
>
> @Ralf:
Thanks for the fast reply . . . indeed, there usually is "a learning curve"
. . . I was thinking after I posted that it might be "a nightmare" to try
to get my Mac Pro with 4 drives with multiple installs spread across each
of them, all switched over from Grub2 . . . without creating a "mess"
beyond the mess that I have now.

It seems like grub2 must "memorize" all of the systems that have ever been
installed or booted by Grub2 . . . because in SG2 disk the list of all of
the various "cfg's" . . . what "vmlinuz" and all of the other overlaps that
might boot something up . . . are all listed there and it's a "very long
list."

Maybe 6 months back I had a Sid linux distro installed and it turned out to
be "unfriendly" to the other distros and removed data across partitions and
possibly drives AND it messed up grub2 . . . and I had a thread on the
opensuse forum that was huugggeee with guys trying to help me figure out
how to get grub2 all tidy again . . . and in spite of what was pretty high
level help . . . nothing seemed to get grub2 "freshened" to just show the
current installs . . . it remina as you say, "cluttered."

It might be easier to fiddle with my olde laptop that only has two OSX
installs and one Manjaro . . . Manjaro is stacked on Arch, right??  That
install is my first or second Arch based install . . . might be "easier" to
get over to syslinux in that computer and if it blows up . . . not too
difficult to do a fresh install???

Or, is this something that is easier to do with a fresh install and then
instead of flagging the EFI boot partition with "grub2" . . . there's a
drop down choice for "syslinux"??

I was trying to figure out if Xenial is 16.04???  Ancient history man,
didn't they just "drop support" for it a couple weeks back???  Check out
Groovy . . . the water is "fine" in the 20.10 game.  : - 
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Apart from this I'm using syslinux instead of grub2.

[Fritz Hudnut]

> Message: 4
> Date: Fri, 10 Jul 2020 20:24:07 +0200
> From: Ralf Mardorf 
> T



> Apart from this I'm using syslinux instead of grub2.
>
>  @Ralf M

Been pondering this last sentence of yours for awhile, then yesterday I had
some "broken patch" error on a Ubuntu-MATE devel/groovy  hybrid system that
I have going, and something about that once again messed up the grub2 menu
access, so that the only linux system that would boot was the U-MATE option
out of the 5 that should have been there . . . the grub2 menu list wasn't
showing up, only "system not found hit any key to continue."

I had to again get the SG2 disk out and fiddle around trying to get
something else to boot up, got back into Tumbleweed . . . ran their Yast
bootloader and then their console "os-prober" command to get back into the
regulargrub2 boot menu.  While I was there I ran a zypper for "1078
packages" and somewhere in there I saw that "syslinux" was upgrading . . .
so OpenSUSE seems to have both grub2 & syslinux??

I and like 20 other people have posted on a launchpad bug report, "grub
menu hidden"???  reporting problems with grub2 on installation and in my
case, just in general use . . . one of the "devs" on that bug report
recently said, "This bug is not actionable, because of conflicting data
posted in the bug report . . . "  that bug has been up for many, many
months . . . and they seem to be saying that "It's by design the grub menu
isn't appearing" ?

I'd be curious if you could give any pointers on the difference between
grub2 and syslinux for booting multiple distros . . . in my case I have 5
linux and 5 OSX . . . might be adding another linux into the mix once I
figure out which one might be amusing . . . but, I am close to ditching
grub2 due to its "instability" when dealing with OSX security updates and
seemingly with ubuntu updates as well??

Any pointers on why you choose syslinux over grub2??

Thanks,

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Can I Use Other Desktops With Lubuntu (Aere Greenway)

[Fritz Hudnut]

> Lubuntu Users:
>
> I currently have Lubuntu 20.04 installed.  In that system, I installed
> the LXDE desktop, which works fine.
>
> Is it also possible to install the Gnome desktop in that system, and use
> that (choosing which desktop at login time)?
>
> I know it will use a fair amount of disk-space, but that isn't a problem
> for me.
>
> --
> Sincerely,
> Aere
>
>
>
> Aere:

There can be "issues" when running different DEs, like when I was messing
with LM a few years back their Cinnamon DE didn't seem to be too friendly
to others; but in linux theory it should be "problem free" . . . .

Back in the PPC days I ran Xubuntu with LXDE added . . . didn't seem to
cause problems . . . .  Now I have multiple OSs, and instead of having
multiple DEs I have variations of DE in the different systems . . . Plasma
seems to be very popular these days, and Lu is I think borrowing from
Plasma to do what it does, could be going to Plasma DE should be compatible
with modern Lu . . . or I have XFCE as the driver for one of my Manjaro
installs . . . XFCE is pretty good . . . lots of services, etc.  Cheap, etc.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] How to get back the wifi icon in taskbar (Wilbert Heeringa)

[Fritz Hudnut]

WH:

Thanks for the follow up, glad someone could help out with it . . . .

F

On Thu, Jul 2, 2020 at 2:41 AM Wilbert Heeringa 
wrote:

> Hi Fritz,
>
> Thanks for your help.
>
> Ranger5 advised me to run:
>
> nm-tray applet show
>
> After getting back the Status Notifier Plugin I ran this.
>
> Then I logged out and logged in and it was solved.
>
> --Wilbert
>
>
>
>
> Op di 30 jun. 2020 om 16:19 schreef Fritz Hudnut :
>
>>
>>
>>
>>
>>
>>> Dear all,
>>>
>>> I am using Lubuntu 20.04 LTS.
>>>
>>> I accidentally lost the wifi icon in the taskbar in the bottom right. I
>>> need it since I have to switch wifi connections (since my printer is
>>> connected via wifi).
>>>
>>> I tried:
>>> right-click taskbar
>>> Choose ‘Configure Panel’
>>> Click ‘Widgets’
>>> Click on +
>>> …
>>>
>>> Then I don’t know what to do, there is nothing in the list that seems to
>>> include the wifi icon. There is a ‘Network monitor’, but that’s something
>>> else, it does not give me a list of wifi connections which I can choose
>>> from.
>>>
>>> Via the Start button you can choose >Preferences >Advanced Network
>>> Configuration, but it does not solve the problem either.
>>>
>>> Does anybody know a solution?
>>>
>>>
>>>
>> @Wilbert:
>>
>> Did you try a basic apt update/upgrade??  I recall that over the years
>> the wifi applet would disappear, or sometimes show up as two applets . . .
>> problem seems to come and go, and often the next update/upgrade will
>> resolve the problem, or a couple of them?  Otherwise in terms of how to go
>> into the console and fix the problem . . . I don't know.
>>
>> F
>>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] How to get back the wifi icon in taskbar (Wilbert Heeringa)

[Fritz Hudnut]

> Dear all,
>
> I am using Lubuntu 20.04 LTS.
>
> I accidentally lost the wifi icon in the taskbar in the bottom right. I
> need it since I have to switch wifi connections (since my printer is
> connected via wifi).
>
> I tried:
> right-click taskbar
> Choose ‘Configure Panel’
> Click ‘Widgets’
> Click on +
> …
>
> Then I don’t know what to do, there is nothing in the list that seems to
> include the wifi icon. There is a ‘Network monitor’, but that’s something
> else, it does not give me a list of wifi connections which I can choose
> from.
>
> Via the Start button you can choose >Preferences >Advanced Network
> Configuration, but it does not solve the problem either.
>
> Does anybody know a solution?
>
>
>
@Wilbert:

Did you try a basic apt update/upgrade??  I recall that over the years the
wifi applet would disappear, or sometimes show up as two applets . . .
problem seems to come and go, and often the next update/upgrade will
resolve the problem, or a couple of them?  Otherwise in terms of how to go
into the console and fix the problem . . . I don't know.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] 18.04 LTS support length? (uninvol...@outlook.com)

[Fritz Hudnut]

Posting below the data posted above it . . . for the OP . . . .



> > Always interesting to see how OPs seem to disappear on ubuntu forums,
> and it winds up RPs discussing the topic . . . .
>
> Oh, I'm still here. My question was already answered and Thunderbird keeps
> stuffing these into the junk mail section.
>
> Also, once it replied to the respondents email address as I forgot to
> change it.
>
> But no, no I'm still here.
>

OK, glad to hear that, but if you were following the gist of it, you
**might** be able to upgrade to the newest LTS . . . and then simply add
"lxde" . . . and you would have the tried and true, but "olden" "lxde" GUI,
stacked on the freshest LTS??

It might be as simple as "sudo apt install lxde" . . . but it might be
something like "sudo apt install lxde-desktop-environment"  ???  If you
looked in synaptic it might show you how it would like to be commanded.

But possibly the difference between "lxde" and what is offered now, "lxqt
desktop" might be minimal and provide extended support, over the choice for
"lxde"???  The great joy of all flavors linux is almost unlimited choices
and any choice made can be changed, etc.



>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] 18.04 LTS support length? (uninvol...@outlook.com)

[Fritz Hudnut]

AG, et al:

Thank you.  So, the "question" might be how radically different is the
debian based "lxde" from the possibly lubuntu engineered "lxqt desktop"???
to find a way forward.

On Sat, May 23, 2020 at 1:44 PM Aere Greenway 
wrote:

> (my comments are bottom-posted)
> On 5/23/20 1:56 PM, Fritz Hudnut wrote:
>
> Always interesting to see how OPs seem to disappear on ubuntu forums, and
> it winds up RPs discussing the topic . . . .
>
> So, booted up in Lu 20.10 and checking the sessions I now have "Lubuntu"
> which seems to be thenewer, richer looking, possibly "Plasma" based GUI DE;
> and "LXQT Desktop" which seems to be more of the basic GUI DE; and then ye
> olde Openbox . . . minimalistic DE . . . .
>
> So I don't know if I had "lxde" only a few weeks back, and then moving up
> to "groovy" removed it, OR, that was an imaginary "fabrication" on my part
> and what I saw as "lxde" was the "lxqt desktop" option . . . that option
> seems similar to what was the traditional "lxde" . . . DE . . . maybe it
> has just been "renamed" as the easy way to change the DE, but under the
> name it is still . . . the same??  I didn't spend too long looking at the
> features offered in lxqt desktop session . . . but, just saying that
> especially in linux, "change is inevitable" . . . the clock runs forward .
> . . .
>
> On Thu, May 21, 2020 at 11:18 AM Fritz Hudnut 
> wrote:
>
>> Possibly I have lxde there from before there was lxqt and I've just
>> updated via changing the sources.list??  I can't remember when I did a
>> fresh install, but I think maybe I had to after Siduction ripped through
>> all of my drives and wiped data . . . probably would have been 18.04??  And
>> I didn't add lxde . . . but, I couldn't swear to that . . . .  : - ))
>>
>> On Thu, May 21, 2020 at 9:27 AM Aere Greenway 
>> wrote:
>>
>>> On 5/21/20 8:36 AM, Fritz Hudnut wrote:
>>>
>>>
>>>
>>>
>>>> Having now used LXQt, I'm much happier with LXDE. I'd like to stick
>>>> with LXDE as long as realistically possible, though I understand (I think)
>>>> the difficulties around that.
>>>>
>>>> Can anyone clear this up, thanks
>>>
>>>
>>> @et al:
>>>
>>> I'm pretty sure that even in 20.10 Lu that I have now, the option of
>>> LXQT, LXDE, or Openbox sessions are available on log in?
>>>
>>> Possibly Aere G could confirm that, but I believe there was a
>>> conversation regarding something similar not too long ago here?  Likely at
>>> least 20.04 . . . I'm a couple days away from my "lubuntu" day . . . .
>>>
>>> F
>>>
>>>
>>> I'm pretty sure you have to install the lxde package, before the LXDE
>>> option appears in the "Session" drop-box, near the upper left corner of the
>>> log-in screen.
>>>
>>> --
>>> Sincerely,
>>> Aere
>>>
>>>
>>>
>>> The LXDE desktop I see on Lubuntu 20.04, appears identical to the LXDE
> desktop I see on my Debian Buster systems.
>
> The launcher icon, and the dark, rounded taskbar, as well as the LXDE
> splash-screen are the same on Lubuntu 20.04, and on Debian Buster.
>
> I suspect the LXDE we get on Lubuntu 20.04, is the same as comes from
> Debian.
>
> --
> Sincerely,
> Aere
>
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] 18.04 LTS support length? (uninvol...@outlook.com)

[Fritz Hudnut]

Always interesting to see how OPs seem to disappear on ubuntu forums, and
it winds up RPs discussing the topic . . . .

So, booted up in Lu 20.10 and checking the sessions I now have "Lubuntu"
which seems to be thenewer, richer looking, possibly "Plasma" based GUI DE;
and "LXQT Desktop" which seems to be more of the basic GUI DE; and then ye
olde Openbox . . . minimalistic DE . . . .

So I don't know if I had "lxde" only a few weeks back, and then moving up
to "groovy" removed it, OR, that was an imaginary "fabrication" on my part
and what I saw as "lxde" was the "lxqt desktop" option . . . that option
seems similar to what was the traditional "lxde" . . . DE . . . maybe it
has just been "renamed" as the easy way to change the DE, but under the
name it is still . . . the same??  I didn't spend too long looking at the
features offered in lxqt desktop session . . . but, just saying that
especially in linux, "change is inevitable" . . . the clock runs forward .
. . .

On Thu, May 21, 2020 at 11:18 AM Fritz Hudnut  wrote:

> Possibly I have lxde there from before there was lxqt and I've just
> updated via changing the sources.list??  I can't remember when I did a
> fresh install, but I think maybe I had to after Siduction ripped through
> all of my drives and wiped data . . . probably would have been 18.04??  And
> I didn't add lxde . . . but, I couldn't swear to that . . . .  : - ))
>
> On Thu, May 21, 2020 at 9:27 AM Aere Greenway 
> wrote:
>
>> On 5/21/20 8:36 AM, Fritz Hudnut wrote:
>>
>>
>>
>>
>>> Having now used LXQt, I'm much happier with LXDE. I'd like to stick with
>>> LXDE as long as realistically possible, though I understand (I think) the
>>> difficulties around that.
>>>
>>> Can anyone clear this up, thanks
>>
>>
>> @et al:
>>
>> I'm pretty sure that even in 20.10 Lu that I have now, the option of
>> LXQT, LXDE, or Openbox sessions are available on log in?
>>
>> Possibly Aere G could confirm that, but I believe there was a
>> conversation regarding something similar not too long ago here?  Likely at
>> least 20.04 . . . I'm a couple days away from my "lubuntu" day . . . .
>>
>> F
>>
>>
>> I'm pretty sure you have to install the lxde package, before the LXDE
>> option appears in the "Session" drop-box, near the upper left corner of the
>> log-in screen.
>>
>> --
>> Sincerely,
>> Aere
>>
>>
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] 18.04 LTS support length? (uninvol...@outlook.com)

[Fritz Hudnut]

Possibly I have lxde there from before there was lxqt and I've just updated
via changing the sources.list??  I can't remember when I did a fresh
install, but I think maybe I had to after Siduction ripped through all of
my drives and wiped data . . . probably would have been 18.04??  And I
didn't add lxde . . . but, I couldn't swear to that . . . .  : - ))

On Thu, May 21, 2020 at 9:27 AM Aere Greenway 
wrote:

> On 5/21/20 8:36 AM, Fritz Hudnut wrote:
>
>
>
>
>> Having now used LXQt, I'm much happier with LXDE. I'd like to stick with
>> LXDE as long as realistically possible, though I understand (I think) the
>> difficulties around that.
>>
>> Can anyone clear this up, thanks
>
>
> @et al:
>
> I'm pretty sure that even in 20.10 Lu that I have now, the option of LXQT,
> LXDE, or Openbox sessions are available on log in?
>
> Possibly Aere G could confirm that, but I believe there was a conversation
> regarding something similar not too long ago here?  Likely at least 20.04 .
> . . I'm a couple days away from my "lubuntu" day . . . .
>
> F
>
>
> I'm pretty sure you have to install the lxde package, before the LXDE
> option appears in the "Session" drop-box, near the upper left corner of the
> log-in screen.
>
> --
> Sincerely,
> Aere
>
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] 18.04 LTS support length? (uninvol...@outlook.com)

[Fritz Hudnut]

> Having now used LXQt, I'm much happier with LXDE. I'd like to stick with
> LXDE as long as realistically possible, though I understand (I think) the
> difficulties around that.
>
> Can anyone clear this up, thanks


@et al:

I'm pretty sure that even in 20.10 Lu that I have now, the option of LXQT,
LXDE, or Openbox sessions are available on log in?

Possibly Aere G could confirm that, but I believe there was a conversation
regarding something similar not too long ago here?  Likely at least 20.04 .
. . I'm a couple days away from my "lubuntu" day . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 20.04 (Aere Greenway)

[Fritz Hudnut]

AG:

Great . . . yep, didn't seem to be an overly serious problem . . . possibly
will resolve itself the next time there is an update listed for
"chromium"  But, sometimes these small problems persist . . . such is
the nature of linux-land . . . .

On Fri, May 1, 2020 at 7:36 PM Aere Greenway 
wrote:

> On 5/1/20 7:02 PM, Fritz Hudnut wrote:
> > well anyway, I'm sure your process was done properly, I was just
> > joshing you about being "wrong" . . . because it would be so unlikely,
> > etc.  I'm sure you noticed that I logged in and out of the three DE
> > options and found "chromium" in the menu . . . we can only "hope and
> > pray" that yours shows up?
>
> I'm not sure why it doesn't show up in the menu of the LXDE desktop on
> my system, but I was able to create a desktop launcher for Chromium, so
> all is well, as far as I'm concerned.
>
> --
> Sincerely,
> Aere
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 20.04 (Aere Greenway)

[Fritz Hudnut]

AG:

Is that "bottom v top" posting really a thing?  I didn't know that . . .
well anyway, I'm sure your process was done properly, I was just joshing
you about being "wrong" . . . because it would be so unlikely, etc.  I'm
sure you noticed that I logged in and out of the three DE options and found
"chromium" in the menu . . . we can only "hope and pray" that yours shows
up?

Only other top posted offering, I mentioned synaptic because I think there
are a few different versions of "chrome" out there, and it might have been
that synaptic showed "chromium-browser" as the package in the repos??  but
I believe that whatever it was I picked that . . . whereas I think in my
other distros I might have used "apt install chromium" . . . ???

But, again, I had not previously logged into the LXDE session before your
post, so it was pre-loaded or pre-preferred . . . and chromium was there in
the menu . . . .

Trying to provide relevant data . . . I think I was running 20.04 since it
was alpha . . . really not too many issues, it's a fine release.

On Fri, May 1, 2020 at 9:00 AM Aere Greenway 
wrote:

> (See below, bottom-posted, as they request us to do)
>
> On 5/1/20 8:53 AM, Fritz Hudnut wrote:
>
> Aere G:
>
> 
>
> So it looks like overall the Lu 20+ install is "OK" . . . except for the
> issue with Chromium ID in the drop down menu??
>
> Having just done a couple of upgrade moves to get to 20.10 in both of my
> ubuntu distros, I do recall seeing a wiki that seemed to suggest going from
> LTS to the next LTS, in this case 18.04 . . . and then to 20.04 . . . you
> may have gone through that process, but it wasn't spelled out . . .
> **possibly** if you jumped from 16 straight outta compton to 20  that
> may have got some stuff "mishandled"
>
> Usually if there is some issue, even "bug report" level stuff, after a few
> updates they often "just disappear . . . gone . . . just like that, gone .
> . . ."
>
> On Thu, Apr 30, 2020 at 7:17 PM Aere Greenway 
> wrote:
>
>> (I posted on the bottom, below)
>>
>> On 4/30/20 4:50 PM, Fritz Hudnut wrote:
>>
>> AG:
>>
>> OK, well, that might be "exclusive," as in my lxde desktop session I have
>> a visual listing of it . . . .  Did you run another "apt
>> update/dist-upgrade" subsequently to your install?
>>
>> On Thu, Apr 30, 2020 at 2:48 PM Aere Greenway 
>> wrote:
>>
>>> On 4/30/20 12:15 PM, Fritz Hudnut wrote:
>>>
>>> Aere:
>>>
>>> I was running Lu 20.04 up until it was released and now I'm in 20.10 . .
>>> . I have Chromium browser installed and it is plainly in view in the
>>> "internet" menu . . .also in the drop down is "chrome apps" . . . .  It's
>>> been so long since I did the install,possibly through synaptics . . . it
>>> should be there, I might think that whether in LXQT or LXDE if it's
>>> installed, it's "installed."
>>>
>>> All I can think of is perhaps you did something "wrong."   : -
>>> )
>>>
>>> F
>>>
>>> It does appear in the menu when using the Lubuntu, or lxqt desktop.  It
>>> just doesn't appear in the menu when using the lxde desktop.
>>>
>>> --
>>> Sincerely,
>>> Aere
>>>
>>>
>>>
>>> I originally installed Lubuntu as a test system, and I kept updating it
>> to the latest version.  I'm not sure which level I started with.
>>
>> When I upgraded to Lubuntu 20.04 (in a terminal session, using "sudo
>> do-release-upgrade -d"), things seemed to be working well, and I was able
>> to install my Eclipse Java development environment, and things were working
>> well.
>>
>> My Ubuntu 20.04 upgrade (which I was thinking of switching to), didn't
>> end up with a working Eclipse development environment.
>>
>> Using the LXDE desktop on Lubuntu 20.04, I was able to even use my
>> strange color scheme, which I like a lot, and things were working in
>> Eclipse.
>>
>> So I restored my production files from 16.04 to the 20.04 system, and
>> started working with that.
>>
>> That process proceeded without many problems, so I 'transferred my flag'
>> to the new system.
>>
>> I'm just now cleaning up the last few 'rough edges'.
>>
>> The thing I like most about the new system, is that Rosegarden now loads
>> channel recording filters (which it didn't on 16.04, and LibreOffice
>> Writer, once again allows you to produce HTML files where graphics images
&

Re: [lubuntu-users] Lubuntu 20.04 (Aere Greenway)

[Fritz Hudnut]

Aere G:



So it looks like overall the Lu 20+ install is "OK" . . . except for the
issue with Chromium ID in the drop down menu??

Having just done a couple of upgrade moves to get to 20.10 in both of my
ubuntu distros, I do recall seeing a wiki that seemed to suggest going from
LTS to the next LTS, in this case 18.04 . . . and then to 20.04 . . . you
may have gone through that process, but it wasn't spelled out . . .
**possibly** if you jumped from 16 straight outta compton to 20  that
may have got some stuff "mishandled"

Usually if there is some issue, even "bug report" level stuff, after a few
updates they often "just disappear . . . gone . . . just like that, gone .
. . ."

On Thu, Apr 30, 2020 at 7:17 PM Aere Greenway 
wrote:

> (I posted on the bottom, below)
>
> On 4/30/20 4:50 PM, Fritz Hudnut wrote:
>
> AG:
>
> OK, well, that might be "exclusive," as in my lxde desktop session I have
> a visual listing of it . . . .  Did you run another "apt
> update/dist-upgrade" subsequently to your install?
>
> On Thu, Apr 30, 2020 at 2:48 PM Aere Greenway 
> wrote:
>
>> On 4/30/20 12:15 PM, Fritz Hudnut wrote:
>>
>> Aere:
>>
>> I was running Lu 20.04 up until it was released and now I'm in 20.10 . .
>> . I have Chromium browser installed and it is plainly in view in the
>> "internet" menu . . .also in the drop down is "chrome apps" . . . .  It's
>> been so long since I did the install,possibly through synaptics . . . it
>> should be there, I might think that whether in LXQT or LXDE if it's
>> installed, it's "installed."
>>
>> All I can think of is perhaps you did something "wrong."   : -
>> )
>>
>> F
>>
>> It does appear in the menu when using the Lubuntu, or lxqt desktop.  It
>> just doesn't appear in the menu when using the lxde desktop.
>>
>> --
>> Sincerely,
>> Aere
>>
>>
>>
>> I originally installed Lubuntu as a test system, and I kept updating it
> to the latest version.  I'm not sure which level I started with.
>
> When I upgraded to Lubuntu 20.04 (in a terminal session, using "sudo
> do-release-upgrade -d"), things seemed to be working well, and I was able
> to install my Eclipse Java development environment, and things were working
> well.
>
> My Ubuntu 20.04 upgrade (which I was thinking of switching to), didn't end
> up with a working Eclipse development environment.
>
> Using the LXDE desktop on Lubuntu 20.04, I was able to even use my strange
> color scheme, which I like a lot, and things were working in Eclipse.
>
> So I restored my production files from 16.04 to the 20.04 system, and
> started working with that.
>
> That process proceeded without many problems, so I 'transferred my flag'
> to the new system.
>
> I'm just now cleaning up the last few 'rough edges'.
>
> The thing I like most about the new system, is that Rosegarden now loads
> channel recording filters (which it didn't on 16.04, and LibreOffice
> Writer, once again allows you to produce HTML files where graphics images
> are linked-to in the HTML file, rather than forcing you to embed them as
> data within the HTML file.
>
> I've been using an old copy of openSUSE Linux for editing HTML web-pages,
> because of the need to keep the graphics images separate.  But now, I can
> use my production system to do it once again.
>
> --
> Sincerely,
> Aere
>
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 20.04 (Aere Greenway)

[Fritz Hudnut]

AG:

OK, well, that might be "exclusive," as in my lxde desktop session I have a
visual listing of it . . . .  Did you run another "apt update/dist-upgrade"
subsequently to your install?

On Thu, Apr 30, 2020 at 2:48 PM Aere Greenway 
wrote:

> On 4/30/20 12:15 PM, Fritz Hudnut wrote:
>
> Aere:
>
> I was running Lu 20.04 up until it was released and now I'm in 20.10 . . .
> I have Chromium browser installed and it is plainly in view in the
> "internet" menu . . .also in the drop down is "chrome apps" . . . .  It's
> been so long since I did the install,possibly through synaptics . . . it
> should be there, I might think that whether in LXQT or LXDE if it's
> installed, it's "installed."
>
> All I can think of is perhaps you did something "wrong."   : -
> )
>
> F
>
> It does appear in the menu when using the Lubuntu, or lxqt desktop.  It
> just doesn't appear in the menu when using the lxde desktop.
>
> --
> Sincerely,
> Aere
>
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 20.04 (Aere Greenway)

[Fritz Hudnut]

Aere:

>From the somewhere between 20.04 & pre-Groovy system that I have for LU, I
logged out of LXQT and logged into LXDE session, and indeed Chromium was
there in the >internet menu, I launched it . . . I logged out, and tried to
log into Openbox . . . had done an update w/o rebooting and system froze.
Restarted and logged into Openbox, and right-clicking shows
>internet>chromium in the menu . . . I picked Firefox to type this email.
Should be showing up w/o issue??

F

On Thu, Apr 30, 2020 at 11:15 AM Fritz Hudnut  wrote:

> Aere:
>
> I was running Lu 20.04 up until it was released and now I'm in 20.10 . . .
> I have Chromium browser installed and it is plainly in view in the
> "internet" menu . . .also in the drop down is "chrome apps" . . . .  It's
> been so long since I did the install,possibly through synaptics . . . it
> should be there, I might think that whether in LXQT or LXDE if it's
> installed, it's "installed."
>
> All I can think of is perhaps you did something "wrong."   : -
> )
>
> F
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Lubuntu 20.04 (Aere Greenway)

[Fritz Hudnut]

Aere:

I was running Lu 20.04 up until it was released and now I'm in 20.10 . . .
I have Chromium browser installed and it is plainly in view in the
"internet" menu . . .also in the drop down is "chrome apps" . . . .  It's
been so long since I did the install,possibly through synaptics . . . it
should be there, I might think that whether in LXQT or LXDE if it's
installed, it's "installed."

All I can think of is perhaps you did something "wrong."   : - )

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Install problems? try do-release-upgrade ??

[Fritz Hudnut]

Gents, et al:

Problems with fresh install?  If there was a Lu install already there, why
not run it in the console via "do-release-upgrade" . . . everything you had
set up should remain, and only new "/" is dropped in.

Or, the way I've been doing it, change the /etc/apt/sources.list  from
"bionic" or whatever to "focal" and then run update/upgrade.  All you need
is a base install, which if you have to run a fresh install via alternate
installer that works, do that, then upgrade it via console.

I was in 20.04 . . . and a couple of days I back I went to Groovy . . .
before there is Groovy, I'm "there" . . . from focal . . . found a simple
command online to run that changes the sources.list very fast.  Easy.  No
messing with the installer . . . is that "calamares"

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Looks like there might be a solution to the problem posted in the launchpad
bug report, won't have time to get to it today, but might tomorrow . . . ??

On Mon, Jan 13, 2020 at 11:32 AM Walter Lapchynski  wrote:

> On Mon, Jan 13, 2020 at 11:28:03AM -0800, Fritz Hudnut wrote:
> > are now two files ending in "upload" in "var/crash" . . . ??
>
> I'd delete those, too.
>
> > Done with messing with it for today, I'll see if the "system report"
> window
> > opens when I log back in tomorrow morning . . .
>
> For this service which is most likely started at boot, I suspect a full
> system restart will be necessary.
>
> > I'll try to post
> > to Lu developer list for the next potential issue that may come up in
> 20.04
>
> Yep. And any other development releases to come.
>
> > . . . ??  I'm sure there's a process involved with doing that
>
> You just need to subscribe to lubuntu-devel live you've subscribed to
> lubuntu-users here and post to it in the same way.
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Walter:

Yep, I do know that cups is for printing, but I didn't take the time to
actually read the entire bug thread to try to figure out why this is
happening . . . just quickly saw that the OP had nvidia graphics and I have
had some issues in various distros relating to nvidia drivers not upgrading
with other upgrades . . . causing substantial problems with the system
  It's "non-critical" for me in that for the most part I'm not printing
much of anything at home due to the expense of it . . . .

And, thanks for the full command, since I was already "in" /var/crash  I
just ran "sudo rm file name" didn't use the "-f" . . . cursor just
returned, file wasn't showing in Trash, but then possibly the "bug report"
process changed the name of the file to ".crash.upload" ???  as there
are now two files ending in "upload" in "var/crash" . . . ??

Done with messing with it for today, I'll see if the "system report" window
opens when I log back in tomorrow morning . . . otherwise we might be done
on this thread if filing the bug report "deals with it"??  I'll try to post
to Lu developer list for the next potential issue that may come up in 20.04
. . . ??  I'm sure there's a process involved with doing that that I'll
look at later.

On Mon, Jan 13, 2020 at 11:06 AM Walter Lapchynski  wrote:

> On Mon, Jan 13, 2020 at 10:52:18AM -0800, Fritz Hudnut wrote:
> > seems like the OP is also using
> > nvidia graphics, might relate there??
>
> Given this is related to CUPS, it's doubtful it has anything to do with
> graphics. In case you're not aware, CUPS is a print server.
>
> > Now to find "sudo" and try to trash that file . . . .
>
> `sudo rm -f /var/crash/_usr_sbin_cups-browsed.0.crash`
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Walter:

Managed to get to var/crash in the console and ran the "ubuntu-bug
_usr_sbin_cups-browsed.0.crash"  again and it opened a more official
looking "ubuntu system crash report" with the effected file showing in the
details, so I "reported" that and then it took me to "launchpad file a bug
report" . . . and it looks like a similar bug filed as #1857815  so I just
added my self there to that bug . . . seems like the OP is also using
nvidia graphics, might relate there??

Now to find "sudo" and try to trash that file . . . .



>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Walter:

Sure, I think you have suggested not using dev releases several times
before . . . it's just for kicks . . . it's a form of testing.  Mostly I'm
using GUI so the ins and outs of the console come and go . . . for the most
part there aren't a whole lot of problems in the ubuntu realm, even in
20.04, it's more or less like 19.10 . . . so I'm not getting a lot of
practice in filing bugs or using the console to navi to a folder and do
stuff . . . I'm old, so I forget data pretty quickly.  : - ))


On Mon, Jan 13, 2020 at 9:31 AM Walter Lapchynski  wrote:

> On Mon, Jan 13, 2020 at 09:17:04AM -0800, Fritz Hudnut wrote:
> > OK, I know nothing . .. nthhhiii . . . .
>
> Then I recommend not using development releases!!! XD
>
> > I tried to trash
> > the file, and it was greyed out in right-click, and I tried to drag it to
> > "trash" and that didn't work . . . seems like it doesn't want to go
> > willingly to the Trash???  : - )
>
> It's not in your home folder, so you don't have permission to do it. You
> would need to `sudo` your way to it.
>

Ah, OK, yes . . . the "sudo" qualifier . . . I vaguely remember that . . .
what day is today??  : - 0

>
> --
>@wxl | polka.bike
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Walter:

OK, I know nothing . .. nthhhiii . . . .  Running out of
time for it today, but after I did that failed command, I tried to trash
the file, and it was greyed out in right-click, and I tried to drag it to
"trash" and that didn't work . . . seems like it doesn't want to go
willingly to the Trash???  : - )

I ran an update/upgrade after this and it pulled in a bunch of files . . .
ran autoremove/autoclean as well . . . .

On Mon, Jan 13, 2020 at 8:21 AM Walter Lapchynski  wrote:

>
>
> On January 13, 2020 8:10:11 AM PST, Fritz Hudnut 
> wrote:
> >PS: I ran "ubuntu-bug _usr_sbin_cups-browsed.0.crash"  and it showed a
> >GUI
> >error window, "No such file or directory detected"??
>
> That's like saying "file a bug report with this file IN THE PRESENT
> WORKING DIRECTORY." If $PWD isn't /var/crash and you hadn't copied the file
> from there, it wouldn't work.
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

PS: I ran "ubuntu-bug _usr_sbin_cups-browsed.0.crash"  and it showed a GUI
error window, "No such file or directory detected"??

On Mon, Jan 13, 2020 at 7:55 AM Fritz Hudnut  wrote:

> Walter, et al:
>
> OK, looked in var/crash and there was a file there,
> "_usr_sbin_cups-browsed.0.crash" . . . not exactly sure what "run
> ubuntu-bug" against it means . . . but I did look at the bug you had linked
> and I'm not sure if that is the same as what I'm experiencing.  That bug
> seemed to be "continuously flashing it's message" . . . in my case the
> "system problem detected" error just flashes when I log into GUI . . .
> seemingly each time I log in, w/o explanation.
>
> It's not a dealbreaker for me, and I'll try trashing the file and see what
> happens . . . but, hopefully those others who reported having a similar
> problem with it will be able to report their issues . . . openly on the
> list, which is a place for discussion about Lubuntu???
>
> F
>
>
> On Fri, Jan 10, 2020 at 10:23 AM Walter Lapchynski  wrote:
>
>> On Fri, Jan 10, 2020 at 09:43:09AM -0800, Fritz Hudnut wrote:
>> > I saw something about "Compton compositer" in that same basic
>> > area, and that was "unchecked" . . . ??  I thought that Compton is the
>> more
>> > or less default compositer these days?
>>
>> Yep, but not enabled by default.
>>
>> > system problem detected" error window opened, and … there isn't
>> > any "would you like more information about this?" $tab to see what it
>> is.
>>
>> This may because you had a program crash. Look in /var/crash. If there's
>> anything there, you can just run `ubuntu-bug` against it. After that,
>> make sure you delete anything in there otherwise you'll get the same
>> harassing messages.
>>
>> --
>>@wxl | polka.bike
>>
>>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Walter, et al:

OK, looked in var/crash and there was a file there,
"_usr_sbin_cups-browsed.0.crash" . . . not exactly sure what "run
ubuntu-bug" against it means . . . but I did look at the bug you had linked
and I'm not sure if that is the same as what I'm experiencing.  That bug
seemed to be "continuously flashing it's message" . . . in my case the
"system problem detected" error just flashes when I log into GUI . . .
seemingly each time I log in, w/o explanation.

It's not a dealbreaker for me, and I'll try trashing the file and see what
happens . . . but, hopefully those others who reported having a similar
problem with it will be able to report their issues . . . openly on the
list, which is a place for discussion about Lubuntu???

F


On Fri, Jan 10, 2020 at 10:23 AM Walter Lapchynski  wrote:

> On Fri, Jan 10, 2020 at 09:43:09AM -0800, Fritz Hudnut wrote:
> > I saw something about "Compton compositer" in that same basic
> > area, and that was "unchecked" . . . ??  I thought that Compton is the
> more
> > or less default compositer these days?
>
> Yep, but not enabled by default.
>
> > system problem detected" error window opened, and … there isn't
> > any "would you like more information about this?" $tab to see what it is.
>
> This may because you had a program crash. Look in /var/crash. If there's
> anything there, you can just run `ubuntu-bug` against it. After that,
> make sure you delete anything in there otherwise you'll get the same
> harassing messages.
>
> --
>@wxl | polka.bike
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] "System problem detected"??

[Fritz Hudnut]

Walter:

OK, thanks for the reply . . . been awhile since I posted anything in Lu
devel . . . I think I was a "member" there but then wasn't???  But,
alrighty, in the future I'll look into posting there . . . I just see it as
"Lubuntu" based . . . as the GUI still says "19" and the desktop looks the
same, etc.  : - )

I'll check into the /var/crash dealie, don't recall seeing any error about
a "crash" lately . . . overall 20 is trouble free for the end user such as
myself.

On Fri, Jan 10, 2020 at 10:23 AM Walter Lapchynski  wrote:

> On Fri, Jan 10, 2020 at 09:43:09AM -0800, Fritz Hudnut wrote:
> > I saw something about "Compton compositer" in that same basic
> > area, and that was "unchecked" . . . ??  I thought that Compton is the
> more
> > or less default compositer these days?
>
> Yep, but not enabled by default.
>
> > I did a Lu 20.04 upgrade a day or so back
>
> Generally, I wouldn't discuss the development release on the
> lubuntu-users list and would confine that to the lubuntu-devel list
> since the development release could be in all sorts of states of broken.
> I would also not expect stability from it.
>
> > system problem detected" error window opened, and … there isn't
> > any "would you like more information about this?" $tab to see what it is.
>
> This may because you had a program crash. Look in /var/crash. If there's
> anything there, you can just run `ubuntu-bug` against it. After that,
> make sure you delete anything in there otherwise you'll get the same
> harassing messages.
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] "System problem detected"??

[Fritz Hudnut]

@Walter:

So unchecking that in the LXQT Session Settings tab, did solve that
questioning problem, and while I was there I unchecked "lock screen before
suspending" as my computer station is not in a public area, etc.  While I
was there I saw something about "Compton compositer" in that same basic
area, and that was "unchecked" . . . ??  I thought that Compton is the more
or less default compositer these days?  I looked around to see if there was
somewhere else where I had overridden Compton, but didn't find it in a fast
look.  My problem is that I have 5 linux installs and a few OSX installs
going in the same computer, so it never gets too "in depth" of a
relationship with each system . . . it remains largely "superficial" in
nature.

Speaking of "superficial" . . . I did a Lu 20.04 upgrade a day or so back
and after a re-start the "system problem detected" error window opened, and
I click "go" on "reporting it" . . . but unlike in prior days there isn't
any "would you like more information about this?" tab to see what it is.
Up in the toolbar applets there was some kind of symbol and I clicked or
right-clicked on it and it showed "There is a problem, right click on
Package Manager to fix the problem" . . . I scrolled down and clicked on
"launch package manager" and synaptic opened . . . and that was showing "no
problems detected."  I went to the "fix dependencies" tab and a
milli-second later it showed "dependencies fixed."  : - ))

This morning a booted Lu and got the same "system problem" error . . . I
fiddled on the net, and awhile later there was a "you have updates waiting
for your command" notification . . . I thought, Oh, maybe that will fix the
problem with the system, ran them, logged out, ate breakfast . . . came
back and logged in to the same error . . . ??  I autoremoved "libplymouth4"
and logged out . . . got same error.

All updates are mostly run via console and apt and just using apt
recommends, not fiddling with trying to add other stuff . . . and yet . . .
some "problem" is being reported??  Nothing appears overtly wrong with the
system functions . . . .

F

On Thu, Jan 9, 2020 at 1:29 PM Fritz Hudnut  wrote:

> Walter:
>
> Thanks for finding that answer . . . I'll give it a try tomorrow morning .
> . . .
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Wish list for Lu 20.04 in 2020

[Fritz Hudnut]

Walter:

Thanks for finding that answer . . . I'll give it a try tomorrow morning .
. . .

On Thu, Jan 9, 2020 at 11:41 AM Walter Lapchynski  wrote:

> On 2020-01-09 17:40, Fritz Hudnut wrote:
> > Possibly there is a way to "disable" these nagging inquiries . . .
>
> I didn't think there was, but I guess I had to "RTFM" as [the answer is
> indeed in our manual][1]: uncheck the "Ask confirmation to leave
> session" box in LXQt Session settings.
>
> [1]: https://manual.lubuntu.me/stable/3/3.2/3.2.13/session_settings.html
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Wish list for Lu 20.04 in 2020

[Fritz Hudnut]

Folks:

Happy New Year to the list . . . .  While we are posting our wish list
items for Lu . . . one area where I wouldn't mind an "adjustment" would be
in the "when I click suspend I'd just like the machine to suspend, and not
open a window asking me 'Do you really want to suspend?' . . ." and having
to ask myself that question each time is just taking up too much time to
ponder it and think about "Why did I click suspend when the machine just
wants to keep running on Lu 20.04 from the sheer joy of using it?"   : - )))

Other OSs I'm using in this machine will just "suspend" or "quit" when I
click on it, no heavy questions about my motivation for clicking on it . .
. for the most part, if there was something "un-saved" would that app not
ask me to save, etc?  In other words, "suspending" is temporary in nature
and wouldn't likely cause any insurmountable issues?

Possibly there is a way to "disable" these nagging inquiries . . . just
haven't had time to investigate . . . but in comparison to other installs I
have, the "question window" thing is a tad cumbersome . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] No Sound in 20.04??

[Fritz Hudnut]

Nio:

Thanks for the reply, I like to get in "early" on stuff and then be gone by
the time the full release is released, etc.  After I sent that email I
fiddled with alsamixer, and that didn't seem to work, then I did a Google
and saw that "PulseAudio" would be the culprit . . . .  I then did a system
update/upgrade and in the list was "pulseaudio" . . . and logging out I
thought nothing changed, but I went back to YT and now I have sound and
listening to a Coltrane track . . . !!!  So, that issue has already been
polished and/or fixed??? early in the process . . . .  : - ))

F

On Sat, Dec 14, 2019 at 11:11 AM Nio Wiklund  wrote:

> Den 2019-12-14 kl. 19:42, skrev Fritz Hudnut:
> > Gents:
> >
> > Maybe I spoke too soon about how "everything appears the same in 20.04"
> > . . . just tried to play a YT video of a singer . . . the sound applet
> > shows "sound" is "on" . . . I went into Pulse Audio and it seems like
> > there should be "sound" . . . YT sound bar was maxed . . . and yet there
> > was nothing but visual and the sound of silence???
> >
> > Is this like back in the 12.04 days where alsamixer had to be launched
> > and stuff had to be adjusted there?  I forgot "alsamixer" until I was
> > typing this out, but still, seems like in the upgrade from 19.10 to
> > 20.04 sound got dropped??
> >
> > F
> >
>
> Hi Fritz,
>
> Please remember that Focal Fossa is still in the development phase. It
> will not be released until April next year, and we must be prepared for
> temporary glitches (and maybe even some show-stopping bugs) during this
> period.
>
> As a matter of fact, I do not consider an LTS version ready until the
> release of the first point release in July or August. By that time it
> will probably be well debugged and polished.
>
> Best regards
> Nio
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] No Sound in 20.04??

[Fritz Hudnut]

Gents:

Maybe I spoke too soon about how "everything appears the same in 20.04" . .
. just tried to play a YT video of a singer . . . the sound applet shows
"sound" is "on" . . . I went into Pulse Audio and it seems like there
should be "sound" . . . YT sound bar was maxed . . . and yet there was
nothing but visual and the sound of silence???

Is this like back in the 12.04 days where alsamixer had to be launched and
stuff had to be adjusted there?  I forgot "alsamixer" until I was typing
this out, but still, seems like in the upgrade from 19.10 to 20.04 sound
got dropped??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Upgraded to focal via console "release-upgrade" but it comes up with a giant 19????

[Fritz Hudnut]

Folks:

So I spent the last month trying to figure out how to fix a recent
Tumbleweed install that got lost in grub or somewhere . . . finally got it
straightened out via "chroot-ing" . . . don't understand why that worked
after trying a bunch of stuff . . . ??

So today I was doing some stuff in Lu 19.10 . . . and after my TW
"adventures" I was thinking that 19.10 was "getting a little worn out," a
little too easy . . . but I didn't want to go through the hassle of editing
the /etc/apt/sources.list . . . again . . . .  So I found the ubuntu wiki
on doing the forced upgrade . . . didn't think it through too much, just
ran it in the GUI console, and seems like it more or less took care of it .
. . couldn't really have been much simpler.  It just deletes third party
apps, so I had to add the mkusb ppa back in . . . I guess at some point
I'll have to delete the "eoan" stuff from the sources.list or software
sources???  seems to have left some trails of "eoan" behind . . . .

Otherwise, I can't say there is too much difference in the 20 GUI from 19 .
. . in fact there was a GIANT "19" in the middle of the log in screen???
What's up with dat??  : - )  It should have been, "This one goes to
twenty, mnn . . . ."

I'll try to pay attention to anything that seems to be requiring attention
in the coming months . . .
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] First response to Lu 20.04 alpha LTS live session . . . .

[Fritz Hudnut]

>
> 1. Live only
>
> Most linux distros provide hybrid iso files, and they make bootable live
> systems when cloned to a USB pendrive (or SSD or memory card). Cloning
> is the main mode of mkusb.
>
> 2. Persistent live
>
> mkusb can also create persistent live drives, but it is more tricky. It
> is an extracting method designed to work with Ubuntu and the Ubuntu
> family flavours (e.g. Lubuntu) and Debian live. mkusb can also create
> persistent live systems with some distros that are similar enough, for
> example Linux Mint, but it will *not* work with most other linux distros.
>
> ---
>
>
>
> Best regards
> Nio
>

Nio:

Thanks again for the details, all seems clear, but seems like you are
saying that the choice for "cloning" as one of the options is the same as
"live installer"???  I usually use "make a live installer" but saw the
"cloning" option which I thought was for making duplicates, rather than the
regular mode??

Got it on the persistent live as a way to move a bootable system around to
other computers, etc.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] First response to Lu 20.04 alpha LTS live session . . . .

[Fritz Hudnut]

@Nio:

Thanks for taking the time to reply.


> Hi Fritz,
>
> An 8GB usb 2.0 flash drive is small and very slow. It works well for a
> live (live-only) system, and can work also for a persistent live system,
> if you use it in a careful way. But it is a bad idea to update & upgrade
> it.
>
> If you have an SSD connected via a USB 3 adapter or box, you have a big
> and fast drive, and you can use mkusb to make a persistent live system,
> that will be very responsive. Such a system can be updated & upgraded
> without problems.
>
> But you should be aware, that the original kernel and its drivers will
> be used, because they are started before the overlay structure of the
> persistent live system is active.
>
> I have tested a persistent live Lubuntu system in an SSD for a long time
> with
>
> sudo apt update
> sudo apt full-upgrade
>
> for a long time without any problems.
>
> I have tested mkusb with Focal Fossa, and it works as it should, except
> that there is a new bug, that will affect you when you try to boot the
> persistent live drive in live-only mode. See this link
>
> https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123
>
> Best regards
> Nio
>

OK I read through that bug report, overall I find mkusb to be very reliable
and consistent maker of live installers, only recently have I started to
fiddle with "persistent" . . . because I saw you and others talking about
it . . . but I guess I don't actually know what it is or does . . . .

I usually discover stuff "the hard way" . . . and the usb2 flash drive was
the "drive I had" at the time and then scrolling thru the "dus" menu I saw
"persistent" . . . and jsut went for it w/o considering the smallish size
of the drive.

In the recent episode of trying to restore or reinstall several systems
that were damaged I was using a 16GB flash and figured that might be a
little "better" . . . but the persistent option seemed to come and go, so I
mainly went back to "live."

One thing to mention, although in the past I had used the usb3 port on my
MP this time the making process seemed to be "quicker" . . . and in the
case of trying out Solus' smallish file size on the .iso . . . very fast;
but then the computer wouldn't boot them (2 versions of it) and not only
that the alt/option key wouldn't bring up the mobo boot manager to choose
any systems.  Took a few minutes to figure out to pull the flash drive and
then function came back.

The making and booting and installing of Manjaro had gone well, I happened
to look into the live folder of the Solus system and there were only 3
folder/directories inside, I recall from memory, I think there was no "EFI
boot" mentioned?  Anyway, there seemed to be a problems with Solus.

That's when I went back to my olde Lu possibly 19.10 iso and zsync'd it
into Focal, and mkusb handled it well, although possibly "persistent"
didn't show up in the list?  Or if it did all I was testing was to see if I
could boot a live installer, which for Lu 20.04 it did well.  Yesterday I
used mkusb to wipe the drive and install an OpenSUSE TW iso and all went
well, after I figured out the pilot error on the OSuse installer . . .
although it didn't seem to get grub in order--otherwise mkusb worked quite
well.
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] First response to Lu 20.04 alpha LTS live session . . . .

[Fritz Hudnut]

Walter:


Appreciate the reply, everything seemed to run well in the live iso on my
'12 MP . . . opened a few apps, nothing seemed to freeze as they had in the
past.

I was considering installing it in the third partition of my 09 MBP laptop,
but if you don't think it's ready for prime time . . . why did it seem to
be "difficult" to get it turned into a "persistent live" usb drive?  I did
one before with Lu 19.10 using mkusb into an 8GB usb 2.0 flash drive and it
didn't complain at all . . . it just took hours to get part way through an
update so I cancelled out of it. This time it kept asking for "efi" and
"grub" and saying it could download them and then it couldn't, and then it
just cancelled the deal, so I just ran a regular live installer and it went
fine.

But if I could get a persistent version of Lu 20.04 going it could be
easier to run through breakages than a bare metal install . . . Siduction
busted up my other linux partitions pretty good a couple times, finally
giving up on it as it's like OSX and doesn't play well with others . . . ???

On Fri, Nov 1, 2019 at 3:28 PM Walter Lapchynski  wrote:

>
>
> On November 1, 2019 2:01:22 PM PDT, Fritz Hudnut 
> wrote:
> > it seems essentially the same as Eoan
>
>
> I should also point out that the images we have are quite old since the
> current Qt transition is breaking new builds. Again, early in the cycle,
> breakages of all kinds are to be expected.
> --
>@wxl | polka.bike
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] First response to Lu 20.04 alpha LTS live session . . . .

[Fritz Hudnut]

So I was fiddling around with some other distro and the live iso wasn't
booting up, so then I thought OK, I'll try Lubuntu and I tried to zsync it
but it wasn't recognizing the file . . . then I saw that current was now
"focal" . . . so I zsync'd that and mkusb did a good job on the "live"
version, couldn't seem to get "persistent" to work on it . . . .

First comment, it seems essentially the same as Eoan, but the desktop image
shows a "19 Eoan Ermine" image, rather than some kind of "20 Focalized
Fossil" type of image???  Intentional??  Seemed like mkusb was reading the
file as "Eoan" when it looked at the base package, but then showed "Focal"
before the install . . . so are there "mixed" sources at play??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Where have all the Bash Shells gone??? "mystery" possibly "solved"

[Fritz Hudnut]

Chris, et al:

Got to thinking, since it seemed like you were using radeon/AMD video, that
both of my computers are running nvidia cards, the 09 MBPro came with
Nvidia, but my '12 MPro came with radeon driver, but I needed to upgrade
the graphics card to get OSX 10.14 running, and I did that perhaps 8 months
to a year ago . . . .  And then for the ubuntu flavors it's very easy to
add the "additional drivers" . . . and over time I changed most, if not all
of the linux installs to nvidia proprietary drivers . . . .  I started
thinking that this might be a "nividia" issue because when I had problems
with getting the machine to "revive from suspend" some folks on the
OpenSUSE forum said, "You should change to proprietary driver . . ." which
I did . . . figured that this tty problem then might be a similarly based
problem.

Since it seemed like another one of those "guy must be crazy" deals I ran a
search on Google and found a thread on the Linux Mint forum where the OP
had the same "screen goes black and nothing happens" issue that I am
experiencing . . . in a thread from . . . 2014 . . . so it seems like
Nvidia is jumping all over this one and is getting it straightened right
out.

https://forums.linuxmint.com/viewtopic.php?t=168108

It does provide some edits to GRUB, and I might get time to mess with it,
right now I'd rather have "suspend" and "revive from suspend" than a TTY,
but possibly the "mystery" is "solved" . . . the ball is in Nvidia's court
and it's just lying there . . . .

F


>
>>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Where have all the Bash Shells gone???

[Fritz Hudnut]

Chris G:

So I booted the persistent live flash drive with Lu 19.10 installed I think
from a daily from 8/19/19 . . . on the same MacPro with the same apple
keyboard . . . and there I could get a tty to show up . . . I do have to
use fn+cntrl+alt + I used your f4 . . . but then couldn't log in to the tty
session, couldn't think of my user name that I might have made or didn't
make for it, as I only made it to test something for wxl . . . and then I
couldn't get the shell to return to the GUI . . . had to hit the power
button to get out of it . . . .

F

On Fri, Sep 13, 2019 at 8:44 PM Chris Guiver  wrote:

> I tried the newer daily (2019-09-13) and it worked on
> - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
> - sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)
>
> I also have Lubuntu 19.10 installed & used on
> - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
> 5000/6000/7350/8350)
> - dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
> 5000/6000/7350/8350)
> - sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)
>
> The d960 is my primary desktop, so I'd notice it not working there very
> quickly.
>
> I do however have a keyboard - Logitech Office Internet keyboard  (I
> don't see a specific model number) where ctrl+alt+Fn does NOT work,
> but that keyboard sends different codes & it's the non-standard
> keyboard's fault in my opinion.  I've noted the same on a microsoft &
> third brand I can't think of that also sent non-standard responses
> (when compared to normal keyboard using `xev` and like tools). They
> were cheap keyboards so I just put them aside, can't recall what I
> discovered the reason was but they were sold only to work with
> windows, and the non-standard returns were to add some function in
> windows but not need extra component & cost (side effect was certain
> key combinations give wrong results - logitech's answer was used
> another of their keyboards).  Your keyboard issue could be because of
> this - ie. a non-standard keystrokes.
>
> Chris g.
>
> On 9/14/19, Fritz Hudnut  wrote:
> > Chris G:
> >
> > Thanks for the reply, well, I noticed this problem across two Macs, and
> > multiple linux hard metal installs . . . .  I do have a "persistent live"
> > usb flash drive of Lu 19.10 . . . maybe I'll try to boot that and see if
> > the tty works there . . . but seemingly on the full installs it just not
> > like it was . . . .
> >
> > On Fri, Sep 13, 2019 at 6:41 PM Chris Guiver  wrote:
> >
> >> I did some QA-testing using the 2019-09-12 daily image of 19.10 and
> >> didn't notice any issues with virtual terminals
> >> (
> >>
> http://iso.qa.ubuntu.com/qatracker/milestones/404/builds/199233/testcases/1303/results/
> >> ).
> >>
> >> I used in testing
> >> - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
> >> 5000/6000/7350/8350)
> >> - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
> >>
> >> and just booted the same 2019-09-12 image on
> >> - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
> >> - lenovo thinkpad x201 (i5-m520, 4gb, i915)
> >> and get virtual terminals.  As I use ctrl+alt+f4 & ctrl+alt+f5 mostly
> >> (I find them easier to find with my fingers without looking)  these
> >> would be all I test before switching back to gui.
> >>
> >> I don't have an intel/amd based mac - but I don't see the issue an
> >> anything I've tested on, nor can I recall noticing it before.
> >>
> >> Chris g.
> >>
> >> On 9/14/19, Fritz Hudnut  wrote:
> >> > I was trying to help a buddy get some form of ubuntu to boot up on his
> >> > iMac, so then I was looking over the ubuntu apple hardware users
> >> sub-forum
> >> > and saw a couple of posts about problems getting ubuntu installed on
> >> Macs,
> >> > and I was going to suggest to one poster to "try to get to a tty" . .
> .
> >> so
> >> > I tried myself, at that time I was running a Leap 15.1 system . . .
> >> screen
> >> > went black, but no login prompt showed up out of the blacknesses . . .
> >> did
> >> > manage to get back to the GUI in that system.
> >> >
> >> > Then today I tried a number of my systems, debian, u-mate, Lu 19.10,
> >> Gecko
> >> > . . . and it seems like the tty Bash shells have gone extinct???  In
> Lu
> >> the
> >> > screen went black, then the display light went orange . . . and would
> >> > not
> >> > return

Re: [lubuntu-users] Where have all the Bash Shells gone???

[Fritz Hudnut]

Chris G:

Thanks for the reply, well, I noticed this problem across two Macs, and
multiple linux hard metal installs . . . .  I do have a "persistent live"
usb flash drive of Lu 19.10 . . . maybe I'll try to boot that and see if
the tty works there . . . but seemingly on the full installs it just not
like it was . . . .

On Fri, Sep 13, 2019 at 6:41 PM Chris Guiver  wrote:

> I did some QA-testing using the 2019-09-12 daily image of 19.10 and
> didn't notice any issues with virtual terminals
> (
> http://iso.qa.ubuntu.com/qatracker/milestones/404/builds/199233/testcases/1303/results/
> ).
>
> I used in testing
> - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
> 5000/6000/7350/8350)
> - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
>
> and just booted the same 2019-09-12 image on
> - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
> - lenovo thinkpad x201 (i5-m520, 4gb, i915)
> and get virtual terminals.  As I use ctrl+alt+f4 & ctrl+alt+f5 mostly
> (I find them easier to find with my fingers without looking)  these
> would be all I test before switching back to gui.
>
> I don't have an intel/amd based mac - but I don't see the issue an
> anything I've tested on, nor can I recall noticing it before.
>
> Chris g.
>
> On 9/14/19, Fritz Hudnut  wrote:
> > I was trying to help a buddy get some form of ubuntu to boot up on his
> > iMac, so then I was looking over the ubuntu apple hardware users
> sub-forum
> > and saw a couple of posts about problems getting ubuntu installed on
> Macs,
> > and I was going to suggest to one poster to "try to get to a tty" . . .
> so
> > I tried myself, at that time I was running a Leap 15.1 system . . .
> screen
> > went black, but no login prompt showed up out of the blacknesses . . .
> did
> > manage to get back to the GUI in that system.
> >
> > Then today I tried a number of my systems, debian, u-mate, Lu 19.10,
> Gecko
> > . . . and it seems like the tty Bash shells have gone extinct???  In Lu
> the
> > screen went black, then the display light went orange . . . and would not
> > return to the GUI no matter what keys I tried???
> >
> > What's up wit dat???  Being able to get to a Bash Shell is one of the
> > handier things about running linux for troubleshooting and so forth.  I
> saw
> > a thread from last year on an OpenSUSE forum thread from Dec '18 where
> one
> > poster said, "they broke the tty" and then another admin saying, "Why did
> > you say 'they' . . .???" but then didn't seem to discuss it anymore.  I
> > know I have dropped into a Bash shell on one of my many systems pretty
> > recently . . . but now it seems like . . . it ain't happnin' 
> >
> > F
> >
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Where have all the Bash Shells gone???

[Fritz Hudnut]

I was trying to help a buddy get some form of ubuntu to boot up on his
iMac, so then I was looking over the ubuntu apple hardware users sub-forum
and saw a couple of posts about problems getting ubuntu installed on Macs,
and I was going to suggest to one poster to "try to get to a tty" . . . so
I tried myself, at that time I was running a Leap 15.1 system . . . screen
went black, but no login prompt showed up out of the blacknesses . . . did
manage to get back to the GUI in that system.

Then today I tried a number of my systems, debian, u-mate, Lu 19.10, Gecko
. . . and it seems like the tty Bash shells have gone extinct???  In Lu the
screen went black, then the display light went orange . . . and would not
return to the GUI no matter what keys I tried???

What's up wit dat???  Being able to get to a Bash Shell is one of the
handier things about running linux for troubleshooting and so forth.  I saw
a thread from last year on an OpenSUSE forum thread from Dec '18 where one
poster said, "they broke the tty" and then another admin saying, "Why did
you say 'they' . . .???" but then didn't seem to discuss it anymore.  I
know I have dropped into a Bash shell on one of my many systems pretty
recently . . . but now it seems like . . . it ain't happnin' 

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Testing 19.10 feedback feature request

[Fritz Hudnut]

@Walter/Lubuntu:

Booted up Lu 19.10 a few minutes ago and seems like the "suspend" applet
has been added to the Lu log in window from a previous upgrade . . . so
thanks kindly for adding that in . . . .  I'll put it to use in a few
minutes for a "system test" . . . .

F

On Sat, Aug 17, 2019 at 2:52 PM ∅  wrote:

> On Sat, Aug 17, 2019 at 08:09:40AM -0700, Fritz Hudnut wrote:
> > I made a request awhile back to have a "suspend the system from the
> > log in window" and that would continue to be the request.
>
> Added a [task][1] to get this in 19.10. I've already written the little
> bit of code that needs to be there to support it. All we need is an
> image and I'll upload it all to the archive.
>
> > I wanted to "log out" of the user, and then "suspend"
>
> I will say that this is one thing I don't understand. Why wouldn't you
> just suspend? Seems like you're just making extra steps for yourself.
>
> [1]: https://phab.lubuntu.me/T110
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] new software needs testing (Walter Lapchynski)

[Fritz Hudnut]

In line comments, couldn't get the Phab links to work in this session
running the persistent live 19.10 in usb2 flashdrive:

On Tue, Aug 20, 2019 at 10:10 PM ∅  wrote:

> On Mon, Aug 19, 2019 at 02:11:23PM -0700, Fritz Hudnut wrote:
> > So I easily downloaded the "sddm-config-editor" . . . but I would need
> more
> > exact commands
>
> Download it. Assuming it downloads to ~/Downloads/sddm-config-editor:
>
>  1. cd ~/Downloads
>  2. chmod +x sddm-config-editor
>  3. ./sddm-config-editor
>

Alrighty, mea culpea, I **should** have known the "cd" . . . but I prolly
would have missed the "~" part.  So I ran those commands and I checked the
"Have sddm auto-login" and I changed the Theme from "breeze" to "lubuntu" .
. . then I went on to the "killall compton" stuff, that'll be posted
below.  On reboot I ran back through the sddm commands, and the settings I
had changed were intact . . .  I changed them back to what they were and
hit "apply" . . . .  Nothing happens too fast in this usb2 flashdrive
system, but I'll check to see if the old settings are back where they were
in a day or so.

>
> > "Fatal error" part is what got my attention, saying "another composite
> > manager is already running"
>
> Try again with `killall -s 9 compton`. Then to make sure it's not
> running, do `pgrep compton`. If it comes back with nothing, you're good.
> Then try running `compton` again.
>

Ran these commands and on return it said "compton: no process found" . . .
wasn't sure if that was because I had "killed" it, or other distinct
possibility I was still in "Downloads"??  can't remember, but trying to
"exit" out of Downloads seems to "exit" out of the Terminal entirely, which
I don't remember happening before.  Anyway, I then typed "compton" and I
got the data posted below.  The top lines over the compton command shows
the bottom few lines of a long string of the "sddm" data, and then the
"compton" data.  Once I figured out I was still in "Downloads" I restarted
the terminal and ran "compton" again . . . got the same basic data.

Also, while this was going on I watched a video on YT . . . seemed to be
more or less "OK" . . . only "issue" so far is that some of the command
menus didn't seem to be too bright, and didn't seem to stay open too long,
but I don't know if that's because I changed some settings in the "Window
effects" . . . I did that yesterday, I checked the two bottom boxes on the
first page . . . ???  Anyway, overall, nothing too crazy going on . . . '12
Mac Pro with Nvidia GTX 780 card and 16 GB RAM.

[code]a layout. This is undefined behavior; use Layout.alignment instead.
qrc:/ui/boolean-editor.qml:64:3: QML Text: Detected anchors on an item that
is managed by a layout. This is undefined behavior; use Layout.alignment
instead.
qrc:/ui/boolean-editor.qml:19:3: QML CheckBox: Detected anchors on an item
that is managed by a layout. This is undefined behavior; use
Layout.alignment instead.
qrc:/ui/boolean-editor.qml:34:3: QML CheckBox: Detected anchors on an item
that is managed by a layout. This is undefined behavior; use
Layout.alignment instead.
qrc:/ui/boolean-editor.qml:64:3: QML Text: Detected anchors on an item that
is managed by a layout. This is undefined behavior; use Layout.alignment
instead.
lubuntu@lubuntu:$ compton
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] Option
`no-dock-shadow` is deprecated, and will be removed. Please use the wintype
option `shadow` of `dock` instead.
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] Option
`no-dnd-shadow` is deprecated, and will be removed. Please use the wintype
option `shadow` of `dnd` instead.
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] Option `menu-opacity`
is deprecated, and will be removed.Please use the wintype option `opacity`
of `popup_menu` and `dropdown_menu` instead.
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] vsync option will
take a boolean from now on. "none" is interpreted as "false" for
compatibility, but this will stop working soon
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] glx-swap-method has
been deprecated since v6, your setting "undefined" should be removed.
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] "clear-shadow" is
removed as an option, and is always enabled now. Consider removing it from
your config file
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] "paint-on-overlay"
has been removed as an option, and is enabled whenever possible
[ 08/21/19 08:52:43.657 parse_config_libconfig WARN ] "alpha-step" has been
removed, compton now tries to make use of all alpha values  [/code]



> Thanks for the help!
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] new software needs testing (Walter Lapchynski)

[Fritz Hudnut]

>
> Message: 1
> Date: Sun, 18 Aug 2019 13:27:22 -0700
> From: Walter Lapchynski 
> To: lubuntu-users@lists.ubuntu.com
> Subject: [lubuntu-users] new software needs testing
> Message-ID: <20190818202721.GD11217@zzt>
> Content-Type: text/plain; charset="utf-8"
>
> For 19.10, there's two pieces of software that we're considering getting
> in:
>
>  1. sddm-config-editor, a GUI for the display manager configuration
>  2. a more updated, featureful fork of our compositor, compton
>
> We've put together some versions to test and could really use your help
> and as soon as possible because 19.10 is set to be released relatively
> soon! To be clear, these should be tested in a 19.10 environment. It's
> ok if you run it in the live environment, so you don't have to overwrite
> your existing install. You can find images to download [here][0].
>
>
> [0]: http://cdimage.ubuntu.com/lubuntu/daily-live/current/
> [1]: https://phab.lubuntu.me/T20
> [2]: https://share.riseup.net/#a0LeSAKG-cODXFDjjSTGww
> [3]: https://github.com/lxqt/compton-conf/issues/18
> [4]: https://phab.lubuntu.me/T96
>
> --
>
>
> Hello Walter and the Lu list:

I'm speaking to you from within a "persistent live" usb 19.10 session,
which I set up using your linked daily, to more or less mimic my "bare
metal" Lu 19.10 install . . . because generally what you are asking is just
a bit beyond my knowledge/skills and although my Lu install is
"developmental" I still didn't want to botch it up playing with stuff that
I didn't understand, whereas in the p-live flashdrive I could . . . .

So I easily downloaded the "sddm-config-editor" . . . but I would need more
exact commands to work with because the terminal isn't responding to my
various attempts to reproduce your commands, clearly the "chmod +x" is not
working.  Like Ian, the file is in /home/lubuntu/Downloads . . . but trying
to add that in front of "sddm-x-x" isn't working . . . and neither is
adding the "./sddm-x-x" after it . . . so for now that testing is on hold.
Do I need to "extract" that file, and if I do that then what?  Or can I do
what Ian did and just "boot" it up from with the Downloads file  I
would need more specific commands to get that part tested.

Moved on to add your ppa and update the system and it installed a few other
packages along with "compton" showing in the command line "setting up
compton (7.3-0buntu1-ppa5)" . . . I then added the Nvidia 430 driver via
the Additional Drivers and rebooted the system, because I'm driving an
aftermarket Nvidia card in my Mac Pro '12 unit.  Whereas before the newer
compton when I clicked on Accesories >> compton the browser window would
briefly "flash" . . . but after the new compton was installed there was
more of a delay and then possibly no flash.  I went into Prefs >> Window
effects and I changed a couple of buttons and hit "apply" . . . and as I
think you suggested . . . nothing happened??  So I opened the terminal and
ran your suggested "killall" . . . and I got the responses below??  the
"Fatal error" part is what got my attention, saying "another composite
manager is already running"

Testing has concluded for the time being . . . but, generally, if this is
the "testing" compton the windows seem to be working fine, no crashes, no
burns.

lubuntu@lubuntu:~$ killall compton && compton
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] Option
`no-dock-shadow` is deprecated, and will be removed. Please use the wintype
option `shadow` of `dock` instead.
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] Option
`no-dnd-shadow` is deprecated, and will be removed. Please use the wintype
option `shadow` of `dnd` instead.
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] Option `menu-opacity`
is deprecated, and will be removed.Please use the wintype option `opacity`
of `popup_menu` and `dropdown_menu` instead.
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] vsync option will
take a boolean from now on. "none" is interpreted as "false" for
compatibility, but this will stop working soon
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] glx-swap-method has
been deprecated since v6, your setting "undefined" should be removed.
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] "clear-shadow" is
removed as an option, and is always enabled now. Consider removing it from
your config file
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] "paint-on-overlay"
has been removed as an option, and is enabled whenever possible
[ 08/19/19 13:46:19.508 parse_config_libconfig WARN ] "alpha-step" has been
removed, compton now tries to make use of all alpha values
[ 08/19/19 13:46:19.510 register_cm FATAL ERROR ] Another composite manager
is already running
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Testing 19.10 feedback feature request

[Fritz Hudnut]

@Walter:

Thanks kindly for adding that into the features, whether it is
"understandable" or not, it is appreciated.  In my case I have Lu 19.10 in
my multi-boot Mac Pro, and so booting a system at least requires a "Grub"
decision, select a system, then wait while the selected system runs through
its "boot" . . . some of them take several minutes to "find the swap" or
something similar . . . although the ubuntu options do do well on the boot
quickness front, others do not and are quite "slow" to arrive at the log in
window.

So, sometimes I want to boot a system, but then don't have time to log in
right then, so being able to "suspend" **before** logging in is the feature
that I find in many other linux installs that I have . . . and having them
in the other systems, U-MATE, a couple OpenSUSE, a sid debian . . . sets up
a "groove" . . . which then caused a "skip" when it came to doing the same
behavior with Lu . . . .

But, yes, as far as Lu is set up, if I suspend when I revive it asks for a
password, so if I'm logged in already it is "redundant" to log out . . .
but others of my installs don't ask for a password when reviving . . .
hence the "log out" to a more secure suspend . . . .  But doing that in the
present iteration of Lu brought the two button option to just "reboot" or
"shut down" . . . .  However, in most of the other linux systems I am
running, the "shut down" button also brings the full range of operational
buttons to choose from, i.e., "suspend," "hibernate," "restart," or "shut
down" . . . so again, "habit" brings the thought that "shut down button
brings all the options" . . . but in the "old" Lu 19.10 . . . it only
brought "the end."

F

On Sat, Aug 17, 2019 at 2:52 PM ∅  wrote:

> On Sat, Aug 17, 2019 at 08:09:40AM -0700, Fritz Hudnut wrote:
> > I made a request awhile back to have a "suspend the system from the
> > log in window" and that would continue to be the request.
>
> Added a [task][1] to get this in 19.10. I've already written the little
> bit of code that needs to be there to support it. All we need is an
> image and I'll upload it all to the archive.
>
> > I wanted to "log out" of the user, and then "suspend"
>
> I will say that this is one thing I don't understand. Why wouldn't you
> just suspend? Seems like you're just making extra steps for yourself.
>
> [1]: https://phab.lubuntu.me/T110
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Testing 19.10 feedback feature request

[Fritz Hudnut]

@TheLuDevs:

Continuing to "test" 19.10, and other than a few GUI retro quirks, all is
well.  I made a request awhile back to have a "suspend the system from the
log in window" and that would continue to be the request.  Yesterday I was
going to be away from the computer for 1.5 hours, and as in my other linux
systems I wanted to "log out" of the user, and then "suspend" . . . but
once in the Log In window . . . only choice is"reboot" or "shut down" . . .
very "limited" or "limiting" in the "command and control" sense.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Ubuntu forums for "usb mobile broadband modem"

[Fritz Hudnut]

https://ubuntuforums.org/forumdisplay.php?f=336  is the link to the Ubuntu
Forums sub-forum for "Networking and Wireless" . . . that forum generally
has been pretty fast on the response/comments.  Top posting for speed and
efficiency . . . .

F



>
>
> The kernel is a core part of Ubuntu. All the flavors share it. That
> said, this is really not a Lubuntu specific problem, but a problem of
> all of the flavors and derivatives of Ubuntu. I say this because the
> Lubuntu Team is relatively small and no one I know has such a device to
> test with. You'll get more luck reaching out to the Ubuntu community as
> a whole. Perhaps askubuntu.com?
>
>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] USB flash drive filesystem (Ian Bruntlett)

[Fritz Hudnut]

>
> I bought a USB flash drive and was wondering what filesystem I should be
> using on it.
>
> I think it is formatted as exFAT but am not sure.
>
> Any ideas?
>
> Thanks :)
>
>
> Ian
>
>
>

> PS:
>
> FAT32 is also good to share data on Linux machines, between different
> user IDs. If you really want to temporarily store xattrs and privileges
> you could use a tar archive on the FAT32 formatted USB stick.
>
>
>
> --
>
> Message: 5
> Date: Thu, 1 Aug 2019 22:45:58 +0200
> From: Ralf Mardorf 
> To: lubuntu-users@lists.ubuntu.com
> Subject: Re: [lubuntu-users] USB flash drive filesystem
> Message-ID: <20190801224558.2c785a04@archlinux>
> Content-Type: text/plain; charset=US-ASCII
>
> PPS:
>
> FAT32:
>
> max. file size 4 GiB, max. volume size is 16 TiB
>
> When not using FAT32:
>
>
> Ian, et al:

Not to be "argumentative" but . . . considering that most operating system
installs are going to be larger than 4GB, the "exFAT" option seems like the
just fine decision for the base formatting.  Of course if you are going to
try an install on the drive then you will be formatting it via the
installer to something like "ext4" or what have you.  Then the "exFAT v
FAT32" decision is . . . somewhat "moot."  It something that obviously can
easily be changed or re-done, numerous times in the life of the drive.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Audio stuttering/crackling in Lubuntu 18.04 (Felipe M. Vieira)

[Fritz Hudnut]

Hi everyone,

>
> I'm a long time Lubuntu user and I have been facing audio issues from
> a `dist-upgrade` from 16.04 to 18.04. I have detailed the question there:
>
> From:
> https://askubuntu.com/questions/1158648/audio-stuttering-crackling-in-ubuntu-18-04
>
> For convenience:
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
> The audio is stuttering/crackling whenever played in external
> speakers/headphone or the laptop's speaker.
>
>
> @Felipe:

Unfortunately I can't help you, because I know nothing about "sound" in
linux.  But, you have made a detailed post, however, the machine you are
trying to get sound in . . . doesn't seem to be mentioned here??  I didn't
click on any links . . . .

We do have a few people who do know about "sound" here and perhaps they
will reply to your question??

The only suggestion I would try is that since Lu is under heavy
development, it might behoove you to move forward to 19.04??  I'm running
19.10 development and overall it is "good" . . . but I did have some
"dependency" issues with an nvidia driver that broke the GUI recently, so I
wouldn't say to jump up to that, but 19.04 is very good and **might**
address or fix your issues??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] goodbye forever, i386 (Aere Greenway)

[Fritz Hudnut]

>
> Where my Lubuntu 18.04 i386 systems all started to no longer boot
> reliably, it motivated me to switch them to Debian.
>
> The things that cause me problems with Debian, so far, is that there is a
> long delay during the reboot after installing Debian 9, where it seems to
> be doing nothing at all, and you really have to just wait for it to
> complete.  Debian 10 doesn't have that problem, and uses the same installer
> as Lubuntu 18.10 (Calamares).
>
> The other problem, is that wireless support on Debian is much poorer than
> with Ubuntu.  It surprised me that I have only one wireless dongle that
> works with Debian out-of-the-box.  After some effort installing things, I
> was able to get the Broadcom (b43) wireless of my HP Mini working.  The
> wireless of my 32-bit MacBook also worked out-of-the-box.
>
> From what I read, all of the Debian releases are supported for 5 years, so
> Debian 10 should be good until July of 2024.
>
> I now know enough to help my kids migrate their systems to Debian 10.
>
> Where so many of my machines are now on Debian, perhaps I should join that
> band of Debian purists.
> --
>
> Sincerely,
> Aere
>
>
>
AG:

So far the Sid/Buster system I have installed has been pretty clear to get
done on the install, and in this machine I use ethernet . . . so no
problems connecting; but I do get the "you should install the b43 module" .
. . error, but I just ignore it.  When I first installed it Buster/Sid
booted up super fast, flew through the dmesg page and into the GUI log in
in the blink of an eye . . . but, over time we've had some growing pains
and it lashed out at the other systems . . . doing damage . . . and so
other systems had to be re-installed after the Sid/Buster . . . and that
seemed to get Buster to "lose track of swap" and other errors requiring
"thought processing" on the boot up . . . and so now it boots fairly
sedately . . . for a 64 bit system.

You could try to join the purists, but they seem to be "picky" . . . and
not exactly "warm" . . . being more on the "technical" side of the
personality spectrum . . . .

But, it does seem a bit "early" for problems to be showing up in 18.04 ??
which should still be "current" LTS across the platforms??  Anyway, you
would have had to move to keep the 32 bit units going sometime soon . . .
perhaps Debian will have more motivation to support the 32 bit crowd
compared to the low motivation for the bleating PPC crowd . . . where the
"death of PPC" was a slow and lingering thing, followed by dropping it like
a stone ??  : - (

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] goodbye forever, i386 (Aere Greenway)

[Fritz Hudnut]

> Thanks for the suggestion.  All of my 32-bit machines are now running
> Debian.  I've tested both Debian 9 (stretch), and Debian 10 (buster).
>
> I use the LXDE desktop, and it is very familiar, and all tests are
> successful.  System updates are different, but easily learned.
>
> --
> Sincerely,
> Aere
>

@Aere:

Thought I'd try to go back to when folks would try to respond to posts
here, rather than just "watch" the posts go on by . . . so, cool that
Debian is still providing an image for 32 bit . . . obviously it isn't
radically different than Ubuntu, other than having to do more stuff
"manually" to get them installed . . . .  Carry on with it . . . I just
checked for any remaining vestiges of "PPC" there, and, sadly . . . none
are current . . . I would assume that 32-bit will stagger forward there for
another couple of years before the ports start being "finicky" as they are
now in remaining Lu 16.04 PPC systems . . . "can't find the package at
http://ports/backports; . . . something like that . . . .

I've got a #Siduction/Plasma install which is based on Deb 10 . . . "sid" .
. . does have a bit of a learning curve to it to avoid blowing everything
up, but otherwise . . . more or less the generic linux system with the
usual band of debian type "purists" gathered around it . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: the new kernel does not sweep clean in Lu 19.10?

[Fritz Hudnut]

@Walter:


>  Minutes later . . . I scrolled back up into the data in the console
> window above the final errors and saw a few things:
>
> [code]I: The initramfs will attempt to resume from /dev/sdc7
>
> I: Set the RESUME variable to override this.
> Processing triggers for linux-image-5.0.0-20-generic (5.0.0-20.21) ...
> /etc/kernel/postinst.d/dkms:
>  * dkms: running auto installation service for kernel 5.0.0-20-generic
>
> Kernel preparation unnecessary for this kernel.  Skipping...
>
> Building module:
> cleaning build area...
> unset ARCH; env NV_VERBOSE=1 'make' -j8 NV_EXCLUDE_BUILD_MODULES=''
> KERNEL_UNAME=5.0.0-20-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
> SYSSRC=/lib/modules/5.0.0-20-generic/build LD=/usr/bin/ld.bfd
> modules.(bad exit status: 2)
> ERROR: Cannot create report: [Errno 17] File exists:
> '/var/crash/nvidia-dkms-430.0.crash'
> Error! Bad return status for module build on kernel: 5.0.0-20-generic
> (x86_64)
> Consult /var/lib/dkms/nvidia/430.26/build/make.log for more information.
>...done.
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-5.0.0-20-generic
> cryptsetup: WARNING: The initramfs image may not contain cryptsetup
> binaries
> nor crypto modules. If that's on purpose, you may want to uninstall
> the
> 'cryptsetup-initramfs' package in order to disable the cryptsetup
> initramfs
> integration and avoid this warning.
> I: The initramfs will attempt to resume from /dev/sdc7  [/code]
>
> And then the data from the previous post showing the "nvidia" errors . . .
> .  I haven't set up anything for "encrypting" so I don't know what that is
> about . . . just ran a basic install, etc.
>
> F
>

Yep, when I rebooted after this the grub menu showed, scrolled down to Lu,
dmesg showed up, the Lu splash showed up briefly . . . then back to the
dmesg where it "froze" . . . got into a tty and ran "-f install" and it
shows the "nvidia" driver issue, says it was "rebuilding" . . . seems to
run through some issues . . . and winds up with the same "nvidia 430"???
error . . . and the GUI doesn't load.  I tried "advanced options" and into
"recovery" and "dpkg" . . . and that said, "fixed, please reboot" . . .
which I did . . . spent about an hour trying different stuff . . . none of
it seemed to get into the GUI . . . .  Seems like the driver from nvidia
isn't working with any of the latest kernels . . . from 5.20 and 5.17 . . .
.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: the new mouse does not sweep clean in Lu 19.10?

[Fritz Hudnut]

@Walter:

On Sun, Jul 7, 2019 at 5:34 PM Fritz Hudnut  wrote:

> @Walter:
>
So again today I got back to Lu 19.10 fiddled around in the GUI, then just
> a few minutes ago I ran an "apt update/upgrade" . . . at the end of which
> then finally "showed" some errors in the console . . . as well as opening a
> fresh "system program problem" again . . . which had also loaded when I
> logged in . . . .  The problem reported was:
>
> [code] Errors were encountered while processing:
>  nvidia-dkms-430
>  nvidia-driver-430
> E: Sub-process /usr/bin/dpkg returned an error code (1) [/code]
>
> F
>
>
>  Minutes later . . . I scrolled back up into the data in the console
window above the final errors and saw a few things:

[code]I: The initramfs will attempt to resume from /dev/sdc7

I: Set the RESUME variable to override this.
Processing triggers for linux-image-5.0.0-20-generic (5.0.0-20.21) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.0.0-20-generic

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 'make' -j8 NV_EXCLUDE_BUILD_MODULES=''
KERNEL_UNAME=5.0.0-20-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/5.0.0-20-generic/build LD=/usr/bin/ld.bfd
modules.(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-dkms-430.0.crash'
Error! Bad return status for module build on kernel: 5.0.0-20-generic
(x86_64)
Consult /var/lib/dkms/nvidia/430.26/build/make.log for more information.
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.0.0-20-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup
binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup
initramfs
integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sdc7  [/code]

And then the data from the previous post showing the "nvidia" errors . . .
.  I haven't set up anything for "encrypting" so I don't know what that is
about . . . just ran a basic install, etc.

F

>
>>
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: the new mouse does not sweep clean in Lu 19.10?

[Fritz Hudnut]

@Walter:

Previous post: "So today, back in Lu 19.10, and logging into the GUI shows
the "system program problem" error window once again . . . I ran an
update/upgrade in Lu and then rebooted back into U-MATE for the comparison,
which continued to **not** show this same error window that it had a day or
so back.  Ran an update/upgrade there and then rebooted back into Lu 19.10
. . . and the error window continues . . . without capacity for stating
"the reasons for this error" . . . ??
>
>
> F"
>

So again today I got back to Lu 19.10 fiddled around in the GUI, then just
a few minutes ago I ran an "apt update/upgrade" . . . at the end of which
then finally "showed" some errors in the console . . . as well as opening a
fresh "system program problem" again . . . which had also loaded when I
logged in . . . .  The problem reported was:

[code] Errors were encountered while processing:
 nvidia-dkms-430
 nvidia-driver-430
E: Sub-process /usr/bin/dpkg returned an error code (1) [/code]

Nvidia drivers were added likely before this "system program problem"
report error stuff, by way of "Additional Drivers" . . . and I usually pick
the newest, but "proprietary, tested" option that is listed . . . GUI video
seems to be working just fine, but somehow seems to be kicking up an
"error."

Hard to know if there are other "errors" that are also happening along with
this nvidia error, but this is the one that finally showed up in the
console . . . which didn't make any suggestions about how I could "fix" the
errors--just showed them.

F



>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Late to the party and playing with a diminished sense of humor

[Fritz Hudnut]

> Date: Wed, 03 Jul 2019 07:21:26 +0200
> From: Ralf Mardorf 
>
> Oops, in my previous mail it shouldn't read "Ralf wrote", ist should
> read
>
> On Tue, 2 Jul 2019 18:52:51 -0700, Fritz Hudnut wrote:
> > > Anyway, it's mildly irritating, sort of like the "hidden file on the
> > > desktop" thing, which does seem to have "gone away" . . . in
> > > 19.10 . . .
>
> My little contribution to sink into total chaos ;).
>

@Ralf:

Thanks for making those corrections, typos and all . . . which hopefully
will indeed stave off the forces of "total chaos" . . . that have recently
entered into the list.
When I get back to the Lu 19.10 partition I'll try to work through your
helpful suggestions and see if that finds anything . . . relevant to the
error window issue.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: the new mouse does not sweep clean in Lu 19.10?

[Fritz Hudnut]

 Walter, et al

In the interest of "science" . . . today I couldn't make my "which distro
> is this morning's distro" decision fast enough, and the top listing is
> U-MATE 18.04 . . . today, the "system program problem" error window that
> doesn't show any "details" did not open after logging in to GUI . . . 
> We've all perhaps moved on to the next point of breakage?  I wanted to see
> if this issue was still happening in "ubuntu" or if it has now been
> upgraded/fixed . . . .  Since this thread wasn't exactly about all of the
> problems I was having, but trying to figure out if the "unidentified system
> problem" was indicating something "serious" or something temporary . . . at
> least in MATE it appears to have been "temporary."  If it continues to open
> when I get back to Lu 19.10 . . . I'll mention it.
>
>
>> So today, back in Lu 19.10, and logging into the GUI shows the "system
program problem" error window once again . . . I ran an update/upgrade in
Lu and then rebooted back into U-MATE for the comparison, which continued
to **not** show this same error window that it had a day or so back.  Ran
an update/upgrade there and then rebooted back into Lu 19.10 . . . and the
error window continues . . . without capacity for stating "the reasons for
this error" . . . ??

The Lu dmesg area shows the usual "can't find size, something else, the #7
signature not found" . . . and the "b43 module" stuff . . . I believe that
all applies to the ubuntu as well, but in the case of the "#7 signature not
found" . . . that is a Gecko partition in another drive, so I don't know
why that would "throw an error" in Lu . . .???

Anyway, it's mildly irritating, sort of like the "hidden file on the
desktop" thing, which does seem to have "gone away" . . . in 19.10 . . .
but, now there is the "error" window . . . which other than that, things
seem to be "working" properly . . . is there actually "an error" or is it a
"false positive"???

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] which personality disorder would say it best?

[Fritz Hudnut]

@Ralf:


> On Mon, 1 Jul 2019 07:48:39 -0700, Fritz Hudnut wrote:
> >it might be akin to a "multiple personality disorder.
>
> No, it's not nearly similar! Keep in mind that you are controlling the
> operating systems and that the operating systems not randomly switch
> from one to another during usage.
>
> There is one possible exception, that is similar to such a human
> disorder. A boot manager could boot into the root directory of one
> install, while booting the kernel of another install. This might cause
> no {,noticeable} issue at all or could be catastrophic.
>
> My apologies for the unusual term, "boot manager", it should read
> "bootloader".
>
> My apologies for the bashism, but hey, it's the default login shell for
> almost all Linux distros.
>

 Point taken on the "it's not multiple personality disorder," it may or may
not be an interaction of the various "personalities" involved, unless we
were checking which kernel was driving which system . . . it's hard to
"rule out" as one of the personalities may have been over-riding the other
personalities, and perhaps causing a Munchhausen situation.  But, since it
was more like the machine was "unresponsive" to key stroke and would only
boot into one system, then perhaps that was more like "Dissociative
Disorder"  ??  Or, maybe just "Cognitive Dissonance Disorder" . . . unable
to make clear cognition due to System Dissonance Signals interfering in
bootloader decision-making???  So many options that could have been
involved, maybe it was MPD-like syndrome, rather than full blown "Disorder"
. . . .

F


> 
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Error: "system program problem" --ubuntu-users

[Fritz Hudnut]

 @Ralf:

If I google for 'grub chainloading osx on apfs' the second hit is
> related to a broken os-prober and seemingly efi is involved. However,
> it's about another issue, at least hfs+ is used.
>
> For a bootloader related request - especially since OSX is
> involved - consider to join
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users .
>
> On Ubuntu users there might be some OSX users subscribed who don't join
> the Lubuntu mailing list.
>

Thanks for playing through, I'll check into it if this issue continues or
returns intermittently . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

@Walter:

"Then don't be too surprised. When you're working on the development
version, it's expected there will be some amount of breakage, no matter
how much folks try to avoid it."

I have experienced a certain amount of "breakage" over the years,
particularly when there was a "PPC" distro; this last bit of "breakage,"
which now seems to be taking a break . . . appeared to be "systemic" across
the machine, and not just in one distro . . . and hard to know which distro
might have been "involved" as a few of them are "rolling" and each of them
seems to have a different kernel.  The Lubuntu 19.04 was the last actual
install, then upgraded to 19.10, but I have upgraded via Terminal, most of
them . . . and there was a week or so back the problem with a Leap 15.1
kernel, that did "do some breakage" . . . a few days later a new kernel was
released . . . a little hard to be "scientific" with so many players
playing through the same machine . . . it might be akin to a "multiple
personality disorder."

On Sun, Jun 30, 2019 at 8:17 PM Walter Lapchynski  wrote:

> On Sun, Jun 30, 2019 at 07:35:43PM -0700, Fritz Hudnut wrote:
> > but, if I just reboot the
> > computer w/o alt/option key, then an OSX command line looking "dmesg" of
> a
> > few lines of "bash" script shows up mentioning "APFS" several times
>
> This is the part that worries me. It sounds like you're not sure how it
> got that way. As this is not necessarily a simple thing to do (Ralf did
> a good job of demonstraing that), I'm concerned about how easy it will
> be to troubleshoot this when it doesn't work. I urge you to see if you
> can't figure out the details as that will certainly help people help
> you.
>

Well, indeed, when running so many distros and installs it is hard to "know
everything/all of the time" . . . this machine is an "experiment" . . . as
far as running a number of installs in the machine, not via virtual . . .
but from what of the Siduction guys posted, I'm not really pushing the
envelope too much . . . compared to some multi-booters.  I did this OSX and
linux thing on all of my computers over the last 12 years or so, in the
same way of using Yaboot or Grub . . . but the APFS format is a new one,
this appears to be similar to if I booted into single user with one install
of OSX 10.14, they run some bash script at the beginning that mentions "UC
Berkeley" or something like that . . . .  I don't know if that is put on
the "mobo" when the install is run, or into its own EFI partition, but, it
shows up for a few seconds and then Grub appears . . . now once again
functioning, seeming to be OK.

In the interest of "science" . . . today I couldn't make my "which distro
is this morning's distro" decision fast enough, and the top listing is
U-MATE 18.04 . . . today, the "system program problem" error window that
doesn't show any "details" did not open after logging in to GUI . . . 
We've all perhaps moved on to the next point of breakage?  I wanted to see
if this issue was still happening in "ubuntu" or if it has now been
upgraded/fixed . . . .  Since this thread wasn't exactly about all of the
problems I was having, but trying to figure out if the "unidentified system
problem" was indicating something "serious" or something temporary . . . at
least in MATE it appears to have been "temporary."  If it continues to open
when I get back to Lu 19.10 . . . I'll mention it.

Thanks for the conversation on it.

F

>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

@Walter:

Yes, this system was upgraded via console to 19.10 . . . but the same error
window shows up in U-MATE 18.04 as well.

On Sun, Jun 30, 2019 at 7:27 PM Walter Lapchynski  wrote:

> On Sun, Jun 30, 2019 at 01:15:57PM -0700, Fritz Hudnut wrote:
> > _usr_sbin_update-apt-xapian-index.0.crash
>
> I know on 19.10, this has been [misbehaving][1], but that's not the
> version you're on, is it?
>
> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931133
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

On Sun, Jun 30, 2019 at 7:18 PM Walter Lapchynski  wrote:

> On Sun, Jun 30, 2019 at 09:48:43AM -0700, Fritz Hudnut wrote:
> > "Death is inevitable, suffering is not . . ."  but, um, SSD is less than
> a
> > year old, shouldn't quite be "dying" just yet . . . one would "hope."
>
> You would expect… but I've had failures in less than a year.
>

OK, remains to be seen . . . if it had continued to not boot then it would
be "clear" there is a problem . . . but, so far I've now been able to boot
it, and then the disk showed up in the other two OSX DU . . . .

>
> > there is an "APFS" "dmesg" section that runs
> > **before** the Grub window loads, and it's hard to know if that has
> > interfered with the Grub menu, or not.
>
> I'm afraid to even ask how you have this thing set up. What is this
> other thing running before GRUB?
>

I'm afraid to think about it as well . . . but, if I just reboot the
computer w/o alt/option key, then an OSX command line looking "dmesg" of a
few lines of "bash" script shows up mentioning "APFS" several times, the it
shows a "Welcome to Grub" . . . and then the list of operating systems.
The 10.14 system was installed with only that drive plugged in, so that
wouldn't mess with the linux installs . . . and generally the linux
installs are done after the OSX installs on the same drive.

>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

@Walter:



>
>>
>> The contents of /var/crash can get wiped (this is normal, actually; it's
>> abnormal when you have things sitting in there), so I'm not too
>> surprised the original disappeared, but you should have this copy, no?
>>
>
> I have the name of the file that was "ls" -ted, but not the contents of
> that file, which didn't seem to show up, or I didn't know how to get it to
> show up.
>

This is a "copy/paste" from the Terminal . . . which I tried to "open" from
the Terminal, but Terminal "refused"

"

/var/crash$ ls

_usr_sbin_update-apt-xapian-index.0.crash


But this file didn’t “show” up in navigate to that directory . . ."
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

@Walter:



> > > Um, so you're saying that the problem is solved? Strangest story ever.
> > Right.  It "appears" to be "solved" . . . for now, but yep, you could say
> > that "'strange' is my middle name" . . .
>
> Well, good. Can I quote you on that, by the way? XD
>

Sure, quote away . . . .


>
> The contents of /var/crash can get wiped (this is normal, actually; it's
> abnormal when you have things sitting in there), so I'm not too
> surprised the original disappeared, but you should have this copy, no?
>

I have the name of the file that was "ls" -ted, but not the contents of
that file, which didn't seem to show up, or I didn't know how to get it to
show up.

>
> > there are some "issues" that go along with running
> > multi-boot systems
>
> Yes, this! I totally caution people against them.
>

Me too . . . don't do it . . . it's a terrible affliction . . . .

>
> > "inode_val:
> > object (oid 0x2b644e): invalid internal flags . . . "  errors
>
> An inode refers to the filesystem. Maybe your disk is dying? Weird
> problems are often caused by hardware failures. Software— algorithms—
> are predictable. Faulty circuitry is not.
>

"Death is inevitable, suffering is not . . ."  but, um, SSD is less than a
year old, shouldn't quite be "dying" just yet . . . one would "hope."

>
> > that disk's partition is
> > formatted as APFS, and that is a new format that Apple is using
>
> Are you sure GRUB supports this? They certainly don't list it in the
> [filesystem section][1] of their manual.
>

No, I don't think Grub supports APFS, question is whether Apple does . . .
possibly Grub does support +HFS, but I haven't taken the time to set up
Grub so it will boot the OSX options, I just use Grub to get into the linux
side of things . . . but, there is an "APFS" "dmesg" section that runs
**before** the Grub window loads, and it's hard to know if that has
interfered with the Grub menu, or not.  Historically the OSX side has not
been "friendly" to the linux side, breaking Grub links willy-nilly when
running an upgrade . . . any of that could be causing problems in "the
system" . . . ?  The APFS formatting might be overwhelming the other
formats??

Later today, I'll try to get back to the Lu system and find the name of the
"crash" file . . . but, main reason for posting here was that these "system
program problem" error windows that open, don't provide any way of seeing
the details, as traditionally they have, there used to be an arrow for a
drop down menu that would "show details" . . . now it's just "report?" or
"cancel" as the two choices, without knowing what it is we are reporting .
. . ???


> [1]:
>
> https://www.gnu.org/software/grub/manual/grub/html_node/Internationalisation.html#Filesystems
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

@Walter:

On Sat, Jun 29, 2019 at 3:29 PM Walter Lapchynski  wrote:

> On Sat, Jun 29, 2019 at 10:54:25AM -0700, Fritz Hudnut wrote:
> > "the new
> > mouse sweeps clean" . . . ???
>
> Um, so you're saying that the problem is solved? Strangest story ever.
>

Right.  It "appears" to be "solved" . . . for now, but yep, you could say
that "'strange' is my middle name" . . .

>
> > I do believe that the "system error" window in both Ubuntu systems
> > pre-dates the new mouse chapter
>
> Did you ever look in /var/crash? There are some odd things in the logs
> you posted up that *could* create a problem, but unknown.
>

I did try to look in /var/crash in Lubuntu Terminal, wasn't exactly sure
how to do it properly, so I ended up doing "cd /var/crash" and then "ls" ??
and it did show one file listed which I pasted the data into a document
that is now in the Lubuntu Documents directory, but I'm over in OSX . . .
while it lasts . . . .  But, when I "navigated" over to the /var/crash
directory in the GUI . . . nothing was in there

But, yeah, I wouldn't have a problem hearing that there are "odd things" in
the logs . . . there are some "issues" that go along with running
multi-boot systems . . . even the UUID for the swap is something that I
haven't "drilled down" on, so that might send up some errors.  Or, I think
there is the "PCKS#7 signature error" ??? that got kicked up because I
wasn't able to get to an OpenSUSE Gecko Rolling partition in the recent
round of problems for a few weeks and that seemed to show a "signature key
doesn't match" problem when running a zypper upgrade, but all I have to do
is "move forward" by clicking yes and the upgrade runs through . . . still
shows as a dmesg error in a number of OSs . . . .

Also, when I did get around to running a DU "first aid" on the OSX 10.14.5
partition that I had this morning logged into, it showed some "inode_val:
object (oid 0x2b644e): invalid internal flags . . . "  errors, for a number
of lines, before checking out as "OK" . . . .  So, that disk's partition is
formatted as APFS, and that is a new format that Apple is using, so I don't
know if it got "damaged" somewhere along the line, or that is "normal" . .
. but a few days back as the only disk plugged in the computer didn't "see"
it, and didn't boot up . . . but, now with the new mouse, same brand as the
previous one : - ))  the OSX side of things is bacckk!!  And likely I
can use it to pick one of three "EFI Boot" disks that will open various
iterations of the Grub file, and give me some linux options??  Haven't
checked that one out yet to know for sure if one of them gives me a "clean"
Grub that will boot all of the linux options or, only Lu 19.10.

Thanks for taking a look at those logs though . . .

F

> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?

[Fritz Hudnut]

@et al:

So . . . new day . . . booted up the computer w/o key modifier and Grub
loaded, but provided no function to select OS, so we went into Lu 19.10 . .
. got the "system program problem" error once again . . . cancelled out of
it.  Ran update/upgrade . . . "nothing to do" . . . checked social media .
. . then after an hour of running I thought I'd try to "leave" Lu by way of
"restart" . . . and this time I held the alt/option key down . . . and, lo and
behold, the OSX bootloader window opened! which hasn't happened in some
days . . . .

OSX 10.14 showed as an option, which previously as mentioned, would not
boot at all and didn't appear to be "there" . . . so I picked it and, it
booted . . . .

When it loaded there was a System Preferences window saying "Keyboard is
not recognized" and it provided a GUI window to "press a key" for it to
"recognize the keyboard" . . . which seemed to hang . . . and do nothing.
I decided to restart with alt key and again OSX bootloader opened and I
picked another OSX option and in we went . . . same SP window opened with
the "keyboard not recognized" . . . but this time it said, "If there is
another USB device connected to the keyboard you can ignore this message" .
. . but I hit the "Z" key anyway, and again . . . it "tried to recognize
the keyboard" . . . but failed.

So, possibly it was the fact that a day or so back I got a new mouse, and
somehow having to "recognize" the mouse by way of the keyboard did
something that caused the keyboard to "work" . . . and, we are at least
back into OSX options . . . and/or Lubuntu if I just restart the computer
w/o alt key selected . . . giving credence to the old adage . . . "the new
mouse sweeps clean" . . . ???

I do believe that the "system error" window in both Ubuntu systems
pre-dates the new mouse chapter . . . but, that is the latest, thanks for
the kind attention.

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . report now?

[Fritz Hudnut]

@Walter:

Why don't you pastebin up /var/log/syslog and dmesg?
>>
>
 https://paste.ubuntu.com/p/VcWX5Vh8gt/
https://paste.ubuntu.com/p/rVR4msj2qb/

I was able to boot into U-MATE this morning and I looked through the dmesg
stuff there, but on reboot I couldn't scroll through the grub list so the
default boot went to Lubuntu . . . both of the dmesg show an "error"
because I didn't install the b43 module for wifi connectivity . . . which I
don't need because I use ethernet in this computer . . . so would that
"error" show up as the "system program problem" that is showing up in both
the U-MATE & Lubuntu systems?  Or, there would be another problem?

Only a few days back I could revive the ubuntu installs from suspend with a
key stroke or mouse click, but, now I have to use the power button . . . .

I looked at lsblk and it does show the three internal drives and the
partitions in them, but the first one is an SSD and it only is partitioned
for OSX 10.14 . . . formatted as APFS . . . and no data is showing up in
Gparted in that drive, so I don't know if Gparted just doesn't recognize
APFS . . . but, when that drive was the only one plugged in, nothing would
boot at all . . . .  So possibly there is nothing in there, or the EFI
partition was "tweaked" possibly by the Siduction upgrade situation awhile
back and it slowly choked off the life energy in the OSX install??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Error: "system program problem" . . . report now?

[Fritz Hudnut]

@Walter:

Thanks for the fast reply, I'm away from that computer for the next few
hours . . .


Anything in /var/crash? Did you try reporting?
>

I did look at some logs I think when I was able to get into Leap . . . but
for sure I didn't look at /var/crash . . . but I have clicked "send report"
numerous times when I was logging into Lu & U-MATE . . . .

>
> > The dsmeg?? window
>
> Why don't you pastebin up /var/log/syslog and dmesg?
>

I'll look into this, likely tomorrow . . . I have done the "pastebin"
process, but it has been awhile . . . can't remember if I have "apport"
re-installed in Lu 19.10 yet.

>
>
> Can you get to GRUB at all?
>
A "grub" list appears, but it is essentially now set for Lu eoan, so I
can't scroll/arrow through the list, although this am I just booted the
unit and I was able to use Grub as "normal" . . . but on several reboots
after that, using alt/option, not using it . . . Grub is "stuck" . . . and
couldn't use the "e" key or "tab" . . . .

>
>
>
>
> Is one of the OS X options removed or all of them? What does `lsblk`
> tell you?
>
Seems like one of them has been "wiped" . . . but two or three versions
show as "having data" in gparted . . . but, when I pulled all of the drives
were pulled out I was able to boot into an OSX installer flash drive, got
the Disk Utility, then slid the SSD drive with the now "vanished" OSX
system, to try to "repair disk" but, it wouldn't show up . . . and then
further problems when I tried to run an install into that disk . . .

I'll try to run "lsblk" later and report back.

F

>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Error: "system program problem" . . . report now?

[Fritz Hudnut]

Folks:

Been having some "problems" in my multi-boot set up running a few different
versions of OSX with a few versions of linux . . . grub seems to have lost
the ability to select from among the choices in spite of running
"update-grub" a number of times . . . .

But, in both of the ubuntu systems I have recently re-installed, Lubuntu
19.10 and U-MATE 18.04 . . . when logging in I get an error saying "system
program problem" . . . "report now" or "cancel" . . . but it doesn't offer
a "show details" drop down arrow to take a look at . . . the details.

Running synaptic "fix dependencies" . . . it appears to "do something" but
it doesn't show any details . . . running "-f install" . . . also doesn't
appear to show anything.

The dsmeg?? window seems to show "initramfs unpacking failed" . . . but,
then it will load the GUI . . . right now I can only get into Lubuntu . . .
.

A week or so back I had some issues in Leap 15.1 where a kernel update
seemed to "break" nouveau and caused problems with grub, which I got help
to add "nomodeset" into the grub listing for Leap . . . and then I added
nvidia drivers . . . seemed to help over there, but, now seemingly there is
again an issue in ubuntu?  But, now I can't scroll through grub to get to
other options or back to Leap to see if somehow "nomodeset" is causing
conflict across the system . . . .

The OSX options will not show up, and seemingly one of them has been
wiped?  Anyway, this question is to find out if there is a way to "see"
what the "system program problem" might be?  The GUI error window isn't
providing that data, whereas it seemed like in the past error windows would
show some details to "give a clue"??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 19.10 installer . . . errors!! second time . . . .

[Fritz Hudnut]

@Walter:

Thanks for the update, glad to hear you got a fix pushed through, it was
kind of a "nasty" one . . . .  I had a few spare moments today, but not
enough time to mess with the download and re-install of 19.10;  so I
"adjusted" my /etc/apt/sources.list  to include the word "eoan" in various
places, I dropped into a tty and and then ran update/upgrade . . . showed
538 MB of packages to make the system into "eoan" . . . and a few minutes
later I rebooted into . . . "eoan" "19.04" . . . .

Seems to be pretty "zippy" in the Terminal . . . "revives" seemingly
consistently from suspend . . . .  I'll test on with it and see if it turns
into "eoan 19.10" at some point.

On Thu, Jun 20, 2019 at 12:23 PM ∅  wrote:

> On Tue, Jun 18, 2019 at 10:54:32PM -0700, ∅ wrote:
> > [1]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829805
>
> Our fix for the kernel panic bug is now uploaded. I rebuilt the ISO last
> night and confirmed it was working so this issue is officially resolved.
> Huzzah!
>
> --
>@wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 19.04 installer . . . no errors!! first time . . . .

[Fritz Hudnut]

et al:

Just to update, got the 19.04 live edition . . . used mkusb to create
startup flash drive . . . this am ran the install, basically repeating the
steps I did for 19.10 . . . only difference in this install the installer
asked me to flag the EFI partition as "esp" . . . which I did.  A few
minutes later install was "done."

This time I shut down rather than reboot . . . and on cold boot (not
holding alt/option) Lubuntu loaded and we were logging in . . . .

Ran an update/upgrade . . . ran "update-grub" which it had already done . .
. sync'd into Firefox . . . in a few minutes I'll be shutting it down for a
number of hours . . . we'll see how things go on cold boot . . . .  But, in
contrast to 19.10 "failure" . . . 19.04 install went well.

Possibly the 19.10 issues might relate to a problem I had over in Leap 15.1
where the recent kernel would not work with nouveau and/or nvidia card . .
. which I have, and could be that 19.04 represents a "falling back" in
kernels . . . and therefore it works in 19.04 . . . ???

O well, hind sight is 100% . . . supposedly a newer kernel is coming out in
a few days . . . perhaps I'll try to upgrade via console or GUI to 19.10
and see how that goes then??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] Lubuntu 19.10 installer . . . errors!! second time . . . .

[Fritz Hudnut]

Folks:

Problem I think is "confirmed" . . . waited until the "6/15" daily showed
up on the server, zsync'd it to the latest version, the old one was "91%"
the same as the new one.  Rather than re-using the U-MATE startup creator
app, I added "mkusb" to the sources.list and installed that . . . wiped the
flash drive . . . and moved the new version of 19.10 over and booted it up
. . . .

Desktop loaded fine and I set the time & location and then ran the install
. . . the only thing I did differently this time besides setting the
partition for "/boot/efi" . . . was to flag it as "bios_grub" . . . and the
install went fast (possibly too fast) . . . seemed like in 5 minutes it was
again declaring itself "done."

I rebooted and just as yesterday it loaded the OSX 10.14 dmesg window . . .
and then "froze" there.  Used the power button to shut down and rebooted
with the alt/option key, got to the OSX Bootloader window and picked the
first disk listing "EFI Partition" . . . which as yesterday I figured was
for the "last installed" system . . . and the Grub window did load . . .
and this time I was able to arrow down through the list to the "Lu 19.10"
option . . . a line of "error -- disk 'hd2, gpt6' not found"  lines loaded
followed by "hit any key to continue" . . . which after a couple seconds it
auto-loaded the Grub list again, and I scrolled down to the "Lu Recovery"
option . . . which brought the same errors . . . .  So, again, seems like
something in the install didn't go well, whereas I seemed to get the U-MATE
18.04 system installed and booted up just fine in the same drive . . . .

I think I'm done with Lu 19.10 for a bit . . . if anyone wants to check
this out, and file an appropriate bug report I would be happy to report
this on the QA.  I've had problems finding the "correct" place to file the
bug report . . . against . . . in the past, traditionally the QA won't
accept "negative" comments w/o a bug report, and the bug report people
don't like being flagged on plays that aren't in their area.  And, system
won't boot to file an "apport-collect" . . . report.

I might try to make my way back to Lu 19.04 . . . in a few days??  See how
that goes, I did have that system running before the recent disaster . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

[lubuntu-users] Lubuntu 19.10 installer . . . errors??

[Fritz Hudnut]

Folks:

A few weeks ago I had a "sid" system problem that seemed to spread damage
across the two drives that I had linux distros installed on . . . so I had
to nuke the drive that I had U-MATE &7 Lubuntu 19.04 installed on . . . and
I've been working my way back to Lu babe . . .: -)

So after I ran the install of U 18.04 I looked around for a daily on Lu
19.04, and I saw that we are now up to 19.10 . . . so I went for that and
transferred it to a flash drive.  Booted the system and the GUI loaded fine
. . . might have opened one app, then went for the install, using "custom"
. . . and all seemed to go well, the installer proudly announced that it
was "done" after a few minutes.  I followed the instructions to "remove the
install media and hit return" for reboot . . . and it rebooted and it did
go to "grub" . . . but it first shows the ?? dmesg?? data for OSX 10.14 . .
. which **usually** then drops into the Grub window . . . but this
"froze."  I shut the unit down and went for a bike ride.

When I got back I again tried a few attempts to get into Lu 19.10 via grub,
but, it failed, and then after one attempt it showed the words "kernel
panic" . . . which I assume to mean that there was a . . . kernel panic???

I got back to U-MATE and ran "sudo update-grub" . . . and it showed the
various options and it did find the "Lu 19.10 Eon Ermine"??? option, but
then I couldn't arrow down through the list, only the top hit, last system
standing is the U-MATE, and that does boot up and I'm typing this post in a
MATE system . . . .

So, point is, that something in the Lu 19.10 installer didn't seem to find
the EFI boot partition??  Or, did something "wrong" . . . looking at
GParted in MATE shows "5+GB" "used" in the partition I set for the "/" . .
. but something is causing a "kernel panic" . . . which isn't letting me
get to the Lu system . . . even though now Grub has "found" it . . . but,
now Grub seems to be "frozen" via the latest installs of ubuntu based
systems.

I think I could get over to the "sid" system via its Grub list, but that is
in another drive than the one where the ubuntu options are located . . .
might be that the Lu 19.10 partition might have to be wiped and
re-re-installed in a few days??

F

I was able to get to a Grub window
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] The ending of various technological "waves"

[Fritz Hudnut]

That could very well happen.
>
> But of course, those perfectly-useful machines could eventually die a
> 'natural computer death', as well, rather than being junked because there
> is no modern OS to run on them.
>
> So far though, they are working well, and going strong, accomplishing
> useful tasks for me.
>
> It may surprise a lot of people to hear that the slower machines are
> actually more valuable to me, because they allow me to test if my software
> really does work on 'older, slower machines', as I claim on my website.
>
> Strangely, my 32-bit MacBook seems to have a better display than my later
> 64-bit MacBook.  And with Linux, it makes a perfectly good musical
> instrument for performances.
>
> --
> Sincerely,
> Aere
>
>
@Aere:

Possibly the 32-bit MacBook might have an Nvidia graphics card, which
generally seems to bring a crisper display than the Radeon options . . . .
Apple seems to "mix n match" the hardware in different platforms, so to
make it seem competitive with PC choices?

And, right, "the wish for a natural death" scenario, rather than "induced
death due to lack of support" . . . I've tried to keep my old PPC machines
going, unnaturally adding parts to revive them from zombie state . . . but,
the pull of the technological wave seems to keep sending them back . . .
and then the new parts don't have the right connectors . . . making it
difficult to sustain "life" . . . .

It's somewhat like "newer, fresher horsies" are the "better" choice in the
cost/benefit ratio of time management theory . . . ??

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Re: [lubuntu-users] The ending of various technological "waves"

[Fritz Hudnut]

Hi,

On Sun, 2 Jun 2019 at 01:28, Aere Greenway 
wrote:
> Thanks for the information.  I will do that if 32-bit is still not
> available in Lubuntu 20.04.
>
Debian is my plan B for my 32-bit netbook :)
BW,

Ian

@Aere && Ian:

I have a "Siduction" install in one of my linux partitions, which is a
"sid" based system stacked on Debian 10, not a bad system but the GUI isn't
as worked out as the Lu 19 GUI, and I think it is 64 bit . . . .  Still,
likely at some point Debian will do with 32 bit what it did with PPC???
Hard to say for sure . . . .

F
-- 
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users