Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[wuischke]

The dsc file: http://archive.ubuntu.com/ubuntu/pool/main/libx/libx11/libx11_1.1.99.2-1ubuntu2.dsc

The package name is "libx11".

Regarding the patch:

Download the patch and save it to xlib-fix.patch
$ cd xlib...
$ cat ../xlib-fix.patch | patch -p1

[Impactor]

Ok, but I don't have any "xlib" folder which means I cannot do "cd xlib..."

[wuischke]

Sorry for not giving exact instructions. You have by some means (either my stupid manual way or btkaos' nice automatic way) extracted the source files, haven't you?

Please cd in this folder. The name might be libx11 or similar.

[Impactor]

Thanks, but now I am stuck here:

Code: [Select]

~/Desktop/patch/libX11-1.1.99.2$ sudo apt-get build-dep xlib
Reading package lists... Done
Building dependency tree       
Reading state information... Done
W: Duplicate sources.list entry http://gb.archive.ubuntu.com jaunty-updates/universe Packages (/var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_jaunty-updates_universe_binary-amd64_Packages)
W: You may want to run apt-get update to correct these problems
E: Unable to find a source package for xlib


[wuischke]

You might have to activate the source repository first. (Or try to execute "dpkg-buildpackage" and install the packages it says are missing.)

(Source with Screenshot) To activate them with Synaptic, go to Settings -> Repositories in the package manager. There are 5 check boxes, the fifth reads "source", check it. Afterwards click on reload.

[Impactor]

As soon as one problem's down, another's up:

Code: [Select]

~/Desktop/patch/libX11-1.1.99.2$ sudo apt-get build-dep xlib
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to find a source package for xlib


[wuischke]

The package's name is libx11, our instructions were not very exact in this regard.

Execute "sudo apt-get build-dep libx11" instead.

[Impactor]

Great. We are moving forward, albeit slowly:

Code: [Select]

~/Desktop/patch/libX11-1.1.99.2$ sudo dpkg-buildpackage
dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package libx11
dpkg-buildpackage: source version 2:1.1.99.2-1ubuntu2
dpkg-buildpackage: source changed by Bryce Harrington <bryce@ubuntu.com>
dpkg-buildpackage: host architecture amd64
 debian/rules clean
Can't exec "debian/rules": Permission denied at /usr/bin/dpkg-buildpackage line 510.
dpkg-buildpackage: failure: debian/rules clean failed with unknown exit code -1


[wuischke]

Code: [Select]

chmod +x debian/rules

[Impactor]

Great, almost done:

Code: [Select]

dpkg-deb: building package `libx11-xcb-dev' in `../libx11-xcb-dev_1.1.99.2-1ubuntu2_amd64.deb'.
dpkg-deb: ignoring 1 warnings about the control file(s)
 signfile libx11_1.1.99.2-1ubuntu2.dsc
gpg: WARNING: unsafe ownership on configuration file `/home/juha/.gnupg/gpg.conf'
gpg: skipped "Bryce Harrington <bryce@ubuntu.com>": secret key not available
gpg: [stdin]: clearsign failed: secret key not available

 dpkg-genchanges  >../libx11_1.1.99.2-1ubuntu2_amd64.changes
dpkg-genchanges: not including original source code in upload
dpkg-buildpackage: binary and diff upload (original source NOT included)
dpkg-buildpackage: warning: Failed to sign .dsc and .changes file


[wuischke]

I believe you can safely ignore this message. There should now be a libx11-xbc_1.1.99.2-1ubuntu2_amd64.deb package in the parent directory of the directory in which you were building the packages.

Please install this package (dpkg -i libx11[...].deb or using gdebi) and you should be done.

[Impactor]

I did as you said although there were 8 other DEB files there. Should I ignore the rest?

[wuischke]

I think this should be enough. You were doing this to replace one file with the bug inside, after all.

Now you should try what made crash aMule previously and see if it's resolved now.

[Impactor]

I am unable to replicate this bug at will as it seems that it was not necessarily connected to losing connection. However, it should occur within 1-2 days, if it has not been resolved. Will report back if it does.

Thank you for being extremely helpful and patient!

[Impactor]

I can confirm the problem still exists. Updating libs did not help
By the way, the problem is not associated to losing connection, as I thought before.