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 477904 - crash in System Log: Opening Samba configurat...
crash in System Log: Opening Samba configurat...
Status: RESOLVED DUPLICATE of bug 442846
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-17 23:00 UTC by palomo
Modified: 2007-09-25 18:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description palomo 2007-09-17 23:00:10 UTC 
Version: 2.18.0

What were you doing when the application crashed?
Opening Samba configuration tool in Gnome


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 276979712 vsize: 276979712 resident: 14811136 share: 8540160 rss: 14811136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190068955 rtime: 188 utime: 177 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/sbin/gnome-system-log'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496319888 (LWP 3051)]
(no debugging symbols found)
0x000000363f80d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 163644

Thread 1 (Thread 46912496319888 (LWP 3051))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gtk_main_quit
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    from /usr/lib64/libgnomeui-2.so.0
  • #5 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #6 gtk_main_quit
    from /lib64/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #9 gtk_main_quit
    from /usr/lib64/libgnomeui-2.so.0
  • #10 _SmcProcessMessage
    from /usr/lib64/libSM.so.6
  • #11 IceProcessMessages
    from /usr/lib64/libICE.so.6
  • #12 gtk_main_quit
    from /usr/lib64/libgnomeui-2.so.0
  • #13 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #14 gtk_main_quit
    from /lib64/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (44 sec old) ---------------------
AttributeError: ('realm', 'CAOBASERVER.EXPROCAOBA.COM')
Traceback (most recent call last):
  File "/usr/share/system-config-samba/system-config-samba.py", line 41, in <module>
    mainWindow.MainWindow(debug_flag)
  File "/usr/share/system-config-samba/mainWindow.py", line 79, in __init__
    self.samba_data = sambaParser.SambaParser(self)
  File "/usr/share/system-config-samba/sambaParser.py", line 177, in __init__
    self.parseFile()
  File "/usr/share/system-config-samba/sambaParser.py", line 215, in parseFile
    token = self.createToken(line, section) 
  File "/usr/share/system-config-samba/sambaParser.py", line 264, in createToken
    token = sambaToken.SambaToken(sambaToken.SambaToken.SAMBA_TOKEN_KEYVAL, (name, value))
  File "/usr/share/system-config-samba/sambaToken.py", line 63, in __init__
    raise AttributeError, value
AttributeError: ('debug level', '5')
--------------------------------------------------
Comment 1 Emmanuele Bassi (:ebassi) 2007-09-25 18:50:11 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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