March 2023 - Epel-packagers-sig - Fedora Mailing-Lists

[Bug 2177993] New: Crash when clicking a modified Google event right after editing it (due to the preview popover)

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2177993 Bug ID: 2177993 Summary: Crash when clicking a modified Google event right after editing it (due to the preview popover) Product: Fedora Version: 38 Status: NEW Component: gnome-calendar Assignee: gnome-sig(a)lists.fedoraproject.org Reporter: kparal(a)redhat.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 Blocks: 2083912 (F38FinalBlocker,FinalBlocker) Target Milestone: --- Link ID: GNOME Gitlab GNOME/gnome-calendar/-/issues/986 Classification: Fedora Please see here: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/986 Proposing for a blocker discussion. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2083912 [Bug 2083912] Fedora 38 Final blocker bug tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177993

1 day, 21 hours

1
5
0 / 0

[Bug 2174149] New: python-claripy-9.2.40 is available

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2174149 Bug ID: 2174149 Summary: python-claripy-9.2.40 is available Product: Fedora Version: rawhide Status: NEW Component: python-claripy Keywords: FutureFeature, Triaged Assignee: mail(a)fabian-affolter.ch Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: epel-packagers-sig(a)lists.fedoraproject.org, mail(a)fabian-affolter.ch, redhat(a)flyn.org Target Milestone: --- Classification: Fedora Releases retrieved: 9.2.40 Upstream release that is considered latest: 9.2.40 Current version/release in rawhide: 9.2.39-1.fc39 URL: https://pypi.org/project/claripy/8.19.10.29 Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release... Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/34905/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-claripy -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2174149

1 week, 3 days

1
62
0 / 0

[Bug 2178639] New: The overview bar does not update with calendar changes

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2178639 Bug ID: 2178639 Summary: The overview bar does not update with calendar changes Product: Fedora Version: 38 Hardware: x86_64 OS: Linux Status: NEW Component: gnome-calendar Assignee: gnome-sig(a)lists.fedoraproject.org Reporter: lruzicka(a)redhat.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: --- Link ID: GNOME Gitlab GNOME/gnome-calendar/-/issues/994 Classification: Fedora Description of problem: This is a tracking bug for Blocker Review purpose. Please refer to the upstream issue to provide details and discuss https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/994 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2178639

1 week, 3 days

1
4
0 / 0

[Bug 2180857] New: [abrt] xapps: gdk_event_source_get_filter_window(): xapp-sn-watcher killed by SIGSEGV

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2180857 Bug ID: 2180857 Summary: [abrt] xapps: gdk_event_source_get_filter_window(): xapp-sn-watcher killed by SIGSEGV Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:8fbbd671c5ec4f9a321a04630b0b55bd7153acf1;VAR IANT_ID=workstation; Component: xapps Assignee: leigh123linux(a)googlemail.com Reporter: shollingsw3(a)gmail.com 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: xapps-2.4.1-2.fc38 Additional info: reporter: libreport-2.17.8 type: CCpp reason: xapp-sn-watcher killed by SIGSEGV journald_cursor: s=384adf4e4a9a4f5dade7f49ff159145d;i=12b89;b=265230d7cf1740ffb73fe9ddce4cc5c7;m=ac8e53d;t=5f77c33f03841;x=909474147fac4e9b executable: /usr/libexec/xapps/sn-watcher/xapp-sn-watcher cmdline: /usr/libexec/xapps/sn-watcher/xapp-sn-watcher cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / uid: 1000 kernel: 6.2.7-300.fc38.x86_64 package: xapps-2.4.1-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: gdk_event_source_get_filter_window Truncated backtrace: Thread no. 1 (8 frames) #0 gdk_event_source_get_filter_window at ../gdk/x11/gdkeventsource.c:123 #1 gdk_event_source_translate_event at ../gdk/x11/gdkeventsource.c:189 #2 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:341 #3 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #4 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #7 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #8 g_main_context_iteration at ../glib/gmain.c:4343 #9 g_application_run at ../gio/gapplication.c:2573 Potential duplicate: bug {crossver_id} -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2180857

1 week, 3 days

1
16
0 / 0

