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 171881 - gnome-panel crashes while changing desktop background
gnome-panel crashes while changing desktop background
Status: RESOLVED DUPLICATE of bug 171880
Product: gnome-panel
Classification: Other
Component: clock
2.6.x
Other other
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-28 16:59 UTC by sline
Modified: 2005-03-28 17:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description sline 2005-03-28 16:59:57 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-panel
Severity: critical
Version: GNOME2.6. 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-panel crashes while changing desktop background
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock applet
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
Changing desktop background (wallpaper) while running two monitors,
kills gnome-panel

Steps to reproduce the crash:
1. run two monitors
2. change desktop background

Expected Results:
gnome-panel crashes. i've now repeated it. gnome-panel crashes even
before i hit the close button on the 'change desktop background' window.



How often does this happen?
everytime i change desktop background with two monitors. it didn't
happen when i did it
with one monitor. 


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-panel'

(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)...[Thread debugging using
libthread_db enabled]
[New Thread -151132000 (LWP 3923)]
(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)...(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)...0x006d07a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -151132000 (LWP 3923))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ORBit_adaptor_setup
    from /usr/lib/libORBit-2.so.0
  • #5 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #6 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #7 link_connection_set_max_buffer
    from /usr/lib/libORBit-2.so.0
  • #8 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #9 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #13 link_main_iteration
    from /usr/lib/libORBit-2.so.0
  • #14 giop_recv_buffer_get
    from /usr/lib/libORBit-2.so.0
  • #15 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #16 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #17 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #18 Bonobo_Unknown_unref
    from /usr/lib/libbonobo-activation.so.4
  • #19 ??
  • #20 ??
  • #21 ??
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-28 11:59 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
   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 sline@steveline.com.
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-03-28 17:05:19 UTC

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