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 413386 - crash in System Log: I moving reading lines o...
crash in System Log: I moving reading lines o...
Status: RESOLVED DUPLICATE of bug 355887
Product: gnome-utils
Classification: Deprecated
Component: logview
2.16.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-01 10:06 UTC by estri
Modified: 2007-03-06 16:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description estri 2007-03-01 10:06:39 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I moving reading lines of log, moving the horizontal scroll.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 56061952 vsize: 0 resident: 56061952 share: 0 rss: 14299136 rss_rlim: 0
CPU usage: start_time: 1170318006 rtime: 0 utime: 526 stime: 0 cutime:488 cstime: 0 timeout: 38 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 -1224587600 (LWP 4890)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 114863

Thread 1 (Thread -1224587600 (LWP 4890))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strrchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-03-01 16:57:32 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 355887 ***






Comment 2


estri





          2007-03-02 12:15:01 UTC
        



Hi there:

Yeah, Susana, I can, but I just see the other bug report, and it has a lot of feedback (comments). I would like to help, but no too time to read them all. If is there any specific question (and if I can answer it), I have really no problem at all.

Cheers, Ibon.






Comment 3


Susana





          2007-03-02 12:48:43 UTC
        



Hi Ibon,

From comment #158:
"Does anybody of the reporters run gnome 2.17.x and can still reproduce
this? Thanks for your help!"

The developers think this issue is already fixed but they need a confirmation from someone who experienced this bug.






Comment 4


estri





          2007-03-06 16:12:28 UTC
        



Hi again:

I'm sorry but I am using Ubuntu Dapper (GNOME 2.16) and I can't confirm that on 2.17.x.

Cheers, Ibon.