I want to submit my experience with beta3

  • SEO Honolulu
Posted: Thu, 03/19/2009 - 22:55
Hey everyone. Never been involved in a test phase of a distro, but I would definitely like to get involved. Specifically, I would like to share what happens at boot and at shutdown. How can I save this info into text files to my desktop for example? Also, if you could, tell me exactly what you want me to test on my system via command line, and I'll be happy to post up what I got. Thanks :D

share what happens at boot and at shutdown

  • skullnotions
  • 09/29/07
  • Sat, 03/21/2009 - 20:01
Hi SEO Honolulu, $ cp seohonolulu.txt seohonolulu-all.txt $ gedit seohonolulu.txt (delete first entry nautilus[4417]: segfault) (save file) $ grep 1ubuntu1 seohonolulu.txt Mar 20 18:03:32 64studio syslogd 1.5.0#1ubuntu1: restart. Mar 20 18:17:37 64studio syslogd 1.5.0#1ubuntu1: restart. Mar 20 18:20:53 64studio syslogd 1.5.0#1ubuntu1: restart. The report.txt now has entries for 3 boots. $ cp seohonolulu.txt seohonolulu-c.txt $ gedit seohonolulu-c.txt (delete first two boot entries) ("leaving last boot only") $ grep 1ubuntu1 seohonolulu-c.txt Mar 20 18:20:53 64studio syslogd 1.5.0#1ubuntu1: restart. (last boot only) $ grep segfault seohonolulu-c.txt Examples: $ grep sda seohonolulu-c.txt $ grep IRQ seohonolulu-c.txt $ grep Warning seohonolulu-c.txt $ grep warning seohonolulu-c.txt $ grep ICE1712 seohonolulu-c.txt $ grep disabled seohonolulu-c.txt All of this started from here: $ cat /var/log/messages >messages.txt Will create messages.txt file in your ~/ directory $ grep "keyword" messages.txt Get to know your system. Play around with grep\find they are powerful tools. You will soon be able to provide valuable information for the development of 64studio. Tweaks and setting up your audio system become easier with practice and your testing will make sure we keep 64studio at the leading edge yet still stable. There are great Tweaks and howto's on the forum. The search function is one of the best ways to further your Testing\reporting skills. Happy Hacking ;-) Cheers! Dave.

report method ~/beta3-seohonolulu

  • skullnotions
  • 09/29/07
  • Sat, 03/21/2009 - 12:49
Hi SEO Honolulu, I have saved your report as ~/seohonolulu.txt This is my method to try to understand what's going on. First I've created a file.txt of your report. I also create ~/beta3-seohonolulu file and write the replies to your posts in that file using "Markdown Syntax" so when I copy\paste to the forum the format is ok. Then I'll check to see if I have the same issue. Other testers should do the same and report there findings. If an error is reproduced by multiple users the first place of call is to see if theres already a ticket for the error\issue. $ grep segfault seohonolulu.txt (or) $ grep nautilus seohonolulu.txt Mar 20 18:02:37 64studio kernel: [ 1263.646262] nautilus[4417]: segfault at 4500002c ip 00007f6aef069f0f sp 00007ffffa616d30 error 4 in libgconf-2.so.4.1.5[7f6aef046000+37000] Mar 20 18:16:41 64studio kernel: [ 805.953164] nautilus[4421]: segfault at 4900002c ip 00007f323e6c7f0f sp 00007fff49c749c0 error 4 in libgconf-2.so.4.1.5[7f323e6a4000+37000] Using Keywords: Check my logfiles: $ sudo grep segfault /var/log/boot $ sudo grep segfault /var/log/dmesg $ sudo grep segfault /var/log/kern.log $ sudo grep segfault /var/log/lastlog $ sudo grep segfault /var/log/messages $ sudo grep segfault /var/log/syslog Run the same using grep nautilus. I get no returns. Because I edited my .bashrc "bashrc grep history" post, I run: $ h find (This returns all my previous .bash_history find entries. $ sudo find / -name "*libgconf-2.so" (no returns) $ sudo find / -name "*libgconf-2.so.4.1.5" (returns) /usr/lib/libgconf-2.so.4.1.5 Google: nautilus[4417]: segfault at 4500002c ip 00007f6aef069f0f sp 00007ffffa616d30 error 4 in libgconf-2.so.4.1.5[7f6aef046000+37000] (no returns) Google: nautilus[4417]: segfault at 4500002c returns http://pastebin.com/m632010fb Google: nautilus[4417]: segfault = (hits now) On with searching now. Cheers! Dave.

http://paste.ubuntu.com/13468

  • SEO Honolulu
  • 07/08/08
  • Sat, 03/21/2009 - 07:21
http://paste.ubuntu.com/134683/ Ok so here we go. On line 1, i wanted to show you a repeating issue I have.. a segfault related to nautilus during shutdown. the rest of it is all boot up. Specifically line 7 which gives an error at boot. Please have a look at the rest and let me know if you spot anything suspicious.. cuz I wouldn't know any better lol. Thanks :)

Managing your log files & Markdown Syntax

  • skullnotions
  • 09/29/07
  • Sat, 03/21/2009 - 02:35
Nice little howto. Checkout tuxradar. The forum uses "Markdown Syntax". This is why when you copy\paste text the format changes. To get line 4 "This is ...." below line 3 "The forum ...." I had to put 2 spaces at the end of the line 3, then hit the Enter key. Until you get the hang of Markdown Syntax http://paste.ubuntu.com is handy. Cheers! Dave.

boot verbose

  • skullnotions
  • 09/29/07
  • Fri, 03/20/2009 - 05:25
Hi, Check out: Main Menu > System > Administration > System Log. or once you have key words search your logs using grep: e.g. acpi $ ls -a /var/log/ $ sudo grep acpi /var/log/messages $ sudo grep hda /var/log/messages $ sudo grep acpi /var/log/syslog $ sudo grep hda /var/log/syslog $ grep WW /var/log/Xorg.0.log $ grep EE /var/log/Xorg.0.log $ grep II /var/log/Xorg.0.log $ dmesg $ dmesg >64s30b3-dmesg.txt The second command will create 64s30b3-dmesg.txt file in your ~/ directory $ cat /var/log/messages >64s30b3-messages.txt Will create 64s30b3-messages.txt file in your ~/ directory More command line here: Cheers! Dave.