Announcement

Collapse
No announcement yet.

Jump into Jammy Kubuntu 22.04 LTS

Collapse
This topic is closed.
X
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #91
    It is now 2 months before the release of Jammy Jellyfish LTS.



    Thanks to Snowhog I have now found my 3 months to go status report to show the progress by the developers since then, which is outstanding.

    Over the past month the only hurdle that I have encountered is that, of the three OS’s that I have, I was only left with one, namely Jammy after recent updates. The solutions to this if given in the posts above. If you have this problem, you can try the one that suites you best.

    Now for a list of the progress by developers since the 3 month to go status. This is listed only contains the items in the Info Center.
    3 Months To Go 2 Months To Go
    KDE Plasma Version 5.23.0 5.24.2
    KDE Frameworks Version 5.90 5.91
    QT Version 5.15.2 5.15.2
    Kernel Version 5.15.0-17-generic 5.15.0-22-generic
    The above list is based on using the Pre-released and Unsupported updates. I also still use the non-standard repositories:
    Code:
    sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma
    sudo add-apt-repository ppa:kubuntu-ppa/staging-frameworks
    sudo add-apt-repository ppa:canonical-kernel-team/unstable
    I have found that Wayland is making good progress, however it is not capable of doing LibreOffice Impress projections correctly. The external monitor is not identified. As a result the presentation is on the same screen as the presentation control. So I have to use X11 for my presentations.

    Last edited by NoWorries; Feb 22, 2022, 04:08 PM. Reason: I have now added the 3 Month To Go status

    Comment


      #92
      Doing an Advanced Search on key words before the release of Jammy Jellyfish LTS found three (counting todays). Here is the link to the one you did for the 3 months to go:

      https://www.kubuntuforums.net/forum/...057#post660057
      Windows no longer obstructs my view.
      Using Kubuntu Linux since March 23, 2007.
      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

      Comment


        #93
        Originally posted by verndog View Post
        I've been using a custom 'grub.cfg' for years without issue. Using 'labels' makes reading easier
        Great to see that someone else does this. The same works in /etc/fstab, (LABEL= instead of UUID=), with similar benefits.

        I replace my 'grub.cfg' whenever it gets overwritten
        (I did that for many years.) If you change the grub package from grub-efi-amd64 to grub-efi-amd64-bin, it
        Originally posted by grub-efi-amd64-bin package details
        will not ... automatically update grub.cfg on upgrade
        Regards, John Little

        Comment


          #94
          Originally posted by jlittle View Post

          Great to see that someone else does this. The same works in /etc/fstab, (LABEL= instead of UUID=), with similar benefits.


          (I did that for many years.) If you change the grub package from grub-efi-amd64 to grub-efi-amd64-bin, it
          Thanks, I'll look into that. One thing I've done is:
          Code:
          sudo sed -i 's/cfg/cfg.CRAP/' /usr/sbin/update-grub
          Maybe you have a better solution.
          Boot Info Script

          Comment


            #95
            So far, the experience on Jammy continues to be quite good! Still have the Software Sources bug posted about previously, which is understandable as I will run Staging and Proposed. One thing I am not a fan of was the update for Firefox forced the SNAP version.

            Comment


              #96
              Things are still going well with 22.04 here. No real problems a couple of third party programs I use had to be from focal but they work fine. They will be update I'm sure when jammy hits final.
              Dave Kubuntu 20.04 Registered Linux User #462608

              Wireless Script: http://ubuntuforums.org/showthread.p...5#post12350385

              Comment


                #97
                I have a LibreOffice presentation coming up and it includes three HD videos. I have being using Pre-released Updates and the LibreOffice version was 7.3.1.2. I found that this did not handle videos correctly. Basically in some cases the presentation screen was on the same screen as the projection control. To fix this, I removed the Pre-released Update option, purged LibreOffice from my system and then installed the standard version which was 7.2.5.2

                LibreOffice presentation 7.2.5.2 works perfectly with HD videos inserted. So I will keep a close eye on any fixes to 7.3.1.2. I will do this by enabling the Pre-released Updates and see what LibreOffice version is to be installed.

                This is one case where I have had Pre-released Updates give me problems. I continue to be impressed with the progress of 22.04

                Comment


                  #98
                  I'm still using Libreoffice 7.2.5.2 here also. One thing I find with it though is that I usually disable Java in options>advanced but in 22.04 it won't let me do that if I uncheck it, it simply rechecks it when I click on apply. Haven't really sought any further to figure out why.. Just don't need Java for anything I do and think it still a security risk.
                  Dave Kubuntu 20.04 Registered Linux User #462608

                  Wireless Script: http://ubuntuforums.org/showthread.p...5#post12350385

                  Comment


                    #99
                    Originally posted by NoWorries View Post
                    I have a LibreOffice presentation coming up and it includes three HD videos. I have being using Pre-released Updates and the LibreOffice version was 7.3.1.2. I found that this did not handle videos correctly. Basically in some cases the presentation screen was on the same screen as the projection control. To fix this, I removed the Pre-released Update option, purged LibreOffice from my system and then installed the standard version which was 7.2.5.2

                    LibreOffice presentation 7.2.5.2 works perfectly with HD videos inserted. So I will keep a close eye on any fixes to 7.3.1.2. I will do this by enabling the Pre-released Updates and see what LibreOffice version is to be installed.

                    This is one case where I have had Pre-released Updates give me problems. I continue to be impressed with the progress of 22.04
                    Even with Pre-released Updates disabled, I unfortunately missed that my system was updated to LibeOffice version 7.3.1.2 which only shows one in-bedded video on LO Impress, others are not shown. I even tried version 7.3.1.3 and that has the same problems.

                    So I have now Locked at Current version, all LO listings on my 21.10 system. This allows me to use a working LO Impress system for presentations that have in-bedded videos. I would like this problem fixed on Jammy, but I am in no hurry as I have a solution to my problem which I feel is not shared by many on this forum.

                    Comment


                      Originally posted by MeMyself View Post
                      So far, the experience on Jammy continues to be quite good! Still have the Software Sources bug posted about previously, which is understandable as I will run Staging and Proposed. One thing I am not a fan of was the update for Firefox forced the SNAP version.
                      Today my Firefox snap failed to start and I initially thought that I would have to return to my Kubuntu 21.10 version which worked OK without the Snap version. I then returned to Jammy and decided to install firefox-dev. This remove the Firefox snap version and installed version 97.0.2 which is not a snap version and works perfectly. So I am now very happy with this solution which I hope continues to work. My Thunderbird version has not been made a snap version yet and I hope it never does.

                      Comment


                        Originally posted by NoWorries View Post

                        Today my Firefox snap failed to start and I initially thought that I would have to return to my Kubuntu 21.10 version which worked OK without the Snap version. I then returned to Jammy and decided to install firefox-dev. This remove the Firefox snap version and installed version 97.0.2 which is not a snap version and works perfectly. So I am now very happy with this solution which I hope continues to work. My Thunderbird version has not been made a snap version yet and I hope it never does.
                        I uninstalled snap and discover from my Neon and I, too, hope that Thunderbird will always be available without snap. I used to use KMail for a loooonnnggg time but then it became too fragile to use and I reverted to Thunderbird.

                        "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                        – John F. Kennedy, February 26, 1962.

                        Comment


                          It sounds like Jammy defaults to the snap version of Firefox. Is the deb version still available in the repos? If so, does anyone know if you do an in-place upgrade from 21.10 whether you get to keep the deb Firefox, or whether it will uninstall the deb and give you the snap as a dependency of the top level desktop package?

                          Comment


                            Originally posted by jlittle View Post
                            If you used btrfs, there'd be no need for lots of partitions, just two, or three if you want a swap partition. Subvolumes take over the role of partitions.

                            When I do test installs of new releases, I install into the same btrfs as other installs. Ubuntu installs into subvolumes called "@" and "@home", and I just have to rename them to something else to get them out of the way of another new install. It saves a lot of time and space, not juggling partitions.
                            So your new installs are named @ and @home. You have to change /etc/fstab settings to point to the set you want to boot into. Is that how how you do it, or do you have an app the lets you choose the boot environment at boot?

                            "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
                            – John F. Kennedy, February 26, 1962.

                            Comment


                              Originally posted by GreyGeek View Post
                              Is that how how you do it, or do you have an app the lets you choose the boot environment at boot?
                              Yes, I edit /etc/fstab. Also, grub needs an extra entry. Symbolic links work in both places, but can be confusing, and a link can't point to more than one place at a time, so some editing is necessary.

                              Note that the /etc/fstab and grub.cfg I use are cleaned up and laid out nicely so that editing is easy and less error-prone. The clean up is mostly banishing UUIDs for volume labels.

                              We did track down the python script that is the origin of the names "@" and "@home", and if one was doing a lot of it, it would be quicker to edit the script.
                              Regards, John Little

                              Comment


                                It is now 1 month before the release of Jammy Jellyfish LTS.


                                During this past month I have experienced significant problems with Jammy. To start with, I had a “deb hell” experience. I had packages which were no longer required, so I removed them as suggested. After doing this, my system was no longer boot-able and didn’t even get to the login screen. My Laptop has Windows, Kubuntu 21.10 and 22.04 systems on it.

                                So I downloaded the latest iso and created an installation USB using my Kubuntu 21.10 system. When I tried the installation USB, ubiquity crashed. I tried earlier March iso files and they gave the same result. I ended up submitting a bug report and found that it was a duplicate of one on the 4th March and can be found at:

                                https://bugs.launchpad.net/bugs/1963697.

                                For anyone wanting to now try Jammy, this problem still exists and it is only possible to try out the desktop provided by the installation USB.

                                So I was well and truly snookered. I fortunately found a February iso for Jammy. I think this iso was used to solve problems with my "Sacrificial Laptop" which I won't go into here.

                                I was able to successfully install Jammy based on this iso. There were hundreds of updates to do and I was able to eventually get the system going. As I have a UHD monitor on my Laptop, the boot screen is minuscule so I use grub customizer to create my own menu and background screen. After doing this, I could no longer boot Jammy. After several attempts to fix this problem, I gave up using grub customizer and now my boot menu has the main options of Ubuntu, Windows and Ubuntu 21.10 in a microscopic list.

                                One advantage of the February iso is that LibreOffice is at 7.2.5.2 and this version correctly deals with a presentation that includes video. LibreOffice version 7.3.2.1 cannot handle videos correctly. So with the February iso my first action is to lock the LibreOffice packages so that they do not get updated.

                                Now for a list of the progress by developers as summarized by the items in the Info Center.

                                3 Months To Go 2 Months To Go
                                KDE Plasma Version 5.24.2 5.24.3
                                KDE Frameworks Version 5.91 5.92.0
                                QT Version 5.15.2 5.15.2
                                Kernel Version 5.15.0-22-generic 5.15.0-23-generic

                                I just hope it does not take too long to solve the problems related to ubiquity crashing, so that more people can experience the development of this LTS. Based on my previous experiences, I for one will carefully test the removal of each package that is no longer required.



                                Comment

                                Working...
                                X