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 172776 - Cambiar fondo de escritorio
Cambiar fondo de escritorio
Status: RESOLVED DUPLICATE of bug 146130
Product: gnome-control-center
Classification: Core
Component: Background
2.8.x
Other other
: Normal normal
: ---
Assigned To: Rodney Dawes
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-06 09:15 UTC by arturoporras
Modified: 2005-04-06 15:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description arturoporras 2005-04-06 09:15:48 UTC 
Distribution: Debian gnulinex2004r1
Package: control-center
Severity: normal
Version: GNOME2.8.1 2.8.1
Gnome-Distributor: Debian
Synopsis: Cambiar fondo de escritorio
Bugzilla-Product: control-center
Bugzilla-Component: background
Bugzilla-Version: 2.8.1
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Al intentar cambiar el fondo de escritorio se produce un error, no deja
hacer nada

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread 1089316448 (LWP 13799)]
[New Thread 1102101424 (LWP 13802)]
[Thread debugging using libthread_db enabled]
[New Thread 1089316448 (LWP 13799)]
[New Thread 1102101424 (LWP 13802)]
(no debugging symbols found)...[New Thread 1101839280 (LWP 13801)]
(no debugging symbols found)...[New Thread 1100852144 (LWP 13800)]
(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 1089316448 (LWP 13799)]
[New Thread 1102101424 (LWP 13802)]
(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)...0x40a26431 in __waitpid_nocancel
() from /lib/tls/libpthread.so.0

+ Trace 57768

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




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-06 05:15 -------


Unknown version 2.8.1 in product control-center.  Setting version to "2.8.x".
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 arturoporras@edu.juntaextremadura.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 Elijah Newren 2005-04-06 15:02:46 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

Matches the stack trace in bug 161550, which has been marked as a duplicate of
146130.

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