kakaroto, "Fix commited" means "A fix has been included in the
(upstream) code".
I'll create a debdiff this evening (I'm in CET) and will request
sponsorship and SRU once I'm ready.
** Changed in: amsn (Ubuntu)
Assignee: (unassigned) => petski (petski)
** Summary changed:
- aMSN fails to l
great!
Pablo: I'm curious, changing the bug status to "Fix committed", does it mean
that ubuntu 9.04 now has a new update for aMSN that includes that patch?
Thanks,
KaKaRoTo
--
aMSN fails to launch after upgrading to Jaunty
https://bugs.launchpad.net/bugs/371103
You received this bug notificati
** Changed in: amsn (Ubuntu)
Status: Incomplete => Fix Committed
--
aMSN fails to launch after upgrading to Jaunty
https://bugs.launchpad.net/bugs/371103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I like that fix better. Thank you!
--
aMSN fails to launch after upgrading to Jaunty
https://bugs.launchpad.net/bugs/371103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Hi, thanks omega13a and petski for the great investigation!
the PATH is set before plugins are loaded, but the plugins are loaded before
you connect and the msntranslator/gnotify plugin does a simple "package require
http", which loads the latest version (2.7.2). We know that the version 2.7.2
o
I found two plugins that contain package require http. They are
msntranslator and gnotify. Changing the occurance of package require
http in msntranslator to package require -exact http 2.4.4 solves the
problem. A rather crude fix if you ask me. I don't know to much about
amsn's source code but I s
I managed to reproduce your error in a test-script. Find it attached.
I have the idea that somewhere, somehow, some script does a "package
require http", which results in the conflict. Maybe in
$HOME/.amsn/plugins?
** Attachment added: "lp371103 testscript"
http://launchpadlibrarian.net/264088
Purging amsn-data and then reinstalling it didn't help.
The provide lin is /usr/share/amsn/utils/http2.4/http.tcl reads package
provide http 2.4.4
Also, here's the file permission stuff for the contents of both the file
and the utils directory:
omega...@omega13a-desktop:~$ ls -l /usr/share/amsn/
For some reason, amsn skips /usr/share/amsn/utils/http2.4/http.tcl
Which filepermissions does it have? Can user "omega13a" read/execute
that file? What's the "provide" line in that file say? Could you please
reinstalled the "amsn-data" package?
--
aMSN fails to launch after upgrading to Jaunty
h
I found the file that is causing the problem. Its a file that didn't
show up in the search for files named http. Its
/usr/share/tcltk/tcl8.5/tcl8/http-2.7.2.tm . Running dpkg -S
/usr/share/tcltk/tcl8.5/tcl8/http-2.7.2.tm says its from the tcl8.5
package...
--
aMSN fails to launch after upgrading
Here's the output of the things you suggested:
omega...@omega13a-desktop:~/amsn-0.97.2$ sudo updatedb
omega...@omega13a-desktop:~/amsn-0.97.2$ locate http.tcl
/home/omega13a/.wine/drive_c/Program
Files/DeFFNetIzer/tcl/tcl8.4/http1.0/http.tcl
/home/omega13a/.wine/drive_c/Program
Files/DeFFNetIzer/
** Changed in: amsn (Ubuntu)
Status: New => Incomplete
--
aMSN fails to launch after upgrading to Jaunty
https://bugs.launchpad.net/bugs/371103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Thank you for your bugreport.
There might be an unwanted version of "http.tcl" somewhere on your
filesystem (in ~/plugins/ ?). Please find all files with the name
"http.tcl" on your filesystem and send us the output of the command.
p...@workmate:~$ sudo updatedb
p...@workmate:~$ locate http.tcl
13 matches
Mail list logo
