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 12365 - background-capplet crash
background-capplet crash
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Background
pre 1.4.0
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Chema Celorio
: 14229 14903 19195 32656 33349 36200 50679 52937 60527 95414 95441 104387 107093 127540 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2000-05-28 01:18 UTC by franco
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description franco 2001-01-27 21:32:30 UTC 
Package: control-center
Severity: normal
Version: 1.2.0

>Synopsis: background-capplet crash
>Class: sw-bug
Distribution: Red Hat Linux release 6.2 (Zoot)
System: Linux 2.2.14 i686 unknown
C library: glibc-2.1.3-15
C compiler: egcs-2.91.66
glib: 1.2.8
GTK+: 1.2.8
ORBit: ORBit 0.5.1
gnome-libs: gnome-libs 1.2.0
gnome-core: gnome-core 1.2.0


>Description:
  When attempting to display the "preview view" of a tiled background
JPEG, the
background-capplet within the control-center crashes with SIGSEGV. The
JPEG
displays correctly if manually entered into the ~/.gnome/Background file
as the
current wallpaper.
  JPEG image available if needed...


>How-To-Repeat:
View attached JPEG in the control-panel background applet


Debugging information:
0x405d78e9 in __wait4 () from /lib/libc.so.6

+ Trace 1856

  • #0 __wait4
    from /lib/libc.so.6
  • #1 ??
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 127
  • #4 idle_fill_monitor
  • #5 g_idle_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #6 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #7 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #8 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #10 capplet_corba_gtk_main
    from /usr/lib/libcapplet.so.0
  • #11 capplet_gtk_main
    from /usr/lib/libcapplet.so.0
  • #12 main
  • #13 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 92
  • #0 __wait4
    from /lib/libc.so.6
  • #1 ??
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 127
  • #4 idle_fill_monitor
  • #5 g_idle_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #6 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #7 g_main_iterate
    from /usr/lib/libglib-1.2.so.0 



--- Included file '/usr/local/share/backgrounds/barely_textured-green.jpg' ---

ÿØÿà

--- End of file ---




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 16:32 -------
This bug was previously known as bug 12365 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=12365
Originally filed under the control-center product and general component.

Unknown version 1.2.x in product control-center. Setting version to the default, "unspecified".
The original reporter (franco@icehouse.net) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, bugmeister@canvas.gnome.org.
Comment 1 Chema Celorio 2001-09-15 17:39:08 UTC 
I would like to fix this crash for the background capplet in the control center.
However i need help from you, i need to know if this crash happes when a
particular image is beeing set as the background and also if it happens every
time that image is set. If this is the case can you provide me with an URL to
the image that makes the background capplet crash so that i can try to replicate
it in my computer. 

Thanks in advance
Comment 2 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 36200 has been marked as a duplicate of this bug. ***
Comment 3 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 52937 has been marked as a duplicate of this bug. ***
Comment 4 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 14229 has been marked as a duplicate of this bug. ***
Comment 5 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 14903 has been marked as a duplicate of this bug. ***
Comment 6 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 19195 has been marked as a duplicate of this bug. ***
Comment 7 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 32656 has been marked as a duplicate of this bug. ***
Comment 8 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 33349 has been marked as a duplicate of this bug. ***
Comment 9 Chema Celorio 2001-09-15 21:25:39 UTC 
*** Bug 50679 has been marked as a duplicate of this bug. ***
Comment 10 Chema Celorio 2001-09-15 21:30:11 UTC 
*** Bug 60527 has been marked as a duplicate of this bug. ***
Comment 11 Joakim Ziegler 2001-09-28 21:10:13 UTC 
Hovinen, this seems to be much duplicated. However, is this gone with 
the rewrite of the background rendering code? Also, Chema, when you 
get a debbugs imported bug like this, where the original reporter 
doesn't have an account in Bugzilla, the original reporter won't get 
a copy of your comments.
Comment 12 Bradford Hovinen 2001-09-28 21:14:05 UTC 
This looks very old. It's almost certainly gone now that the
background renderer has undergone three full iterations of
refactoring. I have not been able to duplicate it. I'm going to mark
it fixed for now; if we run into it again we can reopen it.
Comment 13 Heath Harrelson 2002-10-11 11:53:03 UTC 
*** Bug 95441 has been marked as a duplicate of this bug. ***
Comment 14 Andrew Sobala 2003-01-09 22:02:03 UTC 
*** Bug 95414 has been marked as a duplicate of this bug. ***
Comment 15 Andrew Sobala 2003-01-25 12:17:59 UTC 
*** Bug 104387 has been marked as a duplicate of this bug. ***
Comment 16 David Kennedy 2003-02-26 04:52:43 UTC 
*** Bug 107093 has been marked as a duplicate of this bug. ***
Comment 17 Elijah Newren 2003-12-10 05:17:27 UTC 
*** Bug 127540 has been marked as a duplicate of this bug. ***