Thanks for the bug report. 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.

*** Bug 349517 has been marked as a duplicate of this bug. ***

*** Bug 356089 has been marked as a duplicate of this bug. ***

*** Bug 356163 has been marked as a duplicate of this bug. ***

*** Bug 357133 has been marked as a duplicate of this bug. ***

*** Bug 361686 has been marked as a duplicate of this bug. ***

*** Bug 363311 has been marked as a duplicate of this bug. ***

*** Bug 365614 has been marked as a duplicate of this bug. ***

*** Bug 365781 has been marked as a duplicate of this bug. ***

*** Bug 366480 has been marked as a duplicate of this bug. ***

This crash happened to me earlier today; I can't reproduce it.  Here's one possible clue.  When the crash happened, I was looking at /var/log/messages, which had a bunch of lines in it.  Immediately after the crash, I restarted the log viewer and saw that /var/log/messages only had a single line; the previous messages were now in /var/log/messages.0.  So perhaps the crash occurs when the system decides to rotate messages files at the moment when they are being viewed in the log viewer.

The last line in /var/log/messages.0 looks like this:

Oct 28 13:35:45 adam exiting on signal 15

And the first line in /var/log/messages looks like this:

Oct 28 13:35:46 adam syslogd 1.4.1#18ubuntu6: restart.

Perhaps the system job stops and starts syslogd as part of the log rotation process.  It does seem that the crash occurred at just about the time listed in the log lines above.

yeah, as far as I can tell this is the only reason for gnome-system-log crashing; if the parser gets a malformed line from the log it hits some invalid memory location.

I'll add a guard against this and see if it fixes the case when log files get rotated.

*** Bug 367460 has been marked as a duplicate of this bug. ***

*** Bug 367270 has been marked as a duplicate of this bug. ***

*** Bug 367647 has been marked as a duplicate of this bug. ***

*** Bug 368232 has been marked as a duplicate of this bug. ***

*** Bug 368343 has been marked as a duplicate of this bug. ***

*** Bug 370252 has been marked as a duplicate of this bug. ***

*** Bug 370266 has been marked as a duplicate of this bug. ***

*** Bug 370850 has been marked as a duplicate of this bug. ***

*** Bug 370893 has been marked as a duplicate of this bug. ***

*** Bug 370998 has been marked as a duplicate of this bug. ***

*** Bug 370987 has been marked as a duplicate of this bug. ***

*** Bug 371180 has been marked as a duplicate of this bug. ***

*** Bug 371751 has been marked as a duplicate of this bug. ***

*** Bug 371772 has been marked as a duplicate of this bug. ***

*** Bug 372384 has been marked as a duplicate of this bug. ***

*** Bug 372781 has been marked as a duplicate of this bug. ***

*** Bug 373273 has been marked as a duplicate of this bug. ***

*** Bug 373405 has been marked as a duplicate of this bug. ***

*** Bug 374209 has been marked as a duplicate of this bug. ***

*** Bug 374340 has been marked as a duplicate of this bug. ***

*** Bug 375109 has been marked as a duplicate of this bug. ***

*** Bug 375262 has been marked as a duplicate of this bug. ***

*** Bug 375462 has been marked as a duplicate of this bug. ***

*** Bug 376456 has been marked as a duplicate of this bug. ***

*** Bug 376946 has been marked as a duplicate of this bug. ***

*** Bug 376992 has been marked as a duplicate of this bug. ***

*** Bug 377990 has been marked as a duplicate of this bug. ***

*** Bug 378593 has been marked as a duplicate of this bug. ***

*** Bug 378976 has been marked as a duplicate of this bug. ***

*** Bug 379441 has been marked as a duplicate of this bug. ***

*** Bug 379618 has been marked as a duplicate of this bug. ***

*** Bug 379627 has been marked as a duplicate of this bug. ***

*** Bug 379744 has been marked as a duplicate of this bug. ***

*** Bug 379857 has been marked as a duplicate of this bug. ***

*** Bug 379876 has been marked as a duplicate of this bug. ***

*** Bug 380120 has been marked as a duplicate of this bug. ***

*** Bug 380182 has been marked as a duplicate of this bug. ***

*** Bug 380852 has been marked as a duplicate of this bug. ***

