I understand the request for not attaching a crash file, so the preferred method is for me to open up another bug report and what link to it, what for it to be duplicated checked, posting info there till it gets dupped, then posting requested info on original? Is this a temporary situation ? Till, a time when we can attach additional info to a current crash report ? This sounds like a lot more work for you'all. Since isn't there some commands to run off a full crash report that would give you a lot of info you'all might need, and is a somewhat easy way to confirm a crash or not. If this is the perferred method, then that explains why there are so many bugs filed, when I go to file a report, I sometimes have to choose between multiple reports with the default name, which is what I like to use, when a crash self reports, and between whatever bug name such reporter chooses to use, then which one ? the newest one, the oldest number one ? the one last touched, and invalid one, an incomplete one ? I guess it doesn't matter if you just file a new one everytime.
I am using the current Ubuntu Hardy Heron 8.04 Alpha , as far as I know. I only ran the Live C.D. for a little while to try to test so stuff, and try to upgrade off it, which I don't seem to know how to do, without re-installing everything. This is a upgrade from Alpha 4 to Alpha 5 via internet. -- nautilus crashed with SIGSEGV in __pthread_mutex_unlock_usercnt() https://bugs.launchpad.net/bugs/180795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
