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 104387 - Background failed after reboot from YaST2 freeze
Background failed after reboot from YaST2 freeze
Status: RESOLVED DUPLICATE of bug 12365
Product: gnome-control-center
Classification: Core
Component: Background
unspecified
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-24 14:48 UTC by gmbphx
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gmbphx 2003-01-25 09:46:11 UTC 
Package: control-center
Severity: normal
Version: 1.4.0.4
Synopsis: Background failed after reboot from YaST2 freeze
Bugzilla-Product: control-center
Bugzilla-Component: background

Description:
Description of Problem:


Steps to reproduce the problem:
1. YaST2 Control Center hung searching network for server (in black
box)
2. Warm boot from front panel
3. Restarting X-window Ok, until attempt to log onto desktop

Actual Results:
Background never loaded.  Used SuSe extended desktop menu to try to
configure background and got error message 


Expected Results:


How often does this happen?
First time.


Additional Information:
Total newbie, haven't got system totally configured/working yet.




Debugging Information:

Backtrace was generated from
'/opt/gnome/bin/background-properties-capplet'

(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)...0x4069a8c9 in wait4 () from
/lib/libc.so.6

+ Trace 33114

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    from /opt/gnome/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 fill_monitor
  • #5 idle_fill_monitor
  • #6 g_idle_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #7 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #8 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #9 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #11 capplet_corba_gtk_main
    from /opt/gnome/lib/libcapplet.so.0
  • #12 capplet_gtk_main
    from /opt/gnome/lib/libcapplet.so.0
  • #13 main
  • #14 __libc_start_main
    from /lib/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-25 04:46 -------

The original reporter (gmbphx@qwest.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Comment 1 Andrew Sobala 2003-01-25 12:18:00 UTC 
Please upgrade; this is fixed in later versions.

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