Registered Member
|
HI.
Yes, I have read this: viewtopic.php?f=309&t=140850&p=438777&hilit=calibre#p438777 But, here is the thing: I have kde neon 5.23.2 installed on my home pc and my work pc. They are the same basic architecture: intel with nvidia gpu. They are both up to date as of today. At work, I have calibre installed. At home, I cannot install it. In fact, at home, it isn't even listed in Discover. Using apt, it tries to install, but, as mentioned above, it doesn't like the QT version. At work, it IS listed in discover, and IS installed, and works like a champ -- and, I didn't have to do anything special to get it there. The only difference, AFAICS, is that my work pc was installed about a year ago, and calibre along with it. I has come through many upgrades with me, whereas my home PC is only very recently installed. But, it seems to suggest that a calibre installation, using the standard, stable apt repositories should work... but it doesn't. Why is that? It makes me wonder if the dependencies it complains about are a non-issue, and perhaps the package requirements should be tweaked...
Last edited by grooveman on Fri Nov 12, 2021 11:51 am, edited 1 time in total.
|
Registered Member
|
The Calibre in Ubuntu 20.04 can't be installed in Neon, even a year ago. Not from using apt packages. Not even when Neon was using 18.04 as a base. The package's hard coded dependency on the older Qt version has not changed.
I am thinking that on your work PC maybe has it installed via flatpak or Snap - this is what I see when I look for it in Discover, on a fairly fresh install here. The package dependencies definitely could be changed - by Ubuntu. They have zero reason to do so.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
Registered Member
|
Hmm... that doesn't make much sense to me... perhaps I installed it at work over year ago -- but definitely not more than 1.5 years...
The funny thing is, after I posted the above, I noticed some updates trickled in... I applied them, now I no longer see calibre in Discover -- but it is still on my system, and it works. Now that I've done more poking around, it does look like it was installed via flatpack... but now that pack is gone from Discover. I wonder why this has not been updated in Ubuntu. It is a pretty awesome program. Perhaps Ubuntu users don't read |
Registered Member
|
Ubuntu does, but only every 6 months with a new release. Or every two years if it is LTS (which Neon is based on). This is by their design. I can see Calibre's flatpak in all my Neon systems, fwiw.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
Registered Member
|
I think I misspelled calibre for a that last check I mentioned... it is still there. I'm an American, so it just comes out my fingers as "caliber" if I'm not careful.
But, I did find something interesting about my two Neon installs: When I go to Discover, and click on settings on my work PC, I see that "Flathub" has a check next to it. It is also at the very top of the list -- even though it is not set to be default ("KDE neon User..." is set to default). On my home PC, I see that I also have "Flathub" checked, but it is 3rd down the list... under "firmware updates" and "Snap". What is likely the source of my problem, however, is that when I click the ">" to the far right on on the "Flathub" section (right next to the trash can), On my work PC I get many options (SpeedCrunch, Bitwarden, Blanket, Blender, etc. etc.), but on the home PC I have "Nothing found". No options whatsoever. I look at both systems, and they have the same packages installed to support flatpaks:
When I look at discover, I see that that the discover flatpak backen IS installed. There is nothing under my /var directory to show any flatpak folder... It is as if flatpaks were somehow disabled. Did I somehow turn off flatpacks? Or does it need to be turned on in some way? |
Registered Member
|
Why not just install the binary from the Calibre website? https://calibre-ebook.com/download_linux That works for me on KDE Neon.
Migrated from Linux Mint 17.3/18.3 KDE to KDE neon User Edition.
|
Registered Member
|
Yes, I could do that, but that would put it outside the package management system, and it wouldn't fix my flatpak issue. I try to avoid going outside the package management system on my systems because I manage too many of them. Installing outside of them works great at first, then becomes problematic at update times. Times that by 50, and it is too much of a hassle.
I could very easily see needing other packages that are managed through the flatpak system... I'd much rather have that working. |
Registered Member
|
Well, something strange happened last night. I got home from work, and saw that more updates had trickled in. I applied them, and suddenly, the flatpak system was working.
Maybe I just installed at a weird time where there was something inconsistent there... but all appears well now. Calibre is installed, and Discover now speaks "flatpak". |
Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]