Manjaro 24.0 Wynsdey released

All I could find was that in Star Trek, Wynsdey III was the third inhabited planet of the Memory Alpha system. It was however only mentioned during writing.

2 Likes

It sounds quite interesting and makes no sense which is probably the whole point.

5 posts were merged into an existing topic: [Stable Update] 2024-05-18 - Linux-Firmware, PHP, Gitlab, Qt6

One observation: only a small percentage of the checksum links (in this thread) have been clicked versus the .ISO links … :roll_eyes:

1 Like

Folks, comments in the thread should be about feedback regarding the ISOs and fresh installs, not updating from existing installs. I’ve had to move multiple replies to the proper Stable Updates thread.

2 Likes

Fresh install in my case is the Manjaro GNOME .ISO in VirtualBox. Works well so far with my experimentation/testing. I didn’t install an office suite or a few other things I won’t need for VB testing.

The only issue I’ve had is I found it locks up after a while in (U)EFI mode but that seemingly isn’t a Manjaro issue rather a VirtualBox problem (same thing happens with EndeavourOS and Manjaro KDE).

Also my issue of being a Gnome “Virgin” and as yet have no idea how to find my way around it! Totally alien to me. (Installed it to see if might be useful for “helping” on here).

You will be quite surprised checking all previous Manjaro versions names…

3 Likes

Haha @anton6613 hit the nail on the head - that’s funny.

1 Like

Wasn’t “Vulcan” a dead giveaway? :vulcan_salute:

LLAP...

4 Likes

So I managed to get up-to-date and running nvidia-390 with Plasma 6 [and even Wayland (but only @480p)] with kernels 61, 65, 66, 69.

The last and only iso I could do it with was manjaro-kde-23.0.4-231015-linux65.iso

The ones before it might be doable, but you run into dependency-cycle issues with plasma5>plasma6 packages on pamac/pacman.

The ones after, the isos came with linux66 or newer and proprietary installs (my graphics card is NVIDIA GF119M [GeForce 410M]) would not boot past the logo on the 66+ kernels.

As this might be scaring off “new users on older hardware” I believe this is useful info for devs here.
There must have been some changes in either Calamares, or possibly Mhwd from the 23.0.4 to the 23.1.0 release! Sddm I don’t think is an issue as I selected auto-login on boot in Calamares.

As this is not only concerning this Wynsdey release I can provide info in the thread I opened here for the issue: Nvidia 390 not working with kernel 66 on new install?

Btw, where can I find the plasma-to-defaults.sh script kindly provided by @linux-aarhus ?

2 Likes

Oh no - I see trouble ahead…

1 Like

They have all been celestial bodies. Planets. And stars in some cases I think?
( in the Star Trek universe :wink: )

1 Like

Vulcan, in particular; both a planet (homeworld of Spock) and part of the Star Trek Universe. Some little-known trivia is that Vulcan was once thought to be an actual planet (or planetesimal) within our own non-fictional star system; a hypothetical planet claimed to have been discovered in orbit between Sol and Mercury (though never rediscovered or confirmed). Here’s another fun fact.

Linux distribution code names have always amused me. In particular, Debian, with it’s “Toy Story” theme. I’m still waiting for any distribution to choose “Wascally Wabbit” as a code name.

1 Like

Trouble? Why, I think Grand Nagus Zek would make a fine name for a release.

2 Likes

Article in distrowatch about Manjaro: DistroWatch.com: Put the fun back into computing. Use Linux, BSD.

1 Like

It was a long time since I had installed Manjaro. I decided to reinstall it on my old desktop, since it was a bit of a mess.

I used the default installer with manual partitioning, since I use a bunch of lvm volumes and wanted to keep the layout.

Everything went fine, first boost froze, maybe something related to Wayland, I don’t know (I use X11). Changed tty, terminated the session, installed some more packages I needed, rebooted and everything seems to be working fine.

Thank you very much to the team and keep the good work.

Oh, I changed the kernel to 6.6, but 6.9 was working fine

System:
  Kernel: 6.6.32-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/vmlinuz-6.6-x86_64
    root=/dev/mapper/vgManjaro-lvRoot rw quiet splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.2.0
    wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5P43TD PRO v: Rev X.0x
    serial: <superuser required> uuid: <superuser required>
    BIOS: American Megatrends v: 0710 date: 11/04/2010
