After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 83250 - [Solaris-Multihead] The background options do not work always.
[Solaris-Multihead] The background options do not work always.
Status: VERIFIED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: Background
unspecified
Other Solaris
: High major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks: 85302
 
 
Reported: 2002-05-28 14:18 UTC by Avirupa Chakrabarty
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Avirupa Chakrabarty 2002-05-28 14:18:47 UTC
Reproducibility: Sometimes
 In the multihead system the background option do not work always when 
either one of the monitors or both has 8 bit display.
1. In the background properties window select the 
options "wallpaper", "centered", "stretched" or "scaled" with any image 
file selected as the background. The results do not come up as expected.
2.In the background properties window select the options "solid 
colour", "horizontal gradient" or "vertical gradient" with "no Picture" 
selected as the background. The rsults do not come up as expected.

The application crashes once during selecting the options too.

The stack trace follows:
  • #0 _waitid
    from /usr/lib/libc.so.1
  • #1 _waitpid
    from /usr/lib/libc.so.1
  • #2 waitpid
    from /usr/lib/libthread.so.1
  • #3 __sighndlr
    from /usr/lib/libthread.so.1
  • #4 <signal handler called>
  • #5 __sigprocmask
    from /usr/lib/libthread.so.1
  • #6 _resetsig
    from /usr/lib/libthread.so.1
  • #7 _sigon
    from /usr/lib/libthread.so.1
  • #8 _thrp_kill
    from /usr/lib/libthread.so.1
  • #9 raise
    from /usr/lib/libc.so.1
  • #10 abort
    from /usr/lib/libc.so.1
  • #11 g_logv
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #12 g_log
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #13 gdk_x_error
    from /opt/gnome-2.0/lib/libgdk-x11-
  • #14 bonobo_x_error_handler
    from /opt/gnome-2.0/lib/libbonoboui-2.so.0
  • #15 _XError
    from /usr/lib/libX11.so.4
  • #16 _XEventsQueued
    from /usr/lib/libX11.so.4
  • #17 XPending
    from /usr/lib/libX11.so.4
  • #18 gdk_check_xpending
    from /opt/gnome-2.0/lib/libgdk-x11-2.0.so.0
  • #19 gdk_event_prepare
    from /opt/gnome-2.0/lib/libgdk-x11-2.0.so.0
  • #20 g_main_context_prepare
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #21 g_main_context_iterate
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /opt/gnome-2.0/lib/libglib-
  • #23 gtk_main
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #24 main

Comment 1 Luis Villa 2002-05-28 17:14:21 UTC
I assume that this is with the gtk2 multihead patches? Also, symbols
would be good. Tentatively marking high but if this is caused by the
gtk2 multihead stuff it probably shouldn't be high until that hits
widespread deployment.
Comment 2 jacob berkman 2002-05-28 19:11:07 UTC
for x errors, a stack trace when run with --sync is required.

which date was this taken from?
Comment 3 Avirupa Chakrabarty 2002-05-29 04:58:27 UTC
I have done the testing on the source code taken on 23rd of May.
Comment 4 jacob berkman 2002-05-29 20:37:33 UTC
ok, my fixes went in on the 21st.

please provide a trace when running with --sync
Comment 5 Avirupa Chakrabarty 2002-06-03 05:07:54 UTC
I am not being able to reproduce the crash so that I can take the 
stack trace. However the problem of the options not working still 
persists. I had filed the bug on the basis of the testing on the code 
of 23rd May. Today I tested on the source code of 27th May. 

