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 151641 - Crash with gnome-background-properties when trying to change background
Crash with gnome-background-properties when trying to change background
Status: RESOLVED DUPLICATE of bug 146645
Product: gnome-control-center
Classification: Core
Component: Background
1.4.0
Other other
: Normal normal
: ---
Assigned To: Rodney Dawes
Rodney Dawes
Depends on:
Blocks:
 
 
Reported: 2004-09-01 19:32 UTC by hugues
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description hugues 2004-09-01 19:33:14 UTC 
Distribution: Debian 3.1
Package: control-center
Severity: normal
Version:  2.6.1
Synopsis: Crash with gnome-background-properties when trying to change background
Bugzilla-Product: control-center
Bugzilla-Component: background
Bugzilla-Version: 2.6.1
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:

When trying to access to the gnome-background panel properties (right
click on the nautilus desktop),
it crashes after diplaying the dialog, but before displaying any images
or buttons.
This happens every time.

Regards.



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-background-properties'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread 1087828224 (LWP 16319)]
[New Thread 1098754992 (LWP 16322)]
[Thread debugging using libthread_db enabled]
[New Thread 1087828224 (LWP 16319)]
[New Thread 1098754992 (LWP 16322)]
[Thread debugging using libthread_db enabled]
[New Thread 1087828224 (LWP 16319)]
[New Thread 1098754992 (LWP 16322)]
(no debugging symbols found)...[New Thread 1098484656 (LWP 16321)]
(no debugging symbols found)...[New Thread 1097313200 (LWP 16320)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0xffffe410 in __kernel_vsyscall ()

+ Trace 49813

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gnome_wp_pixbuf_center
  • #5 gnome_wp_xml_load_list
  • #6 gnome_wp_main_quit
  • #7 _IO_stdin_used
  • #8 ??
  • #9 g_source_destroy
    from /usr/lib/libglib-2.0.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-01 15:33 -------


Unknown version 2.6.1 in product control-center. Setting version to "1.4.0".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "control-center".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was hugues@nullpart.net.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Vincent Noel 2004-09-03 14:24:45 UTC 

*** This bug has been marked as a duplicate of 146130 ***
Comment 2 Vincent Noel 2004-09-03 14:26:27 UTC 
nope, my mistake...
Comment 3 Vincent Noel 2004-09-03 14:26:44 UTC 

*** This bug has been marked as a duplicate of 146645 ***