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 358805 - crash in Users and Groups: I clicked on the menu it...
crash in Users and Groups: I clicked on the menu it...
Status: RESOLVED DUPLICATE of bug 358685
Product: gnome-system-tools
Classification: Deprecated
Component: users-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2006-10-01 16:06 UTC by jpauldietrich
Modified: 2006-10-01 22:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jpauldietrich 2006-10-01 16:06:18 UTC 
Version: 2.15.5

What were you doing when the application crashed?
I clicked on the menu item System->Administration->Users and Groups. I wanted to verify that my user name still belonged to the admin group (Synaptic won't accept my user password. I can only start synaptic from terminal with sudo synaptic).


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 109326336 vsize: 109326336 resident: 10006528 share: 7790592 rss: 10006528 rss_rlim: -1
CPU usage: start_time: 1159718284 rtime: 7 utime: 6 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/users-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47230070238032 (LWP 16083)]
0x00002af49a07aeb5 in waitpid () from /lib/libpthread.so.0

+ Trace 73929

Thread 1 (Thread 47230070238032 (LWP 16083))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
  • #2 ??
  • #3 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Elijah Newren





          2006-10-01 16:16:16 UTC
        



Thanks for the bug report. Probably a duplicate of bug 355431 but unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


jpauldietrich





          2006-10-01 17:45:25 UTC
        



OK, I ran gdb on /usr/bin/users-admin
Is this what you need? Let me know if I can be of further assistance.

(gdb) run
Starting program: /usr/bin/users-admin 
(no debugging symbols found)
...
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(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 47224356174672 (LWP 27662)]
type array 97 not a basic type
type invalid 0 not a basic type
type invalid 0 not a basic type
type invalid 0 not a basic type
type invalid 0 not a basic type
type invalid 0 not a basic type

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47224356174672 (LWP 27662)]
0x00002af3459a7170 in strlen () from /lib/libc.so.6
(gdb) 







Comment 3


Elijah Newren





          2006-10-01 17:50:45 UTC
        



nope, but you're on the right path.  We need you to type 'thread apply all bt' at the '(gdb)' prompt and include the output of that.

Thanks for following up.  :)






Comment 4


jpauldietrich





          2006-10-01 21:22:29 UTC
        



OK, below is the output. Let me know if I need to do anything else. In case it is of use, I'm running x86_64 kernel 2.6.17-10 SMP

(gdb) thread apply all bt





+
Trace
    73965






Thread 1
          (Thread 47573684267856 (LWP 13590))


    

  • 
#0
strlen

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
g_strdup

    
                from
                /usr/lib64/libglib-2.0.so.0

    

    • 

  • 
#2
g_value_dup_string

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#3
g_object_new_valist

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#4
g_object_new

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#5
oobs_users_config_get

    
                from
                /usr/lib64/liboobs-1.so.2

    

    • 

  • 
#6
oobs_object_update_async

    
                from
                /usr/lib64/liboobs-1.so.2

    

    • 

  • 
#7
oobs_object_update

    
                from
                /usr/lib64/liboobs-1.so.2

    

    • 

  • 
#8
oobs_users_config_get

    
                from
                /usr/lib64/liboobs-1.so.2

    

    • 

  • 
#9
??

    • 

  • 
#10
g_type_create_instance

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#11
g_object_set

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#12
??

    • 

  • 
#13
g_object_newv

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#14
g_object_new_valist

    • 

  • 
#15
g_object_new

    
                from
                /usr/lib64/libgobject-2.0.so.0

    

    • 

  • 
#16
??

    • 

  • 
#17
??

    • 

  • 
#18
__libc_start_main

    
                from
                /lib/libc.so.6

    

    • 

  • 
#19
??

    • 

  • 
#20
??

    • 

  • 
#21
??

    • 













Comment 5


Elijah Newren





          2006-10-01 22:05:32 UTC
        



Awesome, thanks for following up.  From the stack trace, this is actually a duplicate of bug 358685 which has been fixed upstream already, and should get incorporated into edgy when a new release is made.  :)

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