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 305426 - Launcher results make best segfault
Launcher results make best segfault
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2005-05-25 12:55 UTC by Lukas Lipka
Modified: 2005-05-27 19:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lukas Lipka 2005-05-25 12:55:23 UTC
When I get a result which is type of Launcher in Best, I get Segmentation fault
in the console. No other errors or traces.
Comment 1 Joe Shaw 2005-05-25 18:59:02 UTC
What mono version?
Comment 2 Lukas Lipka 2005-05-25 19:57:36 UTC
Im using 1.1.7. But maybe there is another problem. Sometimes the whole computer
just freezes (I suspect this to be the NVidia driver) and I have to do a hard
reset the machine, and then I come across corrupted files. Sometimes the system
doesnt even start. So maybe this may be the case of a corrupted file.
Comment 3 Lukas Lipka 2005-05-26 07:32:55 UTC
I reverted today to "24 May 2005". I get no crashes or segfaults. So this can be
the multiproperty patch causing this?
Comment 4 Seb Payne 2005-05-26 12:51:46 UTC
Using instructions from dsd, I reverted out the multi-value properties commit
which fixed the Segmentation Failure on Best. Using Mono 1.1.7 on Ubuntu Hoary.
Comment 5 knvijay 2005-05-27 12:11:44 UTC
I too found this problem and debugged the code and found that Template.cs (line 
133) would set formatter = null; and the following switch (formatter) would do 
a NullPointerException. I have checked in a fix y'day. Can some verify the fix 
is fine ? 

thanks
Comment 6 Joe Shaw 2005-05-27 19:46:02 UTC
The fix wasn't quite right, but I found the bug and fixed it in CVS.