On Wed, Jul 11, 2007, E L wrote: > 1) I installed 2.18.3-3 and saw that the problem is still there
Ok; perhaps it's not exactly the same problem. > 2) I apt-get source for the sources of 2.18.3-3 > 3) I looked at the source and saw: You were looking at an unpatched source tree; the patches below debian/patches are applied during the build. > Did I look at the wrong source? > Was I suppose to run some other command rather than apt-get source? apt-get source is correct, make sure it's the correct source which you fetch (2.18.3-3). But to see the patched source, you need to run "quilt" as I explained in my other mail. To build the package, you simply need to run dpkg-buildpackage. If you run ./configure manually, the patches wont get applied, but you can patch manually and run ./configure manually if you like. Don't patch manually and run dpkg-buildpackage though. Please let me know whether you still get the issue with the patched source and ./configure or with a dpkg-buildpackage built package. As you can see in the patched source or in the patch I mentionned, the same fix should already be present. -- Loïc Minier