[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 month
[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 month
[Bug 2240040] New: [abrt] blender: module(): gltf2_blender_conversion.py:5:<module>:ModuleNotFoundError: No module named 'numpy'
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2240040
Bug ID: 2240040
Summary: [abrt] blender: module():
gltf2_blender_conversion.py:5:<module>:ModuleNotFoundE
rror: No module named 'numpy'
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:69a60ba0c5ea2d290eef274755b30460e5715da6;VAR
IANT_ID=workstation;
Component: blender
Assignee: luya_tfz(a)thefinalzone.net
Reporter: redhat.vb4r3(a)passinbox.com
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
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
blender-1:3.5.1-3.fc38
Additional info:
reporter: libreport-2.17.11
kernel: 6.4.14-200.fc38.x86_64
cmdline: /usr/bin/blender /home/seth/obama/obama_freedom_device.blend
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Nautilus@5.service
uid: 1000
reason: gltf2_blender_conversion.py:5:<module>:ModuleNotFoundError: No
module named 'numpy'
executable: /usr/bin/blender
type: Python3
package: blender-1:3.5.1-3.fc38
runlevel: N 5
exception_type: ModuleNotFoundError
crash_function: module
interpreter: blender-3.5.1-3.fc38.x86_64
Truncated backtrace:
#1
[/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/com/gltf2_blender_conversion.py:5]
<module>
#2
[/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_get.py:8]
<module>
#3
[/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather_cache.py:6]
<module>
#4
[/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather_nodes.py:10]
<module>
#5
[/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather.py:8]
<module>
#6
[/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/blender/exp/gltf2_blender_export.py:11]
<module>
#7 [/usr/share/blender/3.5/scripts/addons/io_scene_gltf2/__init__.py:583]
execute
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2240040
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 month, 3 weeks