Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?
On Mon, 1 Jul 2019 20:49:33 +0200, Ralf Mardorf wrote:
>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.
--
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?
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.
--
pacman -Q linux{,-rt{-cornflower,,-pussytoes,-securityink}}|cut -d\ -f2
5.1.15.arch1-1
5.0.21_rt14-0
5.0.19_rt11-1
5.0.14_rt9-0
4.19.50_rt22-0
--
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?
@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?
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. -- 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?
On Sun, Jun 30, 2019 at 07:36:55PM -0700, Fritz Hudnut wrote: > Yes, this system was upgraded via console to 19.10 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. > . . . but the same error > window shows up in U-MATE 18.04 as well. Probably unrelated, though it may be a similar issue. I'm not sure for issues very well-known to the Ubuntu Error Tracker behave like you'd expect with the "Show Details" button. -- @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?
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. -- @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?
@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?
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?
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?
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. > 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? -- @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?
@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?
@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?
On Sat, 29 Jun 2019 22:50:10 -0700, Walter Lapchynski wrote: >On Sat, Jun 29, 2019 at 04:00:55PM -0700, Fritz Hudnut wrote: >> there are some "issues" that go along with running >> multi-boot systems > >Yes, this! I totally caution people against them. Hi, there are absolutely no issues related to multi-boot machines [1]. In the past I have used grub legacy as well as grub 2, with a hand written menu.lst or grub.cfg, even with chainloading FreeBSD or Windows, too. Just turn off that automations that write grub configurations, that are as messy as the emails of the OP send to this mailing list. To write readable emails I recommend to use a decent MUA. To get rid of messy grub configurations, disable the automation, in a way that they even can't come back by accident (e.g. during an upgrade or release upgrade). I wrote a script to do that, since updating the configuration is time consuming and gains nothing. I'm using syslinux anyway, but it's easier to keep an unused grub, due to dependencies enforced by Ubuntu and since working around the bootloader dependencies comes with pitfalls. See [2] for how to use dpkg-divert. [1] [rocketmouse@archlinux ~]$ cat /boot/syslinux/syslinux.cfg # http://syslinux.zytor.com/wiki/index.php/Doc/menu 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 ^H ^i ^K ^M ^n ^o ^P ^Q ^R ^S ^t ^V ^y DEFAULT Cornflower 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_nopti MENU LABEL Arch Linux threadirqs ^nopti LINUX ../vmlinuz-linux APPEND root=LABEL=s3.archlinux ro threadirqs nopti 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 # https://lists.ubuntu.com/archives/ubuntu-users/2018-November/295925.html LABEL Securityink_no_micro MENU LABEL Arch Linux Rt Securityink no micro LINUX ../vmlinuz-linux-rt-securityink APPEND root=LABEL=s3.archlinux ro INITRD ../initramfs-linux-rt-securityink.img # https://lists.archlinux.org/pipermail/arch-proaudio/2018-February/78.html LABEL Securityink_nopti MENU LABEL Arch Linux Rt Securityink nopt^i LINUX ../vmlinuz-linux-rt-securityink APPEND root=LABEL=s3.archlinux ro nopti 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_nopti MENU LABEL Arch Linux Rt Puss^ytoes nopti LINUX ../vmlinuz-linux-rt-pussytoes APPEND root=LABEL=s3.archlinux ro nopti 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_nopti MENU LABEL Arch Linux Rt Corn^flower nopti LINUX ../vmlinuz-linux-rt-cornflower APPEND root=LABEL=s3.archlinux ro nopti 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_nopti MENU LABEL Arch Linux Rt n^opti LINUX ../vmlinuz-linux-rt APPEND root=LABEL=s3.archlinux ro nopti INITRD ../intel-ucode.img,../initramfs-linux-rt.img LABEL Arch MENU LABEL ^Arch Linux LINUX ../vmlinuz-linux APPEND root=LABEL=s3.archlinux ro INITRD ../intel-ucode.img,../initramfs-linux.img MENU SEPARATOR MENU SEPARATOR LABEL Other Menu MENU LABEL Other Linux MENU DISABLE MENU SEPARATOR LABEL Moonstudio MENU LABEL Ubuntu X ^Moon Studio lowlatency LINUX
Re: [lubuntu-users] Error: "system program problem" . . . the new mouse sweeps clean?
On Sat, Jun 29, 2019 at 04:00:55PM -0700, Fritz Hudnut wrote: > 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: > > 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 > > 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 pasted the data into a document > that is now in the Lubuntu Documents directory 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? > there are some "issues" that go along with running > multi-boot systems Yes, this! I totally caution people against them. > "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. > 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. [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?
@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?
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. > 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. -- @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?
@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
