Beware: Ubuntu Jammy Jellyfish

This is why I like NixOS, it let’s me package specific versions of packages and build my system. I make the package for the specific version and then I can use it as long as I want and its part of my system. No PPA, no other repo. Its there, it’s repeatable.

2 Likes

and you will be stuck on an old version without bugfixes and in worst case security fixes. how did you win again?

@darix, I know you mean well, but this whole thread is not that point. What I’m running into with Jammy are significant holes in previously long-supported software. Thanks to @Entropy512 I somewhat get the hugin disconnect, but the wxWidgets one is hard to fathom. I know the devs here are all over Qt, but wxWidgets is a very capable cross-platform toolkit, lets me deploy both Linux and Windows versions of rawproc (according to @anon41087856, a single-customer software :stuck_out_tongue:) with a minimum of fuss. And minimum fuss is what I want, so I can concentrate on my real hobby, photography.

I want my desktop OS to just work, no olympic-class gymnastics involved. Right now, Jammy isn’t doing that for me…

3 Likes

I’ve found a PPA that has hugin: https://launchpad.net/~ubuntuhandbook1/+archive/ubuntu/apps

Unfortunately, it died when I tried launching it:

(hugin:27897): Gtk-CRITICAL **: 06:58:36.530: gtk_widget_set_size_request: assertion 'height >= -1' failed
/usr/share/hugin/data/plugins/woa.py
   CAT:Control Points
   NAM:Warped Overlap Analysis
   fails @api-max
/usr/share/hugin/data/plugins/top_five.py
   CAT:Control Points
   NAM:keep 5 CPs per image pair
   fails @api-max

(hugin:27897): Gdk-ERROR **: 06:58:36.680: The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 438 error_code 2 request_code 151 (GLX) minor_code 24)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

Breaking from the rolling release ?
Lts versions ?
Promise of backporting security patches?

I wouldn’t want plain debian on my servers to be honest .

1 Like

Sticking to an updated lts release is all you need security wise . I’d skip the Ubuntu .10 versions anyway, and stick on the previous lts for a bit before seeing what the reception is :).

Isn’t the wxwidgets thing that they included a new major version and hugin is still on an older one ? Can’t blame a distro for that , that they want to update to more recent versions with a new distro version.

And hugin being ejected from debian upstream, is a nasty surprise. But not in Canonical’s court so to speak.

2 Likes

As I wrote above, for all I see wxwidgets is still supported in debian (I didn’t check ubuntu, but whatever is in debian usually is in ubuntu too). What wx libraries (the .so files) do you need exactly - I can check which packages that corresponds to.

Wait what? Debian doesn’t have a rolling release - ubuntu are the ones cutting their releases from a random debian testing snapshot . Debian has 5 years of security support, if your a corp you can pay freexian for another 5 years. I mean obviously my comment was facetious, there’s likely a few reasons for ubuntu, I just don’t like a lot of their choises, but the above hardly is it.

It’s is not uncommon to have packages disappear in Ubuntu interim releases, especially stuff in Universe repos. Amarok (MP3 player) wasn’t in 19.10,for instance. This is usually due to last minute incompatibilities/unstable code that cannot be resolved before ship date.

LTS releases have more lead time and have all the packages (Amarok is back in 20.04).

Glenn, after years using *Buntu I took the plunge with Sid version of Debian a few months ago, due to the former’s lack of provision of up-to-date packages. I have had zero regrets.

My current uptime is 53 days and change, it is so stable. (I suspend regularly, but a hard reset is a rare thing. Occasionally I will logout and restart my desktop session, but that might be once a fortnight, if that.)

Of course YMMV.

sid could be dangerous. Debian -- The unstable distribution ("sid") says:

“sid” is subject to massive changes and in-place library updates. This can result in a very “unstable” system which contains packages that cannot be installed due to missing libraries, dependencies that cannot be fulfilled etc.

I’m thinking about running Hugin via Ubuntu 20.10 in Docker, if I find no other solution. Also, I may switch to some other distro – the ‘snap’ madness in Ubuntu broke my Firefox, for example. I’ve already set up OpenSuse Tumbleweed in VirtualBox.

1 Like

I have found a somewhat satisfying interim solution: stop down to f22. That give sufficient DOF to render most of my model locomotive parts in-focus through their entire depth, so long as I don’t orient my largest parts too far from the perpendicular… I’m not after photographic excellence, I just need to see small things.

I did install Hugin on my Windows tablet, may at some point figure out their batch tool to run a focus stack. But, my immediate concerns are about how to resin-print very small parts that are to function mechanically…

Working hard to avoid Distro Fever… :crazy_face:

1 Like

You are, of course, correct. That has always been the disclaimer about Sid, and why it is so named after the unstable kid in toy story who likes ripping heads off dolls. My only previous forays into debian have been with the latest stable; however these have never lasted long due to the very conservative nature of what is deemed stable, and thus being no where close to the latest versions of many applications.

Sid’s “instability” however seems more reliable to me than *buntu these days.

…however so could using sudo.

It really comes down to risk management: and what is an unacceptable risk for one person is acceptable to another.

It reminds me of the send-up of TL;DR software agreements of the 1980s: “such flagrant acts as inserting the floppy disk in the drive and installing the software render all warranties null and void.”

@ggbutcher … Rx for Distro Fever: take two beers and revisit Distrowatch in the morning.

1 Like

Backporting kinetic kudu packages was pretty easy
https://launchpad.net/ubuntu/+source/libvigraimpex
https://launchpad.net/ubuntu/+source/enblend-enfuse

Grab the _orig source tarball and the -debian source tarball
Extract the _orig tarball
Change directory, extract the -debian tarball there

run
debuild -us -uc
If it complains about missing dependencies, install them. I had no problem with any packages if I started with libvigraimpex

Install the resulting .debs - so far I haven’t installed the libvigraimpex python packages, no problem so far

Hugin seems to build fine so far too - hugin package : Ubuntu

Time to test it - hugin starts but I haven’t stitched anything with it in quite a while - but backporting the kinetic kudu packages is simple (grab the tarball and rebuild) and seems to work so far

1 Like

This repo seems to work (I’ve just installed hugin, and stitched a panorama):

https://software.opensuse.org/download/package?package=hugin&project=home%3Apmdpalma%3AUbuntu%3Abucket

1 Like

I’m personally not fans of repos like that one and ubuntuhandbook that have a whole bunch of other unrelated applications in them - sometimes they are less-than-stable version upgrades of other applications I use.

You can also download the .deb files you need, without adding the repo to your system.

Ran across this article specifically on the topic:

I’m going to do the PPA, to make sure I get the command-line tools…

Ack, nevermind about the PPA, align_image_stack and enfuse not working, need to go mow the lawn… :frowning:

Nevermind #2, can’t mow the lawn, family logistics, so back at the tablet…

Turns out there was path and library confusion with my previous attempts to compile, so I uninstalled all that, re-did the PPA and installed hugin, now it works.

Okay, back to family logistics… :crazy_face:

2 Likes

I am on PopOS 22.04 and I noticed they removed Hugin. I then replaced with Flatpak. But then I run into access issues and had to use Flatseal to resolve it.

1 Like