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 /.boo
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?
@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?
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?
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?
@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 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?
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?
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
