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 431243 - crash in System Log: I was invoking this menu...
crash in System Log: I was invoking this menu...
Status: RESOLVED DUPLICATE of bug 366458
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-04-19 05:32 UTC by ronled
Modified: 2007-04-20 01:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ronled 2007-04-19 05:32:17 UTC
Version: 2.16.0

What were you doing when the application crashed?
I was invoking this menu option when the Bug Reporting Tool stopped me
system -> administration  -> system log


I am having trouble getting ShoreWall to start

The last few lines of a trace debugging option when starting Shorewall are as follows

+ command=-A
+ shift 7
+ '[' -n '' -a -n '' ']'
+ '[' -n '' ']'
++ printf Shorewall:%s:%s: net2wifi DROP
+ prefix=Shorewall:net2wifi:DROP:
+ '[' 24 -gt 29 ']'
+ case $level in
+ /sbin/iptables -A net2wifi -j LOG --log-level 8/sec:30 --log-prefix Shorewall:net2wifi:DROP:
iptables v1.3.5: log-level `8/sec:30' unknown
Try `iptables -h' or 'iptables --help' for more information.
+ '[' 2 -ne 0 ']'
+ '[' -z '' ']'
+ stop_firewall
+ case $COMMAND in
+ set +x
/sbin/shorewall: line 225: 15242 Terminated              ${VARDIR}/.start $debugging start


This may be less mystifying to someone other than me.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 88166400 vsize: 0 resident: 88166400 share: 0 rss: 13033472 rss_rlim: 0
CPU usage: start_time: 1176956768 rtime: 0 utime: 15 stime: 0 cutime:12 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208240432 (LWP 10382)]
(no debugging symbols found)
0x00258402 in __kernel_vsyscall ()

Thread 1 (Thread -1208240432 (LWP 10382))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_main_quit
  • #5 gtk_main_quit
  • #6 gtk_main_quit
  • #7 gtk_main_quit
  • #8 gtk_main_quit
  • #9 gtk_main_quit
  • #10 __libc_start_main
    from /lib/libc.so.6
  • #11 gtk_main_quit
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Shorewall is stopped
State:Stopped (Wed Apr 18 21:14:58 PDT 2007)
shorewall
Shorewall-3.4.2 Status at slowpoke.outerspace.localdomain - Wed Apr 18 21:22:53 PDT 2007
Shorewall is stopped
State:Stopped (Wed Apr 18 21:14:58 PDT 2007)
** (bug-buddy:10359): WARNING **: Couldn't load icon for Open Folder
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2e00003 (Bug Buddy); these messages lack timestamps and therefore suck.
** (bug-buddy:10384): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-04-20 01:31:02 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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