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 453854 - crash in System Log: Reboot after restart of ...
crash in System Log: Reboot after restart of ...
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-07-05 03:28 UTC by higgijh
Modified: 2007-07-06 00:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description higgijh 2007-07-05 03:28:35 UTC
Version: 2.18.1

What were you doing when the application crashed?
Reboot after restart of ypbind.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 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: 277131264 vsize: 277131264 resident: 20615168 share: 14729216 rss: 20615168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183605722 rtime: 56 utime: 52 stime: 4 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 46912496344464 (LWP 3400)]
(no debugging symbols found)
0x0000003ac160d865 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496344464 (LWP 3400))

  • #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 (110 sec old) ---------------------
rexec
xinetd (pid 2338) is running...
rsync
xinetd (pid 2338) is running...
Traceback (most recent call last):
  File "/usr/sbin/system-config-services", line 669, in on_btnRestart_clicked
    self.get_service_action_results(self.text_in_row, "restart")
  File "/usr/sbin/system-config-services", line 622, in get_service_action_results
    results = self.services[servicename].action(action_type)
  File "/usr/share/system-config-services/servicemethods.py", line 337, in action
    xinetd = self.services.get('xinetd', None)
AttributeError: Services instance has no attribute 'get'
Starting NIS service: [  OK  ]
Binding  NIS service: .........[FAILED]
Shutting down NIS service: [  OK  ]
--------------------------------------------------
Comment 1 higgijh 2007-07-05 04:20:53 UTC
I've been trying to get two machines to "talk" to each other freely over the last month. The Intel motherboards I'm using are two DG964WH each with an Inel Core 2 Duo Processor and 4 cores. My ultimate desire is to get my seismic processing system, that runs in parallel using PVM, to come up - runs serially or in parallel on a single machine but I want to hook many together.

The mother boards are only recognized by Fedore 7 - can't even load Fedore core 6.

I've had some much trouble with the security and firewall stuff that I've just turned that all off - an NO! it does not work the same if you just disable selinux. I've also had to disable the firewall stuff as mentioned above and that's been a major pain because I attempted to disable it after install on one machine but I find that it RE-ENABLES ITSELF almost immediately. To get the firewall down and have it stay down I've had to turn is off at install time.

I am trying to run: NFS, NIS, AUTOFS. For the time being I'm giving up on autofs and just mounting NFS files at boot time by making entries in the /etc/fstab file.

The crash happened on the client machine. Shortly after failing in this way it failed again in a similar but different way and I reported that bug as well.

I am a software developer (scientific) and I've used UNIX and then Linux since 1985 but I'm not a system manager. I've probably made a lot of mistakes but I seem to be making slow progress toward my goal - made a little tonight. 

Joe
Comment 2 Pedro Villavicencio 2007-07-06 00:01:10 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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