[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

1 week, 3 days

1
17
0 / 0

[Bug 2177240] New: [abrt] gnome-calendar: _g_list_remove_link(): gnome-calendar killed by SIGSEGV

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2177240 Bug ID: 2177240 Summary: [abrt] gnome-calendar: _g_list_remove_link(): gnome-calendar killed by SIGSEGV Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e530748025672067b8c5254252b71b1dacf20785;VAR IANT_ID=workstation; Component: gnome-calendar Assignee: gnome-sig(a)lists.fedoraproject.org Reporter: kparal(a)redhat.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: Calendar crashed while I was searching for events. Version-Release number of selected component: gnome-calendar-44~rc-1.fc38 Additional info: reporter: libreport-2.17.8 type: CCpp reason: gnome-calendar killed by SIGSEGV journald_cursor: s=f14ac85b1ea64de087f79c5fe57e0ea5;i=182ace;b=dea6d4e9b8bd44e39c68387c509e0aff;m=49d32752a;t=5f68ce6f8c258;x=36bd6671bd7dd702 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@12.service rootdir: / uid: 1000 kernel: 6.2.2-301.fc38.x86_64 package: gnome-calendar-44~rc-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: _g_list_remove_link comment: Calendar crashed while I was searching for events. Truncated backtrace: Thread no. 1 (16 frames) #0 _g_list_remove_link at ../glib/glist.c:563 #1 g_list_remove_link at ../glib/glist.c:675 #2 g_queue_unlink at ../glib/gqueue.c:847 #3 g_queue_delete_link at ../glib/gqueue.c:869 #4 queue_event_data at ../src/core/gcal-timeline.c:163 #5 on_calendar_monitor_event_removed_cb at ../src/core/gcal-timeline.c:559 #6 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910 #7 _g_closure_invoke_va at ../gobject/gclosure.c:895 #10 remove_events_outside_range at ../src/core/gcal-calendar-monitor.c:1005 #11 gcal_calendar_monitor_set_range at ../src/core/gcal-calendar-monitor.c:1349 #12 update_range at ../src/core/gcal-timeline.c:289 #13 gcal_timeline_add_subscriber at ../src/core/gcal-timeline.c:995 #14 search_func at ../src/search/gcal-search-engine.c:103 #15 g_task_thread_pool_thread at ../gio/gtask.c:1531 #17 g_thread_proxy at ../glib/gthread.c:831 #19 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Potential duplicate: bug {crossver_id} -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177240

1 week, 3 days

1
15
0 / 0

[Bug 2177238] New: [abrt] gnome-calendar: _gtk_widget_is_sensitive(): gnome-calendar killed by SIGSEGV

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2177238 Bug ID: 2177238 Summary: [abrt] gnome-calendar: _gtk_widget_is_sensitive(): gnome-calendar killed by SIGSEGV Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:a5a4a621fe947a1a3c2837111fa5d4fd6f4c165d;VAR IANT_ID=workstation; Component: gnome-calendar Assignee: gnome-sig(a)lists.fedoraproject.org Reporter: kparal(a)redhat.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 edited an event and typed "Prague" into the Location field, then hit Save, and it crashed. Version-Release number of selected component: gnome-calendar-44~rc-1.fc38 Additional info: reporter: libreport-2.17.8 type: CCpp reason: gnome-calendar killed by SIGSEGV journald_cursor: s=f14ac85b1ea64de087f79c5fe57e0ea5;i=182149;b=dea6d4e9b8bd44e39c68387c509e0aff;m=415c9dd48;t=5f68c5f902a76;x=50a38c7ce484216f 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.2-301.fc38.x86_64 package: gnome-calendar-44~rc-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-calendar gnome-calendar-44~rc-1.fc38.x86_64 (Fedora Project) 1678436218 backtrace_rating: 4 crash_function: _gtk_widget_is_sensitive comment: I edited an event and typed "Prague" into the Location field, then hit Save, and it crashed. Truncated backtrace: Thread no. 1 (16 frames) #0 _gtk_widget_is_sensitive at ../gtk/gtkwidgetprivate.h:482 #1 gtk_propagate_event_internal.isra.0 at ../gtk/gtkmain.c:1918 #2 gtk_main_do_event at ../gtk/gtkmain.c:1703 #3 surface_event at ../gtk/gtkwindow.c:4747 #4 _gdk_marshal_BOOLEAN__POINTERv at gdk/gdkmarshalers.c:302 #5 gdk_surface_event_marshallerv at ../gdk/gdksurface.c:463 #6 _g_closure_invoke_va at ../gobject/gclosure.c:895 #9 gdk_surface_handle_event.isra.0 at ../gdk/gdksurface.c:2956 #10 gdk_surface_ensure_motion at ../gdk/gdksurface.c:2473 #11 gdk_surface_flush_events at ../gdk/gdksurface.c:2484 #13 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802 #16 _gdk_frame_clock_emit_flush_events at ../gdk/gdkframeclock.c:668 #17 gdk_frame_clock_flush_idle at ../gdk/gdkframeclockidle.c:369 #21 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #22 g_main_context_iteration at ../glib/gmain.c:4343 #23 g_application_run at ../gio/gapplication.c:2573 Potential duplicate: bug {crossver_id} -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177238

1 week, 3 days

1
15
0 / 0

[Bug 2120537] New: 'bodhi updates new' does not report error/warning when setting karma limit below minimal value for package in critical path

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2120537 Bug ID: 2120537 Summary: 'bodhi updates new' does not report error/warning when setting karma limit below minimal value for package in critical path Product: Fedora Version: rawhide Status: NEW Component: bodhi-client Assignee: thrcka(a)redhat.com Reporter: zdohnal(a)redhat.com CC: aurelien(a)bompard.org, epel-packagers-sig(a)lists.fedoraproject.org, lenka(a)sepu.cz, thrcka(a)redhat.com Target Milestone: --- Classification: Fedora Hi, I was surprised why my bodhi update ( https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 ) doesn't show an option for pushing into stable or why the update is not in stable already, because the positive karma limit (1) is reached. On #fedora-devel IRC channel kalev answered: (09:34:34 AM) zdohnal: Hi all, do you have an idea what blocks this update https://bodhi.fedoraproject.org/updates/FEDORA-2022-6f5e420e52 from being pushed to the stable? (09:38:32 AM) kalev: zdohnal: looks like it's marked as critical path and because of that, it needs minimum of +2 karma to be pushed to stable (09:40:19 AM) GrannyGoose left the room (quit: Quit: Going offline, see ya! (www.adiirc.com)). (09:41:00 AM) zdohnal: kalev: aha - good to know. However bodhi-client should give me error when I set karma below this limit... According to the conversation, there is karma limit for components in critical path and it is higher - 2 - than the limit set by me - 1, which causes confusion. I use 'bodhi updates new' CLI command for creating updates, and I didn't see any error/warning regarding setting the karma limit too low. IMHO CLI command has to fail if user tries to set the limit too low, and bodhi web UI should handle this in some way as well. Would you mind looking into it? Version-Release number of selected component (if applicable): bodhi-client-6.0.1-4.fc37 How reproducible: always Steps to Reproduce: 1. $ bodhi updates new --type bugfix --close-bugs --request testing --autokarma --autotime --stable-karma 1 --unstable-karma -1 --notes "Update for component in critical path" <critical-component-1.2.3-1.fc37> Actual results: No error or warning, bodhi web ui shows user defined limit and the update has karma to fulfill the limit, but the update is not pushed into stable. Expected results: Give error (in both interfaces - CLI and Web UI) if user wants to set lower karma limit than it is required on the package. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2120537

1 week, 3 days

1
1
0 / 0

[Bug 2093731] New: zbarimg does not read a Code 128 barcode

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2093731 Bug ID: 2093731 Summary: zbarimg does not read a Code 128 barcode Product: Fedora Version: 36 Status: NEW Component: zbar Severity: high Assignee: gwync(a)protonmail.com Reporter: cristian.ciupitu(a)yahoo.com QA Contact: extras-qa(a)fedoraproject.org CC: dougsland(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, gwync(a)protonmail.com, mchehab(a)infradead.org, mr.marcelo.barbosa(a)gmail.com, negativo17(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1886898 --> https://bugzilla.redhat.com/attachment.cgi?id=1886898&action=edit Code 128 barcode Description of problem: zbarimg does not read a Code 128 barcode Version-Release number of selected component (if applicable): zbar-0.23.90-1.fc36.x86_64 How reproducible: Every time Steps to Reproduce: 1. zbarimg barcode.png Actual results: scanned 0 barcode symbols from 1 images in 0 seconds WARNING: barcode data was not detected in some image(s) Things to check: - is the barcode type supported? Currently supported symbologies are: . EAN/UPC (EAN-13, EAN-8, EAN-2, EAN-5, UPC-A, UPC-E, ISBN-10, ISBN-13) . DataBar, DataBar Expanded . Code 128 . Code 93 . Code 39 . Codabar . Interleaved 2 of 5 . QR code . SQ code . PDF 417 - is the barcode large enough in the image? - is the barcode mostly in focus? - is there sufficient contrast/illumination? - If the symbol is split in several barcodes, are they combined in one image? - Did you enable the barcode type? some EAN/UPC codes are disabled by default. To enable all, use: $ zbarimg -S*.enable <files> Please also notice that some variants take precedence over others. Due to that, if you want, for example, ISBN-10, you should do: $ zbarimg -Sisbn10.enable <files> Expected results: (Code 128) 755897201062022179.73 Additional info: -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2093731

1 week, 3 days

1
5
0 / 0

[Bug 2182602] New: CVE-2023-0466 openssl3: openssl: Certificate policy check not enabled [epel-8]

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2182602 Bug ID: 2182602 Summary: CVE-2023-0466 openssl3: openssl: Certificate policy check not enabled [epel-8] Product: Fedora EPEL Version: epel8 Status: NEW Component: openssl3 Keywords: Security, SecurityTracking Severity: low Priority: low Assignee: michel(a)michel-slm.name Reporter: trathi(a)redhat.com CC: epel-packagers-sig(a)lists.fedoraproject.org, michel(a)michel-slm.name Target Milestone: --- Classification: Fedora More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2182565 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2182602

2 weeks, 2 days

1
6
0 / 0

2024

2023

2022

2021

Epel-packagers-sig March 2023