[Bug 2189353] New: GNOME: In the calendar at the top, clicking on any day of the next month results in a window with the background cut in half
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2189353
Bug ID: 2189353
Summary: GNOME: In the calendar at the top, clicking on any day
of the next month results in a window with the
background cut in half
Product: Fedora
Version: 38
Hardware: x86_64
OS: Linux
Status: NEW
Component: gnome-calendar
Severity: low
Assignee: gnome-sig(a)lists.fedoraproject.org
Reporter: franceopf(a)gmail.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
Created attachment 1959662
--> https://bugzilla.redhat.com/attachment.cgi?id=1959662&action=edit
Screenshots depicting the issue
Description of problem:
In the calendar at the top, as long as you click on any day of the current
month, everything is fine, however, as soon as you click on a day of the next
month, the window's background is far too short and looks as if it was cut in
half.
Since for graphical issues a screenshot is worth more than a thousand words,
check this out:
https://i.imgur.com/Htgouda.png
https://i.imgur.com/xYuSrs3.png
https://i.imgur.com/4xrng2C.png
As you can see, as soon as I clicked on the first of May, the calendar moved
from April to May however the whole background is being rendered incorrectly as
it should really be longer.
Version-Release number of selected component (if applicable):
GNOME 44.0, X11, Fedora 38 x64
Steps to Reproduce:
1. Click on the clock/date on the top to open up the calendar
2. Click on any day of the next month in the calendar
Actual results:
The window is cut in half
Expected results:
The window is displayed correctly
Additional info:
Linux 6.2.12-300.fc38.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2189353
1 week
[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
[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
[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
[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
[Bug 2282190] New: [abrt] gnome-calendar: gsk_gpu_rect_to_float(): gnome-calendar killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2282190
Bug ID: 2282190
Summary: [abrt] gnome-calendar: gsk_gpu_rect_to_float():
gnome-calendar killed by SIGSEGV
Product: Fedora
Version: rawhide
Hardware: aarch64
Status: NEW
Whiteboard: abrt_hash:271004e47371354f8e804bfd96875745030b3467;VAR
IANT_ID=workstation;
Component: gnome-calendar
Assignee: gnome-sig(a)lists.fedoraproject.org
Reporter: lbrabec(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
Version-Release number of selected component:
gnome-calendar-46.1-1.fc41
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: gnome-calendar killed by SIGSEGV
journald_cursor:
s=4be9692be83b4b349e825c71185a4294;i=63cb;b=d15a528605f64006a121d31cee39321a;m=a9ff144;t=618f4202f1e62;x=50165e49d77b271e
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.9.0-64.fc41.aarch64
package: gnome-calendar-46.1-1.fc41
runlevel: N 5
backtrace_rating: 4
crash_function: gsk_gpu_rect_to_float
Truncated backtrace:
Thread no. 1 (24 frames)
#0 gsk_gpu_rect_to_float at ../gsk/gskrectprivate.h:129
#1 gsk_gpu_color_op at ../gsk/gpu/gskgpucolorop.c:67
#2 gsk_gpu_node_processor_add_color_node at
../gsk/gpu/gskgpunodeprocessor.c:1885
#3 gsk_gpu_node_processor_add_container_node at
../gsk/gpu/gskgpunodeprocessor.c:3815
#7 gsk_gpu_node_processor_process at ../gsk/gpu/gskgpunodeprocessor.c:400
#8 gsk_gpu_frame_record_rect at ../gsk/gpu/gskgpuframe.c:573
#9 gsk_gpu_frame_record at ../gsk/gpu/gskgpuframe.c:606
#10 gsk_gpu_frame_render at ../gsk/gpu/gskgpuframe.c:666
#11 gsk_gpu_renderer_render at ../gsk/gpu/gskgpurenderer.c:411
#12 gsk_renderer_render at ../gsk/gskrenderer.c:510
#13 gtk_widget_render at ../gtk/gtkwidget.c:11997
#14 surface_render at ../gtk/gtkwindow.c:4752
#15 _gdk_marshal_BOOLEAN__BOXEDv at gdk/gdkmarshalers.c:130
#16 _g_closure_invoke_va at ../gobject/gclosure.c:897
#17 signal_emit_valist_unlocked at ../gobject/gsignal.c:3424
#20 gdk_surface_paint_on_clock at ../gdk/gdksurface.c:1370
#22 _g_closure_invoke_va at ../gobject/gclosure.c:897
#23 signal_emit_valist_unlocked at ../gobject/gsignal.c:3424
#26 _gdk_frame_clock_emit_paint at ../gdk/gdkframeclock.c:736
#27 gdk_frame_clock_paint_idle at ../gdk/gdkframeclockidle.c:641
#30 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152
#31 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217
#32 g_main_context_iteration at ../glib/gmain.c:4282
#33 g_application_run at ../gio/gapplication.c:2712
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2282190
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 week
