Fwd: Failure lauching application since iceweasel -> Firefox
Incidentally, also the Vuescan issue was resolved with jessie upgrading -- Forwarded message -- From: Francesco Pietra <chiendar...@gmail.com> Date: Sat, Jul 16, 2016 at 11:07 AM Subject: Fwd: Failure lauching application since iceweasel -> Firefox To: amd64 Debian <debian-amd64@lists.debian.org>, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> I must quickly update my post. Following a reboot francesco@tya64:~$ uname -r 3.16.0-4-amd64 francesco@tya64:~$ -- Forwarded message -- From: Francesco Pietra <chiendar...@gmail.com> Date: Sat, Jul 16, 2016 at 10:56 AM Subject: Re: Failure lauching application since iceweasel -> Firefox To: Lennart Sorensen <lsore...@csclub.uwaterloo.ca> Cc: amd64 Debian <debian-amd64@lists.debian.org> 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 < lsore...@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 >
Fwd: Failure lauching application since iceweasel -> Firefox
I must quickly update my post. Following a reboot francesco@tya64:~$ uname -r 3.16.0-4-amd64 francesco@tya64:~$ -- Forwarded message -- From: Francesco Pietra <chiendar...@gmail.com> Date: Sat, Jul 16, 2016 at 10:56 AM Subject: Re: Failure lauching application since iceweasel -> Firefox To: Lennart Sorensen <lsore...@csclub.uwaterloo.ca> Cc: amd64 Debian <debian-amd64@lists.debian.org> 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 < lsore...@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 >
Re: Failure lauching application since iceweasel -> Firefox
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 < lsore...@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 >
Re: Failure lauching application since iceweasel -> Firefox
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
Re: Failure lauching application since iceweasel -> Firefox
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 < lsore...@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 >
Re: Failure lauching application since iceweasel -> Firefox
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 < lsore...@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 >
Re: Failure lauching application since iceweasel -> Firefox
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.
Re: Failure lauching application since iceweasel -> Firefox
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
Failure lauching application since iceweasel -> Firefox
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
