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 148472 - Setting background failes when different encoding is used in name (iso-8859-2)
Setting background failes when different encoding is used in name (iso-8859-2)
Status: RESOLVED DUPLICATE of bug 146645
Product: gnome-control-center
Classification: Core
Component: Background
1.4.0
Other other
: Normal normal
: ---
Assigned To: Rodney Dawes
Rodney Dawes
Depends on:
Blocks:
 
 
Reported: 2004-07-26 08:33 UTC by michuk
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description michuk 2004-07-26 08:33:24 UTC
Distribution: Debian testing/unstable
Package: control-center
Severity: normal
Version: GNOME2.6.1 2.6.1
Gnome-Distributor: Debian
Synopsis: Setting background failes when different encoding is used in name (iso-8859-2)
Bugzilla-Product: control-center
Bugzilla-Component: background
Bugzilla-Version: 2.6.1
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. add a picture with different encoding used in name	tahn utf-8
2. try to set it as background
3. 

Expected Results:
backgroud set with new picture

How often does this happen?
just tried it once

Additional Information:
after adding that unlicky picture, setting background dialog hangs every
time i want to use it...


Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 10147)]
[New Thread 32769 (LWP 10148)]
[New Thread 16386 (LWP 10149)]
[New Thread 32771 (LWP 10150)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x4054dbdb in waitpid ()
   from /lib/libpthread.so.0

Thread 4 (Thread 32771 (LWP 10150))

  • #0 __pthread_sigsuspend
    from /lib/libpthread.so.0
  • #1 ??
  • #2 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #3 pthread_cond_wait
    from /lib/libpthread.so.0
  • #4 _gnome_vfs_thread_pool_init
    from /usr/lib/libgnomevfs-2.so.0
  • #5 _gnome_vfs_thread_pool_init
    from /usr/lib/libgnomevfs-2.so.0
  • #6 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #7 pthread_start_thread
    from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 10147))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 valid
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 __libc_sigaction
    from /lib/libc.so.6
  • #4 gnome_wp_xml_load_list
  • #5 gnome_wp_main_quit
  • #6 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #7 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-26 04:33 -------


Unknown version 2.6.1 in product control-center. Setting version to "1.4.0".
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 michuk@tlen.pl.
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 Rodney Dawes 2004-09-03 20:00:00 UTC

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