• Failure lauching application since iceweasel -> Firefox

    From Francesco Pietra@21:1/5 to All on Tue Jul 12 17:10:03 2016
    --001a114b30e2136391053770ce55
    Content-Type: text/plain; charset=UTF-8

    On last "upgrade" of amd64 wheezy I found Firefox in place of iceweasel.
    OK, except that the single commercial application in my box (Vuescan) now
    fails to upgrade


    francesco@tya64:~/Vuescan$ ./vuescan
    gvfs-open: http://www.hamrick.com/upgrade-l64.html: error launching application: Failed to execute child process "/usr/lib/iceweasel/iceweasel"
    (No such file or directory)
    francesco@tya64:~/Vuescan$


    I was unable to remedy with a softlink. What to do? Thanks

    francesco pietra

    --001a114b30e2136391053770ce55
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <div dir="ltr"><div><div>On last &quot;upgrade&quot; of amd64 wheezy I found Firefox in place of iceweasel. OK, except that the single commercial application in my box (Vuescan) now fails to upgrade<br><br><br>francesco@tya64:~/Vuescan$ ./vuescan<br>gvfs-
    open: <a href="http://www.hamrick.com/upgrade-l64.html">http://www.hamrick.com/upgrade-l64.html</a>: error launching application: Failed to execute child process &quot;/usr/lib/iceweasel/iceweasel&quot; (No such file or directory)<br>francesco@tya64:~/
    Vuescan$ <br><br><br></div>I was unable to remedy with a softlink. What to do? Thanks<br><br></div>francesco pietra<br></div>

    --001a114b30e2136391053770ce55--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lennart Sorensen@21:1/5 to Francesco Pietra on Tue Jul 12 23:50:01 2016
    On Tue, Jul 12, 2016 at 04:08:36PM +0200, Francesco Pietra wrote:
    On last "upgrade" of amd64 wheezy I found Firefox in place of iceweasel.
    OK, except that the single commercial application in my box (Vuescan) now fails to upgrade


    francesco@tya64:~/Vuescan$ ./vuescan
    gvfs-open: http://www.hamrick.com/upgrade-l64.html: error launching application: Failed to execute child process "/usr/lib/iceweasel/iceweasel" (No such file or directory)
    francesco@tya64:~/Vuescan$


    I was unable to remedy with a softlink. What to do? Thanks

    Why would some application be poking at another package's private
    internals? It should not be poking in /usr/lib/iceweasel. If it wants
    to do anything with iceweasel (or firefox) it should use the binary in
    /usr/bin to do so.

    I don't know who is responsible for gvfs-open trying to do that.

    --
    Len Sorensen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Wed Jul 13 18:50:01 2016
    Why don't you try http://www.palemoon.org installed as a portable (like /opt/palemoon) you don't need the installer, just unzip the package in place.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lennart Sorensen@21:1/5 to Francesco Pietra on Thu Jul 14 22:50:02 2016
    On Thu, Jul 14, 2016 at 08:17:04AM +0200, Francesco Pietra wrote:
    Here the reply by the developer of Vuescan, who had already let me know
    that he never heard of iceweasel:

    This isn’t being started from VueScan code – it’s probably
    something in a shared library.

    Regards,
    Ed Hamrick



    so, it seems to be an issue to be resolved within amd64 (Vuescan code works perfectly, it is only the updating that failed)

    Well I would think something in your gnome settings is doing it.

    Did you ever manually answer a question about how to open something and
    select iceweasel that way?

    --
    Len Sorensen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Francesco Pietra@21:1/5 to lsorense@csclub.uwaterloo.ca on Thu Jul 14 09:20:02 2016
    --089e012290da762b340537927395
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    Here the reply by the developer of Vuescan, who had already let me know
    that he never heard of iceweasel:

    This isn’t being started from VueScan code – it’s probably
    something in a shared library.

    Regards,
    Ed Hamrick



    so, it seems to be an issue to be resolved within amd64 (Vuescan code works perfectly, it is only the updating that failed)

    thanks

    francesco pietra

    On Tue, Jul 12, 2016 at 10:40 PM, Lennart Sorensen < lsorense@csclub.uwaterloo.ca> wrote:

    On Tue, Jul 12, 2016 at 04:08:36PM +0200, Francesco Pietra wrote:
    On last "upgrade" of amd64 wheezy I found Firefox in place of iceweasel. OK, except that the single commercial application in my box (Vuescan) now fails to upgrade


    francesco@tya64:~/Vuescan$ ./vuescan
    gvfs-open: http://www.hamrick.com/upgrade-l64.html: error launching application: Failed to execute child process
    "/usr/lib/iceweasel/iceweasel"
    (No such file or directory)
    francesco@tya64:~/Vuescan$


    I was unable to remedy with a softlink. What to do? Thanks

    Why would some application be poking at another package's private
    internals? It should not be poking in /usr/lib/iceweasel. If it wants
    to do anything with iceweasel (or firefox) it should use the binary in /usr/bin to do so.

    I don't know who is responsible for gvfs-open trying to do that.

    --
    Len Sorensen


    --089e012290da762b340537927395
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <div dir="ltr"><div><div><div>Here the reply by the developer of Vuescan, who had already let me know that he never heard of iceweasel:<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="
    gmail_quote"><div>This isn’t being started from VueScan code – it’s probably</div>
    <div>something in a shared library.</div>
    <div> </div>
    Regards,<br>Ed
    Hamrick<br></blockquote><br><br></div>so, it seems to be an issue to be resolved within amd64 (Vuescan code works perfectly, it is only the updating that failed)<br><br></div>thanks<br><br></div>francesco pietra<br></div><div class="gmail_extra"><br><div
    class="gmail_quote">On Tue, Jul 12, 2016 at 10:40 PM, Lennart Sorensen <span dir="ltr">&lt;<a href="mailto:lsorense@csclub.uwaterloo.ca" target="_blank">lsorense@csclub.uwaterloo.ca</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0
    0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Jul 12, 2016 at 04:08:36PM +0200, Francesco Pietra wrote:<br>
    &gt; On last &quot;upgrade&quot; of amd64 wheezy I found Firefox in place of iceweasel.<br>
    &gt; OK, except that the single commercial application in my box (Vuescan) now<br>
    &gt; fails to upgrade<br>
    &gt;<br>
    &gt;<br>
    &gt; francesco@tya64:~/Vuescan$ ./vuescan<br>
    &gt; gvfs-open: <a href="http://www.hamrick.com/upgrade-l64.html" rel="noreferrer" target="_blank">http://www.hamrick.com/upgrade-l64.html</a>: error launching<br>
    &gt; application: Failed to execute child process &quot;/usr/lib/iceweasel/iceweasel&quot;<br>
    &gt; (No such file or directory)<br>
    &gt; francesco@tya64:~/Vuescan$<br>
    &gt;<br>
    &gt;<br>
    &gt; I was unable to remedy with a softlink. What to do? Thanks<br>

    </span>Why would some application be poking at another package&#39;s private<br>
    internals?  It should not be poking in /usr/lib/iceweasel.  If it wants<br> to do anything with iceweasel (or firefox) it should use the binary in<br> /usr/bin to do so.<br>

    I don&#39;t know who is responsible for gvfs-open trying to do that.<br>
    <span class="HOEnZb"><font color="#888888"><br>
    --<br>
    Len Sorensen<br>
    </font></span></blockquote></div><br></div>

    --089e012290da762b340537927395--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lennart Sorensen@21:1/5 to Francesco Pietra on Fri Jul 15 21:00:02 2016
    On Fri, Jul 15, 2016 at 06:57:28PM +0200, Francesco Pietra wrote:
    I fear that on the amd64-gnome box my sources list should be amended:

    deb http://debian.netcologne.de/debian/ wheezy main contrib non-free

    Wheezy is long gone, given jessie was release well over a year ago now.
    Might be worth an upgrade.

    --
    Len Sorensen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Francesco Pietra@21:1/5 to lsorense@csclub.uwaterloo.ca on Fri Jul 15 20:00:01 2016
    --047d7b6705d98969710537af8368
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    I fear that on the amd64-gnome box my sources list should be amended:

    deb http://debian.netcologne.de/debian/ wheezy main contrib non-free
    deb-src http://debian.netcologne.de/debian/ wheezy main contrib non-free

    deb http://security.debian.org/ wheezy/updates main contrib non-free
    deb-src http://security.debian.org/ wheezy/updates main contrib non-free

    deb http://www.deb-multimedia.org wheezy main non-free

    deb http://mozilla.debian.net/ wheezy-backports iceweasel-release

    deb http://debian.netcologne.de/debian/ testing-proposed-updates main
    contrib non-free
    deb-src http://debian.netcologne.de/debian/ testing-proposed-updates main contrib non-free



    root@tya64:/home/francesco# aptitude update
    reports

    W: There is no public key available for the following key IDs: 1397BC53640DB551
    W: Failed to fetch
    http://mozilla.debian.net/dists/wheezy-backports/Release: Unable to find expected entry 'iceweasel-release/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)
    E: Some index files failed to download. They have been ignored, or old
    ones used instead.
    E: Couldn't rebuild package cache



    thanks for advice

    francesco pietra



    On Thu, Jul 14, 2016 at 9:47 PM, Lennart Sorensen < lsorense@csclub.uwaterloo.ca> wrote:

    On Thu, Jul 14, 2016 at 08:17:04AM +0200, Francesco Pietra wrote:
    Here the reply by the developer of Vuescan, who had already let me know that he never heard of iceweasel:

    This isn’t being started from VueScan code – it’s probably
    something in a shared library.

    Regards,
    Ed Hamrick



    so, it seems to be an issue to be resolved within amd64 (Vuescan code
    works
    perfectly, it is only the updating that failed)

    Well I would think something in your gnome settings is doing it.

    Did you ever manually answer a question about how to open something and select iceweasel that way?

    --
    Len Sorensen


    --047d7b6705d98969710537af8368
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <div dir="ltr"><div><div><div><font size="2">I fear that on the amd64-gnome box my sources list should be amended:<br><br></font><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><
    font size="2">deb <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> wheezy main contrib non-free</font><br><font size="2">deb-src <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a>
    wheezy main contrib non-free</font><br><br><font size="2">deb <a href="http://security.debian.org/">http://security.debian.org/</a> wheezy/updates main contrib non-free</font><br><font size="2">deb-src <a href="http://security.debian.org/">http://
    security.debian.org/</a> wheezy/updates main contrib non-free</font><br><br><font size="2">deb <a href="http://www.deb-multimedia.org">http://www.deb-multimedia.org</a> wheezy main non-free</font><br><br><font size="2">deb <a href="http://mozilla.debian.
    net/">http://mozilla.debian.net/</a> wheezy-backports iceweasel-release</font><br><br><font size="2">deb <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> testing-proposed-updates main contrib non-free</font><br><font
    size="2">deb-src <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> testing-proposed-updates main contrib non-free</font><br></blockquote><font size="2"><br><br>root@tya64:/home/francesco# aptitude update<br></font></
    <font size="2">reports<br></font><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><font size="2">W: There is no public key available for the following key IDs:</font><br><font
    size="2">1397BC53640DB551</font><br><font size="2">W: Failed to fetch <a href="http://mozilla.debian.net/dists/wheezy-backports/Release">http://mozilla.debian.net/dists/wheezy-backports/Release</a>: Unable to find expected entry &#39;iceweasel-release/
    binary-amd64/Packages&#39; in Release file (Wrong sources.list entry or malformed file)</font><br><font size="2">E: Some index files failed to download. They have been ignored, or old ones used instead.</font><br><font size="2">E: Couldn&#39;t rebuild
    package cache</font><br></blockquote><font size="2"><br><br></font></div><font size="2">thanks for advice<br><br></font></div><font size="2">francesco pietra<br></font><div><div><font size="2"><br></font><div><br></div></div></div></div><div class="gmail_
    extra"><br><div class="gmail_quote">On Thu, Jul 14, 2016 at 9:47 PM, Lennart Sorensen <span dir="ltr">&lt;<a href="mailto:lsorense@csclub.uwaterloo.ca" target="_blank">lsorense@csclub.uwaterloo.ca</a>&gt;</span> wrote:<br><blockquote class="gmail_quote"
    style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Jul 14, 2016 at 08:17:04AM +0200, Francesco Pietra wrote:<br>
    &gt; Here the reply by the developer of Vuescan, who had already let me know<br>
    &gt; that he never heard of iceweasel:<br>
    &gt;<br>
    &gt; This isn’t being started from VueScan code – it’s probably<br>
    &gt; &gt; something in a shared library.<br>
    &gt; &gt;<br>
    &gt; &gt; Regards,<br>
    &gt; &gt; Ed Hamrick<br>
    &gt; &gt;<br>
    &gt;<br>
    &gt;<br>
    &gt; so, it seems to be an issue to be resolved within amd64 (Vuescan code works<br>
    &gt; perfectly, it is only the updating that failed)<br>

    </span>Well I would think something in your gnome settings is doing it.<br>

    Did you ever manually answer a question about how to open something and<br> select iceweasel that way?<br>
    <span class="HOEnZb"><font color="#888888"><br>
    --<br>
    Len Sorensen<br>
    </font></span></blockquote></div><br></div>

    --047d7b6705d98969710537af8368--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Francesco Pietra@21:1/5 to lsorense@csclub.uwaterloo.ca on Sat Jul 16 12:00:01 2016
    --089e011834dc217db60537bcea0a
    Content-Type: text/plain; charset=UTF-8

    Following dist-upgrade wheezy->jessie, linux prompt could only be reached
    from 3.2.0-4 sysinit and no screen

    startx

    mdprobe error /libkmod/libkmod-module.c:816 kmod_module_insert_module()
    could not find module by name 'nvidia-current'

    Then, I adjusted the sources.list as for my GPU work station, where wheezy->jessie had been carried out long ago:

    deb http://debian.netcologne.de/debian/ jessie main contrib non-free
    deb-src http://debian.netcologne.de/debian/ jessie main contrib non-free

    deb http://security.debian.org/ jessie/updates main contrib non-free
    deb-src http://security.debian.org/ jessie/updates main contrib non-free

    deb http://www.deb-multimedia.org wheezy main non-free

    deb http://debian.netcologne.de/debian/ jessie-proposed-updates main
    contrib non-free
    deb-src http://debian.netcologne.de/debian/ jessie-proposed-updates main contrib non-free


    i.e., testing -> jessie for proposed updates
    jessie -> wheezy for multimedia

    Following #aptitude update/upgrade

    startx
    gnome-session

    performed perfectly.

    uname -r
    3.2.0-4

    i.e., 3.16-0-4 was not used in combination with nvidia. Is my procedure
    correct or should jessie be used for also multimedia?

    thanks

    francesco pietra


    On Fri, Jul 15, 2016 at 7:56 PM, Lennart Sorensen < lsorense@csclub.uwaterloo.ca> wrote:

    On Fri, Jul 15, 2016 at 06:57:28PM +0200, Francesco Pietra wrote:
    I fear that on the amd64-gnome box my sources list should be amended:

    deb http://debian.netcologne.de/debian/ wheezy main contrib non-free

    Wheezy is long gone, given jessie was release well over a year ago now.
    Might be worth an upgrade.

    --
    Len Sorensen


    --089e011834dc217db60537bcea0a
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div>Following dist-upgrade wheezy-&gt;jessie, linux prompt could only be reached from 3.2.0-4 sysinit and no screen<div><br></div><div>startx<br></div><div><br></div><div>mdprobe error /
    libkmod/libkmod-module.c:816 kmod_module_insert_module()</div><div>could not find module by name &#39;nvidia-current&#39;</div><br></div>Then, I adjusted the sources.list as for my GPU work station, where wheezy-&gt;jessie had been carried out long ago:<
    <br><blockquote>deb <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> jessie main contrib non-free<br>deb-src <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> jessie main contrib
    non-free<br><br>deb <a href="http://security.debian.org/">http://security.debian.org/</a> jessie/updates main contrib non-free<br>deb-src <a href="http://security.debian.org/">http://security.debian.org/</a> jessie/updates main contrib non-free<br><br>
    deb <a href="http://www.deb-multimedia.org">http://www.deb-multimedia.org</a> wheezy main non-free<br><br>deb <a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> jessie-proposed-updates main contrib non-free<br>deb-src <
    a href="http://debian.netcologne.de/debian/">http://debian.netcologne.de/debian/</a> jessie-proposed-updates main contrib non-free<br></blockquote><br></div>i.e., testing -&gt; jessie for proposed updates<br></div>       jessie -&gt; wheezy for
    multimedia<br><br></div>Following #aptitude update/upgrade<br><br></div>startx<br></div>gnome-session<br><br></div>performed perfectly.<br><br></div>uname -r<br>3.2.0-4<br><br></div>i.e., 3.16-0-4 was not used in combination with nvidia. Is my procedure
    correct or should jessie be used for also multimedia?<br><br></div>thanks<br><br></div>francesco pietra<br><div><div><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><
    <div class="gmail_quote">On Fri, Jul 15, 2016 at 7:56 PM, Lennart Sorensen <span dir="ltr">&lt;<a href="mailto:lsorense@csclub.uwaterloo.ca" target="_blank">lsorense@csclub.uwaterloo.ca</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="
    margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Jul 15, 2016 at 06:57:28PM +0200, Francesco Pietra wrote:<br>
    &gt; I fear that on the amd64-gnome box my sources list should be amended:<br> &gt;<br>
    &gt; deb <a href="http://debian.netcologne.de/debian/" rel="noreferrer" target="_blank">http://debian.netcologne.de/debian/</a> wheezy main contrib non-free<br>

    </span>Wheezy is long gone, given jessie was release well over a year ago now.<br>
    Might be worth an upgrade.<br>
    <span class="HOEnZb"><font color="#888888"><br>
    --<br>
    Len Sorensen<br>
    </font></span></blockquote></div><br></div>

    --089e011834dc217db60537bcea0a--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)