Garuda update networkmanager-l2tp-gtk3 and networkmanager-l2tp-gtk4 are in conflict

Not sure if this is the intended outcome of the new garuda update

brian@brian in ~ 
λ garuda-update
[sudo] password for brian:          
:: Synchronising package databases...
garuda                                 86.3 KiB  71.4 KiB/s 00:01 [------------------------------------] 100%
core                                  157.9 KiB   756 KiB/s 00:00 [------------------------------------] 100%
extra                                1712.0 KiB  3.94 MiB/s 00:00 [------------------------------------] 100%
community                               6.7 MiB  7.01 MiB/s 00:01 [------------------------------------] 100%
multilib                              174.1 KiB   795 KiB/s 00:00 [------------------------------------] 100%
chaotic-aur                          1981.2 KiB  1859 KiB/s 00:01 [------------------------------------] 100%
looking for conflicting packages...

Packages (1) garuda-update-2.5.5-1

Total Download Size:   0.01 MiB
Total Installed Size:  0.01 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
garuda-update-2.5.5-1-any               7.6 KiB  22.2 KiB/s 00:00 [------------------------------------] 100%
(1/1) checking keys in keyring                                     [------------------------------------] 100%
(1/1) checking package integrity                                   [------------------------------------] 100%
(1/1) loading package files                                        [------------------------------------] 100%
(1/1) checking for file conflicts                                  [------------------------------------] 100%
(1/1) checking available disk space                                [------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Performing snapper pre snapshots for the following configurations...
snapper snapshots skipped
:: Processing package changes...
(1/1) upgrading garuda-update                                      [------------------------------------] 100%
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Foreign/AUR package notification
brother-mfc-j6530dw 1.0.1-0
frozen-bubble 2.2.1beta1-17
instant-meshes-git r46.7b31608-1
kipi-plugins 22.04.0-1
lib32-libstdc++5 3.3.6-8
libkipi 22.04.0-1
libmediawiki 5.37.0-7
perl-alien-sdl 1.446-13
perl-sdl 2.548-7
replay-sorcery 0.6.0-1
samba-mounter-git 186.29ebad4-1
sdl_pango 0.1.2-9
(3/6) Orphaned package notification...
=> No orphans found.
(4/6) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/locale.gen.pacnew
/etc/pamac.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/paru.conf.pacnew
/etc/retroarch.cfg.pacnew
Please check and merge
(5/6) Performing snapper post snapshots for the following configurations...
snapper snapshots skipped
(6/6) Syncing all file systems...

--> Refreshing mirrorlists using rate-mirrors, please be patient..
:: Synchronising package databases...
garuda                                 86.3 KiB   277 KiB/s 00:00 [------------------------------------] 100%
core                                  157.9 KiB  1548 KiB/s 00:00 [------------------------------------] 100%
extra                                1712.0 KiB  7.30 MiB/s 00:00 [------------------------------------] 100%
community                               6.7 MiB  11.9 MiB/s 00:01 [------------------------------------] 100%
multilib                              174.1 KiB  1795 KiB/s 00:00 [------------------------------------] 100%
chaotic-aur                          1981.2 KiB  4.86 MiB/s 00:00 [------------------------------------] 100%

--> Applying keyring updates before starting full system update..
warning: archlinux-keyring-20220727-1 is up to date -- skipping
warning: garuda-hotfixes-1.1.2-1 is up to date -- skipping
resolving dependencies...
looking for conflicting packages...

Packages (1) chaotic-keyring-20220803-1

Total Download Size:   0.03 MiB
Total Installed Size:  0.03 MiB
Net Upgrade Size:      0.01 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
chaotic-keyring-20220803-1-any         26.9 KiB  92.5 KiB/s 00:00 [------------------------------------] 100%
(1/1) checking keys in keyring                                     [------------------------------------] 100%
(1/1) checking package integrity                                   [------------------------------------] 100%
(1/1) loading package files                                        [------------------------------------] 100%
(1/1) checking for file conflicts                                  [------------------------------------] 100%
(1/1) checking available disk space                                [------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Performing snapper pre snapshots for the following configurations...
snapper snapshots skipped
:: Processing package changes...
(1/1) upgrading chaotic-keyring                                    [------------------------------------] 100%
==> Appending keys from chaotic.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signed 2 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  15  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  15  signed:  93  trust: 0-, 0q, 0n, 15m, 0f, 0u
gpg: depth: 2  valid:  73  signed:  30  trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-08-09
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  15  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  15  signed:  93  trust: 0-, 0q, 0n, 15m, 0f, 0u
gpg: depth: 2  valid:  73  signed:  30  trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-08-09
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Foreign/AUR package notification
brother-mfc-j6530dw 1.0.1-0
frozen-bubble 2.2.1beta1-17
instant-meshes-git r46.7b31608-1
kipi-plugins 22.04.0-1
lib32-libstdc++5 3.3.6-8
libkipi 22.04.0-1
libmediawiki 5.37.0-7
perl-alien-sdl 1.446-13
perl-sdl 2.548-7
replay-sorcery 0.6.0-1
samba-mounter-git 186.29ebad4-1
sdl_pango 0.1.2-9
(3/6) Orphaned package notification...
=> No orphans found.
(4/6) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/locale.gen.pacnew
/etc/pamac.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/paru.conf.pacnew
/etc/retroarch.cfg.pacnew
Please check and merge
(5/6) Performing snapper post snapshots for the following configurations...
snapper snapshots skipped
(6/6) Syncing all file systems...
spawn pacman -Su
:: Starting full system upgrade...
:: Replace networkmanager-l2tp with community/networkmanager-l2tp-gtk3? [Y/n] y
:: Replace networkmanager-l2tp with community/networkmanager-l2tp-gtk4? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: networkmanager-l2tp-gtk3 and networkmanager-l2tp-gtk4 are in conflict

My garuda inxi

[🔴] × garuda-inxi
System:
Kernel: 5.18.15-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=44c661c5-fecf-4c99-813c-ef7ab3f53989 rw rootflags=subvol=@
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=411b741b-4385-44ac-af56-73fc209822eb loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.25.3 tk: Qt v: 5.15.5 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG MAXIMUS XI HERO v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 2004
date: 11/02/2021
Battery:
ID-1: hidpp_battery_0 charge: 47% condition: N/A volts: 3.8 min: N/A
model: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A
serial: <filter> status: discharging
CPU:
Info: model: Intel Core i9-9900K bits: 64 type: MT MCP arch: Coffee Lake
gen: core 9 built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158)
stepping: 0xD (13) microcode: 0xF0
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 4960 high: 5007 min/max: 800/5000 scaling:
driver: intel_pstate governor: performance cores: 1: 5004 2: 4967 3: 4998
4: 4921 5: 5002 6: 4915 7: 4916 8: 4999 9: 5004 10: 5007 11: 4941
12: 4868 13: 5002 14: 4918 15: 4997 16: 4904 bogomips: 115200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: Enhanced IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB
filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3090] vendor: Micro-Star MSI
driver: nvidia v: 515.57 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-07) arch: Ampere code: GAxxx process: TSMC n7
(7nm) built: 2020-22 pcie: gen: 2 speed: 5 GT/s lanes: 8 link-max: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2204
class-ID: 0300
Device-2: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A]
vendor: Micro-Star MSI driver: nvidia v: 515.57
alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current (as of
2022-07) arch: Turing code: TUxxx process: TSMC 12nm built: 2018-22 pcie:
gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 02:00.0 chip-ID: 10de:1e07 class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 81 s-size: 1405x457mm (55.31x17.99")
s-diag: 1477mm (58.17")
Monitor-1: DP-0 pos: primary,top-right res: 2560x1440 dpi: 109
size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
Monitor-2: DP-2 pos: bottom-l res: 1920x1080 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 3090/PCIe/SSE2 v: 4.6.0 NVIDIA
515.57 direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 1-4:4 alternate: snd_soc_skl,snd_sof_pci_intel_cnl
chip-ID: 0951:16a4 bus-ID: 00:1f.3 class-ID: 0300 serial: <filter>
chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GA102 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:1aef class-ID: 0403
Device-3: NVIDIA TU102 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 02:00.1
chip-ID: 10de:10f7 class-ID: 0403
Device-4: Kingston HyperX 7.1 Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound Server-1: ALSA v: k5.18.15-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 16.1 running: no
Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 5.01 TiB used: 102.99 GiB (2.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8PCP3512F-AI1
size: 476.94 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFK52.8
temp: 33.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung model: SSD 970 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7
temp: 23.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM001-1ER164
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: HP51 scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM001-1ER164
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: CC43 scheme: GPT
Partition:
ID-1: / raw-size: 442.25 GiB size: 442.25 GiB (100.00%) used: 102.98 GiB
(23.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 580 KiB
(0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 442.25 GiB size: 442.25 GiB (100.00%) used: 102.98
GiB (23.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 442.25 GiB size: 442.25 GiB (100.00%) used: 102.98
GiB (23.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 442.25 GiB size: 442.25 GiB (100.00%) used: 102.98
GiB (23.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.26 GiB used: 1.2 MiB (0.0%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.39 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 28.0 C mobo: N/A gpu: nvidia temp: 39 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 368 Uptime: 9m wakeups: 4 Memory: 31.26 GiB used: 4.92 GiB
(15.8%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.1.0 alt: 11 clang: 14.0.6 Packages: 2025 pacman: 2020
lib: 554 flatpak: 5 Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.20
Garuda (2.6.5-1):
System install date:     2022-02-24
Last full system update: 2022-07-31
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:            bluetooth-autoconnect.service
1 Like

I’m assuming you could only choose one of both in this situation. Likely we now have 2 packages that provide networkmanager-l2tp. Try answering y to the desired version and n to the other one. Personally, I’d probably choose gtk3 since I’m unsure whether gtk4 actually integrates into the desktop theming-wise currently (although it might be possible, gotta have a try :wink: ).

1 Like

This is the default answers that the new garuda update inserts when it is upgrading, no human intervention :smile:

2 Likes

Interesting. That's definitely something to take a look at then! Thanks for posting this :slight_smile:

2 Likes

Oughhh

Which one do we want to pick though? gtk3 or gtk4?

2 Likes

As described above both are being chosen by the new garuda update

Just facing the same and was just about to post an issue..

had to remove networkmanager-support fot networkmanager-l2tp to be removed.
No confused on whether to choose gtk3/4, but 4 will use more of libadvaita, won't it?

And which one do we want it to pick?

1 Like

I do not get the choice :smile: as to which i wish to use

I am asking which one you would want it to pick though.
I am not familiar with this package so I don't have an opinion.

2 Likes

It doesn't ask you to pick one but just lists both when trying to remove, it has to be done manually.

I'd stay with gtk3 for now. Not all GTK themes are having a proper gtk4 theme yet.

3 Likes

Sure thing!

3 Likes

I would say gtk3 aswell

2 Likes

Fixed in garuda-update 2.5.6

6 Likes

Omg I remember asking windows to fix a bug it took two years !
Wow 5 mins
:star_struck:

5 Likes

You can thank Nico for letting me know on telegram so quickly :stuck_out_tongue:

4 Likes

@dr460nf1r3 gets my thank's every day when i boot up my machine's
Need i say more :star_struck:

3 Likes

@Dr4g0n1z3r @TNE This whole thing started because l2tp settings do not work on gnome desktop.

Please see: FS#75482 : [networkmanager-l2tp] Add gtk4 support so gnome GUI connection editor works

For gnome system gtk4 should be the right choice. I wish there was a way to choose the proper package based on what gtk/DE is in use.

I guess that's doable in iso-profiles Garuda Linux / Tools / iso-profiles · GitLab :eyes:

@dr460nf1r3 do you want to go ahead and do that maybe?
@pkasemir Do you by any chance know if there is any downside to using the gtk4 variant everywhere else too?