Leap 15.6 broken update

English Applications
21

No, @hui isn’t blaming you for anything. He carefully explained how the doubled repos occurred. But the topic author didn’t quite understand that at first. Only then did @hui mention your name. I doubt that he is specifically following you. He was just attempting to explain what happened.

22

Really?

This sounds like double standard.

23

Directly after the TO explained that this is a fresh Leap 15.6 installation i considered the above sentence as claim that it is the TOs fault (and if you read the answers from the TO, you see that he had the same understanding.)

As already said, i stepped in to clear up this statement, as the repo services are now already known for a long time and is also not the first time that these double set of repos occur in terminal outputs from different users in the forum.

24

On my 15.6 system I allowed
remove |gtk3-branding-openSUSE|15.0-lp156.3.3

Update proceeded fine with no issues

25

Hi
I have 2 Leap 15.6 installs on this PC.

Both displayed the GTK error.

One resolved it using zypper, in that it, if I remember correctly, removed a 0 byte file and all was well.
The other NADA, still complains, so there is a glitch I believe.

However I have broken both my update methods, and see a re-install as the only answer, so I guess the GTK error will occur on those also.

26

Installed gtk3-branding-upstream 3.24.43-150600.3.7.1 instead of gtk3-branding-openSUSE to resolve the issue.

27

@clive … try one of these workarounds:

That’s interesting :slight_smile:

I swapped out gtk3-branding-openSUSE and replaced it with gtk3-branding-SLE. That fixed it for me.

28

Both packages are only different in a license.

1 Like
29

Hi

Unfortunately my systems are really broken, but thank you for the offered help.

I know they are broken because I broke them.

1 Like
30

Shouldn’t we simply wait until the packaging guys resolve this issue?
See hui’s reply (Leap 15.6 broken update - #4 by hui).

There was a similar issue with Xfce related packages before Christmas time which got resolved beginning of January.

31

I went with:

Solution 4: break gtk3-branding-openSUSE-15.0-lp156.4.2.1.noarch by ignoring some of its dependencies

Yes, there’s a risk with the breaking. But since it is only a branding package, the risk is probably low. I’ll take my chances.

1 Like
32

Hi
No issues seen here on a standard GNOME install…

zypper -vvv up
....
 gtk3-branding-openSUSE         
    15.0-lp156.3.3 -> 15.0-lp156.4.2.1                 noarch  Main Update Repository                                        openSUSE
....
Retrieving: gtk3-branding-openSUSE-15.0-lp156.4.2.1.noarch (Main Update Repository)
....
Installing: gtk3-branding-openSUSE-15.0-lp156.4.2.1.noarch ................[done]
33

I got this conflict today(01/09/2025) after a week of not updating.

I tried the break option per @nrickert, and it didn’t work for me. Leap 15.6 broken update - #31 by nrickert

I did use the solution from @vertclair Leap 15.6 broken update - #12 by vertclair

@malcolmlewis what are the 'VVV’s in your zypper command?

AND, just hope it doesn’t screw up something in the system!

34

@Bill_L I always add verbosity (-vvv) to see what is what on refresh/download/install

35

Thanks , I asked because I did a ‘help’ on zypper up and it did not show them. I’ll look deeper

36

I have a 15.6 system installed and I also have the same problem with the gtk3 branding error on the update.
I tried the solution 2 on yast of
deinstallation of gtk3-branding-openSUSE-15.0-lp156.3.3.noarch
just as sugested.
the probem is that I got a file conflict after procedding from there:

File /usr/lib64/gstreamer-1.0/libgstamrnb.so
  from install of
     gstreamer-plugins-good-1.24.0-150600.3.3.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)
  conflicts with file from package
     gstreamer-plugins-ugly-codecs-1.22.0-150500.1.pm.2.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstamrwbdec.so
  from install of
     gstreamer-plugins-good-1.24.0-150600.3.3.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)
  conflicts with file from package
     gstreamer-plugins-ugly-codecs-1.22.0-150500.1.pm.2.x86_64 (@System)

Is there any way to get solve this issue.
Regards,

37

That problem has nothing to do with the bug described here.

Please open new thread.

2 Likes
38

I had the problem switched to SLE branding and it allowed the rest of the updates

39

Fix is underway: Request 1236820 - openSUSE Build Service

40

You’re right, I already did, thanks.

1 Like