[Dapper Flight 3] Full load cpu with gnome-system-log (Random)

Thanks for your bug. Could you get a backtrace when you start it?
- gdb gnome-system-log
(gdb) run
... after some seconds of cpu eating
<ctrl-C>
(gdb) thread apply all bt

Subject: gnome-utils: Full load cpu with gnome-system-log (Random)
Package: gnome-utils
Version: 2.13.92-0ubuntu1
Severity: important

== Info ==
caravena@hefesto:~$ gdb gnome-system-log
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/gnome-system-log
(no debugging symbols found)
[Reppeat message...]

---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
[Reppeat message...]

[Thread debugging using libthread_db enabled]
[New Thread 1997375168 (LWP 19468)]
(no debugging symbols found)
[Reppeat message...]

---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
[Reppeat message...]

---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
[Reppeat message...]

Program exited normally.
(gdb) run

=== Pre Configuration program ===
* Open gnome-system-log
* Select log_=/var/log/ log_apic, log_kern.log, log_message, etc.
* Quit

=== Open Program ===
* Open gnome-system-log
* Default select in log_apic
* program log_apic strong/black
* I select with touchpad log_apic

== Problem ==
* CPU FULL LOAD in 50 seconds or pluss
* Change log_acpi many seconds pluss (I's Random)

Notes:
* gnome-system-log not crash
* gnome-system-log problem with log_acpi

Hardware:
https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresarioV2417LA

Many Thanks,
Caravena

-- System Information:
Ubuntu Release: testing/unstable/Dapper Flight 4
  APT prefers dapper
  APT policy: (500, 'dapper')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-16-k7
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)

