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 300390 - gnome-background-properties quit with no reasons
gnome-background-properties quit with no reasons
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-12 20:33 UTC by jb
Modified: 2005-04-12 21:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description jb 2005-04-12 20:33:25 UTC
Distribution: Debian 3.1
Package: control-center
Severity: normal
Version: GNOME2.8.3 2.8.2
Gnome-Distributor: Debian
Synopsis: gnome-background-properties quit with no reasons
Bugzilla-Product: control-center
Bugzilla-Component: background
Bugzilla-Version: 2.8.2
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:

When I want to change my background, gnome-background-properties
instantanly quit

Steps to reproduce the crash:

1. change background?
2. 
3. 

Expected Results:

/

How often does this happen?

Not usual. Sometimes works Sometimes not
First time on 2005-04-12

Additional Information:

I have to reboot to change my background !


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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 1087690080 (LWP 7524)]
[New Thread 1100225456 (LWP 7527)]
[New Thread 1099963312 (LWP 7526)]
[New Thread 1098927024 (LWP 7525)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x40641511 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread 1087690080 (LWP 7524))

  • #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 g_child_watch_add
    from /usr/lib/libglib-2.0.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_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-12 16:33 -------


Unknown version 2.8.2 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 jb@kheops.frmug.org.
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 Christian Kirbach 2005-04-12 20:35: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.
Please briefly check for duplicates on http://bugzilla.gnome.org before 
submitting any future reports.

*** This bug has been marked as a duplicate of 146130 ***
Comment 2 Elijah Newren 2005-04-12 20:57:08 UTC
Christian: Given that bug-buddy politely asks users to report crashes (i.e.
they're doing us a favor), and the fact that most people don't know how to tell
if two bugs are duplicates, I don't think that's a fair requirement to place on
users.  It's something we can definitely encourage, but I think that's it.
Comment 3 Christian Kirbach 2005-04-12 21:10:36 UTC
I think I was politely asking , not demanding a favour.
If you think this is offending I'll alter the text.
Comment 4 Elijah Newren 2005-04-12 21:26:00 UTC
I don't think it was offending; I agree that you asked politely.  What I was
pointing out was that it sounded like a requirement (which you were nicely
drawing people's attention to); meaning that users would be unlikely to file
future bug reports because they wouldn't know how to verify if a bug they had
was a duplicate of several other similarly sounding ones and thus just not file
at all.

Anyway, it's just a nitpick.  Thanks for all your help and awesome work in
triaging.  :)