Bug 113686 - resapplet crashes on login with default GNOME config
Summary: resapplet crashes on login with default GNOME config
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 3
Hardware: i686 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Rodrigo Moya
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-28 18:27 UTC by James Ogley
Modified: 2005-09-12 17:15 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Ogley 2005-08-28 18:27:27 UTC
New user, logging into GNOME, resapplet crashes with the following backtrace:

Backtrace was generated from '/opt/gnome/bin/resapplet'

(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 1089912384 (LWP 28206)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x40b9f3e3 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#2  0x400929f5 in libgnomeui_module_info_get ()
   from /opt/gnome/lib/libgnomeui-2.so.0
#3  <signal handler called>
#4  0x40b91147 in XRRConfigCurrentRate () from /usr/X11R6/lib/libXrandr.so.2
#5  0x0804dd24 in main ()

Thread 1 (Thread 1089912384 (LWP 28206)):
#0  0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1  0x40b9f3e3 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
No symbol table info available.
#2  0x400929f5 in libgnomeui_module_info_get ()
   from /opt/gnome/lib/libgnomeui-2.so.0
No symbol table info available.
#3  <signal handler called>
No symbol table info available.
#4  0x40b91147 in XRRConfigCurrentRate () from /usr/X11R6/lib/libXrandr.so.2
No symbol table info available.
#5  0x0804dd24 in main ()
No symbol table info available.
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 JP Rosevear 2005-08-29 02:37:01 UTC
This is a duplicate that should be fixed upstream now.  Rodrigo knows more.
Comment 2 JP Rosevear 2005-08-29 02:37:43 UTC
Oops, wrong bug.
Comment 3 JP Rosevear 2005-09-12 17:15:58 UTC
This should be solved now.