Versions of packages gnome-utils depends on:
ii e2fslibs 1.38-2ubuntu1 ext2 filesystem libraries
ii gconf2 2.13.5-0ubuntu1 GNOME configuration database syste
ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi
ii libatk1.0-0 1.11.2-0ubuntu1 The ATK accessibility toolkit
ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio
ii libavahi-client3 0.6.7-1ubuntu1 Avahi client library
ii libavahi-common3 0.6.7-1ubuntu1 Avahi common library
ii libavahi-glib1 0.6.7-1ubuntu1 Avahi glib integration library
ii libbonobo2-0 2.13.1-0ubuntu2 Bonobo CORBA interfaces library
ii libbonoboui2-0 2.13.1-0ubuntu1 The Bonobo UI library
ii libc6 2.3.6-0ubuntu6 GNU C Library: Shared libraries an
ii libcairo2 1.0.2-3ubuntu1 The Cairo 2D vector graphics libra
ii libdbus-1-2 0.60-2ubuntu12 simple interprocess messaging syst
ii libesd-alsa0 [libesd0 0.2.36-3ubuntu2 Enlightened Sound Daemon (ALSA...

dbg, gnome-sysmtem-log y cpu FULL LOAD in many secons.

2006/2/17, Sebastien Bacher <email address hidden>:
> Comment:
> Thanks for your bug. Could you get a backtrace when you start it?
> - gdb gnome-system-log
> (gdb) run
> ... after some seconds of cpu eating
> <ctrl-C>

Ok, ok.... Sorry, no read...

(no debugging symbols found)

Program received signal SIGINT, Interrupt.
[Switching to Thread 1997043392 (LWP 21409)]
0x77a00916 in gtk_tree_store_move_after () from /usr/lib/libgtk-x11-2.0.so.0
(gdb)

Many Thanks,
Caravena

could you type "thread apply all bt" on the gdb prompt you get after the ctrl-C as indicated by the previous comment?

2006/2/25, Sebastien Bacher <email address hidden>:
> Comment:
> could you type "thread apply all bt" on the gdb prompt you get after the
> ctrl-C as indicated by the previous comment?

* $gdb gnome-system-log
[...]

* gdb run
[...]

Use Program...
** In gnome-system-log open files log, message, kern.log, acpid, etc.
** Select [kern.log|message| NOT acpid] (Read message)
** In log acpid strong
** Change of [kern.log|message| NOT acpid] to acpid
** Use CPU 100%, gnome-system-log stop in many^N seconds.

* Ctrl-C, message:

(no debugging symbols found)

Program received signal SIGINT, Interrupt.
[Switching to Thread 1997043392 (LWP 21409)]
0x77a00916 in gtk_tree_store_move_after () from
/usr/lib/libgtk-x11-2.0.so.0 (gdb)

Many Thanks,
Caravena

you still did type "thread apply all bt", your comment has still no backtrace ...

Debbuging Program:

* Install libglib2.0-0-dbg libgtk2.0-0-dbg
* Run $gdb gnome-systems-log
* Open logs: acpid, kern.log, etc.
* Not select acpid (example: kern.log), strong acpid and select acpid.
** Results: CPU ~99% use.
* Ctrl+C
* Press Enter and regrese to dbg
* Write "thread apply all bt" and press enter.
* Copy paste in file gdb_gnome-system-log.txt

Many Thanks,
Caravena

Does gnome-system-log say something if you start it from the terminal?

2006/3/2, Daniel Holbach <email address hidden>:
> Comment:
> Does gnome-system-log say something if you start it from the terminal?

gnome-system-log problem a run in console and icon. Nor run in
terminal for use dbg and show problem.

thank you so much,
Cristian Aravena Romero

I'm afraid I don't understand. Could you paste the output, if you start gnome-terminal and type
          gnome-system-log

and start it? Does it say anything?

I'm sorry... Now new report:

Description of problem:
Full load cpu to run gnome-system-log.

Version-Release number of selected component:
gnome-utils 2.14.0-0ubuntu1.

How reproducible:
Run in console gnome-system-log, open /var/log/*, select not log acpid (example: /var/log/kern.log) and select in strong /var/log/acpid.

Steps to Reproduce:
1. Install package for debug libglib2.0-0-dbg and libgtk2.0-0-dbg
2. Run with gdb
caravena@hefesto:/var/log$ gdb gnome-system-log
[...]

(gdb) run
Starting program: /usr/bin/gnome-system-log
(no debugging symbols found)
[Repeat message...]

[Thread debugging using libthread_db enabled]
[New Thread -1223382272 (LWP 21087)]

3. Select /var/log/kern.log, in moment /var/log/acpid strong, now select /var/log/acpid (not change message in console in gdb). Now Full Load cpu in many minutes, now press Ctrl+C.
Program received signal SIGINT, Interrupt.
[Switching to Thread -1223382272 (LWP 21087)]
0xb7ac8a36 in gtk_tree_store_get_path (tree_model=0x87c0198, iter=0xbffde20c)
    at gtktreestore.c:610
610 gtktreestore.c: No existe el fichero o el directorio.
---Type <return> to continue, or q <return> to quit---
        in gtktreestore.c
4. Now write "thread apply all bt"
(gdb) thread apply all bt

Thread 1 (Thread -1223382272 (LWP 21087)):
#0 0xb7ac8a36 in gtk_tree_store_get_path (tree_model=0x87c0198,
    iter=0xbffde20c) at gtktreestore.c:610
#1 0xb7ac906b in IA__gtk_tree_store_insert_before (tree_store=0x87c0198,
    iter=0xbffde20c, parent=0x0, sibling=0x0) at gtktreestore.c:1240
#2 0xb7ac9235 in IA__gtk_tree_store_append (tree_store=0x87c0198,
    iter=0xbffde20c, parent=0x0) at gtktreestore.c:1454
#3 0x0804efa0 in ?? ()
#4 0x087c0198 in ?? ()
#5 0xbffde20c in ?? ()
#6 0x00000000 in ?? ()

Actual results:
Full load cpu in many minutes in select /var/log/acpid in strong.

Expected results:
Change of /var/log/* to log acpid y not full load.

Additional info:
- Configuration delfault of gnome-system-log http://img211.imageshack.us/my.php?image=configurationofgnomesystemlog1.png
- https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresarioV2417LA

could you run a "ls -lh /var/log/acpid"?

2006/3/17, Sebastien Bacher <email address hidden>:
> Comment:
> could you run a "ls -lh /var/log/acpid"?

Sebastien:

caravena@hefesto:~$ ls -lh /var/log/acpid
-rw-r----- 1 root adm 7,1M 2006-03-17 13:32 /var/log/acpid

7.1M of gzip is quite some data and not trivial to parse, it should be logrotated. I'm not sure if that's a bug ...

2006/3/18, Sebastien Bacher <email address hidden>:
> Comment:
> 7.1M of gzip is quite some data and not trivial to parse, it should be
> logrotated. I'm not sure if that's a bug ...

Sebastien:

ok, not is bug (Not Crash). Problem is "optimitation"

Information of Hardware;
* CPU: AMD Sempron 3000+ (1.7 Ghz and 128L2)
* 512Mbyte RAM
Comment: Computer very fast.

In console write "time gnome-system-log" select kern.log in 10 seconds
strong /acpid/, select /acpid/ and revise in new terminal with top
(full load gnome-system-log). Many time, in console press Ctrl+C.

Results:

- caravena@hefesto:~$ time gnome-system-log
 real 27m7.428s
 user 25m3.207s
 sys 0m4.026s
[Not load acpid and press Ctrl+C]

Many time in read acpid

Many Thanks,
Cristian Aravena Romero

2006/3/18, Sebastien Bacher <email address hidden>:
> Comment:
> 7.1M of gzip is quite some data and not trivial to parse, it should be
> logrotated. I'm not sure if that's a bug ...

Sebastien Bacher:

caravena@hefesto:~$ ls -lh /var/log/acp*
-rw-r----- 1 root adm 7,5M 2006-03-19 01:12 /var/log/acpid
-rw-r----- 1 root adm 352K 2006-03-12 07:36 /var/log/acpid.1.gz
-rw-r----- 1 root adm 478K 2006-03-06 14:49 /var/log/acpid.2.gz
-rw-r----- 1 root adm 193K 2006-02-26 07:35 /var/log/acpid.3.gz

1) acpid.[1...3].gz is gzip
2) acpid is gzip?

2006/3/19, Cristian Aravena Romero <email address hidden>:

[...]

> caravena@hefesto:~$ ls -lh /var/log/acp*
> -rw-r----- 1 root adm 7,5M 2006-03-19 01:12 /var/log/acpid
> -rw-r----- 1 root adm 352K 2006-03-12 07:36 /var/log/acpid.1.gz
> -rw-r----- 1 root adm 478K 2006-03-06 14:49 /var/log/acpid.2.gz
> -rw-r----- 1 root adm 193K 2006-02-26 07:35 /var/log/acpid.3.gz
>
> 1) acpid.[1...3].gz is gzip
> 2) acpid is gzip?

Couting lines:

caravena@hefesto:~$ vi /var/log/acpid
[...]

In spanish:
"/var/log/acpid" [Solo lectura] 136712L, 9188051C 1,1 Comienzo

In resumen is:
* <importat>136712</important> _LINES_
* parse of 136712 lines in 25 minutes?

Howto Debug program?

Many Thanks,
Cristian

Thank you for forwarding the bug upstream

I update Bios and packages.

Now not problem, I work with edgy.

marking as fixed then, feel free to reopen if you get the issue again