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 316830 - Crash after trying to open log without permission to do it
Crash after trying to open log without permission to do it
Status: RESOLVED DUPLICATE of bug 316738
Product: gnome-utils
Classification: Deprecated
Component: logview
2.12.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-21 08:05 UTC by Kjartan Maraas
Modified: 2005-09-25 22:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Kjartan Maraas 2005-09-21 08:05:37 UTC 
I opened the logviewer and it crashed after trying to open /var/log/acpid.log as
a normal user.

Backtrace was generated from '/usr/bin/gnome-system-log'

Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208387920 (LWP 3732)]
[New Thread -1224258640 (LWP 3750)]
[New Thread -1223992400 (LWP 3749)]
[New Thread -1223722064 (LWP 3747)]
[New Thread -1223447632 (LWP 3734)]
0x00bff402 in __kernel_vsyscall ()

+ Trace 63114

Thread 1 (Thread -1208387920 (LWP 3732))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 749 






Comment 1


Kjartan Maraas





          2005-09-21 08:23:07 UTC
        



This happens if you just open gnome-system-log and click on the WM's close
window "button"






Comment 2


Vincent Noel





          2005-09-21 14:48:15 UTC
        



I just committed the patch in bug #316738 that seems to fix a similar crash. Is
this crash happening with CVS ?






Comment 3


Kjartan Maraas





          2005-09-25 22:02:00 UTC
        



Yeah, this is fixed now.

*** This bug has been marked as a duplicate of 316738 ***