CPU:
  Info: model: Intel Core2 Quad Q9650 bits: 64 type: MCP arch: Penryn
    level: v1 built: 2008 process: Intel 45nm family: 6 model-id: 0x17 (23)
    stepping: 0xA (10) microcode: 0xA0B
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 12 MiB desc: 2x6 MiB
  Speed (MHz): avg: 3300 high: 3600 min/max: N/A cores: 1: 3600 2: 2400
    3: 3600 4: 3600 bogomips: 28808
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: GCN-4
    code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 2
    speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: HDMI-A-2 off: HDMI-A-1 empty: DP-1,DP-2,DVI-D-1 bus-ID: 01:00.0
    chip-ID: 1002:67df class-ID: 0300 temp: 46.0 C
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 506x285mm (19.92x11.22")
    s-diag: 581mm (22.86") monitors: <missing: xrandr>
  Monitor-1: HDMI-A-1 model: LG (GoldStar) TV serial: <filter> built: 2009
    res: 1440x900 dpi: 78 gamma: 1.2 size: 409x230mm (16.1x9.06")
    diag: 558mm (22") ratio: 16:10 modes: max: 1440x900 min: 720x400
  Monitor-2: HDMI-A-2 model: LG (GoldStar) W2246 serial: <filter>
    built: 2010 res: 1920x1080 dpi: 102 gamma: 1.2
    size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.8-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 470 Graphics
    (radeonsi polaris10 LLVM 17.0.6 DRM 3.54 6.6.32-1-MANJARO)
    device-ID: 1002:67df memory: 3.91 GiB unified: no
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel 82801JI HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3a3e class-ID: 0403
  Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
    chip-ID: 1002:aaf0 class-ID: 0403
  API: ALSA v: k6.6.32-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
    vendor: ASUSTeK driver: ATL1E v: N/A modules: atl1e pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: dc00 bus-ID: 02:00.0 chip-ID: 1969:1026
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Realtek RTL88x2bu [AC1200 Techkey] driver: rtw_8822bu type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 9-1.4:3
    chip-ID: 0bda:b812 class-ID: 0000 serial: <filter>
  IF: wlp4s0u1u4 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: ASUSTek ASUS USB-BT500ÿ driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2 chip-ID: 0b05:190e
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.25 TiB used: 12.49 GiB (1.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 120GB SSD
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0613 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SD7SB3Q064G1122
    size: 59.63 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0000 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Zheino model: CHN 25SATA02M 064
    size: 59.62 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 6K scheme: MBR
  ID-4: /dev/sdd maj-min: 8:48 vendor: Hitachi model: HDT721010SLA360
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A31B scheme: MBR
  ID-5: /dev/sde maj-min: 8:64 vendor: Vaseky model: V800 128G
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 7A scheme: GPT
Partition:
  ID-1: / raw-size: 78.2 GiB size: 78.19 GiB (100.00%) used: 12.17 GiB (15.6%)
    fs: f2fs dev: /dev/dm-14 maj-min: 254:14 mapped: vgManjaro-lvRoot
  ID-2: /boot raw-size: 512 MiB size: 487.2 MiB (95.16%)
    used: 322.7 MiB (66.2%) fs: ext4 dev: /dev/dm-5 maj-min: 254:5
    mapped: vgManjaro-lvBoot
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 209.0 C mobo: 33.0 C gpu: amdgpu temp: 46.0 C
  Fan Speeds (rpm): cpu: 892 psu: 1298 case-1: 1973 gpu: amdgpu fan: 1454
  Power: 12v: 12.62 5v: N/A 3.3v: 2.93 vbat: N/A gpu: amdgpu watts: 14.00
Info:
  Memory: total: 16 GiB available: 15.62 GiB used: 2.07 GiB (13.2%)
  Processes: 268 Power: uptime: 17m states: freeze,standby,mem,disk
    suspend: deep avail: s2idle,shallow wakeups: 0 hibernate: platform
    avail: shutdown, reboot, suspend, test_resume image: 6.23 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd
    v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1187 libs: 345 tools: pamac pm: flatpak pkgs: 0
    Compilers: N/A Shell: Zsh v: 5.9 default: Bash v: 5.2.26 running-in: konsole
    inxi: 3.3.34
1 Like

HI , how did you make the taskbar’s “current running apps” look like that? I mean like, with the name displaying and all
I am on KDE myself and would like to change to that. Here’s a screenshot of my taskbar setup

Right click on free space of your panel and choose another alternative.

1 Like

thanks so much, good sir!