Craig Maloney [2008-06-03 2:05 -]:
enabled=1
OK, that should work. After you get a crash, what does
/var/log/apport.log contain? You can easily generate a fake crash
with opening a Terminal and typing
bash -c 'kill -SEGV $$'
--
produces empty core dumps
OK, that seemed to work. It must be something else then, because I'm
trying to get a crash report for Rhythmbox, and while the app disappears
repeatedly when I perform a certain task, I can't seem to generate a
crash dump off of that.
Thanks for the pointers!
--
produces empty core dumps
Hi,
Craig Maloney [2008-05-31 3:34 -]:
I can confirm this is an issue with an upgrade from Gutsy to Hardy. I am
experiencing exactly the same behavior mentioned above. I'm not
receiving any crash reports, even though apport is supposedly running.
NB that apport is turned off by default
I agree, but this is the settings in /etc/default/apport. I'm not sure
how more enabled I can make it, yet I'm still not receiving anything in
/var/crash when I crash an application.
# set this to 0 to disable apport, or to 1 to enable it
enabled=1
# set maximum core dump file size (default:
I can confirm this is an issue with an upgrade from Gutsy to Hardy. I am
experiencing exactly the same behavior mentioned above. I'm not
receiving any crash reports, even though apport is supposedly running.
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this
(gdb) info registers
eax0xfdfc -516
ecx0x6 6
edx0x63 99
ebx0x87d1398142414744
esp0xbfdeb484 0xbfdeb484
ebp0xbfdeb4a8 0xbfdeb4a8
esi0x63 99
edi0xb6e84ff4
** Attachment added: apport.log
http://launchpadlibrarian.net/12547730/apport.log
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
linuxatico88, you attached a test suite run which is invalid because you
ran it as root. Please run it as normal user.
Do you also have the problem? Your reply did not have any explanations
or context.
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug
** Changed in: apport (Ubuntu)
Status: New = Fix Released
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
cool, thanks.
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
miked, your run looks good, the test suite passed. I haven't seen this
anywhere else on Hardy any more, so I'm closing this.
** Changed in: apport (Ubuntu Gutsy)
Status: Incomplete = Fix Released
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug
[EMAIL PROTECTED]:~# /usr/share/apport/testsuite/test-apport kernel 21 | tee
/tmp/test-kernel.out
* Check that empty core dumps do not generate a report
* Check test process creation/killing with apport
* Check that a subsequent crash does not alter unseen report
* Check that a subsequent crash
Added Info
** Tags added: hardyheronalpha4
** Changed in: apport (Ubuntu)
Status: Incomplete = New
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: apport-test.out
http://launchpadlibrarian.net/9602828/apport-test.out
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
BTW, the effect of filing useless bugs is mitigated with
apport (0.86) gutsy; urgency=low
* test-apport: Check that apport does not create reports for emtpy core
dumps.
* problem_report.py: Introduce a fourth optional parameter fail_on_empty
to file pointer tuples which causes
Removing milestone, since it does not generate bug spam any more. It
does, however, prevent bugs to be filed under some circumstances.
** Changed in: apport (Ubuntu Gutsy)
Importance: High = Medium
Target: tribe-3 = None
--
produces empty core dumps
Thanks, folks, for the logs so far, this gave me an initial idea. Can
you please now do the following:
/usr/share/apport/testsuite/test-apport kernel 21 | tee /tmp/test-
kernel.out
And attach /tmp/test-kernel.out and /var/log/apport.log now? If
/var/log/apport.log does not exist, don't bother
There's no /var/log/apport.log
** Attachment added: test-kernel.out
http://launchpadlibrarian.net/8221153/test-kernel.out
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I've install 'build-essential'
** Attachment added: test-kernel.out
http://launchpadlibrarian.net/8221184/test-kernel.out
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
not a gnome-speech bug, closing this task.
** Changed in: gnome-speech (Ubuntu)
Status: New = Invalid
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
RobertGradini,
sorry, I forgot to mention that you have to clean /var/crash/ before
running the test suite. Can you please do
sudo rm /var/crash/*
/usr/share/apport/testsuite/test-apport kernel 21 | tee /tmp/test-kernel.out
instead? Thank you!
--
produces empty core dumps
I'm sorry but there's a problem:
[EMAIL PROTECTED]:~$ /usr/share/apport/testsuite/test-apport kernel 21 | tee
/tmp/test-kernel.out
* Check test process creation/killing with apport
* Check that a subsequent crash does not alter unseen report
* Check that a subsequent crash alters seen report
*
Performed the actions as requested in Bug #122771, being:
Actually apport should work on this kernel again. Can you please do the
following:
sudo rm /var/crash/*
sudo rm /var/log/apport.log
/usr/share/apport/testsuite/run-tests 21 | tee /tmp/apport-test.out
and attach /tmp/apport-test.out and
The second file /var/log/apport.log was not present.
Please find attached the results of the last command as provided in the
instructions:
[EMAIL PROTECTED]:~$ /usr/share/apport/testsuite/run-tests 21 | tee
/tmp/apport-test.out
+ python -tt
Here is the whole thing in case if people are interested
[EMAIL PROTECTED]:~$ /usr/share/apport/testsuite/run-tests 21 | tee
/tmp/apport-test.out
+ python -tt /usr/share/python-support/python-problem-report/problem_report.py
-v
Test adding information to an existing report. ... ok
Test basic
tried /usr/share/apport/testsuite/test-apport kernel 21 | tee /tmp
/test-kernel.out
this happens
[EMAIL PROTECTED]:~$ sudo rm /var/crash/*
[sudo] password for shirish:
rm: cannot remove `/var/crash/*': No such file or directory
[EMAIL PROTECTED]:~$ /usr/share/apport/testsuite/test-apport kernel
FAIL: Test add_gdb_info() with a script.
--
Traceback (most recent call last):
File /usr/share/python-support/python-apport/apport/report.py, line 1179,
in test_add_gdb_info_script
self.assert_('libc.so' in
After talking with martin pitti I removed the core file :-
[EMAIL PROTECTED]:~$ rm core
[EMAIL PROTECTED]:~$ /usr/share/apport/testsuite/test-apport kernel 21 | tee
/tmp/test-kernel.out
* Check test process creation/killing with apport
* Check that a subsequent crash does not alter unseen
Here's the /var/log/apport.log for that session.
** Attachment added: apport.log
http://launchpadlibrarian.net/8223383/apport.log
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Thanks for the logs so far. So we just found out that bug 74691 is the
reason why 'run-tests' fails on i386. It works fine on amd64 and powerpc
(the platforms I'm testing on).
I will install i386 now to have a look at this myself.
--
produces empty core dumps
[EMAIL PROTECTED]:~$ LC_ALL=en_US apt-cache policy linux-image-`uname -r`
linux-image-2.6.22-7-generic:
Installed: 2.6.22-7.14
Candidate: 2.6.22-7.14
Version table:
*** 2.6.22-7.14 0
500 http://in.archive.ubuntu.com gutsy/main Packages
100 /var/lib/dpkg/status
--
produces
this is output from /tmp
[EMAIL PROTECTED]:~$ /usr/share/apport/testsuite/test-apport kernel 21 | tee
/tmp/test-kernel.out
Traceback (most recent call last):
File /usr/share/apport/testsuite/test-apport, line 147, in module
assert apport.fileutils.get_all_reports() == [], 'no reports
after talking with pitti, I did the following things :-
1. go to /var/crash :- rm *
2. then copied test apport to /tmp
cp /usr/share/apport/testsuite/test-apport /tmp
3. ran the test more than 15 times /tmp/test-apport kernel 21 | tee
/tmp/test-kernel.out
I get the same output as in
Can people who are affected by this please do the following:
sudo rm /var/crash/*
sudo rm /var/log/apport.log
/usr/share/apport/testsuite/run-tests 21 | tee /tmp/apport-test.out
and attach /tmp/apport-test.out and /var/log/apport.log to bug 122688?
Thanks a lot!
** Description changed:
** Attachment added: apport-test.out
http://launchpadlibrarian.net/8219966/apport-test.out
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: apport.log.1
http://launchpadlibrarian.net/8219967/apport.log.1
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I will attach the files you requested. It thought it may also be useful
to know that your final command ended as follows:
[snip]
Test search_bug_patterns(). ... ok
Test standard_title(). ... ok
==
FAIL: Test add_gdb_info() with
** Attachment added: apport-test.out
http://launchpadlibrarian.net/8220042/apport-test.out
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
It appears after running those commands that /var/log/apport.log does
not exist. I have attached the closest match (/var/log/apport.log.1),
although I guess this is just a backup or older log. I assume the
failure to create /var/log/apport.log was caused by the AssertionError
generated by the 3rd
** Attachment added: apport-test.out
http://launchpadlibrarian.net/8220417/apport-test.out
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: apport.log.1
http://launchpadlibrarian.net/8220418/apport.log.1
--
produces empty core dumps
https://bugs.launchpad.net/bugs/122688
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
41 matches
Mail list logo
