http://bugzilla.opensuse.org/show_bug.cgi?id=1199210
Bug ID: 1199210
Summary: Firefox 99 no longer plays video content due to
Tumbleweed FFMPEG / openh264 incompatibility
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Firefox
Assignee: factory-mozilla(a)lists.opensuse.org
Reporter: jphands(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
About 21 days ago, I reported a bug (
https://bugzilla.mozilla.org/show_bug.cgi?id=1764436 ) to the FireFox team,
after a Tumbleweed update caused FireFox to stop playing some video content.
Other browsers like Brave or Opera worked just fine, leading me to suspect
Firefox. I worked with the FF team to run various tests and their eventual
resolution is "wontfix" because the problem actually seems to be some packaging
issue with FFMPEG and OPeH264...perhaps a version mismatch.
One of the FF developers said "To fix the problem, you need to install the
exact same version of https://software.opensuse.org/package/libopenh264-6 that
was used to build OpenSuse's ffmpeg-5." The mozilla bug link above gives the
full story.
I have been unable to get Firefox to play video content, no matter what
combination of FFMPEG and Openh264 I've tried, but this area isn't my strength.
The FF people recommended that I open a bug with Tumbleweed, and perhaps
together, the bug can be resolved.
I'm available for any testing or experiments...just let me know.
==========================MACHINE
INFO==========================================
Operating System: openSUSE Tumbleweed 20220503
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: X11
Processors: 24 � AMD Ryzen 9 3900X 12-Core Processor
Memory: 47.0 GiB of RAM
Graphics Processor: AMD DIMGREY_CAVEFISH
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1191924
Bug ID: 1191924
Summary: kernel-source.git/README outdated
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: ohering(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
There is a section "Before You Commit -- Things To Check" in
kernel-source.git/README, it will likely not work out of the box.
According to rpm/kernel-binary.spec.in, at least three more packages beside the
obvious gcc/make/patch need to be installed:
BuildRequires: libopenssl-devel
BuildRequires: libelf-devel
BuildRequires: dwarves >= 1.21
Furthermore rapidquilt is not mentioned. It is not strictly required, but one
can hardly live without it.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1184490
Bug ID: 1184490
Summary: mame creates a cfg directory in PWD instead of ~/.mame
and ignoring ~/.mame/cfg
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: ilya(a)ilya.pp.ua
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After updating mame to 0.226, mame started ignoring the configuration directory
~/.mame/cfg/ and started creating it in PWD, i.e. the directory where mame runs
from (~/ if you run mame via the menu).
In 0.229 nothing has changed.
In 0.211 it was no problem.
To reproduce, just run "cd /tmp && mame", wait for mame to load the interface,
then press Esc to quit mame, and then check /tmp "ls -lah /tmp | grep cfg".
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047218
Bug ID: 1047218
Summary: trackerbug: packages do not build reproducibly from
including build time
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: SUSE Other
Status: CONFIRMED
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: bwiedemann(a)suse.com
Reporter: bwiedemann(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: Development
Blocker: ---
See also https://reproducible-builds.org/
and https://reproducible-builds.org/specs/source-date-epoch/
When packages include the current time of build
it results in binaries that differ on every build
and thus trigger rebuilds of depending packages
and are published to mirrors and users
when actually nothing really changed.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1131931
Bug ID: 1131931
Summary: OCFS2: Defragmentation error: No space left on device
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: High Availability
Assignee: ha-bugs(a)suse.de
Reporter: weikai.wang(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 802412
--> http://bugzilla.suse.com/attachment.cgi?id=802412&action=edit
this script is used to generate disk framentation
when I used the defragfs.ocfs2 to clean up disk fragmentation that generated by
the attached shell script.
you could execute the scrip by command "./defragfs_test.sh -d DEVICE -m
MOUNT_POINT -n CLUSTER_NAME -s pcmk -o /tmp"
You should use the device on your cluster replace DEVICE, use the same way
replace MOUNT_POINT and CLUSTER_NAME.
Then use the command defragfs.ocfs2 MOUNT_POINT. And if no accident, you will
see some message like this:
“
defragfs.ocfs2 1.8.5
[1/201]/mnt/ocfs2/tmp_file:Success [ERROR]Move extent
failed:"/mnt/ocfs2/test_from_dd1" - No space left on device
[2/201]/mnt/ocfs2/test_from_dd1:Failed [ERROR]Move extent
failed:"/mnt/ocfs2/test_from_dd2" - No space left on device
[3/201]/mnt/ocfs2/test_from_dd2:Failed [ERROR]Move extent
failed:"/mnt/ocfs2/test_from_dd3" - No space left on device
”
but if you execute defragfs.ocfs2 MOUNT_POINT again, the error message will not
show again. and all the defragmentation will pass.
please make sure your device's capacity is more tha 1G.
Some times this error can make mount, unmount, and mkfs crushed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1199184
Bug ID: 1199184
Summary: switch Tumbleweed to a 4096bit RSA signing key
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: dimstar(a)opensuse.org
Reporter: meissner(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: dmueller(a)suse.com
Found By: ---
Blocker: ---
We currently still use a 2048 bit key for signing.
It would be better to switch to a 4096 RSA key.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182998
Bug ID: 1182998
Summary: libcontainers-common seems to miss prerequires
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Containers
Assignee: containers-bugowner(a)suse.de
Reporter: kukuk(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
There are several errors during initial installation of libcontainers-common.
As result, the configuration is broken and podman not correct working:
# 2021-03-04 05:56:10 libcontainers-common-20210112-2.1.noarch.rpm installed ok
# Additional rpm output:
# /var/tmp/rpm-tmp.fgZbcB: line 4: findmnt: command not found
# /var/tmp/rpm-tmp.fgZbcB: line 4: findmnt: command not found
#
2021-03-04
05:56:10|install|libcontainers-common|20210112-2.1|noarch||openSUSE-MicroOS-20210302-0|867c95e8e8cd2e09046dc327b743e9134c6072146f59c6f3b357b0e92420b494|
# 2021-03-04 05:56:10 openssh-8.4p1-4.1.x86_64.rpm installed ok
# Additional rpm output:
# find: '/etc/init.d/rc[35].d': No such file or directory
#
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200441
Bug ID: 1200441
Summary: go1.19 release tracking
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: screening-team-bugs(a)suse.de
Reporter: jkowalczyk(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
go1.19 (expected August 2022) is a major release of Go.
Minor releases of go1.19.x will be provided through August 2023.
This issue tracks go1.19.x releases packaged and submitted initially
to openSUSE:Factory and can be referenced in submissions to
additional repositories.
Go Release Cycle
https://github.com/golang/go/wiki/Go-Release-Cycle
Go Release history
https://golang.org/doc/devel/release.html
--
You are receiving this mail because:
You are on the CC list for the bug.