Comments

508 Comments

For some reason this popped up today, even though I checked updates-testing in last few days:

Problem 1: package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- cannot install the best update candidate for package usd-libs-21.05-3.fc34.x86_64
- cannot install the best update candidate for package openvdb-libs-8.0.1-2.fc34.x86_64
Problem 2: problem with installed package usd-libs-21.05-3.fc34.x86_64
- package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- package openvdb-8.2.0-1.fc34.x86_64 requires libopenvdb.so.8.2()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package openvdb-8.0.1-2.fc34.x86_64

Problems without updates-testing:

Problem 1: package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- cannot install the best update candidate for package usd-libs-21.05-3.fc34.x86_64
- cannot install the best update candidate for package openvdb-libs-8.0.1-2.fc34.x86_64
Problem 2: problem with installed package usd-libs-21.05-3.fc34.x86_64
- package usd-libs-21.05-3.fc34.x86_64 requires libopenvdb.so.8.0()(64bit), but none of the providers can be installed
- cannot install both openvdb-libs-8.2.0-1.fc34.x86_64 and openvdb-libs-8.0.1-2.fc34.x86_64
- package OpenImageIO-2.2.19.0-2.fc34.x86_64 requires libopenvdb.so.8.2()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package OpenImageIO-2.2.19.0-1.fc34.x86_64
karma

Yay, full speed YT downloads are back (youtube-dl issue)!

BZ#2018036 pango 1.49.1 broke multi-line text rendering in Inkscape

No regressions spotted.

Upgrade to F35 installs tracker next to baloo on KDE ;/

Wayland with external display still has glitches, X11 still works.

Plasma working fine.

BZ#2012371 Pull in latest commits from KDE 5.15 fork
karma

Yay! Panel resizing got better, thanks!

karma

Now it installed fine. Only vlc requires it on my computer, so I don't know how to test it further.

Problem: cannot install the best update candidate for package libusb-1:0.1.7-3.fc34.x86_64
- nothing provides libusb1(x86-64) needed by libusb-1:0.1.7-5.fc34.x86_64

I was too fast with adding karma, after starting chromium it can't load the new tab page (set to open after start), page stays blank, there's a loading indicator spinning on tab's handle/title. I can open any bookmark or address, it loads, after that I also can successfully open a new tab page, unless original tab is not closed and still trying to load. Console is flooded with four messages.

$ chromium-browser 
ATTENTION: default value of option allow_rgb10_configs overridden by environment.
libva error: /usr/lib64/dri/iHD_drv_video.so init failed
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
ATTENTION: default value of option allow_rgb10_configs overridden by environment.
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
[4294:4294:1015/101910.167732:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[4294:4294:1015/101910.171755:ERROR:shared_context_state.cc(357)] OOP raster support disabled: GrContext creation failed.
[4294:4294:1015/101910.171865:ERROR:gpu_channel_manager.cc(900)] ContextResult::kFatalFailure: Failed to InitializeGrContext for SharedContextState
[4294:4294:1015/101910.172138:ERROR:shared_image_stub.cc(524)] SharedImageStub: unable to create context
[4294:4294:1015/101910.172212:ERROR:gpu_channel.cc(568)] GpuChannel: Failed to create SharedImageStub
[4294:4294:1015/101910.173520:ERROR:shared_context_state.cc(357)] OOP raster support disabled: GrContext creation failed.
[4294:4294:1015/101910.173641:ERROR:gpu_channel_manager.cc(900)] ContextResult::kFatalFailure: Failed to InitializeGrContext for SharedContextState
[4294:4294:1015/101910.173828:ERROR:shared_image_stub.cc(524)] SharedImageStub: unable to create context
[4294:4294:1015/101910.173908:ERROR:gpu_channel.cc(568)] GpuChannel: Failed to create SharedImageStub

I tried to create a new profile and now it does not load at all, there's just an empty window and same messages in console. Same after downgrade to 93.0.4577.82-2.fc34.

I ended up with backing up and nuking ~/.config/chromium - now newest version works fine. I've had uBlock Origin installed and probably some flags changed.

Fixed 94.0.4606.61-1.fc34 crash, thanks.

BZ#2010170 chromium browser crashes upon launch

@kalev I guess it would be best if libtracker-sparql (or other gtk component) could also use baloo as index/search provider.

This update installs libtracker-sparql as a dependency and, as weak dependencies, tracker with tracker-miners. I'm using KDE spin, where there's already Baloo, does it mean that from now on we'll have two indexing services working in background (unless someone removes tracker manually)?

No regressions spotted on X.

karma

No regressions spotted on IVB GT2 + AMD TURKS laptop.