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 450477 - crash in System Log: I was in the process of ...
crash in System Log: I was in the process 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-06-23 22:22 UTC by jacques
Modified: 2007-06-24 00:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jacques 2007-06-23 22:22:54 UTC 
Version: 2.18.1

What were you doing when the application crashed?
I was in the process of creating a new partition on a new disk. The system asked to be rebooted so that the new partition could be mounted and made accessible. The incident occured as I ordered a reboot.


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 57667584 vsize: 57667584 resident: 27971584 share: 9428992 rss: 27971584 rss_rlim: 4294967295
CPU usage: start_time: 1182626531 rtime: 1892 utime: 1643 stime: 249 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 "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226589888 (LWP 8320)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 143224

Thread 1 (Thread -1226589888 (LWP 8320))

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






Comment 1


Pedro Villavicencio





          2007-06-24 00:56:35 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 ***