View Poll Results: Share with us your Noble Numbat upgrade/Installation Experience

Voters
25. You may not vote on this poll
  • Upgrade - Worked Flawlessly.

    4 16.00%
  • Upgrade - Worked but had a few things to fix, nothing serious though..

    5 20.00%
  • Upgrade - Had many problems that I've not been able to solve.

    0 0%
  • Install - Worked flawlessly

    10 40.00%
  • Install - Worked but had a few things to fix.

    5 20.00%
  • Install - Had many problems that I have not been able to solve.

    3 12.00%
Multiple Choice Poll.
Page 4 of 4 FirstFirst ... 234
Results 31 to 38 of 38

Thread: Share with us your Noble Numbat installation/Upgrade Experience

  1. #31
    Join Date
    Aug 2017
    Location
    melbourne, au
    Beans
    Hidden!
    Distro
    Lubuntu Development Release

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    I'll give my latest experience on a system of mine (was Ubuntu 23.10 Desktop): Perfect (outside of operator forgetfulness)

    - hp prodesk 400 g1 sff (i5-4570, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350)

    I'd received notification on the box that upgrade to 24.04 was available, but I'd ignored it until today.. Booted into 23.10 [text] terminal, ensured I'd applied all updates, then `do-release-upgrade`... System upgraded fine.. a few prompts/questions, then i was asked to reboot

    I reboot, and on switching to text terminal (habit; I check at text terminal first to get a feel for how the system looks before I switch to GUI) everything looked good, so switch to sddm/greeter & enter my password.

    Alas here I only got 2x black screens & pointer , not what I expected (I expected a desktop/wm session; LXQt actually).. and here the box was ignored awhile.. until I had some ideas on what had gone wrong & where to look

    Turned out nothing had gone wrong , the last thing I'd used the box for was a support question about an `openbox` session (yesterday or day before), thus my last GUI login/session was openbox back on 23.10. Once I'd logged out, and switched to something I use, all was great.

    My desktop is a multi-desktop install, and all of Lubuntu (LXQt), Xubuntu (Xfce) & Ubuntu (GNOME) are as expected (openbox was too; I just forgotten I'd used it very recently & thus it was default).. I'm not talking about my primary machine here (that box has been running oracular awhile now) but a nearby secondary machine I can use if I want to use the primary box for QA or something else. Its only the 2nd or 3rd release-upgrade for that box; so it's not an old install. That install is rather bloated (multi-desktop for starters), but mostly Ubuntu repository packages.

  2. #32
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    The poll is starting to be useful, but we need more than just 19 votes. Only 10% had huge issues. That's encouraging considering all the possible wonky configurations there are in the world.

  3. #33
    Join Date
    Apr 2014
    Location
    Tucson AZ, USA
    Beans
    1,092
    Distro
    Ubuntu

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    An update. As of now everything is still great. I have however replaced the Snap Firefox with the Flatpak. I had to hunt for my downloads and thought they were getting lost or something. Till that type of thing is fixed I won't be using Snap browsers for sure.

  4. #34
    Join Date
    Aug 2024
    Beans
    0

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    Fresh install or upgrade from mantic does not work at all. Either it freezes during install, reboots during install with broken install, seems to successfully complete install and on reboot does not load UI shell and much more.

    Environment: Mantic # System Details Report
    ---
    Code:
    ## Report details
    - **Date generated:**                              2024-08-13 07:52:00
    
    ## Hardware Information:
    - **Hardware Model:**                              Apple Inc. MacPro6,1
    - **Memory:**                                      32.0 GiB
    - **Processor:**                                   Intel® Xeon® E5-1620 v2 × 8
    - **Graphics:**                                    AMD Radeon™ HD 7800 Series
    - **Graphics 1:**                                  AMD Radeon™ HD 7800 Series
    - **Disk Capacity:**                               42.0 TB
    
    ## Software Information:
    - **Firmware Version:**                            132.0.0.0.0
    - **OS Name:**                                     Ubuntu 23.10
    - **OS Build:**                                    (null)
    - **OS Type:**                                     64-bit
    - **GNOME Version:**                               45.2
    - **Windowing System:**                            Wayland
    - **Kernel Version:**                              Linux 6.10.3-061003-generic
    
    Graphics Driver
    *-display                 
           description: VGA compatible controller
           product: Tahiti LE [Radeon HD 7870 XT]
           vendor: Advanced Micro Devices, Inc. [AMD/ATI]
           physical id: 0
           bus info: pci@0000:02:00.0
           version: 00
           width: 64 bits
           clock: 33MHz
           capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
           configuration: driver=amdgpu latency=0
           resources: irq:165 memory:80000000-8fffffff memory:a0700000-a073ffff ioport:3000(size=256) memory:a0740000-a075ffff
      *-display
           description: VGA compatible controller
           product: Tahiti LE [Radeon HD 7870 XT]
           vendor: Advanced Micro Devices, Inc. [AMD/ATI]
           physical id: 0
           bus info: pci@0000:06:00.0
           logical name: /dev/fb0
           version: 00
           width: 64 bits
           clock: 33MHz
           capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
           configuration: depth=32 driver=amdgpu latency=0 resolution=2560,1440
           resources: irq:167 memory:90000000-9fffffff memory:a0600000-a063ffff ioport:2000(size=256) memory:a0640000-a065ffff
    
    Dmesg amdgpu
    
    [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.10.3-061003-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash radeon.si_support=0 amdgpu.si_support=1 idle=nomwait intel_idle.max_cstate=1 vt.handoff=7
    [    0.085199] Kernel command line: BOOT_IMAGE=/vmlinuz-6.10.3-061003-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash radeon.si_support=0 amdgpu.si_support=1 idle=nomwait intel_idle.max_cstate=1 vt.handoff=7
    [   13.965217] [drm] amdgpu kernel modesetting enabled.
    [   13.965584] amdgpu: Virtual CRAT table created for CPU
    [   13.965639] amdgpu: Topology: Add CPU node
    [   13.966193] amdgpu 0000:02:00.0: enabling device (0006 -> 0007)
    [   13.966744] amdgpu 0000:02:00.0: amdgpu: Fetched VBIOS from VFCT
    [   13.966761] amdgpu: ATOM BIOS: 113-C3861LA-029
    [   13.966785] kfd kfd: amdgpu: TAHITI  not supported in kfd
    [   13.966796] amdgpu 0000:02:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
    [   13.969983] amdgpu 0000:02:00.0: amdgpu: VRAM: 3072M 0x000000F400000000 - 0x000000F4BFFFFFFF (3072M used)
    [   13.969999] amdgpu 0000:02:00.0: amdgpu: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
    [   13.970226] [drm] amdgpu: 3072M of VRAM memory ready
    [   13.970233] [drm] amdgpu: 16033M of GTT memory ready.
    [   13.971472] amdgpu 0000:02:00.0: amdgpu: PCIE GART of 1024M enabled (table at 0x000000F400000000).
    [   13.974631] [drm] amdgpu: dpm initialized
    [   14.492623] amdgpu 0000:02:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 24
    [   14.809349] amdgpu 0000:02:00.0: amdgpu: overdrive feature is not supported
    [   14.809537] amdgpu 0000:02:00.0: amdgpu: Runtime PM not available
    [   14.810132] [drm] Initialized amdgpu 3.57.0 20150101 for 0000:02:00.0 on minor 1
    [   14.955224] amdgpu 0000:02:00.0: [drm] Cannot find any crtc or sizes
    [   14.958332] amdgpu 0000:06:00.0: amdgpu: Fetched VBIOS from VFCT
    [   14.958340] amdgpu: ATOM BIOS: 113-C3861LB-029
    [   14.958358] kfd kfd: amdgpu: TAHITI  not supported in kfd
    [   14.976713] amdgpu 0000:06:00.0: vgaarb: deactivate vga console
    [   14.976720] amdgpu 0000:06:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
    [   14.977856] amdgpu 0000:06:00.0: amdgpu: VRAM: 3072M 0x000000F400000000 - 0x000000F4BFFFFFFF (3072M used)
    [   14.977861] amdgpu 0000:06:00.0: amdgpu: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF
    [   14.978002] [drm] amdgpu: 3072M of VRAM memory ready
    [   14.978006] [drm] amdgpu: 16033M of GTT memory ready.
    [   14.979010] amdgpu 0000:06:00.0: amdgpu: PCIE GART of 1024M enabled (table at 0x000000F400000000).
    [   14.980490] [drm] amdgpu: dpm initialized
    [   15.098767] amdgpu 0000:02:00.0: [drm] Cannot find any crtc or sizes
    [   15.237187] amdgpu 0000:02:00.0: [drm] Cannot find any crtc or sizes
    [   15.476544] amdgpu 0000:06:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 24
    [   15.793405] amdgpu 0000:06:00.0: amdgpu: overdrive feature is not supported
    [   15.793622] amdgpu 0000:06:00.0: amdgpu: Runtime PM not available
    [   15.795661] [drm] Initialized amdgpu 3.57.0 20150101 for 0000:06:00.0 on minor 2
    [   16.016533] fbcon: amdgpudrmfb (fb0) is primary device
    [   16.083069] amdgpu 0000:06:00.0: [drm] fb0: amdgpudrmfb frame buffer device
    [   25.031265] Modules linked in: apple_gmux(+) fjes(-) hid_magicmouse(+) joydev input_leds apple_mfi_fastcharge mac_hid dm_multipath msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 amdgpu amdxcp drm_exec gpu_sched drm_buddy raid0 radeon uas video usb_storage wmi crct10dif_pclmul drm_suballoc_helper crc32_pclmul polyval_clmulni drm_ttm_helper polyval_generic ghash_clmulni_intel sha256_ssse3 ttm nvme sha1_ssse3 igb drm_display_helper nvme_core firewire_ohci dca ahci xhci_pci nvme_auth cec firewire_core libahci i2c_algo_bit thunderbolt crc_itu_t xhci_pci_renesas rc_core tg3 hid_generic usbhid hid aesni_intel crypto_simd cryptd
    
    Dmesg Error
    [   38.683811] gsd-power[2188]: segfault at 8 ip 0000705eb1074d80 sp 00007ffd7bfa1c80 error 4 in libupower-glib.so.3.1.0[15d80,705eb1067000+e000] likely on CPU 3 (core 1, socket 0)
    [   39.155264] gsd-power[2568]: segfault at 8 ip 000079c3862d7d80 sp 00007fffdd83dd40 error 4 in libupower-glib.so.3.1.0[15d80,79c3862ca000+e000] likely on CPU 5 (core 2, socket 0)
    [   52.943730] gsd-power[3122]: segfault at 8 ip 00007ec82a732d80 sp 00007ffdc47bd3e0 error 4 in libupower-glib.so.3.1.0[15d80,7ec82a725000+e000] likely on CPU 1 (core 0, socket 0)
    [   54.622099] gsd-power[3841]: segfault at 8 ip 00007f882d63bd80 sp 00007ffc951e7d90 error 4 in libupower-glib.so.3.1.0[15d80,7f882d62e000+e000] likely on CPU 6 (core 3, socket 0)
    [   56.362050] gsd-power[3877]: segfault at 8 ip 000076367609cd80 sp 00007fff2539e4f0 error 4 in libupower-glib.so.3.1.0[15d80,76367608f000+e000] likely on CPU 3 (core 1, socket 0)
    [   58.127826] gsd-power[4002]: segfault at 8 ip 00007523107a0d80 sp 00007ffc88c38e10 error 4 in libupower-glib.so.3.1.0[15d80,752310793000+e000] likely on CPU 0 (core 0, socket 0)
    [   59.750884] gsd-power[4039]: segfault at 8 ip 00007b359633fd80 sp 00007ffc45736560 error 4 in libupower-glib.so.3.1.0[15d80,7b3596332000+e000] likely on CPU 4 (core 2, socket 0)
    [   61.383396] gsd-power[4589]: segfault at 8 ip 00007a19ee7fcd80 sp 00007fffa27fccf0 error 4 in libupower-glib.so.3.1.0[15d80,7a19ee7ef000+e000] likely on CPU 4 (core 2, socket 0)
    [   63.108337] gsd-power[5220]: segfault at 8 ip 0000797052c1bd80 sp 00007ffe53966570 error 4 in libupower-glib.so.3.1.0[15d80,797052c0e000+e000] likely on CPU 2 (core 1, socket 0)
    [   65.114307] gsd-power[5558]: segfault at 8 ip 0000772113ed7d80 sp 00007ffdb9e60700 error 4 in libupower-glib.so.3.1.0[15d80,772113eca000+e000] likely on CPU 3 (core 1, socket 0)
    [   66.904128] gsd-power[5961]: segfault at 8 ip 000078baf0fe9d80 sp 00007ffe9e2e3ce0 error 4 in libupower-glib.so.3.1.0[15d80,78baf0fdc000+e000] likely on CPU 2 (core 1, socket 0)
    [   68.632791] gsd-power[6059]: segfault at 8 ip 00007ff0756d7d80 sp 00007ffe16f3c570 error 4 in libupower-glib.so.3.1.0[15d80,7ff0756ca000+e000] likely on CPU 4 (core 2, socket 0)
    
    Dmesg Fail
    
    [    0.419073] pci 0000:15:00.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419076] pci 0000:15:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419079] pci 0000:15:06.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419084] pci 0000:15:06.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419086] pci 0000:15:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419089] pci 0000:15:00.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419107] pci 0000:17:00.0: bridge window [io  size 0x2000]: failed to assign
    [    0.419109] pci 0000:17:00.0: bridge window [io  size 0x2000]: failed to assign
    [    0.419114] pci 0000:18:04.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419118] pci 0000:18:05.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419122] pci 0000:18:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419124] pci 0000:18:05.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419128] pci 0000:18:05.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419130] pci 0000:18:05.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419133] pci 0000:18:04.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419135] pci 0000:18:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419263] pci 0000:3a:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419266] pci 0000:3a:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419481] pci 0000:5c:00.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419483] pci 0000:5c:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419486] pci 0000:5c:06.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419489] pci 0000:5c:06.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419491] pci 0000:5c:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419494] pci 0000:5c:00.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419509] pci 0000:5e:00.0: bridge window [io  size 0x2000]: failed to assign
    [    0.419512] pci 0000:5e:00.0: bridge window [io  size 0x2000]: failed to assign
    [    0.419515] pci 0000:5f:04.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419518] pci 0000:5f:04.0: bridge window [mem size 0x00200000 64bit pref]: failed to assign
    [    0.419521] pci 0000:5f:05.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419524] pci 0000:5f:05.0: bridge window [mem size 0x00200000 64bit pref]: failed to assign
    [    0.419526] pci 0000:5f:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419529] pci 0000:5f:05.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419532] pci 0000:5f:05.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419535] pci 0000:5f:05.0: bridge window [mem size 0x00200000 64bit pref]: failed to assign
    [    0.419537] pci 0000:5f:05.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419540] pci 0000:5f:04.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419543] pci 0000:5f:04.0: bridge window [mem size 0x00200000 64bit pref]: failed to assign
    [    0.419545] pci 0000:5f:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419832] pci 0000:a3:00.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419834] pci 0000:a3:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419836] pci 0000:a3:06.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419839] pci 0000:a3:06.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419842] pci 0000:a3:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419844] pci 0000:a3:00.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419862] pci 0000:a6:04.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419866] pci 0000:a6:05.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419870] pci 0000:a6:04.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419872] pci 0000:a6:05.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419875] pci 0000:a6:05.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419878] pci 0000:a6:05.0: bridge window [io  size 0x1000]: failed to assign
    [    0.419880] pci 0000:a6:04.0: bridge window [mem size 0x00200000]: failed to assign
    [    0.419883] pci 0000:a6:04.0: bridge window [io  size 0x1000]: failed to assign
    [    1.639365] thunderbolt 0000:16:00.0: device link creation from 0000:15:00.0 failed
    [    2.615781] thunderbolt 0000:5d:00.0: device link creation from 0000:5c:00.0 failed
    [    3.199709] thunderbolt 0000:a4:00.0: device link creation from 0000:a3:00.0 failed
    [    3.532219] ata1.00: failed to read native max address (err_mask=0x1)
    
    Dmesg Broken
    [    3.532228] ata1.00: HPA support seems broken, skipping HPA handling
    
    Dmesg Kernel
    [    0.000000] Linux version 6.10.3-061003-generic (kernel@sita) (x86_64-linux-gnu-gcc-14 (Ubuntu 14.1.0-5ubuntu1) 14.1.0, GNU ld (GNU Binutils for Ubuntu) 2.42.90.20240720) #202408030740 SMP PREEMPT_DYNAMIC Sat Aug  3 07:53:03 UTC 2024
    [    0.084649] Booting paravirtualized kernel on bare hardware
    [    0.085328] Unknown kernel command line parameters "splash BOOT_IMAGE=/vmlinuz-6.10.3-061003-generic", will be passed to user space.
    [    0.173785] Memory: 32444280K/33524772K available (22528K kernel code, 4521K rwdata, 14236K rodata, 4916K init, 4708K bss, 1080232K reserved, 0K cma-reserved)
    [    0.234472] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/late...-vuln/mds.html for more details.
    [    0.669880] Loaded X.509 cert 'Build time autogenerated kernel key: acfe868aca82b94eea8937538239ff1de#######'
    [    0.761743] Loaded X.509 cert 'Build time autogenerated kernel key: acfe868aca82b94eea8937538239ff1de#######'
    [    0.801130] Freeing unused kernel image (initmem) memory: 4916K
    [    0.801227] Write protecting the kernel read-only data: 36864k
    [    0.801577] Freeing unused kernel image (rodata/data gap) memory: 100K
    [    4.317718] [drm] radeon kernel modesetting enabled.
    [   13.965217] [drm] amdgpu kernel modesetting enabled.
    [   13.966419] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679E 0x106B:0x0126 0x00).
    [   14.958036] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679E 0x106B:0x0125 0x00).
    [   24.051902] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
    [   24.056553] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
    [   24.057308] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
    [   24.081728] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
    [   24.082043] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
    [   24.087689] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...
    [   24.090176] systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System.
    Last edited by ajgreeny; 1 Week Ago at 08:17 AM. Reason: Code tags

  5. #35
    Join Date
    Mar 2007
    Location
    Promiseland
    Beans
    1,662
    Distro
    Xubuntu 22.04 Jammy Jellyfish

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    Had a spare, empty disk on a fairly new mini computer. Installed Xubuntu LTS 24.04 without any issues.

    On second thought: I had an issue trying to ssh into the new installation. I posted a question in these forums and got three different good suggestions.

    The installation itself went well.
    Last edited by him610; 4 Weeks Ago at 09:52 PM.
    Cheers,


    The Linux Command Line at https://linuxcommand.org/

  6. #36
    Join Date
    Apr 2014
    Location
    Tucson AZ, USA
    Beans
    1,092
    Distro
    Ubuntu

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    An update. As of now everything is still great. I have however replaced the Snap Firefox with the Flatpak. I had to hunt for my downloads and thought they were getting lost or something. Till that type of thing is fixed I won't be using Snap browsers for sure.
    Refreshing my information on my post earlier. I found that Snap simply cannot comprehend symlinks in some cases. In my case I had a data partition and I symlinked everything other than my /home/$USER/.var which i bind mounted. Since it didn't know what to do with the symlink it would default to /run/user some nonsense. bind mounting my downloads folder solved this issue.

  7. #37
    Join Date
    Aug 2017
    Location
    melbourne, au
    Beans
    Hidden!
    Distro
    Lubuntu Development Release

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    Just an update, but release-upgrades aren't open any longer, with noble or 24.04 no longer appearing inside https://changelogs.ubuntu.com/meta-release

    https://lists.ubuntu.com/archives/ub...er/006225.html

    Utkarsh Gupta of the Ubuntu Release team states
    That's correct - the upgrade was disabled due to a critical bug in
    ubuntu-release-upgrader in the way it's using the apt solver. This is
    being worked on and as soon as this is fixed, we'll re-enable the
    upgrades.

    We're also working on an announcement post/mail so that people are aware.

  8. #38
    Join Date
    Jul 2011
    Location
    /Europe/Netherlands
    Beans
    378
    Distro
    Kubuntu 24.04 Noble Numbat

    Re: Share with us your Noble Numbat installation/Upgrade Experience

    Upgrade notification started showing again in Kubuntu 22.04 and today I upgraded my Kubuntu to Noble. Everything went fine! Thanks to all the devs involved and of course the people testing and reporting bugs so others upgrade experiences are smooth.

Page 4 of 4 FirstFirst ... 234

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •