What info is necessary for a bug report? lazarus / 8-Other ---------------------------------------------------------------------- PingWin · 2006-11-30 09:53 I have problems under Linux using forms with Lazarus 0.9.20 and GTK 2.0. Basically when I set autoscroll or vert/horz scrollbar properties to true on a form my program crashes. Here are my questions: 1. What info should I gather for a bug report? 2. How do I find out the exact version of GTK I'm using? 3. A "diff" file has been posted on the bugtracker that might address the problem. What is a "diff" file and how do I use it ? 4. Can I undo a "diff" patch after it has been applied? Sorry for my newbie questions... Lazarus is a great project and I will definitely be using it a lot. ---------------------------------------------------------------------- Marc · 2006-11-30 10:29 If you haven't found it yet, info about patches can be found in the  wiki 1) for a bugrep, at least your os,  the laz and fpc version is needed. If you think you have widgetset problems, the version of that widgetset. 2) goto /usr/lib and do a ls -l libgtk* for gtk1 look where libgtk.so is pointing to for gtk2 look where libgtk-x11-2.0.so is pointing to alternatively, if you have a rpm based system, rpm -q gtk+ resolves the gtk1 version and rpm-q gtk2 resolves the gtk2 version 3) A diff file is a text file with the difference between 2 versions of a file. If you open it you see something like Code: [Select] -some line +some change this means that the first line gor replaces by the latter On the wiki page it is described how to use it. One thing missing: the diff file contains filenames with a relative or absolute path (or no path) with the -p parameter you specify how much of this path should be trimmed when applying a patch. Most patches are made within the lazarus dir, so the path is ok. therefor you specify -p0 4) you undiff by applying the same patch again. Usually the patch program tells you that the patch is already applied, so that it might be a reverse patch. Just to be sure,  use the patch -R option. (with a reverse patch, the meaning of the - and the + lines are reversed) ---------------------------------------------------------------------- PingWin · 2006-11-30 11:20 Thanks for your helpful response. I managed to find the gtk version (2.8.10-39.13) which was really the issue as I'm new to Linux (running Suse 10.1 OSS). As for the "diff" files I'm still a bit confused after readng the wiki because I didn't compile Lazarus from scratch using the source files or get it from SVN (as mentionned in the wiki). Instead I installed Lazarus via a third party RPM. Do I need to get the source files and compile from scratch to use "diff" files ? Once again, thanks for your help. ---------------------------------------------------------------------- Marc · 2006-12-03 13:59 that depends. Diff files are usually against some version of the source. It can be the same version as from your distro, or it can be based on a newer/older version of the files. Usually when a diff is made with SVN, the first lines contains the version of the original source used. If you want to use a patch for something not under heavy development, applying a patch on older/newer sources usually works. The patch program does some matching on surrounding lines. If a patch fails, it tells you so. (## out of ## chucks failed) Whan applying patches for lazarus, I usually use the latest SVN. In that case chances are big that the submittor of the patch didn't use the same source version. Only in a few cases I've to edit something manually. ---------------------------------------------------------------------- PingWin · 2006-12-04 13:55 Ok, I got it now. Thanks.