Jump to content

Hedon James

Members
  • Content Count

    938
  • Joined

  • Last visited

Community Reputation

824 Excellent

About Hedon James

  • Rank
    Topic Cop

Profile Information

  • Gender
    Male
  • Location
    Pennsylvania, USA
  • Interests
    Real Estate, Linux, Android, guitars, rock music, & recording

Previous Fields

  • Main System Specs:
    Ubuntu 14.04.2 LTS on a home-brewed system
  • Secondary System Specs:
    Ubuntu Studio 12.04.3 & Pangaea-Lubuntu (a personally remixed Lubuntu 14.04)
  • Other System(s) Specs:
    I only run LTS versions on hardware; in-between releases are just BETA versions of LTS systems! ;-)

Recent Profile Visitors

148 profile views
  1. Install a sticky note program and place a sticky note directly on your desktop, in the most visible place on your desktop, and call the note "REMASTER FOR PERSISTENCE!" LOL!
  2. hmmmm....hadn't considered the VBox angle. another +1 in the potential culprit list. I think I need to start looking into kvm & virt-manager. I note that Debian 10 (Buster) does NOT support VB, has no plans to support, and the Debian Wiki recommends kvm & virt-manager as the alternative. That would certainly isolate/eliminate VB as a culprit. Thanks for the thoughts!
  3. After about a year, I've just now experienced my first problem with Siduction LXQT in a VM. Looking back, it probably started about 2 months ago, during a dist-upgrade with a new kernel. I always check the "warnings" in Siduction forum before update/upgrade and wait until "resolved" shows up. But after a dist-upgrade and re-booting to the DM (SDDM), I have weird blinking "artefacts" where the username & password fields should be. Switching to TTYs does nothing...she's locked up...the only way out is to shut down VirtualBox and startup again. After some trial & error, I realize that my prior kernel boots fine, so it's probably a graphics driver in the new kernel that'll get patched or fixed in the next version, right? Nope... Each subsequent dist-upgrade with a new kernel displays the same issues during what SHOULD be a SDDM login. But I keep booting with the old "good" kernel (I think it was 4.20.x?) and I'm back in business...until yesterday. The most recent dist-upgrade provided new kernel 5.3.0 and a whole host of LXQT upgrades; although nothing appears to be xserver or xorg related, nor sddm related (although sddm is a QT software, so there's that). Now, I can no longer boot with my previously good "old" kernel, nor any of my more recent kernels; but at least the "old" kernel will drop me into a TTY1 shell if I ctr-alt-f1. From there, I run the dist-upgrade sequence again, thinking I've got a partial install or broken package, but everything's up to date. So I'm back to scratching my head and stumble onto the revelation that the most recent kernel will boot to SDDM, where I can select a naked Openbox, Fluxbox, or PekWM session, as well as LXQT session. So I choose familiar old Fluxbox and voila....I'm in the desktop with a Fluxbox session. I can also switch on the fly to Openbox or PekWM, and back to Flux again. So I'm thinking the problem is the LXQT session, right? Here's where it gets REALLY interesting...if I open a terminal and enter lxqt-session & I now have a very familiar looking and perfectly functional LXQT desktop session. So maybe it's NOT the LXQT session, maybe its SDDM. But SDDM boots other sessions just fine. So now I'm not sure who to point the finger at. I did some forum cruising on Siduction and found a 2018 thread about SDDM starting very slow; so I'm thinking MAYBE that's my issue, disguised as blinking artefacts before final session launch. The resolution in that thread was to delete the ./Xauthority file, log out, and log back in without re-booting in order to recreate a fresh ./Xauthority file. Didn't work for me. Another suggestion was to replace SDDM (something about problems with "entropy") with LightDM. I don't want to go there yet, as I have Siduction in a VM to monitor it's long-term viability, and Siduction LXQT's preferred DM is SDDM...which seemed to be working fine until about 2 months ago. Potential culprits seem to include the kernel, SDDM, and LXQT itself; although it seems that I've ruled each one out, individually, which may suggest a 2-factor factor. But now I'm at a loss... Any ideas where to look next?
  4. What SB said is the path of least resistance. But if you want to continue for knowledge's sake, your terminal output indicates you're missing the dependencies libcurl3 and libcurl4, but only libcurl3 was installed with your -f option. not sure if libcurl3 and libcurl4 are "either, or" dependencies or if they're stacking dependencies, but you might want to try installing libcurl4 and see if it wants to remove libcurl3 and replace with libcurl4, or just install side-by-side, like python2 and python3 did for awhile. OR...you can create your own launcher icons by creating a *.desktop file. You can do this yourself, from scratch, by creating a blank text file and save it with the name "launcher.desktop", where launcher=name of the icon you're creating (In your case Opera.desktop) and by providing some basic information in the file that is needed to create a launcher, such as relative path to the executable file, path to the icon, menu categories, etc... Here's a quick tutorial on how to do that from scratch: https://www.maketecheasier.com/create-desktop-file-linux/ Alternatively, I often use a "shortcut" method where I copy a similar *.desktop file, contents and all, but change the relative information. In your case, I might suggest the following: - From ROOT file manager (open as root), navigate to usr/share/applications directory - find another web browser desktop icon (Firefox, Chrome?), right click, and "open" as text file, or open with text file editor (gedit, leafpad, mousepad, etc...) - save file with a different name, but ending in *.desktop, such as Opera.desktop - change "exec" line to the terminal command used to run the program - change "icon" line to the ABSOLUTE path of the icon you want displayed as the launcher (doesn't have to be Opera, although that's what I'd choose) - edit the "name" line for the application description displayed on "mouse over". Again, can be anything you want - optionally, I usually delete any additional lines that aren't in English (if you're multi-lingual, edit what you want to keep, delete the rest?!) - lastly, save these changes to file again, and exit the text editor Voila, you've created your own custom-icon launcher, which will show in menu under appropriate categories, and is available for desktop icon or launcher bar placement. Just like any other application launcher on your system!
  5. no problem. I haven't tried Anbox, but I did remember reading about it and filing that info away for future reference. the only other thought I'd have is to try ChromeOS in Virtualbox, rather than Android. I'll be watching this thread with interest to see what else I can learn. Good luck!
  6. Have you looked at Anbox? https://linuxconfig.org/how-to-install-anbox-and-run-android-apps-in-linux
  7. building on SBs suggestion, and assuming you CAN install newer version of Mint, I'd install with a separate /home partition; then mount the clonezilla backup and rsync his old home directory to his new /home partition. a lot of work, but probably save yourself future efforts in the long run.
  8. i figured as much....pick your poison. I love the idea of rolling release, but it seems impractical to keep a small network updated so frequently, and it's equally impractical to re-install a small network every 2+/- years. What do small companies do that run Linux as an OS? I've got to believe they've already solved this problem, while I'm still looking at options.
  9. I haven't had that experience with leading edge distros in VMs. Arch, Manjaro, Siduction, Sparky...all in VMs on my system and all running fairly smoothly, mostly without incident, for at least 1+ year. Perhaps the key, just like on the rails, is to keep updated in smaller monthly increments? Any issues I've had seemed to revolve around graphics, mostly, which supports your assertion that it's Oracle issues (i tend to agree). But usually if I reboot the VM and choose the original/former kernel, I'm back in business. At least that's been MY experience. I'll agree wholeheartedly with your comments regarding too many updates. Seems like I'm ALWAYS updating the mentioned VMs before I can do anything to tinker with them. Once again, you and I have very similar tastes and outlooks on our distros...we just conclude differently based on personal criteria. There doesn't seem to be a "happy medium" in linux land for me. I prefer the stability and familiarity of the "buntus LTS distros, but upgrading in place is always a white-knuckle affair of hoping that no new quirks appear in the machine; to the point of learning that re-installation is just the smarter way to go, but re-installing my entire highly-customized OS every 2+/- years is a huge PITA. Then factor in that I have a production desktop, laptop, old crappy "test bed" laptop, media server, studio computer, and a few other family members on similar release cycles and you can see how that turns into a bi-annual fiasco that I dread. That's what started my rolling release quest, so I never have to re-install again. But all those updates make it a challenge to keep all those machines sufficiently updated to maintain smooth operation. In a VM is one thing, but on the rails I think it will be just a matter of time before I brick one of them due to lack of timely updating. Just a thought... Is there such a thing as a rolling STABLE distro? Incremental updates, with NO re-installation ever? I can't find one out there, but I also don't know what I don't know! That's why I keep plugging distro ISOs into VMs...just trying to learn stuff. Maybe stuff I'll never need to know, or never use, but it's not like I'm paying much for that knowledge!
  10. LOL! I'm getting frustrated with 2 year LTS cycles in the 'buntus...appreciate the invitation but that'll be a hard pass on the Slacks!
  11. I must admit that the more I learn, the more interesting Arch becomes. You said that would happen...looks like you're right. I'm not there...yet...but I can see it on the horizon. Exploring Debian proper is my last item on the Debian family checklist. When I've finished scratching the Debian/apt itch, the Arch/pacman ecosystem will be on deck. But that's a whole 'nuther thread for a future day!
  12. sunrat, your presumption regarding livecd is correct. and I think your explanation regarding Calamares vs Debian Installer makes the most sense. Invoking Occam's Razer, I do believe your supposition connects the dots in the most concise way. I would also note that my installation follows a website article regarding the "correct" way to install Debian Testing, which was to install the most recent Stable I can get my hands on, completely update && upgrade it, then change the repos in etc/sources from buster/stable to testing. I added the contrib and non-free from another article I read. It makes sense to me that a livecd of Debian Stable would provide locales for everything they have a language/translation for. I have used the Calamares installer with Siduction before, but didn't have this issue....at least I didn't notice it. But Siduction isn't trying to hold anyone's hand for an installation either... FWIW, I've been trying to get "closer" to the "mother" distribution and see how packages in the "mother" may differ from "patched packages" in the progeny. I've learned that the 'Buntus are forked from Debian Testing and massaged into 'Buntu. I've read folks stating that Debian Testing and Sid are quite stable for them (despite the monikers), as long as you read the warnings and/or watch the apt messages before upgrading...and avoiding upgrades alltogether during times of heavy upheaval, like the monster QT package changes you mentioned. I was trying to upgrade before that hit Testing, hence the hurry... I feel like I'm "fighting" Debian to make it what I want. Their software policies on free vs non-free are a huge PITA. I understand their philosophy, and can agree with it fundamentally, but their implementation is too austere, IMO!
  13. Good stuff SB! duplicating your grep search shows my libreoffice packages as follows: jim@DebianTesting-VM:~$ sudo apt list --installed | grep libreoffice [sudo] password for jim: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libreoffice-avmedia-backend-gstreamer/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-base-core/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-base-drivers/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-base/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-calc/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-common/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-core/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-draw/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-gtk3/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-help-ca/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-common/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-cs/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-da/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-de/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-dz/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-el/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-en-gb/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-en-us/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-es/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-et/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-eu/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-fi/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-fr/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-gl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-hi/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-hu/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-it/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-ja/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-km/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-ko/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-nl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-pl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-pt/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-ru/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-sk/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-sl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-sv/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-zh-cn/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-help-zh-tw/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-impress/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-java-common/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ar/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ast/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-be/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-bg/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-bn/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-bs/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ca/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-cs/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-cy/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-da/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-de/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-dz/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-el/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-en-gb/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-en-za/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-eo/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-es/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-et/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-eu/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-fa/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-fi/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-fr/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ga/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-gl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-gu/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-he/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-hi/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-hr/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-hu/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-id/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-is/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-it/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ja/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ka/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-km/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ko/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-lt/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-lv/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-mk/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ml/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-mr/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-nb/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ne/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-nl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-nn/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-pa-in/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-pl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-pt-br/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-pt/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ro/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ru/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-si/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-sk/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-sl/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-sr/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-sv/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ta/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-te/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-th/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-tr/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-ug/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-uk/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-vi/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-xh/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-zh-cn/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-l10n-zh-tw/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-librelogo/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-math/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-nlpsolver/now 0.9+LibO6.1.5-3+deb10u4 all [installed,upgradable to: 0.9+LibO6.3.2-1] libreoffice-report-builder-bin/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-report-builder/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-script-provider-bsh/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-script-provider-js/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-script-provider-python/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-sdbc-firebird/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-sdbc-hsqldb/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-sdbc-postgresql/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice-style-colibre/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-style-tango/now 1:6.1.5-3+deb10u4 all [installed,upgradable to: 1:6.3.2-1] libreoffice-voikko/now 5.0-3 amd64 [installed,upgradable to: 5.0-3+b1] libreoffice-wiki-publisher/now 1.2.0+LibO6.1.5-3+deb10u4 all [installed,upgradable to: 1.2.0+LibO6.3.2-1] libreoffice-writer/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] libreoffice/now 1:6.1.5-3+deb10u4 amd64 [installed,upgradable to: 1:6.3.2-1+b1] Scrolling the entire list of upgradeable packages on my VM, it seems the entire "group" of irrelevant packages are contained entirely within hunspell* (dictionary or spellcheck?), libreoffice (specifically help-* and l10n-* packages) , and task-*-desktop packages. I feel like this confirms my thoughts of "locale" or "language pack" issues, but I've already reconfigured the locale (as discussed above) and removed language packs. Not sure where to look next, as everything I find seems to suggest to reconfigure locale and remove language packs. Since that didn't work, I'm now guessing it's a lower level issue. Any additional thoughts welcome...
  14. @SB I'm agree those packages are already installed. But I can't figure out HOW or WHY that happened. This is a brand new installation in VM, using the included Calamares installer, which I have seen and used many times before. I'm guessing Debian includes all those by default. But it seems stupid to me to keep those packages, and subsequently upgrade those packages, when all I want/need is US English. This is my first go-round with the mothership of pure Debian, so no baseline of what IS and ISN'T "normal" behavior. @sunrat after using apt autoremove and a subsequent reboot, there is no change in the packages to be upgraded. See comments to SB above. I feel like I'm looking in the right area to address this problem, but haven't hit the bullseye yet (no pun intended). Any idea how to get rid of slovenian, ukrainian, and other irrelevant "tasks" and "desktop" packages? I had better success with your tip on Kvantum. I couldn't find Kvantum using CLI apt search, but located the packages using Synaptic. Turns out that 'Buntu syntax of apt search cache packagename is incorrect for Debian. Debian Wiki indicates correct syntax for Debian package search is apt search packagename Using the correct syntax, I found the four (4) packages you referenced! THANKS! I also agree (mostly) with your comments regarding Sid and Testing. I've had Siduction LXQT and Sparky LXQT in VMs for quite some time, and Siduction has required less intervention on my part. I'm just trying to run Debian Testing in a VM as an exercise in additional learnings and trying to compare the difference(s) between Debian Testing and the somewhat curated Sparky repo experiences. I do like the fact that Sparky isn't so stringent about non-free software in its repo. For instance, I use MasterPDF Editor a LOT in my daily workflow...it's my "go to" PDF viewer. Sparky shows a version available in its APTus software offering (although I haven't been able to install it, as APTus is hit & miss for me....I tend to stick to command line, with Synaptic as a backup), while Debian says "no way, it's non-free". I'd like the freedom to install that software if I choose, but I'm also trying to comply with the standards promulgated to not make a "FrankenDebian". It seems to me the best way to approach that when I need software that Debian doesn't provide, is to compile it myself into a Debian package, and use gdebi or dpkg to install, that way apt is aware and can track/update dependencies. Or am I missing something? Please feel free to correct me and/or educate me on a better way to accomplish what I've described. THANK YOU!
×
×
  • Create New...