Still the options stop working after some tries but crashing does not 
happen. I had run gnome-control-center with the --sync option.
Comment 6 Luis Villa 2002-06-03 15:14:56 UTC
Closing this one; what # is the 'options do not work' bug or is this it?
Comment 7 Avirupa Chakrabarty 2002-06-03 15:39:45 UTC
But the problem is there, specially when any one of the displays on 
the mutihead is a 8 bit display. I could not reproduce the crash today 
but problems I have mentioned above in steps 1 and 2 are still there. 
try to play with the options in the 'Background Preferences' dialog 
window and they stop working after some time.
Comment 8 Luis Villa 2002-06-03 16:15:34 UTC
Ah, I misunderstood and thought you'd opened another bug for the other
issues.
Comment 9 jacob berkman 2002-06-05 21:02:53 UTC
i can't reproduce this at all...

do i need to only have an 8-bit visual, or if the root window is 8-bit
is that ok?

Comment 10 Avirupa Chakrabarty 2002-06-06 03:50:37 UTC
Preferably the root window should be a 8 bit one at least if not both.
It happens here if keep on changing the options from wallpaper to 
center and then stretched, scaled and no picture. After some time 
whatever option I choose it does not come up.
Comment 11 jacob berkman 2002-06-06 16:31:26 UTC
if you wait a while, do the changes come up?

i still cannot reproduce this on a single head system.
Comment 12 Avirupa Chakrabarty 2002-06-07 04:32:50 UTC
I think  you will be able to reproduce it of a multihead system with 
the primary display at least set to 8 bit.
Comment 13 Luis Villa 2002-07-02 15:13:34 UTC
[Search for 'luis spamming' to catch every instance of this email.]
In order to better track Sun's bugs for Sun and Ximian's internal use, I've
added a temporary keyword to some bugs. I apologize for the spam, and for the
use of an additional keyword, but this is the best way for Sun to track 'it's'
bugs without interfering with the community's own triage and bug behavior. If
you have any questions or objections, please drop me a note at louie@ximian.com
or email bugmaster@gnome.org for more open discussion.
Comment 14 Mamatha 2002-08-14 04:01:49 UTC
Gnome 2.0 beta2 build2, Solaris sparc 8 (multihead)
The background options not working properly .
I)
2. Try to change the background of the first screen from background 
properties window. The change is getting reflected to both the 
windows.

II)
In the background properties window select the 
options "wallpaper", "centered", "stretched" ,"scaled" or "No 
picture" with any image  sometimes it crashes.


stack Trace:

current	thread:	t@1
=>[1] _waitid(0x0, 0xcdb, 0xffbedb40, 0x3, 0x540d0, 0x2), at 
0xfe09c65c
  [2] _waitpid(0x0, 0xffbedc44,	0x0, 0xffbedc44, 0xfeba8bac, 0x2688), 
at 0xfe056690
  [3] waitpid(0x6, 0x354c, 0x51638, 0xfe3cd0e8,	0xff34a65c, 0x4800), 
at	0xfe3dab00
  [4] __sighndlr(0x6, 0xffbee098, 0xffbedde0, 0xff2f11a0, 0x3c554, 
0x3c544), at	0xfe3db82c
  [5] sigacthandler(0x6, 0x3c4b0, 0x0, 0x0, 0x0, 0xfe3ee000), at 
0xfe3d8504
  ---- called from signal handler with signal 6	(SIGABRT) ------
  [6] __sigprocmask(0x0, 0xffbee1a8, 0x0, 0x0, 0x0, 0x0), at 
0xfe3d9790
  [7] _resetsig(0xfe3dbf68, 0x0, 0x0, 0x3c4b0, 0xfe3ee000, 0x0), at 
0xfe3ce9ac
  [8] _sigon(0x3c4b0, 0xfe3f5938, 0x6, 0xffbee27c, 0x3c4b0, 
0xfe5d1c60), at 0xfe3ce14c
  [9] _thrp_kill(0x0, 0x1, 0x6,	0xfe3ee000, 0x1, 0x6), at 0xfe3d118c
  [10] raise(0x6, 0x6, 0xffbee340, 0xfe313ad0, 0x6, 0x0), at 
0xfe04b738
  [11] abort(0xfe0ba004, 0x6, 0x1, 0x4000, 0xffbee2f8, 0x46968), at 
