GNOME Bugzilla – Bug 171616
Crash on trying to set the monitor option
Last modified: 2005-03-25 17:51:41 UTC
Distribution: Debian 3.1 Package: gnome-utils Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: Crash on trying to set the monitor option Bugzilla-Product: gnome-utils Bugzilla-Component: logview Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Enabling the Monitor option on the second of two System Log windows causes a crash. At the time some datas were effectively being written in the /var/log/syslog file. Steps to reproduce the crash: 1. Open a 'System Log' window from Application > System Tools 2. Choose the 'Open' command in the 'Log' menu and open syslog 3. Select the 'Monitor' option in the 'Log' menu Expected Results: crash How often does this happen? It happened three times, but strangely no more while filling up that bug report! Additional Information: The crash occured while lauching a dial-up connection. Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/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) [Thread debugging using libthread_db enabled] [New Thread -1221532864 (LWP 7682)] [New Thread -1233499216 (LWP 7689)] [New Thread -1233232976 (LWP 7688)] [New Thread -1232966736 (LWP 7686)] [New Thread -1232634960 (LWP 7685)] [New Thread -1224148048 (LWP 7684)] (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) (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 ()
+ Trace 57332
Thread 6 (Thread -1224148048 (LWP 7684))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-25 12:47 ------- Unknown version 2.10.0 in product gnome-utils. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". 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 xavierba@free.fr. 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.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 170244 ***