*** Bug 382292 has been marked as a duplicate of this bug. ***

*** Bug 382498 has been marked as a duplicate of this bug. ***

*** Bug 382907 has been marked as a duplicate of this bug. ***

*** Bug 382918 has been marked as a duplicate of this bug. ***

*** Bug 382993 has been marked as a duplicate of this bug. ***

*** Bug 383002 has been marked as a duplicate of this bug. ***

*** Bug 383157 has been marked as a duplicate of this bug. ***

*** Bug 383430 has been marked as a duplicate of this bug. ***

*** Bug 383487 has been marked as a duplicate of this bug. ***

(In reply to comment #1)
> Thanks for the bug report. 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.
> 
Hi

I am sorry,i do not know you leave message here.   sorry@__@
My english is poor.sorry.

It happen in looking log files.

I try to learn linux few day ago.

 gdb gnome-system-log 2>&1 | tee gdb-gnome-system-log.txt 
(gdb) handle SIG33 pass nostop noprint
(gdb) set pagination 0
(gdb) run

(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)
.
.
.
.
Is it correct way to debug gnome-system-log?

until gnome-system-log crash , right?

I run beryl+xgl those day.

My pc

mainboard gigabyte 748-L

cpu：sp2600

ram： 512mb ddr400 ram(kingston)

display card：gigabyte geforce 6600(ubuntu driver)

20g hard disk ata100.

ps2 keyboard and logitech optical mouse

os ubuntu6.10 desktop

no overclock
no rebuild kernel

Is any other information i need to tell you?

err @__@ i send this message to everyone below.

sorry T_T

(In reply to comment #1)
> Thanks for the bug report. 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.
> 

If you remote to my computer,It can help you?

Created attachment 78029 [details]
gdb-gnome-system-log.txt   bug355887

I am sorry.

*** Bug 384266 has been marked as a duplicate of this bug. ***

*** Bug 384974 has been marked as a duplicate of this bug. ***

*** Bug 384993 has been marked as a duplicate of this bug. ***

*** Bug 385217 has been marked as a duplicate of this bug. ***

*** Bug 385562 has been marked as a duplicate of this bug. ***

*** Bug 385678 has been marked as a duplicate of this bug. ***

*** Bug 385741 has been marked as a duplicate of this bug. ***

*** Bug 385790 has been marked as a duplicate of this bug. ***

*** Bug 386224 has been marked as a duplicate of this bug. ***

*** Bug 386724 has been marked as a duplicate of this bug. ***

*** Bug 387277 has been marked as a duplicate of this bug. ***

*** Bug 387331 has been marked as a duplicate of this bug. ***

*** Bug 387725 has been marked as a duplicate of this bug. ***

*** Bug 387911 has been marked as a duplicate of this bug. ***

*** Bug 388121 has been marked as a duplicate of this bug. ***

*** Bug 388129 has been marked as a duplicate of this bug. ***

*** Bug 388233 has been marked as a duplicate of this bug. ***

*** Bug 388357 has been marked as a duplicate of this bug. ***

*** Bug 388560 has been marked as a duplicate of this bug. ***

*** Bug 388603 has been marked as a duplicate of this bug. ***

*** Bug 388635 has been marked as a duplicate of this bug. ***

*** Bug 388661 has been marked as a duplicate of this bug. ***

*** Bug 388742 has been marked as a duplicate of this bug. ***

*** Bug 388928 has been marked as a duplicate of this bug. ***

*** Bug 389390 has been marked as a duplicate of this bug. ***

*** Bug 390157 has been marked as a duplicate of this bug. ***

latest duplicate is Gnome 2.16.1

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

*** Bug 390155 has been marked as a duplicate of this bug. ***

*** Bug 390173 has been marked as a duplicate of this bug. ***

Hello,
I'm running ubuntu 6.10. And I have a lot packages with dbg-syms to install, but
gnome-system-log is bundled in the package gnome-utils and there is no package
named gnome-utils-dbg. ~:(
The packages I found are:
- libgtk2.0.0-dbg
- libglib2.0.0-dbg
- gnome-panels-dbg
- gnome-control-center-dbg
- gnome-applets-dbg

Missing packages are:
- gnome-vfs-dbg
- gnome-utils-dbg

Perhaps the dbg-syms are in one of the other packages. I'll install those 
packages I have and then I will try to reproduce the crash.
We'll see. ~;)

Mr Canis

Created attachment 78967 [details]
Output from buddy after gnome-system-log crash

Hello,
here is the new generated trace, but if I saw it right I have the wrong dbg-syms
installed. If so, please give me some info where I can find them.
Thanks in advance,
                  Mr Canis

*** Bug 390256 has been marked as a duplicate of this bug. ***

*** Bug 390257 has been marked as a duplicate of this bug. ***

mr_canis: thank you for your response.

there are packages called 

gnome-utils-dbgsym 
libgnomevfs2-0-dbg

at the "deb http://people.ubuntu.com/~pitti/ddebs edgy main universe" deb package repository

Christian Kirchbach: I doesn't have all librarys. ~:(
Unfortunately I can only find the library libgnomevfs2-0-dbg, whom I installed.
But the library gnome-utils-dbgsym I can't find. What I found were gnome-utils,
but that's only the package, where gnome-system-log is integrated, but no
dbg librarys. Below I post my /etc/apt/source.list. That's the original
unmodified version from ubuntu 6.10 (edgy).
Any ideas?
Ubuntu doesn't have the librarys? Why not?

/etc/apt/source.list: ---- Begin ----
deb http://archive.ubuntu.com/ubuntu/ edgy main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ edgy main restricted universe multiverse

## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu/ edgy-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ edgy-updates main restricted universe multiverse

## Uncomment the following two lines to add software from the 'universe'
## repository.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
# deb http://de.archive.ubuntu.com/ubuntu/ edgy universe
# deb-src http://de.archive.ubuntu.com/ubuntu/ edgy universe

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://de.archive.ubuntu.com/ubuntu/ edgy-backports main restricted universe multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ edgy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu edgy-security main restricted universe multiverse
# deb http://security.ubuntu.com/ubuntu edgy-security universe
# deb-src http://security.ubuntu.com/ubuntu edgy-security universe
/etc/apt/source.list --- End ----

Canis: you need to add the the "deb http://people.ubuntu.com/~pitti/ddebs edgy main universe" deb package repository to your sources.list, as mentioned in http://live.gnome.org/GettingTraces

you can do so by using the software properties (software sources?) menu entry under system in the third parties tab. 
Or opening sources.list as root with your favourite text editor and adding the line manually. Or you can use synaptic package manager and add the new repository using the add source menu entry.

Hello Christian Kirchbach,
there are the dbg-syms, but I haven't a certificate, can I trust this repository
in general? Or can I get a certificate, if so, where?
For ubuntu updates, should I disable this repository?
Synaptic gives me the message: Can't package authorize. Or something like this.
I'm so carefully, because I had, a couple of weeks before, my system corrupted.
I had added the repositories from debian-multimedia to install the w32codecs
package. And all works fine, but after an update (suggested from updage-no-
tifier) my system was mixed with debian sarge. That isn't so good. That's the 
background for my questions.

Thanks in advance,
                  Mr Canis

*** Bug 390595 has been marked as a duplicate of this bug. ***

Ok, I installed the debugging packages, and sat around waiting for the System Log Viewer to crash. Then I got tired of waiting, and decided to see if I could force it, and I succeeded. I crashed it by leaving onscreen the /var/log/syslog log, then executing (as root) the /etc/cron.daily/sysklogd script, thus forcing the log rotation of the syslog log. This cause an immediate crash. I'm attaching the details, hope this helps. Let me know if you need more info!  --Madasi

Created attachment 79056 [details]
Stacktrace from today's forced crash

It looks like I might still be missing some debugging symbols. If you need them, could you help me figure out which ones I still need to install? Thanks - Madasi

*** Bug 390931 has been marked as a duplicate of this bug. ***

*** Bug 391031 has been marked as a duplicate of this bug. ***

Mr. Canis: yes you can trust *.ubuntu.com


madasi: thank you for tracking down on (at least one) cause of the crash.
your trace is quite good, thank you!
if you could install the libc debug package we had a perfect trace.

anyways, it is good enough for the developers to examine.

posting the relevant parts here

+ Trace 98063

Note: I am not able to reproduce the crash with logview 2.17.1 using the instructions given in comment #102

Christian Kirchbach Comment 106: That wasn't my question. My question concerned
the repository with regard to ubuntu updates. After an update, will the dbysyms
match? That's the question.

Mr Canis

*** Bug 391346 has been marked as a duplicate of this bug. ***

*** Bug 391988 has been marked as a duplicate of this bug. ***

*** Bug 392381 has been marked as a duplicate of this bug. ***

*** Bug 392403 has been marked as a duplicate of this bug. ***

*** Bug 392463 has been marked as a duplicate of this bug. ***

*** Bug 392659 has been marked as a duplicate of this bug. ***

*** Bug 392796 has been marked as a duplicate of this bug. ***

*** Bug 392817 has been marked as a duplicate of this bug. ***

*** Bug 393757 has been marked as a duplicate of this bug. ***

*** Bug 394112 has been marked as a duplicate of this bug. ***

*** Bug 394448 has been marked as a duplicate of this bug. ***

looking at the stack trace and to comment #107, I think this is a dupe of bug #380410 - which has been fixed and is available in the 2.17.1 release and will be part of the 2.16.3 stable release.

could people experiencing this bug try and download gnome-utils from trunk and use that just to be sure I can close this bug for good?  thanks in advance.

*** Bug 394667 has been marked as a duplicate of this bug. ***

*** Bug 395177 has been marked as a duplicate of this bug. ***

*** Bug 395324 has been marked as a duplicate of this bug. ***

So, we'd be happy if someone is able to use and test the latest version from our svn software repository, or to install one of the development distributions (Ubunto 7.04 etc.) and try to reproduce the error there.

*** Bug 396757 has been marked as a duplicate of this bug. ***

*** Bug 397016 has been marked as a duplicate of this bug. ***

*** Bug 397123 has been marked as a duplicate of this bug. ***

*** Bug 397140 has been marked as a duplicate of this bug. ***

(refering to comment #120)
this really looks like a dup of bug 380410, the stacktraces match perfectly. i'd tend to close this one here as a dup. :-/

again: does anybody of the reporters run gnome 2.17.x and can still reproduce this? thanks for your help!

*** Bug 397558 has been marked as a duplicate of this bug. ***

*** Bug 397610 has been marked as a duplicate of this bug. ***

*** Bug 398127 has been marked as a duplicate of this bug. ***

*** Bug 398205 has been marked as a duplicate of this bug. ***

*** Bug 399166 has been marked as a duplicate of this bug. ***

*** Bug 399229 has been marked as a duplicate of this bug. ***

*** Bug 399837 has been marked as a duplicate of this bug. ***

*** Bug 399695 has been marked as a duplicate of this bug. ***

*** Bug 399914 has been marked as a duplicate of this bug. ***

*** Bug 400124 has been marked as a duplicate of this bug. ***

*** Bug 400891 has been marked as a duplicate of this bug. ***

*** Bug 401250 has been marked as a duplicate of this bug. ***

*** Bug 401330 has been marked as a duplicate of this bug. ***

*** Bug 401638 has been marked as a duplicate of this bug. ***

*** Bug 401685 has been marked as a duplicate of this bug. ***

*** Bug 402253 has been marked as a duplicate of this bug. ***

*** Bug 402455 has been marked as a duplicate of this bug. ***

*** Bug 403853 has been marked as a duplicate of this bug. ***

*** Bug 403862 has been marked as a duplicate of this bug. ***

*** Bug 404681 has been marked as a duplicate of this bug. ***

*** Bug 404614 has been marked as a duplicate of this bug. ***

*** Bug 404557 has been marked as a duplicate of this bug. ***

*** Bug 404805 has been marked as a duplicate of this bug. ***

*** Bug 404865 has been marked as a duplicate of this bug. ***

*** Bug 404930 has been marked as a duplicate of this bug. ***

*** Bug 405042 has been marked as a duplicate of this bug. ***

*** Bug 405103 has been marked as a duplicate of this bug. ***

*** Bug 405253 has been marked as a duplicate of this bug. ***

Does anybody of the reporters run gnome 2.17.x and can still reproduce
this? Thanks for your help!

*** Bug 405710 has been marked as a duplicate of this bug. ***

*** Bug 406219 has been marked as a duplicate of this bug. ***

*** Bug 406282 has been marked as a duplicate of this bug. ***

*** Bug 406298 has been marked as a duplicate of this bug. ***

*** Bug 406977 has been marked as a duplicate of this bug. ***

*** Bug 406851 has been marked as a duplicate of this bug. ***

*** Bug 407157 has been marked as a duplicate of this bug. ***

*** Bug 407420 has been marked as a duplicate of this bug. ***

*** Bug 407915 has been marked as a duplicate of this bug. ***

*** Bug 408213 has been marked as a duplicate of this bug. ***

*** Bug 408308 has been marked as a duplicate of this bug. ***

*** Bug 408389 has been marked as a duplicate of this bug. ***

*** Bug 408516 has been marked as a duplicate of this bug. ***

*** Bug 408856 has been marked as a duplicate of this bug. ***

*** Bug 409129 has been marked as a duplicate of this bug. ***

*** Bug 409175 has been marked as a duplicate of this bug. ***

*** Bug 409586 has been marked as a duplicate of this bug. ***

*** Bug 409864 has been marked as a duplicate of this bug. ***

*** Bug 409912 has been marked as a duplicate of this bug. ***

*** Bug 410309 has been marked as a duplicate of this bug. ***

*** Bug 410746 has been marked as a duplicate of this bug. ***

*** Bug 410792 has been marked as a duplicate of this bug. ***

considering Comment #120 : this pretty much seems to be a duplicate of bug 380410 . 

Has anybody tried to reproduce this on Gnome 2.17 (Ubuntu Feisty Fawn, Fedora Core 7) and can tell us that he/she did not succeed?

*** Bug 411101 has been marked as a duplicate of this bug. ***

christian: i share your opinion (see comment #129). i guess the results will show whether this is a dup or not... :-/
i will not mark this bug as a showstopper, since we don't have any 2.17.x reports so far.

*** Bug 411262 has been marked as a duplicate of this bug. ***

*** Bug 411297 has been marked as a duplicate of this bug. ***

*** Bug 411471 has been marked as a duplicate of this bug. ***

*** Bug 411500 has been marked as a duplicate of this bug. ***

*** Bug 411553 has been marked as a duplicate of this bug. ***

*** Bug 411567 has been marked as a duplicate of this bug. ***

*** Bug 411701 has been marked as a duplicate of this bug. ***

*** Bug 412141 has been marked as a duplicate of this bug. ***

*** Bug 412549 has been marked as a duplicate of this bug. ***

*** Bug 412632 has been marked as a duplicate of this bug. ***

*** Bug 412660 has been marked as a duplicate of this bug. ***

*** Bug 412746 has been marked as a duplicate of this bug. ***

*** Bug 412871 has been marked as a duplicate of this bug. ***

*** Bug 413290 has been marked as a duplicate of this bug. ***

*** Bug 413386 has been marked as a duplicate of this bug. ***

*** Bug 415151 has been marked as a duplicate of this bug. ***

*** Bug 415609 has been marked as a duplicate of this bug. ***

*** Bug 415954 has been marked as a duplicate of this bug. ***

*** Bug 415993 has been marked as a duplicate of this bug. ***

*** Bug 416598 has been marked as a duplicate of this bug. ***

*** Bug 416729 has been marked as a duplicate of this bug. ***

Has someone tried to reproduce this with Gnome 2.17.1 or newer? 

*** Bug 416724 has been marked as a duplicate of this bug. ***

*** Bug 417044 has been marked as a duplicate of this bug. ***

*** Bug 417212 has been marked as a duplicate of this bug. ***

*** Bug 417555 has been marked as a duplicate of this bug. ***

*** Bug 418310 has been marked as a duplicate of this bug. ***

*** Bug 418237 has been marked as a duplicate of this bug. ***

*** Bug 418428 has been marked as a duplicate of this bug. ***

*** Bug 418638 has been marked as a duplicate of this bug. ***

*** Bug 419405 has been marked as a duplicate of this bug. ***

*** Bug 419477 has been marked as a duplicate of this bug. ***

*** Bug 419796 has been marked as a duplicate of this bug. ***

*** Bug 420024 has been marked as a duplicate of this bug. ***

*** Bug 420077 has been marked as a duplicate of this bug. ***

*** Bug 420085 has been marked as a duplicate of this bug. ***

*** Bug 420458 has been marked as a duplicate of this bug. ***

*** Bug 421012 has been marked as a duplicate of this bug. ***

*** Bug 421098 has been marked as a duplicate of this bug. ***

*** Bug 421337 has been marked as a duplicate of this bug. ***

*** Bug 421690 has been marked as a duplicate of this bug. ***

*** Bug 421794 has been marked as a duplicate of this bug. ***

*** Bug 421913 has been marked as a duplicate of this bug. ***

I ran into this problem using gnome 2.18.0.  Here is a simple way to cause a crash:
1. open a shell
2. cd to /var/log
3. open log viewer, select auth.log
5. in the shell, sudo as root to bash
6. delete auth.log file
7. open another shell, sudo as root 
7. in log viewer, double click auth.log.  log viewer will crash

Obviously, this is not a typical user scenario but perhaps log rotation is causing something similar.  I was running this from ubuntu 7.04

*** Bug 421991 has been marked as a duplicate of this bug. ***

*** Bug 422177 has been marked as a duplicate of this bug. ***

*** Bug 422248 has been marked as a duplicate of this bug. ***

*** Bug 422866 has been marked as a duplicate of this bug. ***

*** Bug 422902 has been marked as a duplicate of this bug. ***

On my computer the problem was to do with my Iomega Rev drive.
When I removed the drive and rebooted, nautilus, rhythmbox and gnome became responsive again.

I believe it may be down to a read/write error. 
The problem with nautilus (and the other programs) occurred  when the system was attempting to read from the rev drive. Also at the time a strange error appeared in my console window .

If you like, I can try to replicate the error...

I was not able to trigger the crash using the instructions from Comment #227

gnome-system-log 2.17.93

Inserted a cd in the cdrom.


(In reply to comment #0)
> Version: 2.15.94
> 
> What were you doing when the application crashed?
> opening the app =/
> 
> 
> Distribution: Ubuntu 6.10 (edgy)
> Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
> BugBuddy Version: 2.15.92
> 
> Memory status: size: 35135488 vsize: 0 resident: 35135488 share: 0 rss:
> 13746176 rss_rlim: 0
> CPU usage: start_time: 1158194202 rtime: 0 utime: 109 stime: 0 cutime:104
> cstime: 0 timeout: 5 it_real_value: 0 frequency: 0
> 
> 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)
> [Thread debugging using libthread_db enabled]
> [New Thread -1224767296 (LWP 7325)]
> 0xffffe410 in __kernel_vsyscall ()
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xb79d32e3 in __waitpid_nocancel ()
>    from /lib/tls/i686/cmov/libpthread.so.0
> #2  0xb7f05ed5 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
> #3  <signal handler called>
> #4  0xb7148053 in strrchr () from /lib/tls/i686/cmov/libc.so.6
> #5  0x0804e9de in ?? ()
> #6  0x00000000 in ?? ()
> 
> Thread 1 (Thread -1224767296 (LWP 7325)):
> #0  0xffffe410 in __kernel_vsyscall ()
> No symbol table info available.
> #1  0xb79d32e3 in __waitpid_nocancel ()
>    from /lib/tls/i686/cmov/libpthread.so.0
> No symbol table info available.
> #2  0xb7f05ed5 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
> No symbol table info available.
> #3  <signal handler called>
> No symbol table info available.
> #4  0xb7148053 in strrchr () from /lib/tls/i686/cmov/libc.so.6
> No symbol table info available.
> #5  0x0804e9de in ?? ()
> No symbol table info available.
> #6  0x00000000 in ?? ()
> No symbol table info available.
> #0  0xffffe410 in __kernel_vsyscall ()
> 

x_acc: can you provide a stacktrace? which version do you run? this is most probably a totally different problem that already has been fixed (bug 320020).

*** Bug 423636 has been marked as a duplicate of this bug. ***

*** Bug 424145 has been marked as a duplicate of this bug. ***

*** Bug 424209 has been marked as a duplicate of this bug. ***

*** Bug 424214 has been marked as a duplicate of this bug. ***

*** Bug 425621 has been marked as a duplicate of this bug. ***

*** Bug 425771 has been marked as a duplicate of this bug. ***

*** Bug 425919 has been marked as a duplicate of this bug. ***

Removed from CC list

*** Bug 426827 has been marked as a duplicate of this bug. ***

*** Bug 426877 has been marked as a duplicate of this bug. ***

*** Bug 426892 has been marked as a duplicate of this bug. ***

*** Bug 427175 has been marked as a duplicate of this bug. ***

*** Bug 427297 has been marked as a duplicate of this bug. ***

*** Bug 427428 has been marked as a duplicate of this bug. ***

*** Bug 427749 has been marked as a duplicate of this bug. ***

*** Bug 428071 has been marked as a duplicate of this bug. ***

*** Bug 428575 has been marked as a duplicate of this bug. ***

closing as fixed since 2.18.0 is out and it seems nobody is able to consistently reproduce it using 2.17.x/2.18.x releases of gnome-utils.

feel free to reopen this bug in case someone is able to reproduce it:

  * consistently (with a clear sequence of actions)
  * under a 2.18.x release of gnome-utils
  * with a meaningful stacktrace, with debugging symbols

*** Bug 428748 has been marked as a duplicate of this bug. ***

*** Bug 429223 has been marked as a duplicate of this bug. ***

*** Bug 429256 has been marked as a duplicate of this bug. ***

*** Bug 429588 has been marked as a duplicate of this bug. ***

*** Bug 430833 has been marked as a duplicate of this bug. ***

*** Bug 430836 has been marked as a duplicate of this bug. ***

*** Bug 430902 has been marked as a duplicate of this bug. ***

*** Bug 430983 has been marked as a duplicate of this bug. ***

*** Bug 431249 has been marked as a duplicate of this bug. ***

*** Bug 431332 has been marked as a duplicate of this bug. ***

*** Bug 431769 has been marked as a duplicate of this bug. ***

*** Bug 433738 has been marked as a duplicate of this bug. ***

*** Bug 434372 has been marked as a duplicate of this bug. ***

*** Bug 436111 has been marked as a duplicate of this bug. ***

*** Bug 439033 has been marked as a duplicate of this bug. ***

*** Bug 440138 has been marked as a duplicate of this bug. ***

*** Bug 440183 has been marked as a duplicate of this bug. ***

*** Bug 440726 has been marked as a duplicate of this bug. ***

*** Bug 440773 has been marked as a duplicate of this bug. ***

*** Bug 441752 has been marked as a duplicate of this bug. ***

*** Bug 448418 has been marked as a duplicate of this bug. ***

*** Bug 447850 has been marked as a duplicate of this bug. ***

*** Bug 447798 has been marked as a duplicate of this bug. ***

*** Bug 426039 has been marked as a duplicate of this bug. ***

*** Bug 379968 has been marked as a duplicate of this bug. ***

*** Bug 454474 has been marked as a duplicate of this bug. ***

*** Bug 456650 has been marked as a duplicate of this bug. ***

*** Bug 375012 has been marked as a duplicate of this bug. ***

*** Bug 449164 has been marked as a duplicate of this bug. ***

*** Bug 477973 has been marked as a duplicate of this bug. ***

*** Bug 477477 has been marked as a duplicate of this bug. ***

*** Bug 477364 has been marked as a duplicate of this bug. ***

*** Bug 470320 has been marked as a duplicate of this bug. ***

*** Bug 480462 has been marked as a duplicate of this bug. ***

*** Bug 480853 has been marked as a duplicate of this bug. ***

*** Bug 482512 has been marked as a duplicate of this bug. ***

*** Bug 484359 has been marked as a duplicate of this bug. ***

*** Bug 495164 has been marked as a duplicate of this bug. ***

*** Bug 495308 has been marked as a duplicate of this bug. ***

*** Bug 500369 has been marked as a duplicate of this bug. ***

*** Bug 508529 has been marked as a duplicate of this bug. ***

*** Bug 514225 has been marked as a duplicate of this bug. ***

*** Bug 516932 has been marked as a duplicate of this bug. ***