Opened sudo gedit -> Apport said pidgin crashed... when it didn't. -> gedit crashed -> apport failed to report the pidgin crash -> apport notified me of gedit crashing 3 minutes later.
Bug #349745 reported by
Michael Jones
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
interestingly enough, non-sudo gedit stayed online.
I was running the suspend/resume testing just before i rebooted and tried to do this (unrelated) stuff
pidgin didn't crash.. I don't know why it said it did.
I don't know what to tell you.. half of the time when apport says something crashed I don't even know what i was doing at the time, nor what the package it claims crashed does or is.
This is the only time a program that *I* started within a few minutes of boot crashed and apport reported it, normally about 5 or 4 programs that I don't even know about crash.
heres a screenshot.. I don't know how to reproduce this issue, nor do I really know exactly what happened.
Revision history for this message
| Michael Jones (jonesmz) wrote | #1 |
| affects: | ubuntu → apport (Ubuntu) |
Revision history for this message
| Marco Scannadinari (zheoffec) wrote | #2 |
Revision history for this message
| Mörgæs (moergaes) wrote | #3 |
| Changed in apport (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
jonesmz, Always use gksu or gksudo for GTK apps or apps with a UI, and sudo for CLIs (Apps run from the command line).
And if you know what bug apport was trying to report in the firs place, simply press Alt + F2, or open a terminal, and type 'ubuntu-bug gedit', or whatever package you would like to file a bug against.