https://bugzilla.suse.com/show_bug.cgi?id=1196613
Bug ID: 1196613
Summary: pam-config doesn't handle /usr/etc properly
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: fcrozat(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
This might be a follow-up of bsc#1187091
on a freshly installed openSUSE MicroOS desktop, I've tried to enable
pam_config:
pam-config --service login -a --mount
pam-config complained there was no /etc/pam.d/login and created one, which was
broken (couldn't login anymore)
It should have checked the presence of /usr/etc/pam.d/login and use this file
as "reference".
Workaround:
cp /usr/etc/pam.d/login /etc/pam.d/login
and run pam-config
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1204074https://bugzilla.suse.com/show_bug.cgi?id=1204074#c8
--- Comment #8 from Callum Farmer <gmbr3(a)opensuse.org> ---
(In reply to Klaus K�mpf from comment #6)
> Hmm, chromium directly links with libavcodec59 (bad !) while Firefox
> (apparently) loads this library dynamically (good !).
>
> And loading a working libavcodec library is the purpose of
> mozilla-libavcodec58_91.patch - which doesn't work. :-(
No that's not how things work as in most cases linking is better to avoid
symbol errors. The codec issues are there because you are running the openSUSE
version and not the Packman version, how the library is loaded has no effect.
The issue is your zypper repo config, you need to increase priority of packman
above (lower number) openSUSE-OSS.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1204074https://bugzilla.suse.com/show_bug.cgi?id=1204074#c7
--- Comment #7 from Wolfgang Rosenauer <wolfgang(a)rosenauer.org> ---
The purpose of the patch is just to add weird API incompatible versioned
"inbetween" releases of ffmpeg.
The list which is modified is the order Firefox tries to load the libavcodec
version.
As 59 is the first one mentioned it will be used. Only if not available it
steps down the list.
And as explained in my first comment Firefox is not checking for supported
codecs. It just checks if it can load the versioned library.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1163046https://bugzilla.suse.com/show_bug.cgi?id=1163046#c25
Tom���� Ba��ant <tbazant(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
CC| |tbazant(a)suse.com
Resolution|--- |NORESPONSE
--- Comment #25 from Tom���� Ba��ant <tbazant(a)suse.com> ---
Idle for too long, closing, reopen if needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203968https://bugzilla.suse.com/show_bug.cgi?id=1203968#c2
Richard Farthing <rf(a)keynet-technology.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Richard Farthing <rf(a)keynet-technology.com> ---
Latest kernel was OK.
However I then reverted to test with 5.14.21.15400.24.21.2 again, and now that
is also working as expected, after using earlier kernel 5.14.21.15400.22.1 for
a few days with autoupdates etc. Something must have has changed, so I think
this is no longer traceable - I closed it
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1204074https://bugzilla.suse.com/show_bug.cgi?id=1204074#c6
--- Comment #6 from Klaus K�mpf <kkaempf(a)suse.com> ---
Hmm, chromium directly links with libavcodec59 (bad !) while Firefox
(apparently) loads this library dynamically (good !).
And loading a working libavcodec library is the purpose of
mozilla-libavcodec58_91.patch - which doesn't work. :-(
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202292
Bug ID: 1202292
Summary: [staging][ftbfs] ceph fails to build against fmt 9.0
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: dimstar(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
fmt 9.0 has been submitted for inclusion into Factory.
During the staging process we have observed ceph failing to build
(currently logs available at
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:…
- but that won't stay forever)
[ 471s] In file included from /usr/include/fmt/format.h:48,
[ 471s] from
/home/abuild/rpmbuild/BUILD/ceph-16.2.9-538-g9de83fa4064/src/tools/neorados.cc:31:
[ 471s] /usr/include/fmt/core.h: In instantiation of 'constexpr
fmt::v9::detail::value<Context> fmt::v9::detail::make_value(T&&) [with Context
= fmt::v9::basic_format_context<fmt::v9::appender, char>; T =
boost::program_options::options_description&]':
[ 471s] /usr/include/fmt/core.h:1753:29: required from 'constexpr
fmt::v9::detail::value<Context> fmt::v9::detail::make_arg(T&&) [with bool
IS_PACKED = true; Context = fmt::v9::basic_format_context<fmt::v9::appender,
char>; type <anonymous> = fmt::v9::detail::type::custom_type; T =
boost::program_options::options_description&; typename
std::enable_if<IS_PACKED, int>::type <anonymous> = 0]'
[ 471s] /usr/include/fmt/core.h:1877:77: required from 'constexpr
fmt::v9::format_arg_store<Context, Args>::format_arg_store(T&& ...) [with T =
{boost::program_options::options_description&}; Context =
fmt::v9::basic_format_context<fmt::v9::appender, char>; Args =
{boost::program_options::options_description}]'
[ 471s] /usr/include/fmt/core.h:1894:38: required from 'constexpr
fmt::v9::format_arg_store<Context, typename std::remove_cv<typename
std::remove_reference<Args>::type>::type ...> fmt::v9::make_format_args(Args&&
...) [with Context = basic_format_context<appender, char>; Args =
{boost::program_options::options_description&}]'
[ 471s] /usr/include/fmt/core.h:3251:44: required from 'void
fmt::v9::print(format_string<T ...>, T&& ...) [with T =
{boost::program_options::options_description&}; format_string<T ...> =
basic_format_string<char, boost::program_options::options_description&>]'
[ 471s]
/home/abuild/rpmbuild/BUILD/ceph-16.2.9-538-g9de83fa4064/src/tools/neorados.cc:324:17:
required from here
[ 471s] /usr/include/fmt/core.h:1733:7: error: static assertion failed: Cannot
format an argument. To make type T formattable provide a formatter<T>
specialization: https://fmt.dev/latest/api.html#udt
[ 471s] 1733 | formattable,
[ 471s] | ^~~~~~~~~~~
--
You are receiving this mail because:
You are on the CC list for the bug.