0xfe035a6c
  [12] g_logv(0xfeb95e74, 0xfe37f550, 0x5, 0x3c00, 0xfe379f14, 0x4), 
at	0xfe312c90
  [13] g_log(0xfeb95e74, 0x4, 0xfeb95e78, 0x6d0d88, 0x8, 0x6d0d88), 
at 0xfe312cbc
  [14] gdk_x_error(0x3000, 0xffbee960, 0x2400, 0x375b8,	0x623a8, 
0x400), at 0xfeb71680
  [15] _XError(0xfe19f7dc, 0x4b1c8, 0xfe19a000,	0x0, 0xffbeea88, 
0x1161), at 0xfe13c334
  [16] _XReply(0x4b1c8,	0x1165,	0x0, 0x1161, 0x1165, 0x4b1c8), at 
0xfe11cc28
  [17] XGetWindowProperty(0x4b1c8, 0x4b, 0x14f,	0x14, 0x1, 0x0), at 
0xfe127944
  [18] bg_applier_apply_prefs(0x14f, 0xffbeeb94, 0xffbeeb9c, 
0xffbeeb98, 0x0, 0x0), at 0x1e268
  [19] 0x18534(0x6d0d20, 0x6d0d01, 0x3c2fc, 0x8, 0x3c000, 0x73ca0), 
at 0x18533
  [20] 0x16354(0x60428,	0x68b38, 0x6d0d20, 0x41838, 0x41830, 
0x18500), at 0x16353
  [21] gconf_listeners_notify(0xdd088, 0x6d0ce8, 0xfe8ccea0, 
0xffbeed2c, 0x10, 0x73e98), at 0xfe8ad8ac
  [22] gconf_client_flush_notifies(0x60428, 0x0, 0x0, 0x6d0d20,
	0x761a8, 0xfe8ec52c), at 0xfe8cd1e0
  [23] notify_idle_callback(0x60428, 0xfe8cce80, 0x60428, 0xfe302d48, 
0x1, 0xfe33f144),	at 0xfe8cce88
  [24] g_main_dispatch(0x579a8,	0x0, 0xfe37f54c, 0xfe362cec, 0x579b0, 
0xfe379f14), at 0xfe302d58
  [25] g_main_context_iterate(0x579a8, 0x1, 0x1, 0x1, 0xfe3daebc, 
0xe1a88), at 0xfe305470
  [26] g_main_loop_run(0xdf228,	0xdf228, 0x1800, 0xfe37f550, 
0xfe37f548, 0xfe379f14), at 0xfe3069b4
  [27] gtk_main(0xfebae188, 0xfefd9734,	0xdf228, 0xfefd9740, 0x0, 
0xfefb7324), at 0xfed84ebc
  [28] main(0x0, 0x39800, 0x3ac3c, 0x261fc, 0x0, 0x3ac9c), at 0x161e4



Comment 15 Jody Goldberg 2002-09-06 14:21:03 UTC
1) You want the capplet to edit the background for each root window 
seperately ?  That is not feasible with the current ui which can not 
be changed until 2.2.  I'd rather see this filed as an extension 
request in a distinct report.

2) That trace does not correspond to a seg fault, it is an X error.  
We need a trace that is run with --sync to see where the fault is 
occuring.  I have not been able to replicate this under linux.
Comment 16 Mamatha 2002-09-13 03:09:55 UTC
Thanks Jody ,
I will file a separate enhancement bug for being able to apply 
separate backgrounds on  separate heads.

I tested  problem no 2 with Sun beta 2 build 6 package. Source taken 
from "Tue Aug  27 14:57:39 BST 2002".
I am not able to reproduce the crash at the moment.  Will attach a 
fresh trace with --sync option if i find this crash again. Please  
close this bug.

Comment 17 Jody Goldberg 2002-09-13 03:14:56 UTC
Ok. Thanks