Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yeah, I have a back up: it is not a current one as I don't do one periodically due to a smaller SSD, just a single right after all updates are installed after initial installation. I'm guessing that would be the most efficient route to take. I want to say a big thank you to all the effort and patience you put forth to assist me. Before I go, any signs, or ideas of what may have happened, I've never experienced anything like this with Linux before?
Yeah, I have a back up: it is not a current one as I don't do one periodically due to a smaller SSD, just a single right after all updates are installed after initial installation. I'm guessing that would be the most efficient route to take. I want to say a big thank you to all the effort and patience you put forth to assist me. Before I go, any signs, or ideas of what may have happened, I've never experienced anything like this with Linux before?
That was just an option. If you didn't want to TimeShift back, my next suggestion was going to be, through dpkg rather than apt, to force the purging of libreoffice-base, libreoffice-core, and all the packages marked to be autoremoved, then work upwards from dpkg through apt while checking that everything is solid on the way up.
However, in saying that, yours is the second such "interesting" package system tangle I've had to deal with here in the last 2 days where I almost feel that the package system database itself is in a twist, but not a "normal" twist, with my usual tools and methods not working. In both cases, warning or error messages have been produced that don't make sense. For example, one error message said that libreoffice-common was not going to be installed, but it is in the repos and therefore I don't see why it couldn't be. I'm even starting to doubt myself.
If you still want to give this a go though before deciding to revert to the earlier snapshot then let me know - I don't mind carrying on through dogged persistence. We might even get somewhere...
LOL... had I seen your response first I would have preferred to dig in and maybe do some learning, but I just did a "restore". Slickest 3-4 minutes I've experienced with anything associated with the word "restore" (too many failed Windows experiences). But I'm up and running now though so we'll see what happens in the future with the updates that will need to be done. Again thanks for everything.
Ah, great! I would advise in the future that you make the occasional TimeShift (or other) snapshot/backup from time to time so that you don't have too much reconfiguration etc. to do if you have to revert to a previous snapshot. I have daily snapshots saved for a month, because I have the disk space to do that, and they have saved my skin on a couple of occasions.
In this specific case, do let me know if you manage to install all outstanding updates without encountering the same issue as before. I'd be interested to see if that is the case.
Here we go again which command do we start with. Here is msg from Update Manager: also say I have 4 broken packages now.
Code:
E: /var/cache/apt/archives/libreoffice-common_1%3a6.0.7-0ubuntu0.18.04.5_all.deb: unable to open '/usr/lib/libreoffice/share/gallery/bullets/Bullet03-Circle-Green.svg.dpkg-new': Operation not permitted
Ok. Another program (Update Manager, Software Manager, Software Sources, Synaptic, etc.) is accessing the package database. Ensure those other programs are closed and try again.
If none of the programs are visibly open, then the only one that is probably running is Update Manager and you can quit that by right-clicking on the icon in the system tray and selecting "Quit". In saying that, however, the lock on the package database might have been grabbed but not released again by the program in question so even doing that might not solve the problem and a reboot would probably be required.
If the dpkg command fails again, try prefixing it with a sudo (it shouldn't need it, but it may reveal something if it does).
scott@scott-NV57H:~$ sudo dpkg --audit
[sudo] password for scott:
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
libreoffice-java-common office productivity suite -- arch-independent Java sup
libreoffice-pdfimport transitional package for PDF Import component for LibreO
libreoffice-sdbc-hsqldb HSQLDB SDBC driver for LibreOffice
libreoffice-style-galaxy office productivity suite -- Galaxy (Default) symbol
libreoffice-style-tango office productivity suite -- Tango symbol style
Looks like I need a newer version of libreoffice-common????
Code:
scott@scott-NV57H:~$ sudo dpkg --configure libreoffice-java-common
dpkg: dependency problems prevent configuration of libreoffice-java-common:
libreoffice-java-common depends on libreoffice-common (= 1:6.0.7-0ubuntu0.18.04.5); however:
Version of libreoffice-common on system is 1:6.0.7-0ubuntu0.18.04.2.
dpkg: error processing package libreoffice-java-common (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libreoffice-java-common
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
which command do we start with. Here is msg from Update Manager: also say I have 4 broken packages now.
