Bug 709409 - gnome-background-properties goes in busy loop when screen width is more than 4800pixels
Summary: gnome-background-properties goes in busy loop when screen width is more than ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: control-center
Version: 5.6
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 743405 1002709
TreeView+ depends on / blocked
 
Reported: 2011-05-31 16:24 UTC by Yogesh
Modified: 2018-12-01 18:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-07 01:40:08 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Yogesh 2011-05-31 16:24:31 UTC
Description of problem:
gnome-background-properties goes in busy loop when screen width is more than 3500pixels

Version-Release number of selected component (if applicable):
control-center-2.16.0

How reproducible:
always

Steps to Reproduce:
1.Attach 3 monitors with 1600x1200 resolution side by side or use xvfb with resolution 1600x3500
2.Open gnome-background-properties
  
Actual results:
g-b-p goes in busy loop with message
(control-center:31033): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_height > 0' failed
(control-center:31033): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(control-center:31033): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(control-center:31033): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
.. last line more than 2,000,000 times repeated ..

Expected results:
It should run without busy loop

Additional info:

Comment 3 RHEL Program Management 2011-05-31 16:47:13 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2011-09-23 00:38:31 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2012-06-12 01:25:44 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 11 RHEL Program Management 2013-07-24 04:17:00 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 13 Andrius Benokraitis 2013-10-07 01:40:08 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.


Note You need to log in before you can comment on or make changes to this bug.