Your message dated Thu, 12 Jan 2012 15:08:02 +0100
with message-id <[email protected]>
and subject line Re: Bug#651268: uzbl-core: error while loading shared 
libraries: libwebkit-1.0.so.2
has caused the Debian Bug report #651268,
regarding uzbl-core: error while loading shared libraries: libwebkit-1.0.so.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
651268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651268
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: uzbl
Version: 0.0.0~git.20111001-1
Severity: important

Dear Maintainer,

I installed uzbl from the unstable repo
ii uzbl  0.0.0~git.20111001-1   Lightweight Webkit browser following the UNIX 
philosophy

however, starting uzbl-browser will produce the following error: (edited $HOME 
for real name)

$ uzbl-browser 
{'cookie_jar': '$HOME/.local/share/uzbl/cookies.txt',
'cookie_socket': '$HOME/.cache/uzbl/cookie_daemon_socket',
'cookie_whitelist': '$HOME/.config/uzbl/cookie_whitelist',
'daemon_mode': True,
'daemon_timeout': 0,
'use_whitelist': False,
'verbose': True}
uzbl-cookie-daemon: detected daemon listening on 
'$HOME/.cache/uzbl/cookie_daemon_socket'
uzbl-event-manager: will auto close.
uzbl-event-manager: found pid file: '$HOME/.cache/uzbl/event_daemon.pid'
uzbl-event-manager: event daemon already started with pid: 5464
uzbl-core: error while loading shared libraries: libwebkit-1.0.so.2: cannot 
open shared object file: No such file or directory

ll /usr/lib/libwebkit*
lrwxrwxrwx 1 root root       26 2011-11-15 19:37 /usr/lib/libwebkitgtk-1.0.so.0 
-> libwebkitgtk-1.0.so.0.11.0*
-rwxr-xr-x 1 root root 23982024 2011-11-15 19:37 
/usr/lib/libwebkitgtk-1.0.so.0.11.0*

something is clearly missing.
Do not hesitate to contact me, if you need further information.
Thanks for making Debian!

Cheers,
Erich

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages uzbl depends on:
ii  libatk1.0-0                 2.2.0-2
ii  libc6                       2.13-21
ii  libcairo2                   1.10.2-6.1
ii  libfontconfig1              2.8.0-3
ii  libfreetype6                2.4.8-1
ii  libgdk-pixbuf2.0-0          2.24.0-1
ii  libglib2.0-0                2.30.2-4
ii  libgtk2.0-0                 2.24.8-2
ii  libjavascriptcoregtk-1.0-0  1.6.1-5+b1
ii  libpango1.0-0               1.29.4-2
ii  libsoup2.4-1                2.36.1-1
ii  libwebkitgtk-1.0-0          1.6.1-5+b1
ii  libx11-6                    2:1.4.4-4
ii  python                      2.7.2-9
ii  python-gobject              3.0.2-4
ii  python-gtk2                 2.24.0-2
ii  python-support              1.0.14

Versions of packages uzbl recommends:
pn  python-simplejson  2.2.0-1
pn  socat              <none>
pn  suckless-tools     38-1
pn  xclip              <none>
pn  zenity             <none>

uzbl suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---

> $ type -a uzbl-core
> uzbl-core is /home/ew/bin/uzbl-core
> uzbl-core is /usr/bin/uzbl-core
> 
> There we go!
> I removed $HOME/bin from PATH to test this and everything
> works like a charm!

> bug report can be closed.



-- 
 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.    | lucab (AT) debian.org
`. `'`                          | GPG Key ID: 3BFB9FB3
  `-     http://www.debian.org  | Debian GNU/Linux Developer

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to