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 166034 - The aplicatión «gnome-background-properties» teps to reproduce the crash
The aplicatión «gnome-background-properties» teps to reproduce the crash
Status: RESOLVED DUPLICATE of bug 155517
Product: gnome-control-center
Classification: Core
Component: Background
unspecified
Other other
: Normal normal
: ---
Assigned To: Rodney Dawes
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-02 13:19 UTC by pelipro
Modified: 2005-02-24 11:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description pelipro 2005-02-02 13:19:56 UTC 
Distribution: Debian testing/unstable
Package: gnome-backgrounds
Severity: blocker
Version: GNOME2.8.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: The aplicatión «gnome-background-properties» teps to reproduce the crash
Bugzilla-Product: gnome-backgrounds
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
The aplicatión «gnome-background-properties» teps to reproduce the
crash:
1. When, i try change background of desktop
2. bloked
3. 

Expected Results:


How often does this happen?
At the first day

Additional Information:



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)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread 1087558080 (LWP 9464)]
[New Thread 1099189168 (LWP 9468)]
[Thread debugging using libthread_db enabled]
[New Thread 1087558080 (LWP 9464)]
[New Thread 1099189168 (LWP 9468)]
(no debugging symbols found)...[New Thread 1098922928 (LWP 9467)]
(no debugging symbols found)...[New Thread 1098595248 (LWP 9465)]
(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 1087558080 (LWP 9464)]
[New Thread 1099189168 (LWP 9468)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...0xffffe410 in __kernel_vsyscall ()

+ Trace 55200

Thread 4 (Thread 1098595248 (LWP 9465))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-02 08:19 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-backgrounds".
   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 pelipro@yahoo.es.
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-02-02 15:07:45 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 164891, which has been marked as a duplicate of
155517.

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