[Bug 2252179] New: arch-install-scripts: does not install from EPEL 8/9
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2252179
Bug ID: 2252179
Summary: arch-install-scripts: does not install from EPEL 8/9
Product: Fedora EPEL
Version: epel9
Status: NEW
Component: arch-install-scripts
Assignee: zbyszek(a)in.waw.pl
Reporter: carl(a)redhat.com
CC: ecurtin(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
i(a)cicku.me, zbyszek(a)in.waw.pl
Target Milestone: ---
Classification: Fedora
Description of problem:
arch-install-scripts does not install from EPEL 8 or EPEL 9.
Version-Release number of selected component (if applicable):
arch-install-scripts-28-2.el8
arch-install-scripts-28-2.el9
How reproducible:
always
Steps to Reproduce:
1. dnf install arch-install-scripts
Actual results:
Error:
Problem: conflicting requests
- nothing provides archlinux-keyring needed by
arch-install-scripts-28-2.el8.noarch from epel
- nothing provides pacman needed by arch-install-scripts-28-2.el8.noarch from
epel
Error:
Problem: conflicting requests
- nothing provides archlinux-keyring needed by
arch-install-scripts-28-2.el9.noarch from epel
- nothing provides pacman needed by arch-install-scripts-28-2.el9.noarch from
epel
Expected results:
successful installation
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2252179
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
57 minutes
[Bug 2277782] New: Package older clang-formats on newer Fedoras
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2277782
Bug ID: 2277782
Summary: Package older clang-formats on newer Fedoras
Product: Fedora
Version: 39
OS: Linux
Status: NEW
Component: clang16
Keywords: RFE
Severity: medium
Assignee: tuliom(a)redhat.com
Reporter: alyssa(a)rosenzweig.io
CC: epel-packagers-sig(a)lists.fedoraproject.org,
fedora-llvm-team(a)lists.fedoraproject.org,
michel(a)michel-slm.name, tuliom(a)redhat.com
Target Milestone: ---
Classification: Fedora
Fedora packages clang-format, an automatic C/C++ code reformatting tool used by
various FOSS projects, including the kernel and Mesa. Some project's CI systems
enforce developer use of clang-format to produce a consistent style across the
code base.
However, clang-format's output is not stable from version to version, as
upstream clang-format tweaks affect the results. Projects therefore pin a
single "blessed" version of clang-format that all contributors use.
Other distributions like Debian package simultaneously multiple versions of
LLVM (and hence multiple version suffixed clang-formats), so contributors can
install whatever the agreed upon version is without needing the whole team to
use the same distro. Unfortunately, Fedora only packages a single latest clang
version... and as soon as the Fedora LLVM is newer than what the project was
using, boom! formatting changes randomly and the developer can no longer
contribute.
Therefore, this is a request to package older clang-formats even on newer
Fedoras. For my own use case, I need clang-format-16 on F39 (soon F40), since
that's the version FEX-Emu pins. But F39 only has clang-format-17, which is
incompatible.
Is it reasonable to include the older binaries in the newer Fedoras? If not,
what is a reasonable workaround (that doesn't require switching from Fedora to
another distro)?
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2277782
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 hour, 36 minutes
[Bug 2180613] New: Feature Request: compile blender with oneAPI support for Cycles
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2180613
Bug ID: 2180613
Summary: Feature Request: compile blender with oneAPI support
for Cycles
Product: Fedora
Version: 38
Hardware: x86_64
OS: Linux
Status: NEW
Component: blender
Severity: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: koppe(a)posteo.de
QA Contact: extras-qa(a)fedoraproject.org
CC: code(a)musicinmybrain.net,
design-devel(a)lists.fedoraproject.org,
epel-packagers-sig(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com, promac(a)gmail.com
Target Milestone: ---
Classification: Fedora
With Intel Level Zero now available in the Fedora repositories, I think the
version of Blender shipped with Fedora should be compiled with Cycles oneAPI
support for Intel GPUs enabled, currently only CUDA and HIP are enabled
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2180613
11 hours, 15 minutes
[Bug 2196198] New: Program crashes when trying to open preferences due to wayland protocol error
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2196198
Bug ID: 2196198
Summary: Program crashes when trying to open preferences due to
wayland protocol error
Product: Fedora
Version: 38
Hardware: x86_64
OS: Linux
Status: NEW
Component: tikzit
Keywords: Desktop
Severity: high
Assignee: redhat(a)flyn.org
Reporter: fedora(a)joshuanoeske.de
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
redhat(a)flyn.org
Target Milestone: ---
Classification: Fedora
When I try to open the preferences, the whole application crashes. I can
reproduce that reliably. The output of tikzit to stdout/stderr is the
following:
QSocketNotifier: Can only be used with threads started with QThread
Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is
created.
QSocketNotifier: Can only be used with threads started with QThread
The Wayland connection experienced a fatal error: Protocol error
Reproducible: Always
Steps to Reproduce:
1. Open TikzIt using Wayland as display server.
2. Open preferences via toolbar.
Actual Results:
Whole program crashes
Expected Results:
Preferences open
My system is fully upgraded, so I am using the qt packages version 6.5.0 and
Gnome/mutter 44.1. I have also tried downgrading Gnome and mutter to version
44.0, as well as the qt packages to 6.4.3, but both did not help to solve the
problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2196198
11 hours, 51 minutes
[Bug 2196117] New: [abrt] cinnamon-screensaver: position_overlay_child(): stage.py:862:position_overlay_child:SystemError: gi.FunctionInfo(get_monitor_geometry, bound=<CScreensaver.Screen object at 0x7f9fbe409000 (CsScreen at 0x5594ca39bac0)>) returned a result with an exce
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2196117
Bug ID: 2196117
Summary: [abrt] cinnamon-screensaver: position_overlay_child():
stage.py:862:position_overlay_child:SystemError:
gi.FunctionInfo(get_monitor_geometry,
bound=<CScreensaver.Screen object at 0x7f9fbe409000
(CsScreen at 0x5594ca39bac0)>) returned a result with
an exce
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:b73795c1f0214695c21efe65b7cad5f1dc3879a5;VAR
IANT_ID=cinnamon;
Component: cinnamon-screensaver
Assignee: leigh123linux(a)googlemail.com
Reporter: dani(a)letai.org.il
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
leigh123linux(a)googlemail.com, riehecky(a)fnal.gov
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
cinnamon-screensaver-5.6.3-2.fc38
Additional info:
reporter: libreport-2.17.9
kernel: 6.2.14-300.fc38.x86_64
cmdline: cinnamon-screensaver '' '' '' '' '' '' '' '' '' '' '' '' '' ''
'' '' '' '' '' '' '' '' '' '' '' ''
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dorg.cinnamon.ScreenSaver.slice/dbus-:1.2-org.cinnamon.ScreenSaver@4.service
uid: 1000
reason: stage.py:862:position_overlay_child:SystemError:
gi.FunctionInfo(get_monitor_geometry, bound=<CScreensaver.Screen object at
0x7f9fbe409000 (CsScreen at 0x5594ca39bac0)>) returned a result with an
exception set
executable: /usr/bin/cinnamon-screensaver
type: Python3
package: cinnamon-screensaver-5.6.3-2.fc38
runlevel: N 5
exception_type: SystemError
crash_function: position_overlay_child
interpreter: cinnamon-screensaver-5.6.3-2.fc38.x86_64
Truncated backtrace:
stage.py:862:position_overlay_child:SystemError:
gi.FunctionInfo(get_monitor_geometry, bound=<CScreensaver.Screen object at
0x7f9fbe409000 (CsScreen at 0x5594ca39bac0)>) returned a result with an
exception set
TypeError: could not get typecode from object
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/share/cinnamon-screensaver/stage.py", line 862, in
position_overlay_child
monitor_rect = status.screen.get_monitor_geometry(current_monitor)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SystemError: gi.FunctionInfo(get_monitor_geometry, bound=<CScreensaver.Screen
object at 0x7f9fbe409000 (CsScreen at 0x5594ca39bac0)>) returned a result with
an exception set
Local variables in innermost frame:
self: <stage.Stage object at 0x7f9fbe409080 (stage+Stage at 0x5594ca5656b0)>
overlay: <Gtk.Overlay object at 0x7f9fcebba380 (GtkOverlay at 0x5594ca4354f0)>
child: <clock.ClockWidget object at 0x7f9fbe413780 (clock+ClockWidget at
0x5594ca487a70)>
allocation: <Gdk.Rectangle object at 0x7f9fbe3e6270 (GdkRectangle at
0x7ffed0ca29b0)>
min_rect: <Gtk.Requisition object at 0x7f9fbe3e62d0 (GtkRequisition at
0x7f9fb4004170)>
nat_rect: <Gtk.Requisition object at 0x7f9fbe3e6330 (GtkRequisition at
0x7f9fb4001d70)>
current_monitor: 0
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2196117
11 hours, 51 minutes
[Bug 2196063] New: [abrt] gnome-calendar: on_calendar_monitor_completed_cb(): gnome-calendar killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
Bug ID: 2196063
Summary: [abrt] gnome-calendar:
on_calendar_monitor_completed_cb(): gnome-calendar
killed by SIGABRT
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:774e75e519e48b0b8e6e9562ea89da0b5fc6e38a;VAR
IANT_ID=workstation;
Component: gnome-calendar
Assignee: gnome-sig(a)lists.fedoraproject.org
Reporter: ice_qub3(a)protonmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
igor.raits(a)gmail.com, klember(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I tried adding a protonmail calander share link into the calander app, but it
crashed
Version-Release number of selected component:
gnome-calendar-44.1-1.fc38
Additional info:
reporter: libreport-2.17.9
type: CCpp
reason: gnome-calendar killed by SIGABRT
journald_cursor:
s=5f6cdd2ccacb47d980c17e321cba366e;i=4dce;b=9328860e87ea40dda685ecb062e5f865;m=80eac649;t=5fb1c8f41e320;x=1d48fa4e450888e5
executable: /usr/bin/gnome-calendar
cmdline: /usr/bin/gnome-calendar --gapplication-service
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Calendar@0.service
rootdir: /
uid: 1000
kernel: 6.2.14-300.fc38.x86_64
package: gnome-calendar-44.1-1.fc38
runlevel: N 5
dso_list: /usr/bin/gnome-calendar gnome-calendar-44.1-1.fc38.x86_64
(Fedora Project) 1683470020
backtrace_rating: 4
crash_function: on_calendar_monitor_completed_cb
comment: I tried adding a protonmail calander share link into the
calander app, but it crashed
Truncated backtrace:
Thread no. 1 (9 frames)
#6 on_calendar_monitor_completed_cb at ../src/core/gcal-timeline.c:579
#8 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3812
#12 g_object_notify_by_spec_internal at ../gobject/gobject.c:1552
#13 g_object_notify_by_pspec at ../gobject/gobject.c:1658
#14 set_complete at ../src/core/gcal-calendar-monitor.c:1044
#15 complete_in_idle_cb at ../src/core/gcal-calendar-monitor.c:1167
#19 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
#20 g_main_context_iteration at ../glib/gmain.c:4343
#21 g_application_run at ../gio/gapplication.c:2573
Potential duplicate: bug 1883681
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2196063
11 hours, 51 minutes