Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201736 > unrolled thread
| Started by | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| First post | 2018-10-27 10:30 +0200 |
| Last post | 2018-10-27 14:50 +0200 |
| Articles | 20 on this page of 73 — 17 participants |
Back to article view | Back to linux.debian.user
i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 10:30 +0200
Re: i386 version for chrome Andrew Wood <andrewjameswood@ymail.com> - 2018-10-27 10:40 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 12:40 +0200
Re: i386 version for chrome Roberto C. Sánchez <roberto@debian.org> - 2018-10-27 13:10 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 13:30 +0200
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 14:10 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 15:10 +0200
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 16:10 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 17:00 +0200
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 18:00 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 17:00 +0200
Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-27 17:20 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 19:20 +0200
Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-27 20:30 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 23:30 +0200
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 00:50 +0200
Re: i386 version for chrome David <bouncingcats@gmail.com> - 2018-10-28 00:30 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 01:00 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 01:00 +0200
Re: i386 version for chrome David <bouncingcats@gmail.com> - 2018-10-28 23:00 +0100
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-28 10:10 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 12:00 +0100
Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-29 12:00 +0100
resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 13:00 +0100
Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 13:50 +0100
Re: resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 14:20 +0100
Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 14:20 +0100
Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 14:50 +0100
Re: resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 16:40 +0100
Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-28 01:00 +0200
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-28 16:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 17:20 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 11:30 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-27 20:40 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 23:40 +0200
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 08:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 11:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 11:40 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 12:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 13:50 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 17:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 17:30 +0100
Re: i386 version for chrome The Wanderer <wanderer@fastmail.fm> - 2018-10-28 18:00 +0100
Re: i386 version for chrome john doe <johndoe65534@mail.com> - 2018-10-28 18:10 +0100
Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 18:20 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 12:20 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 13:30 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 13:40 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 14:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 15:50 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 15:50 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 16:10 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 21:20 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 21:20 +0100
Re: i386 version for chrome John Hasler <jhasler@newsguy.com> - 2018-10-29 21:30 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-29 21:40 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-29 21:50 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 20:00 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 20:10 +0100
Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 20:30 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 00:40 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 12:20 +0100
Re: i386 version for chrome Thomas D Dial <tdial@acm.org> - 2018-10-28 04:10 +0100
Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-28 15:50 +0100
Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 17:10 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 17:40 +0200
Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 22:00 +0200
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 00:10 +0200
Re: i386 version for chrome David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 04:10 +0100
Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-11-03 04:40 +0100
Re: i386 version for chrome tony <lists@vanderhoff.org> - 2018-10-27 15:10 +0200
Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 13:50 +0200
Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 14:50 +0200
Page 1 of 4 [1] 2 3 4 Next page →
| From | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| Date | 2018-10-27 10:30 +0200 |
| Subject | i386 version for chrome |
| Message-ID | <wNs8O-6Vx-3@gated-at.bofh.it> |
hi, I wanted to install chrome on my intel desktop, but the only version I found is amd64. Is it possible to get the i386 version? best regards, -- Pierre Frenkiel
[toc] | [next] | [standalone]
| From | Andrew Wood <andrewjameswood@ymail.com> |
|---|---|
| Date | 2018-10-27 10:40 +0200 |
| Message-ID | <wNsiu-6Yr-3@gated-at.bofh.it> |
| In reply to | #201736 |
On 27/10/2018 09:19, Pierre Frenkiel wrote: > hi, > I wanted to install chrome on my intel desktop, but the only version I > found > is amd64. Is it possible to get the i386 version? > > best regards, Google no longer produce a 32 bit version but you could try vivaldi which is based on Chrome and has a 32 bit version https://vivaldi.com/download/
[toc] | [prev] | [next] | [standalone]
| From | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| Date | 2018-10-27 12:40 +0200 |
| Message-ID | <wNuaC-85I-7@gated-at.bofh.it> |
| In reply to | #201737 |
On Sat, 27 Oct 2018, Andrew Wood wrote:
> Google no longer produce a 32 bit version but you could try vivaldi which is
> based on Chrome and has a 32 bit version
> https://vivaldi.com/download/
>
thank you.
I installed it, but I'm not convince by its features
1/ I want to define my ~/bookmarks.html file as home page, but
it insists putting a https:// before my file://...
2/ worst: playing sound only works on youtube, but I can't play
mp3 files from other sites. I get the error:
ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: no supported streams"}
ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_NO_SUPPORTED_STREAMS
I think I'll revert to chromium
best regards,
--
Pierre Frenkiel
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2018-10-27 13:10 +0200 |
| Message-ID | <wNuDF-8uF-7@gated-at.bofh.it> |
| In reply to | #201739 |
On Sat, Oct 27, 2018 at 12:37:04PM +0200, Pierre Frenkiel wrote: > On Sat, 27 Oct 2018, Andrew Wood wrote: > > > Google no longer produce a 32 bit version but you could try vivaldi > > which is based on Chrome and has a 32 bit version > > https://vivaldi.com/download/ > > > thank you. > I installed it, but I'm not convince by its features > > 1/ I want to define my ~/bookmarks.html file as home page, but > it insists putting a https:// before my file://... > Did you try an absolute path? file:///home/user/bookmarks.html I don't think the file:// protocol works with a path unless it starts with /. Regards, -Roberto -- Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| Date | 2018-10-27 13:30 +0200 |
| Message-ID | <wNuWZ-9A-3@gated-at.bofh.it> |
| In reply to | #201740 |
On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: > Did you try an absolute path? > > file:///home/user/bookmarks.html I tried it, and also file://~user... but the problem is not there, but in the fact that, as I said, it puts a https:// before.. which of course can't work Anyway, what interested me was the additional features that chrome adds to chromium. best regards, -- Pierre Frenkiel
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2018-10-27 14:10 +0200 |
| Message-ID | <wNvzJ-BO-21@gated-at.bofh.it> |
| In reply to | #201741 |
On 2018-10-27, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote: > On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: > >> Did you try an absolute path? >> >> file:///home/user/bookmarks.html > I tried it, and also file://~user... > > but the problem is not there, but in the fact that, as I said, > it puts a https:// before.. > which of course can't work > > Anyway, what interested me was the additional features that chrome > adds to chromium. These folks appear to have found some kind of workaround for the https prefixation syndrome: https://forum.vivaldi.net/topic/28038/how-to-set-a-local-file-as-home-page > best regards, -- "Now she understood that Anna could not have been in lilac, and that her charm was just that she always stood out against her attire, that her dress could never be noticeable on her." Leo Tolstoy, Anna Karenina
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-27 15:10 +0200 |
| Message-ID | <wNwvL-1be-1@gated-at.bofh.it> |
| In reply to | #201743 |
On Saturday 27 October 2018 08:05:13 Curt wrote: > On 2018-10-27, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote: > > On Sat, 27 Oct 2018, Roberto C. S?nchez wrote: > >> Did you try an absolute path? > >> > >> file:///home/user/bookmarks.html > > > > I tried it, and also file://~user... > > > > but the problem is not there, but in the fact that, as I said, > > it puts a https:// before.. > > which of course can't work > > > > Anyway, what interested me was the additional features that > > chrome adds to chromium. > > These folks appear to have found some kind of workaround for the https > prefixation syndrome: > > https://forum.vivaldi.net/topic/28038/how-to-set-a-local-file-as-home- >page > > > best regards, Might be nice, but several of the dependecies can only be satisfied if on stretch, and the curl command lines don't work on wheezy. At all. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2018-10-27 16:10 +0200 |
| Message-ID | <wNxrQ-1Ke-5@gated-at.bofh.it> |
| In reply to | #201745 |
On 2018-10-27, Gene Heskett <gheskett@shentel.net> wrote: >> >> These folks appear to have found some kind of workaround for the https >> prefixation syndrome: >> >> https://forum.vivaldi.net/topic/28038/how-to-set-a-local-file-as-home- >>page >> >> > best regards, > > Might be nice, but several of the dependecies can only be satisfied if on > stretch, and the curl command lines don't work on wheezy. At all. > Gnomic. I searched the cited page for 'curl' and didn't find one reference to it; then I realized you were talking about something else but remain uncertain exactly what. At any rate a curl command line that proves inoperable on Wheezy arouses the interest of even the most jaded observer. -- "Now she understood that Anna could not have been in lilac, and that her charm was just that she always stood out against her attire, that her dress could never be noticeable on her." Leo Tolstoy, Anna Karenina
[toc] | [prev] | [next] | [standalone]
| From | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| Date | 2018-10-27 17:00 +0200 |
| Message-ID | <wNyed-20G-1@gated-at.bofh.it> |
| In reply to | #201748 |
On Sat, 27 Oct 2018, Curt wrote: > At any rate a curl command line that proves inoperable on Wheezy arouses > the interest of even the most jaded observer. I found it on Stretch, but was unable to use it for a ftp transfer, while ncftp works like a charm. best regards, -- Pierre Frenkiel
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2018-10-27 18:00 +0200 |
| Message-ID | <wNzai-2zW-11@gated-at.bofh.it> |
| In reply to | #201749 |
On 2018-10-27, Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote: > On Sat, 27 Oct 2018, Curt wrote: > >> At any rate a curl command line that proves inoperable on Wheezy arouses >> the interest of even the most jaded observer. > > I found it on Stretch, but was unable to use it for a ftp transfer, > while ncftp works like a charm. That's interesting. > best regards, -- "Now she understood that Anna could not have been in lilac, and that her charm was just that she always stood out against her attire, that her dress could never be noticeable on her." Leo Tolstoy, Anna Karenina
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-27 17:00 +0200 |
| Message-ID | <wNyef-20G-23@gated-at.bofh.it> |
| In reply to | #201748 |
On Saturday 27 October 2018 09:58:45 Curt wrote: > On 2018-10-27, Gene Heskett <gheskett@shentel.net> wrote: > >> These folks appear to have found some kind of workaround for the > >> https prefixation syndrome: > >> > >> https://forum.vivaldi.net/topic/28038/how-to-set-a-local-file-as-ho > >>me- page > >> > >> > best regards, > > > > Might be nice, but several of the dependecies can only be satisfied > > if on stretch, and the curl command lines don't work on wheezy. At > > all. > > Gnomic. I searched the cited page for 'curl' and didn't find one > reference to it; then I realized you were talking about something else > but remain uncertain exactly what. > > At any rate a curl command line that proves inoperable on Wheezy > arouses the interest of even the most jaded observer. f you goto the vivaladi page, and look up its helpers, it gives a loooooong curl command to fetch them, but pasted into bash shell and return is pressed, you wind up with zero action and an empty prompt. A ctl+c gets you back your normal prompt. But thats all experimental any way since dpkg outputs quite a string of its own dependencies not met: root@coyote:/home/gene/Downloads# dpkg -i vivaldi-stable_2.1.1337.36-1_i386.deb Selecting previously unselected package vivaldi-stable. (Reading database ... 517038 files and directories currently installed.) Unpacking vivaldi-stable (from vivaldi-stable_2.1.1337.36-1_i386.deb) ... dpkg: dependency problems prevent configuration of vivaldi-stable: vivaldi-stable depends on libappindicator3-1; however: Package libappindicator3-1 is not installed. vivaldi-stable depends on libc6 (>= 2.16); however: Version of libc6:i386 on system is 2.13-38+deb7u12. vivaldi-stable depends on libgtk-3-0 (>= 3.9.10); however: Version of libgtk-3-0:i386 on system is 3.4.2-7+deb7u1. vivaldi-stable depends on libpango-1.0-0 (>= 1.14.0); however: Package libpango-1.0-0 is not installed. vivaldi-stable depends on libpangocairo-1.0-0 (>= 1.14.0); however: Package libpangocairo-1.0-0 is not installed. dpkg: error processing vivaldi-stable (--install): dependency problems - leaving unconfigured Processing triggers for menu ... Processing triggers for desktop-file-utils ... Errors were encountered while processing: vivaldi-stable So its not going to work on a 32 bit wheezy, ever. I'll update this machine to a 64 bit stretch if and when the network works again. Armbian is now working on a rock64, but thats the only variety of nix for arm64 that will accept and use a gateway statement in its net config and it took me a week to make that work. I put another drive in an older dell dimension and installed 64 bit stretch, but was never able to get it to accept a gateway statement. No errors, it just ignores it unless applied by hand using route. So its back on the old wheezy drive which Just Works(TM) That machine isn't quite sacrificial as its the box I use to program the mesa fpga based CNC cards, so its needed eventually. Its actually got a parport! And them is scarce on new machines today. :( Thanks Curt. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Steve McIntyre <steve@einval.com> |
|---|---|
| Date | 2018-10-27 17:20 +0200 |
| Message-ID | <wNyxA-2mE-25@gated-at.bofh.it> |
| In reply to | #201750 |
Gene Heskett wrote: >On Saturday 27 October 2018 09:58:45 Curt wrote: > >root@coyote:/home/gene/Downloads# dpkg -i >vivaldi-stable_2.1.1337.36-1_i386.deb >Selecting previously unselected package vivaldi-stable. >(Reading database ... 517038 files and directories currently installed.) >Unpacking vivaldi-stable (from vivaldi-stable_2.1.1337.36-1_i386.deb) ... > >dpkg: dependency problems prevent configuration of vivaldi-stable: > vivaldi-stable depends on libappindicator3-1; however: > Package libappindicator3-1 is not installed. > > vivaldi-stable depends on libc6 (>= 2.16); however: > Version of libc6:i386 on system is 2.13-38+deb7u12. > > vivaldi-stable depends on libgtk-3-0 (>= 3.9.10); however: > Version of libgtk-3-0:i386 on system is 3.4.2-7+deb7u1. > > vivaldi-stable depends on libpango-1.0-0 (>= 1.14.0); however: > Package libpango-1.0-0 is not installed. > > vivaldi-stable depends on libpangocairo-1.0-0 (>= 1.14.0); however: > Package libpangocairo-1.0-0 is not installed. > >dpkg: error processing vivaldi-stable (--install): > dependency problems - leaving unconfigured >Processing triggers for menu ... >Processing triggers for desktop-file-utils ... >Errors were encountered while processing: > vivaldi-stable > >So its not going to work on a 32 bit wheezy, ever. That's hardly a surprise. Wheezy was released over 5 years ago, and isn't even in LTS any more. >I'll update this machine to a 64 bit stretch if and when the network >works again. Armbian is now working on a rock64, but thats the only >variety of nix for arm64 that will accept and use a gateway statement >in its net config You keep on asserting this, but it's patently not true. That's a standard feature of Debian on all architectures. I understand you've seen problems, but it just needs debugging to see how things were broken in your case. :-( -- Steve McIntyre, Cambridge, UK. steve@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-27 19:20 +0200 |
| Message-ID | <wNApI-3ui-23@gated-at.bofh.it> |
| In reply to | #201752 |
On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > Gene Heskett wrote: > >On Saturday 27 October 2018 09:58:45 Curt wrote: > > > >root@coyote:/home/gene/Downloads# dpkg -i > >vivaldi-stable_2.1.1337.36-1_i386.deb > >Selecting previously unselected package vivaldi-stable. > >(Reading database ... 517038 files and directories currently > > installed.) Unpacking vivaldi-stable (from > > vivaldi-stable_2.1.1337.36-1_i386.deb) ... > > > >dpkg: dependency problems prevent configuration of vivaldi-stable: > > vivaldi-stable depends on libappindicator3-1; however: > > Package libappindicator3-1 is not installed. > > > > vivaldi-stable depends on libc6 (>= 2.16); however: > > Version of libc6:i386 on system is 2.13-38+deb7u12. > > > > vivaldi-stable depends on libgtk-3-0 (>= 3.9.10); however: > > Version of libgtk-3-0:i386 on system is 3.4.2-7+deb7u1. > > > > vivaldi-stable depends on libpango-1.0-0 (>= 1.14.0); however: > > Package libpango-1.0-0 is not installed. > > > > vivaldi-stable depends on libpangocairo-1.0-0 (>= 1.14.0); however: > > Package libpangocairo-1.0-0 is not installed. > > > >dpkg: error processing vivaldi-stable (--install): > > dependency problems - leaving unconfigured > >Processing triggers for menu ... > >Processing triggers for desktop-file-utils ... > >Errors were encountered while processing: > > vivaldi-stable > > > >So its not going to work on a 32 bit wheezy, ever. > > That's hardly a surprise. Wheezy was released over 5 years ago, and > isn't even in LTS any more. > > >I'll update this machine to a 64 bit stretch if and when the network > >works again. Armbian is now working on a rock64, but thats the only > >variety of nix for arm64 that will accept and use a gateway statement > >in its net config > > You keep on asserting this, but it's patently not true. That's a > standard feature of Debian on all architectures. I understand you've > seen problems, but it just needs debugging to see how things were > broken in your case. :-( Then give me an install that can be made to work in a hosts file defined local network that can accept a gateway statement in its e/n/i file. The default install does NOT accept it until the network has been brought up. And the syntax for the deprecated route command is too complex to remember, then everybody wants me to use ip-(mumble) for that without anything that resembles a man page to tell me how to use it for that. Thats the singular most obtuse man pages group I've tried to make sense of in 35+ years of making networks work starting even before Hayes modems were the default. The arm64 stretch install has, as e/n/i.d/eth0: auto eth0 iface eth0 inet static address 192.168.NN.2/24 gateway 192.168.NN.1 dns-nameserver 192.168.NN.1 dns-search hosts dns And that works, I just got it from that machine with an ssh login. So all the stuff that used to be in e/resolv.conf is now in that file, but no one in 2 damned years of my asking questions has ever mentioned that its been moved or why. To add to the confusion, /etc/resolv.conf is now a link that returns a list of nameservers only. But is there any documentation for all the shuffling? Not thats been converted to a utf8 file I can peruse and learn from. Sorry Steve, but your claim that its simply not true, pulls my trigger, best to duck. And maybe fix a few man pages. Please. ;-) -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Steve McIntyre <steve@einval.com> |
|---|---|
| Date | 2018-10-27 20:30 +0200 |
| Message-ID | <wNBvr-467-15@gated-at.bofh.it> |
| In reply to | #201756 |
Gene Heskett wrote: >On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: >> >> You keep on asserting this, but it's patently not true. That's a >> standard feature of Debian on all architectures. I understand you've >> seen problems, but it just needs debugging to see how things were >> broken in your case. :-( > >Then give me an install that can be made to work in a hosts file defined >local network that can accept a gateway statement in its e/n/i file. The >default install does NOT accept it until the network has been brought >up. And the syntax for the deprecated route command is too complex to >remember, then everybody wants me to use ip-(mumble) for that without >anything that resembles a man page to tell me how to use it for that. >Thats the singular most obtuse man pages group I've tried to make sense >of in 35+ years of making networks work starting even before Hayes >modems were the default. Right. The ip-* man pages are atrocious, I won't argue - they're basically not human-readable. :-( >The arm64 stretch install has, as e/n/i.d/eth0: Checking: is that straight Debian stretch, or some derivative? >auto eth0 >iface eth0 inet static >address 192.168.NN.2/24 >gateway 192.168.NN.1 >dns-nameserver 192.168.NN.1 >dns-search hosts dns I'm assuming that "NN" is a placeholder you've added, and not copied verbatim from the file! Otherwise, that last line looks suspect. The "dns-nameserver" and "dns-search" lines are instructions for resolvconf when setting up networking. The "dns-search" line is meant to be passed straight through into resolv.conf to set up a DNS search path. A valid example from the resolvconf man page is "dns-search foo.org bar.com". What that means is that each time you look up something that's no fully-qualified (e.g. "foo"), this machine will be looking for "foo.hosts" then "foo.dns". That's probably not what you want. However, it'll be harmless if you're looking up FQDN hostnames all the time. >And that works, I just got it from that machine with an ssh login. > >So all the stuff that used to be in e/resolv.conf is now in that file, >but no one in 2 damned years of my asking questions has ever mentioned >that its been moved or why. To add to the confusion, /etc/resolv.conf is >now a link that returns a list of nameservers only. But is there any >documentation for all the shuffling? Not thats been converted to a utf8 >file I can peruse and learn from. This is down to the resolvconf package, which is often pulled in via Recommends: from other packages. For a simple network with simple needs, you shouldn't need to use it. It should work for you, though. It manages resolv.conf, hence wanting to move the normal config from that file. If you *don't* have resolvconf installed, putting the details in /etc/resolv.conf still works, and it's how I configure static things on my own network (e.g. on the gateway/router box). >Sorry Steve, but your claim that its simply not true, pulls my trigger, >best to duck. I understand - I've seen you're struggling, but I know this stuff works on lots of other machines. There's nothing broken here on standard Debian on any architecture that I know of. *However*, remotely debugging what other thing might be causing your woes is really difficult. -- Steve McIntyre, Cambridge, UK. steve@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-27 23:30 +0200 |
| Message-ID | <wNEjF-5Nf-31@gated-at.bofh.it> |
| In reply to | #201759 |
On Saturday 27 October 2018 14:21:23 Steve McIntyre wrote: > Gene Heskett wrote: > >On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > >> You keep on asserting this, but it's patently not true. That's a > >> standard feature of Debian on all architectures. I understand > >> you've seen problems, but it just needs debugging to see how things > >> were broken in your case. :-( > > > >Then give me an install that can be made to work in a hosts file > > defined local network that can accept a gateway statement in its > > e/n/i file. The default install does NOT accept it until the network > > has been brought up. And the syntax for the deprecated route > > command is too complex to remember, then everybody wants me to use > > ip-(mumble) for that without anything that resembles a man page to > > tell me how to use it for that. Thats the singular most obtuse man > > pages group I've tried to make sense of in 35+ years of making > > networks work starting even before Hayes modems were the default. > > Right. The ip-* man pages are atrocious, I won't argue - they're > basically not human-readable. :-( And who might we beat about the brow over that, I've already got the elm club for that job carved. :) > >The arm64 stretch install has, as e/n/i.d/eth0: > > Checking: is that straight Debian stretch, or some derivative? Armbian I believe, Steve, thats what the default xfce login gui says anyway, but a cat /etc/issue says: gene@rock64:~$ cat /etc/issue Debian GNU/Linux 9 \n \l, and a uname -a: gene@rock64:~$ uname -a Linux rock64 4.4.124-rk3328 #24 SMP Wed Mar 28 17:15:52 CEST 2018 aarch64 GNU/Linux > >auto eth0 > >iface eth0 inet static > >address 192.168.NN.2/24 > >gateway 192.168.NN.1 > >dns-nameserver 192.168.NN.1 > >dns-search hosts dns > > I'm assuming that "NN" is a placeholder you've added, and not copied > verbatim from the file! Of course, I don't really want to give the farm to the first hacker that gets thru dd-wrt (which FWIW has yet to occur in 15+ years of having it standing guard here). > Otherwise, that last line looks suspect. The "dns-nameserver" and > "dns-search" lines are instructions for resolvconf when setting up > networking. The "dns-search" line is meant to be passed straight > through into resolv.conf to set up a DNS search path. A valid example > from the resolvconf man page is "dns-search foo.org bar.com". What > that means is that each time you look up something that's no > fully-qualified (e.g. "foo"), this machine will be looking for > "foo.hosts" then "foo.dns". That's probably not what you > want. However, it'll be harmless if you're looking up FQDN hostnames > all the time. > > >And that works, I just got it from that machine with an ssh login. > > > >So all the stuff that used to be in e/resolv.conf is now in that > > file, but no one in 2 damned years of my asking questions has ever > > mentioned that its been moved or why. To add to the confusion, > > /etc/resolv.conf is now a link that returns a list of nameservers > > only. But is there any documentation for all the shuffling? Not > > thats been converted to a utf8 file I can peruse and learn from. > > This is down to the resolvconf package, which is often pulled in via > Recommends: from other packages. For a simple network with simple > needs, you shouldn't need to use it. It should work for you, > though. It manages resolv.conf, hence wanting to move the normal > config from that file. > > If you *don't* have resolvconf installed, putting the details in > /etc/resolv.conf still works, and it's how I configure static things > on my own network (e.g. on the gateway/router box). > > >Sorry Steve, but your claim that its simply not true, pulls my > > trigger, best to duck. > > I understand - I've seen you're struggling, but I know this stuff > works on lots of other machines. There's nothing broken here on > standard Debian on any architecture that I know of. *However*, > remotely debugging what other thing might be causing your woes is > really difficult. I've considered enableing dhcpd in the router, and matching the mac to the address issued. I did have that setup years ago to service my old lappy but that only worked around 25% of the time, and since I am no longer playing visiting fireman at other tv stations, its now hard coded in the hosts files which works unless the cat5 has been cut. In 15 years of blowing in the wind that piece of cat5 is still doing 100 megabaud over 45 feet of it to the shop building. I'm suitably amazed, as its survived 110+ mph winds that it took $18K to fix up the rest of the damages to the house and fencing, took out 3.5 40+ foot pines too. I finally took out the half of the 4th one last year as it was looking uglier by the year. Back on topic, sorta. The last time I tried a debian-arm as a dl and write to the sd card, failed just like the amd64 versions, plus armbian doesn't hard code the first user=1000, which IMNSHO is just inexcusable breakage by denying sudo to the the user doing the install. But thats a separate horse I think. If you feed it right, you can make it work most of the time. I believe the phrase we're looking for here is "cast iron bitch"? Thanks Steve. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2018-10-28 00:50 +0200 |
| Message-ID | <wNFz4-6tj-11@gated-at.bofh.it> |
| In reply to | #201764 |
On Sat 27 Oct 2018 at 17:21:43 -0400, Gene Heskett wrote: > On Saturday 27 October 2018 14:21:23 Steve McIntyre wrote: > > > Gene Heskett wrote: > > >On Saturday 27 October 2018 11:09:48 Steve McIntyre wrote: > > >> You keep on asserting this, but it's patently not true. That's a > > >> standard feature of Debian on all architectures. I understand > > >> you've seen problems, but it just needs debugging to see how things > > >> were broken in your case. :-( > > > > > >Then give me an install that can be made to work in a hosts file > > > defined local network that can accept a gateway statement in its > > > e/n/i file. The default install does NOT accept it until the network > > > has been brought up. And the syntax for the deprecated route > > > command is too complex to remember, then everybody wants me to use > > > ip-(mumble) for that without anything that resembles a man page to > > > tell me how to use it for that. Thats the singular most obtuse man > > > pages group I've tried to make sense of in 35+ years of making > > > networks work starting even before Hayes modems were the default. > > > > Right. The ip-* man pages are atrocious, I won't argue - they're > > basically not human-readable. :-( > > And who might we beat about the brow over that, I've already got the elm > club for that job carved. :) Not really on topic but that's in tune with many of your posts. Violence is never a solution. (Your smiley doesn't take the edge off the implied threat). > > -- > Cheers, Gene Heskett > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > Genes Web page <http://geneslinuxbox.net:6309/gene> -- Since 1968, more than 1.5 million Americans have died in gun-related incidents in the USA. More than have been killed in war in US history. Defending freedom has a high price.
[toc] | [prev] | [next] | [standalone]
| From | David <bouncingcats@gmail.com> |
|---|---|
| Date | 2018-10-28 00:30 +0200 |
| Message-ID | <wNFfH-6mH-13@gated-at.bofh.it> |
| In reply to | #201759 |
On Sun, 28 Oct 2018 at 05:21, Steve McIntyre <steve@einval.com> wrote: > Gene Heskett wrote: > > >auto eth0 > >iface eth0 inet static > >address 192.168.NN.2/24 > >gateway 192.168.NN.1 > >dns-nameserver 192.168.NN.1 > >dns-search hosts dns > > I'm assuming that "NN" is a placeholder you've added, and not copied > verbatim from the file! > > Otherwise, that last line looks suspect. The "dns-nameserver" and > "dns-search" lines are instructions for resolvconf when setting up > networking. The "dns-search" line is meant to be passed straight > through into resolv.conf to set up a DNS search path. A valid example > from the resolvconf man page is "dns-search foo.org bar.com". What > that means is that each time you look up something that's no > fully-qualified (e.g. "foo"), this machine will be looking for > "foo.hosts" then "foo.dns". That's probably not what you > want. However, it'll be harmless if you're looking up FQDN hostnames > all the time. There seems to be an ongoing theme here with lines that look like *search hosts dns popping up in other places in Gene's system. See: https://lists.debian.org/debian-user/2017/10/msg00857.html https://lists.debian.org/debian-user/2017/10/msg00859.html Gene, the line > >dns-search hosts dns that you show above does not match anything documented by the manpages on wheezy. I checked interfaces(5) resolv.conf(5) resolvconf(8) nsswitch.conf(5) Gene, what are you trying to achieve with that line?
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-28 01:00 +0200 |
| Message-ID | <wNFIK-6wG-1@gated-at.bofh.it> |
| In reply to | #201767 |
On Saturday 27 October 2018 18:20:16 David wrote: > On Sun, 28 Oct 2018 at 05:21, Steve McIntyre <steve@einval.com> wrote: > > Gene Heskett wrote: > > >auto eth0 > > >iface eth0 inet static > > >address 192.168.NN.2/24 > > >gateway 192.168.NN.1 > > >dns-nameserver 192.168.NN.1 > > >dns-search hosts dns > > > > I'm assuming that "NN" is a placeholder you've added, and not copied > > verbatim from the file! > > > > Otherwise, that last line looks suspect. The "dns-nameserver" and > > "dns-search" lines are instructions for resolvconf when setting up > > networking. The "dns-search" line is meant to be passed straight > > through into resolv.conf to set up a DNS search path. A valid > > example from the resolvconf man page is "dns-search foo.org > > bar.com". What that means is that each time you look up something > > that's no fully-qualified (e.g. "foo"), this machine will be looking > > for "foo.hosts" then "foo.dns". That's probably not what you > > want. However, it'll be harmless if you're looking up FQDN hostnames > > all the time. > > There seems to be an ongoing theme here with lines that look like > *search hosts dns > popping up in other places in Gene's system. > > See: > https://lists.debian.org/debian-user/2017/10/msg00857.html > https://lists.debian.org/debian-user/2017/10/msg00859.html > > Gene, the line > > > >dns-search hosts dns > > that you show above does not match anything documented by > the manpages on wheezy. I checked > interfaces(5) > resolv.conf(5) > resolvconf(8) > nsswitch.conf(5) > > Gene, what are you trying to achieve with that line? Whatever it takes to get a working gateway at bootup. Next time I reboot, I'll kill that line first. If I can't ping yahoo.com, (= no gateway. so it cannot get to the internet) I'll put it back. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-10-28 01:00 +0200 |
| Message-ID | <wNFIK-6wG-19@gated-at.bofh.it> |
| In reply to | #201769 |
On Saturday 27 October 2018 18:49:13 Gene Heskett wrote: > On Saturday 27 October 2018 18:20:16 David wrote: > > On Sun, 28 Oct 2018 at 05:21, Steve McIntyre <steve@einval.com> wrote: > > > Gene Heskett wrote: > > > >auto eth0 > > > >iface eth0 inet static > > > >address 192.168.NN.2/24 > > > >gateway 192.168.NN.1 > > > >dns-nameserver 192.168.NN.1 > > > >dns-search hosts dns > > > > > > I'm assuming that "NN" is a placeholder you've added, and not > > > copied verbatim from the file! > > > > > > Otherwise, that last line looks suspect. The "dns-nameserver" and > > > "dns-search" lines are instructions for resolvconf when setting up > > > networking. The "dns-search" line is meant to be passed straight > > > through into resolv.conf to set up a DNS search path. A valid > > > example from the resolvconf man page is "dns-search foo.org > > > bar.com". What that means is that each time you look up something > > > that's no fully-qualified (e.g. "foo"), this machine will be > > > looking for "foo.hosts" then "foo.dns". That's probably not what > > > you want. However, it'll be harmless if you're looking up FQDN > > > hostnames all the time. > > > > There seems to be an ongoing theme here with lines that look like > > *search hosts dns > > popping up in other places in Gene's system. > > > > See: > > https://lists.debian.org/debian-user/2017/10/msg00857.html > > https://lists.debian.org/debian-user/2017/10/msg00859.html > > > > Gene, the line > > > > > >dns-search hosts dns > > > > that you show above does not match anything documented by > > the manpages on wheezy. I checked > > interfaces(5) > > resolv.conf(5) > > resolvconf(8) > > nsswitch.conf(5) And I just noticed you were checking wheezy, but the problem is in a stretch install, wheezy works fine using 5 yo man pages. Stretch does not, using year old man pages that are installed with stretch. > > Gene, what are you trying to achieve with that line? > > Whatever it takes to get a working gateway at bootup. Next time I > reboot, I'll kill that line first. If I can't ping yahoo.com, (= no > gateway. so it cannot get to the internet) I'll put it back. Thanks David. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David <bouncingcats@gmail.com> |
|---|---|
| Date | 2018-10-28 23:00 +0100 |
| Message-ID | <wO1ge-2xI-3@gated-at.bofh.it> |
| In reply to | #201771 |
On Sun, 28 Oct 2018 at 09:59, Gene Heskett <gheskett@shentel.net> wrote: > On Saturday 27 October 2018 18:49:13 Gene Heskett wrote: > > On Saturday 27 October 2018 18:20:16 David wrote: > > > > > > There seems to be an ongoing theme here with lines that look like > > > *search hosts dns > > > popping up in other places in Gene's system. > > > > > > See: > > > https://lists.debian.org/debian-user/2017/10/msg00857.html > > > https://lists.debian.org/debian-user/2017/10/msg00859.html > > > > > > Gene, the line > > > > > > > >dns-search hosts dns > > > > > > that you show above does not match anything documented by > > > the manpages on wheezy. I checked > > > interfaces(5) > > > resolv.conf(5) > > > resolvconf(8) > > > nsswitch.conf(5) > > And I just noticed you were checking wheezy, but the problem is in a > stretch install, wheezy works fine using 5 yo man pages. Stretch does > not, using year old man pages that are installed with stretch. I checked wheezy only because I thought that's what you use, I didn't read carefully enough, sorry. Regardless, it makes no difference, the man pages say that lines search hosts dns or dns-search hosts dns do NOT work the way you seem to think, regardless of which file they're in. The dns-search version that goes in /etc/network/interfaces is documented in resolvconf(8). It does NOT accept arguments like "hosts" or "dns", according to the man pages. I have not read the source though.
[toc] | [prev] | [next] | [standalone]
Page 1 of 4 [1] 2 3 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web