![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1199895 https://bugzilla.suse.com/show_bug.cgi?id=1199895#c35 --- Comment #35 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Ednilson Miura from comment #32)
Hello, while testing S:M:24915:275232 (packagekit update for SLE15SP3) I'm having some issues reproducing this issue. What I have tried:
I know that there is a tigervnc pending update,so:
# zypper al tigervnc Specified lock has been successfully added. ligur:~ # zypper ll
# | Name | Type | Repository | Comment --+----------+---------+------------+-------- 1 | tigervnc | package | (any) |
But now: # pkcon update Getting updates [=========================] Finished [=========================] Refreshing software list [=========================] Testing changes [=========================] Finished [=========================] Fatal error: the to be installed patch:SUSE-SLE-Module-Basesystem-15-SP3-2022-3012-1.noarch conflicts with 'tigervnc.x86_64 < 1.9.0-150100.19.20.1' provided by the installed tigervnc-1.9.0-150100.19.17.1.x86_64
It says that it "conflicts" with the updated package. Removing the lock solves the issue.
Is there another way to reproduce this issue? (I have the same behaviour before/after applying packagekit update)
Maybe try locking packages that doesn't belong to a patch upate. -- You are receiving this mail because: You are on the CC list for the bug.